I’m trying multiple displays for the first time. On my third one the mouse cursor cannot interact with anything in a qube. It is able to click and drag a window but nothing else. Feels like a bug but i’m not sure. The third monitor is rotated to the left to be used for my IDE.
dom0 windows respond to clicks but nothing else does. Feels like a bug. Lmk if anyone has experienced something similar
Hi Nika
Does this:
look like a solution to your problem?
it does. I did not troll the forum hard enough. whoops
I lied it doesnt I tried it and get this
sed: cant read : No such file or directory
Hi Nika
Are you willing to share the command you tried to run?
I tried this one because it matched my use case. I have one external working great as an extended display for my laptop. It’s when a third display is added that things get weird. I have one display connected hdmi to hdmi. The other is USB C to hdmi. On that third display is where the mouse cannot interact at all with anything inside the app vm
qvm-features dom0 gui-videoram-min $(xrandr --verbose | grep "Screen 0" | sed -e 's/.*current //' -e 's/\,.*//' | awk '{print $1*$3*4/1024}')
H Nika
So it’s the calculation of the size, that fails … not the actual “set the gui-videoram-min”?
Can you try manually calculating the maximum $WIDTH and $HEIGHT you’ll need … and then try the:
qvm-features dom0 gui-videoram-min $(($WIDTH * $HEIGHT * 4 / 1024))
qvm-features dom0 gui-videoram-overhead 0
Sorry I’m a little confused. For $WIDTH and $HEIGHT am I taking the literal W and H in inches and inputting them into that command?
Also this could be incredibly silly of me but should i run that command with the third display plugged in?
Hi Nika
The $WIDTH and $HIGHT is the resolution of the desktop you want.
The command xrandr --verbose should (among other things) give you the values for your [current layout] … can you try these commands (and share the output)?
xrandr --verbose | grep "Screen 0"
xrandr --verbose | grep "Screen 0" | sed -e 's/.*current //' -e 's/\,.*//'
Note: I’ve never tried/needed to rotate a monitor, so I’m partially guessing …
Edit: re-reading what I had typed, missed a few words …
Sorry for the delay yesterday got hectic
$ xrandr --verbose | grep "Screen 0"
Screen 0: minimum 64 x 64, current 2560 x 2640, maximum 32767 x 32767
$ xrandr --verbose | grep "Screen 0" | sed -e 's/.*current //' -e 's/\,.*//'
2560 x 2640
Hi Nika
Thanks – did it work with:
qvm-features dom0 gui-videoram-min 26400
qvm-features dom0 gui-videoram-overhead 0
where 26400 is based on:
echo "2560 * 2640 * 4 / 1024" | bc
?
it’s working right now without running
qvm-features dom0 gui-videoram-min 26400
qvm-features dom0 gui-videoram-overhead 0
which is confusing to me. but im currently able to click in qubes
Still not working. now my laptop screen doesnt respond to clicks
The correct output from dom0 was actually this
Screen 0: minimum 320 x 200, current 5120 x 2640, maximum 16384 x 16384
so the correct number is actually 52800 and even with inputting
qvm-features dom0 gui-videoram-min 52800
qvm-features dom0 gui-videoram-overhead 0
It still doesnt work at all no matter what orientation the screen is in
^ the above is a lie. Just needed to reboot apparently. When I plugged the third monitor in this morning it worked as inteded in both orientations. thank you so much @ChrisA
Hi Nika
I’m happy that it worked!
– since I hadn’t tried it myself, it was a lot of guess/assumption.