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 393650 - crash in gThumb Image Viewer: connected the digi camer...
crash in gThumb Image Viewer: connected the digi camer...
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-01-06 20:05 UTC by pali.spacek
Modified: 2007-01-06 21:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description pali.spacek 2007-01-06 20:05:03 UTC 
What were you doing when the application crashed?
connected the digi camera
one instance of gthumb was already opened


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2869.fc6 #1 SMP Wed Dec 20 14:51:34 EST 2006 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 1107615744 vsize: 1107615744 resident: 29503488 share: 7671808 rss: 29503488 rss_rlim: -1
CPU usage: start_time: 1168039024 rtime: 4039 utime: 3820 stime: 219 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496441696 (LWP 7402)]
[New Thread 1262557504 (LWP 13838)]
[New Thread 1252067648 (LWP 13837)]
[New Thread 1241577792 (LWP 13836)]
[New Thread 1210108224 (LWP 13835)]
[New Thread 1220598080 (LWP 13834)]
[New Thread 1231087936 (LWP 13833)]
[New Thread 1199618368 (LWP 11499)]
[New Thread 1189128512 (LWP 11498)]
[New Thread 1178638656 (LWP 11497)]
[New Thread 1168148800 (LWP 11496)]
[New Thread 1147169088 (LWP 11495)]
[New Thread 1157658944 (LWP 11494)]
[New Thread 1136679232 (LWP 7411)]
[New Thread 1126189376 (LWP 7410)]
[New Thread 1115699520 (LWP 7409)]
[New Thread 1105209664 (LWP 7408)]
[New Thread 1094719808 (LWP 7407)]
[New Thread 1084229952 (LWP 7405)]
(no debugging symbols found)
0x00000039e2a0d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 99972

Thread 1 (Thread 46912496441696 (LWP 7402))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gth_location_new
  • #4 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #5 g_signal_override_class_closure
    from /lib64/libgobject-2.0.so.0
  • #6 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #7 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #8 gnome_vfs_volume_monitor_emit_pre_unmount
    from /usr/lib64/libgnomevfs-2.so.0
  • #9 gnome_vfs_volume_monitor_client_shutdown_private
    from /usr/lib64/libgnomevfs-2.so.0
  • #10 dbus_connection_dispatch
    from /lib64/libdbus-1.so.3
  • #11 dbus_server_setup_with_g_main
    from /usr/lib64/libdbus-glib-1.so.2
  • #12 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #13 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #15 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #16 main
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


Michael Chudobiak





          2007-01-06 21:51:53 UTC
        



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 is fixed in 2.8.x and 2.9.x, available at
http://ftp.gnome.org/pub/gnome/sources/gthumb/2.8/ and
http://ftp.gnome.org/pub/gnome/sources/gthumb/2.9/.

*** This bug has been marked as a duplicate of 356623 ***