on my laptop running opensuse 16.0 Argon after the last update I cannot login in plasma wayland, when I insert password and enter the login screen appear again, I can login in gnome wayland and other desktop environment
haw can I login again in my plasma wayland?
Did you try to login with the same user on all desktop environments or did you use a different user for each desktop environment?
Which login manager are you using? Could you try selecting Plasma (X11) at the login screen and see whether that works? From a working desktop session you can examine the journal…
sudo journalctl -b | grep -Ei 'dm|plasma|kwin_wayland|startplasma'
and report back with the output.
Also inxi -GSaz details please.
I tried, unsuccessfully, with three users on Plasma (wayland)
and I tried, successfully, with the same three users in GNOME and with one user in the other desktop environment
I think SDDM but I’m not sure
there is no more (before the update there was and working) Plasma (X11) option at the login screen
Strange. I have a fresh install of Leap 16.1 (an RC release), and X11 is available.
As suggested … you need to check the logs for errors.
I logout from GNOME session with user nipoti an tied to login (unsuccessfully) with plasma (wayland) and user nipoti and then launched the commandhere is the output
https://paste.opensuse.org/pastes/af637417c622
here is
nipoti@pla4-TW:~> inxi -GSaz
System:
Kernel: 6.12.0-160000.37-default arch: x86_64 bits: 64 compiler: gcc
v: 13.4.0 clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.0-160000.37-default
root=UUID=739ff20f-7711-4c18-a71a-4210fc55cf1e
resume=/dev/disk/by-uuid/551fc2e6-1664-473b-ba77-495bc9bbbed7
mitigations=auto security=selinux enforcing=1 selinux=1 ia32_emulation=1
Desktop: GNOME v: 48.4 tk: GTK v: 3.24.50 wm: gnome-shell
tools: gsd-screensaver-proxy avail: lxlock,xscreensaver dm: 1: GDM v: 48.0
note: stopped 2: SDDM Distro: openSUSE Leap 16.0
Graphics:
Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: CLEVO/KAPOK
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: HDMI-A-2,eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0
chip-ID: 8086:3ea0 class-ID: 0300
Device-2: Chicony USB2.0 Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7:3 chip-ID: 04f2:b684
class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.6
compositor: gnome-shell driver: X: loaded: modesetting unloaded: vesa
alternate: fbdev,intel dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-2 mapped: HDMI-2 model: Beyond TV serial: <filter>
built: 2023 res: 1920x1080 hz: 120 dpi: 40 gamma: 1.2
size: 1209x680mm (47.6x26.77") diag: 1387mm (54.6") ratio: 16:9 modes:
max: 4096x2160 min: 640x480
Monitor-2: eDP-1 pos: primary model: ChiMei InnoLux 0x15e8 built: 2016
res: 1920x1080 hz: 60 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 platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.3.3 glx-v: 1.4
direct-render: yes renderer: Mesa Intel UHD Graphics 620 (WHL GT2)
device-ID: 8086:3ea0 memory: 15.17 GiB unified: yes
API: Vulkan v: 1.4.309 layers: 1 device: 0 type: integrated-gpu name: Intel
UHD Graphics 620 (WHL GT2) driver: N/A device-ID: 8086:3ea0
surfaces: xcb,xlib
nipoti@pla4-TW:~>yes, before was for me also, after the update disappeared
There are countless Plasma services core-dumping on your box. A reason might be non standard repositories or incompatible package versions.
I have the same issue in a fresh install of Tumbleweed Slowroll, Wayland SDDM. X11 is not available. As a workaround, I am be able to log in with the virtual keyboard.
So this means
- all three users have a home directory that can be accessed.
- at least one of your users is using three different desktop environments.
Every desktop environment stores its configuration files in a users home directory. I have never tried something like this so I can’t tell whether that is working or not (i.e. if several configurations can coexist without interfering with each other).
If you setup a new user will that one be able to login with Plasma (Wayland)?
FYI: Having and using multiple DEs with the same user login has been supported for > 15 years. Even using the same application from various DEs works fine these days. The OP has most likely still not learned the essential lesson to not add random home: and devel: repos, as others assume too.
As I said: I have never tried so I can’t tell if it is working or not.
However setting up a new user and testing it with Plasma (Wayland) only might be worth a try.
I can’t find any repository listing in this post?!
Pick any thread by the OP.
@pier_andreit Again, show zypper lr -d
You are using SDDM, as shown by the journal output.
The immediate cause of the Plasma Wayland failure…
Sep 26 15:35:58 pla4-TW systemd[5145]: Starting KDE Plasma Workspace...
Sep 26 15:35:58 pla4-TW kwin_wayland_wrapper[5210]: /usr/bin/kwin_wayland: symbol lookup error: /lib64/libkwin.so.6: undefined symbol: wl_global_set_withdrawn_listener
Sep 26 15:35:58 pla4-TW kwin_wayland_wrapper[5230]: /usr/bin/kwin_wayland: symbol lookup error: /lib64/libkwin.so.6: undefined symbol: wl_global_set_withdrawn_listener
Sep 26 15:35:58 pla4-TW kwin_wayland_wrapper[5249]: /usr/bin/kwin_wayland: symbol lookup error: /lib64/libkwin.so.6: undefined symbol: wl_global_set_withdrawn_listener
Sep 26 15:35:58 pla4-TW kwin_wayland_wrapper[5250]: /usr/bin/kwin_wayland: symbol lookup error: /lib64/libkwin.so.6: undefined symbol: wl_global_set_withdrawn_listener
Sep 26 15:35:58 pla4-TW kwin_wayland_wrapper[5251]: /usr/bin/kwin_wayland: symbol lookup error: /lib64/libkwin.so.6: undefined symbol: wl_global_set_withdrawn_listener
Sep 26 15:35:58 pla4-TW kwin_wayland_wrapper[5252]: /usr/bin/kwin_wayland: symbol lookup error: /lib64/libkwin.so.6: undefined symbol: wl_global_set_withdrawn_listener
Sep 26 15:35:58 pla4-TW kwin_wayland_wrapper[5253]: /usr/bin/kwin_wayland: symbol lookup error: /lib64/libkwin.so.6: undefined symbol: wl_global_set_withdrawn_listener
Sep 26 15:35:59 pla4-TW kwin_wayland_wrapper[5254]: /usr/bin/kwin_wayland: symbol lookup error: /lib64/libkwin.so.6: undefined symbol: wl_global_set_withdrawn_listener
Sep 26 15:35:59 pla4-TW kwin_wayland_wrapper[5255]: /usr/bin/kwin_wayland: symbol lookup error: /lib64/libkwin.so.6: undefined symbol: wl_global_set_withdrawn_listener
Sep 26 15:35:59 pla4-TW kwin_wayland_wrapper[5256]: /usr/bin/kwin_wayland: symbol lookup error: /lib64/libkwin.so.6: undefined symbol: wl_global_set_withdrawn_listener
Sep 26 15:35:59 pla4-TW kwin_wayland_wrapper[5257]: /usr/bin/kwin_wayland: symbol lookup error: /lib64/libkwin.so.6: undefined symbol: wl_global_set_withdrawn_listener
Likely library/package version mismatch(es).
From your working GNOME session, post the output…
zypper se -si 'kwin*' 'libwayland*'
and your repo list as others have asked for.
In my case, I found that the issue is caused by a wrong locale in the password form in SDDM: it is defined to english, but my system locale is french. If I use the QWERTY layout to type my password (french layout is AZERTY), it works.
See this thread: Fresh install, can't login with SDDM, but I can login into a TTY session
This shouldn’t be the case for the OP, as he can login with the same PW into another DE…
1 Like
maaanythanks, you lead me in the right direction, I suspected I may be I did some error in update and I’m running opensuse Argon, so I followed the directions for installation in the
opensuse argon site
and run:
zypper -v dup --allow-vendor-change
zypper -v install pattern:kde_plasma
and everything worked out