You are not logged in.
Most XWayland applications are not actually blurry, but rather running on a lower resolution. Is it possible to change zxdg_output_manager_v1 - which I think it's the output to Xwayland applications, to also run on the same resolution as Wayland even if it means no scaling?
$ wayland-info
interface: 'wl_output', version: 2, name: 5
x: 0, y: 0, scale: 2,
physical_width: 700 mm, physical_height: 380 mm,
make: 'GSM', model: 'Samsung HDR 4K',
subpixel_orientation: unknown, output_transform: normal,
mode:
width: 3840 px, height: 2160 px, refresh: 59.996 Hz,
flags: current preferred
interface: 'zxdg_output_manager_v1', version: 3, name: 6
xdg_output_v1
output: 5
name: 'DP-1'
description: 'Samsung Electronics 34"'
logical_x: 0, logical_y: 0
logical_width: 1920, logical_height: 1080Offline
First zxdg_output_manager_v1 is not for xwayland. It is an experimental wayland protocol for managing different outputs somewhat analogous to information provided by RandR on X11 (e.g., xrandr being the most known implementation).
Xwayland is just a concept of running a X11 server nested as a wayland client under a compositor. There is no actual definition of a protocol for this, so the details of the implementation are entirely up to the compositor or the Xwayland program itself. If your compositor allows you to specify options to pass to the Xwayland server, that is likely your best bet for addressing your concerns.
So which compositor is this?
EDIT: perhaps you were assuming it was for X11 due to the "xdg_output_v1" nexted under it, but that "xdg" is in reference to the xdg-shell protocol not to x11. The xdg-shell protocol is what all native wayland "windows" are using to communicate with the compositor (excluduing docks / backgrounds / dekstops which use the layer-shell protocol ... but just the same nothing to do with X11).
EDIT 2: perhaps this will be helpful:
https://www.reddit.com/r/swaywm/comment … _monitors/
Last edited by Trilby (2022-03-21 01:20:15)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
First zxdg_output_manager_v1 is not for xwayland. It is an experimental wayland protocol for managing different outputs somewhat analogous to information provided by RandR on X11 (e.g., xrandr being the most known implementation).
Xwayland is just a concept of running a X11 server nested as a wayland client under a compositor. There is no actual definition of a protocol for this, so the details of the implementation are entirely up to the compositor or the Xwayland program itself. If your compositor allows you to specify options to pass to the Xwayland server, that is likely your best bet for addressing your concerns.
So which compositor is this?
EDIT: perhaps you were assuming it was for X11 due to the "xdg_output_v1" nexted under it, but that "xdg" is in reference to the xdg-shell protocol not to x11. The xdg-shell protocol is what all native wayland "windows" are using to communicate with the compositor (excluduing docks / backgrounds / dekstops which use the layer-shell protocol ... but just the same nothing to do with X11).
EDIT 2: perhaps this will be helpful:
https://www.reddit.com/r/swaywm/comment … _monitors/
Thanks for explaining the details about xdg.
--force-device-scale-factor=and using scaling factors on fonts did it for some electrum apps. I was actually using this with X11, but switched to scaling factor after running on Wayland - I guess it's not time YET to run Wayland smoothly, although it's possible to use as a daily driver.
Qbittorrent and Wine applications are still a mistery, as they do not scale fonts nor take
--force-device-scale-factor=as parameter
Edit:
QT_SCALE_FACTOR=2as env variable (/etc/environment, ~/.bashrc) solved for QBit
Last edited by fastrespawn (2022-03-22 17:30:01)
Offline