Comment 8 for bug 1058987
Revision history for this message
| the-unconventional (the-unconventional-deactivatedaccount-deactivatedaccount) wrote | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Tested this in VirtualBox:
Custom Xubuntu 12.10 installation (netinst with Xfce packages) - fully updated: not fixed
Stock Ubuntu 12.10 installation (installed with ubiquity, unmodified) - fully updated: not fixed
Stock Xubuntu 12.10 installation (installed with ubiquity, unmodified) - fully updated: not fixed
Fresh custom Xubuntu 12.10 installation (latest netinst with Xfce packages) - fully updated (while installing): not fixed
Tested this on my testing machine:
Custom Xubuntu 12.10 installation (netinst with Xfce packages) - fully updated: not fixed
Stock Xubuntu 12.10 installation (installed with ubiquity, unmodified) - fully updated: not fixed
Fresh custom Xubuntu 12.10 installation (latest netinst with Xfce packages) - fully updated (while installing): not fixed
In each and every case, purging dnsmasq-base solves all issues. Purging only network-manager only solves the long shutdown time, but not the unmounting issue.
Am I really the only one noticing the huge increase in shutdown time compared to 12.04, and hasn't anyone else seen fsck show up in every dmesg log?