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 444068 - crash in Terminal: Creating a new profile.
crash in Terminal: Creating a new profile.
Status: RESOLVED DUPLICATE of bug 457825
Product: gnome-terminal
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
: 459059 459979 470722 471462 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-04 19:23 UTC by rheron
Modified: 2007-10-28 23:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description rheron 2007-06-04 19:23:40 UTC 
Version: 2.18.0

What were you doing when the application crashed?
Creating a new profile.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: marble-ice
Icon Theme: OSX

Memory status: size: 123101184 vsize: 123101184 resident: 23441408 share: 12742656 rss: 23441408 rss_rlim: 4294967295
CPU usage: start_time: 1180969789 rtime: 716 utime: 553 stime: 163 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208248080 (LWP 4159)]
[New Thread -1222407280 (LWP 4223)]
(no debugging symbols found)
0x00d11402 in __kernel_vsyscall ()

+ Trace 138231

Thread 1 (Thread -1208248080 (LWP 4159))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 terminal_profile_update
  • #5 ??
  • #6 g_cclosure_marshal_VOID
    from /lib/libgobject-2.0.so.0
  • #7 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #8 ??
    from /lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #11 gtk_dialog_response
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #15 ??
    from /lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #18 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #21 ??
    from /lib/libgobject-2.0.so.0
  • #22 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #23 ??
    from /lib/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #26 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /lib/libgobject-2.0.so.0
  • #30 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #31 ??
    from /lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #34 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #38 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #39 ??
    from /lib/libglib-2.0.so.0
  • #40 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #41 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #42 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
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 "/lib/libsepol.so.1" 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
warning: .dynamic section for "/lib/libkeyutils.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-06-04 23:54:14 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Pedro Villavicencio 2007-07-01 02:05:52 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 3 Pedro Villavicencio 2007-07-26 23:37:06 UTC 
*** Bug 459059 has been marked as a duplicate of this bug. ***
Comment 4 Pedro Villavicencio 2007-07-27 00:12:12 UTC 
*** Bug 459979 has been marked as a duplicate of this bug. ***
Comment 5 Behdad Esfahbod 2007-09-03 22:42:43 UTC 
*** Bug 470722 has been marked as a duplicate of this bug. ***
Comment 6 Cosimo Cecchi 2007-09-18 10:19:26 UTC 
*** Bug 471462 has been marked as a duplicate of this bug. ***
Comment 7 André Klapper 2007-10-28 23:44:02 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 457825 ***