GNOME Bugzilla – Bug 519735
crash in Document Viewer: While reading file "http...
Last modified: 2008-03-02 12:51:25 UTC
Version: 2.20.2 What were you doing when the application crashed? While reading file "http://www.hs-bremen.de/Uploaded/Eintrag78119/Normen_im_Schriftverkehr.pdf" and after pressing "ctrl+f", then escape, then "ctrl+p" (trying to open 'goto page'), and then after finally pressing "ctrl+g", the programm crashed (the focus was in the Contents section at that time) Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-486 #1 Sun Feb 10 19:36:16 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: Amaranth Memory status: size: 67497984 vsize: 67497984 resident: 45289472 share: 14872576 rss: 45289472 rss_rlim: 4294967295 CPU usage: start_time: 1204379857 rtime: 626 utime: 550 stime: 76 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b416c0 (LWP 13555)] [New Thread 0xb6972b90 (LWP 13556)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 190956
Thread 1 (Thread 0xb6b416c0 (LWP 13555))
----------- .xsession-errors (88 sec old) --------------------- Got modmask 0 Keymap changed! Regrabbing keys...Removing grab for 'F12' Got accel 65481, 0, 0 Got keycode 96 Got modmask 0 Keymap changed! Regrabbing keys...Removing grab for 'F12' Got accel 65481, 0, 0 Got keycode 96 Got modmask 0 Keymap changed! Regrabbing keys...Removing grab for 'F12' Got accel 65481, 0, 0 Got keycode 96 Got modmask 0 Fenstermanager-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4c00003 (Evince Dok) Fenstermanager-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
Could you please provide a stacktrace? Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance! (not closing bug because someone might try to reproduce it using the pdf file provided)
Not yet the stacktrace (I am reading the article you mentioned at the moment). To reproduce: It really looks like the mentioned pdf (again: http://www.hs-bremen.de/Uploaded/Eintrag78119/Normen_im_Schriftverkehr.pdf) is relevant. It seems to play no role where you look at in the document. It is enough to press <ctrl+p> to open the print dialog, then <escape>. Wait some moments, and crash. .... [now trying to get a symbol'd backtrace]
Created attachment 106375 [details] stacktrace containing debugging symbols this is a stacktrace containg debugging symbols for bug 519735
Many thanks for your report, i've found it to be a duplicate. Your help is really apprecciated. Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 460887 ***