GNOME Bugzilla – Bug 115517
Gnome Terminal 2.2.1 Crashes when tabs are used and one app closes one of the tabs.
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-terminal Severity: critical Version: 2.2.1 Synopsis: Gnome Terminal 2.2.1 Crashes when tabs are used and one app closes one of the tabs. Bugzilla-Product: gnome-terminal Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: In gnome-terminal 2.2.1, I set it up to use execute as a login shell, with default options, except I had it execute /usr/bin/pine instead of the login shell, also having it close the window when the app exits. I also have it set in the command line to have a tab with the default profile to load with the pine client, so I have a terminal and the pine email client. When I exited pine it went to the terminal tab and then crashed a second later, locking up the application and rendering an unresponsive window, requiring me to have to kill the application and the error window. Steps to reproduce the problem: 1. Setup a profile called "Pine" with default options, except, the title is "Pine Email Client" and check the box to execute a command instead of the login shell, and put /usr/bin/pine in the command box. Tell it to close the window when the application exits. 2. bring up gnome-terminal with the following command line: gnome-terminal --geometry 110x20 --login --window-with-profile=Pine --tab-with-profile=Default --hide-menubar --title="Pine Email Client" 3. Then, click over to pine and exit it using the "q" command as you normaly would exit pine in a shell. Actual Results: It will flip over to the shell with the Default profile, become unresponsive and an error message should appear and then bug-buddy should follow shortly, if you try to bring up another terminal before the other is killed, the error window and the other should become unresponsive and the window manager (if bluecurve) should ask you if you want to kill them. Also things started to get slower as immediatly after turning off the menu neumonics, so that too may have caused it, it sped back up a little after turning them back on. Expected Results: When pine exits, it should either flipped to the open terminal tab or closed the window all togeather. How often does this happen? This only has happened once so far, this is the first time. Additional Information: I could not regenerate the crash again, so this may have been a fluke, but thaught you should know about it anyway, incase it happenes again. 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)... (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)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 1087450112 (LWP 15725)] (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)... (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)... (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)...0xffffe002 in ?? ()
+ Trace 37960
Thread 1 (Thread 1087450112 (LWP 15725))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-19 02:28 ------- The original reporter (twolf@kc.net) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, hp@redhat.com.
Thanks for the bug report--and for the great detail in describing the problem (that's sort of rare). However, 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 ***