[Desktop-packages] [Bug 628105] Re: [Upstream] Text not black in LibreOffice
@Bejamin Drung: What about in Precise? Will there be any update soon? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/628105 Title: [Upstream] Text not black in LibreOffice Status in LibreOffice Productivity Suite: Fix Released Status in “libreoffice” package in Ubuntu: Confirmed Bug description: Binary package hint: light-themes When using Ambiance theme the body text in Ooo Writer is not black but gray. This is quite uncomfortable when writing and thus renders the theme in effect unusable. See attached png. [Impact] * Auto-colored text is illegible on dark background in LibreOffice. * Use "High Contrast" theme, unacceptable to customer. * User has to mnaually change the color from "automatic" to white. * This is affecting a flagship customer. [Test Case] * In Libreoffice Impress the text with the color "automatic" is hard to read if the background color is set to black (example file/screenshot attached). [Regression Potential] * This patch is a backport form upstream, and has been tested. I do not see any possible regression potential here. [Workaround] Go to Tools -> Options... -> LibreOffice -> Appearance -> Font Color and change the color from Automatic to Black. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/628105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes
I have a mobile broadband device here. I have also removed "modemmanager " but
the message still appears.
I'm thinking to open a new bug-report. Thanks.
--
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/963106
Title:
NetworkManager causes orphaned inodes
Status in “network-manager” package in Ubuntu:
Fix Released
Status in “network-manager” source package in Precise:
Fix Released
Bug description:
[Impact]
On shutdown, dhclient isn't getting reaped by NetworkManager, despite being
kept running through sendsigs so as not to disrupt remote filesystems (and
their unmounting at shutdown). dhclient may be keeping open files for its lease
files, which causes issues when unmounting /var/lib, which contains those lease
files.
[Development Fix]
Remove support for connection assumption, which is meant to bring
NetworkManager up to speed with connections that may have already be up during
a restart of the daemon. Since we don't actually restart the daemon
automatically (and instead suggest a restart of the system after upgrade) and
the advantage is minimal compared to the impact on users of this interacting
with the shutdown sequence, patch connection assumption out of the NM code and
just always take down dhclient when NM stops.
[Stable Fix]
See above "Development fix".
[Test Case]
1) Shut down coputer.
2) In the shutdown process, perhaps as a post-stop script in
/etc/init/network-manager, track down open files for the dhclient pid (which
should be available from /run/sendsigs.omit.d/network-manager.dhclient{6,}.pid)
[Regression Potential]
Minimal, only affects bringing NetworkManager up on a restart of the daemon
(sudo restart network-manager or /etc/init.d/network-manager restart), which
improves on the speed of this operation and avoid resetting the connection if
it's already up.
-
During system shutdown, NetworkManager neither kills dhclient nor does
it remove the dhclient pid file from the directory
/var/run/sendsigs.omit.d. As a result, dhclient continues to hold the
pid file open for write and when /etc/init.d/umountroot tries to
remount the root filesystem read-only, the remount fails. The
message:
mount: / is busy
is seen in the console, and the filesystem must be recovered at boot
time:
[8.946427] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.947057] EXT4-fs (sda1): write access will be enabled during recovery
[ 11.234075] EXT4-fs (sda1): recovery complete
If shared libraries used by dhclient are updated before the reboot,
orphaned inodes associated with the .so files are created. For
example, doing "sudo apt-get install --reinstall libc6" and then
rebooting leads to:
[8.356521] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.356521] EXT4-fs (sda1): write access will be enabled during recovery
[8.716544] EXT4-fs (sda1): orphan cleanup on readonly fs
[8.716544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313749
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313733
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313725
[8.724544] EXT4-fs (sda1): 3 orphan inodes deleted
[8.728544] EXT4-fs (sda1): recovery complete
This is network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
running under 12.04. I don't believe any actual data loss will occur
as a result of this bug, but it's likely to produce much user anxiety.
Also see Bug 952315, which misidentifies the cause of the problems as
upstart.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Fri Mar 23 07:42:20 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm
LANG=en_US.UTF-8
SHELL=/bin/bash
RfKill:
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-03-02 (20 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes
I could not open the file of /dev/null, where the output of 'ps p
$(pgrep modem-manager) 2>/dev/null' went, the error on gedit: "Could not
open the file /dev/null. /dev/null is not a regular file". But, when I
piped it to Desktop, like: "ps p $(pgrep modem-manager) 2>/root/Desktop"
, the output showed an error: "ERROR: List of process IDs must follow p.
* simple selection * * selection by list
* ... and.. so-on...".
The message "mount: / is busy" appears no matter my Huawei ec156 mobile
broadband is attached or not. Or, when wireless network is active or
not.
There is no error in /var/log/upstart/modemmanager.log, as you can see
in the atachment.
** Attachment added: "modemmanager.log"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+attachment/3195946/+files/modemmanager.log
--
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/963106
Title:
NetworkManager causes orphaned inodes
Status in “network-manager” package in Ubuntu:
Fix Released
Status in “network-manager” source package in Precise:
Fix Released
Bug description:
[Impact]
On shutdown, dhclient isn't getting reaped by NetworkManager, despite being
kept running through sendsigs so as not to disrupt remote filesystems (and
their unmounting at shutdown). dhclient may be keeping open files for its lease
files, which causes issues when unmounting /var/lib, which contains those lease
files.
[Development Fix]
Remove support for connection assumption, which is meant to bring
NetworkManager up to speed with connections that may have already be up during
a restart of the daemon. Since we don't actually restart the daemon
automatically (and instead suggest a restart of the system after upgrade) and
the advantage is minimal compared to the impact on users of this interacting
with the shutdown sequence, patch connection assumption out of the NM code and
just always take down dhclient when NM stops.
[Stable Fix]
See above "Development fix".
[Test Case]
1) Shut down coputer.
2) In the shutdown process, perhaps as a post-stop script in
/etc/init/network-manager, track down open files for the dhclient pid (which
should be available from /run/sendsigs.omit.d/network-manager.dhclient{6,}.pid)
[Regression Potential]
Minimal, only affects bringing NetworkManager up on a restart of the daemon
(sudo restart network-manager or /etc/init.d/network-manager restart), which
improves on the speed of this operation and avoid resetting the connection if
it's already up.
-
During system shutdown, NetworkManager neither kills dhclient nor does
it remove the dhclient pid file from the directory
/var/run/sendsigs.omit.d. As a result, dhclient continues to hold the
pid file open for write and when /etc/init.d/umountroot tries to
remount the root filesystem read-only, the remount fails. The
message:
mount: / is busy
is seen in the console, and the filesystem must be recovered at boot
time:
[8.946427] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.947057] EXT4-fs (sda1): write access will be enabled during recovery
[ 11.234075] EXT4-fs (sda1): recovery complete
If shared libraries used by dhclient are updated before the reboot,
orphaned inodes associated with the .so files are created. For
example, doing "sudo apt-get install --reinstall libc6" and then
rebooting leads to:
[8.356521] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.356521] EXT4-fs (sda1): write access will be enabled during recovery
[8.716544] EXT4-fs (sda1): orphan cleanup on readonly fs
[8.716544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313749
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313733
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313725
[8.724544] EXT4-fs (sda1): 3 orphan inodes deleted
[8.728544] EXT4-fs (sda1): recovery complete
This is network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
running under 12.04. I don't believe any actual data loss will occur
as a result of this bug, but it's likely to produce much user anxiety.
Also see Bug 952315, which misidentifies the cause of the problems as
upstart.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Fri Mar 23 07:42:20 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
IwConfig:
lono wireless extensions.
eth0 no wireless
[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes
I have put a sync command on the line 64 of /etc/init.d/sendsigs,
Steven. But, the message "mount: / is busy" still appears. Hope there
will be some suggestion from the others then. Thank you for your
suggestions so far.
--
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/963106
Title:
NetworkManager causes orphaned inodes
Status in “network-manager” package in Ubuntu:
Fix Released
Status in “network-manager” source package in Precise:
Fix Released
Bug description:
[Impact]
On shutdown, dhclient isn't getting reaped by NetworkManager, despite being
kept running through sendsigs so as not to disrupt remote filesystems (and
their unmounting at shutdown). dhclient may be keeping open files for its lease
files, which causes issues when unmounting /var/lib, which contains those lease
files.
[Development Fix]
Remove support for connection assumption, which is meant to bring
NetworkManager up to speed with connections that may have already be up during
a restart of the daemon. Since we don't actually restart the daemon
automatically (and instead suggest a restart of the system after upgrade) and
the advantage is minimal compared to the impact on users of this interacting
with the shutdown sequence, patch connection assumption out of the NM code and
just always take down dhclient when NM stops.
[Stable Fix]
See above "Development fix".
[Test Case]
1) Shut down coputer.
2) In the shutdown process, perhaps as a post-stop script in
/etc/init/network-manager, track down open files for the dhclient pid (which
should be available from /run/sendsigs.omit.d/network-manager.dhclient{6,}.pid)
[Regression Potential]
Minimal, only affects bringing NetworkManager up on a restart of the daemon
(sudo restart network-manager or /etc/init.d/network-manager restart), which
improves on the speed of this operation and avoid resetting the connection if
it's already up.
-
During system shutdown, NetworkManager neither kills dhclient nor does
it remove the dhclient pid file from the directory
/var/run/sendsigs.omit.d. As a result, dhclient continues to hold the
pid file open for write and when /etc/init.d/umountroot tries to
remount the root filesystem read-only, the remount fails. The
message:
mount: / is busy
is seen in the console, and the filesystem must be recovered at boot
time:
[8.946427] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.947057] EXT4-fs (sda1): write access will be enabled during recovery
[ 11.234075] EXT4-fs (sda1): recovery complete
If shared libraries used by dhclient are updated before the reboot,
orphaned inodes associated with the .so files are created. For
example, doing "sudo apt-get install --reinstall libc6" and then
rebooting leads to:
[8.356521] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.356521] EXT4-fs (sda1): write access will be enabled during recovery
[8.716544] EXT4-fs (sda1): orphan cleanup on readonly fs
[8.716544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313749
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313733
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313725
[8.724544] EXT4-fs (sda1): 3 orphan inodes deleted
[8.728544] EXT4-fs (sda1): recovery complete
This is network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
running under 12.04. I don't believe any actual data loss will occur
as a result of this bug, but it's likely to produce much user anxiety.
Also see Bug 952315, which misidentifies the cause of the problems as
upstart.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Fri Mar 23 07:42:20 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm
LANG=en_US.UTF-8
SHELL=/bin/bash
RfKill:
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-03-02 (20 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : http
[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes
And, here is something. The message "mount: / is busy" does not appear
each time I power off the system from tty1 while the lightdm is off.
--
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/963106
Title:
NetworkManager causes orphaned inodes
Status in “network-manager” package in Ubuntu:
Fix Released
Status in “network-manager” source package in Precise:
Fix Released
Bug description:
[Impact]
On shutdown, dhclient isn't getting reaped by NetworkManager, despite being
kept running through sendsigs so as not to disrupt remote filesystems (and
their unmounting at shutdown). dhclient may be keeping open files for its lease
files, which causes issues when unmounting /var/lib, which contains those lease
files.
[Development Fix]
Remove support for connection assumption, which is meant to bring
NetworkManager up to speed with connections that may have already be up during
a restart of the daemon. Since we don't actually restart the daemon
automatically (and instead suggest a restart of the system after upgrade) and
the advantage is minimal compared to the impact on users of this interacting
with the shutdown sequence, patch connection assumption out of the NM code and
just always take down dhclient when NM stops.
[Stable Fix]
See above "Development fix".
[Test Case]
1) Shut down coputer.
2) In the shutdown process, perhaps as a post-stop script in
/etc/init/network-manager, track down open files for the dhclient pid (which
should be available from /run/sendsigs.omit.d/network-manager.dhclient{6,}.pid)
[Regression Potential]
Minimal, only affects bringing NetworkManager up on a restart of the daemon
(sudo restart network-manager or /etc/init.d/network-manager restart), which
improves on the speed of this operation and avoid resetting the connection if
it's already up.
-
During system shutdown, NetworkManager neither kills dhclient nor does
it remove the dhclient pid file from the directory
/var/run/sendsigs.omit.d. As a result, dhclient continues to hold the
pid file open for write and when /etc/init.d/umountroot tries to
remount the root filesystem read-only, the remount fails. The
message:
mount: / is busy
is seen in the console, and the filesystem must be recovered at boot
time:
[8.946427] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.947057] EXT4-fs (sda1): write access will be enabled during recovery
[ 11.234075] EXT4-fs (sda1): recovery complete
If shared libraries used by dhclient are updated before the reboot,
orphaned inodes associated with the .so files are created. For
example, doing "sudo apt-get install --reinstall libc6" and then
rebooting leads to:
[8.356521] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.356521] EXT4-fs (sda1): write access will be enabled during recovery
[8.716544] EXT4-fs (sda1): orphan cleanup on readonly fs
[8.716544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313749
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313733
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313725
[8.724544] EXT4-fs (sda1): 3 orphan inodes deleted
[8.728544] EXT4-fs (sda1): recovery complete
This is network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
running under 12.04. I don't believe any actual data loss will occur
as a result of this bug, but it's likely to produce much user anxiety.
Also see Bug 952315, which misidentifies the cause of the problems as
upstart.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Fri Mar 23 07:42:20 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm
LANG=en_US.UTF-8
SHELL=/bin/bash
RfKill:
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-03-02 (20 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes
Here is the DEBUG file.
I have no VMware player installed on my system, the non-Ubuntu
applications that are installed in my system are Oracle Virtualbox,
remastersys, and nvidia proprietary driver. But, I remember, last time,
I installed a dialer and driver for Huawei ec156 USB modem (provided in
the modem). But, it was not work, the make process of the driver was
failed. Thus, I deleted the installed directory of the dialer manually.
** Attachment added: "DEBUG file"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+attachment/3188762/+files/DEBUG
--
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/963106
Title:
NetworkManager causes orphaned inodes
Status in “network-manager” package in Ubuntu:
Fix Released
Status in “network-manager” source package in Precise:
Fix Released
Bug description:
[Impact]
On shutdown, dhclient isn't getting reaped by NetworkManager, despite being
kept running through sendsigs so as not to disrupt remote filesystems (and
their unmounting at shutdown). dhclient may be keeping open files for its lease
files, which causes issues when unmounting /var/lib, which contains those lease
files.
[Development Fix]
Remove support for connection assumption, which is meant to bring
NetworkManager up to speed with connections that may have already be up during
a restart of the daemon. Since we don't actually restart the daemon
automatically (and instead suggest a restart of the system after upgrade) and
the advantage is minimal compared to the impact on users of this interacting
with the shutdown sequence, patch connection assumption out of the NM code and
just always take down dhclient when NM stops.
[Stable Fix]
See above "Development fix".
[Test Case]
1) Shut down coputer.
2) In the shutdown process, perhaps as a post-stop script in
/etc/init/network-manager, track down open files for the dhclient pid (which
should be available from /run/sendsigs.omit.d/network-manager.dhclient{6,}.pid)
[Regression Potential]
Minimal, only affects bringing NetworkManager up on a restart of the daemon
(sudo restart network-manager or /etc/init.d/network-manager restart), which
improves on the speed of this operation and avoid resetting the connection if
it's already up.
-
During system shutdown, NetworkManager neither kills dhclient nor does
it remove the dhclient pid file from the directory
/var/run/sendsigs.omit.d. As a result, dhclient continues to hold the
pid file open for write and when /etc/init.d/umountroot tries to
remount the root filesystem read-only, the remount fails. The
message:
mount: / is busy
is seen in the console, and the filesystem must be recovered at boot
time:
[8.946427] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.947057] EXT4-fs (sda1): write access will be enabled during recovery
[ 11.234075] EXT4-fs (sda1): recovery complete
If shared libraries used by dhclient are updated before the reboot,
orphaned inodes associated with the .so files are created. For
example, doing "sudo apt-get install --reinstall libc6" and then
rebooting leads to:
[8.356521] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.356521] EXT4-fs (sda1): write access will be enabled during recovery
[8.716544] EXT4-fs (sda1): orphan cleanup on readonly fs
[8.716544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313749
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313733
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313725
[8.724544] EXT4-fs (sda1): 3 orphan inodes deleted
[8.728544] EXT4-fs (sda1): recovery complete
This is network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
running under 12.04. I don't believe any actual data loss will occur
as a result of this bug, but it's likely to produce much user anxiety.
Also see Bug 952315, which misidentifies the cause of the problems as
upstart.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Fri Mar 23 07:42:20 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm
LANG=en_US.UTF-8
SHELL=/bin/bash
RfKill:
SourcePackage: network-manager
UpgradeStatus:
[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes
Thanks for the respond Steven,
Yes, I did execute it from a terminal in the desktop environment.
I have un-checked "Available to all users" for my active network
connection, but, the "mount: / is busy" message still appears. So, I
think my problem is not with the network manager.
So, as you suggested, I added:
/bin/ps > /DEBUG
/usr/bin/lsof >> /DEBUG
to /etc/init.d/umountroot before the 'mount -n -o remount,ro /' sequence. And
you can see the out put in the attachment. This time, I input the 'ps -ef and
losf -nP' command not from terminal but from tty1. Was that what you meant? Or
how is it to reproduce the output you meant?
** Attachment added: "umountroot, ps -ef, & lsof -nP output"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+attachment/3187427/+files/umountroot%2Cps%20-ef%2C%20%26%20lsof%20-nP%20output.txt
--
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/963106
Title:
NetworkManager causes orphaned inodes
Status in “network-manager” package in Ubuntu:
Fix Released
Status in “network-manager” source package in Precise:
Fix Released
Bug description:
[Impact]
On shutdown, dhclient isn't getting reaped by NetworkManager, despite being
kept running through sendsigs so as not to disrupt remote filesystems (and
their unmounting at shutdown). dhclient may be keeping open files for its lease
files, which causes issues when unmounting /var/lib, which contains those lease
files.
[Development Fix]
Remove support for connection assumption, which is meant to bring
NetworkManager up to speed with connections that may have already be up during
a restart of the daemon. Since we don't actually restart the daemon
automatically (and instead suggest a restart of the system after upgrade) and
the advantage is minimal compared to the impact on users of this interacting
with the shutdown sequence, patch connection assumption out of the NM code and
just always take down dhclient when NM stops.
[Stable Fix]
See above "Development fix".
[Test Case]
1) Shut down coputer.
2) In the shutdown process, perhaps as a post-stop script in
/etc/init/network-manager, track down open files for the dhclient pid (which
should be available from /run/sendsigs.omit.d/network-manager.dhclient{6,}.pid)
[Regression Potential]
Minimal, only affects bringing NetworkManager up on a restart of the daemon
(sudo restart network-manager or /etc/init.d/network-manager restart), which
improves on the speed of this operation and avoid resetting the connection if
it's already up.
-
During system shutdown, NetworkManager neither kills dhclient nor does
it remove the dhclient pid file from the directory
/var/run/sendsigs.omit.d. As a result, dhclient continues to hold the
pid file open for write and when /etc/init.d/umountroot tries to
remount the root filesystem read-only, the remount fails. The
message:
mount: / is busy
is seen in the console, and the filesystem must be recovered at boot
time:
[8.946427] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.947057] EXT4-fs (sda1): write access will be enabled during recovery
[ 11.234075] EXT4-fs (sda1): recovery complete
If shared libraries used by dhclient are updated before the reboot,
orphaned inodes associated with the .so files are created. For
example, doing "sudo apt-get install --reinstall libc6" and then
rebooting leads to:
[8.356521] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.356521] EXT4-fs (sda1): write access will be enabled during recovery
[8.716544] EXT4-fs (sda1): orphan cleanup on readonly fs
[8.716544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313749
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313733
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313725
[8.724544] EXT4-fs (sda1): 3 orphan inodes deleted
[8.728544] EXT4-fs (sda1): recovery complete
This is network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
running under 12.04. I don't believe any actual data loss will occur
as a result of this bug, but it's likely to produce much user anxiety.
Also see Bug 952315, which misidentifies the cause of the problems as
upstart.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Fri Mar 23 07:42:20 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
IwConfig:
lono wireless extensions.
eth0
