GNOME Bugzilla – Bug 635815
crash in Document Viewer:
Last modified: 2010-11-25 23:24:22 UTC
Version: 2.30.3 What were you doing when the application crashed? Distribution: Unknown Gnome Release: 2.30.2 2010-08-01 (GNOME.Org) BugBuddy Version: 2.30.0 System: Linux 2.6.34.3 #2 SMP Thu Aug 12 13:41:37 EDT 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10701000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 147320832 vsize: 147320832 resident: 18558976 share: 11767808 rss: 18558976 rss_rlim: 18446744073709551615 CPU usage: start_time: 1290725968 rtime: 218 utime: 174 stime: 44 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/local/bin/evince' [Thread debugging using libthread_db enabled] [New Thread 0xb02ffb90 (LWP 11200)] [New Thread 0xb0c6fb90 (LWP 11199)] 0xb770d424 in __kernel_vsyscall ()
+ Trace 224845
Thread 1 (Thread 0xb6749700 (LWP 11198))
Inferior 1 [process 11198] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors --------------------- ** (evince:11198): WARNING **: DjvuLibre error: DjVuFile.cpp:2252 ** (evince:11198): WARNING **: DjvuLibre error: DjVuFile.cpp:2252 ** (evince:11198): WARNING **: DjvuLibre error: DjVuFile.cpp:2252 ** (evince:11198): WARNING **: DjvuLibre error: DjVuFile.cpp:2252 ** (evince:11198): WARNING **: DjvuLibre error: DjVuFile.cpp:2252 ** (evince:11198): WARNING **: DjvuLibre error: DjVuFile.cpp:2252 ** EvinceDocument:ERROR:ev-document-misc.c:58:ev_document_misc_get_thumbnail_frame: assertion failed: (width_r >= 0 && height_r >= 0) ** (bug-buddy:11203): WARNING **: Couldn't load /usr/local/share/applications/openoffice-qstart.desktop: No such file or directory --------------------------------------------------
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 bug 594408 ***