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 410598 - crash in Terminal: said yes to overwrite ex...
crash in Terminal: said yes to overwrite ex...
Status: RESOLVED DUPLICATE of bug 363609
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-02-21 23:31 UTC by Euan
Modified: 2007-02-27 19:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Euan 2007-02-21 23:31:06 UTC
Version: 2.16.1

What were you doing when the application crashed?
said yes to overwrite exisiting profile with a new one of same name.


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

Memory status: size: 73400320 vsize: 0 resident: 73400320 share: 0 rss: 17510400 rss_rlim: 0
CPU usage: start_time: 1172098959 rtime: 0 utime: 208 stime: 0 cutime:194 cstime: 0 timeout: 14 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226291536 (LWP 6247)]
[New Thread -1267782752 (LWP 6251)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226291536 (LWP 6247))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 ??
  • #6 _IO_stdin_used
  • #7 _IO_stdin_used
  • #8 ??
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall

Comment 1 Christian Kirbach 2007-02-22 22:04:18 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 Euan 2007-02-27 19:46:38 UTC
To repeat: make profile called "ser".  Close teminal, attempt to make another profile also called "ser", then say yes when the prompt: "You already have a profile called "ser". Do you want to create another profile with the same name?"

debug trace as requested:

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

Memory status: size: 72765440 vsize: 0 resident: 72765440 share: 0 rss: 16343040 rss_rlim: 0
CPU usage: start_time: 1172605065 rtime: 0 utime: 101 stime: 0 cutime:95 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1226418512 (LWP 5160)]
[New Thread -1267909728 (LWP 5164)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226418512 (LWP 5160))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 874
  • #3 <signal handler called>
  • #4 terminal_profile_update
    at terminal-profile.c line 1975
  • #5 new_profile_response_callback
    at terminal.c line 2386
  • #6 IA__g_cclosure_marshal_VOID__INT
    at gmarshal.c line 216
  • #7 IA__g_closure_invoke
    at gclosure.c line 490
  • #8 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #9 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #10 IA__g_signal_emit
    at gsignal.c line 2243
  • #11 gtk_dialog_response
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_dialog_response
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #14 IA__g_closure_invoke
    at gclosure.c line 490
  • #15 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #16 IA__g_signal_emit_valist
  • #17 IA__g_signal_emit
    at gsignal.c line 2243
  • #18 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_button_set_alignment
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #21 g_type_class_meta_marshal
    at gclosure.c line 567
  • #22 IA__g_closure_invoke
    at gclosure.c line 490
  • #23 signal_emit_unlocked_R
    at gsignal.c line 2370
  • #24 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #25 IA__g_signal_emit
    at gsignal.c line 2243
  • #26 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 g_type_class_meta_marshal
    at gclosure.c line 567
  • #30 IA__g_closure_invoke
    at gclosure.c line 490
  • #31 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #32 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #33 IA__g_signal_emit
    at gsignal.c line 2243
  • #34 gtk_widget_get_default_style
    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 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #38 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #39 g_main_context_iterate
    at gmain.c line 2677
  • #40 IA__g_main_loop_run
    at gmain.c line 2881
  • #41 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #42 main
    at terminal.c line 1773
  • #43 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #44 _start
  • #0 __kernel_vsyscall

Comment 3 Mariano Suárez-Alvarez 2007-02-27 19:49:31 UTC
Thanks for the info!

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 363609 ***