Apparently this:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/811441 is a
duplicate of this 'Fix Released' bug yet I still get the error on my
Xubuntu 13.10 laptop...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After I patched the right version, do I need to reboot the box or it
will take effect on the fly?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete migration to /run (shutdown
Looks like it was.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete migration to /run (shutdown script
This bug was fixed in the package insserv - 1.12.0-14ubuntu0.2
---
insserv (1.12.0-14ubuntu0.2) lucid-proposed; urgency=low
* Only try to move links in /etc/rc{0,6}.d that match S0*. LP:
#941867.
insserv (1.12.0-14ubuntu0.1) lucid-proposed; urgency=low
[ Adam Stokes ]
* Add
This bug was fixed in the package insserv - 1.14.0-2ubuntu0.11.04.2
---
insserv (1.14.0-2ubuntu0.11.04.2) natty-proposed; urgency=low
* Only try to move links in /etc/rc{0,6}.d that match S0*. LP:
#941867.
insserv (1.14.0-2ubuntu0.11.04.1) natty-proposed; urgency=low
[ Adam
This bug was fixed in the package insserv - 1.14.0-2.1ubuntu0.2
---
insserv (1.14.0-2.1ubuntu0.2) oneiric-proposed; urgency=low
* Only try to move links in /etc/rc{0,6}.d that match S0*. LP:
#941867.
insserv (1.14.0-2.1ubuntu0.1) oneiric-proposed; urgency=low
[ Adam Stokes ]
@Clint
Wasn't verification done on all releases back in comment #66?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete migration to /run (shutdown script order has been
[BUMP] can somebody verify this fix on lucid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete migration to /run (shutdown script order has been
demolished)
To manage
This bug affects Ubuntu 10.10, Maverick Meerkat. Maverick has reached
end-of-life and is no longer supported, so I am closing the bugtask for
Maverick. Please upgrade to a newer version of Ubuntu.
More information here:
https://lists.ubuntu.com/archives/ubuntu-announce/2012-April/000158.html
** Tags removed: verification-failed
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete migration to /run (shutdown script order has been
** Branch linked: lp:ubuntu/sysvinit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete migration to /run (shutdown script order has been
demolished)
To manage notifications
Please see #941867 - in Precise the postinst script that attempts to
change the order to the correct one fails, leaving the system unable to
boot the default kernel (because initrd isn't generated during dist-
upgrade) with no networking (update of network-manager depends on
initscripts) or
Bug #941867 is a regression introduced by this change. We need to cope
with systems whose shutdown script ordering has already been partially
fixed locally by the admin.
** Tags removed: verification-done
** Tags added: verification-failed
--
You received this bug notification because you are
The debian/changelog entry also has the LP number listed incorrectly
(as does the related Bazaar commit message):
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/lucid/insserv/lucid-proposed/revision/15/debian/changelog
On webpage http://people.canonical.com/~ubuntu-archive/pending-sru.html
the package insserv has wrong LP number.
It is #897390 , but it should be #858122
Could you please fix this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello.
I've installed Ubuntu 11.10 from the scratch and I do not have VMWare on
my computer, but I have the same problem. I've recreated symbolic links
(please see below), but this didn't solved problem with loading.
alex@alex-thinkpad-t410:~$ ls -l /var/run /var/lock
lrwxrwxrwx 1 root root 9
On Wed, Feb 29, 2012 at 06:21:14PM -, Alex L. wrote:
I've installed Ubuntu 11.10 from the scratch and I do not have VMWare on
my computer, but I have the same problem. I've recreated symbolic links
(please see below), but this didn't solved problem with loading.
Please test the package in
Just a note... I can't get why the sendsig (for example) does have a
S-link. The script does only handle stop (start is a no-op). Same goes
for umountfs etc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: insserv (Ubuntu Oneiric)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete migration to /run (shutdown script order
Sorry! I managed to click on a link that changed the status with no
questions asked (just wanted to get an explanation of the status). Can
someone undo the Status change? I can't undo it myself :-/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: insserv (Ubuntu Oneiric)
Status: Fix Released = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete migration to /run (shutdown script order
The fixes seem to work in my build chroots for all 4 releases:
evan@caron:~$ schroot -c oneiric-amd64 -u root
(oneiric-amd64)root@caron:~# apt-get update -qq
(oneiric-amd64)root@caron:~# apt-get dist-upgrade -yy /dev/null
(oneiric-amd64)root@caron:~# insserv /dev/null
(oneiric-amd64)root@caron:~#
Yes, Tom is right. In order to avoid the problem I reinstalled my system
from scratch and did not install the faulty package.
Nevertheless, I tried oneiric-proposed with a virtual machine and the
faulty package.
# BEFORE INSTALL OF turboprint
eduard@qemu-oneiric:~$ ls /etc/rc6.d
I'm not sure we can report anything useful though, as anyone reading
this will already have fixed the boot order in order to get their
machine working again :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Tom, or anyone else affected,
Accepted into lucid-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed
Hello Tom, or anyone else affected,
Accepted into maverick-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags
Hi, uploading a debdiff for Lucid. thanks,
** Patch added: Lucid insserv_1.12.0-14_14ubuntu1.debdiff
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/858122/+attachment/2774864/+files/insserv_1.12.0-14_14ubuntu1.debdiff
--
You received this bug notification because you are a member
I've uploaded SRUs of insserv to lucid, maverick, natty, and oneiric.
Based on IRC discussions with Steve, I added a postinst to those
versions that cleans up the broken shutdown sequence. It's the same
snippet that I added to initscripts, but for the SRU case, ensuring
correct ordering of the
Fixed in the latest upload of insserv:
insserv (1.14.0-2.1ubuntu1) precise; urgency=low
* Add 200_hide_insserv_on_ubuntu.patch: Move insserv out of system path
to disuade package maintainers from invoking it directly. (LP:
#897390)
** Changed in: insserv (Ubuntu Precise)
This bug was fixed in the package sysvinit - 2.88dsf-13.10ubuntu10
---
sysvinit (2.88dsf-13.10ubuntu10) precise; urgency=low
* On upgrade, detect and correct broken shutdown sequence caused by
3rd-party packages running insserv. (LP: #858122)
-- Evan Broder e...@ebroder.net
** Also affects: insserv (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/858122
Title:
incomplete migration to /run (shutdown script order has
(Err, to clarify, I have not sponsored it just yet, but will be doing so
momentarily after a little more testing)
** Changed in: insserv (Ubuntu Oneiric)
Status: New = Triaged
** Changed in: insserv (Ubuntu Precise)
Status: New = Triaged
** Changed in: insserv (Ubuntu Oneiric)
Hi Adam -
Thanks for working on getting that patch together. I've gone ahead and
sponsored it into precise, and will be working on an SRU for oneiric
momentarily. For future reference, I made a few tweaks before uploading:
1. The insserv package is source format 3.0 (quilt), so it uses quilt
to
Ok. I've installed the package in a VM and then verified that installing
VMware Player does not break my boot order. Therefore, I've uploaded the
change to precise and oneiric-proposed. The oneiric-proposed upload
should be processed by a member of the SRU team before too long.
--
You received
** Also affects: insserv (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: sysvinit (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: insserv (Ubuntu Maverick)
Importance: Undecided
Status: New
** Also affects: sysvinit (Ubuntu
It's a bit unclear to me what the recommended fix for the upgrade
process is. I would like to upgrade from 11.04 to 11.10. I am running
Ubuntu in VMware Workstation 7.1.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- I had the exact same issue documented as
- https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/807306 on
- upgrade from 11.04 to 11.10. Opening new bug as req.
+ [Impact]
+ fill me in with explanation of severity and frequency of bug on users and
** Description changed:
[Impact]
- fill me in with explanation of severity and frequency of bug on users and
justification for backporting the fix to the stable release
+ severity : a total lack of system (wireless) networking coming up - this
gives a ! minute pause during boot, as well as a
This patch attempts to move insserv out of the system path in order to
dissuade package maintainers from invoking it directly.
** Patch added: insserv_1.14.0-2.1ubuntu1.unstable.debdiff
re comment #45
Steve,
If we think about moving insserv out of system path we need to make sure
that update-rc.d is not broken by this since it assumes it can reach the
binary within the path. Other than that I dont think anything else
would be affected.
--
You received this bug notification
On Fri, Jan 13, 2012 at 08:42:12AM -, Adam Stokes wrote:
If we think about moving insserv out of system path we need to make sure
that update-rc.d is not broken by this since it assumes it can reach the
binary within the path. Other than that I dont think anything else
would be affected.
Still not fixed as of 26 December 2011.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete migration to /run (shutdown script order has been
demolished)
To manage
As A.B. (abadr) wrote in comment#43, my system that was hit by this is
a pure Ubuntu box, *except for the fact that webmin is installed*.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
Suffered similar issue of the /etc/rc0.d and rc6.d links being mangled
by VMware player upgrade, in my case using 10.04.3 LTS version. Wrote a
short script that puts it back to the order that I found on another
(hopefully correct) 10.04 installation.
As with all scripts, and in particular with
** Attachment added: bash script to restore rc0.d and rc6.d ordering.
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/858122/+attachment/2606029/+files/debork-vmware.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Mon, Nov 07, 2011 at 12:07:12PM -, markusj wrote:
My rc0.d/rc6.d have been broken the same way. Can someone please tell me
the default order for rc0.d, please? For now, i'm assuming they are the
same as for rc6, is that correct?
See comment #22.
This /run migration thing created a big
** Description changed:
I had the exact same issue documented as
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/807306 on
upgrade from 11.04 to 11.10. Opening new bug as req.
Removing the existing /var/run and /var/run/lock and replacing with sym
links as per comment
My rc0.d/rc6.d have been broken the same way. Can someone please tell me
the default order for rc0.d, please? For now, i'm assuming they are the
same as for rc6, is that correct?
This is an epic fail. Really. fsck on each boot because none of the
filesystems has been unmounted properly is
The root of this cause is not vmware (because I never even knew about it until
some weeks, but my bug exists longer) or I have another variant.
Look at my symlinks:
/var$ ll
insgesamt 64
drwxr-xr-x 16 root root 4096 2011-10-30 22:47 ./
drwxr-xr-x 23 root root 4096 2011-10-19 21:43 ../
...
On Mon, Oct 31, 2011 at 08:57:44PM -, magelan wrote:
The root of this cause is not vmware (because I never even knew about it
until some weeks, but my bug exists longer) or I have another variant.
You have a completely unrelated issue, because:
Look at my symlinks:
/var$ ll
insgesamt 64
packrook solution worked for me. Thanks.
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/811441/comments/9
This is a serious bug brought down an important backup server. The
server was a standard Ubuntu server installation with only 1 foreign
repo (webmin). This doesn't look good for Ubuntu
If you are pre upgrade to 11.10 can you uninstall VMWare Player and then
reinstall Player after update and avoid this issue? Just thinking about
work around strategies. As currently the this only covers how to fix up
the issue.
--
You received this bug notification because you are a member of
On Sun, Oct 30, 2011 at 09:46:30PM -, karit wrote:
If you are pre upgrade to 11.10 can you uninstall VMWare Player and then
reinstall Player after update and avoid this issue?
No. VMWare Player damages the shutdown script ordering; uninstalling it
won't undo this.
--
Steve Langasek
Trebacz (from Comment #25),
I was able to simply uninstall and re-install the package, and it seems
to work fine now. I pressed Ctrl+Alt+F1 when I got the blank screen
after a reboot, logged in, and did this:
sudo apt-get remove nvidia-current
sudo apt-get install nvidia-current
--
You
Any progress on this one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete migration to /run (shutdown script order has been
demolished)
To manage notifications about this
I also experienced this bug, because I had the shutdown script order messed up
by VMware Workstation.
Everything was fixed by manually creating the links to /run and /run/lock as
per #18, and restoring the correct shutdown script order as per #22.
So, as a side effect of the /run problem, this
Jeff, maybe you suffer from bug #881079 too? I thought about the extra
NIC from my 3G card, but I also experience it without the modem enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Hi,
same problem after a migration from natty-oneiric desktop.
I had to create symlinks for /var/run and /var/lock
and it works again
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
Steve, I opened a new bug report #881079 as I could not see any reported
for my case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete migration to /run (shutdown script order
It looks like I'm having the Waiting for network configuration issue as well,
but while an annoyance, I've ignored it until today. I figured it was related
to an extra NIC being unconfig'd. I just config'd LACP and I've still got it,
so went hunting for a bug.
I checked and I've got the
Could I know that what should be done to receive the fix? The manual fix
(commands listed in #18) does not seems to be stable when my PC is going
to upgrade again (to 12.04 LTS).
I do not dare to reboot my PC because of this bug.
--
You received this bug notification because you are a member of
On Sun, Oct 23, 2011 at 06:50:16AM -, TinHo MAK wrote:
Could I know that what should be done to receive the fix? The manual fix
(commands listed in #18) does not seems to be stable when my PC is going
to upgrade again (to 12.04 LTS).
I do not dare to reboot my PC because of this bug.
Hmm, I have verified #22 and my /run seems right:
$ ls -lhd /run
drwxr-xr-x 23 root root 880 2011-10-23 04:22 /run
$ ls -lhd /var/run
lrwxrwxrwx 1 root root 4 2011-10-22 01:34 /var/run - /run
$ ls -lhd /var/run/lock/
drwxrwxrwt 2 root root 40 2011-10-23 04:22 /var/run/lock/
but I still get the
You don't say what error message you're receiving, but if you have
/var/run as a symlink, then it's not caused by this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete
Like many here, I had the same problem when upgrading natty server to
oneiric server. The conversion/migration of /var/run to /run during the
upgrade process is buggy causing all sorts of problems until the content
of /var/run and /var/lock are moved to /run and symlinks are created
shown below as
** Changed in: ubuntu-release-notes
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete migration to /run (shutdown script order has
Like #18 ran into this when updating to maverick. As both occured in
VMware guest installations I suspect that in that specific case vmware-
tools caused the incomplete transition.
I also saw messed up shutdown orders, but not in all installations. You
may also have a look at rc0.d for halting.
This error produces the Waiting for network configuration error message.
The fix is to symlink /var/run to /run and /var/lock to /run/lock
http://uksysadmin.wordpress.com/2011/10/14/upgrade-to-ubuntu-11-10
-problem-waiting-for-network-configuration-then-black-screen-solution/
I've had a massive
Update: I found that the root cause of my X11 not starting was due to
my nvidia-current package being in a bad state during the upgrade. The
video drivers were not installed for the new kernel, which was causing
the second issue.
After manually doing the move symlink of /var/run and
Much like the responder in #24. I became a subscriber to this bug to to
the errors that I was seeing after the upgrade from 11.04 to 11.10.
Based on what I'm seeing in my system logs it seems the video driver
integration into the latest 3.0.0-12.20 kernel is borked. My upgrade
reported that the
Maybe it makes sense to put also the 3rd party turboprint package in
the affected package list for the release-notes (See Bug #811675)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
For me, this problem was caused by VMWare Workstation 8 leaving a mount
point of some sort in /var/run. After umounting and symlinking manually
(per the comments above) I was good to go. I wouldn't say VMware is the
root cause. The mount point is in the fstab. They aren't doing anything
wrong by
I had this problem, too, and I don't have VMWare installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete migration to /run (shutdown script order has been
demolished)
For me, this problem was caused by VMWare Workstation 8
leaving a mount point of some sort in /var/run.
Incorrect. The problem is that upon installation, VMWare Workstation 8
*destroys* the shutdown sequence of the system. Merely adding a mount
point doesn't matter, because the shutdown
I'm seeing this on a Thinkpad T410 that has been dist-upgraded to
Oneric. It started out running a freshly installed Maverick, which I
have upgraded up to Oneric now.
The system failed to boot after dist-upgrade with dbus error messages
like in Bug #811441
I do not have any weird cifs or nfs
FYI: I had previously upgraded from Maverick - Natty
I experienced the issue when upgrading from Natty - Oneric
I manually did the following:
sudo mv /var/run/* /run/
sudo mv /var/lock/* /run/lock/
sudo rmdir /var/run
sudo rmdir /var/lock
sudo ln -s /run /var/run
sudo ln -s /run/lock /var/lock
The same what Steve said for vmware is also true for turboprint:
*destroys* the shutdown sequence of the system.
You could try to fiddle with the '/run' symlinks and manually correct
the script order. But IMHO the only reliable way to get the script order
back is to make a fresh Oneiric install,
I disagree. There is no sane reason for those packages to be messing with the
order.
The change to the order renders a system unusable on upgrade.
The upgrade should just fix the order.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As a highly experimental means to get the system back working one can
try to:
sudo mv /etc/rc6.d/S01reboot /etc/rc6.d/S90reboot
sudo mv /etc/rc6.d/S01umountroot /etc/rc6.d/S60umountroot
and do a sudo reboot afterwards. Please be aware that the other
scripts remain reordered, but it should be
On Fri, Oct 14, 2011 at 09:50:19PM -, Eduard Hasenleithner wrote:
As a highly experimental means to get the system back working one can
try to:
and do a sudo reboot afterwards. Please be aware that the other
scripts remain reordered, but it should be enough to be able to backup
your
** Changed in: ubuntu-release-notes
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete migration to /run (shutdown script order has been
** Also affects: sysvinit (Ubuntu Oneiric)
Importance: High
Status: Triaged
** Also affects: sysvinit (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: sysvinit (Ubuntu Precise)
Status: New = Triaged
** Changed in: sysvinit (Ubuntu Precise)
The root cause of this problem seems to be VMWare Workstation 8/Player.
https://bugs.launchpad.net/ubuntu/lucid/+source/sysvinit/+bug/616287/comments/93
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Changed in: ubuntu-release-notes
Importance: Undecided
Manual symlink of /var/run-/run and /var/lock-/run/lock fixed my
issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete migration to /run (shutdown script order has been
84 matches
Mail list logo
