New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 780612 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

xwayland doesn't handle scaling properly

Project Member Reported by smbar...@chromium.org, Nov 1 2017

Issue description

xwayland gets the host native resolution instead of the effective resolution, so on eve at 1200x800 we only see the upper left quadrant of the screen. Changing CrOS to "native" 1x resolution does show the full desktop, though.
 
Screenshot 2017-11-01 at 14.01.22.png
762 KB View Download
Ah the screenshot is meant to illustrate that my xterm spawned in the middle of the huge X screen.
This looks like a bug in Xwayland. Xwayland uses the full resolution reported as mode in wl_output events but ignores the devices scale factor.

https://cgit.freedesktop.org/xorg/xserver/tree/hw/xwayland/xwayland.c#n607 should probably be updated to take the value from https://cgit.freedesktop.org/xorg/xserver/tree/hw/xwayland/xwayland-output.c#n241 into account.

However, it might be more useful just be able to specify the resolution and scale factor directly when starting Xwayland in non-rootless mode.

Would also be nice to have it use the aura-shell protocol for chrome side decorations.
Status: WontFix (was: Unconfirmed)
Actually, using Xwayland directly is not a good idea. It only works well in rootless mode. You want to use something like:

weston --backend=wayland-backend.so

have have a weston.ini file with:
[core]
modules=xwayland.so
Components: OS>Systems>Containers

Sign in to add a comment