[Parti-discuss] Xpra + scroll wheel

[Ethan]

Yes, now it doesn't crash and I get
Failed to pass on (un)press of mouse button 5 (perhaps your Xvfb does  
not support mousewheels?)
in the log.

The mousewheel does work fine normally (when not going through xpra).

xdpyinfo says:
name of display:    :37.0
version number:    11.0
vendor string:    The X.Org Foundation
vendor release number:    10300000
X.Org version: 1.3.0
maximum request size:  16777212 bytes
motion buffer size:  256
bitmap unit, bit order, padding:    32, LSBFirst, 32
image byte order:    LSBFirst
number of supported pixmap formats:    6
supported pixmap formats:
     depth 1, bits_per_pixel 1, scanline_pad 32
     depth 4, bits_per_pixel 8, scanline_pad 32
     depth 8, bits_per_pixel 8, scanline_pad 32
     depth 16, bits_per_pixel 16, scanline_pad 32
     depth 24, bits_per_pixel 32, scanline_pad 32
     depth 32, bits_per_pixel 32, scanline_pad 32
keycode range:    minimum 8, maximum 255
focus:  window 0x400020, revert to Parent


Ethan


On 2009-03-03, at 02:02, Nathaniel Smith wrote:

> 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
> <catch-fake-button-errors.diff>