After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 472864 - crash in gThumb Image Viewer:
crash in gThumb Image Viewer:
Status: RESOLVED DUPLICATE of bug 356623
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2007-09-02 15:55 UTC by andrew
Modified: 2007-09-04 12:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description andrew 2007-09-02 15:55:10 UTC
What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.21-0182.rt21.3.fc6.ccrmart #1 SMP PREEMPT RT Thu Jul 19 14:08:13 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Enabled

Memory status: size: 237748224 vsize: 0 resident: 237748224 share: 0 rss: 75751424 rss_rlim: 0
CPU usage: start_time: 1188748038 rtime: 0 utime: 146 stime: 0 cutime:131 cstime: 0 timeout: 15 it_real_value: 0 frequency: 0

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 -1208449328 (LWP 8224)]
[New Thread -1358967920 (LWP 8234)]
[New Thread -1350575216 (LWP 8233)]
[New Thread -1342182512 (LWP 8232)]
[New Thread -1333789808 (LWP 8231)]
[New Thread -1306301552 (LWP 8228)]
[New Thread -1240220784 (LWP 8227)]
0xb7fad410 in __kernel_vsyscall ()

Thread 1 (Thread -1208449328 (LWP 8224))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gth_location_new
  • #5 IA__g_cclosure_marshal_VOID__OBJECT
    at gmarshal.c line 636
  • #6 IA__g_closure_invoke
    at gclosure.c line 490
  • #7 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #8 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #9 IA__g_signal_emit
    at gsignal.c line 2243
  • #10 _gnome_vfs_volume_monitor_unmounted
    at gnome-vfs-volume-monitor.c line 784
  • #11 dbus_filter_func
    at gnome-vfs-volume-monitor-client.c line 343
  • #12 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #13 dbus_server_setup_with_g_main
    from /usr/lib/libdbus-glib-1.so.2
  • #14 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #15 g_main_context_iterate
    at gmain.c line 2677
  • #16 IA__g_main_loop_run
    at gmain.c line 2881
  • #17 IA__gtk_main
    at gtkmain.c line 1154
  • #18 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
package is installed and that the service is running.
** Message: Failed to close thumbnail pixbuf loader for /home/andrew/fairtradelogo2.gif: Unrecognised image file format
** Message: Failed to close thumbnail pixbuf loader for /home/andrew/fairtradelogo2.gif: Unrecognised image file format
GTK Accessibility Module initialized
Bonobo accessibility support initialized
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
** (bug-buddy:8408): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-09-04 12:14:02 UTC
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 356623 ***