GNOME Bugzilla – Bug 540176
crash in Document Viewer: i was sending printing c...
Last modified: 2008-06-25 18:30:13 UTC
Version: 2.20.2 What were you doing when the application crashed? i was sending printing command Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: gnome Memory status: size: 62173184 vsize: 62173184 resident: 39239680 share: 14446592 rss: 39239680 rss_rlim: 4294967295 CPU usage: start_time: 1214409039 rtime: 1781 utime: 1685 stime: 96 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 0xb6a1c940 (LWP 3031)] [New Thread 0xb67f1b90 (LWP 3032)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 201374
Thread 2 (Thread 0xb67f1b90 (LWP 3032))
----------- .xsession-errors (58 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/debian:/tmp/.ICE-unix/2886 ** Message: another SSH agent is running at: /tmp/ssh-IiPzzF2886/agent.2886 ** (gnome-settings-daemon:2948): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No such file or directory Avviso del window manager: Lettura del file della sessione /home/rici/.metacity/sessions/default0.ms fallita: Failed to open file '/home/rici/.metacity/sessions/default0.ms': No such file or directory seahorse nautilus module initialized Initializing gnome-mount extension Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1c00003 (Visualizza) Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Xlib: unexpected async reply (sequence 0x65c0)! --------------------------------------------------
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 524762 ***