scarecrow

Yes, it's out for more than one month. It's the "enhanced" Go-OO version that went 3.1 (or 3.1.0.6, to be more exact) at June 2nd... The final version was the same as go-oo 3.1.0 RC7 which was out at May 29th (I think).

Ooops, sorry- I saw it late: The "server" kernel will not work with the proprietary nvidia driver. You need either e "desktop" kernel, or a patch for the server kernel (although I have no idea how that patch could probably be... sorry).

There are premade for Mandy 2009.1, and they are autoupdated via DKMS every time you upgrade kernel, but you can also use the binary from nvidia. The procedure there is standard: 1. Download the binary and make it executable ( chmod +x blah ) 2. Install kernel headers for your running kernel 3. Go to runlevel 3, login as root, and run the nvidia binary. You will have to answer just a couple of easy questions. The driver is rather kernel-depandent, and less x-server dependent. Using Mandy 9001.1 there are good chances you will still use either the "nv" or "vesa" driver even after installing the proprietary driver, because there is no xorg.conf file. You can easily remedy that by running as root # nvidia-xconfig or maybe # nvidia-xconfig --composite (the second one also enables native compositing via aiglx) and then, restart the xserver.

I think you need mplayer/mencoder compiled with AMR support to do that. Have no idea if the PLF version has AMR support, though... my self-compiled mplayer has AMR and vdpau support, and no GTK gui.

# urpmi kernel-headers should be enough (unless you are using a custom kernel (most likely not), or some third party one from /contrib. For the record, the kernel modules you're looking for are already prebuilt for Mandriva... all you have to do is installing virtualbox from the official repos (although I think it's the OSE version, not the PUEL one).

Before upgrading, please clear the browser cache and try again.

No - just delete or comment ( # at the start of the line) the last line, and add right after it alias net-pf-10 off As Ian suggested. Now- to unload the ipv6 module you must first stop the network daemon and then "modprobe -r ipv6", or windows-style, reboot... As for a probable different behaviour of Seamonkey and Firefox, I think (not sure) that in Mandriva both are using xulrunner 1.9.X, so their behaviour should be more or less the same.

Yes, It's really very good. Personally, I use since quite some time ago Opera 10 snapshots from http://my.opera.com/desktopteam/blog/ (the gcc4/qt4 version as well, currently build 4402, which is more or less the same as beta1). It's my default browser under ArchLinux/KDEMod 4.2.3 (I also have Konqueror with the webkit engine, FF 3.5 beta4 and Arora from git). Most of the usual java quirks are gone, streaming media are working very well (via gnome-mplayer/gecko-mediaplayer combo), flash is pretty much OK... I'm quite happy with it. Turbo is suitable only for dialup users- DSL ones should rather forget its existence.

Is the kernel ipv6 module disabled? To find out, #lsmod | grep net-pf-10 Or also #lsmod | grep ipv6 (net-pf-10 is just an alias to the ipv6 module). Also, if you are connecting via DHCP, then you're likely using your ISP's DNS servers, which may not resolve some IP's very fast. A good idea (most of the times, anyway) is switching to the OpenDNS servers, which are very fast and do not bloack any IP's by default. You must add these lines at the top of your /etc/resolv.conf configuration file: nameserver 208.67.222.222 nameserver 208.67.220.220 and then restart the network daemon ( # service network restart )

Just a stupid question: Why do you use compiz (fusion) with KDE4? The embedded KDE4 window manager effects with composite enabled may not be as impressive as the ones from Compiz, but that are quite good, and they consume very little resources. I only use compiz-fusion under XFCE4 and LXDE, where the WM effects are very spartan/nonexistent, respectively. Under KDE4, I do not use compiz at all.

Likely the chip is identified as the wrong model (they are quite a few which are using the snd-hda-intel module). See here: http://my.opera.com/pacho/blog/show.dml/3290753 If you don't find an answer there, an idea would be switching to OSS v.4, which generally has less issues and offers better sound quality, although it does have its own quirks with certain applications and hardware (namely MIDI and the laptop's power management features).

# urpmi xscreensaver-gl xscreensaver-base sounds like a good pick. You can likely find some more screensavers in /contrib and PLF. IMO an installation CD should not include screensavers, artwork and clipart- just the necessary core binaries. You can add whatever you like after installing.

Then, please consider turning off the kernel tickless timer (which is on by default in most stock Mandriva kernels). It's not sure that THIS is the reason of your hard lockups, but nevertheless it's a common symptom with certain hardware configurations and VMWare and/or VirtualBox running at the host system. To disable the tickless timer, simply add an argument nohz=off at the kernel boot string in /boot/grub/menu.lst You can find several instances of that in the forum.

Are you running VMWare or VirtualBox?

Generally, it's a very good idea to have separate / and /home partitions for backup purposes, as well as other things (e.g. reiserfs 3.6 is still the fastest for / while for /home you may wish to use ext4 or xfs), but I highly doubt that putting them in different HD's will help, speed-wise.

Your "extra features" probably included some buggy plasmoids. Don't worry, everyone has made this mistake (myself- innumerable times -DUH!). Instead of logging out, try alt+F2 (it should work, even with plasma crashed) and type in killall plasma && plasma (the first argument is for removing any zombie plasma instances). The second step is of course removing the problematic plasmoid.

I don't have a solution for everything, but I can say with enough confidence that gecko-mediaplayer works ten times better than mplayerplugin. Actually both come from the same author.

You may wish giving Vuescan a spin: www.hamrick.com This is working with most scanners, including the V100, and it's working really great: the output quality is stellar. That's the good news. The bad news are it's commercial, and rather expensive.

I really doubt if you will see any speed gains that way. Ubuntu is rather slow compared to Mandy, and Nautilus is the slowest filemanager out there, by a huge margin.

Errr... you told me so! The version of Java in your PATH is: java version "1.6.0_0" OpenJDK Runtime Environment (IcedTea6 1.4.1) (mandriva-0.19.b14.3mdv2009.1-i386) OpenJDK Client VM (build 14.0-b08, mixed mode)

You are running OpenJDK, not Sun JRE. On principle, I would prefer opensource to "just" freeware, but I had quite a few regressions with OpenJDK... so, ATM I am still using Sun JRE until OpenJDK gets a bit more mature/

That's interesting. I'm using it under Arch Linux with Sun Java 6u13 (monolithic package), no JDK, and a "semi official" Archlinux specific build (from the distro's Community repo). It works straight out of the box, without the need to run it as root once, or something like that. I would file a bug report at Frostwire forum, but since they do not seem to consider the way they package the Mandriva RPM as faulty, it could be pointless...

Monospace is a whole family of fonts with a common characteristic (fixed char width), and not a particular font. Perhaps the one you used is not unicode?

Here's a post about the same issue on Frostwire forums: http://forum.frostwire.com/viewtopic.php?f=5&t=5881 Which means, that in the end it ***IS*** a matter of java- or rather, the way java packages are split in Mandriva, and the way the Frostwire RPM is built. IMO this RPM is just faulty- it should just refuse to install due to missing dependencies.

You can run it from everywhere. I have it on /usr/share/frostwire with just a startup script at /usr/bin All settings are stored in the user's folder, and it runs fine for me (with jre 6u13)- no need to run it as root first time, or whatever.