hidpi: How do AppVMs and Template/SysVMs get the screen dpi

73 views
Skip to first unread message

Torsten Sadowski

unread,
Jul 25, 2017, 5:57:48 PM7/25/17
to qubes...@googlegroups.com
Hi,

I am wondering how the dpi information is passed from dom0 to domU. I
did adjust the settings as best as I could in dom0 and some things
simply work, but there is also erratic behaviour and some things don't work.

AppVMs mostly work as can be seen at the untrusted terminal. But Firefox
behaves erratic and is too large if it is the application that launches
the AppVM. Firefox is fine when I close it and open it again without
shutting down the AppVM.

The TemplateVMs and SysVMs have always very tiny displays. That is
usable for terminals (Ctrl+++) but annoying for sys-net because the
network settings are tiny as well.

I am baffled why this is, especially why the AppVMs work. xrandr has the
same output for App / Template / SysVMs. Why are the Apps behaving
differently. And is there a way to transmit the detected screen size
from dom0 to all domUs?

Is there a possibility to change the font and icon size inside the Qubes VM Manager?

Any hints are appreciated.


Cheers,

Torsten


hidpi.png

tsad...@gmx.net

unread,
Jul 26, 2017, 5:51:10 PM7/26/17
to qubes-users
Update

I changed Xft.dpi in /etc/X11/Xresources to a more reasonable value and this solved most of the problems for Template/Sys-VMs. Firefox is still erratic and DispVMs are still tiny. For some strange reason the Xresources don't find their way into xrdb.

Cheers,
Torsten

tsad...@gmx.net

unread,
Aug 7, 2017, 4:41:30 PM8/7/17
to qubes-users
Well, the display size reported by xrandr is correct for 200 dpi but xdpyinfo reports 96 x 96.

I did put
xrandr --fbmm XxY
in
/etc/X11/xinit/xinitrc-common
and now xdpyinfo reports the right resolution, but the DispVM has still a tiny Firefox.

Cheers,
Torsten

Reply all
Reply to author
Forward
0 new messages