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 upWindow disabled until popup is closed, but doesn't keep popup above self. #3959
Comments
andrewdavidwong
added
bug
C: qubes-manager
UX
labels
Jun 6, 2018
andrewdavidwong
added this to the Release 4.0 updates milestone
Jun 6, 2018
andrewdavidwong
assigned
marmarta
Jun 6, 2018
marmarta
referenced this issue
in QubesOS/qubes-manager
Jun 12, 2018
Merged
Fixed a bug with warnings not modal in VM Settings #96
marmarek
closed this
in
marmarek/qubes-manager@8de2641
Jun 13, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
qubesos-bot
Jun 27, 2018
Automated announcement from builder-github
The package qubes-manager-4.0.18-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
qubesos-bot
commented
Jun 27, 2018
|
Automated announcement from builder-github The package
|
qubesos-bot
added
the
r4.0-dom0-cur-test
label
Jun 27, 2018
qubesos-bot
referenced this issue
in QubesOS/updates-status
Jun 27, 2018
Closed
manager v4.0.18 (r4.0) #563
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
RefinedSoftwareLLC commentedJun 5, 2018
•
edited
Edited 3 times
-
RefinedSoftwareLLC
edited Jun 5, 2018 (most recent)
-
RefinedSoftwareLLC
edited Jun 5, 2018
-
RefinedSoftwareLLC
edited Jun 5, 2018
-
RefinedSoftwareLLC
created Jun 5, 2018
Qubes OS version:
Qubes release 4.0 (R4.0)
I also used:
$ sudo qubes-dom0-update --enablerepo=qubes-dom0-security-testing
Affected component(s):
GUI of dom0 and Qube Manager
Steps to reproduce the behavior:
Open qube settings. Change qube networking to n/a. Apply changes. Open "Firewall rules" tab. A popup "[Dom0] Qube configuration problem!" should appear. Click past it onto the Settings window. The popup gets moved behind, while the Settings window refuses to register any interaction until the hidden popup is closed.
This shows the bug. Any window that requires a popup to be closed before continuing, should never allow that popup to be below the window.
For more info on weird behavor: Rearrange the windows so that the popup is only half behind the Settings window. Clicking on the popup still has it behind the Settings window. Now click on another VM. Then click directly on the popup. It finally shows in front of the Settings window. But if you click on the Settings window then the popup, the popup refuses to be displayed above the Settings window.
Expected behavior:
Any window that refuses all interactions until a popup is closed, should never allow that popup to be below itself. Clicking on the Window should bring the popup to the top of all windows and focus the popup.
Actual behavior:
See "Steps to reproduce the behavior"
General notes:
Related issues: