** Changed in: libnih (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: libnih (Ubuntu Natty)
Status: New = Won't Fix
** Changed in: libnih (Ubuntu Oneiric)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I verified this following James' and Marc's instructions in bug 1062202.
** Tags removed: removal-candidate verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package libnih - 1.0.3-4ubuntu9.1
---
libnih (1.0.3-4ubuntu9.1) precise-proposed; urgency=low
* Addition of debian/libnih-dbus1.postinst and
debian/libnih1.postinst to force Upstart re-exec on shutdown
to avoid unmounting disks uncleanly (LP:
** Branch linked: lp:~ubuntu-branches/ubuntu/precise/libnih/precise-
proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740390
Title:
libdbus-1-3 upgrade does not respawn init, resulting in
Hello Alan, or anyone else affected,
Accepted libnih into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/libnih/1.0.3-4ubuntu9.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Still get uncleaned shutdown process:
with the last shutdown, i've seen:
- modemmanager reloading its dozen drivers
- mount / is busy
- and last with a [drm] nouveau complaint, switching to fbcon (or so)
with the next reboot:
oem@dub:~$ dmesg | grep orphan
[8.812542] EXT4-fs (sdb5): orphan
I've created bug 1062202 to handle the lbnih SRU for precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740390
Title:
libdbus-1-3 upgrade does not respawn init, resulting in unclean
shutdown
** Changed in: libnih (Ubuntu Quantal)
Assignee: (unassigned) = James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740390
Title:
libdbus-1-3 upgrade does not respawn init,
** Branch linked: lp:~jamesodhunt/ubuntu/quantal/libnih/bug-740390
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740390
Title:
libdbus-1-3 upgrade does not respawn init, resulting in unclean
This bug was fixed in the package dbus - 1.4.18-1ubuntu1.3
---
dbus (1.4.18-1ubuntu1.3) precise-security; urgency=low
* REGRESSION FIX: some applications launched with the activation helper
may need DBUS_STARTER_ADDRESS. (LP: #1058343)
-
This bug was fixed in the package dbus - 1.2.16-2ubuntu4.7
---
dbus (1.2.16-2ubuntu4.7) lucid-security; urgency=low
* REGRESSION FIX: some applications launched with the activation helper
may need DBUS_STARTER_ADDRESS. (LP: #1058343)
-
This bug was fixed in the package dbus - 1.4.6-1ubuntu6.4
---
dbus (1.4.6-1ubuntu6.4) natty-security; urgency=low
* REGRESSION FIX: some applications launched with the activation helper
may need DBUS_STARTER_ADDRESS. (LP: #1058343)
-
This bug was fixed in the package dbus - 1.4.14-1ubuntu1.3
---
dbus (1.4.14-1ubuntu1.3) oneiric-security; urgency=low
* REGRESSION FIX: some applications launched with the activation helper
may need DBUS_STARTER_ADDRESS. (LP: #1058343)
-
The dbus upgrade has been applied, and this basic unique desktop still
show on shutdown: mount: / is busy (each time it is shutdown). This is
on QQ i386 with pata/sata hdds and bios.
** Tags added: i386 quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug was fixed in the package libnih - 1.0.3-4ubuntu11
---
libnih (1.0.3-4ubuntu11) quantal; urgency=low
* Addition of debian/libnih-dbus1.postinst and
debian/libnih1.postinst to force Upstart re-exec on shutdown
to avoid unmounting disks uncleanly (LP: #740390).
--
** Branch linked: lp:ubuntu/lucid-security/dbus
** Branch linked: lp:ubuntu/natty-security/dbus
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740390
Title:
libdbus-1-3 upgrade does not respawn
** Branch linked: lp:ubuntu/precise-updates/dbus
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740390
Title:
libdbus-1-3 upgrade does not respawn init, resulting in unclean
shutdown
To manage
@dino99: Thanks for spotting this - I too saw this in testing. I've
isolated the problem - see bug 1061639.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740390
Title:
libdbus-1-3 upgrade does not
Thanks James, confirmation done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740390
Title:
libdbus-1-3 upgrade does not respawn init, resulting in unclean
shutdown
To manage notifications
Clint: I don't think there's any point in doing a complex trigger
arrangement when (a) only a tiny number of libraries are involved, and
(b) stateful-reexec will solve this anyway.
FWIW, libnih1/libnih-dbus1 have this problem too.
--
You received this bug notification because you are a member
Added tasks for libnih.
** Also affects: libnih (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740390
Title:
libdbus-1-3 upgrade does not
This bug was fixed in the package dbus - 1.6.4-1ubuntu3
---
dbus (1.6.4-1ubuntu3) quantal-proposed; urgency=low
* REGRESSION FIX: some applications launched with the activation helper
may need DBUS_STARTER_ADDRESS. (LP: #1058343)
-
** Branch linked: lp:ubuntu/dbus
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740390
Title:
libdbus-1-3 upgrade does not respawn init, resulting in unclean
shutdown
To manage notifications
If stateful re-exec does indeed handle this then agreed, no need for any
triggers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740390
Title:
libdbus-1-3 upgrade does not respawn init, resulting
Well, hindsight being 20-20, I should have seen this as more serious.
Bug 1058517 is now open, it is really a dupe of this. we should
collapse them one way or another.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: upstart (Ubuntu)
Status: Confirmed = Invalid
** Also affects: dbus (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: upstart (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: dbus (Ubuntu Natty)
Importance: Undecided
** Also affects: ubuntu-on-ec2
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740390
Title:
libdbus-1-3 upgrade does not respawn init, resulting in
Ubuntu on EC2 project is not the right place to file these any more.
Instead, please use 'ubuntu-bug package' on an instance, or tag with
'ec2-images' and 'uec-images'
** Changed in: ubuntu-on-ec2
Status: New = Invalid
** Tags added: ec2-images uec-images
--
You received this bug
I'm unable to reproduce this bug.
The ami given (ami-30669459
ubuntu-images-testing/ubuntu-natty-daily-amd64-server-20110321) is no longer
public.
I've tried running the latest daily :
us-east-1 ami-d8e21eb1 canonical ubuntu-natty-daily-i386-server-20110418
then doing:
$ sudo apt-get update
I suspect that the fallout of this is that the filesystem is not
unmounted and thus not clean, right?
Correct. This results in orphaned inodes on reboot. Touching
/var/run/init.upggraded is a possible solution. This will cause init
to respawn on shutdown.
You have reproduced the bug. The problem
I just tested this on a clean natty VM with all updates applied, and I
do indeed see an orphaned inode left over on /
We really need to trigger /var/run/init.upgraded on any of upstart's
dependent libraries. Rather than making all the libraries do this, a
trigger on /lib seems to make more sense
31 matches
Mail list logo
