GNOME Bugzilla – Bug 560755
crash in Document Viewer: I'm viewing pdf file
Last modified: 2008-11-14 19:33:17 UTC
Version: 2.22.2 What were you doing when the application crashed? I'm viewing pdf file Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 545439744 vsize: 545439744 resident: 264531968 share: 16601088 rss: 264531968 rss_rlim: 18446744073709551615 CPU usage: start_time: 1226643200 rtime: 3793 utime: 3353 stime: 440 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2ab9eccc8780 (LWP 25087)] [New Thread 0x40800950 (LWP 25088)] (no debugging symbols found) 0x00002ab9e8357d96 in poll () from /lib/libc.so.6
+ Trace 209765
Thread 2 (Thread 0x40800950 (LWP 25088))
----------- .xsession-errors (175369 sec old) --------------------- Error (2279): Dictionary key must be a name object Error (2279): Dictionary key must be a name object Error (2279): Dictionary key must be a name object Error (2282): Illegal character '>' Error (2282): Dictionary key must be a name object Error (2282): Dictionary key must be a name object Error (2284): Dictionary key must be a name object Error (2284): Dictionary key must be a name object Error (2286): Dictionary key must be a name object Error (2286): Dictionary key must be a name object Error (2286): Dictionary key must be a name object Error (2286): Illegal character '>' Error (2286): Dictionary key must be a name object Error (2288): Dictionary key must be a name object ...Too much output, ignoring rest... --------------------------------------------------
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 536482 ***