Eduard Hasenleithner [2011-07-15 6:27 -]:
One further info: During installation of the upgrade, it looked like
that not all postinst scripts were executed properly because of the cups
postinst script failing.
This should be fixed in cups 1.4.7-1ubuntu1.
Could it be that the /var/run
On Fri, Jul 15, 2011 at 08:05:25AM -, Eduard Hasenleithner wrote:
No, it's set up in an upstart job, so you need to reboot after
the upgrade.
Now that is strange, I rebooted already several times, but the situation
did not change. Maybe there is a chicken-and-egg problem of upstart not
On Fri, Jul 15, 2011 at 05:40:12PM -, Eduard Hasenleithner wrote:
Is your /etc/init.d/umountroot the unmodified version from the
package?
I didn't change it, md5sum is 36d5098f8a3965dce172a1c8f75e1429.
This is the correct md5sum.
Do the symlinks /etc/rc0.d/S60umountroot and
On Fri, Jul 15, 2011 at 07:30:54PM -, Eduard Hasenleithner wrote:
Do the symlinks /etc/rc0.d/S60umountroot and /etc/rc6.d/S60umountroot
exist?
Yes they do. Question: Do I remember correctly that the symlinks with S
are used for starting, and those with K for stopping? If that is the
On Mon, Jul 11, 2011 at 11:36:38PM -, Robert Hooker wrote:
if sysvinit and initramfs-tools are going to take awhile to update
(which they probably will since its a very complex merge) perhaps
removing /run in the base-files postinst is the way to go? This should
be affecting 100% of
On Fri, Jul 08, 2011 at 10:44:31PM -, Dave Gilbert wrote:
The older kernels (3.0-1 and 2.6.39 something) also don't work, so not that.
One thing I've had ever since I first upgraded that vm to OO is that during
boot I get the message:
error: runtime directory '/run/udev' not
On Fri, Jul 08, 2011 at 10:44:31PM -, Dave Gilbert wrote:
dpkg-log's below.
Thanks for that. So, attached is the tabulated list of upgraded
packages. Quite a few actually, although few that have to do with
input, and only a small number of X packages.
Still, I would suggest testing
