Returns to SDDM after I login when using KDE Plasma Wayland [SOLVED]

Azobioz · 2026-06-26 17:04:30

Hi, I'm using arch for 3 days and have never used any linux OS before.

After entering password for root user in SDDM, terminal is opened for few seconds and returns to SDDM screen. I have no idea how to solve this problem. It happens in KDE Plasma Wayland. But if I use COSMIC everything works fine.

Before this happend I installed Brave Browser, used pacman -Syu command, tried to download steam and make it work by this instruction https://wiki.archlinux.org/title/Steam: I enable the multilib repository by uncommenting the [multilib] section in /etc/pacman.conf, installed steam package, downloaded mesa-amber and xf86-video-intel packages (I use intel 2 gen gpu btw) and that's all.

Hope this info helps to solve my problem.

Last edited by Azobioz (2026-06-26 19:38:54)

seth · 2026-06-26 17:45:10

plasma crashes, please post your complete system journal for the boot *after* failing to start an X11 session :

sudo journalctl -b | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'

Azobioz · 2026-06-26 17:57:17

seth wrote:

plasma crashes, please post your complete system journal for the boot *after* failing to start an X11 session :
sudo journalctl -b | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'

https://paste.c-net.org/BlazerColby

seth · 2026-06-26 18:05:23

You're logging in fom cosmic-greeter into a cosmic session as user azobioz
This doesn't at all reflect the problem - you need to cause the failure and then upload the journal from a cosmic session (you should be able to log into that from sddm as well) or the console (ctrl+alt+f3)

Edit: logging in as actual root user (UID0) into a GUI session might be denied and is also a terrible idea. Don't do that tbw.

Last edited by seth (2026-06-26 18:06:10)

Azobioz · 2026-06-26 18:16:47

seth wrote:

You're logging in fom cosmic-greeter into a cosmic session as user azobioz
This doesn't at all reflect the problem - you need to cause the failure and then upload the journal from a cosmic session (you should be able to log into that from sddm as well) or the console (ctrl+alt+f3)
Edit: logging in as actual root user (UID0) into a GUI session might be denied and is also a terrible idea. Don't do that tbw.

https://paste.c-net.org/WerewolfAbortion

I'll create a new regular user for logging into GUI session, thanks for the tip.

seth · 2026-06-26 18:28:01

The user 'azobioz' will do

