search

njsmith / partiwm

[defunct] Experiments with window managers in Python + GTK+, including the original version of xpra
GNU General Public License v2.0
23 stars 3 forks source link

Certain X server versions have SEGFAULT bugs in XTest code #20

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Start xpra and a gtk application (i've only tried pidgin and gimp)
$ xpra start :7
$ DISPLAY=:7 pidgin &
$ xpra attach :7
2. Activate a window of the application
3. Press Ctrl+Alt (what I press to move windows between workspaces)

This seems to bring down (segfault) the xpra server each time I try it. 
However, if I press other keys first the server does not crash. Also, it 
only seems to happen with some applications - perhaps gtk? When I tried 
xclock and xlogo the server didn't crash but when I run pidgin or gimp it 
crashes. To me the common denominator seems to be GTK, but you are the 
xperts!

What version of the product are you using? On what operating system?

parti-all 0.0.6 (AUR package parti-all 0.0.6-1, if you are using Arch 
Linux)
Arch Linux, which of course uses rolling releases, but here are some 
library versions:
extra/gtk2 2.18.6-1
extra/python 2.6.4-2
extra/pygtk 2.16.0-2
extra/pyrex 0.9.8.5-2
extra/libxtst 1.1.0-1

Please provide any additional information below.

I've attached my xpra log

Original issue reported on code.google.com by andre.la...@gmail.com on 17 Feb 2010 at 11:45

Attachments:

GoogleCodeExporter commented 9 years ago 
Oh, and libc which is mentioned in the backtrace is glibc 2.11.1.

Original comment by andre.la...@gmail.com on 17 Feb 2010 at 11:53

GoogleCodeExporter commented 9 years ago 
Issue 26 has been merged into this issue.

Original comment by njsmith@ucsd.edu on 26 Jun 2010 at 3:14

GoogleCodeExporter commented 9 years ago 
If someone can install the debug information for the 'xvfb' package (e.g., for 
Ubuntu the instructions are here: 
https://wiki.ubuntu.com/DebuggingProgramCrash), and then reproduce this crash, 
then the backtrace will hopefully be more useful.

Also, can you please attach the output of the commands 'xmodmap -pm' and 
'xmodmap -pk'?

Original comment by njsmith@ucsd.edu on 26 Jun 2010 at 3:29

GoogleCodeExporter commented 9 years ago 
Okay, it looks like this crash is caused by a bug in the X server, that was 
fixed in this commit (says 'git bisect'):
  http://cgit.freedesktop.org/xorg/xserver/commit/?id=af170a4ab76d33254dd4e54a33bb410fa1624739

I'm not sure when the bug was introduced, but it affects X server 1.7.6. It 
looks like the patch above has been back-ported to the 1.7 branch and is fixed 
in 1.7.7, but I haven't tested 1.7.7 yet.

Original comment by njsmith@ucsd.edu on 19 Jul 2010 at 4:56

GoogleCodeExporter commented 9 years ago 
I've just tested 1.7.7, and it does in fact work.

So it looks like the solution is to upgrade your X server (in particular, your 
Xvfb).

Original comment by njsmith@ucsd.edu on 19 Jul 2010 at 5:02

GoogleCodeExporter commented 9 years ago 
Xvfb 1.8.2 is also fine.

Original comment by njsmith@ucsd.edu on 19 Jul 2010 at 5:19

GoogleCodeExporter commented 9 years ago 
For future reference (since I'm sure people will keep running into this), 
here's the bug report for Ubuntu:
  https://bugs.launchpad.net/ubuntu/+source/parti-all/+bug/607071
If you run into this problem on another distribution then please feel free to 
file a bug with them as well, asking them to update their X server or to apply 
the patch.

Original comment by njsmith@ucsd.edu on 19 Jul 2010 at 5:35