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 146940 - Terminal crashes after exit
Terminal crashes after exit
Status: RESOLVED DUPLICATE of bug 107234
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-06-28 13:55 UTC by kim.karlsson
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description kim.karlsson 2004-07-09 13:25:29 UTC 
Package: gnome-terminal
Severity: major
Version: 2.2.1
Synopsis: Terminal crashes after exit
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
After having made myself a su user, and typing exit, then exit again
crashes the terminal.

Steps to reproduce the problem:
1. su into root
2. type exit and return
3. type exit to close the terminal window. it crashes, and it is
reproducable

Actual Results:
I get a message box "Gnome-terminal has crashed due to fatal error
(aborted)."

Expected Results:
The terminal window should just close.

How often does this happen?
Every time I try to do it.

Additional Information:
I've reported this bug just a minute ago, and decided to see if I could
reproduce it.



Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 1087444704 (LWP 24590)]
0xffffe002 in ??
    ()

+ Trace 48276

Thread 1 (Thread 1087444704 (LWP 24590))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 abort
    from /lib/tls/libc.so.6
  • #5 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib/libglib-2.0.so.0
  • #7 vte_terminal_fork_command
    from /usr/lib/libvte.so.4
  • #8 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #9 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    at gtkmain.c line 1092
  • #14 main
  • #15 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ?? 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 09:25 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-terminal".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 Olav Vitters 2004-07-09 15:11:22 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 107234 ***