Bug 414477 – crash in Terminal: Right clicked on desktop

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 414477 - crash in Terminal: Right clicked on desktop


Summary:	crash in Terminal: Right clicked on desktop


Status:	RESOLVED DUPLICATE of bug 413036

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.17.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	GNOME Terminal Maintainers
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-03-04 06:08 UTC by geekieboi
Modified:	2007-03-04 12:10 UTC

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

Description geekieboi 2007-03-04 06:08:12 UTC

Version: 2.17.91

What were you doing when the application crashed?
Right clicked on desktop


Distribution: Fedora release 6.91 (Rawhide)
Gnome Release: 2.17.91 2007-02-13 (Red Hat, Inc)
BugBuddy Version: 2.17.3

System: Linux 2.6.20-1.2949.fc7 #1 SMP Mon Feb 26 18:37:35 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: Enforcing
Accessibility: Enabled

Memory status: size: 41181184 vsize: 0 resident: 41181184 share: 0 rss: 14061568 rss_rlim: 0
CPU usage: start_time: 1172987853 rtime: 0 utime: 204 stime: 0 cutime:43 cstime: 0 timeout: 161 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 -1208437024 (LWP 3717)]
[New Thread -1214903408 (LWP 3722)]
(no debugging symbols found)
0x0061f402 in __kernel_vsyscall ()

+ Trace 115659

Thread 1 (Thread -1208437024 (LWP 3717))

#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/libvte.so.9
#5 ??
from /usr/lib/libvte.so.9
#6 ??
from /usr/lib/libgtk-x11-2.0.so.0
#7 ??
from /lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /lib/libgobject-2.0.so.0
#9 ??
from /lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#11 g_signal_emit
from /lib/libgobject-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libgdk-x11-2.0.so.0
#15 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#16 ??
from /usr/lib/libvte.so.9
#17 ??
from /lib/libglib-2.0.so.0
#18 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#19 ??
from /lib/libglib-2.0.so.0
#20 g_main_loop_run
from /lib/libglib-2.0.so.0
#21 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#22 main
#0 __kernel_vsyscall



----------- .xsession-errors (15 sec old) ---------------------
(gnome-terminal:3717): Vte-WARNING **: Can not find appropiate font for character U+ac04.
(gnome-terminal:3717): Vte-WARNING **: Can not find appropiate font for character U+ac08.
(gnome-terminal:3717): Vte-WARNING **: Can not find appropiate font for character U+ac10.
The application '<unknown>' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
--------------------------------------------------

Comment 1 Chris Wilson 2007-03-04 12:10:44 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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