GNOME Bugzilla – Bug 499251
crash in gThumb Image Viewer: Deleting partially full ...
Last modified: 2007-11-23 21:13:19 UTC
What were you doing when the application crashed? Deleting partially full folders while many other processes are running, cpu capacity at near 100%, but plenty of ram available. 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: Bluecurve-Lime Icon Theme: Crux Memory status: size: 92356608 vsize: 92356608 resident: 38002688 share: 20545536 rss: 38002688 rss_rlim: 4294967295 CPU usage: start_time: 1195851525 rtime: 4461 utime: 3918 stime: 543 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 -1208776992 (LWP 27990)] [New Thread -1248191600 (LWP 28151)] [New Thread -1277256816 (LWP 28002)] [New Thread -1276728432 (LWP 28001)] [New Thread -1276200048 (LWP 28000)] [New Thread -1223222384 (LWP 27994)] [New Thread -1222694000 (LWP 27993)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 179401
Thread 1 (Thread -1208776992 (LWP 27990))
----------- .xsession-errors (548 sec old) --------------------- Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. [mpeg4 @ 0x11111a4]header damaged [mpeg4 @ 0x11111a4]header damaged [mpeg4 @ 0x11111a4]header damaged [mpeg4 @ 0x11111a4]header damaged [mpeg4 @ 0x11111a4]header damaged [mpeg4 @ 0x11111a4]header damaged [mpeg4 @ 0x11111a4]header damaged [mpeg4 @ 0x11111a4]header damaged [mpeg4 @ 0x11111a4]header damaged Some deprecated features have been used. Set the environment variable GUILE_WARN_DEPRECATED to "detailed" and rerun the program to get more information. Set it to "no" to suppress this message. --------------------------------------------------
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 (2.10.8). *** This bug has been marked as a duplicate of 492169 ***