Robert: Re the rmmod/modprobe fandango I'm doing: I've done a bunch of testing (my next post will detail it), but I'm pretty sure what's going on with rmmod/modprobe is simply a kernel regression---if pcspkr is loaded too early, it doesn't work correctly. So if it's blacklisted, and then loaded by hand by the user once everything is up, that's equivalent to un-blacklisting it, waiting until the system is up, and then doing rmmod/modprobe on it. You didn't see that with the LiveCD because you couldn't un-blacklist it since you're booting off read-only media that specifies the blacklisting. (I don't know how early it can be safely enabled; that'll be some other testing, but that's pretty clearly a kernel regression in my eyes and otherwise unrelated to the rest of the bugs we're tracking down.) This also means that, until the kernel bug is fixed, the easiest thing for people to do is just leave it blacklisted and then put something in rc.local (or equivalent) that modprobes it; that's probably late enough, but I'll find out for sure at some point.
Lots of detailed testing on all the other bugs & aspects of this report in my next post, once I finish editing it. -- System beep broken in Karmic despite heroic efforts to fix it https://bugs.launchpad.net/bugs/486154 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
