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
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
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.
--
Mavericks Evince
Hm. Reopening because an upgrade just broke my evince:
mue...@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
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
Didier, you worked on the new version, could you check if depends are
correct?
** Changed in: evince (Ubuntu)
Assignee: (unassigned) = Didier Roche (didrocks)
--
Mavericks Evince doesn't start
https://bugs.launchpad.net/bugs/589194
You received this bug notification because you are a
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:
didro...@tidus:~$ apt-cache show evince
Package: evince
[…]
Version: 2.30.1-3ubuntu1
Depends: libatk1.0-0 (= 1.29.3), libc6
Setting the task to In Progress then, Thanks Didier.
** Changed in: evince (Ubuntu)
Status: New = In Progress
--
Mavericks Evince doesn't start
https://bugs.launchpad.net/bugs/589194
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Also evince-gtk should depend on libevdocument2. It wont start woithout
it, with the same erro message (no backends found).
--
Mavericks Evince doesn't start
https://bugs.launchpad.net/bugs/589194
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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?
--
Mavericks Evince doesn't start
https://bugs.launchpad.net/bugs/589194
You received this bug notification because you are a member of
Hm. That's weird.
mue...@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
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/49606523/Dependencies.txt
** Attachment added: KernLog.txt
http://launchpadlibrarian.net/49606524/KernLog.txt
** Attachment added: ProcEnviron.txt
http://launchpadlibrarian.net/49606525/ProcEnviron.txt
** Attachment
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.
** Changed in:
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:
mue...@xbox:/tmp$ dpkg --listfiles evince | grep
14 matches
Mail list logo
