Bug 70130 - closing one gnome-terminal causes all to exit
Summary: closing one gnome-terminal causes all to exit
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: vte
Version: limbo
Hardware: i386
OS: Linux
high
medium
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 67217
TreeView+ depends on / blocked
 
Reported: 2002-07-30 17:11 UTC by Kris Urquhart
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-08-02 21:15:42 UTC
Embargoed:


Attachments (Terms of Use)

Description Kris Urquhart 2002-07-30 17:11:54 UTC
Description of Problem:
closing one gnome-terminal causes all to exit

Version-Release number of selected component (if applicable):
vte-0.5.1-2
gnome-terminal-2.0.0.90-2

How Reproducible:
Very

Steps to Reproduce:
1. open 4 gnome terminals (bash shell)
2. type Ctrl-D in one of them
3. they all go away

Actual Results:
all gnome-terminals exit

Expected Results:
only the one gnome-terminal exits

Additional Information:
clicking on the "X" in the upper right hand corner of the window border only
closes the one gnome-terminal.

Comment 1 Havoc Pennington 2002-07-30 18:44:26 UTC
first thing to check is whether it exits cleanly or crashes.

Comment 2 Kris Urquhart 2002-07-31 02:12:11 UTC
From .xsession-errors:
The program 'gnome-terminal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAccess (attempt to access private resource denied)'.
  (Details: serial 6821 error_code 10 request_code 88 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


Comment 3 Havoc Pennington 2002-08-02 21:05:20 UTC
This works OK for me. Can you reproduce with newer VTE packages?

Comment 4 Kris Urquhart 2002-08-02 21:15:37 UTC
I found this under limbo1, but work's fine in limbo2 (vte-0.5.4-2).

Comment 5 Havoc Pennington 2002-08-14 01:10:19 UTC
Should be fixed.


Note You need to log in before you can comment on or make changes to this bug.