Bug 495617 – crash in gThumb Image Viewer: renamed folder

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 495617 - crash in gThumb Image Viewer: renamed folder


Summary:	crash in gThumb Image Viewer: renamed folder


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:	2007-11-10 15:45 UTC by dave
Modified:	2007-11-10 16:44 UTC

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

Description dave 2007-11-10 15:45:14 UTC

What were you doing when the application crashed?
renamed folder


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.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Bluecurve

Memory status: size: 173219840 vsize: 173219840 resident: 94056448 share: 33132544 rss: 94056448 rss_rlim: 4294967295
CPU usage: start_time: 1194708564 rtime: 1496 utime: 1383 stime: 113 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 -1208293664 (LWP 10903)]
[New Thread -1274549360 (LWP 10992)]
[New Thread -1274020976 (LWP 10991)]
[New Thread -1272132720 (LWP 10990)]
[New Thread -1261114480 (LWP 10979)]
[New Thread -1260586096 (LWP 10978)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 176816

Thread 1 (Thread -1208293664 (LWP 10903))

#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 (1062 sec old) ---------------------
	at com.aelitis.azureus.core.dht.transport.udp.impl.packethandler.DHTUDPPacketHandlerFactory.process(DHTUDPPacketHandlerFactory.java:176)
	at com.aelitis.azureus.core.dht.transport.udp.impl.packethandler.DHTUDPPacketNetworkHandler.process(DHTUDPPacketNetworkHandler.java:73)
	at com.aelitis.net.udp.uc.impl.PRUDPPacketHandlerImpl$4.runSupport(PRUDPPacketHandlerImpl.java:650)
	at org.gudy.azureus2.core3.util.AEThread.run(AEThread.java:69)
[plug] [Distributed DB] 
DEBUG::Sat Nov 10 15:12:47 GMT 2007::com.aelitis.azureus.plugins.dht.DHTPlugin$7::log::528:
  com.aelitis.azureus.core.dht.transport.DHTTransportException: Active write queue process thread limit exceeded
	at com.aelitis.azureus.core.dht.transport.udp.impl.DHTTransportUDPImpl.dataRequest(DHTTransportUDPImpl.java:2343)
	at com.aelitis.azureus.core.dht.transport.udp.impl.DHTTransportUDPImpl.process(DHTTransportUDPImpl.java:3355)
	at com.aelitis.azureus.core.dht.transport.udp.impl.packethandler.DHTUDPPacketHandler.receive(DHTUDPPacketHandler.java:271)
	at com.aelitis.azureus.core.dht.transport.udp.impl.packethandler.DHTUDPPacketHandlerFactory.process(DHTUDPPacketHandlerFactory.java:176)
	at com.aelitis.azureus.core.dht.transport.udp.impl.packethandler.DHTUDPPacketNetworkHandler.process(DHTUDPPacketNetworkHandler.java:73)
	at com.aelitis.net.udp.uc.impl.PRUDPPacketHandlerImpl$4.runSupport(PRUDPPacketHandlerImpl.java:650)
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Michael Chudobiak 2007-11-10 16:44:06 UTC

This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.


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