Perhaps it's a small percentage but it's a small percentage that are doing an effort to test Intrepid and the fact that the shutdown will be badly done are increasing the risk for the file system and by consequence for the data of the user. Don't think that anyone will wait 10 or 15 minutes (at least for me it's the time I wait for nothing) to have a system cleanly stop. The magic sysreq keys don't work on my laptop (an ibm one), never did, so it's not a solution and I don't think that a lambda user will now how to use them (a new linux user for example) and that he will appreciate this kind of behaviour but perhaps I'm doing a mistake... I don't think so.
I'm sorry to insist but the quality, one week before the launch, of intrepid is not good. I'm using linux since 96 and ubuntu since the first version. I pass all my lab on it but honestly I cannot vouch for this version and the fact that the priority of a bug like this is just decided because of the small percentage of people affected is a little bit strange. There are a big risk to mess up the filesystem (hard shutdown has never been good for it!) but it's seems that it's not important now... -- shutdown freeze on alsa shutdown https://bugs.launchpad.net/bugs/274995 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
