*** This bug is a duplicate of bug 257052 ***
https://bugs.launchpad.net/bugs/257052
>From the initial stack trace I presented in the initial report we can
see that the problem is identified in not being able to find
libffi.s0.4. The file is truly not installed under Intrepid. I have
confirmed this on two separate Intrepid installations. Digging into the
problem I found that if I cheat and create a symlink called
/usr/lib/libffi.so.4 and link it to /usr/lib/libffi.so.5.0.6 then
glipper will not only allow me to install it on the panel without error,
but it seems to function fully. The crude fix was primarily for
diagnostics only, although glipper is important to my desktop and I
really need to use it so it may stand until completely fixed...
I traced the problem to the shared object file called _keybinder.so. The
file is located /var/lib/python-support/python2.5/glipper/keybinder/
directory. You can see the needed dependency if you run the following
command:
ironman:~> objdump
/var/lib/python-support/python2.5/glipper/keybinder/_keybinder.so -x|grep ffi
NEEDED libffi.so.4
The problem can be clearly seen at this point. There are three solutions
to the problem. The first would be to rebuild the glipper shared objects
using libffi.so.5, readd libffi.so.4 back on Intrepid, or create a bogus
symlink from libffi.so.4 to /usr/lib/libffi.so.5.0.6. I personally would
recommend the option as all others are retroactively solving the
problem.
** Changed in: glipper (Ubuntu)
Status: New => In Progress
--
intrepid: glipper crashed with ImportError in <module>()
https://bugs.launchpad.net/bugs/271408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
