Cursor becomes visible by itself when an external monitor is connected
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
Medium
|
Alan Griffiths | ||
mir (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Steps to reproduce:
-------
1 - Build and install the following branches on a laptop:
lp:~dandrader/unity-api/mousePointer
lp:~dandrader/qtmir/multimonitorNext
lp:~dandrader/unity8/externalMonitor
2 - In lightdm greeter, log into a unity8 session
3 - connect an external monitor
Expected outcome:
-------
You see only one cursor (the one unity8 draws)
Actual outcome:
-------
You see two cursors: the unity8 one and the mir one.
Comments:
------------------
In qtmir's mir::Server class, this is the snippet it uses to hide the mir cursor:
"""
add_init_
"""
The mir cursor remains visible also after you unplug the external monitor.
Related branches
- Kevin DuBois (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 242 lines (+130/-68)1 file modifiedtests/acceptance-tests/test_nested_mir.cpp (+130/-68)
tags: | added: cursor multimonitor |
Changed in mir: | |
milestone: | none → 0.17.0 |
status: | Triaged → In Progress |
assignee: | nobody → Alan Griffiths (alan-griffiths) |
Changed in mir: | |
status: | Fix Committed → Fix Released |
I don't think this is a reliable way to hide the cursor.: there are lots of events that will cause a call to cursor->show() which will make the cursor reappear.
If you don't want to use the Mir cursor at all it is probably better to call override_ the_cursor( ) with a stub implementation.
Having said that, there should be a way to temporarily hide the cursor.