Jump to content


  • Posts

  • Joined

  • Last visited

Extra Info

  • Your CPU
    Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
  • Your Graphics Card
    EVGA GeForce 9500 GT
  • Your RAM
    2G Corsair Twin2X2048-8500C5D 1066MHz
  • Your Hard Drive
    2x 40G Seagate ST340016A ata, 80G MAXTOR 6L080L4 ata, 120G SeagateST3120026A ata, 2x 500G Seagate ST3500630AS sata, 250G Seagate ST3250824A ata
  • Your Sound Card
    onboard 82801JI (ICH10 Family) HD Audio Controller
  • Your Operating System
    Mandriva Linux release 2010.0 (Official-PWP) for x86_64
  • Your Monitor
    Samsung Syncmaster 220WM
  • Your Case
    Ultra ULT31824 Aluminus Mid Tower ATX, 12 Bays

Contact Methods

  • Website URL
  • ICQ

Profile Information

  • Gender
  • Location
    Oakland, CA
  • Interests

rolf's Achievements


frequent (3/7)



  1. I did try the rpm, google-chrome-beta- (google-chrome-beta_current_x86_64.rpm) at http://www.google.com/chrome/intl/en/w00t.html I had google-chrome- from Mandriva Turkiye http://forum.mandriva.com/viewtopic.php?p=740623&sid=816040c774f4e2bdac260f9f97bd7570#740623 installed with a release date of 27 Oct 2009 vs. 06 Dec 2009 for google-chrome-beta, so decided to try the newer build. There was no signature that I could find, so I ok'd the warning, and, since the package name is different, I guess, I had to uninstall the mvt program, first, due to conflicting files. It's ok and I've sometimes loaded google-chrome in case it can handle hulu.com better but I don't see that it does. I would expect if I'm opening a new Tab from link (middle-click), that page would display automatically but it doesn't and I don't see a place to configure it. I'd say it works fine, for what it is, but I won't use it, much. Thanks for the link! :)
  2. Won't know till you try! I would say rpm/urpmi are pretty reliable and, as long as you don't use --force or --nodeps, it won't allow you to break the system. Personally, I haven't heard anything about old-rpmdrake breaking anything but I haven't heard much about anyone using it. Whether using it meets your needs, you are the only one who can tell.
  3. The last I heard is the panel applet is broken and not being sold as a service anymore. My first post in this thread suggested the old rpmdrake is installable but I don't see anyone trying that.
  4. Hi. I've come to use the command line as I find it to be more stable and flexible, so I don't know if it would help you but I have heard the old version of rpmdrake has been kept in the distro. I hardly ever use the gui and have not tried this but here is some info about it: [rolf@localhost ~]$ urpmq -y rpmdrake old_rpmdrake park-rpmdrake rpmdrake [rolf@localhost ~]$ urpmq -i old_rpmdrake Name : old_rpmdrake Version : 2.27 Release : 2mdv2007.0 Group : System/Configuration/Packaging Size : 546141 Architecture: i586 Source RPM : old_rpmdrake-2.27-2mdv2007.0.src.rpm Build Host: n3.mandriva.com Packager : Iurt the rebuild bot <warly@mandriva.com> URL : http://cvs.mandriva.com/cgi-bin/cvsweb.cgi/soft/rpmdrake/ Summary : Mandriva Linux graphical front end for sofware installation/removal Description : rpmdrake is a simple graphical frontend to manage software packages on a Mandriva Linux system; it has 3 different modes: - software packages installation; - software packages removal; - MandrivaUpdate (software packages updates). A fourth program manages the media (add, remove, edit). [rolf@localhost ~]$ su Password: [root@localhost rolf]# urpmi --test old_rpmdrake installing old_rpmdrake-2.27-2mdv2007.0.i586.rpm from /mnt/hd/media/contrib/release Preparing... ################################################################################ ######## Installation is possible [root@localhost rolf]# You (or I) could remove the --test option to install old_rpmdrake. (You need a contrib source added.)
  5. I wonder if you re-started X after editing xorg.conf?
  6. That's about what I was thinking, also, but I would link to what Opera says are its search paths, such as /usr/lib/opera/plugins opera: [plugin path ] #001: /usr/lib/opera/plugins opera: [plugin path ] #002: /usr/lib/netscape/plugins opera: [plugin path ] #003: /usr/lib/mozilla/plugins So, I would do # ln -s /usr/lib/mozilla-firefox-1.0.2/libxpcom.so /usr/lib/opera/plugins for example.
  7. I don't know what you mean by this. urpmf shows what package(s) contain a given file. They don't have to be installed, just in one of the urpmi media. I was saying the error message seemed to be saying it couldn't find this file. If so, maybe that is because it isn't in the path Opera searches for plugins, implied by other lines in the console output you posted. So, I suggested to make a link in the path Opera searches to this file.
  8. I've got a Microsoft wheel mouse, ps/2 connected, that is working with the wheel OK. That part of my xorg.conf looks like:
  9. Does is say it can't find libxpcom.so? [rolf@localhost ~]$ urpmf libxpcom.so nvu:/usr/lib/nvu-0.81/libxpcom.so mozilla-firefox:/usr/lib/mozilla-firefox-1.0.2/libxpcom.so mozilla-thunderbird:/usr/lib/mozilla-thunderbird-1.0.2/libxpcom.so mozilla:/usr/lib/mozilla-1.7.6/libxpcom.so mozilla:/usr/lib/mozilla-1.7.6/libxpcom.so mozilla-firefox:/usr/lib/mozilla-firefox-1.0.2/libxpcom.so [rolf@localhost ~]$ urpmf /usr/lib/mozilla/plugins/mplayerplug-in.so mplayerplugin:/usr/lib/mozilla/plugins/mplayerplug-in.so mplayerplugin:/usr/lib/mozilla/plugins/mplayerplug-in.so How about if you link one of the libxpcom.so files into your opera plugin path?
  10. I am in mozilla. Although you checked about:config, did you see that the settings are correct in Edit > Preferences > Advanced > Mouse Wheel? Just in case.
  11. rolf

    Hello all [solved]

    For each release, Mandriva provides official updates, mostly security fixes. To get those, add an updates source from the easyurpmi site and, as root, do: urpmi --update --auto-select Or, run MandrakeUpdate from terminal or the Menu > System > Configuration > Packaging. There are gui frontends to the urpmi family of commands at that spot As new updates are added to the mirror, you have to download the new package list to urpmi's database: urpmi.update --update then run the first command to see if there are new packages to install. Read the manual pages; man urpmi man urpmi.addmedia man urpmi.update man urpmf man urpmq and the manuals listed at the bottom of each man page. There is a pretty intense tutorial about using urpmi here: http://mandrake.vmlinuz.ca/bin/view/Main/UsingUrpmi Also, there are comprehensive manuals at the Doc link at the top of the MandrivaLinux main page: http://www1.mandrivalinux.com/en-us/
  12. # urpmf /usr/share/emacs/21.3/etc/TUTORIAL emacs-doc:/usr/share/emacs/21.3/etc/TUTORIAL emacs-doc:/usr/share/emacs/21.3/etc/TUTORIAL.cs emacs-doc:/usr/share/emacs/21.3/etc/TUTORIAL.de It is not clear whether that path is on your machine. It is from emacs-doc. Do you have that installed? You can see with rpm -q emacs-doc
  13. Guarddog is pretty easy. Press the Help button and read the KDE Guarddog Handbook. For a one-box web browser, just check the protocols you need to have served to you in the Internet Zone. Putting the X will 'Block' packets, sending confirmation to the sender, and will show 'Closed' at grc.com, so don't X if you want 'Stealth'. Some of the protocols I need are http, https, dns, ftp, cddb, smtp, pop, Real Audio, bittorrent... All are checked in the Internet Zone and it tests Stealth. The current Mandriva guarddog has a bug that it won't load the rules at boot, so you have to open and OK guarddog to start it. This bug is fixed in the latest Mandriva rpm at the author's site: http://www.simonzone.com/software/guarddog/ or in the cooker contrib/ package: ftp://ftp.ciril.fr/pub/linux/mandrakelinu...0-3mdk.i586.rpm
  14. You seem to me to have followed a pretty unorthodox path: installing a giant software suite from a source outside the distro, throwing some distro stuff at it that I wouldn't try, personally: there are plenty of reports of problems with the 3.4 upgrade, and a power failure on top of that. All I can suggest is a search at www.google.com Maybe someone else recognizes a solution.
  15. As the message says, the error will be toward the end of the log. I don't know which log; I would think it would be in the directory the build was in when the error occured. There will be, at least, the same error messages you get on the terminal, maybe more.
  • Create New...