GNOME Bugzilla – Bug 317294
Evince crashes when copying text after switching back from presentation mode
Last modified: 2008-01-31 13:45:51 UTC
Steps to reproduce: 1. Download http://media.nextangle.com/rails/rails.pdf 2. Open the downloaded file in evince and go to page 2. 3. Press F5 to switch to presentation mode. 4. Highlight the text "blocks give...end" 5. Press F5 to switch to windows mode. 6. Highlight the text "blocks give...end" 7. Go to Step 3. Stack trace: 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) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1228417344 (LWP 8916)] [New Thread -1229800528 (LWP 8917)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 63211
Thread 2 (Thread -1229800528 (LWP 8917))
Other information: While it's hard to produce this bug in the first place, once you have the knack it is reproducible every time. Reproduced with both the splash and cairo versions of poppler 0.4.2 on Ubuntu Breezy and OpenSUSE 10 respectively. evince-0.4.0-0ubuntu3
Sometimes the following is printed on the terminal (but not always): Xlib: unexpected async reply (sequence 0x2f02)! Running with evince --sync doesn't stop the problems.
(evince:24743): GLib-CRITICAL **: g_str_has_suffix: assertion `str != NULL' failed ** ERROR **: file ev-pixbuf-cache.c: line 810 (ev_pixbuf_cache_get_selection_pixbuf): assertion failed: (job_info->rc) aborting... Terminated Using evince 0.4.0/poppler 0.4.2 (cairo) I get the following stack trace, which is probably a dup of my own bug (bug 317624): Backtrace was generated from '/opt/gnome2/bin/evince' Using host libthread_db library "/lib/tls/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1227987264 (LWP 24743)] [New Thread -1229386832 (LWP 24744)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 63291
Thread 1 (Thread -1227987264 (LWP 24743))
*** Bug 319100 has been marked as a duplicate of this bug. ***
*** Bug 319575 has been marked as a duplicate of this bug. ***
I can reproduce the problem here also with Poppler 0.4.2 and the same document.
Here is my backtrace for this bug, if it can help ... Backtrace was generated from '/usr/bin/evince' Using host libthread_db library "/lib/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1228577104 (LWP 12984)] [New Thread -1230849104 (LWP 12985)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 63813
Backtrace was generated from '/usr/bin/evince' Using host libthread_db library "/lib/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1228577104 (LWP 13019)] [New Thread -1230849104 (LWP 13020)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 63814
Here is mine : Starting program: /usr/bin/evince [Thread debugging using libthread_db enabled] [New Thread -1228147008 (LWP 5206)] [New Thread -1230410832 (LWP 5209)] [New Thread -1240253520 (LWP 5218)] [New Thread -1240622160 (LWP 5219)] *** attempt to put segment in horiz list twice *** attempt to put segment in horiz list twice Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1228147008 (LWP 5206)] 0xb73aee49 in SplashOutputDev::updateFont () from /usr/lib/libpoppler.so.0 (gdb) thread apply all bt
+ Trace 63822
Thread 1 (Thread -1228147008 (LWP 5206))
*** Bug 320351 has been marked as a duplicate of this bug. ***
*** Bug 321232 has been marked as a duplicate of this bug. ***
Hi all, actually it's the same poppler bug as 315552 and poppler bug 4402 has patch that should that problem. About stack trace with assertion of job_info->rc, it's fixed in CVS already, see bug 317624. *** This bug has been marked as a duplicate of 315552 ***
Ups, 315552 is already fixed, while this bug still stays, we are working on it in https://bugs.freedesktop.org/show_bug.cgi?id=4481
*** Bug 323932 has been marked as a duplicate of this bug. ***
*** Bug 324877 has been marked as a duplicate of this bug. ***
*** Bug 326016 has been marked as a duplicate of this bug. ***
*** Bug 326233 has been marked as a duplicate of this bug. ***
*** Bug 326950 has been marked as a duplicate of this bug. ***
*** Bug 328650 has been marked as a duplicate of this bug. ***
*** Bug 331043 has been marked as a duplicate of this bug. ***
*** Bug 332649 has been marked as a duplicate of this bug. ***
*** Bug 334207 has been marked as a duplicate of this bug. ***
*** Bug 336597 has been marked as a duplicate of this bug. ***
*** Bug 336701 has been marked as a duplicate of this bug. ***
*** Bug 338679 has been marked as a duplicate of this bug. ***
*** Bug 339155 has been marked as a duplicate of this bug. ***
*** Bug 339391 has been marked as a duplicate of this bug. ***
*** Bug 345152 has been marked as a duplicate of this bug. ***
*** Bug 348053 has been marked as a duplicate of this bug. ***
*** Bug 347442 has been marked as a duplicate of this bug. ***
*** Bug 345986 has been marked as a duplicate of this bug. ***
*** Bug 348267 has been marked as a duplicate of this bug. ***
*** Bug 349839 has been marked as a duplicate of this bug. ***
*** Bug 372104 has been marked as a duplicate of this bug. ***
*** Bug 421501 has been marked as a duplicate of this bug. ***
*** Bug 430004 has been marked as a duplicate of this bug. ***
*** Bug 433733 has been marked as a duplicate of this bug. ***
*** Bug 438295 has been marked as a duplicate of this bug. ***
*** Bug 438358 has been marked as a duplicate of this bug. ***
*** Bug 438930 has been marked as a duplicate of this bug. ***
*** Bug 440432 has been marked as a duplicate of this bug. ***
*** Bug 443923 has been marked as a duplicate of this bug. ***
*** Bug 444313 has been marked as a duplicate of this bug. ***
*** Bug 453304 has been marked as a duplicate of this bug. ***
*** Bug 484103 has been marked as a duplicate of this bug. ***
*** Bug 513456 has been marked as a duplicate of this bug. ***