libapt-pkg-libc6.6-6.so.4.5: cannot open shared object file: no such file or directory

Bug #175691 reported by switlikbob
2
Affects Status Importance Assigned to Milestone
command-not-found (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: command-not-found

On boot, a fsck is forced and fails with the following error:

libapt-pkg-libc6.6-6.so.4.5: cannot open shared object file: no such file or directory

Traceback (most recent call last)

File "/usr/lib/command-not-found", line 10, in module
from CommandNotFound import CommandNotFound

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

Is this still a problem?

Changed in command-not-found:
status: New → Incomplete
Revision history for this message
switlikbob (switlikbob) wrote : RE: [Bug 175691] Re: libapt-pkg-libc6.6-6.so.4.5: cannot open shared object file: no such file or directory

No, it turned out that my hard disk was bad. That was the root of all of my problems.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Sarah Hobbs
Sent: Sunday, January 06, 2008 6:17 AM
To: <email address hidden>
Subject: [Bug 175691] Re: libapt-pkg-libc6.6-6.so.4.5: cannot open shared object file: no such file or directory

Is this still a problem?

** Changed in: command-not-found (Ubuntu)
       Status: New => Incomplete

--
libapt-pkg-libc6.6-6.so.4.5: cannot open shared object file: no such file or directory
https://bugs.launchpad.net/bugs/175691
You received this bug notification because you are a direct subscriber
of the bug.

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for this status update on the bugreport.

I close it now.

Changed in command-not-found:
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.