Plasma won't start on Wayland

So since KDE Plasma is going to drop support for X11 I decided to give wayland another shot.
However, when I select Plasma (Wayland) and log in, I get a black screen for 1-2 seconds, and I am sent back to sddm.
After trying to start with Wayland, it won’t start with X11 either until I reboot.
I can manually start a Wayland session from X11 without issue.

Only once I achieved to log in with X11 after trying to do so with Wayland, and I ran journalctl -p 3 -xb where there were several core dumps and qt-related errors.

I suspect it might have something to do with my Nvidia graphics card.

Any help would be greatly appreciated.

Thank you in advance!

Kind regards,

All machines with Nvidia and wayland run flawlessly here.

So you may upload your journal to https://paste.opensuse.org/
Additionally post inxi -GSaz and zypper lr -d here.

Thanks for your answer. Unfortunately, I can’t seem to get the journal again. I can however, post the other things:

inxi:

System:
  Kernel: 6.18.0-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.18.0-1-default
    root=UUID=d6289511-6a12-4047-8a23-91b1e2d776cb splash=silent
    mitigations=auto quiet security=apparmor rd.driver.blacklist=nouveau
  Desktop: KDE Plasma v: 6.5.3 tk: Qt v: N/A info: frameworks v: 6.20.0
    wm: kwin_x11 tools: avail: xscreensaver vt: 2 dm: SDDM Distro: openSUSE
    Tumbleweed 20251204
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Lenovo
    driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
    ports: active: eDP-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:3e9b
    class-ID: 0300
  Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] vendor: Lenovo
    driver: nvidia v: 580.105.08 alternate: nouveau,nvidia_drm
    non-free: 550-580.xx+ status: current (as of 2025-11; EOL~2026-12-xx)
    arch: Pascal code: GP10x process: TSMC 16nm built: 2016-2021 pcie: gen: 3
    speed: 8 GT/s lanes: 16 ports: active: none empty: DP-1,DP-2,HDMI-A-1
    bus-ID: 01:00.0 chip-ID: 10de:1c8d class-ID: 0300
  Device-3: Bison SunplusIT Integrated Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-6:3 chip-ID: 5986:2113
    class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.21 with: Xwayland v: 24.1.8
    compositor: kwin_x11 driver: X: loaded: modesetting,nvidia alternate: intel
    dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 507x285mm (19.96x11.22")
    s-diag: 582mm (22.9")
  Monitor-1: eDP-1 mapped: eDP-1-1 model: AU Optronics 0x21ed built: 2016
    res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 142 gamma: 1.2
    size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9
    modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.105.08
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1050/PCIe/SSE2
    memory: 3.91 GiB
  API: Vulkan v: 1.4.328 layers: 8 device: 0 type: discrete-gpu
    name: NVIDIA GeForce GTX 1050 driver: nvidia v: 580.105.08
    device-ID: 10de:1c8d surfaces: N/A device: 1 type: integrated-gpu
    name: Intel UHD Graphics 630 (CFL GT2) driver: mesa intel v: 25.3.1
    device-ID: 8086:3e9b surfaces: N/A device: 2 type: cpu name: llvmpipe
    (LLVM 21.1.6 256 bits) driver: mesa llvmpipe v: 25.3.1 (LLVM 21.1.6)
    device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info
    x11: xdpyinfo, xprop, xrandr

zypper lr -d
# | Alias                      | Name              | Enabled | GPG Check | Refresh | Keep | Priority | Type   | URI                                                                  | Service
--+----------------------------+-------------------+---------+-----------+---------+------+----------+--------+----------------------------------------------------------------------+---------
1 | NVIDIA:repo-non-free       | repo-non-free     | Sí      | (r ) Sí   | Sí      | -    |   99     | rpm-md | https://download.nvidia.com/opensuse/tumbleweed                      | NVIDIA
2 | openSUSE:repo-non-oss      | repo-non-oss      | Sí      | (r ) Sí   | Sí      | -    |   99     | rpm-md | http://cdn.opensuse.org/tumbleweed/repo/non-oss                      | openSUSE
3 | openSUSE:repo-openh264     | repo-openh264     | Sí      | (r ) Sí   | Sí      | -    |   99     | rpm-md | https://codecs.opensuse.org/openh264/openSUSE_Tumbleweed             | openSUSE
4 | openSUSE:repo-oss          | repo-oss          | Sí      | (r ) Sí   | Sí      | -    |   99     | rpm-md | http://cdn.opensuse.org/tumbleweed/repo/oss                          | openSUSE
5 | openSUSE:repo-oss-debug    | repo-oss-debug    | No      | ----      | ----    | -    |   99     | N/A    | http://cdn.opensuse.org/debug/tumbleweed/repo/oss                    | openSUSE
6 | openSUSE:repo-oss-source   | repo-oss-source   | No      | ----      | ----    | -    |   99     | N/A    | http://cdn.opensuse.org/source/tumbleweed/repo/oss                   | openSUSE
7 | openSUSE:update-tumbleweed | update-tumbleweed | Sí      | (r ) Sí   | Sí      | -    |   99     | rpm-md | http://cdn.opensuse.org/update/tumbleweed                            | openSUSE
8 | packman                    | Packman           | Sí      | (r ) Sí   | Sí      | -    |   70     | rpm-md |

Nevermind, here’s the journal:
https://paste.opensuse.org/pastes/9dd891bfbf58

Since this might take a bit longer, a link to another paste, the same log.
https://paste.opensuse.org/pastes/a000fec8d83b

@Spam which packman repo, if it’s all of them, then may have pulled in unnecessary packages… eg Mesa.

What do you mean by “which packman repo”?
I only use the codecs

@Spam only if your URL is tied to the “Essentials” repository, else you can pull rpms from the others likes of Extra…

I would suggest a check to see what is installed via zypper se -si -r 8

It could be. What am I looking for specifically?
https://paste.opensuse.org/pastes/7ede577274ff

@Spam you missed the -r 8 should only show items from the packman repo?

Just checked, I did type

zypper se -si r 8

Here:
https://paste.opensuse.org/pastes/b905f725b631
Sorry for that.

So as you can see you got many more packages like Mesa. If you’re only wanting to use the likes of VLC install the flatpak version as your user.

I need several codecs for video editing. Can’t I just exclude the Packman packages I don’t need?

@Spam what codecs? What application are you using?

Packman should in these days only be for esoteric codecs (even then flatpaks can help) and the unfortunate people with AMD stuff…

I have the same sort of setup as your hardware here, it did run Tumbleweed, but now runs Leap 16.0 I use VLC flatpak, else the oss tools work fine with the Intel 630 GPU, I off load Vulkan to the Nvidia GPU, works better for GNOME/Wayland.

My suggestion is to switch everything back to openSUSE oss packages, check you have good intel support packages installed, perhaps set the Nvidia card to control Vulkan and see how it goes.

Oh yeah youtube and twitch didn’t work without the packman codecs either. Can’t remember which ones specifically rn.
Thanks for the advice, I’ll try going back to oss

@Spam youtube should work fine, likely missing the intel packages to support? What browser? Likewise, switcherooctl should be employed to launch applications on the Nvidia GPU.

Just Firefox. They were some specific proprietary codecs: h264 or h265 from ffmpeg4.
I should note that Wayland doesn’t launch on the intel iGPU, should have tried earlier, sorry.

@Spam I have no issues with Wayland on the Intel 630 GPU, I have three systems, Dell OptiPlex 3080 running Aeon another Dell OptiPlex 3080 dual boots Windows 11 Pro and Tumbleweed (grub-bls) and a Dell OptiPlex XE3 all systems have the Intel 630 GPU the latter also has a Nvidia Quadro T400 which is set to Primary, so the 630 is a Display Controller running Leap 16.0. All use Wayland…

Yeah I think it used to work too.