Needs looking at nm-dns-dnsmasq.c to make sure the daemon is properly
shut down when NM stops, which might have been broken by the dbus patch.
** Changed in: dnsmasq (Ubuntu)
Status: New => In Progress
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided => High
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Package changed: dnsmasq (Ubuntu) => network-manager (Ubuntu)
** Changed in: network-manager (Ubuntu)
Milestone: None => ubuntu-12.10
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1058987
Title:
In Quantal, the root filesystem is not cleanly unmounted at shutdown
or reboot
Status in “network-manager” package in Ubuntu:
In Progress
Bug description:
Ever since some update in the Quantal pre-releases, having dnsmasq-
base installed will cause the root filesystem to not be properly
unmounted on shutdown and reboot. In case the Plymouth splash screen
is disabled, the message 'mount: / is busy' will be shown, but
otherwise the user will not even be aware of this problem.
After rebooting, the root filesystem needs recovery, as shown in
dmesg:
kevin@vbox-xubuntu-quantal:~$ dmesg | grep EXT4
[ 1.022746] EXT4-fs (sda2): INFO: recovery required on readonly filesystem
[ 1.022750] EXT4-fs (sda2): write access will be enabled during recovery
[ 1.248294] EXT4-fs (sda2): recovery complete
[ 1.248661] EXT4-fs (sda2): mounted filesystem with ordered data mode.
Opts: (null)
[ 1.456315] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
Yet again, the user will not be aware of this until it is too late.
The only way to avoid this from happening (or at least what I've
found) is running 'sudo apt-get purge dnsmasq-base'. Sadly, this also
removes network-manager and network-manager-gnome, so it isn't really
a viable solution.
Another problem that might be related is that having an active
connection with the Network Manager prior to shutting down or
rebooting, will cause the process to hang for a few seconds, after
which the message about / being busy is shown. Stopping the network
service (sudo service networking stop) will solve the hanging, but not
the unclean unmount. So far, only purging dnsmasq-base seems to do
that, which obviously also solves the other problem, as Network
Manager will then also be removed.
Although I haven't experienced it yet, this could cause potential data
loss; especially for users without a seperate /home partition.
ProblemType: Bug
ApportVersion: 2.5.3-0ubuntu1
Architecture: amd64
Date: Sun Sep 30 12:49:24 2012
DistroRelease: Ubuntu 12.10
Package: dnsmasq-base 2.63-1ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
SourcePackage: dnsmasq
Tags: quantal
Uname: Linux 3.5.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
