Bug 246604 - gnome-terminal sometimes fails with X11 error:serial 309 error_code 10 request_code 147 minor_code 5
Summary: gnome-terminal sometimes fails with X11 error:serial 309 error_code 10 reques...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-terminal
Version: 7
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-07-03 12:33 UTC by Joachim Backes
Modified: 2008-06-17 05:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-17 01:46:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Joachim Backes 2007-07-03 12:33:36 UTC
Description of problem:
Having a shell script as "ssh -X somehost gnome-terminal -e ...". Sometimes (not
alltimes) the gnome-terminal inside of the script fails on the remote host with
the message:

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 309 error_code 10 request_code 147 minor_code 5)
  (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.)

Then waiting some seconds and recalling the cmd, it runs properly.


Version-Release number of selected component (if applicable):
gnome-terminal-2.18.1-1.fc7


How reproducible:

sometimes
Steps to Reproduce:
1."ssh -X somehost gnome-terminal -e ..."
2.
3.
  
Actual results:
See the above error message

Expected results:
No failure.

Additional info:

After waiting some seconds, the command runs without error

Comment 1 Bug Zapper 2008-05-14 13:23:49 UTC
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
http://docs.fedoraproject.org/release-notes/

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2008-06-17 01:46:45 UTC
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 is no longer maintained, which means that it will not 
receive any further security or bug fix updates. As a result we 
are closing this bug. 

If you can reproduce this bug against a currently maintained version 
of Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Joachim Backes 2008-06-17 05:16:11 UTC
Unable to reproduce in F9!


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