| Summary: | kscreenlocker crashes with segfault | ||
|---|---|---|---|
| Product: | [KDE Neon] neon | Reporter: | Moritz <bixilon> |
| Component: | Packages Unstable Edition | Assignee: | Neon Bugs <neon-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | bixilon, bshah, clay, jay, jr, neon-bugs, orangewinds, sitter |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Moritz
2022-09-30 09:03:48 UTC
This bug should have the highest priority, it destorys all KDE neon user (maybe even whole plasma 5.26?) experience. And if we take it in consideration that plasma 5.26 should be released in 3 days. It makes my laptop unuseable, I don't even want to update my other ones. I don't believe this is related to Plasma 5.26. I am seeing thew same in Neon User (upgraded top the 22.04 base) with Plasma 5.25.5 since updating on Sept 30. No issues in Xorg, just in Wayland. I suspect something is missing or out of sync, version-wise? Reverting to a snapshot from the 29th, these are the updates since then: The following NEW packages will be installed: neon-repositories-launchpad-mozilla ubuntu-dbgsym-keyring The following packages have been kept back: apt apt-transport-https apt-utils libapt-pkg6.0 The following packages will be upgraded: gir1.2-wp-0.4 google-chrome-stable gstreamer1.0-pipewire liblur3 libpipewire-0.3-0 libpipewire-0.3-dev libpipewire-0.3-modules libqt5script5 libqt5scripttools5 libqt5waylandclient5 libqt5waylandclient5-dev libqt5waylandcompositor5 libratbag-tools libspa-0.2-bluetooth libspa-0.2-dev libspa-0.2-jack libspa-0.2-modules libspeechd2 libwireplumber-0.4-0 libwireplumber-0.4-dev lur-command neon-essentials-desktop neon-settings-2 obs-studio openrgb openshot-qt pipewire pipewire-alsa pipewire-bin pipewire-jack pipewire-locales pipewire-pulse pipewire-tests plasma-wayland-protocols python3-distupgrade qtscript5-dev qtwayland5 qtwayland5-dev-tools ratbagd ubuntu-release-upgrader-core ubuntu-release-upgrader-qt wireplumber wireplumber-doc The held packages can be ignored, those are being phased, specific to Ubuntu 22.04. You are right. When updating libqt5waylandclient5 libqt5waylandcompositor5 plasma-wayland-protocols qtwayland5 to debian sid packages and rebooting it works. (In reply to Moritz from comment #4) > You are right. When updating libqt5waylandclient5 libqt5waylandcompositor5 > plasma-wayland-protocols qtwayland5 to debian sid packages and rebooting it > works. It would probably be safer/wiser to downgrade to a slightly earlier build than to mix and match both different distro packaging as well as Qt versions. $ apt policy libqt5waylandclient5 libqt5waylandclient5: Installed: 5.15.5+p22.04+tunstable+git20220928.0054-0 Candidate: 5.15.5+p22.04+tunstable+git20220928.0054-0 Version table: *** 5.15.5+p22.04+tunstable+git20220928.0054-0 500 500 http://archive.neon.kde.org/user jammy/main amd64 Packages 100 /var/lib/dpkg/status 5.15.5+p22.04+tunstable+git20220923.0055-0 500 500 http://archive.neon.kde.org/user jammy/main amd64 Packages 5.15.5+p22.04+tunstable+git20220921.0058-0 500 500 http://archive.neon.kde.org/user jammy/main amd64 Packages 5.15.5+p22.04+tunstable+git20220920.0122-0 500 500 http://archive.neon.kde.org/user jammy/main amd64 Packages Downgrading libqt5waylandclient5, libqt5waylandcompositor5 and qtwayland5 to September 23's builds (5.15.5+p22.04+tunstable+git20220923.0055-0) seems to work. seems to work again (at least for me) Yes, this seems to have been fixed after the upgrade to Plasma 5.26 today. |