Bug 382799 – crash in Terminal: Starting beryl-manager

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 382799 - crash in Terminal: Starting beryl-manager


Summary:	crash in Terminal: Starting beryl-manager


Status:	RESOLVED DUPLICATE of bug 361117

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:	2006-12-05 22:35 UTC by the.insomniac
Modified:	2006-12-05 22:38 UTC

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

Description the.insomniac 2006-12-05 22:35:49 UTC

Version: 2.16.1

What were you doing when the application crashed?
Starting beryl-manager


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 142200832 vsize: 142200832 resident: 19574784 share: 10862592 rss: 19574784 rss_rlim: -1
CPU usage: start_time: 1165357896 rtime: 106 utime: 88 stime: 18 cutime:5 cstime: 6 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 47276686866096 (LWP 4883)]
[New Thread 1082132816 (LWP 4888)]
(no debugging symbols found)
0x00002aff71f55eef in waitpid () from /lib/libpthread.so.0

+ Trace 91897

Thread 1 (Thread 47276686866096 (LWP 4883))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_type_check_instance_is_a
from /usr/lib64/libgobject-2.0.so.0
#4 g_object_unref
from /usr/lib64/libgobject-2.0.so.0
#5 gtk_widget_get_default_style
from /usr/lib64/libgtk-x11-2.0.so.0
#6 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#7 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#8 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#9 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#10 gtk_object_destroy
from /usr/lib64/libgtk-x11-2.0.so.0
#11 g_object_run_dispose
from /usr/lib64/libgobject-2.0.so.0
#12 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#13 _gdk_events_init
from /usr/lib64/libgdk-x11-2.0.so.0
#14 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#15 g_main_context_check
from /usr/lib64/libglib-2.0.so.0
#16 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#17 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#18 ??
#19 __libc_start_main
from /lib/libc.so.6
#20 ??
#21 ??
#22 ??
#0 waitpid
from /lib/libpthread.so.0

Comment 1 Christian Kirbach 2006-12-05 22:38:00 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 361117 ***