Bug 610225 – crash in gThumb: Middle mouse scrolling t...

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 610225 - crash in gThumb: Middle mouse scrolling t...


Summary:	crash in gThumb: Middle mouse scrolling t...


Status:	RESOLVED DUPLICATE of bug 608463

Product:	gthumb
Classification:	Other
Component:	general
Version:	2.11.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-02-17 07:11 UTC by mjd
Modified:	2010-02-17 13:04 UTC

See Also:
GNOME target:	---
GNOME version:	2.27/2.28

Description mjd 2010-02-17 07:11:38 UTC

Version: 2.11.1

What were you doing when the application crashed?
Middle mouse scrolling through photos


Distribution: Debian squeeze/sid
Gnome Release: 2.28.2 2009-12-18 (Debian)
BugBuddy Version: 2.28.0

System: Linux 2.6.32-2-amd64 #1 SMP Fri Feb 12 00:01:47 UTC 2010 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10705000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 636334080 vsize: 636334080 resident: 146227200 share: 32686080 rss: 146227200 rss_rlim: 18446744073709551615
CPU usage: start_time: 1266386980 rtime: 2950 utime: 2790 stime: 160 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7fd369afe910 (LWP 18428)]
[New Thread 0x7fd36bdfb910 (LWP 3979)]
[New Thread 0x7fd36be7c910 (LWP 3978)]
[New Thread 0x7fd36befd910 (LWP 3977)]
[New Thread 0x7fd36bf7e910 (LWP 3976)]
0x00007fd37e22c51d in __libc_waitpid (pid=18432, 
    stat_loc=<value optimized out>, options=0)
    at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 220606

Thread 1 (Thread 0x7fd383bed7f0 (LWP 3957))

#0 __libc_waitpid
at ../sysdeps/unix/sysv/linux/waitpid.c line 41
#1 g_spawn_sync
from /lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 gth_browser_viewer_scroll_event_cb
#6 ??
from /usr/lib/gthumb-2.0/extensions/libimage_viewer.so
#7 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#8 ??
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#11 ??
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#14 ??
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#17 ??
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#20 ??
from /usr/lib/libgdk-x11-2.0.so.0
#21 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#22 ??
from /lib/libglib-2.0.so.0
#23 g_main_loop_run
from /lib/libglib-2.0.so.0
#24 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#25 main

Current language:  auto
The current source language is "auto; currently c".
A debugging session is active.

	Inferior 1 [process 3957] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (10595 sec old) ---------------------
(firefox-bin:2283): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2283): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2283): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2283): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2283): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2283): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2283): Gdk-WARNING **: XID collision, trouble ahead
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Akhil Laddha 2010-02-17 12:18:13 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 2010-02-17 13:04:50 UTC

Probably a dupe of bug 608463, which is fixed in git.

- Mike

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