** Changed in: linux (Ubuntu)
Status: Invalid => Incomplete
** Changed in: upstart
Status: Invalid => Confirmed
** Changed in: upstart (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: upstart
Status: Confirmed => Invalid
** Changed in: upstart (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is
Looks like bug #1169614 was finally fixed.
But there's one more bug which cause same problem: bug #1307008
--
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/1073433
Title:
Ext4
** Changed in: network-manager (Ubuntu)
Status: Triaged = Fix Released
--
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/1073433
Title:
Ext4 corruption associated with
** Tags added: trusty
--
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/1073433
Title:
Ext4 corruption associated with shutdown of Ubuntu 12.10
Status in Upstart:
Confirmed
14.04 — it's still a problem (dhclient issue).
--
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/1073433
Title:
Ext4 corruption associated with shutdown of Ubuntu 12.10
Status
Lennert of systemd refers to this bug on google+. He outlines a fix for
the simple case:
https://plus.google.com/115547683951727699051/posts/LjkLwkeDiLc
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
This does seem to be getting kind of embarassing. With modern journalled
filesystems on relatively straightforward hardware configs an unclean
shutdown shouldn't be the end of the world (after all, power failures
can happen), but it's not nice either.
Unfortunately we also seem to have a hell of
Steve Dodd:
Last time I did, my own problems were caused by dhclient and ureadahead..
It is not an ureadahead issue, it is an extra fork in upstart to launch
shell for ureadahead if more than one partition mounted.
--
You received this bug notification because you are a member of Desktop
On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote:
Lennert of systemd refers to this bug on google+. He outlines a fix for
the simple case:
The fix he outlines is not for this bug. It's not for a bug we have in
upstart in Ubuntu at all; we already reliably ensure telinit u on upgrade of
Excerpts from Steve Langasek's message of 2014-01-22 16:51:06 UTC:
On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote:
Lennert of systemd refers to this bug on google+. He outlines a fix for
the simple case:
The fix he outlines is not for this bug. It's not for a bug we have in
On Wed, Jan 22, 2014 at 05:11:03PM -, Clint Byrum wrote:
The other one is the one that would sweep up the mess we occasionally
see when something misbehaves.
I'd like to see Ubuntu's shutdown do more to protect against that
failure mode.
I would, too, but I don't agree that the method he
On 01/22/2014 05:51 PM, Steve Langasek wrote:
On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote:
Lennert of systemd refers to this bug on google+. He outlines a fix for
the simple case:
The fix he outlines is not for this bug. It's not for a bug we have in
upstart in Ubuntu at all; we
On Wed, Jan 22, 2014 at 04:13:19PM -, Max wrote:
Steve Dodd:
Last time I did, my own problems were caused by dhclient and ureadahead..
It is not an ureadahead issue, it is an extra fork in upstart to launch
shell for ureadahead if more than one partition mounted.
Yes, I know - I was
In my case it's a dhclient process that likely respawns and prevents
remount to read-only of root fs, due to a lease file opened for writing
under /var/lib/NetworkManager/.. Result is unclean shutdown and recovery
of dirty root file system on next boot.
Attaching lsof output obtained just before
I'd guess patch in bug 1169614 would help in my case (dhclient process).
Any progress on evaluating and possibly including the patch provided in
that bug ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
You are definivly right in that case
a bug is allready opened(Bug #1073433 ) as i writing a comment to it
The normal user wants a clean shutdown or reboot and as I wrote its a dirty
hack until this problem is resolved by the maintainers
we know the schutdown process isn't working correctly as
due the respawn of some processes i think they are (re)started again even on
shutdown
so they are running if the / is remounted readonly
and that is why it fails
i think upstart should insure that all processes are killed (also the
respawning) at the moment we mount / readonly on halt or
Excerpts from Bernd's message of 2014-01-05 21:37:21 UTC:
due the respawn of some processes i think they are (re)started again even on
shutdown
so they are running if the / is remounted readonly
and that is why it fails
i think upstart should insure that all processes are killed (also
I have tried some workarounds from the comments and nothing seems to
work. Fsck still runs at every boot. Bootchart included.
** Attachment added: Bootchart image
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3929572/+files/andrej-namizni-saucy-20131215-1.png
--
Regardless of that one comment above. But it is really frustrating if
now the user's of ubuntu get blamed for not filing the correct bug. Dear
folks at Canonical, you have so much information in this one thread,
about how to reproduce this error. I'm not that experienced. So please,
could someone
So when I wrote 6 months ago that:
If you can reproduce this issue, please file a new bug report against
the sysvinit-utils package with details. It is certainly unrelated to the
common issue being described here.
Rather than doing this to help yourself, you switch distros, decide that
Excerpts from Alexander's message of 2013-10-25 05:39:16 UTC:
Guys, come on!
What the heck network-manager and network connections are you talking about?!
This really pissed me off already!
As I've said earlier, the problem is NOT in network-manager!
Excerpts from Steve Dodd's message of 2013-10-21 16:16:29 UTC:
That sounds plausible - I would guess wireless connections are usually torn
down at the end of the user session (i.e. logout) whereas I assume wired
connections persist right to system shutdown??
In theory they're brought down when
Guys, come on!
What the heck network-manager and network connections are you talking about?!
This really pissed me off already!
As I've said earlier, the problem is NOT in network-manager!
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/comments/105
because it appears even when
I did a bit of hacking on init.d/umountroot, adding lsof and ps -ef after the
remount fails.
I could see that dhclient was still running, so I added before the remount:
pkill -9 dhclient
After this change, dhclient was gone, but the remount still failed. In
lsof output I can see:
init
Sorry, forgot to added version info to #146
Ubuntu Saucy 32-bit, package version: upstart 1.10-0ubuntu7 i386
--
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/1073433
Title:
On Wed, Oct 23, 2013 at 10:15:46PM -, Gregor Larson wrote:
init 1 root 15w REG 8,24 1134 438383
/var/log/upstart/mountall.log
mountall is a service that's supposed to run once at boot and then exit. If
mountall is still running when you shut the system down, then
It occurs that the problem did *not* exist after a recent clean install
of 13.10 (64bit Desktop CD) on a friend's notebook. While it still
happens on my desktop PC.
Differences:
On the notebook we used wireless (b43 out of the box) internet during
installation. Reboot into new system, login,
That sounds plausible - I would guess wireless connections are usually torn
down at the end of the user session (i.e. logout) whereas I assume wired
connections persist right to system shutdown??
On Oct 21, 2013 3:01 PM, Christian Niemeyer chr.nieme...@gmail.com
wrote:
It occurs that the problem
I'm seeing this in 13.10 as well.
--
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/1073433
Title:
Ext4 corruption associated with shutdown of Ubuntu 12.10
Status in Upstart:
Yeah, still exists in 13.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/1073433
Title:
Ext4 corruption associated with shutdown of Ubuntu 12.10
Status in Upstart:
This still happens in 13.10 (saucy). This time I installed the Beta-2 of
Lubuntu (thus using an lxsession). Reboot or shutdown fails everytime.
It hangs for around ten seconds, then it reboots and fsck shows deleted
orphaned inode.
Only helps to uninstall network-manager-*, nm-*, modemmanager,
I have the same problem on 13.04, which is solved by 2 steps (as mentioned
above):
1) uninstalling ureadahead or adding console none to
/etc/init/ureadahead-other.conf
2) killing dhclient in umountfs.
Indeed, why it has not been fixed for years
--
You received this bug notification
Dmitry, I confirm your solution. I already uninstalled ureadahead (no
need for it with a SSD).
I added killall dhclient to my /etc/init.d/umountfs (at the beginning of
the do_stop function).
This problem happens for me only when I use the regular wired ethernet
on my ThinkPad X230 (not just when
I've tried patches in mentioned in comment #137, but they didn't help.
--
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/1073433
Title:
Ext4 corruption associated with shutdown
My problems (on current saucy) were caused by bugs in upstart (affecting
ureadahead) and network-manager. The patches in bug #1181789 and bug
#1169614 give me a clean unmount and shutdown.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
In my case the bug with unclean shutdown happens only when my machine
(Thinkpad X230) is docked to the Thinkpad ultrabase when shutting it
down.
When I shutdown outside of a dock, everything is fine. I don't use
ureadahead (have SSD), doesn't matter if there are mounted network
filesystems or
Finally did a workaround of this bug with:
1) killing dhclient on umountfs step
2) /etc/init/ureadahead-other.override with manual start
AFAIK this bug exists since 12.10 and I have no idea why it still
doesn't fixed.
--
You received this bug notification because you are a member of Desktop
This does seem like a bug in upstart. It seems to me that there needs to
be a command to say upstart, close all of your log files and do not
reopen them so that one can remount / readonly. Systems may have things
that want to keep running right up until poweroff/reboot, but that make
use of
I added the following line to /etc/init/ureadahead-other.conf to disable
logging for this particular Upstart job:
console none
This prevents the log file from keeping the file system busy. The only
downside is that anything logged by ureadahead-other goes to /dev/null
instead.
--
You received
P.S. You will have to reboot 2 times after adding console none for it
to work.
--
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/1073433
Title:
Ext4 corruption associated with
The cause of ureadahead issue is upstart. The pure case
unrelated to ureadahead is Bug lp: #1181789.
In some cases upstart might hold log files
opened for writing for other daemons.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Bug #1181528 for ureadahead/upstart issue.
Unfortunately the conditions to reproduce are not clear.
--
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/1073433
Title:
Ext4
On Thu, May 16, 2013 at 04:21:12PM -, Max wrote:
'ps uw' only shows processes belonging to the current user.
Unless PID is specified
Oops, true. So the process is definitely not running.
Also, please file a bug report against the ureadahead package
for this package, and post the
'ps uw' only shows processes belonging to the current user.
Unless PID is specified
Also, please file a bug report against the ureadahead package
for this package, and post the number of the new bug here.
I would rather file a bug against upstart.
Ureadahead does his job and exits with
There is at least one more cause of busy / besides network-manager
in Raring 13.10.
I have noticed file /var/log/upstart/ureadahead-other.log opened
for writing by init when /etc/init.d/umountroot was running.
It seems that the problem was caused by absent pack file
in /var/lib/ureadahead/ for a
Hi Max,
On Tue, May 14, 2013 at 04:17:18PM -, Max wrote:
There is at least one more cause of busy / besides network-manager
in Raring 13.10.
I have noticed file /var/log/upstart/ureadahead-other.log opened
for writing by init when /etc/init.d/umountroot was running.
It seems that the
** Tags removed: kernel-da-key
--
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/1073433
Title:
Ext4 corruption associated with shutdown of Ubuntu 12.10
Status in Upstart:
Except for dependency upon Nvidia drivers, I would be quite satisfied with
12,04.
I really would like to put Nvidia drivers in the trash where they belong.
The list of 13.xx BUGs preventing the switch from 12.04 is getting shorter.
Please shorten the list by fixing this BUG promptly. Thanks.
See also LP: #869635.
--
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/1073433
Title:
Ext4 corruption associated with shutdown of Ubuntu 12.10
Status in Upstart:
Confirmed
Paul, In Quantal 12.10 it is the bug lp: #1124803
NetworkManager doesn't respond to SIGTERM in daemon mode.
And that patch fixes the issue for network-manager 0.9.6
(however there are no .deb packages).
In 13.04 Raring, network-manager maintainers in Ubuntu missed
that upstream dropped
I'm experiencing similar issues on an EXT-3 filesystem. There are no
inode/block errors reported by fsck but the root filesystem (/ is
mounted on /dev/sda2 in my case) fails the fsck check at boot.
% dmesg | grep sda2
EXT3-fs (sda2): recovery required on readonly filesystem
EXT3-fs (sda2): write
Max,
I did a quick search for the NetworkManger source code. Many variations
and levels of development exist.
Since I have no experience as a developer or QA type in the Ubuntu arena
and have repeatedly submitted DETAILED steps for this 100% reproducible
problem, I will pass on trying to fix it
1. Will I have to download and install a compiler and a linker?
Sure:
sudo apt-get install build-essential
2. Will I have to recompile the kernel to use the updated
NetworkManager?
No, just network-manager:
sudo apt-get build-dep network-manager
apt-get source network-manager
cd
Is this bug still present in the released 13.04 version?
--
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/1073433
Title:
Ext4 corruption associated with shutdown of Ubuntu
ABSOLUTELY!
64-bit Desktop 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC
2013
IF
Internet connection to the modem exists and
Ethernet connection from my desktop to the modem and
Enable Networking checked and
Shutdown or Restart or Reboot
THEN
Bad shutdown
fsck from another copy of
Ernie, have you tried the suggestion from the comment #114?
(Bug lp: #1169614)
--
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/1073433
Title:
Ext4 corruption associated with
Hi Max,
The last time I touched a compiler was in the windoze world about ten
years ago.
1. Will I have to download and install a compiler and a linker?
2. Will I have to recompile the kernel to use the updated NetworkManager?
Advise please. Thanks.
--
You received this bug notification
Morning, 'halt'... and / is busy again.
VERBOSE=yes
in /etc/default/rcS didn't help either.
Just a few messages are added:
* Will now unmount temporary filesystems
tmpfs has been unmounted
* Will now deactivate swap
swapoff on /dev/sdb1
* Mounting root filesystem read-only...
umount:
Russel, please read my comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/comments/105
carefully.
I repeat: I have neither plymouth nor network-manager nor modemmanager nor wicd
installed. Just plain /etc/network/interfaces. +guessnet.
/etc/network/interfaces is the native way
Steve, thanks for the info.
As I've mentioned earlier, I'm using autofs. I think that such names like
'tmp/autoX' are autofs temporary mount points. Also I have /tmp mounted as
tmpfs.
So my guess is that tmpfs is getting unmounted BEFORE autofs daemon have been
terminated (unmounted it's
Ernie, please, try to rebuild network-manager
with
#define TARGET_DEBIAN
added to src/dns-manager/nm-dns-dnsmasq.c
src/nm-device.c src/nm-manager.c
in the very beginning of that files.
Perhaps you might need to change the line 45
of debian/rules from
--with-tests
to
--enable-tests=no
--
You
Something really going wrong here.
Today's morning I've found reaaally something new! I'm seeing this for the
first time ever. I've tried to halt the system (not poweroff as usually):
* Unmounting temporary filesystems...
umount: /tmp/auto6FJPRq (deleted): not found
umount: /tmp: device busy.
Alexander, get rid of NM and install wicd to learn if the problem(s)
still persist.
Using wicd, I get clean and fast shutdown in 5 seconds, with no fsck
checks on reboot. Worth a try!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
On Tue, Apr 16, 2013 at 08:38:29PM -, Alexander wrote:
Something really going wrong here.
Today's morning I've found reaaally something new! I'm seeing this for the
first time ever. I've tried to halt the system (not poweroff as usually):
* Unmounting temporary filesystems...
umount:
Russel,
When using the CLI, I got an error and could not install wicd on 13.04
However, I was able to install it via the software center.
Each time that I attempted to use it, a connection failure message
occurred immediately after the requested password was entered. Are you
able to
Another data set:
1. ATT is my ISP. My Desktop connects to a DSL modem via Ethernet.
2. There seems to be some keepalive traffic. A packet of 64 or 121 bytes gets
sent or received about every 10 seconds. This activity appears to happen in
12.04 which functions correctly and in 13.04 which
Ernie, I'm still on 12.10 (I'm waiting for RC before upgrading) and
using wicd with a wireless connection, so I'm not sure why you are
getting an error with your ethernet connection. You have probably
explored all the options...
In the next couple of days I'll upgrade one computer to 13.04RC and
1) Problem appears on different hardware. I mean totally different (except for
my usb hdd, from which the system boots).
2) I run memtest about a year ago... But I don't see any oops-es, hangs or
kernel panics. So the problem is not related with (broken) hardware.
3) How I've removed plymouth? I
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
I just want to say about my expirience here. Maybe it adds some useful details
to understanding what's going on.
Ubuntu = 12.04 amd64
kernel = 3.5.0-22-generic.
rootfs = btrfs
Sometimes I was able to see
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
Forget to say.
I have plymouth installed, but just removed of quiet and splash from
GRUB_CMDLINE_LINUX_DEFAULT.
--
You received this bug notification because you are a member of Desktop
Packages, which
** This bug is no longer a duplicate of bug 1124803
NetworkManager doesn't respond to SIGTERM in daemon mode
--
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/1073433
Title:
I have broken the link to duplication of bug #1124803
NetworkManager doesn't respond to SIGTERM in daemon mode.
This bug have been reported by Ernie and in the discussion
of bug #1124803 he insists that his bug has not fixed.
Network manager 0.9.6.0 in 12.10 quantal is really affected
by that
I have Network manager installed in Ubuntu 12.04, but I have / busy only with
generic kernel.
With pf-kernel I have clear shutdown.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
In another perhaps related bug 1124803, it was suggested to try wicd.
Unfortunately wicd would not install on 13.04 amd64.deb for me. Failure
indicated partway through the installation.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
Alexander, by the way, how have you managed to remove plymouth?
mountall depends on plymouth, initscripts depends on plymouth.
--
You received this bug notification because you are a member of Desktop
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
It turned out to a kind of mystery. No files are left open for writing
but device is busy and can not be cleanly remounted readonly.
Moreover it is not clear how to reproduce the issue.
Concerning the
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
The original description does not mention removing of network-manager
and other packages.
The phrase concerning redundant open files in unclear for me.
Is there any files open for writing? I wonder if the
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
Max, as I've understood, no splash doesn't disable plymouth. Some people
suppose that the freezed plymouth is the cause:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1019347
I've decided to find
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
** Attachment added: S59-2013-04-11.log.old
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3640750/+files/S59-2013-04-11.log.old
--
You received this bug notification
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
** Attachment added: S75-2013-04-11.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3640751/+files/S75-2013-04-11.log
** Attachment removed: S59-2013-04-11.log.old
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
** Attachment added: S59-2013-04-11.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3640770/+files/S59-2013-04-11.log
--
You received this bug notification because you
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
I have exactly the same problem.
Everything stopped, dhclient, network manager and plymouthd as well, no
redundant open files, everything what should be umounted is umounted.
But every reboot I still see
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
As I've understood, unmount of tmpfs filesystems is called from
/etc/rc{0,6}.d/S40umountfs right?
My /etc/rc{0,6}.d/S59 script calls 'cat /proc/mounts S59.log'
Then, why do I see tmpfs in log?
$ grep
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
Forgot to mention that the lsof launched from S59 didn't show any files
opened for writing too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
Steve Langasek, maybe it's a race condition. When init scripts trying to
unmount root, they fail because of opened files. But, when I check for opened
files in S75 script those processes had been
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
Marius B. Kotsbak, no, currently, I can't, sorry. (lack of time)
Upd: I also have
tmpfs /tmptmpfs defaults
string in /etc/fstab. Maybe this is the case...
I'll check this too.
--
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
I think, the problem is somewhere deeper... In upstart/init.
I've purged network-manager, modem-manager and even plymouth! And added S75
script in
/etc/rc0.d:
cat /proc/mounts
/usr/bin/lsof
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
Alexander, could you test it using a Raring daily image?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
Alexander, your lsof output doesn't show any files open for writing on
the root filesystem except for the S75 script's own log. If you're
getting ext4 corruption on shutdown, that seems to be unrelated to
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
Using 64-bit 3.8.0-16-generic #26-Ubuntu SMP Mon Apr 1 19:52:57 UTC 2013
from the 2013-04_02 daily build:
1. NetworkManager stopped correctly (immediately) via sudo stop network-manager.
2. A reboot to an
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
From the upstream report [1], the fix is for Ubuntu to carry the patch
against NetworkManager [2].
Since this is correctly understood and addressed in bug 1124803 as Max
points out, this is a duplicate bug
It seems that the issue may be connected with bug 1124803
NetworkManager doesn't respond to SIGTERM in daemon mode
That patch helped me on 12.10. But I am puzzled by the reports
that this bug has not fixed in Raring.
--
You received this bug notification because you are a member of Desktop
Does anybody know if the workarounds posted here remain effective after
a kernel upgrade to 3.5.0-26?
--
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/1073433
Title:
Ext4
Franciso, I am using 3.5.0-26, and the my comment at #75 holds true.
--
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/1073433
Title:
Ext4 corruption associated with shutdown of
Do not be deceived. This is a 1210 and 13.04 problem.
64-bit 1204 3.2.0-39-generic #62-Ubuntu SMP Thu Feb 28 00:28:53 UTC 2013
and prior 12.04 64-bit versions work just fine!
It would be quite delightful if someone would correct this problem of
failing to shutdown properly.
--
You received
I repeat. This is a 12.10 and 13.04 problem.
64-bit 1204 3.5.0-26-generic #42~precise1-Ubuntu SMP Mon Mar 11 22:17:58 UTC
2013 and prior 12.04
64-bit versions work just fine!
A fix for this problem of failing to shutdown properly would be much
appreciated.
--
You received this bug
Thanks again Russell. I'm upgrading to 3.5.0-26. It's good to know that
the upgrade won't break the workarounds.
And of course I agree with Ernest that a proper fix for this bug would
be very much appreciated.
--
You received this bug notification because you are a member of Desktop
Packages,
Not directly, but I would assume so, as unchecking 'Available to all
users' still works with 3.5.0-25.
I have also tried your suggestion at #60, thanks. It works for me -- but
I have reverted to the simple 'uncheck' as there seems no downside in my
installations and any future fix should be with
1 - 100 of 157 matches
Mail list logo
