[feisty] libx86.so.1 moved to /usr/lib -- and completely hosed my system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libx86 (Ubuntu) |
Fix Released
|
Critical
|
Colin Watson |
Bug Description
Binary package hint: libx86-1
This afternoon I applied libx86-
At home I powered on... and found my (so farquite) nice Ubuntu completely hosed. It did boot, but it did not bring up the wired network interface (and the wireless was hosed), hal and udev were completely bonkers, and Gnome would simply blow on startup and freeze.
After some research, and tries and retries, I isolated the issue to libx86.so.1 (with the help of another reboot, and a quick glance at some not-so-kosher messages being put out by usplash_write.
And I got it, finally. libx86.so.1 has been moved (from /lib) to /usr/lib.
With all due respect, a Real Bad Idea.
On systems that install everything under a single filesystem, no problem. On systems that maintain /usr/lib under the same filesystem as /, no problem.
On ANY other system... I guess you can figure it: a lot of init.d programs depend on libx86.so.1, and some are started BEFORE the filesystems are mounted.
Which is my case: all my machines have /usr/lib on a different filesystem than / (which is to say, under /usr).
I cannot set the priority on this bug -- I do not have this type of access. So, please whoever does have it: set it as CRITICAL. Real Show-Stopper.
I cannot emphasise it more: this is a critical issue. This has to be fixed ASAP.
List of installed files for the package:
/.
/usr
/usr/lib
/usr/lib/
/usr/share
/usr/share/doc
/usr/share/
/usr/share/
/usr/share/
On the other hand... this is what we are bound to see happening when we work with pre-releases :-) Part of the game.
Confirmed