GNOME Bugzilla – Bug 567768
crash in Document Viewer: selection
Last modified: 2009-01-15 02:07:15 UTC
Version: 2.22.2 What were you doing when the application crashed? selection Distribution: Debian 5.0 Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-etchnhalf.1-686 #1 SMP Mon Oct 13 07:27:05 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 63152128 vsize: 63152128 resident: 41594880 share: 12115968 rss: 41594880 rss_rlim: 4294967295 CPU usage: start_time: 1231953850 rtime: 792 utime: 760 stime: 32 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 0xb6b0c700 (LWP 31669)] [New Thread 0xb69b1b90 (LWP 31670)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 211553
Thread 1 (Thread 0xb6b0c700 (LWP 31669))
----------- .xsession-errors --------------------- (evolution:4019): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed (evolution:4019): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed (evolution:4019): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed (evolution:4019): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed (evolution:4019): evolution-shell-CRITICAL **: e_shell_window_peek_shell: assertion `E_IS_SHELL_WINDOW (window)' failed bbdb: Buddy list has changed since last sync. bbdb: Buddy list has changed since last sync. (evolution:4019): evolution-shell-CRITICAL **: e_shell_window_peek_shell: assertion `E_IS_SHELL_WINDOW (window)' failed Cannot access memory at address 0x4 Cannot access memory at address 0x4 --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 528484 ***