GNOME Bugzilla – Bug 372843
crash in Document Viewer: I've been printing the l...
Last modified: 2007-04-24 02:28:07 UTC
Version: 0.6.1 What were you doing when the application crashed? I've been printing the last page of the document before closing the window. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 75010048 vsize: 0 resident: 75010048 share: 0 rss: 45568000 rss_rlim: 0 CPU usage: start_time: 1163059687 rtime: 0 utime: 3270 stime: 0 cutime:3040 cstime: 0 timeout: 230 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evince' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1229343056 (LWP 5701)] [New Thread -1230824544 (LWP 5703)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 84654
Thread 1 (Thread -1229343056 (LWP 5701))
Thanks for the bug report. Unfortunately it lacks some information that may help us in finding the cause of the bug. Can you, if possible, attach the file causing the crash? Also this may be a Poppler Bug (the backend used by Evince to render PDF), could you please supply the poppler version and type? You can find it in the Help->About menu in Evince. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Created attachment 76264 [details] the pdf document, which caused the crash selecting the url on top ("www.stromeffizienz.de") caused evince to crash.
the poppler version is 0.5.4
Here's another backtrace: Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1229547856 (LWP 8448)] [New Thread -1231029344 (LWP 8450)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 84725
Thread 1 (Thread -1229547856 (LWP 8448))
first (bad) stacktrace is a duplicate of bug 362110 which was marked as a dup of bug 350108 which was marked as a dup of
The url on the top left of the first page of the PDF attached in comment #2 is not clickable over here. Are you sure the crash is related to clicking that region of the page?
When I try to _select_ the URL (yes, it is not clickable) so I an copy it to the location field of my browser, evince crashes.
I wonder, whether I should open a new poppler bug report since https://bugs.freedesktop.org/show_bug.cgi?id=7793 which seems to be a bug in poppler_page_render_selection() as well, should already be fixed in my poppler version (0.5.4).
*** Bug 377514 has been marked as a duplicate of this bug. ***
https://bugs.freedesktop.org/show_bug.cgi?id=7793 looks totally unrelated to this problem No crash here with evince 0.6.1 / poppler 0.5.4 when selecting the URL
Poppler issue it seems.
Why has that bug been marked fixed? Ubuntu bug about that: https://launchpad.net/ubuntu/+source/evince/+bug/81534 That's still happening with evince 0.7.1 on http://librarian.launchpad.net/5855158/PC-BSD.pdf, reopening
I can't reproduce it with evince svn trunk and poppler cvs head. Could you provide a new backtrace with evince 0.7.1, please?
Hmm sorry, bugbuddy automatically made a new issue: http://bugzilla.gnome.org/show_bug.cgi?id=401042
hey Pascal, unfortunately, the new trace is totally useless. can you retry and copy and paste the trace into this report?
How do I get a better trace?
no crash here with evince 0.7.1 Using poppler 0.5.4 (cairo) pristine gnome svn build
I was using Evince 0.7.1 with Poppler 0.5.4, but then with the splash backend instead of the cairo backend.
I can confirm, that poppler with splash backend crashes.
*** Bug 405204 has been marked as a duplicate of this bug. ***
Forwarded to poppler bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=10402 Thanks you all for your help.
*** Bug 426895 has been marked as a duplicate of this bug. ***
*** Bug 428066 has been marked as a duplicate of this bug. ***
*** Bug 432785 has been marked as a duplicate of this bug. ***