GNOME Bugzilla – Bug 527619
crash in Document Viewer: Opening a PDF
Last modified: 2008-04-12 00:32:52 UTC
Version: 2.20.2 What were you doing when the application crashed? Opening a PDF Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-2-686-bigmem #1 SMP Fri Aug 31 01:40:59 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: crystalsvg Memory status: size: 63721472 vsize: 63721472 resident: 40783872 share: 11890688 rss: 40783872 rss_rlim: 4294967295 CPU usage: start_time: 1207948706 rtime: 60 utime: 54 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb69bfaa0 (LWP 21456)] [New Thread 0xb67bab90 (LWP 21457)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 194987
Thread 1 (Thread 0xb69bfaa0 (LWP 21456))
----------- .xsession-errors --------------------- (evolution:4950): gtkhtml-WARNING **: Cannot create spell dictionary instance (iid:OAFIID:GNOME_Spell_Dictionary:0.3) (evolution:4950): Bonobo-WARNING **: Activation exception 'Failed to activate 'OAFIID:GNOME_Spell_Control:0.3'' (evolution:4950): evolution-shell-CRITICAL **: e_shell_window_peek_shell: assertion `E_IS_SHELL_WINDOW (window)' failed (evolution:4950): evolution-shell-CRITICAL **: e_shell_window_peek_shell: assertion `E_IS_SHELL_WINDOW (window)' failed (evolution:4950): evolution-shell-CRITICAL **: e_shell_window_peek_shell: assertion `E_IS_SHELL_WINDOW (window)' failed (evolution:4950): evolution-shell-CRITICAL **: e_shell_window_peek_shell: assertion `E_IS_SHELL_WINDOW (window)' failed (evolution:4950): evolution-shell-CRITICAL **: e_shell_window_peek_shell: assertion `E_IS_SHELL_WINDOW (window)' failed Error: Bad named destination value --------------------------------------------------
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 415714 ***