Wayland boot loop on KDE Plasma

Desktop Environments Plasma
1

Can not boot into Wayland unless I drop down to tty3 and run systemctl restart sddm.
Fresh install on different computers all seem to have the same problem and restarting sddm in tty seems to be a work around for now. Hoping one of you good folks here can lead me down the path to success.

[sam@sam ~]$ echo $XDG_SESSION_TYPE
wayland
[sam@sam ~]$

#################### inxi -Fxxc0z ########################

System:
  Kernel: 6.6.7-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 13.2.1 Desktop: KDE Plasma
    v: 5.27.10 tk: Qt v: 5.15.11 wm: kwin_wayland dm: SDDM Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Laptop System: TOSHIBA product: Satellite L650 v: PSK1E1-1234567
    serial: <superuser required>
  Mobo: TOSHIBA model: Portable PC serial: <superuser required> BIOS: INSYDE v: 2.40
    date: 11/09/2011
Battery:
  ID-1: BAT0 charge: 35.8 Wh (100.0%) condition: 35.8/47.5 Wh (75.2%) volts: 10.8 min: 10.8
    model: PA381 serial: <filter> status: full
CPU:
  Info: dual core model: Intel Core i5 M 480 bits: 64 type: MT MCP arch: Westmere rev: 5 cache:
    L1: 128 KiB L2: 512 KiB L3: 3 MiB
  Speed (MHz): avg: 1716 high: 2572 min/max: 1199/2667 boost: enabled cores: 1: 2572 2: 1414
    3: 1302 4: 1579 bogomips: 21342
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Core Processor Integrated Graphics vendor: Toshiba driver: i915 v: kernel
    arch: Gen-5.75 ports: active: LVDS-1 empty: DP-1,HDMI-A-1,VGA-1 bus-ID: 00:02.0
    chip-ID: 8086:0046
  Display: wayland server: X.org v: 1.21.1.10 with: Xwayland v: 23.2.3 compositor: kwin_wayland
    driver: X: loaded: modesetting alternate: fbdev,intel,vesa dri: crocus gpu: i915 display-ID: 0
  Monitor-1: LVDS-1 res: 1366x768 size: N/A
  API: EGL v: 1.5 platforms: device: 0 drv: crocus device: 1 drv: swrast surfaceless: drv: crocus
    wayland: drv: crocus x11: drv: crocus inactive: gbm
  API: OpenGL v: 4.5 compat-v: 2.1 vendor: intel mesa v: 23.2.1-arch1.2 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel HD Graphics (ILK) device-ID: 8086:0046 display-ID: :1.0
  API: Vulkan Message: No Vulkan data available.
Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Toshiba 5
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56
  API: ALSA v: k6.6.7-arch1-1 status: kernel-api
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
  Device-1: Qualcomm Atheros AR8152 v1.1 Fast Ethernet vendor: Toshiba driver: atl1c v: kernel
    pcie: speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0 chip-ID: 1969:2060
  IF: enp1s0 state: down mac: <filter>
  Device-2: Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver: rtl8192ce v: kernel pcie:
    speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 02:00.0 chip-ID: 10ec:8176
  IF: wlan0 state: up mac: <filter>
  IF-ID-1: sammiev_L650 state: unknown speed: N/A duplex: N/A mac: N/A
Drives:
  Local Storage: total: 232.89 GiB used: 7.94 GiB (3.4%)
  ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB speed: 3.0 Gb/s
    serial: <filter>
Partition:
  ID-1: / size: 228.17 GiB used: 7.94 GiB (3.5%) fs: ext4 dev: /dev/sda1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 55.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 181 Uptime: 40m Memory: total: 8 GiB available: 7.56 GiB used: 2.01 GiB (26.6%)
  Init: systemd v: 255 default: graphical Compilers: gcc: 13.2.1 Packages: pm: pacman pkgs: 938
  Client: shell wrapper v: 5.2.21-release inxi: 3.3.31
2

What about ltskernel? Same issue?
I see you are using a fresh installation. I already had problems with Plasmoids under Wayland which were not updated.

1 Like
3

I’m sure that I tried the lts kernel but did a fresh install after trying everything including the kitchen sink, just installed the lts kernel and the problem remains.
Many thanks for your assistance.

1 Like
4

Able to boot into Wayland now without having to drop into tty by creating 10-wayland.conf

/etc/sddm.conf.d/10-wayland.conf

[General]
DisplayServer=wayland
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell

Will not mark this as a solution yet as I may change things around a little.

3 Likes
5

Are you by any chance, using autologin into plasma-wayland session?

If adding the following config works:

/etc/sddm.conf.d/10-wayland.conf
----

[General]
DisplayServer=wayland
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell

[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1

Then, its most probably because sddm runs in x11, and therefore wayland session is launched in separate tty and the switch between ttys is not made successfully each time.

3 Likes
6

Thanks for the reply, no I’m not using autologin. The only lines in 10-wayland.conf are

1 Like
7

Also add the following as a parameter to CompositorCommand into the SDDM config /etc/sddm.conf.d/10-wayland.conf:

[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1
4 Likes
8

I will certainly give it a try, post back shortly.

1 Like
9

@ainz I will mark your post as the solution as they both work, yours is likely the better way.
Many Thanks !

PS you can work on my truck any time. :rofl:

4 Likes