@manzdagratiano I had the same symptom (but without mixed jaunty/karmic sources). It turned out to be caused by a rogue evince installation in /usr/local
What I did to track this down (in a terminal): 1. Verify these versions match: for f in evince libevview1 libevdocument1 ; do apt-cache show $f | grep Version; done 2. Verify which evince you're running and where its libs are coming from: which evince ldd `which evince` | grep libev 3. Confirm the files in 2. are installed by the packages you installed dpkg -S `which evince` ldd `which evince` | sed -n 's/.*=> \([^ ]*libev[^ ]*\) .0x.*/\1/p' | xargs dpkg -S If the package versions don't match then fix that (e.g. "dpkg --force- depends -r PKG" to remove followed by "apt-get install PKG" to get latest. If evince or any of its loaded libs are not the files provided by the system packager then fix your path/libpath, or remove the bad versions. -- the shlibs version need to be updated https://bugs.launchpad.net/bugs/459977 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