Jun 26 21:10:27 azobioz-host kwin_wayland[807]: querying vulkan devices failed: "ErrorInitializationFailed"
Jun 26 21:10:27 azobioz-host kwin_wayland[807]: No backend specified, automatically choosing drm
Jun 26 21:10:27 azobioz-host systemd[1]: Started Disk Manager.
Jun 26 21:10:27 azobioz-host kwin_wayland[807]: Invalid framebuffer status:  "GL_FRAMEBUFFER_UNSUPPORTED"
Jun 26 21:10:27 azobioz-host kernel: traps: kwin_wayland[807] trap divide error ip:7f18a77c9321 sp:7ffd72639aa0 error:0 in i965_dri.so[9c9321,7f18a6f7c000+8c7000]
Jun 26 21:10:27 azobioz-host systemd-coredump[836]: Process 807 (kwin_wayland) of user 1000 terminated abnormally with signal 8/FPE, processing...
Jun 26 21:10:27 azobioz-host systemd[1]: Created slice Slice /system/systemd-coredump.
Jun 26 21:10:27 azobioz-host systemd[1]: Started Process Core Dump (PID 836/UID 0).
Jun 26 21:10:28 azobioz-host systemd-coredump[837]: Process 807 (kwin_wayland) of user 1000 dumped core.
                                                    
                                                    Stack trace of thread 807:
                                                    #0  0x00007f18a77c9321 n/a (i965_dri.so + 0x9c9321)
                                                    #1  0x00007f18a74f16c8 n/a (i965_dri.so + 0x6f16c8)
                                                    #2  0x00007f18a7839afb n/a (i965_dri.so + 0xa39afb)
                                                    #3  0x00007f18afe22f54 n/a (libgbm.so.1 + 0x5f54)
                                                    #4  0x00007f18afe267db gbm_bo_create_with_modifiers (libgbm.so.1 + 0x97db)
                                                    #5  0x00007f18b31cb7dd n/a (libkwin.so.6 + 0x1cb7dd)
                                                    #6  0x00007f18b331f970 _ZN4KWin12EglSwapchain6createEPNS_23GraphicsBufferAllocatorEPNS_10EglContextERK5QSizejRKNS_12ModifierListE (libkwin.so.6 + 0x31f970)
                                                    #7  0x00007f18b35244ac n/a (libkwin.so.6 + 0x5244ac)
                                                    #8  0x00007f18b3525038 n/a (libkwin.so.6 + 0x525038)
                                                    #9  0x00007f18b3525695 n/a (libkwin.so.6 + 0x525695)
                                                    #10 0x00007f18b351ae5c n/a (libkwin.so.6 + 0x51ae5c)
                                                    #11 0x00007f18b3521930 _ZN4KWin6DrmGpu13testPipelinesEv (libkwin.so.6 + 0x521930)
                                                    #12 0x00007f18b3521b7d _ZN4KWin6DrmGpu19checkCrtcAssignmentE5QListIPNS_12DrmConnectorEERKS1_IPNS_7DrmCrtcEENSt6chrono10time_pointINSA_3_V212steady_clockENSA_8durationIlSt5ratioILl1ELl1000000000EEEEEE (libkwin.so.6 + 0x521b7d)
                                                    #13 0x00007f18b3521b7d _ZN4KWin6DrmGpu19checkCrtcAssignmentE5QListIPNS_12DrmConnectorEERKS1_IPNS_7DrmCrtcEENSt6chrono10time_pointINSA_3_V212steady_clockENSA_8durationIlSt5ratioILl1ELl1000000000EEEEEE (libkwin.so.6 + 0x521b7d)
                                                    #14 0x00007f18b3521b7d _ZN4KWin6DrmGpu19checkCrtcAssignmentE5QListIPNS_12DrmConnectorEERKS1_IPNS_7DrmCrtcEENSt6chrono10time_pointINSA_3_V212steady_clockENSA_8durationIlSt5ratioILl1ELl1000000000EEEEEE (libkwin.so.6 + 0x521b7d)
                                                    #15 0x00007f18b352201b _ZN4KWin6DrmGpu19checkCrtcAssignmentE5QListIPNS_12DrmConnectorEERKS1_IPNS_7DrmCrtcEENSt6chrono10time_pointINSA_3_V212steady_clockENSA_8durationIlSt5ratioILl1ELl1000000000EEEEEE (libkwin.so.6 + 0x52201b)
                                                    #16 0x00007f18b352246e _ZN4KWin6DrmGpu24testPendingConfigurationEv (libkwin.so.6 + 0x52246e)
                                                    #17 0x00007f18b3501ea6 _ZN4KWin10DrmBackend18applyOutputChangesERKNS_19OutputConfigurationE (libkwin.so.6 + 0x501ea6)
                                                    #18 0x00007f18b348ec0d _ZN4KWin9Workspace24applyOutputConfigurationERNS_19OutputConfigurationE (libkwin.so.6 + 0x48ec0d)
                                                    #19 0x00007f18b348ef30 _ZN4KWin9Workspace25updateOutputConfigurationEv (libkwin.so.6 + 0x48ef30)
                                                    #20 0x00007f18b34972c6 _ZN4KWin9Workspace31slotOutputBackendOutputsQueriedEv (libkwin.so.6 + 0x4972c6)
                                                    #21 0x00007f18b348c842 _ZN4KWin9Workspace4initEv (libkwin.so.6 + 0x48c842)
                                                    #22 0x00007f18b3301b4f _ZN4KWin11Application15createWorkspaceEv (libkwin.so.6 + 0x301b4f)
                                                    #23 0x00005643de204d8b n/a (kwin_wayland + 0x4bd8b)
                                                    #24 0x00005643de1f801a n/a (kwin_wayland + 0x3f01a)
                                                    #25 0x00007f18afc27741 n/a (libc.so.6 + 0x27741)
                                                    #26 0x00007f18afc27879 __libc_start_main (libc.so.6 + 0x27879)
                                                    #27 0x00005643de1fc635 n/a (kwin_wayland + 0x43635)

