@ Nicolas: yes, yes, you are definately right. there seems to be some kind of vacation taking since the release. ive seen more regressions on this release than any other. nothing mayor. but the ammount of technicalites have long past their bearable threshold.
i was too considering another distribution, once my exams are over and i can afford to have a semi working laptop for a while. i think all of these bugs related to alsa, networks, and whatnot to be related to upstart. i dont know what the change was since hardy. but i think the push to start migrating to upstart must have triggered all sort of conflicts (things shutting down in an unexpected order, for example). i think this to be the case, because my personal experence is that some bugs are quite random...sometimes when i boot, i will get no thermal sensors, and fan would run non stop, some times, everything is ok. some times i get stuck at ALSA shutting down, sometimes i dont, having wlan0 on auto (/etc/network/interfaces) with my home wireless network configured. will ONLY work when the network is available, if its not, bringing network interfaces up during boot will timeout after 5 minutes aprox. another issue is concerning backlight, and screen control. its laggy at best. my fn-F3 power-off display doesnt work anymore. i could go on ranting,.. but i dont think thats the point of this bug report. good luck -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up 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
