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 512151 - crash in gThumb Image Viewer: Trying to rename a folde...
crash in gThumb Image Viewer: Trying to rename a folde...
Status: RESOLVED DUPLICATE of bug 492169
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2008-01-26 00:19 UTC by margaret81
Modified: 2008-02-17 16:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description margaret81 2008-01-26 00:19:42 UTC
What were you doing when the application crashed?
Trying to rename a folder.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 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: 146313216 vsize: 146313216 resident: 81997824 share: 20254720 rss: 81997824 rss_rlim: 4294967295
CPU usage: start_time: 1201301925 rtime: 9402 utime: 8720 stime: 682 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 -1208785184 (LWP 2880)]
[New Thread -1235752048 (LWP 2888)]
[New Thread -1235223664 (LWP 2887)]
[New Thread -1233613936 (LWP 2886)]
[New Thread -1222595696 (LWP 2884)]
[New Thread -1222067312 (LWP 2883)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208785184 (LWP 2880))

  • #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 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #15 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #16 ??
    from /lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #19 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 gtk_action_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #22 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #23 ??
    from /lib/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #26 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 ??
    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 /lib/libgobject-2.0.so.0
  • #32 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #33 ??
    from /lib/libgobject-2.0.so.0
  • #34 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #35 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #36 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #40 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #41 ??
    from /lib/libglib-2.0.so.0
  • #42 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #43 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #44 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (81 sec old) ---------------------
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Max failures exceeded, exiting now
--------------------------------------------------
Comment 1 Michael Chudobiak 2008-02-17 16:54:43 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 492169 ***