Hi! I've come back to using Qubes on a HiDPI device again and getting into the same trap as always; even if I set the real resolution using Xresources (or .xsettingss) I'll end up with problems if I connect a different display to my machine. Getting rid of xsettingsd seems to be the wrong way, too.
The method that seems to be working under all circumstances (especially with multiple displays running at different resolutions seems to be nailing the necessary values into RANDR and XFT after all the sabotage has been done by GNOME, xfce4 or KDE. Would it be possible to extend VM launching after WaitForSession by one more RPC "FixTheBloodyResolution" that will get the horizontal size, vertical size and resolution followed by a stream of Xft database entries (from his .xresources or optionally .Xresources.vm in dom0) a user might want to have pushed down to xrdb. If someone wants to go the extra mile also followed by further data handed over into gsd- xsettingsd The result would be fed into xrandr and xrdb -merge by the client part of the rpc. I'm doing something similar locally right now using a script qvm-start-2 containing a qvm-start followed by qvm-run -u root launching xrandr and xrdb but I believe integrating it int VM launch would help everybody who is dealing with more than one display. Comments? Better ideas? Achim -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To post to this group, send email to qubes-devel@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/3824ffc94d41a548e330723e63f79ffaf9276c41.camel%40noses.com. For more options, visit https://groups.google.com/d/optout.
