Bug 413587 – crash in Terminal: datei->neues terminal. ...

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 413587 - crash in Terminal: datei->neues terminal. ...


Summary:	crash in Terminal: datei->neues terminal. ...


Status:	RESOLVED DUPLICATE of bug 353498

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.16.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-01 20:10 UTC by satan0rx
Modified:	2007-03-02 01:26 UTC

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

Description satan0rx 2007-03-01 20:10:25 UTC

Version: 2.16.1

What were you doing when the application crashed?
datei->neues terminal.

PS: meine hardware macht Zicken, könnte also daran liegen



Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.16.3 2007-02-07 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 150904832 vsize: 150904832 resident: 23375872 share: 13103104 rss: 23375872 rss_rlim: -1
CPU usage: start_time: 1172782742 rtime: 73 utime: 66 stime: 7 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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 47533583661888 (LWP 5336)]
[New Thread 1082140992 (LWP 5340)]
0x00002b3b438c3aef in waitpid () from /lib/libpthread.so.0

+ Trace 115008

Thread 1 (Thread 47533583661888 (LWP 5336))

#0 waitpid
from /lib/libpthread.so.0
#1 ??
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 gtk_widget_style_get_valist
from /usr/lib/libgtk-x11-2.0.so.0
#4 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#5 ??
from /usr/lib/libgtk-x11-2.0.so.0
#6 ??
from /usr/lib/libgtk-x11-2.0.so.0
#7 ??
from /usr/lib/libgtk-x11-2.0.so.0
#8 ??
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_widget_queue_resize
from /usr/lib/libgtk-x11-2.0.so.0
#10 ??
from /usr/lib/libgtk-x11-2.0.so.0
#11 ??
from /usr/lib/libgtk-x11-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#18 ??
from /usr/lib/libglib-2.0.so.0
#19 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 ??
#22 __libc_start_main
from /lib/libc.so.6
#23 ??
#24 ??
#25 ??
#0 waitpid
from /lib/libpthread.so.0

Comment 1 Bruno Boaventura 2007-03-02 01:26:54 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 353498 ***