Bug 202854 - x11/xorg: On 10.2-RELEASE and laptops Lenovo X220, X201 after suspend via zzz and resume under X11 mouse is frozen
Summary: x11/xorg: On 10.2-RELEASE and laptops Lenovo X220, X201 after suspend via zzz...
Status: Closed DUPLICATE of bug 200938
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-x11 (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-02 18:36 UTC by Kurt Jaeger
Modified: 2016-07-08 12:27 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kurt Jaeger freebsd_committer freebsd_triage 2015-09-02 18:36:55 UTC 
Problem: On FreeBSD-10.2 amd64, with very recent ports, if I startx, suspend using
zzz, and resume afterwards, the mouse pointer is no longer available.

It helps to stop X and restart X. On the X220, the hald sometimes needs to
be restarted as well (not always).
Comment 1 Thomaz 2015-09-03 05:59:01 UTC 
Same with X230. Restarting moused brings it back.
Comment 2 rkoberman 2015-09-03 16:49:29 UTC 
Try adding:
hint.psm.0.flags="0x6000"
to /boot/loader.conf
Comment 3 Kurt Jaeger freebsd_committer freebsd_triage 2015-09-03 17:19:48 UTC 
This worked: Deactivate hald in /etc/rc.conf, use moused instead. Then,
after resume, restart moused, and the mouse comes back.

Now, how can the moused-restart be done automatically after resume ?

Kevin: Is the hint.psm.0.flags="0x6000" needed ? It did not change the
behaviour, only switching from hald to moused did change it.
Comment 4 Kurt Jaeger freebsd_committer freebsd_triage 2015-09-03 17:20:42 UTC 
There's a related PR:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200938
Comment 5 Kurt Jaeger freebsd_committer freebsd_triage 2015-09-03 17:44:47 UTC 
(In reply to Kurt Jaeger from comment #4)
The other PR contains a workaround, see comment #5. Closing this ticket as duplicate.

*** This bug has been marked as a duplicate of bug 200938 ***