(posting to planet in the hopes that some kind soul has a clue what’s going on)
So most eyes these days seem to be firmly focused on that other operating system release, but I want to talk about Gutsy for a bit. A few nights ago I updated my machine to it, and there are quite a few new problems, and also quite a few old ones that are still not fixed.
Update 2007-10-31: Most of the below is now fixed. For explanations, see the comments at the bottom of this post.
- [FIXED] Somehow whenever I boot, my system believes it’s necessary to make my harddisk churn continuously. It didn’t use to do this on Feisty, I have a gig of RAM on this machine and am only running a webbrowser and Gnome Terminal, so I doubt my ‘extreme use’ is the cause of it all. System Monitor manages to tell me that udevd is eating CPU, at least (I can’t figure out how to monitor harddisk activity). “man udevd” seems to be telling me “it could be anything telling me what to do, I’m just a humble event daemon”. So no clue where that’s coming from.
- [FIXED] I can’t mount my other partitions anymore. Windows has no trouble finding them though, and Feisty had always been fine with them. The three partitions in question are formatted using NTFS (1) and FAT32 (2). Running “sudo mount /winC” manually gets me:
fuse: mount failed: Device or resource busy
FUSE mount point creation failed
Unmounting /dev/sda1 ()
- [FIXED] Somehow I now have a huuuge submenu “Other” in my Applications menu, containing things varying from “Browser Identification” to “Zeroconf Service Detection” to “Fonts” (twice) to “AdBlocK Filters” (To my knowledge, I’ve never installed this) to “Joystick” (I don’t have a joystick). This didn’t use to be there on Feisty, either. It doesn’t seem to serve any purpose whatsoever. Why did it pop up?
- [PROBABLY FIXED] It seems to believe that, if there is still a cd(-rom) left in the drive, using the Eject button on my cd/dvd-rom drive really means I want it to show me how fast it can open and close the drive in succession. I’ve almost lost a cd like this, and have no clue where to look for info on why it behaves like this. It shouldn’t have any reason to keep the disk in there – it’s not writable, so there are no writes left so unmounting should be quick and painless (and even if it weren’t, it should keep the drive shut tight, instead of being all weird about it).
- [POSSIBLY FIXED] GRUB sucks, or Ubuntu’s use of it sucks. Whenever I update this machine, it adds two boot entries for the new kernel (one is ‘normal’, one is “Recovery Mode”). It doesn’t remove old entries. If I remove entries manually, they reappear the next time the kernel is updated. I have edited menu.lst to boot my windows install by default. Whenever these two entries get added, the default boot index is off-by-two, causing it to start memtest86 if I’m not at the machine to correct it. Why is it smart enough to remember the value I set it to, but not smart enough to update it when it changes the list?
- This machine is slightly over two years old. Ubuntu is still not able to shut it down correctly – I always have to press and hold the power button for five seconds after I hear the harddrive shut off (without Ubuntu telling me “you can now turn your machine off” – it seems to think this will happen automagically). Back when I just got this machine, I installed debian stable on it (I believe that was Sarge, back then, but I’m not sure). It never had a problem with this (nor does Windows). So clearly it’s not just that it’s not possible, but that Ubuntu somehow isn’t using the right version/type of acpi or whatever. This machine has an ASUS P5AD2-E motherboard, if that is any help.
All in all this means I really don’t want to use Ubuntu anymore, as it’s downright painful to get anything done (without access to my windows partitions, most of my documents, patches, photos and other personal things are out of reach, and with my computer busy with some invisible SomeThing, getting other work done becomes painfully slow, too). Solutions appreciated. 🙁