Bug 399648 – crash in Terminal: Scroll w/mouse wheel

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 399648 - crash in Terminal: Scroll w/mouse wheel


Summary:	crash in Terminal: Scroll w/mouse wheel


Status:	RESOLVED DUPLICATE of bug 389538

Product:	vte
Classification:	Core
Component:	general
Version:	0.15.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	future
Assigned To:	VTE Maintainers
QA Contact:	VTE Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-23 03:39 UTC by Boris Goldowsky
Modified:	2007-01-23 22:47 UTC

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

Description Boris Goldowsky 2007-01-23 03:39:01 UTC

Version: 2.16.1

What were you doing when the application crashed?
Scroll w/mouse wheel


Distribution: Fedora Core release 6 (Rawhide)
Gnome Release: 2.17.90 2007-01-21 (Red Hat, Inc)
BugBuddy Version: 2.17.3

System: Linux 2.6.17-1.2630.fc6 #1 SMP Wed Sep 6 16:16:03 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Enabled

Memory status: size: 47828992 vsize: 0 resident: 47828992 share: 0 rss: 10940416 rss_rlim: 0
CPU usage: start_time: 1169493289 rtime: 0 utime: 3176 stime: 0 cutime:2611 cstime: 0 timeout: 565 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-terminal'

(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 -1208674608 (LWP 3256)]
[New Thread -1214772336 (LWP 3263)]
(no debugging symbols found)
0xb7f74402 in __kernel_vsyscall ()

+ Trace 104469

Thread 1 (Thread -1208674608 (LWP 3256))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_malloc
from /lib/libglib-2.0.so.0
#10 ??
from /usr/lib/libvte.so.9
#11 atk_text_get_text
from /usr/lib/libatk-1.0.so.0
#12 ??
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#13 ??
from /lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#15 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#16 ??
from /usr/lib/libvte.so.9
#17 ??
from /usr/lib/libvte.so.9
#18 g_cclosure_marshal_VOID
from /lib/libgobject-2.0.so.0
#19 g_closure_invoke
from /lib/libgobject-2.0.so.0
#20 ??
from /lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#22 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#23 ??
from /usr/lib/libvte.so.9
#24 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#25 g_closure_invoke
from /lib/libgobject-2.0.so.0
#26 ??
from /lib/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#28 g_signal_emit
from /lib/libgobject-2.0.so.0
#29 gtk_adjustment_value_changed
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_adjustment_set_value
from /usr/lib/libgtk-x11-2.0.so.0
#31 ??
from /usr/lib/libvte.so.9
#32 ??
from /usr/lib/libgtk-x11-2.0.so.0
#33 ??
from /lib/libgobject-2.0.so.0
#34 g_closure_invoke
from /lib/libgobject-2.0.so.0
#35 ??
from /lib/libgobject-2.0.so.0
#36 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#37 g_signal_emit
from /lib/libgobject-2.0.so.0
#38 ??
from /usr/lib/libgtk-x11-2.0.so.0
#39 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#40 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#41 ??
from /usr/lib/libgdk-x11-2.0.so.0
#42 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#43 ??
from /lib/libglib-2.0.so.0
#44 g_main_loop_run
from /lib/libglib-2.0.so.0
#45 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#46 g_cclosure_marshal_VOID__OBJECT
#47 __libc_start_main
from /lib/libc.so.6
#48 g_cclosure_marshal_VOID__OBJECT
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
(bug-buddy:15154): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: cannot open shared object file: No such file or directory
(bug-buddy:15154): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: cannot open shared object file: No such file or directory
(bug-buddy:15154): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: cannot open shared object file: No such file or directory
(bug-buddy:15154): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: cannot open shared object file: No such file or directory
(bug-buddy:15154): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: cannot open shared object file: No such file or directory
(bug-buddy:15154): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: cannot open shared object file: No such file or directory
(bug-buddy:15154): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: cannot open shared object file: No such file or directory
Xlib:  extension "SHAPE" missing on display ":0.0".
--------------------------------------------------

Comment 1 Chris Wilson 2007-01-23 10:26:08 UTC

Is there a possibility that this is actually an older version of vte? For this is an exact dup of bug 389538 - except that should be impossible now!

Comment 2 Boris Goldowsky 2007-01-23 21:34:47 UTC

It is possible that there were some bits remaining from an older version, since I did a large "yum update" that day and don't remember the exact sequence of events w.r.t. that.

Comment 3 Chris Wilson 2007-01-23 22:47:09 UTC

I'll assume that a gnome-terminal was still running from before the update, hence the misreported version ;)

Please shout if it happens again. It won't, but...

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