mapdevfs: error while loading shared libraries

Bug #387093 reported by Asif Youssuff
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
os-prober (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: os-prober

Freshly installed Karmic system, I run sudo os-prober to try to detect my Windows partition -- I get these errors:

sudo os-prober
[sudo] password for tanzib:
mapdevfs: error while loading shared libraries: libdebian-installer.so.4: cannot open shared object file: No such file or directory
mapdevfs: error while loading shared libraries: libdebian-installer.so.4: cannot open shared object file: No such file or directory
mapdevfs: error while loading shared libraries: libdebian-installer.so.4: cannot open shared object file: No such file or directory
mapdevfs: error while loading shared libraries: libdebian-installer.so.4: cannot open shared object file: No such file or directory
mapdevfs: error while loading shared libraries: libdebian-installer.so.4: cannot open shared object file: No such file or directory
mapdevfs: error while loading shared libraries: libdebian-installer.so.4: cannot open shared object file: No such file or directory

ProblemType: Bug
Architecture: amd64
Date: Sun Jun 14 18:35:24 2009
Dependencies:

DistroRelease: Ubuntu 9.10
Package: os-prober 1.29ubuntu2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-9.10-generic
SourcePackage: os-prober
Uname: Linux 2.6.30-9-generic x86_64

Asif Youssuff (yoasif)
summary: - mapdevfs: error while loading shared libraries
+ [karmic] mapdevfs: error while loading shared libraries
Revision history for this message
Colin Watson (cjwatson) wrote : Re: [karmic] mapdevfs: error while loading shared libraries

You shouldn't have a mapdevfs binary installed at all; this isn't really os-prober's fault (it can deal with a *missing* mapdevfs, but not a broken one), but the fault of whatever set your system up to have a mapdevfs binary without its dependencies satisfied. Could you please attach /var/log/installer/syslog to this bug?

Changed in os-prober (Ubuntu):
status: New → Incomplete
Revision history for this message
Asif Youssuff (yoasif) wrote :

/var/log/installer/syslog does not exist on this system, and the os-prober bug seems to have been fixed in a recent update.

Revision history for this message
orange (launchpad-net-orange-tree) wrote :

I'm having this on karmic as well - no /var/log/installer/syslog
dpkg -S /bin/mapdevfs gives:
ubiquity: /bin/mapdevfs

Revision history for this message
orange (launchpad-net-orange-tree) wrote :

temporarily removing /bin/mapdevfs seems to solve the problem - I suspect this is related to the install not finishing properly :(

Revision history for this message
Colin Watson (cjwatson) wrote :

If you experience this, please try reinstalling to reproduce this bug, and *before* you reboot, attach /var/log/syslog from the running live session.

Revision history for this message
orange (launchpad-net-orange-tree) wrote :

will try on the latest daily live cd...
no news is good news...

Revision history for this message
papukaija (papukaija) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If you could test the current Ubuntu development version, this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 387093, and any other logs that are relevant for this particular issue. Please feel free to report any other bugs you may find.

summary: - [karmic] mapdevfs: error while loading shared libraries
+ mapdevfs: error while loading shared libraries
tags: added: karmic
Revision history for this message
papukaija (papukaija) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
papukaija (papukaija) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in os-prober (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.