GNOME Bugzilla – Bug 494423
crash in Image Viewer: 將視窗放到最大
Last modified: 2007-11-07 17:55:31 UTC
Version: 2.18.2 What were you doing when the application crashed? 將視窗放到最大 Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 111755264 vsize: 111755264 resident: 50024448 share: 19333120 rss: 50024448 rss_rlim: 4294967295 CPU usage: start_time: 1194400470 rtime: 757 utime: 712 stime: 45 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/eog' (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 -1208559904 (LWP 15848)] [New Thread -1262134384 (LWP 15851)] [New Thread -1212171376 (LWP 15849)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 175922
Thread 1 (Thread -1208559904 (LWP 15848))
----------- .xsession-errors (8 sec old) --------------------- (file-roller:14584): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (file-roller:14584): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (file-roller:14584): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (file-roller:14584): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (eog:15848): Eog-CRITICAL **: eog_image_cache_add: assertion `EOG_IS_IMAGE_CACHE (cache)' failed (eog:15848): Eog-CRITICAL **: eog_image_list_iter_valid: assertion `EOG_IS_IMAGE_LIST (list)' failed (eog:15848): Eog-CRITICAL **: eog_image_list_iter_valid: assertion `EOG_IS_IMAGE_LIST (list)' failed (bug-buddy:15856): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: 第 1 行第 40 個字發生錯誤:元素‘b’已關閉,但開啟中的元素是‘span’ --------------------------------------------------
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 version 2.20. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 320206 ***