From 4bc755033b9525eeaf8eb5b1c1d71411ca8660dc Mon Sep 17 00:00:00 2001 From: kimsmi Date: Fri, 14 Mar 2025 11:11:11 -0400 Subject: [PATCH 1/3] gui-troubleshooting.md: Improve the section about external screens I was affected by this problem. When I saw this documentation, I didn't realize this was the problem affecting me. I don't have a 4K monitor; I have a wide monitor. I can click on most things, just not in specific sections of the screen. Rewrite to be more generic. --- user/troubleshooting/gui-troubleshooting.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/user/troubleshooting/gui-troubleshooting.md b/user/troubleshooting/gui-troubleshooting.md index a2761396..689990df 100644 --- a/user/troubleshooting/gui-troubleshooting.md +++ b/user/troubleshooting/gui-troubleshooting.md @@ -6,16 +6,22 @@ ref: 233 title: GUI troubleshooting --- -## Can't click on anything after connecting 4k external display +## Can't click on parts of screens after connecting high-resolution external display -When you connect a 4K external display, you may be unable to click on anything but a small area in the upper-right corner. +When you connect a high-resolution external display, you may be unable to click on parts of the screen. When a qube starts, a fixed amount of RAM is allocated to the graphics buffer called video RAM. This buffer needs to be at least as big as the whole desktop, accounting for all displays that are or will be connected to the machine. By default, it is as much as needed for the current display and an additional full HD (FHD) display (1920×1080 8 bit/channel RGBA). -This logic fails when the machine has primary display in FHD resolution and, after starting some qubes, a 4K display is connected. +This logic fails when the machine has primary display in FHD resolution and, after starting some qubes, a high-resolution display is connected. If the buffer is too small, and internal desktop resize fails. +To determine if this is the problem affecting you, look at the Xorg log inside the Qube at `/home/user/.local/share/xorg/Xorg.0.log` for lines like the following: + +~~~ +[ 1623.988] (EE) DUMMYQBS(0): Unable to set up a virtual screen size of 3440x1440 with 17101 Kb of video memory available. Please increase the video memory size. +~~~ + The solution to this problem is to increase the minimum size of the video RAM buffer, as explained in [GUI Configuration](/doc/gui-configuration/#video-ram-adjustment-for-high-resolution-displays). ## Screen blanks / Weird computer glitches like turning partially black or black boxes From 1e9029ac7d23588d4c7a0f0deda0d3f2e422303e Mon Sep 17 00:00:00 2001 From: kimsmi Date: Fri, 14 Mar 2025 11:16:22 -0400 Subject: [PATCH 2/3] Improve phrasing --- user/troubleshooting/gui-troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/user/troubleshooting/gui-troubleshooting.md b/user/troubleshooting/gui-troubleshooting.md index 689990df..819b7e6b 100644 --- a/user/troubleshooting/gui-troubleshooting.md +++ b/user/troubleshooting/gui-troubleshooting.md @@ -6,7 +6,7 @@ ref: 233 title: GUI troubleshooting --- -## Can't click on parts of screens after connecting high-resolution external display +## Can't click on parts of the screen after connecting high-resolution external display When you connect a high-resolution external display, you may be unable to click on parts of the screen. From 8db0e634b390c7bef3704c54c161e5d9311e8c6a Mon Sep 17 00:00:00 2001 From: Corey Ford Date: Tue, 18 Mar 2025 19:12:09 +0100 Subject: [PATCH 3/3] firewall: reword DNS resolution note --- user/security-in-qubes/firewall.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/user/security-in-qubes/firewall.md b/user/security-in-qubes/firewall.md index a94f087a..5df80b5c 100644 --- a/user/security-in-qubes/firewall.md +++ b/user/security-in-qubes/firewall.md @@ -40,8 +40,8 @@ If the qube is running, you can open Settings from the Qube Popup Menu. ICMP and DNS are not accessible in the GUI, but can be changed via `qvm-firewall` described below. Connections to Updates Proxy are not made over a network so can not be allowed or blocked with firewall rules, but are controlled using the relevant policy file (see [R4.x Updates proxy](/doc/software-update-vm/) for more detail). -Note that if you specify a rule by DNS name it will be resolved to IP(s) *at the moment of applying the rules*, and not on the fly for each new connection. -This means it will not work for servers using load balancing, and traffic to complex web sites which draw from many servers will be difficult to control. +Note that if you specify a rule by DNS name it will be resolved to IP(s) *at the moment the rules take effect* (including each time the qube or netvm starts), and not on the fly for each new connection. +This means it will not work reliably for servers that have different IPs at different times as a result of DNS-based load balancing. Instead of using the firewall GUI, you can use the `qvm-firewall` command in Dom0 to edit the firewall rules by hand. This gives you greater control than by using the GUI.