GNOME Bugzilla – Bug 493013
crash in Image Viewer:
Last modified: 2007-11-03 12:34:21 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-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 108736512 vsize: 108736512 resident: 55107584 share: 18305024 rss: 55107584 rss_rlim: 4294967295 CPU usage: start_time: 1194123440 rtime: 1260 utime: 1133 stime: 127 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 -1208273184 (LWP 2741)] [New Thread -1256281200 (LWP 2745)] [New Thread -1211987056 (LWP 2743)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 174833
Thread 1 (Thread -1208273184 (LWP 2741))
----------- .xsession-errors (154 sec old) --------------------- Starting SCIM as daemon ... SCIM has been successfully launched. Smart Common Input Method 1.4.5 --- Hash table keys for warning below: --> file:///home/saikun-kor (nautilus:2672): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) ** (nautilus:2573): WARNING **: mime 형식 "x-directory/smb-share"(파일은 "Datas")에 대한 설명을 찾을 수 없습니다, gnome-vfs 메일링 리스트로 알려주십시오. connection_message_func(): Callback CALLBACK: fill-authentication!!! (nautilus:2573): Gtk-WARNING **: Invalid input string --------------------------------------------------
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 ***