Bug 510603 – crash in gThumb Image Viewer:

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 510603 - crash in gThumb Image Viewer:


Summary:	crash in gThumb Image Viewer:


Status:	RESOLVED DUPLICATE of bug 486886

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-01-19 13:51 UTC by victor.von.destino
Modified:	2008-03-10 12:34 UTC

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

Description victor.von.destino 2008-01-19 13:51:58 UTC

What were you doing when the application crashed?



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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 135233536 vsize: 135233536 resident: 81215488 share: 21135360 rss: 81215488 rss_rlim: 4294967295
CPU usage: start_time: 1200746340 rtime: 55733 utime: 50123 stime: 5610 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 -1208351008 (LWP 4509)]
[New Thread -1235375216 (LWP 4518)]
[New Thread -1234846832 (LWP 4517)]
[New Thread -1234318448 (LWP 4516)]
[New Thread -1223300208 (LWP 4514)]
[New Thread -1222771824 (LWP 4513)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 185953

Thread 1 (Thread -1208351008 (LWP 4509))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
from /usr/lib/gthumb/libgthumb.so
#5 get_metadata_time
from /usr/lib/gthumb/libgthumb.so
#6 ??
#7 ??
#8 ??
#9 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /lib/libgobject-2.0.so.0
#11 ??
from /lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#13 g_signal_emit
from /lib/libgobject-2.0.so.0
#14 ??
from /usr/lib/gthumb/libgthumb.so
#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 image_loader_load_from_image_loader
from /usr/lib/gthumb/libgthumb.so
#21 load_from_image_loader__step2
from /usr/lib/gthumb/libgthumb.so
#22 ??
from /usr/lib/gthumb/libgthumb.so
#23 ??
from /lib/libglib-2.0.so.0
#24 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#25 ??
from /lib/libglib-2.0.so.0
#26 g_main_loop_run
from /lib/libglib-2.0.so.0
#27 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#28 main
#0 __kernel_vsyscall



----------- .xsession-errors (258 sec old) ---------------------
Checking if there is an instance already running...
There seems to be an instance of aMule already running
If this is not the case, you may have to remove
the file ~/.aMule/muleLock, to allow aMule to run.
Attempting to raise current running instance.
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
Loading temp files from /home/Angelo/.aMule/Temp.

Loading PartFile 1 of 68
Loading PartFile 2 of 68
Loading PartFile 3 of 68
Loading PartFile 4 of 68
Loading PartFile 5 of 68
Loading PartFile 6 of 68
Loading PartFile 7 of 68
Loading PartFile 8 of 68
All PartFiles Loaded.
ListenSocket: Ok.
External connections disabled in config file
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
***
--------------------------------------------------

Comment 1 Michael Chudobiak 2008-01-21 13:16:17 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!

Comment 2 Michael Chudobiak 2008-03-10 12:34:17 UTC


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