[Parti-discuss] Xpra + scroll wheel

[Nathaniel Smith]

2009/3/2 Ethan <notethan at gmail.com>:
> log is attached. the last bit (the relevant bit?) is:
> got ['button-action', 1, 5, 1, [39, 94], []]
> current mask: set([]), wanted: set([])
> Gdk-ERROR **: The program 'xpra' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadValue (integer parameter out of range for operation)'.
>   (Details: serial 455 error_code 2 request_code 131 minor_code 2)
>   (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.)
> aborting...

Ugh -- it looks like your Xvfb (or your Xvfb's XTest extension) thinks
that mice have only 3 buttons. (X treats mouse wheels as "extra
buttons".)

Can you test the attached patch? With it applied (on the server side),
then using the wheel *should* no longer crash your session. (And you
should see a nice warning in your .log file.) However, the mouse wheel
still won't *work*, it will just be ignored. I'm not sure if there's
any magic incantation that will convince Xvfb to accept mouse wheel
events -- does anyone know? Do mouse wheels work for anyone else? (I
don't have any wheel mice handy to test.)

What does 'xdpyinfo | head' say when run against the xpra server?
(I.e., 'DISPLAY=:36 xpydinfo | head'.)

-- Nathaniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: catch-fake-button-errors.diff
Type: text/x-diff
Size: 1457 bytes
Desc: not available
URL: <http://lists.partiwm.org/pipermail/parti-discuss/attachments/20090302/b93012bc/attachment.diff>