Mavericks Evince doesn't start

Hello Tobias, could you attach gdb to that process to see if it's waiting for something? Do you get that behavior only running evince without passing to it any document or do you get the same using it to open a doc from the command line? Works fine here so cannot confirm, thanks.

Hey Pedro.

I've just reinstalled the lucid evince.
I don't think gdb will help in any way because there is no crasher at all.
Instead, evince is looking for the backend libraries, i.e. PDF or PS which are provided by lucids evince package:

muelli@xbox:/tmp$ dpkg --listfiles evince | grep backends
/usr/lib/evince/2/backends
/usr/lib/evince/2/backends/pdfdocument.evince-backend
/usr/lib/evince/2/backends/libpdfdocument.so
/usr/lib/evince/2/backends/psdocument.evince-backend
/usr/lib/evince/2/backends/libpsdocument.so
/usr/lib/evince/2/backends/pixbufdocument.evince-backend
/usr/lib/evince/2/backends/libpixbufdocument.so
/usr/lib/evince/2/backends/djvudocument.evince-backend
/usr/lib/evince/2/backends/libdjvudocument.so
/usr/lib/evince/2/backends/tiffdocument.evince-backend
/usr/lib/evince/2/backends/libtiffdocument.so
/usr/lib/evince/2/backends/dvidocument.evince-backend
/usr/lib/evince/2/backends/libdvidocument.so
/usr/lib/evince/2/backends/comicsdocument.evince-backend
/usr/lib/evince/2/backends/libcomicsdocument.so
/usr/lib/evince/2/backends/impressdocument.evince-backend
/usr/lib/evince/2/backends/libimpressdocument.so
muelli@xbox:/tmp$

Mavericks evince package does not have those backends. Neither does the evince-common package. In fact, I can't find any package that provides those backends: http://packages.ubuntu.com/search?searchon=contents&keywords=backends&mode=exactfilename&suite=maverick&arch=any
And if there was such a package, that provided those backends, it should have been marked as hard dependency for evince. But I'm actually surprised that the evince package does not ship the backends.

And yes, I get the behaviour regardless of me giving an argument to evince or not.

Which package provides /usr/lib/evince/2/backends/libpdfdocument.so for you?

that's provided by libevdocument2 here, I'm testing with a new installation on a VM still cannot confirm the issue, is libevdocument2 installed for you there?

Hm. That's weird.
muelli@xbox:~$ apt-cache policy libevdocument2
libevdocument2:
  Installed: 2.30.1-0ubuntu3
  Candidate: 2.30.1-0ubuntu3
  Version table:
     2.30.1-3ubuntu1 0
        400 http://de.archive.ubuntu.com/ubuntu/ maverick/main Packages
 *** 2.30.1-0ubuntu3 0
        500 http://de.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
        100 /var/lib/dpkg/status
     2.30.0-0ubuntu1 0
        500 http://de.archive.ubuntu.com/ubuntu/ lucid/main Packages
[13]+ Done epiphany -p
muelli@xbox:~$ dpkg --listfiles libevdocument2
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libevdocument2
/usr/share/doc/libevdocument2/README
/usr/share/doc/libevdocument2/TODO
/usr/share/doc/libevdocument2/AUTHORS
/usr/share/doc/libevdocument2/copyright
/usr/share/doc/libevdocument2/NEWS.gz
/usr/share/doc/libevdocument2/changelog.Debian.gz
/usr/lib
/usr/lib/libevdocument.so.2.0.0
/usr/lib/libevdocument.so.2
muelli@xbox:~$

But anyway: If Mavericks Evince needslibevdocument2= 2.30.1-3ubuntu1 then it should indicate that, i.e. with proper dependency models.
I'm just again trying to install the maverick evince on lucid, and it doesn't update libevdocument2:
muelli@xbox:~$ sudo apt-get install -t maverick evince
[sudo] password for muelli:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  python-sexy
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  evince-common
Suggested packages:
  poppler-data
The following NEW packages will be installed
  evince-common
The following packages will be upgraded:
  evince
1 upgraded, 1 newly installed, 0 to remove and 937 not upgraded.
Need to get 0B/322kB of archives.
After this operation, 930kB disk space will be freed.
Do you want to continue [Y/n]?

It's easy enough to reproduce: Have a lucid installation (fair enough assumption ;-) ) and then try to install mavericks evince via apt-get install -t maverick evince. Then, evince wouldn't work anymore.

I had installed libevdocument2 myself to make it work. So clearly, mavericks evince should depend on a recent enough libevdocument2.

Also evince-gtk should depend on libevdocument2. It wont start woithout it, with the same erro message (no backends found).

Didier, you worked on the new version, could you check if depends are correct?

Hum, that's weird, I have a clean netbook install there, when trying to launch evince, no issue at all.

Furthemore, evince and evince-gtk are depending on libevdocument2:

