Multi-monitor: Mousepointer hangs when passing between monitors, although no Launcher is there (regression)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Fix Released
|
Medium
|
Brandon Schaefer | ||
unity (Ubuntu) |
Fix Released
|
Medium
|
Brandon Schaefer |
Bug Description
[How to reproduce]
1. Have a dual screen left-right config, with the Launcher just visible on your main (left) monitor
2. Make your mousepointer move between first and second display multiple times
[What you would expect]
You should feel no barrier when doing that, as there is no Launcher on the right screen.
[What actually happens]
The mousepointer sometimes hangs, when moving between those screens (both directions are
affected, left->right && right->left).
Note: It always hangs once you stay longer than 1 second on each monitor.
It also starts blocking after one second if you move between your screens rapidly.
Workaround (without hacking the code):
Edit unityshell.xml (best copy it to ~/.compiz-
pointer will hang once in 250 hours/once every 10 days after the barrier has been broken.
Related branches
- Marco Trevisan (Treviño): Approve
- PS Jenkins bot: Pending (continuous-integration) requested
-
Diff: 246 lines (+104/-35)4 files modifiedlauncher/Launcher.cpp (+3/-1)
launcher/PointerBarrier.cpp (+30/-9)
launcher/PointerBarrier.h (+6/-0)
tests/test_pointer_barrier.cpp (+65/-25)
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
- Andrea Azzarone (community): Approve
-
Diff: 703 lines (+261/-152)8 files modifiedCMakeLists.txt (+2/-1)
debian/changelog (+4/-3)
debian/control (+1/-0)
launcher/EdgeBarrierController.cpp (+126/-3)
launcher/EdgeBarrierControllerPrivate.h (+9/-0)
launcher/PointerBarrier.cpp (+82/-94)
launcher/PointerBarrier.h (+7/-5)
tests/test_pointer_barrier.cpp (+30/-46)
description: | updated |
Changed in unity: | |
assignee: | nobody → Brandon Schaefer (brandontschaefer) |
Changed in unity: | |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in unity: | |
milestone: | none → 7.0.0 |
Changed in unity (Ubuntu): | |
status: | New → In Progress |
Changed in unity (Ubuntu): | |
assignee: | nobody → Brandon Schaefer (brandontschaefer) |
Changed in unity: | |
status: | In Progress → Fix Committed |
Changed in unity (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in unity: | |
status: | New → Fix Committed |
status: | Fix Committed → Fix Released |
status: | Fix Released → Fix Committed |
Changed in unity: | |
status: | Fix Committed → Fix Released |
description: | updated |
Changed in unity: | |
status: | Confirmed → Fix Released |
Changed in unity (Ubuntu): | |
status: | Confirmed → Fix Released |
I gotta reopen this bug report.
It was fixed (for a short time), but now this bug seems to be back again...