Random X crashes, very often

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Let torchat run for a while

What is the expected output? What do you see instead?
a)
python: Fatal IO error 11 (Resource temporarily unavailable) on X 
server :0.0.

and all windows disappear (process still running but must be kill'd)

or

b)
The program 'python' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 80672 error_code 9 request_code 142 minor_code 3)
  (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.)

and torchat exits

What version of the product are you using? On what operating system?
torchat 0.9.9.287 using deb on Kubuntu 9.10

Please provide any additional information below.
This is very annoying and makes torchat practically useless, it usually 
happens within a minute of chatting to someone, but I've found no 
reproducible cause.

Original issue reported on code.google.com by kjella...@yahoo.no on 16 Dec 2009 at 9:26

[GoogleCodeExporter]

I have the identical problem running debian torchat v 0.9.9.287 on Ubuntu 
karmic 9.10
using tor executable of 3 Feb 2010 v0.2.1.23.

This problem first appeared when I installed ubuntu karmic koala, it was not 
present
in earlier ubuntu versions.

This fault does NOT appear in the windows version of torchat.

What triggers the torchat window shutdown for me is another torchat user 
sending a
message to me. And, as kjella said above, the tor processes continue to run even
though the torchat windows have disappeared.

Yes, it does make torchat useless in ubuntu, maybe in other Linux distros too.

Original comment by torc...@yopmail.com on 27 Feb 2010 at 9:03

[GoogleCodeExporter]

This must be a bug in xorg or wxpython. does this still happen in the latest 
TorChat release (which enforces the use of python2.5 and python2.5-wxgtk-2.8 on 
all ubuntu versions)?

does it only happen with a specific wxpython version when you install these 
combinations:

python2.5 and python2.5-wxgtk-2.8
python2.6 and python2.6-wxgtk-2.8
python2.7 and python2.7-wxgtk-2.8

and then start TorChat like so:

$ cd /usr/lib/torchat
$ python2.5 torchat.py
$ python2.6 torchat.py
$ python2.7 torchat.py

could you please enable logging or simply start it from the console to capture 
any error messages immediately before the crash?

torchat will by default use python2.5 because I have still Ubuntu Hardy on one 
of my old Laptops but if for some strange reasons this does not work while 
newer versions would not crash then I could make a .deb that uses 2.6 or 2.7 as 
a temporary workaround. But the main priority should be to debug why it is 
crashing in the first place.

Original comment by prof7...@gmail.com on 20 Dec 2010 at 7:03

• Added labels: Priority-Critical

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

typo. the above packages are named (without the "-" in front of the 2.8):

python2.5, python2.5-wxgtk2.8
python2.6, python2.6-wxgtk2.8
python2.7, python2.7-wxgtk2.8

Original comment by prof7...@gmail.com on 20 Dec 2010 at 7:10

[GoogleCodeExporter]

Does it reliably go away when notification pop-up is disabled (second tab, 3rd 
option in the settings dialog)?

Original comment by prof7...@gmail.com on 21 Dec 2010 at 6:14

• Changed state: Started

[GoogleCodeExporter]

The xserver is more restrictive in the newer versions
regarding the (wrong) usage of different threads. Many apps
had similar problems, problems began with Ubuntu Karmic.

fixed in latest release 0.9.9.324

Original comment by prof7...@gmail.com on 22 Dec 2010 at 9:42

• Changed state: Fixed