GNOME Bugzilla – Bug 501516
crash in Image Viewer:
Last modified: 2007-12-12 13:22:41 UTC
Version: 2.18.2 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (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: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 89350144 vsize: 89350144 resident: 46141440 share: 18964480 rss: 46141440 rss_rlim: 4294967295 CPU usage: start_time: 1196774025 rtime: 521 utime: 280 stime: 241 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 -1208289568 (LWP 6669)] [New Thread -1258980464 (LWP 6671)] [New Thread -1210389616 (LWP 6670)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 180706
Thread 3 (Thread -1210389616 (LWP 6670))
----------- .xsession-errors (6078 sec old) --------------------- --- Hash table keys for warning below: --> file:///home/mahesh (nautilus:5418): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) kbuildsycoca running... Reusing existing ksycoca Initializing nautilus-open-terminal extension Initializing nautilus-search-tool extension Initializing nautilus-image-converter extension Launched ok, pid = 5623 ICE default IO error handler doing an exit(), pid = 5619, errno = 0 error getting update info: Cannot retrieve repository metadata (repomd.xml) for repository: skype. Please verify its path and try again Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4800058 (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
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 320206 ***