Bug 406955 – crash in Terminal: tring to open a new wind...

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 406955 - crash in Terminal: tring to open a new wind...


Summary:	crash in Terminal: tring to open a new wind...


Status:	RESOLVED DUPLICATE of bug 399877

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-02-12 05:11 UTC by james
Modified:	2007-02-21 14:57 UTC

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

Description james 2007-02-12 05:11:13 UTC

Version: 2.16.0

What were you doing when the application crashed?
tring to open a new window


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 19:28:18 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 44027904 vsize: 0 resident: 44027904 share: 0 rss: 12513280 rss_rlim: 0
CPU usage: start_time: 1171240063 rtime: 0 utime: 4158 stime: 0 cutime:3226 cstime: 0 timeout: 932 it_real_value: 0 frequency: 9657

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 -1208830256 (LWP 4164)]
[New Thread -1215112304 (LWP 4169)]
(no debugging symbols found)
0x00cb2402 in __kernel_vsyscall ()

+ Trace 109993

Thread 1 (Thread -1208830256 (LWP 4164))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gtk_widget_style_get_valist
from /usr/lib/libgtk-x11-2.0.so.0
#5 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#6 gtk_menu_bar_new
from /usr/lib/libgtk-x11-2.0.so.0
#7 gtk_menu_bar_new
from /usr/lib/libgtk-x11-2.0.so.0
#8 gtk_marshal_BOOLEAN__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#9 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /lib/libgobject-2.0.so.0
#11 g_signal_chain_from_overridden
from /lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#13 g_signal_emit
from /lib/libgobject-2.0.so.0
#14 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#16 gdk_window_is_viewable
from /usr/lib/libgdk-x11-2.0.so.0
#17 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#18 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#19 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#21 g_main_context_check
from /lib/libglib-2.0.so.0
#22 g_main_loop_run
from /lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 g_cclosure_marshal_VOID__OBJECT
#25 __libc_start_main
from /lib/libc.so.6
#26 g_cclosure_marshal_VOID__OBJECT
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
** Message: plugin_get_value 2 (2)
** Message: plugin_get_value 1 (1)
** Message: plugin_get_value 2 (2)
** Message: plugin_get_value 1 (1)
** Message: plugin_get_value 2 (2)
(gnome-terminal:4164): Gtk-CRITICAL **: _gtk_style_peek_property_value: assertion `GTK_IS_STYLE (style)' failed
** (bug-buddy:14712): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Comment 1 palfrey 2007-02-21 14:57:56 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find

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