package fakeroot (not installed) failed to install/upgrade: unable to open '/usr/lib64/libfakeroot/libfakeroot-tcp.so.dpkg-new': No such file or directory

Confirming from duplicates, although I can't reproduce it...

If anyone is still having this issue, could you please post the output of the following commands in a terminal ( Applications -> Accessories -> Terminal ):
ls -ld /usr/lib64
dpkg -S /usr/lib64

Output of
~$ ls -ld /usr/lib64

is this
lrwxrwxrwx 1 root root 3 2009-09-07 22:31 /usr/lib64 -> lib

and of
~$ dpkg -S /usr/lib64

this one
fakeroot: /usr/lib64

It happens with every update. After the update is complete there's this "!" exclamation point.

Hi Çağrı,
thanks for this -- it seems you are on a 64-bit system? I.e. what is your output of:
  uname -a
All other reporters seem to be on a 32-bit system, though... One more question: Did you install Ubuntu 10.04 directly from a CD or USB stick or did you upgrade from an earlier version?

Nope, it's a 32-bit 10.04. I'm sorry, I don't remember perfectly well whether this installation is through upgrade or direct install. Cuz I closed the pc during the 9.04 -> 10.04 upgrade process by mistake. Then it wouldn't normally open up. Then I don't remember what I did. I guess I reinstalled it (10.04) from the cd afai can recall.
I'm not home now, I'll try posting the output when I get home around 13 hours later.

Ok, thanks for following up on this. If you are on a 32-bit, then you shouldn't have this symbolic link from /usr/lib64 to /usr/lib -- this is only correct for 64-bit systems. If I manually add this link on a 32-Bit system I can reproduce the error, so that really seems to be the cause of the problem! I'm not sure whether an old version of fakeroot or another package is responsible for this wrong link.

I think the following should work (DISCLAIMER: The first step might break your system by removing your graphics driver, so maybe not do this on a system where the failing update of fakeroot is just a minor annoyance...):
1. remove the old fakeroot package:
   sudo apt-get remove fakeroot
   Note that this will also remove packages depending on fakeroot, e.g. nvidia or flgrx drivers -- take a note which packages were removed
2. Check whether the symlink still exists, i.e.
    ls -ld /usr/lib64
    If you get "No such file or directory", continue with step 5
3. *If* there is still a symlink, make sure no package claims it:
    dpkg -S /usr/lib64
    This should issue "/usr/lib64 not found"
4. Manually remove the symlink:
    sudo rm /usr/lib64
5. Reinstall fakeroot and/or packages depending on fakeroot (that were removed in step 1)

In fact thank YOU, for following this :D I'm using a faster and safer os free of charge and still I get to have backup support : )
I'll try that when I get home.
Thank you for the solution.

To: M. Stimberg

I had this bug also. I was running a 64 bit version (amd-64 10.04 destop edition installed from cd). I also was using nvidia graphics card/drivers. I have since upgraded to 10.10 desktop using the cd installation and the problem has gone away.
I hope this helps,
Chad

The bug has been correctly diagnosed, more info at http://raphaelhertzog.com/2011/07/18/deciphering-one-of-dpkg-weirdest-errors-unable-to-open-pathtofoo-dpkg-new/

Thus this is not a bug of fakeroot, it didn't setup the /usr/lib64/ symlink. If anyone finds out what did setup this symlink, you should file a bug against this software.

Hi Raphaël,
it's been a while since I looked at this bug -- but doesn't the output of "dpkg -S /usr/lib64" (comment #4) indicate that (some version of) fakeroot indeed installed this symlink?

I have seen this bug as well.
There seem to be two separate issues:

1) some package installs a /usr/lib64. On my system possible culprits could be a) downgrading a Ubuntu 64 bit to 32 bit. The installer said all files would be deleted, but this might have failed. b) Non-native ATI video software that I was trying to install, and that might have contained a bug and c) fakeroot itself : see
dpkg -S /usr/lib64
fakeroot: /usr/lib64

2) fakeroot fails to run upon seeing /usr/lib64 in a 32 bit system. fakeroot should be made more robust.

Is there anybody knowledgeable to tackle both issues ?

This version is now outdated and no more supported