GNOME Bugzilla – Bug 499305
crash in gThumb Image Viewer: deleting a .jpg file
Last modified: 2007-11-24 18:21:52 UTC
What were you doing when the application crashed? deleting a .jpg file 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: 142286848 vsize: 142286848 resident: 101322752 share: 21028864 rss: 101322752 rss_rlim: 4294967295 CPU usage: start_time: 1195880719 rtime: 677 utime: 632 stime: 45 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 -1209125152 (LWP 4846)] [New Thread -1233761392 (LWP 4863)] [New Thread -1246229616 (LWP 4861)] [New Thread -1245701232 (LWP 4860)] [New Thread -1245172848 (LWP 4859)] [New Thread -1244644464 (LWP 4858)] [New Thread -1232426096 (LWP 4852)] [New Thread -1231897712 (LWP 4851)] [New Thread -1231369328 (LWP 4850)] [New Thread -1230840944 (LWP 4849)] [New Thread -1230312560 (LWP 4848)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 179434
Thread 1 (Thread -1209125152 (LWP 4846))
----------- .xsession-errors (9 sec old) --------------------- Major opcode: 54 Minor opcode: 0 Resource id: 0x14034a1 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x14034a1 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x48 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x48 --------------------------------------------------
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 485721 ***