Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upChanging screen resolution makes domU elements in bottom half of screen noninteractive #2421
Comments
andrewdavidwong
added
bug
C: gui-virtualization
labels
Nov 7, 2016
andrewdavidwong
added this to the Release 3.2 milestone
Nov 7, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
cyrinux
Nov 7, 2016
Hi, I have similar problem since about 3 weeks. (I update all everyday). I
use two work with 2 screens horizontally. When I two screen, I can't click
anymore on the right screen. I used i3wm.
On Mon, 7 Nov 2016, 04:34 Andrew David Wong, notifications@github.com
wrote:
Qubes OS version (e.g., R3.1):
R3.2
Affected TemplateVMs (e.g., fedora-23, if applicable):
On 2016-11-06 14:34, yaqu wrote:
https://groups.google.com/d/msgid/qubes-users/20161106223414.10544103B33%40mail2.openmailbox.orgWhen I
change resolution from lower to higher, some icons in tray at the
bottom of the screen are not accessible - no tooltip on hoover, no
response to click. It looks like only icons of appVM apps are affected
(NetworkManager, Psi, Remmina, KeePass...), and icons of dom0 apps work
correctly (volume control, power manager, qubes manager). Tray needs to
be on bottom of screen, of course.I have found out that to make these icons work again, I have to switch
on or off any of connected displays.This issue can be reproduced even without external monitors. Assuming
laptop's LCD is on LVDS1, one needs to switch it to some low resolution
and then back to default:[user@dom0 ~]$ xrandr --output LVDS1 --mode "800x600"; sleep 3; xrandr
--output LVDS1 --autoNow icons are not accessible. To fix it one needs to turn LCD off and
on:[user@dom0 ~]$ xrandr --output LVDS1 --off; xrandr --output LVDS1 --auto
BTW now as I tested it, it looks that not only tray icons are not
accessible. The bottom half of the screen is not clickable for appVM
applications.
Related issues:
#1599 #1599 (might not be
closely related)—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#2421, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAfrq9wMpmLERLVXnzjSLrDSEYLAHSyqks5q7pw5gaJpZM4Kqztm
.
cyrinux
commented
Nov 7, 2016
|
Hi, I have similar problem since about 3 weeks. (I update all everyday). I On Mon, 7 Nov 2016, 04:34 Andrew David Wong, notifications@github.com
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
cyrinux
commented
Nov 17, 2016
|
Yes @andrewdavidwong it is that ;) |
marmarek
modified the milestones:
Release 3.2,
Release 3.2 updates
Nov 19, 2016
marmarek
closed this
in
marmarek/old-qubes-gui-daemon@a2e1220
Nov 19, 2016
added a commit
to QubesOS/qubes-gui-daemon
that referenced
this issue
Nov 19, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Nov 26, 2016
Member
Automated announcement from builder-github
The package qubes-gui-dom0-3.2.7-1.fc23 has been pushed to the r3.2 testing repository for dom0.
To test this update, please install it with the following command:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
|
Automated announcement from builder-github The package
|
marmarek
added
the
r3.2-dom0-cur-test
label
Nov 26, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesos-bot
Jan 8, 2017
Automated announcement from builder-github
The package qubes-gui-dom0-3.2.8-1.fc23 has been pushed to the r3.2 stable repository for dom0.
To install this update, please use the standard update command:
sudo qubes-dom0-update
Or update dom0 via Qubes Manager.
qubesos-bot
commented
Jan 8, 2017
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
andrewdavidwong commentedNov 7, 2016
Qubes OS version (e.g.,
R3.1):R3.2
Affected TemplateVMs (e.g.,
fedora-23, if applicable):On 2016-11-06 14:34, yaqu wrote:
Related issues:
#1599 (might not be closely related)