Bug 108301 - Unresponsive mouse wheel and buttons after update to 1.13{,.1}
Summary: Unresponsive mouse wheel and buttons after update to 1.13{,.1}
Status: RESOLVED NOTOURBUG
Alias: None
Product: XCB
Classification: Unclassified
Component: Misc (show other bugs)
Version: 1.13.1
Hardware: Other All
: medium normal
Assignee: xcb mailing list dummy
QA Contact: xcb mailing list dummy
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-09 11:19 UTC by Paul Menzel
Modified: 2018-10-16 13:08 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log from X.Org X Server 1.20.1 (20.53 KB, text/plain)
2018-10-09 14:20 UTC, Paul Menzel
Details

Description Paul Menzel 2018-10-09 11:19:25 UTC
Updating to libxcb 1.13 (or 1.13.1), our user reports the problem below [1].

> When I update libxcb (only) to libxcb-1.13-0, restart the X-Server by 
> log-out/log-in, then use the mouse wheel to scroll a long firefox page, the
> mouse wheel and the mouse buttons suddenly become unresponsive (e.g. after 30
> seconds activity for 10 seconds). Typing any key immediately unfreezes the
> mouse.

With libxcb 1.13.1 and updated X.Org X Server 1.20.1 (I believe it is still built against libxcb 1.12) the problem persists.

Does the X server need to be rebuilt?

[1]: https://github.molgen.mpg.de/mariux64/bee-files/pull/926#issuecomment-6111
Comment 1 Michel Dänzer 2018-10-09 13:27:27 UTC
Please attach the corresponding Xorg log file.
Comment 2 Paul Menzel 2018-10-09 14:20:11 UTC
Created attachment 141961 [details]
Xorg.0.log from X.Org X Server 1.20.1
Comment 3 Uli Schlachter 2018-10-09 17:19:47 UTC
What are you updating from? libxcb 1.12?

If so, the only "actual code changes" (outside of generated code) are commits fad81b63422105f9345215ab2716c4b804ec7986 and f830eb93c9c38b2c6c7ea2971af3bc6a61e92277. The second one obviously cannot cause this and fad81b634... well, it shouldn't cause anything? But might expose latent bugs in something else.

Also possibly related: Does your user uses compton?
https://github.com/chjj/compton/issues/494
https://gitlab.freedesktop.org/xorg/lib/libx11/issues/79
Comment 4 Paul Menzel 2018-10-09 19:21:29 UTC
(In reply to Uli Schlachter from comment #3)
> What are you updating from? libxcb 1.12?

Yes, we are updating from libxcb 1.12.

> If so, the only "actual code changes" (outside of generated code) are
> commits fad81b63422105f9345215ab2716c4b804ec7986 and
> f830eb93c9c38b2c6c7ea2971af3bc6a61e92277. The second one obviously cannot
> cause this and fad81b634... well, it shouldn't cause anything? But might
> expose latent bugs in something else.

I guess we can test a revert of fad81b634 next week.

> Also possibly related: Does your user uses compton?
> https://github.com/chjj/compton/issues/494
> https://gitlab.freedesktop.org/xorg/lib/libx11/issues/79

No, we use Xfce 4.13 and xfwm 4.13 and no compton.
Comment 5 Michel Dänzer 2018-10-10 07:23:12 UTC
That libX11 bug affected other compositors like gnome-shell/mutter as well. It's probably worth testing if libX11 1.6.7 helps.
Comment 6 Paul Menzel 2018-10-16 13:08:14 UTC
(In reply to Michel Dänzer from comment #5)
> That libX11 bug affected other compositors like gnome-shell/mutter as well.
> It's probably worth testing if libX11 1.6.7 helps.

libX11 1.6.7 seems to have fixed this. No idea, why this problem doesn’t manifest with libX11 1.6.6 and libxcb 1.13.x.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.