GNOME Bugzilla – Bug 563484
crash in Document Viewer: intentar copiar document...
Last modified: 2008-12-08 11:13:48 UTC
Version: 2.22.2 What were you doing when the application crashed? intentar copiar documentació d'un cdrom a un altre document Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Thu Oct 9 15:18:09 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Mac_OS_X_Leopard_for_Debian_v1.4 Memory status: size: 66387968 vsize: 66387968 resident: 28041216 share: 12931072 rss: 28041216 rss_rlim: 4294967295 CPU usage: start_time: 1228588157 rtime: 45 utime: 40 stime: 5 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 0xb6b28700 (LWP 7253)] [New Thread 0xb6973b90 (LWP 7254)] 0xb7fd7424 in __kernel_vsyscall ()
+ Trace 210544
Thread 1 (Thread 0xb6b28700 (LWP 7253))
----------- .xsession-errors --------------------- Error (18673): Illegal character <d0> in hex string Error (18674): Illegal character <dc> in hex string Error (18675): Illegal character <a5> in hex string Error (18677): Illegal character <c2> in hex string Error (18678): Illegal character <f4> in hex string Error (18679): Illegal character <07> in hex string Error (18680): Illegal character <06> in hex string Error (18682): Illegal character <2f> in hex string Error (18683): Illegal character <84> in hex string Error (18684): Illegal character <72> in hex string Error (18686): Dictionary key must be a name object Error (18709): Dictionary key must be a name object Error (18722): Dictionary key must be a name object Error (18722): Illegal character ')' Error (18756): Illegal character ')' --------------------------------------------------
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 543942 ***