GNOME Bugzilla – Bug 520070
crash in Document Viewer: I was opening a dvi docu...
Last modified: 2008-04-18 18:19:38 UTC
Version: 2.21.91 What were you doing when the application crashed? I was opening a dvi document, when there was another pdf (not same) document opened. Distribution: Gentoo Base System release 2.0.0_rc6-r1 Gnome Release: 2.21.92 2008-02-27 (Gentoo) BugBuddy Version: 2.20.1 System: Linux 2.6.25-rc3-00081-g7704a8b #11 SMP PREEMPT Thu Feb 28 09:43:44 EET 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 418947072 vsize: 418947072 resident: 112025600 share: 19779584 rss: 112025600 rss_rlim: 18446744073709551615 CPU usage: start_time: 1204542634 rtime: 1369 utime: 1278 stime: 91 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x7fc3cbcdd700 (LWP 12361)] [New Thread 0x40831950 (LWP 12362)] 0x00007fc3c8c76dd4 in __lll_lock_wait () from /lib/libpthread.so.0
+ Trace 191139
Thread 2 (Thread 0x40831950 (LWP 12362))
----------- .xsession-errors (5275 sec old) --------------------- Error (52182): Illegal character '>' Error (52192): Missing 'endstream' Error (48160): Illegal character '>' Error (48170): Missing 'endstream' Error (51287): Illegal character '>' Error (51297): Missing 'endstream' Error (52948): Illegal character '>' Error (52958): Missing 'endstream' Error (53506): Illegal character '>' Error (53516): Missing 'endstream' Error (48160): Illegal character '>' Error (48170): Missing 'endstream' Error (57053): Illegal character '>' Error (57063): Missing 'endstream' ...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 519679 ***