GNOME Bugzilla – Bug 512814
crash in Document Viewer: just aggresively klickin...
Last modified: 2008-01-29 15:12:14 UTC
Version: 2.20.2 What were you doing when the application crashed? just aggresively klicking on the presentation Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 82513920 vsize: 82513920 resident: 49557504 share: 12988416 rss: 49557504 rss_rlim: 4294967295 CPU usage: start_time: 1201622318 rtime: 1402 utime: 1298 stime: 104 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 0xb6ac06c0 (LWP 16614)] [New Thread 0xb674bb90 (LWP 16615)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187207
Thread 1 (Thread 0xb6ac06c0 (LWP 16614))
----------- .xsession-errors (7453 sec old) --------------------- ** gg_watch_fd(0x8560088); // gg_watch_fd() GG_STATE_CONNECTED ** gg_watch_fd_connected(0x8560088, 0x86be538); ** gg_recv_packet(0x8560088); // gg_recv_packet() header recv(9,0xbfa36e54,8) = 8 // gg_recv_packet() body recv(9,0x86907a0,58) = 58 // gg_recv_packet(0f) 0f 00 00 00 3a 00 00 00 d4 e9 41 10 05 00 00 00 00 00 00 24 00 00 67 6d 61 69 6c 20 6a 65 73 74 20 7a 6c 79 2c 20 70 61 20 70 61 20 2f 2f 6b 77 69 74 65 6b 40 6a 61 62 62 65 72 2 // gg_watch_fd_connected() received a status change ** gg_event_free(0x86be538); ** gg_watch_fd(0x8560088); // gg_watch_fd() GG_STATE_CONNECTED ** gg_watch_fd_connected(0x8560088, 0x86be388); ** gg_recv_packet(0x8560088); ...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 316907 ***