libx86_0.99-1ubuntu1 should fix the most-underlying cause but I think a
change to udev is needed too (to make it less fragile).
Thanks very much to Mathieu Bérard for doing the hard lifting here.
** Changed in: udev (Ubuntu)
Assignee: (unassigned) => Ian Jackson
Status: Confirmed => In Progress
** Changed in: usplash (Ubuntu)
Sourcepackagename: usplash => libx86
Status: Unconfirmed => Fix Released
** Summary changed:
- wrong permissions for /dev/null
+ wrong permissions for /dev/null when /usr is a separate filesystem
** Description changed:
- Binary package hint: udev
-
- just dist-upgraded my desktop (and rebooted), and now zsh complains when
- trying to tab-complete any commands. Also, starting gnome doesn't work.
- Maybe something to do with the uploads today?
+ /etc/init.d/udev calls usplash_write which fails because libx86.so is in
+ /usr (not mounted at this point if /usr is a separate filesystem).
+ /etc/init.d/udev's set -e setting then causes udevd not to run and
+ /dev/null (and many other entries in /dev) end up being wrong.
** Also affects: usplash (Ubuntu)
Importance: Undecided
Status: Unconfirmed
** Description changed:
/etc/init.d/udev calls usplash_write which fails because libx86.so is in
/usr (not mounted at this point if /usr is a separate filesystem).
/etc/init.d/udev's set -e setting then causes udevd not to run and
/dev/null (and many other entries in /dev) end up being wrong.
+
+ Additionally, it is a bug that usplash_write links to libx86 since it is
+ just the IPC client and shouldn't need it.
** Changed in: usplash (Ubuntu)
Importance: Undecided => Low
Status: Unconfirmed => Confirmed
--
wrong permissions for /dev/null when /usr is a separate filesystem
https://launchpad.net/bugs/83878
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
