Upgrading to kde 6.2.1-1 is killing my SDDM/KDE session

Help
1

I upgraded to KDE 6.2.1.-1 from

Operating System: EndeavourOS
KDE Plasma Version: 6.2.0
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.9.7-x64v2-xanmod1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon HD 7800 Series

And after reboot, I got a flashing _ when EOS is trying to go into SDDM
I timeshifted back one step. It is lifesaver that I have pacman hooks for timeshift before and after an update

What could be the problem?
mesa?

Here is the link for the error log of the system journal

system_journal_err_log.txt

2 Likes
2

On my PC, after upgrading to 6.2.1-1 my mouse cursor disappeared. I’ve already downgraded to 6.2.0 and it went back to normal. I’d suggest downgrade if you are experiencing problems.

3

I use timeshift and I restored my system to 6.2.0

4

Downgrading kwin can temporary fix the issue.
Every updates that they release since 6.2 are a mess, they claim that 6.2 fix many bugs, instead they make more horrible bugs, and they still release them, it reminds me of Windows.

2 Likes
5

It’s unbelievable to see them releasing this kind of update. Have they tested it before releasing it?

6

For anyone who doesn’t have Timeshift, they can downgrade Kwin to 6.2.0. If that doesn’t work, update your pacman.conf as follows:

[core]
#Include = /etc/pacman.d/mirrorlist
Server=https://archive.archlinux.org/repos/2024/10/15/$repo/os/$arch

Do the same for any additional repositories you may have (e.g., multilib, extra, etc.).

2 Likes
7

I filed a bug
https://bugs.kde.org/show_bug.cgi?id=494860

2 Likes
8

tbh for me the kwin_wayland was crashing not ksplash but downgrading to 6.2.0 fixed that.

1 Like
9

Can’t confirm on Arch with amdgpu. Though it takes more time for the splash screen to go away admittedly.

(This has the benefit though that I see all my pre-defined windows that have to be opened maximized on multiple virtual desktops at autostart already in position, without having to see them opening one by one like before (and in X11 they were opening in the background and not stealing focus, that’s a regression with Wayland) :slight_smile: )

1 Like
10

Can confirm on Arch with AMD RX6750XT.

11

I also have this behaviour with the splash taking a long time to transition, but for me its more of a slow down as I do not use session restore.

edit: doing some light testing it seems to be an additional 30 seconds on top of the load time with no splash enabled. Is it timing out? Should a bug report be opened?

1 Like
12

According to OP’s log ksplashqml crashed. Select None in the Splash Screen settings, then re-login (or soft-reboot, restart sddm, whatever) did it improve for you now? I was dropped to my desktop instantly like it was before.

In the changelog there was a reference to it, could be relevant?

13

Similar issue on Arch.
Just a flashing “_” cursor on black screen when SDDM should show up.

I tried what was suggested here:

Did not work, not a Issue with the Breeze theme here.

The KDE start from the command line with /usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland
complained about unable to get display or something similar.
I deactivated SDDM systemctl disable sddm.service and restarted, now the display complain is gone but I still get:

org.kde.startup: "kdeinit5_shutdown" QList() exited with code 255
startplasma-wayland: Shuting down...
startplasmacompositor:  Shuting down...
startplasmacompositor:  Done.

And that’s it.

Used timeshift to revert to 6.2.0 in fact I’m slightly more back now then where I was yesterday.

14

This is 494840 – KSplash screen takes long time after 6.2.1

Looks like a regression and a fix has been merged.

1 Like
15

hm…
talks about that after ~30 seconds something should happen (it just takes long) or did I read that wrong.
I am pretty sure I waited over 30 seconds, and I have not a slow machine (i9-13900HX). in fact I even “played” around at another TTY way longer and when switching back still nothing had happened. And the commandline start shuts down immediately.

If someone can post here as soon that supposedly fix arrives on Arch it would be great and I will give it a try.

Edit: Just out of curiosity I tried what @rockandstone suggested.
Turned of Splash screen it the settings, updated to 6.2.1 and rebooted
Did not work, but I’m not really surprised as I have never seen the Spash screen before SDDM only after and same as the OP said “trying to go into SDDM” not even SDDM showed up.
Waited full 5 Minutes, nothing changed, logged into TTY5 and tried to start plasma-wayland from command line, shut itself down immediately with the messages from my last post.

Restored to 6.2.0 with Timeshift,
does Timeshift preserve the logs or do they get overwritten with the old version as well? Looks like log got reset as well a journalctl -b -p err now has nothing in that timeframe. :frowning_face:

16

I reinstalled an older Fedora Kinoite which uses Plasma 6.0.3, did not update just to test this, and I have the same problems: windows disappearing, black screen, freezing mouse, crashes. So it is not only with Plasma 6.2 or higher.

17

A rebuild covering the aforementioned fix/merge is now available for Arch (6.2.1.1-1)
, you may try it. I selected the Breeze Splash Screen again and there was no delay anymore. :+1:

1 Like
18

Thanks
with that I am now finally on a working 6.2.1.1-1
At least so far, as I have not run very much yet.

:+1:
Operating System: Arch Linux
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 32 × 13th Gen Intel® Core™ i9-13900HX
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO Gemini Gen2

2 Likes
19

Same black screen at startup for me

have to CTL-ALT # to terminal, CTL-ALT# to open plasma desktop

Am not prepared to timeshift backwards.

Fortunately, I have a Manjaro Stable partition.

20

Are you perhaps on Manjaro testing? That uses an overlay package build by PhilM himself, and not the one from Arch, maybe that is the reason.

image
image892×516 38.1 KB

image