scarecrow

You will need kdelibs3 and qt3 (both should be available), plus downgrading a couple of libraries. The latter could be a serious issue. My recommendation: 1. Use another music manager. Songbird is very buggy and eating too much RAM, Banshee is even buggier and very sluggish (typically for a Mono app), but Quodlibet, Exaile and Rhythmbox ain't bad at all. Even better is the new (0.6.X series) Listen, which is GTK, but with rather few GNOME dependencies. And finally, the best music manager for windoze ( Foobar2000 ) works very, very well under WINE. 2. Use Amarok 2, and wait for improvements. Already Amarok 2.1 is more than usable.

You don't need it, and anyway such convertions are not recommended, unless you are a very experienced user. You may well fall into what's described as "RPM hell": unresolved dependencies, replacement of existing files, breakage of shared libraries.

It's crashing quite often here. It's not a skin/gtk theme issue (I have already changed a few), so I guess something is wrong with xulrunner 1.9.1.1 I may try an unbranded version (without xulrunner) to see if it works better.

HAL is not crashing. Draksnapshot is. https://mandrivausers.org/index.php?showtopic=87973 There's no remedy ATM. Simply do not use draksnapshot, until it is fixed. About the memory issue: Since you are using a 32-bit OS, utilizing 3 GB out of 4 is normal. To utilize 4GB, you have to enable PAE in the system BIOS, and install a himem kernel, or use a 64-bit Mandriva. In both cases, you will have more available RAM, but worse performance. Advice: Leave it as-it-is... 32-bit apps cannot use more than 2 GB RAM, by design.

It may be the fact that several newer versions of the bluez library are very buggy. I have eventually sorted it out, but I did have serious problems with quite a few versions of bluez. Since I have no idea which bluez version 2009.1 is using, I cannot give a solid advice.

qtdesigner or glade are the easiest I can recall.

Dolphin is a very good filemanager, once you get used to its peculiarities. But KDE lets you use as default konqueror, if you wish so, or even krusader, or any non-kde filemanager (for some time I was using thunar compiled with no xfce4 desktop dependencies). KDE 4.2.4 still has issues, but the current unstable KDE 4.3 release (RC2) is simply great. Most plasma crashes are cured, and the only serious issue ATM is qtcurve glitches (but then again, qtcurve is NOT part of the KDE4 project).

Give first the output of uname -a and then of lsmod | grep snd My guess it's either a pc speaker module loading and conflicting with the alsa modules, or that crap pulseaudio server is acting again...

Synaptic does have a progress indicator, and it's not used in Fedora. Are you sure you didn't load Ubuntu instead? :P

You have to load any composite manager BEFORE loading awn. The simplest one is xorg's xcompmgr, but most DE's (KDE4, Gnome, XFCE4) do have compositing as an option of their default windoze manager. It can be turned on or off fairly easily. About compiz, I really have no idea, never used it. I'm using compiz-fusion with aiglx though, with native nvidia compositing support, and awn loads without issues.

Look for "rarlinux" or something like that, although installing it by hand should not create any dependency issues.

https://qa.mandriva.com/show_bug.cgi?id=46618 It has been reported many months ago, but apparently it's not fixed yet. Solution: use something else instead.

urpmi libqt4-devel should do the trick. qmake is part of qt.

Just get rarlinux from here and read "makefile" You can change PREFIX to any convenient in your PATH, e.g. /usr instead of /usl/local

The point is having a more reliable solution than ReactOS, and a cheaper one than windoze. Ain't that a point good enough?

I can already boot my XP installation both physically and as a virtual machine. Currently working with VMWare 6.5.2, but I'm considering switching to VirtualBox 3, once it will become less buggy. I more or less followed the tutorial in Vbox forums ( http://forums.virtualbox.org/viewtopic.php?f=2&t=9697 ) with just a couple of adaptations. However, I still need a few times to boot XP natively, as DirectX support is still incomplete in VMWare, and in VirtualBox it was just implemented, and many nuts and bolts are loose.

