Bug 366634 – crash in gThumb Image Viewer: Opening gthumb from Gnom...

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 366634 - crash in gThumb Image Viewer: Opening gthumb from Gnom...


Summary:	crash in gThumb Image Viewer: Opening gthumb from Gnom...


Status:	RESOLVED DUPLICATE of bug 447311

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:	2006-10-29 03:05 UTC by prd
Modified:	2007-06-14 11:43 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description prd 2006-10-29 03:05:11 UTC

What were you doing when the application crashed?
Opening gthumb from Gnome menu


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 200024064 vsize: 0 resident: 200024064 share: 0 rss: 16830464 rss_rlim: 0
CPU usage: start_time: 1162091018 rtime: 0 utime: 108 stime: 0 cutime:104 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gthumb'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227921216 (LWP 5660)]
[New Thread -1396044896 (LWP 5674)]
[New Thread -1387652192 (LWP 5673)]
[New Thread -1379259488 (LWP 5672)]
[New Thread -1370866784 (LWP 5671)]
[New Thread -1362474080 (LWP 5670)]
[New Thread -1354081376 (LWP 5669)]
[New Thread -1345688672 (LWP 5668)]
[New Thread -1337295968 (LWP 5667)]
[New Thread -1328780384 (LWP 5666)]
[New Thread -1258824800 (LWP 5664)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 79556

Thread 1 (Thread -1227921216 (LWP 5660))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 ??
from /usr/lib/libgthread-2.0.so.0
#10 ??
from /usr/lib/libgthread-2.0.so.0
#11 ??
#12 ??
from /usr/lib/libgthread-2.0.so.0
#13 ??
from /usr/lib/libgthread-2.0.so.0
#14 ??
#15 ??
from /usr/lib/libgthread-2.0.so.0
#16 ??
#17 ??
from /usr/lib/libgthread-2.0.so.0
#18 calloc
from /lib/tls/i686/cmov/libc.so.6
#19 g_thread_create_full
from /usr/lib/libglib-2.0.so.0
#20 image_loader_new
from /usr/lib/libgthumb.so
#21 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#22 g_object_set
from /usr/lib/libgobject-2.0.so.0
#23 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#24 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#25 g_object_new
from /usr/lib/libgobject-2.0.so.0
#26 image_loader_new
from /usr/lib/libgthumb.so
#27 gthumb_preloader_new
#28 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#29 g_object_set
from /usr/lib/libgobject-2.0.so.0
#30 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#31 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#32 g_object_new
from /usr/lib/libgobject-2.0.so.0
#33 gthumb_preloader_new
#34 gth_browser_new
#35 all_windows_update_catalog_list
#36 main
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-10-29 13:02:29 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. Thanks in advance!

Comment 2 Michael Chudobiak 2006-11-16 13:03:50 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!

Comment 3 Michael Chudobiak 2007-06-14 11:43:00 UTC

Probably a duplicate of bug 447311.

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