From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR
Description of problem:
Client program is killed by X server after approx 15 seonds with msg:
"X connection to :0.0 broken (explicit kill or server shutdown)"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Run my little test program "bugtest" from the unix promt.
2.Wait for 15 seconds.
3.See bugtest being killed by the X server.
Actual Results: Application is killed and you see the message "X connection
to :0.0 broken (explicit kill or server shutdown)".
Expected Results: I like my application te be left running.
I will attach my little test application together with it's source. If you run
it as compiled now, the bug will show itself as described above. However, if
you uncomment the code in bugtest.c enclosed by "Lars bugfix block" and then
recompile, "bugtest" will be left alive. Of course, this workaround is only
possible in code that you are free to manipulate, but it should aid you to find
the bug. The real problem is with an application that I purchased compiled.
Created attachment 59744 [details]
tar file of program showing the bug. Extract by tar -xvf bugtest.tar
Created attachment 59745 [details]
The executable that demonstrates the bug
The X server does not _ever_ kill any client application. You are totally
misinterpreting the error message.
What the message is saying, is that your program lost it's connection to
the X server. The error message hypothesizes potential reasons why, and
one of them is that the program may have been killed - not by the X server,
which is totally impossible, but for some other reason including the
I consider this problem entirely a bug in your software, and not an
X server bug. If you need assistance determining the source of the
problem, and possibly finding a solution, I suggest subscribing to
the firstname.lastname@example.org mailing list, posting the problem you're having,
and getting feedback from the hundreds of developers there.
If after doing so, it turns out there is in fact a bug in the X server,
feel free to reopen this bug report, and include all of the details from
your research on the xpert list. Also report said findings to the
official XFree86 bug reporting address of email@example.com, which
should the problem truely be an X problem, will accelerate the likelyhood
of the problem being looked at and addressed.