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 487729 - crash in gThumb Image Viewer:
crash in gThumb Image Viewer:
Status: RESOLVED DUPLICATE of bug 470493
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2007-10-18 01:18 UTC by radeighan
Modified: 2007-10-18 11:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description radeighan 2007-10-18 01:18:38 UTC
What were you doing when the application crashed?



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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 152977408 vsize: 152977408 resident: 83832832 share: 20434944 rss: 83832832 rss_rlim: 4294967295
CPU usage: start_time: 1192589292 rtime: 11231 utime: 10390 stime: 841 cutime:0 cstime: 1 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 -1208457504 (LWP 12681)]
[New Thread -1230976112 (LWP 15584)]
[New Thread -1230447728 (LWP 15583)]
[New Thread -1229919344 (LWP 15582)]
[New Thread -1229390960 (LWP 15574)]
[New Thread -1228862576 (LWP 15573)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208457504 (LWP 12681))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 ??
  • #6 gthumb_marshal_VOID__STRING_STRING
    from /usr/lib/gthumb/libgthumb.so
  • #7 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #8 ??
    from /lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #11 gth_monitor_notify_directory_renamed
  • #12 all_windows_notify_directory_rename
  • #13 ??
  • #14 gth_browser_activate_action_edit_dir_rename
  • #15 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_action_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #23 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #24 ??
    from /lib/libgobject-2.0.so.0
  • #25 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #26 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #27 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 ??
    from /lib/libgobject-2.0.so.0
  • #33 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #34 ??
    from /lib/libgobject-2.0.so.0
  • #35 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #36 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #37 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #41 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #42 ??
    from /lib/libglib-2.0.so.0
  • #43 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #44 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (12628 sec old) ---------------------
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400003 (Deinterlac)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400003 (Despeckle)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400003 (Save as JP)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400003 (Save as JP)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400003 (Save as JP)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
CalDAV Eplugin starting up ...
** (evolution:15465): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:15465): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-10-18 11:56:25 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 bug has been marked as a duplicate of 470493 ***