GNOME Bugzilla – Bug 486082
crash in Image Viewer: I am opening an image fr...
Last modified: 2007-10-13 10:26:08 UTC
Version: 2.18.2 What were you doing when the application crashed? I am opening an image from a network share and I am sure the image is modifying by a program at the same time. 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.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Fedora Memory status: size: 34603008 vsize: 34603008 resident: 7331840 share: 6176768 rss: 7331840 rss_rlim: 4294967295 CPU usage: start_time: 1192223247 rtime: 11 utime: 11 stime: 0 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 -1209166112 (LWP 10037)] [New Thread -1211266160 (LWP 10039)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 169777
Thread 2 (Thread -1211266160 (LWP 10039))
----------- .xsession-errors (1203 sec old) --------------------- CALLBACK: fill-authentication!!! --- Hash table keys for warning below: --> file:///home/skanduku (nautilus:9871): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) Xlib: unexpected async reply (sequence 0x8a)! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! Package eclipse-changelog - 1:2.3.4-1.fc7.i386 already installed and latest version Package eclipse-cdt - 1:3.1.2-3.fc7.i386 already installed and latest version --------------------------------------------------
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 357405 ***