GNOME Bugzilla – Bug 613087
crash in Document Viewer: trying to load a pdf fil...
Last modified: 2010-03-17 04:36:19 UTC
Version: 2.28.2 What were you doing when the application crashed? trying to load a pdf file i've just received. Distribution: Debian squeeze/sid Gnome Release: 2.28.2 2009-12-18 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10705000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 110546944 vsize: 110546944 resident: 35368960 share: 9977856 rss: 35368960 rss_rlim: 18446744073709551615 CPU usage: start_time: 1268121382 rtime: 5347 utime: 3845 stime: 1502 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' [Thread debugging using libthread_db enabled] [New Thread 0xb4a91b70 (LWP 15166)] [New Thread 0xb562eb70 (LWP 22907)] 0xb77b8424 in __kernel_vsyscall ()
+ Trace 220989
Thread 3 (Thread 0xb562eb70 (LWP 22907))
A debugging session is active. Inferior 1 [process 22905] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (591311 sec old) --------------------- (Pidgin:5381): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed (Pidgin:5381): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed (Pidgin:5381): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed (Pidgin:5381): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed (Pidgin:5381): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed (Pidgin:5381): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed (Pidgin:5381): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed ...Too much output, ignoring rest... --------------------------------------------------
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 bug 611144 ***