[winswitch] Trouble with xpra 0.10.0

Antoine Martin antoine at nagafix.co.uk
Sun Aug 18 16:34:53 BST 2013

On 17/08/13 05:48, Douglas Doole wrote:
> One update - I downgraded the client to xpra 0.9.8 and all the problems
> seem to have gone away.
> On Fri, Aug 16, 2013 at 6:31 PM, Douglas Doole <dougdoole at gmail.com> wrote:
>> I just upgraded both my server and client to xpra 0.10.0. Both my server
>> and client are running 64-bit Ubuntu 12.04. My client is running KDE, and
>> it was running 0.9.x with no problems.
>> Since upgrading, I've had a lot of problems, such as:
>> - Windows not repainting at all (get just a frame). Refresh generally
>> clears this up until it happens again.
>> - Windows partially repainting (sometime a narrow band shows the desktop
>> background, sometimes half the window is blank white, sometimes half the
>> window is a smear of green). Again refresh clears it up for a while.
Sounds like GL rendering might be to blame. Try --no-opengl
>> - Lots of random client side shutdowns. (Bringing up the Session Info
>> window is almost guaranteed to cause the client to abort.)
As above.
>> - When I start xpra, all windows are moved to desktop #1.
>> - Lots of focus problems. (Typically have to click the desktop then into
>> the window that needs focus.)
The last 2 are probably related to this one:
> So something seems to be fundamentally wrong.
None of these problems have been reported by anyone who tested 0.10
before its release, but then again... AFAIK none of them tested Ubuntu
very thoroughly either.
(though I did quite a bit of testing on 13.04 myself recently)

FWIW: apart from the well tested platforms (win32, OSX, Fedora, some
CentOS versions), it even runs on OpenBSD (I've just verified) so I am
pretty confident this is mostly an Ubuntu only problem (yet again).

>> I do see one error message on the client as I attach:
>> xpra client version 0.10.0
>> 2013-08-16 18:27:24,081 No OpenGL_accelerate module loaded: No module
>> named OpenGL_accelerate
>> 2013-08-16 18:27:24,131 Unable to load registered array format handler
>> numeric:
>> Traceback (most recent call last):
>>   File "/usr/lib/pymodules/python2.7/OpenGL/arrays/formathandler.py", line
>> 44, in loadPlugin
>>     plugin_class = entrypoint.load()
>>   File "/usr/lib/pymodules/python2.7/OpenGL/plugins.py", line 14, in load
>>     return importByName( self.import_path )
>>   File "/usr/lib/pymodules/python2.7/OpenGL/plugins.py", line 28, in
>> importByName
>>     module = __import__( ".".join(moduleName), {}, {}, moduleName)
>>   File "/usr/lib/pymodules/python2.7/OpenGL/arrays/numeric.py", line 15,
>> in <module>
>>     raise ImportError( """No Numeric module present: %s"""%(err))
>> ImportError: No Numeric module present: No module named Numeric
This can be ignored, there are no "python-numeric" packages available,
and this causes this warning in PyOpenGL.

>> 2013-08-16 18:27:24,161 OpenGL Version: 3.0 Mesa 8.0.4
>> 2013-08-16 18:27:24,179 GL Extension GL_ARB_shader_objects available
>> 2013-08-16 18:27:24,194 GL Extension GL_ARB_framebuffer_object available
>> 2013-08-16 18:27:24,196 GL Extension GL_ARB_fragment_program available
>> 2013-08-16 18:27:24,196 GL Extension GL_ARB_texture_rectangle available
>> 2013-08-16 18:27:24,197 GL Extension GL_ARB_vertex_program available
>> 2013-08-16 18:27:28,005 Attached to ssh:reorx:1 (press Control-C to detach)
>> On one instance of the client side abort (in this case, it happened when I
>> tried to open the Session Info window), I saw:
>> The program 'Xpra' 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 7628 error_code 9 request_code 137 minor_code 4)
>>   (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.)
>> Any suggestions? Anything else I can provide to help narrow this down?
Please try --no-opengl and see if that fixes most of your problems.
If so, please post the output of:
So we can blacklist the offending drivers - though I am tempted to just
blacklist all Ubuntu releases and give up on supporting that platform.


>> --
>> -- Doug Doole
>> aibohphobia - The irrational fear of palindromes

More information about the shifter-users mailing list