[jaunty] last update broke some libraries (libnss3-1d, libnspr4-0d)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nspr (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
| Jaunty |
Fix Released
|
High
|
Unassigned | ||
| nss (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
| Jaunty |
Fix Released
|
High
|
Unassigned | ||
Bug Description
Hello! I'm running an (almost) up-to-date Jaunty here.
Earlier today I did an "aptitude safe-upgrade", and I didn't check the output very carefully. After a restart, I got a report that the clock applet crashed, which I ignored (it happens); then I noticed my network wasn't running, and Firefox refused to start.
So I looked around a bit and noticed the boot log (in the console) complained that NetworkManager can't start because of a missing libnss3.so.1d. Indeed, when I checked the package libnss3-1d was there and was supposed to have that file, but the file wasn't there (libnss3.so existed, though).
I started the network manually and did an "aptitude reinstall libnss3-1d", which created the correct link. Firefox still wasn't starting and it wasn't telling me why, so I installed epiphany-gecko which complained about a missing libnspr4.so.0d. So I did the same thing, now Firefox is running (I'm sending this report with it).
I've no idea why those two links were missing, maybe somebody should look into it. Anyone have any idea how to find out if I've got other missing files?
I attached the contents of /var/log/
| Bogdan Butnaru (bogdanb) wrote | #1 |
| Bogdan Butnaru (bogdanb) wrote | #2 |
| Alexander Sack (asac) wrote | #3 |
| Alexander Sack (asac) wrote | #4 |
| Bogdan Butnaru (bogdanb) wrote | #5 |
| hoffmajs (hoffmajs) wrote | #6 |
| Bogdan Butnaru (bogdanb) wrote | #7 |
| Alexander Sack (asac) wrote | #8 |
| Changed in nspr: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| Changed in nss: | |
| status: | New → Confirmed |
| Michael Vogt (mvo) wrote | #9 |
| Changed in nspr: | |
| milestone: | none → jaunty-alpha-3 |
| status: | Confirmed → Triaged |
| Alexander Sack (asac) wrote | #10 |
| Changed in nss: | |
| importance: | Undecided → High |
| milestone: | none → jaunty-alpha-3 |
| status: | Confirmed → Triaged |
| Alexander Sack (asac) wrote | #11 |
| Alexander Sack (asac) wrote | #12 |
| Ara Pulido (ara) wrote | #13 |
| James Westby (james-w) wrote | #14 |
| Alexander Sack (asac) wrote | #15 |
| Alexander Sack (asac) wrote | #16 |
| Changed in nspr: | |
| status: | Triaged → Fix Committed |
| Alexander Sack (asac) wrote | #17 |
| Changed in nss: | |
| status: | Triaged → Fix Committed |
| Launchpad Janitor (janitor) wrote | #18 |
| Changed in nss: | |
| status: | Fix Committed → Fix Released |
| Launchpad Janitor (janitor) wrote | #19 |
| Changed in nspr: | |
| status: | Fix Committed → Fix Released |
Just in case somebody needs this, the script below will display missing files from your computer (in the sense that dpkg believes a package supplies a certain file, but the file either doesn't exist or is a dangling symlink). It found quite a few problems, but I didn't have time to figure out what's wrong with each and report them.
#!/bin/bash
for PAK in `dpkg-query -W -f='${Package} '`; do
dpkg-query -L $PAK \
| sed 's/diverted by [^:]*: //;s/package diverts others to: //' \
| xargs -I {} \
bash -c '\
if [ ! -e "$0" ] ; then \
if [ -L "$0" ]; then \
echo Dangling link "$0" in package '"$PAK"';\
else
echo File "$0" missing from package '"$PAK"';\
fi;\
fi'\
{}
#break
done