Bug 1196 - Cannot interact with block mode buttons on primary monitor
Status:
RESOLVED DUPLICATE
Component:
Core :: UNIX
Version:
1.10
Hardware:
All All
Importance:
P5 normal
Target Milestone:
---
Assignee:
Rob Caelers
URL:
Depends on:
Blocks:
Reported:
Feb 25 2015 23:55:59 UTC
by:
azizLIGHT
Modified:
Dec 23 2015 18:38:42 UTC
CC List:
bu**@wo**.net
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| bu**@wo**.net | Mar 4 2015 12:45:36 UTC | cc | bu**@wo**.net | |
| Rob Caelers | Dec 23 2015 18:38:42 UTC | status | NEW | RESOLVED |
| resolution | DUPLICATE |
Description
azizLIGHT Feb 25 2015 23:55:59 UTC
Version: workrave 1.10.6.0-ppa2~trusty2 Source: ppa:rob-caelers/workrave OS: Ubuntu 14.04 LTS x64 Issue: In a dual monitor setup, cannot interact with block mode buttons (Lock/Skip/Postpone) on primary monitor. Primary monitor is physically on the right and set primary via xrandr and ~/.config/monitors.xml Buttons can be interacted with on non-primary monitor (physical left monitor) Is this because workrave is only accepting input only from a monitor which has 0x0 coordinates (my left monitor)? Possible solution: 1) Accept input for block mode buttons on all monitors. 2) Accept interaction for block mode button on primary monitor
Comment 1
azizLIGHT Mar 4 2015 03:25:48 UTC
I have found out that you can interact with the block mode buttons on the primary right monitor in dual display setup, using a workaround. If you move your mouse temporarily from the right monitor to the left monitor, you can interact with the block mode buttons on the right monitor. Sometimes I keep my left monitor off and because of this bug I couldn't interact with the block mode buttons unless I turned the left monitor on. With this workaround, I can keep the monitor off, and just move the mouse left and back to the right and be able to click the buttons. Though there is this workaround that works for me, I'm not sure it would work for other people who have larger number of displays. It might be difficult for them to do this, and they may need to be able to interact with block mode buttons on the monitor of their choice.
Comment 2
bu**@wo**.net Mar 4 2015 12:45:36 UTC
The subject line of this bug is inaccurate as it does not matter if the monitor is "primary" or not. Please see bug #1199.
Comment 3
Rob Caelers Dec 23 2015 18:38:42 UTC
Marking this one as duplicate for 1199. I will se what I can do. Unfortunately, I don't have a multi head linux setup anymore. *** This bug has been marked as a duplicate of bug 1199 ***