Bug 515690 – crash in gThumb Image Viewer: Renaming a directory

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 515690 - crash in gThumb Image Viewer: Renaming a directory


Summary:	crash in gThumb Image Viewer: Renaming a directory


Status:	RESOLVED DUPLICATE of bug 492169

Product:	gthumb
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Paolo Bacchilega
QA Contact:	Paolo Bacchilega

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-02-11 05:54 UTC by rwuest
Modified:	2008-04-11 14:19 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description rwuest 2008-02-11 05:54:55 UTC

What were you doing when the application crashed?
Renaming a directory


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.14-64.fc7 #1 SMP Sun Jan 20 22:20:19 EST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 536363008 vsize: 536363008 resident: 113291264 share: 13869056 rss: 113291264 rss_rlim: 18446744073709551615
CPU usage: start_time: 1202708886 rtime: 4561 utime: 4324 stime: 237 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496458112 (LWP 16660)]
[New Thread 1086871888 (LWP 16668)]
[New Thread 1086343504 (LWP 16667)]
[New Thread 1085815120 (LWP 16666)]
[New Thread 1074796880 (LWP 16664)]
[New Thread 1074268496 (LWP 16663)]
(no debugging symbols found)
0x0000003e0340d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 188792

Thread 1 (Thread 46912496458112 (LWP 16660))

#0 waitpid
from /lib64/libpthread.so.0
#1 uricmp
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 ??
#4 ??
#5 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#6 uricmp
from /lib64/libgobject-2.0.so.0
#7 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#8 g_signal_emit
from /lib64/libgobject-2.0.so.0
#9 ??
#10 gth_browser_activate_action_edit_dir_rename
#11 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#12 uricmp
from /lib64/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#14 g_signal_emit
from /lib64/libgobject-2.0.so.0
#15 uricmp
from /usr/lib64/libgtk-x11-2.0.so.0
#16 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#17 uricmp
from /lib64/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#19 g_signal_emit
from /lib64/libgobject-2.0.so.0
#20 gtk_widget_activate
from /usr/lib64/libgtk-x11-2.0.so.0
#21 gtk_menu_shell_activate_item
from /usr/lib64/libgtk-x11-2.0.so.0
#22 uricmp
from /usr/lib64/libgtk-x11-2.0.so.0
#23 uricmp
from /usr/lib64/libgtk-x11-2.0.so.0
#24 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#25 uricmp
from /lib64/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#27 g_signal_emit
from /lib64/libgobject-2.0.so.0
#28 uricmp
from /usr/lib64/libgtk-x11-2.0.so.0
#29 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#30 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#31 uricmp
from /usr/lib64/libgdk-x11-2.0.so.0
#32 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#33 uricmp
from /lib64/libglib-2.0.so.0
#34 g_main_loop_run
from /lib64/libglib-2.0.so.0
#35 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#36 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors ---------------------
DCOP Cleaning up dead connections.
ScimInputContextPlugin()
~ScimInputContextPlugin()
ScimInputContextPlugin()
QFile::open: No file name specified
QFile::open: No file name specified
~ScimInputContextPlugin()
Fontconfig warning: no <cachedir> elements found. Check configuration.
Fontconfig warning: adding <cachedir>/var/cache/fontconfig</cachedir>
Fontconfig warning: adding <cachedir>~/.fontconfig</cachedir>
Fontconfig warning: no <cachedir> elements found. Check configuration.
Fontconfig warning: adding <cachedir>/var/cache/fontconfig</cachedir>
Fontconfig warning: adding <cachedir>~/.fontconfig</cachedir>
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff7bbfd000
--------------------------------------------------

Comment 1 Michael Chudobiak 2008-04-11 14:19:37 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 ***