I have a VMware VM running linux on one screen of a 3 screen Windows 7 machine Under X11, in order to get a full screen 1920x1080 screen I have to create an Xorg.conf: Section "Monitor" Identifier "Default Monitor" UseModes "Default Modes" Option "PreferredMode" "1920x1080@60" EndSection Section "Modes" Identifier "Default Modes" modeline "1920x1080@60" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync EndSection Section "Device" Identifier "Default Device" Driver "vmware" Option "IgnoreEDID" "1" EndSection Section "Screen" Identifier "Default Screen" Monitor "Default Monitor" Device "Default Device" EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" EndSection If I don't specify this then 1920x1080 is missing (the closest to this is then 1680x1050 or 1920x1440) If however I start a Wayland session there doesn't appear to be a way to force 1080p Is there a wayland equivalent of Xorg.0.log?
We cannot workaround VMware issues.
Ignoring VMware, how does one specify a different mode on kwin_wayland?
That is outside the scope of KWin. Modes are reported by the drm subsystem. You need to check the capabilities the drm driver provides to add modes.
So the reason the 1080p resolution wasn't showing up was because CONFIG_DRM_VMWGFX_FBCON=y wasn't set in my kernel However now when my Wayland session starts at boot it takes up a small portion of the screen Under "Display and Monitor" it says the screen name is XWAYLAND0 and the resolution is 1024x768 and that field is not selectable /usr/libexec/Xorg -nolisten tcp -auth /var/run/sddm/{f44714bd-0d30-4035-a483-39ff732022cf} -background none -noreset -displayfd 17 -seat seat0 vt1 /usr/bin/Xwayland -displayfd 30 -rootless -wm 33 /usr/bin/kwin_wayland --xwayland --libinput --exit-with-session=/usr/lib64/libexec/startplasma If I logout and back in again it runs at 1080p and "Display and Monitor" says Virtual-1-unknown and I'm able to change resolutions I double checked the 2nd login was definitely running wayland: /usr/libexec/Xorg -nolisten tcp -auth /var/run/sddm/{9f9e7eba-e4ee-409e-98be-c0c4a3bc8039} -background none -noreset -displayfd 17 -seat seat0 vt1 /usr/bin/Xwayland -displayfd 40 -rootless -wm 43 /usr/bin/kwin_wayland --xwayland --libinput --exit-with-session=/usr/lib64/libexec/startplasma
Created attachment 113775 [details] First boot
Created attachment 113776 [details] After logout and back in again
Please don't reopen the report. Your systemsettings is started as an X11 application and due to that not offering to change resolution. Please use a proper Wayland session.
When the bug is resolved to my satisfaction I'll close the bug How does one start a proper Wayland session? Is starting Plasma (Wayland) from SDDM not enough?
Closing properly
Martin, you want people to switch to Wayland, you've made clear that X11 is in maintenance only How on earth are people supposed to use Wayland as a daily driver when switching causes issues? I realise this bug might now be in kwin_wayland itself - it could possibly be in SDDM or some other component, but currently when I first start this machine with wayland it does one thing and when I restart the session it does another - that I hope you can see is a bug You say start a proper wayland session but you don't say _how_ if I'm making a mistake, please point it out. I was under the impression that simply changing the default session in SDDM was enough
Sorry but bug reports are not user support forum. You reopened this report several times and when I asked you to not do this your reply was rather rude. I am personally not interested to spend any more time on it.
So what is the correct avenue to get this issue resolved?
DRM modes not being available, not kwin's scope. system settings not showing the right stuff first boot is interesting.. But it gets complex when a bug report ends up with two issues. Launching from sddm should be fine. You're clearly running in wayland. How did you start systemsettings? Is this on every reboot and reproducible? Can you type "env" in a terminal and paste output.
Created attachment 113794 [details] env first boot
Created attachment 113795 [details] env after logout and log back in
Here's the diff between the two diff -u0 env.firstboot env.restartedSession --- env.firstboot 2018-07-06 09:41:15.353376835 +0100 +++ env.restartedSession 2018-07-06 09:42:43.555992997 +0100 @@ -10 +10 @@ -SHELL_SESSION_ID=f09d54d32a4e41ff945d0d28cc031101 +SHELL_SESSION_ID=c15f0b195ead455bbde690e9f8782f6f @@ -16 +16 @@ -XDG_VTNR=1 +XDG_VTNR=2 @@ -20 +20 @@ -XDG_SESSION_ID=c1 +XDG_SESSION_ID=c3 @@ -29 +29 @@ -XDG_SESSION_TYPE=x11 +XDG_SESSION_TYPE=wayland @@ -36 +35,0 @@ -GTK_MODULES=canberra-gtk-module @@ -43 +42 @@ -KONSOLE_DBUS_SERVICE=:1.32 +KONSOLE_DBUS_SERVICE=:1.27 @@ -51,0 +51 @@ +QT_WAYLAND_DISABLE_WINDOWDECORATION=1 @@ -57 +57 @@ -WINDOWID=6291463 +WINDOWID=1 @@ -60 +60 @@ -DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-DDAQDmC9XR,guid=1afbe537d8aab7b3ed4a73575b3f2abc +DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-OTaCi1PozB,guid=80b520e5d9ec2cb030ce605c5b3f2b65 @@ -62,2 +62 @@ -XAUTHORITY=/home/fireburn/.Xauthority -XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0 +XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session2 @@ -70 +69 @@ -SESSION_MANAGER=local/sky.fireburn.co.uk:@/tmp/.ICE-unix/564,unix/sky.fireburn.co.uk:/tmp/.ICE-unix/564 +SESSION_MANAGER=local/sky.fireburn.co.uk:@/tmp/.ICE-unix/867,unix/sky.fireburn.co.uk:/tmp/.ICE-unix/867 I've not noticed when I first boot I can't VT switch, once I've logged out and back in again, Plasma is running on VT2 and VT1 is a black screen with an unthemed mouse cursor Also on the first boot on the part of the screen that's black, it I move the mouse there the mouse cursor is unthemed too
Created attachment 113796 [details] sddm.conf
-XDG_SESSION_TYPE=x11 +XDG_SESSION_TYPE=wayland Well here's our problem.. But this is set by SDDM...which means it's my bug. But I don't understand.
Would you like me to create a new bug for this issue? Could it be the auto logon doing something screwy?
On bootup, could it be that Wayland is starting before VT2 is setup/created? First boot: fireburn@sky ~ $ ps -ef | grep X root 405 379 1 11:18 tty1 00:00:00 /usr/libexec/Xorg -nolisten tcp -auth /var/run/sddm/{ea6c489d-82b5-4ba2-a0c8-d0fad97fe1ea} -background none -noreset -displayfd 17 -seat seat0 vt1 fireburn 467 463 4 11:18 ? 00:00:01 /usr/bin/Xwayland -displayfd 30 -rootless -wm 33 Restart Session: fireburn@sky ~ $ ps -ef | grep X root 712 379 1 11:17 tty1 00:00:00 /usr/libexec/Xorg -nolisten tcp -auth /var/run/sddm/{6e63afef-6365-4f51-8bb7-9f300774a7be} -background none -noreset -displayfd 17 -seat seat0 vt1 fireburn 780 775 2 11:17 tty2 00:00:00 /usr/bin/Xwayland -displayfd 40 -rootless -wm 43