GNOME Bugzilla – Bug 487412
crash in gThumb Image Viewer: When I was changing the ...
Last modified: 2007-10-17 11:42:37 UTC
What were you doing when the application crashed? When I was changing the folder name, it 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.22.7-85.fc7 #1 SMP Fri Sep 21 19:53:05 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 130535424 vsize: 130535424 resident: 41574400 share: 28819456 rss: 41574400 rss_rlim: 4294967295 CPU usage: start_time: 1192608021 rtime: 2576 utime: 2318 stime: 258 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gthumb' (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 -1209112864 (LWP 8077)] [New Thread -1290359920 (LWP 8088)] [New Thread -1289831536 (LWP 8087)] [New Thread -1289303152 (LWP 8086)] [New Thread -1278284912 (LWP 8083)] [New Thread -1277756528 (LWP 8082)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 170772
Thread 1 (Thread -1209112864 (LWP 8077))
----------- .xsession-errors (969 sec old) --------------------- Currently active devices: lo eth0 kbuildsycoca running... Reusing existing ksycoca Launched ok, pid = 7805 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3a0000a LibClamAV Warning: ************************************************** LibClamAV Warning: *** The virus database is older than 7 days. *** LibClamAV Warning: *** Please update it IMMEDIATELY! *** LibClamAV Warning: ************************************************** LibClamAV Error: cli_loaddb(): No supported database files found in /var/lib/clamav/daily.inc Window manager warning: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp --------------------------------------------------
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 470493 ***