2nd gen is not the CPU but the GPU, you've gen6 HW which should™ be covered by the crocus driver.
Does mesa instead of mesa-amber not work (either)? (Remove xf86-video-intel)

Azobioz · 2026-06-26 18:44:08

seth wrote:

Does mesa instead of mesa-amber not work (either)? (Remove xf86-video-intel)

In the process of installing mesa-amber package there was a conflict with mesa package and there was a choice to delete mesa, I chose to delete it. Aren't these package similar in functionality or mesa-amber is dependent of mesa? Removed xf86-video-intel.

Azobioz · 2026-06-26 18:55:06

Gonna install mesa package and remove mesa-amber

seth · 2026-06-26 18:56:26

mesa-amber is mesa for very old hardware. Your IGP is actually covered by both variants but since kwin is complaining about lack of GL fbo support…
Why did you install msa-amber itfp?

Azobioz · 2026-06-26 19:17:02

seth wrote:

mesa-amber is mesa for very old hardware. Your IGP is actually covered by both variants but since kwin is complaining about lack of GL fbo support…
Why did you install msa-amber itfp?

I installed mesa-amber because this instruction says https://wiki.archlinux.org/title/Steam :
"You must install the 32-bit version of the OpenGL graphics driver appropriate for your system." so went there: https://wiki.archlinux.org/title/Graphi … stallation and in "1.2. Intel" I downloaded packages for 2 gen gpu
I have no idea what is itfp.

Azobioz · 2026-06-26 19:19:31

After removing mesa-amber and installing mesa plasma wayland is working.
Ty seth!
Btw why it's bad idea to logging in as actual root user into a GUI session?

Azobioz · 2026-06-26 19:21:48

Azobioz wrote:

I downloaded packages for 2 gen gpu.

So I need to download 6 gen instead?

seth · 2026-06-26 19:31:18

You don't need to download anything. You've 6 gen hardware (with 2nd gen graphics - I get that's confusing. Blame intel )
"In The First Place"

The root user has unchecked control over the system - it should™ never be invoked w/o cause and certainly not w/ bloated code and it's not getting much more bloated than a graphical session.
Leaving aside attack vulnerability, the software might accidentally cause damage to the system because it can now write directly into eg. device nodes and of course this amplifies every PEBKAC

Edit: Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Last edited by seth (2026-06-26 19:31:44)

Arch Linux

#1 2026-06-26 17:04:30

Returns to SDDM after I login when using KDE Plasma Wayland [SOLVED]

#2 2026-06-26 17:45:10

Re: Returns to SDDM after I login when using KDE Plasma Wayland [SOLVED]

#3 2026-06-26 17:57:17

Re: Returns to SDDM after I login when using KDE Plasma Wayland [SOLVED]

#4 2026-06-26 18:05:23

Re: Returns to SDDM after I login when using KDE Plasma Wayland [SOLVED]

#5 2026-06-26 18:16:47

Re: Returns to SDDM after I login when using KDE Plasma Wayland [SOLVED]

#6 2026-06-26 18:28:01

Re: Returns to SDDM after I login when using KDE Plasma Wayland [SOLVED]

#7 2026-06-26 18:44:08

Re: Returns to SDDM after I login when using KDE Plasma Wayland [SOLVED]

#8 2026-06-26 18:55:06

Re: Returns to SDDM after I login when using KDE Plasma Wayland [SOLVED]

#9 2026-06-26 18:56:26

Re: Returns to SDDM after I login when using KDE Plasma Wayland [SOLVED]

#10 2026-06-26 19:17:02

Re: Returns to SDDM after I login when using KDE Plasma Wayland [SOLVED]

#11 2026-06-26 19:19:31

Re: Returns to SDDM after I login when using KDE Plasma Wayland [SOLVED]

#12 2026-06-26 19:21:48

Re: Returns to SDDM after I login when using KDE Plasma Wayland [SOLVED]

#13 2026-06-26 19:31:18

Re: Returns to SDDM after I login when using KDE Plasma Wayland [SOLVED]

Board footer