the shlibs version need to be updated

Bug #459977 reported by Muelli
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evince

Evince won't start for me:
muelli@xbox:~$ evince
evince: symbol lookup error: evince: undefined symbol: ev_stock_icons_init
muelli@xbox:~$

The problem is, that libevview is too old.

muelli@xbox:~/hg/ss08-gender-in-min$ apt-cache policy libevview1 evince
libevview1:
  Installed: 2.26.1-0ubuntu1
  Candidate: 2.26.1-0ubuntu1
  Version table:
     2.28.1-0ubuntu1 0
        400 http://de.archive.ubuntu.com karmic/main Packages
 *** 2.26.1-0ubuntu1 0
        500 http://de.archive.ubuntu.com jaunty-updates/main Packages
        100 /var/lib/dpkg/status
     2.26.0-0ubuntu1 0
        500 http://de.archive.ubuntu.com jaunty/main Packages
evince:
  Installed: 2.28.1-0ubuntu1
  Candidate: 2.28.1-0ubuntu1
  Version table:
 *** 2.28.1-0ubuntu1 0
        400 http://de.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
     2.26.1-0ubuntu1 0
        500 http://de.archive.ubuntu.com jaunty-updates/main Packages
     2.26.0-0ubuntu1 0
        500 http://de.archive.ubuntu.com jaunty/main Packages
muelli@xbox:~

And evince-2.28 doesn't depend on a recent libevview but it obviously should:

muelli@xbox:$ apt-cache show evince
Package: evince
Priority: optional
Section: gnome
Installed-Size: 5796
Maintainer: Ubuntu Desktop Team <email address hidden>
Original-Maintainer: Marc 'HE' Brockschmidt <email address hidden>
Architecture: amd64
Version: 2.28.1-0ubuntu1
Replaces: evince-gtk
Provides: djvu-viewer, evince-gtk, pdf-viewer, postscript-viewer
Depends: libatk1.0-0 (>= 1.20.0), libc6 (>= 2.7), libcairo2 (>= 1.6.0), libdbus-1-3 (>= 1.0.2), libdbus-glib-1-2 (>= 0.78), libdjvulibre21 (>= 3.5.22), libevdocument1, libevview1, libfontconfig1 (>= 2.4.0), libfreetype6 (>= 2.2.1), libgcc1 (>= 1:4.1.1), libgconf2-4 (>= 2.23.2), libglib2.0-0 (>= 2.18.0), libgnome-keyring0 (>= 2.22.2), libgs8, libgtk2.0-0 (>= 2.18.0), libice6 (>= 1:1.0.0), libjpeg62, libkpathsea4 (>= 2007), liblaunchpad-integration1 (>= 0.1.17), libpango1.0-0 (>= 1.14.0), libpoppler-glib4, libsm6, libspectre1, libstdc++6 (>= 4.1.1), libtiff4, libx11-6, libxml2 (>= 2.7.4), zlib1g (>= 1:1.1.4), gconf2 (>= 2.10.1-2), gnome-icon-theme (>= 2.17.1), shared-mime-info
Recommends: dbus-x11, gvfs
Suggests: unrar, poppler-data, nautilus, apparmor
Conflicts: apparmor (<< 2.3.1+1403-0ubuntu18), evince-gtk
Filename: pool/main/e/evince/evince_2.28.1-0ubuntu1_amd64.deb
Size: 442128
MD5sum: c0369333e2278d604e3c0893e8dc162a
SHA1: 612f30c8266716791567874726a9556f94c549fe
SHA256: 36b86ea617d013645c35ffe4b620407cfc6811005ea7d96b616655b1bad15bb3
Description: Document (postscript, pdf) viewer
 Evince is a simple multi-page document viewer. It can display and print
 PostScript (PS), Encapsulated PostScript (EPS), DJVU, DVI and Portable
 Document Format (PDF) files.
 When supported by the document, it also allows searching for text,
 copying text to the clipboard, hypertext navigation, and
 table-of-contents bookmarks.
Homepage: http://www.gnome.org/projects/evince/
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu
Task: ubuntu-desktop, edubuntu-desktop, xubuntu-desktop, mobile-mid, mythbuntu-backend-master, mythbuntu-backend-slave, mythbuntu-desktop, mythbuntu-frontend, ubuntu-netbook-remix

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: evince 2.28.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: evince
Uname: Linux 2.6.31-14-generic x86_64

Revision history for this message
Muelli (ubuntu-bugs-auftrags-killer) wrote :
Revision history for this message
Muelli (ubuntu-bugs-auftrags-killer) wrote : Re: [Bug 459977] Re: Dependency on libevview-2.28

Same for libevdocument1

Revision history for this message
Dimitrios Symeonidis (azimout) wrote : Re: Dependency on libevview-2.28

muelli, how have you managed to have both jaunty and karmic repositories enabled?

Changed in evince (Ubuntu):
status: New → Incomplete
Revision history for this message
Muelli (ubuntu-bugs-auftrags-killer) wrote :

This is simple. Have the repositories set up in /etc/apt/sources.list.d/karmic.list ...

I wonder why you set this bug to INCOMPLETE. The issue is totally unrelated to my repositories: evince depends on more recent versions of libraries...

Changed in evince (Ubuntu):
status: Incomplete → New
Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

confirmed, evince does not have minimum version dependencies for libevview1 and libevdocument1
I'm slightly reluctant about whether it's ok to have repositories from multiple releases...

Changed in evince (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

right, that will not be for karmic now though since changes are frozen

Changed in evince (Ubuntu):
importance: Undecided → Low
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
summary: - Dependency on libevview-2.28
+ the shlibs version need to be updated
Revision history for this message
Manjul Apratim (manzdagratiano) wrote :

I have a similar issue - I enabled some of the karmic repositories in the hope of getting the newer version of virtualbox (so that I could run Dustin Kirkland's testdrive); that did not work out as too many things would have been broken, but a few things did get updated from the karmic repos, which I do not remember. After the reboot everything works fine except for evince, which gives me an error: evince: symbol lookup error: evince: undefined symbol: ev_view_update_view_size.

I have no idea what is causing this issue - I have reinstalled evince along with ubuntu-desktop, and I also installed poppler-data. The problem still persists. Any pointers for what I could do to fix this? I disabled the karmic repos as soon as I saw that pulling virtualbox from karmic would break other packages.

Revision history for this message
Nathan Kidd (nathan-svn) wrote :

@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.

Revision history for this message
Manjul Apratim (manzdagratiano) wrote :

Hmmm... thanks for the analysis! I had, after the problem commenced, uninstalled and reinstalled evince as well as libevview1 and libevdocument1 - and then tried a dpkg-reconfigure. The problem had still persisted though. I guess this might have been due to an incorrect version being referred to by other libraries. The problem has for me been effectively fixed since I could no longer resist the temptation to try to upgrade to karmic a second time, and I did, starting with a clean install, so that I have evince up and running. However, this line of diagnosing where the problem lies should be helpful to others who have similar issues.

Revision history for this message
Sebastien Bacher (seb128) wrote :

usually issue similar to the current comment are due do local make install installations

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is fixed in lucid now, evince Depends on "libevdocument2 (>= 2.29.5), libevview2 (>= 2.29.5)"

Changed in evince (Ubuntu):
status: Confirmed → Fix Released
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.