GNOME Bugzilla – Bug 625941
crash in Document Viewer:
Last modified: 2010-08-04 07:08:10 UTC
Version: 2.30.3 What were you doing when the application crashed? Distribution: Debian squeeze/sid Gnome Release: 2.30.2 2010-07-17 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.32-5-686 #1 SMP Sat Jul 24 02:27:10 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 1417375744 vsize: 1417375744 resident: 15589376 share: 11563008 rss: 15589376 rss_rlim: 18446744073709551615 CPU usage: start_time: 1280231005 rtime: 7210 utime: 5563 stime: 1647 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 0xaede3b70 (LWP 11124)] [New Thread 0xae5e2b70 (LWP 2834)] 0xb7873424 in __kernel_vsyscall ()
+ Trace 223095
Thread 3 (Thread 0xae5e2b70 (LWP 2834))
A debugging session is active. Inferior 1 [process 2770] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (598309 sec old) --------------------- ** (gnome-volume-control-applet:2780): WARNING **: Connection failed, reconnecting... ** (gnome-volume-control-applet:2780): WARNING **: Connection failed, reconnecting... ** (gnome-volume-control-applet:2780): WARNING **: Connection failed, reconnecting... ** (gnome-volume-control-applet:2780): WARNING **: Connection failed, reconnecting... ** (gnome-volume-control-applet:2780): WARNING **: Connection failed, reconnecting... ** (gnome-volume-control-applet:2780): WARNING **: Connection failed, reconnecting... ** (gnome-volume-control-applet:2780): WARNING **: Connection failed, reconnecting... ...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 565758 ***