Bug 430243 – crash in Terminal: rebooting the computer

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 430243 - crash in Terminal: rebooting the computer


Summary:	crash in Terminal: rebooting the computer


Status:	RESOLVED DUPLICATE of bug 161843

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-04-16 09:01 UTC by hmm
Modified:	2007-04-16 14:32 UTC

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

Description hmm 2007-04-16 09:01:45 UTC

Version: 2.16.0

What were you doing when the application crashed?
rebooting the computer


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 11:38:26 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 69210112 vsize: 0 resident: 69210112 share: 0 rss: 18890752 rss_rlim: 0
CPU usage: start_time: 1176713009 rtime: 0 utime: 739 stime: 0 cutime:588 cstime: 0 timeout: 151 it_real_value: 0 frequency: 1

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 -1208596784 (LWP 2947)]
[New Thread -1216193648 (LWP 2950)]
(no debugging symbols found)
0x0078a402 in __kernel_vsyscall ()

+ Trace 128173

Thread 1 (Thread -1208596784 (LWP 2947))

#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 strlen
from /lib/libc.so.6
#5 vfprintf
from /lib/libc.so.6
#6 vasprintf
from /lib/libc.so.6
#7 g_vasprintf
from /lib/libglib-2.0.so.0
#8 g_strdup_vprintf
from /lib/libglib-2.0.so.0
#9 g_print
from /lib/libglib-2.0.so.0
#10 g_cclosure_marshal_VOID__OBJECT
#11 gnome_ice_init
from /usr/lib/libgnomeui-2.so.0
#12 g_closure_invoke
from /lib/libgobject-2.0.so.0
#13 g_signal_chain_from_overridden
from /lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#15 g_signal_emit
from /lib/libgobject-2.0.so.0
#16 gnome_client_set_clone_command
from /usr/lib/libgnomeui-2.so.0
#17 _SmcProcessMessage
from /usr/lib/libSM.so.6
#18 IceProcessMessages
from /usr/lib/libICE.so.6
#19 gnome_ice_init
from /usr/lib/libgnomeui-2.so.0
#20 g_io_channel_unix_get_fd
from /lib/libglib-2.0.so.0
#21 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#22 g_main_context_check
from /lib/libglib-2.0.so.0
#23 g_main_loop_run
from /lib/libglib-2.0.so.0
#24 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#25 g_cclosure_marshal_VOID__OBJECT
#26 __libc_start_main
from /lib/libc.so.6
#27 g_cclosure_marshal_VOID__OBJECT
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/libX11.so.6" is not at the expected address
warning: .dynamic section for "/usr/lib/libgssapi_krb5.so.2" is not at the expected address
warning: .dynamic section for "/usr/lib/libkrb5.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libk5crypto.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libkrb5support.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 palfrey 2007-04-16 14:32:49 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 161843 ***