didrocks@tidus:~$ apt-cache show evince
Package: evince
[…]
Version: 2.30.1-3ubuntu1
Depends: libatk1.0-0 (>= 1.29.3), libc6 (>= 2.4), libcairo2 (>= 1.2.4), libdbus-1-3 (>= 1.0.2), libdbus-glib-1-2 (>= 0.78), libevdocument2 (>= 2.30.1), libevview2 (>= 2.30.1), libfontconfig1 (>= 2.8.0), libfreetype6 (>= 2.2.1), libgconf2-4 (>= 2.27.0), libglib2.0-0 (>= 2.24.0), libgnome-keyring0 (>= 2.22.2), libgtk2.0-0 (>= 2.16.0), libice6 (>= 1:1.0.0), liblaunchpad-integration1 (>= 0.1.17), libnautilus-extension1 (>= 1:2.29.1), libpango1.0-0 (>= 1.14.0), libsm6, libx11-6, libxml2 (>= 2.7.4), zlib1g (>= 1:1.1.4), gconf2 (>= 2.28.1-2), evince-common (>= 2.30), evince-common (<< 2.31), gnome-icon-theme (>= 2.17.1), shared-mime-info

$ apt-cache show evince-gtk
Package: evince-gtk
[…]
Version: 2.30.1-3ubuntu1
Depends: libatk1.0-0 (>= 1.29.3), libc6 (>= 2.4), libcairo2 (>= 1.2.4), libevdocument2 (>= 2.30.1), libevview2 (>= 2.30.1), libfontconfig1 (>= 2.8.0), libfreetype6 (>= 2.2.1), libglib2.0-0 (>= 2.24.0), libgtk2.0-0 (>= 2.16.0), libice6 (>= 1:1.0.0), liblaunchpad-integration1 (>= 0.1.17), libpango1.0-0 (>= 1.14.0), libsm6, libx11-6, libxml2 (>= 2.7.4), zlib1g (>= 1:1.1.4), evince-common (>= 2.30), evince-common (<< 2.31), gnome-icon-theme (>= 2.17.1), shared-mime-info

So, right, they only depends on 2.30.1, not on 2.30.1-3ubuntu1 despite the packaging changes (some files changed between package). And as you just apt-get install evince for maverick, that's why you don't get the new libevdocument2 version, which shouldn't happen if you dist-upgrade. Fixing that today.

Setting the task to In Progress then, Thanks Didier.

This bug was fixed in the package evince - 2.30.1-3ubuntu2

---------------
evince (2.30.1-3ubuntu2) maverick; urgency=low

  * debian/rules:
    - bump DEB_DH_MAKESHLIBS_ARGS to not have people trying partial
      upgrade with apt-get install evince and not having new
      libevdocument2 version (some files have moved between package)
      (LP: #589194)
 -- Didier Roche <email address hidden> Tue, 08 Jun 2010 09:31:18 +0200

Hm. Reopening because an upgrade just broke my evince:

muelli@xbox:/tmp$ apt-cache policy libevdocument2
libevdocument2:
  Installed: 2.30.3-0ubuntu1
  Candidate: 2.30.3-0ubuntu1
  Version table:
 *** 2.30.3-0ubuntu1 0
        500 http://de.archive.ubuntu.com/ubuntu/ lucid-proposed/main Packages
        100 /var/lib/dpkg/status
     2.30.1-3ubuntu2 0
        400 http://de.archive.ubuntu.com/ubuntu/ maverick/main Packages
     2.30.1-0ubuntu3 0
        500 http://de.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
     2.30.0-0ubuntu1 0
        500 http://de.archive.ubuntu.com/ubuntu/ lucid/main Packages
muelli@xbox:/tmp$

and the lucid libevdocument doesn't seem to have the required files in /usr/lib/evince/2/backends:
muelli@xbox:/tmp$ evince

(evince:12880): EvinceDocument-WARNING **: Error opening directory '/usr/lib/evince/2/backends': No such file or directory
muelli@xbox:/tmp$

sudo apt-get install -t maverick libevdocument2=2.30.1-3ubuntu2
fixed the issue for me. I don't want to do that on every unattended-upgrade though ;-) So please get the dependencies right.

That's because you mix lucid and maverick in your source.list!

Please, do not mix that as the packaging has diverged (lucid-proposed got another verson which was installed there) and stick with maverick repository only. That explains why you had this invalid bug reopened, you won't have it otherwise.

Hey,

On 28.06.2010 09:33, Didier Roche wrote:
> That's because you mix lucid and maverick in your source.list!
>
Well. I've also pinned packages from the maverick repository to a lower
priority. Which, at least for the people I deal with, is quite a normal
thing to do. And it rarely caused problems, except for bug 459977 (which
funnily enough was a packaging problem in Evince, too). But that was,
rightfully so, fixed.

So I am quite surprised that the Evince package is the only one so far,
that causes troubles although it worked (almost) flawlessly for years.

Cheers,
  Tobi

There was simply some files not in the right package for lucid and we don't want to change the packaging in a stable release. Hence the fact you either stick with evince related package in maverick or take all from lucid, but don't mix box of them and downgrade/upgrade.