Do the login screens look different from one another?
As far as I know KDE Neon isn't really meant as a daily driver. A different distribution would probably be more stable.
this post was submitted on 12 Apr 2025
21 points (100.0% liked)
KDE
6441 readers
17 users here now
KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.
Plasma 6 Bugs
If you encounter a bug, proceed to https://bugs.kde.org/, check whether it has been reported.
If it hasn't, report it yourself.
PLEASE THINK CAREFULLY BEFORE POSTING HERE.
Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.
founded 2 years ago
MODERATORS
Do the login screens look different from one another?
Nope
KDE Neon isn't really meant as a daily driver
Why not ? It's Plasma and KDE apps on a Ubuntu LTS base with none of Canonical's crap.
And all KDE apps work on it, while other distros running KDE don't necessarily support all KDE apps, especially Discover.
@KaKi87 @bjoern_tantau
𝚆𝚑𝚢 𝚗𝚘𝚝 ? 𝙸𝚝’𝚜 𝙿𝚕𝚊𝚜𝚖𝚊 𝚊𝚗𝚍 𝙺𝙳𝙴 𝚊𝚙𝚙𝚜 𝚘𝚗 𝚊 𝚄𝚋𝚞𝚗𝚝𝚞 𝙻𝚃𝚂 𝚋𝚊𝚜𝚎 𝚠𝚒𝚝𝚑 𝚗𝚘𝚗𝚎 𝚘𝚏 𝙲𝚊𝚗𝚘𝚗𝚒𝚌𝚊𝚕’𝚜 𝚌𝚛𝚊𝚙.
Because of this: https://neon.kde.org/#%3A%5C%7E%3Atext=You+should+use+KDE+neon+if+you+are+an+adventurous+KDE+enthusiast
I don't see any contradiction here. As long as you're using the user edition, you're still using a tested distro.
Plus, except for Ubuntu, no Debian-based distro ships Plasma 6 (Tuxedo doesn't count because Neon-based).
Well, distros that say "is stable" and don't say "there might be some teething problems" still have problems, so this is average. Just because I was warned doesn't mean I can't talk about an issue...
are you using any sddm themes? splash screens?
Also check/share the logs (you can use ksystemlogs or gnome logs if you prefer guis).
Hi,
Did you get a chance to look at my logs ?
Thank you
sorry I was really busy this week, didnt have time to look into this.
The issue seems to happen in qt6 xcb so you could try switching sddm to run on wayland, which might bypass the issue (from Arch wiki):
Create the file /etc/sddm.conf.d/10-wayland.conf with the following content:
[General]
DisplayServer=wayland
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell
[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1
This requires layer-shell-qt to be installed, preferably versions 6.x which kde neon probably has in their repos (its on 5.x on base ubuntu).
Other than that, on sddm's issue repo I found two similar issues: #1761 and #1468, though both have no resolutions yet.
So, I tried this, and got a blank scren, I had to press Ctrl-Alt-F2 to log in, delete the file and reboot to go back to the initial state.
No logs appeared at boot and the logs app didn't reveal anything either.
As for the package, it was already installed : 6.3.4-0zneon+24.04+noble+release+build26
are you using any sddm themes? splash screens?
Nope, all default.
Also check/share the logs (you can use ksystemlogs or gnome logs if you prefer guis).
I'm guessing you don't want the last few lines, what am I looking for ?
Not sure tbh but probably anything around the time you experience the issue. Check the time when the issue occurs, then look at the logs from around that time for any errors warnings. That should at least give you a clue.
Hi,
Here's what I found :
(part 1/2)
Process 1323 (sddm-greeter-qt) of user 122 dumped core.
Module libudev.so.1 from deb systemd-255.4-1ubuntu8.6.amd64
Module libnss_systemd.so.2 from deb systemd-255.4-1ubuntu8.6.amd64
Module libgomp.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.amd64
Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2build1.1.amd64
Module libgcc_s.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.amd64
Module libstdc++.so.6 from deb gcc-14-14.2.0-4ubuntu2~24.04.amd64
Module libsystemd.so.0 from deb systemd-255.4-1ubuntu8.6.amd64
Stack trace of thread 1323:
#0 0x000075d797a4798b __run_exit_handlers (libc.so.6 + 0x4798b)
#1 0x000075d797a47bbe __GI_exit (libc.so.6 + 0x47bbe)
#2 0x000075d793b7da31 n/a (libQt6XcbQpa.so.6 + 0x4fa31)
#3 0x000075d793b95baf n/a (libQt6XcbQpa.so.6 + 0x67baf)
#4 0x000075d7977d75b5 n/a (libglib-2.0.so.0 + 0x5d5b5)
#5 0x000075d797836717 n/a (libglib-2.0.so.0 + 0xbc717)
#6 0x000075d7977d6a53 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca53)
#7 0x000075d79846e6ef _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x26e6ef)
#8 0x000075d7986b14d3 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x4b14d3)
#9 0x000075d7986b2ffd _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x4b2ffd)
#10 0x00005cf22e4bd5b9 n/a (sddm-greeter-qt6 + 0x175b9)
#11 0x000075d797a2a1ca __libc_start_call_main (libc.so.6 + 0x2a1ca)
#12 0x000075d797a2a28b __libc_start_main_impl (libc.so.6 + 0x2a28b)
#13 0x00005cf22e4c2835 n/a (sddm-greeter-qt6 + 0x1c835)
Stack trace of thread 1344:
#0 0x000075d797b1b4cd __GI___poll (libc.so.6 + 0x11b4cd)
#1 0x000075d79783666e n/a (libglib-2.0.so.0 + 0xbc66e)
#2 0x000075d7977d6a53 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca53)
#3 0x000075d79846e6ef _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x26e6ef)
#4 0x000075d7986b14d3 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x4b14d3)
#5 0x000075d7985c8df7 _ZN7QThread4execEv (libQt6Core.so.6 + 0x3c8df7)
#6 0x000075d79775c02d n/a (libQt6DBus.so.6 + 0x9c02d)
#7 0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#8 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#9 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1355:
#0 0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1 0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2 0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3 0x000075d789fefbc3 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x7efbc3)
#4 0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1359:
#0 0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1 0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2 0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3 0x000075d789fec04b n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x7ec04b)
#4 0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1413:
#0 0x000075d797b2725d syscall (libc.so.6 + 0x12725d)
#1 0x000075d7985895da _ZN10QSemaphore7acquireEi (libQt6Core.so.6 + 0x3895da)
#2 0x000075d76c6c5524 n/a (libQt6HunspellInputMethod.so.6 + 0x10524)
#3 0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#4 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#5 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1423:
#0 0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1 0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2 0x000075d79858d0db _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x38d0db)
#3 0x000075d76c50e9bd n/a (libQt6LabsFolderListModel.so.6 + 0xf9bd)
#4 0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#5 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1441:
#0 0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1 0x000075d797a9bc8e __pthread_cond_wait_common (libc.so.6 + 0x9bc8e)
#2 0x000075d79858d058 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x38d058)
#3 0x000075d798587a36 n/a (libQt6Core.so.6 + 0x387a36)
#4 0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#5 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1442:
#0 0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1 0x000075d797a9bc8e __pthread_cond_wait_common (libc.so.6 + 0x9bc8e)
#2 0x000075d79858d058 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x38d058)
#3 0x000075d798587a36 n/a (libQt6Core.so.6 + 0x387a36)
#4 0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#5 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1356:
#0 0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1 0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2 0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3 0x000075d789fefbc3 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x7efbc3)
#4 0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1357:
#0 0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1 0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2 0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3 0x000075d789fefbc3 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x7efbc3)
#4 0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1360:
#0 0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1 0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2 0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3 0x000075d789fec04b n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x7ec04b)
#4 0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1362:
#0 0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1 0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2 0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3 0x000075d789fec04b n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x7ec04b)
#4 0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1365:
#0 0x000075d797b1b4cd __GI___poll (libc.so.6 + 0x11b4cd)
#1 0x000075d79783666e n/a (libglib-2.0.so.0 + 0xbc66e)
#2 0x000075d7977d6a53 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca53)
#3 0x000075d79846e6ef _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x26e6ef)
#4 0x000075d7986b14d3 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x4b14d3)
#5 0x000075d7985c8df7 _ZN7QThread4execEv (libQt6Core.so.6 + 0x3c8df7)
#6 0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#7 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#8 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1440:
#0 0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1 0x000075d797a9bc8e __pthread_cond_wait_common (libc.so.6 + 0x9bc8e)
#2 0x000075d79858d058 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x38d058)
#3 0x000075d798587a36 n/a (libQt6Core.so.6 + 0x387a36)
#4 0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#5 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1358:
#0 0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1 0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2 0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3 0x000075d789fefbc3 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x7efbc3)
#4 0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1363:
#0 0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1 0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2 0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3 0x000075d78992ed0b n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x12ed0b)
#4 0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
(part 2/2)
Stack trace of thread 1409:
#0 0x000075d797b1b4cd __GI___poll (libc.so.6 + 0x11b4cd)
#1 0x000075d79783666e n/a (libglib-2.0.so.0 + 0xbc66e)
#2 0x000075d7977d6a53 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca53)
#3 0x000075d79846e6ef _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x26e6ef)
#4 0x000075d7986b14d3 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x4b14d3)
#5 0x000075d7985c8df7 _ZN7QThread4execEv (libQt6Core.so.6 + 0x3c8df7)
#6 0x000075d79a0a4272 n/a (libQt6Quick.so.6 + 0x4a4272)
#7 0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#8 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#9 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1439:
#0 0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1 0x000075d797a9bc8e __pthread_cond_wait_common (libc.so.6 + 0x9bc8e)
#2 0x000075d79858d058 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x38d058)
#3 0x000075d798587a36 n/a (libQt6Core.so.6 + 0x387a36)
#4 0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#5 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1444:
#0 0x000075d797a98f0b futex_wait (libc.so.6 + 0x98f0b)
#1 0x000075d797a47a90 __run_exit_handlers (libc.so.6 + 0x47a90)
#2 0x000075d797a47bbe __GI_exit (libc.so.6 + 0x47bbe)
#3 0x000075d797900bd7 _XDefaultIOError (libX11.so.6 + 0x3dbd7)
#4 0x000075d79790390c _XIOError (libX11.so.6 + 0x4090c)
#5 0x000075d797909932 _XReply (libX11.so.6 + 0x46932)
#6 0x000075d7978e0e18 XGetGeometry (libX11.so.6 + 0x1de18)
#7 0x000075d792dbf5c8 n/a (libGLX_mesa.so.0 + 0x305c8)
#8 0x000075d7898e1d33 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0xe1d33)
#9 0x000075d7898e9365 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0xe9365)
#10 0x000075d7899be915 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x1be915)
#11 0x000075d7899bf865 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x1bf865)
#12 0x000075d789c3136e n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x43136e)
#13 0x000075d789c36360 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x436360)
#14 0x000075d79901fa1b n/a (libQt6Gui.so.6 + 0x61fa1b)
#15 0x000075d799023b9f n/a (libQt6Gui.so.6 + 0x623b9f)
#16 0x000075d798ee3440 _ZN4QRhi8endFrameEP13QRhiSwapChain6QFlagsINS_12EndFrameFlagEE (libQt6Gui.so.6 + 0x4e3440)
#17 0x000075d79a0083af n/a (libQt6Quick.so.6 + 0x4083af)
#18 0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#19 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#20 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
Stack trace of thread 1361:
#0 0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1 0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2 0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3 0x000075d789fec04b n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x7ec04b)
#4 0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
ELF object binary architecture: AMD x86-64
Do you have multiple monitors? My laptop behaves in a similar fassion when the screens turn off from inactivity and i want to log back in. I have 2 monitors attached that take different amounts of time to wake up and each time sddm rearranges the screens.
The login prompt is "per screen" and gets erased when a display is attached (or wakes up)
Nope, just the laptop monitor.