Bug 413653 – crash in Gnome Terminal: Maximizing a minimized g...

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 413653 - crash in Gnome Terminal: Maximizing a minimized g...


Summary:	crash in Gnome Terminal: Maximizing a minimized g...


Status:	RESOLVED DUPLICATE of bug 352444

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 22:42 UTC by robert
Modified:	2007-03-17 20:22 UTC

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

Description robert 2007-03-01 22:42:51 UTC

Version: 2.16.1

What were you doing when the application crashed?
Maximizing a minimized gnome console windows.


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 382754816 vsize: 382754816 resident: 91500544 share: 13029376 rss: 104529920 rss_rlim: 1676477440
CPU usage: start_time: 1172285449 rtime: 7318 utime: 4380 stime: 2938 cutime:23476346 cstime: 201346 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47721472973120 (LWP 8196)]
[New Thread 1082132800 (LWP 8251)]
(no debugging symbols found)
0x00002b6703225c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 115051

Thread 1 (Thread 47721472973120 (LWP 8196))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 g_logv
from /opt/gnome/lib64/libglib-2.0.so.0
#6 g_log
from /opt/gnome/lib64/libglib-2.0.so.0
#7 g_assert_warning
from /opt/gnome/lib64/libglib-2.0.so.0
#8 ORBit_RootObject_duplicate_T
from /opt/gnome/lib64/libORBit-2.so.0
#9 CORBA_free
from /opt/gnome/lib64/libORBit-2.so.0
#10 CORBA_free
from /opt/gnome/lib64/libORBit-2.so.0
#11 ORBit_free_T
from /opt/gnome/lib64/libORBit-2.so.0
#12 ORBit_free
from /opt/gnome/lib64/libORBit-2.so.0
#13 gnome_accessibility_module_shutdown
from /opt/gnome/lib64/gtk-2.0/modules/libatk-bridge.so
#14 gnome_accessibility_module_shutdown
from /opt/gnome/lib64/gtk-2.0/modules/libatk-bridge.so
#15 g_signal_override_class_closure
from /opt/gnome/lib64/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /opt/gnome/lib64/libgobject-2.0.so.0
#17 g_signal_emit
from /opt/gnome/lib64/libgobject-2.0.so.0
#18 gail_window_new
from /opt/gnome/lib64/gtk-2.0/modules/libgail.so
#19 gtk_marshal_BOOLEAN__VOID
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#20 g_closure_invoke
from /opt/gnome/lib64/libgobject-2.0.so.0
#21 g_signal_override_class_closure
from /opt/gnome/lib64/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /opt/gnome/lib64/libgobject-2.0.so.0
#23 g_signal_emit
from /opt/gnome/lib64/libgobject-2.0.so.0
#24 gtk_widget_get_default_style
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#25 gtk_main_do_event
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#26 gdk_add_client_message_filter
from /opt/gnome/lib64/libgdk-x11-2.0.so.0
#27 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#28 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#29 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#30 gtk_main
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#31 g_cclosure_marshal_VOID__OBJECT
#32 __libc_start_main
from /lib64/libc.so.6
#33 g_cclosure_marshal_VOID__OBJECT
#34 ??
#35 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 André Klapper 2007-03-17 20:22:19 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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