Try adding the "noatime" flag in your fstab for the CIFS entries. Since I do not have any Mandriva handy right now, can you tell me if the netfs daemon is loaded before, or after hal? You may also have to change the permissions for cifs.mount and cifs.umount, e.g # chmod u+x mount.cifs etc

The question is as above... To my rather poor knowledge, ext4 partitions are readable under windows by the known drivers for ext2/3, but for achieving that you must disable barriers (no problem, I've already disabled that) as well as extents (which is an issue- it pretty much defies the usage of ext4). I wouldn't mind a read-only driver, writing to ext4 is not a priority... but being able to read my ext4 partitions on the rare instances I boot into windozeXP would be handy. And yeah, I know about the bugs that still are present on ext4, and that for certain things reiser 3.6 is rather faster, but I've converted to ext4 and I do not want to go back- at least until ButterFS gets some sort of reliability.

Usually CMOS batteries on laptops are soldered on the mainboard, and removing them can be a pain in the butt.

Most distros have "powertop" in their repos. Hopefully Mandriva, too.

Foxit does have a Linux version since at least one year ago, but it works since February or so. Before that, it was segfaulting even with all sorts of compatibility libs installed. Yes, it's not opensource. Podofo is, but it's just a library-the only UI for it I currently know is Scribus-qt4 The current version renders fonts in an ugly way, but after all, the same applies for Evince. Arcoread renders flawlessly, but 70+ MB for a pure PDF reader is rather too much for many users, while okular is a superb document reader, but... it depends on kdelibs4.

FYI it's not just crappy media: the backend (cdrkit) is a bad hack of cdrtools. It simply does not work well- period.

It's both snappier and more themeable than 3.0.X, but still I find it's RAM usage to be on the high side.

I guess you are running all the laptop mode utils: cpufreq, pm-utils, and all. If you do and still you have heating problems, please run Intel's powertop to find out what is causing that.

# Entry for /dev/sda5 : UUID=f8d97912-6435-11de-bfcd-2b9329108ba0 / ext3 relatime 1 1 # Entry for /dev/sda12 : UUID=01d3e2e0-53fd-42d0-b786-96f0c488f1f1 /home ext3 relatime 1 2 # Entry for /dev/sda6 : UUID=e5143227-d5f8-46e8-87fe-6d5ff20a3c2f /home1 ext3 relatime 1 2 /dev/cdrom /media/cdrom auto umask=0,users,iocharset=utf8,noauto,ro,exec 0 0 /dev/fd0 /media/floppy auto umask=0,users,iocharset=utf8,noauto,exec,flush 0 0 # Entry for /dev/sda1 : UUID=01C6A4C7DBC66FA0 /mnt/windows ntfs-3g defaults 0 0 none /proc proc defaults 0 0 # Entry for /dev/sda10 : UUID=c8cc7479-0436-45d4-a70d-7cc17cca35a0 swap swap defaults 0 0 # Entry for /dev/sda11 : UUID=135c1f17-1e9a-4445-b831-f371be917360 swap swap defaults 0 0 /dev/sda7 <mount point 1> vfat umask=000,iocharset=utf8 0 0 /dev/sda8 <mount point 2> vfat umask=000,iocharset=utf8 0 0 /dev/sda9 <mount point 3> vfat umask=000,iocharset=utf8 0 0 /dev/sdb1 <mount point 4> vfat umask=000,iocharset=utf8 0 0 /dev/sdd1 <mount point 5> vfat umask=000,iocharset=utf8 0 0 Paste the above in a file named "fstab". Replace <mount point n> with an actual, existing mount point at your system, and then replace your /etc/fstab with that one (as root). Note that the above does not take care of the issue of two swap drives, and to be honest I don't understand the reason to use FAT32 partitions anywhere- excluding pen drives. They could, and should be substituted by NTFS.