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 399046 - crash in Terminal: I editted and renamed th...
crash in Terminal: I editted and renamed th...
Status: RESOLVED DUPLICATE of bug 324227
Product: gnome-terminal
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-21 15:45 UTC by jwboyer
Modified: 2007-01-29 23:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description jwboyer 2007-01-21 15:45:42 UTC 
Version: 2.16.1

What were you doing when the application crashed?
I editted and renamed the Default profile.  Then I went to create a new profile which I named "Default".  That is when the program crashed.


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

Memory status: size: 199729152 vsize: 199729152 resident: 32587776 share: 13836288 rss: 32587776 rss_rlim: -1
CPU usage: start_time: 1169342860 rtime: 2458 utime: 2318 stime: 140 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47838669301424 (LWP 5181)]
[New Thread 1082132816 (LWP 5185)]
(no debugging symbols found)
0x00002b824ab8ceef in waitpid () from /lib/libpthread.so.0

+ Trace 104030

Thread 1 (Thread 47838669301424 (LWP 5181))

  • #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 ??
  • #4 ??
  • #5 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #6 g_signal_chain_from_overridden
    from /usr/lib64/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #10 g_signal_chain_from_overridden
    from /usr/lib64/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #13 gtk_button_set_alignment
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #14 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #15 g_signal_chain_from_overridden
    from /usr/lib64/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #18 gtk_button_released
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #19 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #20 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #21 g_signal_chain_from_overridden
    from /usr/lib64/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #24 gtk_widget_get_default_style
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #25 gtk_propagate_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #26 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #27 _gdk_events_init
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #28 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #29 g_main_context_check
    from /usr/lib64/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #31 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #32 ??
  • #33 __libc_start_main
    from /lib/libc.so.6
  • #34 ??
  • #35 ??
  • #36 ??
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


Bruno Boaventura





          2007-01-21 15:54:38 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


Mariano Suárez-Alvarez





          2007-01-29 23:50:13 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 324227 ***