GNOME Bugzilla – Bug 487390
crash in gThumb Image Viewer: Deleting an image from f...
Last modified: 2007-10-17 11:43:14 UTC
What were you doing when the application crashed? Deleting an image from fullscreen mode 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: Fedora Memory status: size: 119123968 vsize: 119123968 resident: 74833920 share: 19640320 rss: 74833920 rss_rlim: 4294967295 CPU usage: start_time: 1192601305 rtime: 4037 utime: 3806 stime: 231 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 -1208654112 (LWP 3320)] [New Thread -1235518576 (LWP 3446)] [New Thread -1254106224 (LWP 3445)] [New Thread -1253577840 (LWP 3444)] [New Thread -1253049456 (LWP 3443)] [New Thread -1246008432 (LWP 3442)] [New Thread -1234183280 (LWP 3329)] [New Thread -1233654896 (LWP 3328)] [New Thread -1233126512 (LWP 3327)] [New Thread -1220543600 (LWP 3324)] [New Thread -1220015216 (LWP 3323)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 170755
Thread 1 (Thread -1208654112 (LWP 3320))
----------- .xsession-errors (51 sec old) --------------------- localuser:polo being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3080 (gnome-help:3399): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed --------------------------------------------------
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 in gthumb 2.10.7. *** This bug has been marked as a duplicate of 485721 ***