[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep with wayland protocol error (wl_display@1: error 1: invalid arguments for wl_display@1.get_registry)
https://bugs.kde.org/show_bug.cgi?id=485084 Zamundaaa changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||6.1.1 Resolution|--- |FIXED --- Comment #17 from Zamundaaa --- This should be fixed since https://invent.kde.org/plasma/kwin/-/merge_requests/5939 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep with wayland protocol error (wl_display@1: error 1: invalid arguments for wl_display@1.get_registry)
https://bugs.kde.org/show_bug.cgi?id=485084 Milton Hagler changed: What|Removed |Added CC||milton...@gmail.com --- Comment #16 from Milton Hagler --- (In reply to Nate Graham from comment #11) > Is anyone affected using only one screen? Or is it only with multiple > screens? Seen the same thing periodically using multiple monitors - laptop screen, laptop hdmi, laptop usb-c to display link. CTRL-ALT-F2 - opens the login screen which is disabled and unusable CTRL-D - does not function Forced to do a hardware reboot. Saw similar issue occasionally in Plasma 5.27. Now more frequent. Appears to be a multiple monitor issue. Operating System: Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.1.94-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 46.5 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep with wayland protocol error (wl_display@1: error 1: invalid arguments for wl_display@1.get_registry)
https://bugs.kde.org/show_bug.cgi?id=485084 --- Comment #15 from DAK --- Addendum: I also noticed that by unlocking the session via virtual terminal also breaks the brightness control. So now i cannot press the night light and brightness icon and control the screen brightness -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep with wayland protocol error (wl_display@1: error 1: invalid arguments for wl_display@1.get_registry)
https://bugs.kde.org/show_bug.cgi?id=485084 DAK changed: What|Removed |Added CC||phantomslayer...@gmail.com --- Comment #14 from DAK --- (In reply to Nate Graham from comment #11) > Is anyone affected using only one screen? Or is it only with multiple > screens? Happening to me with just one screen. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep with wayland protocol error (wl_display@1: error 1: invalid arguments for wl_display@1.get_registry)
https://bugs.kde.org/show_bug.cgi?id=485084 Simone Lazzaris changed: What|Removed |Added Version|6.1.0 |6.1.1 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep with wayland protocol error (wl_display@1: error 1: invalid arguments for wl_display@1.get_registry)
https://bugs.kde.org/show_bug.cgi?id=485084 --- Comment #13 from Simone Lazzaris --- (In reply to Nate Graham from comment #11) > Is anyone affected using only one screen? Or is it only with multiple > screens? I'm using dual screen. I've also got an update: with kde 6.1.1, the unlock screen works, I don't need to switch to a console, but still there are crashes. Now apparently kmail also crashes, but I'm not sure if it is related. giu 27 20:44:30 betelgeuse systemd-coredump[131031]: Process 130365 (kmail) of user 1000 terminated abnormally with signal 11/SEGV, processing... giu 27 20:44:30 betelgeuse systemd[1]: Started Process Core Dump (PID 131031/UID 0). giu 27 20:44:30 betelgeuse systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling. giu 27 20:44:30 betelgeuse kernel: kscreenlocker_g[130883]: segfault at 8 ip 7d59a31aaee4 sp 7fffa7d681a8 error 4 in libQt6Gui.so.6.7.2[7d59a30d9000+618000] likely on CPU 10 (core 12, socket 0) giu 27 20:44:30 betelgeuse kernel: Code: 84 00 00 00 00 00 f0 83 28 01 75 9a 48 8b 7d b0 ff 15 90 87 68 00 eb 8e ff 15 80 8c 68 00 0f 1f 84 00 00 00 00 00 f3 0f 1e fa <48> 8b 57 08 48 8b 02 48 85 c0 74 10 8b 40 04 85 c0 74 09 48 8b 42 giu 27 20:44:44 betelgeuse systemd-coredump[131029]: [] Process 125756 (plasmashell) of user 1000 dumped core. Stack trace of thread 125879: #0 0x7e68684a8e44 n/a (libc.so.6 + 0x94e44) #1 0x7e6868450a30 raise (libc.so.6 + 0x3ca30) #2 0x7e686b31b643 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x6643) #3 0x7e6868450ae0 n/a (libc.so.6 + 0x3cae0) #4 0x7e68699a540b _ZNK15QtWaylandClient14QWaylandWindow16devicePixelRatioEv (libQt6WaylandClient.so.6 + 0x9140b) #5 0x7e686236ff0c _ZN15QtWaylandClient17QWaylandEglWindow13updateSurfaceEb (libQt6WaylandEglClientHwIntegration.so.6 + 0x8f0c) #6 0x7e6862370905 _ZN15QtWaylandClient17QWaylandGLContext11makeCurrentEP16QPlatformSurface (libQt6WaylandEglClientHwIntegration.so.6 + 0x9905) #7 0x7e68694adc28 _ZN14QOpenGLContext11makeCurrentEP8QSurface (libQt6Gui.so.6 + 0x4adc28) #8 0x7e686966f112 n/a (libQt6Gui.so.6 + 0x66f112) #9 0x7e686a418647 n/a (libQt6Quick.so.6 + 0x418647) #10 0x7e686a419f9a n/a (libQt6Quick.so.6 + 0x419f9a) #11 0x7e6868cc9747 n/a (libQt6Core.so.6 + 0x2c9747) #12 0x7e68684a6ded n/a (libc.so.6 + 0x92ded) #13 0x7e686852a0dc n/a (libc.so.6 + 0x1160dc) Stack trace of thread 125756: #0 0x7e68684a34e9 n/a (libc.so.6 + 0x8f4e9) #1 0x7e68684a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9) #2 0x7e6868cce120 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2ce120) #3 0x7e686a413bd4 n/a (libQt6Quick.so.6 + 0x413bd4) #4 0x7e686a4148bd n/a (libQt6Quick.so.6 + 0x4148bd) #5 0x7e686a24d8de _ZN12QQuickWindowD1Ev (libQt6Quick.so.6 + 0x24d8de) #6 0x60db1a4bea40 n/a (plasmashell + 0x3ca40) #7 0x7e6868b8be0a _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x18be0a) #8 0x7e686aafc51c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfc51c) #9 0x7e6868b44d28 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x144d28) #10 0x7e6868b450eb _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x1450eb) #11 0x7e6868da49ec n/a (libQt6Core.so.6 + 0x3a49ec) #12 0x7e686764da89 n/a (libglib-2.0.so.0 + 0x5ca89)
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep with wayland protocol error (wl_display@1: error 1: invalid arguments for wl_display@1.get_registry)
https://bugs.kde.org/show_bug.cgi?id=485084 --- Comment #12 from Enrico --- I'm using, and always used, a single monitor connected to my Intel NUC. I've never used multiple screens -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep with wayland protocol error (wl_display@1: error 1: invalid arguments for wl_display@1.get_registry)
https://bugs.kde.org/show_bug.cgi?id=485084 Nate Graham changed: What|Removed |Added Summary|Screen Locker broken on |Screen Locker broken on |resume from sleep |resume from sleep with ||wayland protocol error ||(wl_display@1: error 1: ||invalid arguments for ||wl_display@1.get_registry) CC||k...@davidedmundson.co.uk, ||n...@kde.org, ||xaver.h...@gmail.com Severity|normal |critical --- Comment #11 from Nate Graham --- Is anyone affected using only one screen? Or is it only with multiple screens? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084 Simone Lazzaris changed: What|Removed |Added Version|6.0.3 |6.1.0 --- Comment #10 from Simone Lazzaris --- Note it wasn't happening on kde 6.0.X -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084 Simone Lazzaris changed: What|Removed |Added CC||sim...@omni.it --- Comment #9 from Simone Lazzaris --- I'm seeing the same problem. Archlinux, kde 6.1.0, amd ryzen 9 5900X, radeon 7600X. It seems to crash when the screensaver kicks in *and* the monitor shuts down. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084 --- Comment #8 from Enrico --- This bug also happens on OpenBSD Plasma 6, where loginctl is not available so it can't be fixed with the CTRL+ALT+F2 trick. Since this bug report is not so active, I can suppose it's something related to some hardware or specific configuration because I get this bug on every distro I tried (KaOS/6, Kubuntu/5.27, OpenBSD/6) but most of the users don't. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084 bugs.kde@trezamere.net changed: What|Removed |Added CC||bugs.kde@trezamere.net -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084 --- Comment #7 from Enrico --- Related to this bug, I suggest also the change the error message which asks to press CTRL+ALT+F2 because it doesn't work at least on Wayland. I must use CTRL+ALT+F3, not F2 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084
Enrico changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0 |1
CC||enric...@hotmail.com
--- Comment #6 from Enrico ---
Same here on Plasma 6.1 Beta
Operating System: KaOS (2024)
KDE Plasma Version: 6.0.90
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.8.11-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × 12th Gen Intel® Core™ i5-1240P
Product Name: NUC12WSHi5
plasmashell[1146]: qml: Connection lost
kernel: kscreenlocker_g[7309]: segfault at 62 ip 7f64e898da2a sp
7ffcc2ec38f0 error 4 in libPlasmaQuick.so.6.0.90[7f64e8959000+6] likely
on CPU 2 (core 4, socket 0)
kernel: Code: 48 8b 47 28 48 8b 78 08 e9 83 bb fc ff 90 66 90 48 83 ec 08 48 8b
47 28 48 8b 78 08 e8 0f d8 fc ff 48 85 c0 74 11 48 8b 50 08 42 31 01 ba 00
00 00 00 48 0f 44 c2 48 83 c4 08 c3 0f 1f 40 00
kwin_wayland_wrapper[1026]: not a valid new object id (2), message
get_registry(n)
kwin_wayland_wrapper[1026]: error in client communication (pid 1026)
kwin_wayland_wrapper[7478]: error: received delete_id for unknown id (49)
kwin_wayland_wrapper[7478]: error: received delete_id for unknown id (50)
kwin_wayland_wrapper[7478]: error: received delete_id for unknown id (47)
kwin_wayland_wrapper[7478]: error: received delete_id for unknown id (42)
kwin_wayland_wrapper[7478]: error: received delete_id for unknown id (46)
kwin_wayland_wrapper[7478]: error: received delete_id for unknown id (38)
kwin_wayland_wrapper[7478]: error: received delete_id for unknown id (25)
kwin_wayland_wrapper[7478]: error: received delete_id for unknown id (24)
kwin_wayland_wrapper[7478]: wl_display@1: error 1: invalid arguments for
wl_display@1.get_registry
kscreenlocker_greet[7478]: qt.qpa.wayland: Loading shell integration failed.
kscreenlocker_greet[7478]: qt.qpa.wayland: Attempted to load the following
shells QList("layer-shell")
kscreenlocker_greet[7478]: qt.qpa.plugin: Could not load the Qt platform plugin
"wayland" in "" even though it was found.
kscreenlocker_greet[7478]: This application failed to start because no Qt
platform plugin could be initialized. Reinstalling the application may fix this
problem.
Available platform
plugins are: eglfs, linuxfb, minimalegl, minimal, offscreen, vkkhrdisplay, vnc,
xcb, wayland-egl, wayland.
kscreenlocker_greet[7482]: qt.qpa.wayland: Loading shell integration failed.
kscreenlocker_greet[7482]: qt.qpa.wayland: Attempted to load the following
shells QList("layer-shell")
kscreenlocker_greet[7482]: qt.qpa.plugin: Could not load the Qt platform plugin
"wayland" in "" even though it was found.
kscreenlocker_greet[7482]: This application failed to start because no Qt
platform plugin could be initialized. Reinstalling the application may fix this
problem.
Available platform
plugins are: eglfs, linuxfb, minimalegl, minimal, offscreen, vkkhrdisplay, vnc,
xcb, wayland-egl, wayland.
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084 --- Comment #5 from todd.br...@hey.com --- Created attachment 169787 --> https://bugs.kde.org/attachment.cgi?id=169787=edit Boot from suspend log - sanitized Log of boot up from suspend, replugged thunderbolt dock after "seeing SDDM crashed switch to vterm 1 to login" message. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084 todd.br...@hey.com changed: What|Removed |Added CC||todd.br...@hey.com --- Comment #4 from todd.br...@hey.com --- Getting the same issue with resume from sleep on my laptop; I have a thunderbolt dock with two monitors running off the dock. Have the same eglSwapBuffers failed error followed by a kernel trap. Doesn't happen consistently :| Laptop has an intel iGPU Have also observed on my desktop when resuming from sleep and forgot to switch my kvm over; meaning it would have resumed with no monitors attached. Desktop uses nvidia proprietary drivers (version 550). Software versions observed on: KDE Plasma 6.0.4 & 6.0.5 KDE Frameworks 6.2.0 QT 6.7.0 & 6.7.1 Linux Kernel: 6.8.9, 6.8.10, 6.9.0, 6.9.1 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084 jd4dvc...@mozmail.com changed: What|Removed |Added CC||jd4dvc...@mozmail.com --- Comment #3 from jd4dvc...@mozmail.com --- I have EXACTLY the same problem. I have 3 monitors, the center one doesn't wake up from sleep, I have to unplug the power chord and plug it again. It started happening yesterday, after the Manjaro big update, which updated KDE to the latest version. I'm using NVIDIA proprietary drivers. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084 --- Comment #2 from lrdarkne...@yahoo.de --- Created attachment 169505 --> https://bugs.kde.org/attachment.cgi?id=169505=edit Journal logs -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084 lrdarkne...@yahoo.de changed: What|Removed |Added CC||lrdarkne...@yahoo.de --- Comment #1 from lrdarkne...@yahoo.de --- I have a similar problem also using AMD GPU. On Plasma 5 this happened only occasionally, but now with Plasma 6 I already had this 2 times in just two days after the upgrade. I also see the error message about broken lock screen requesting me to do "loginctl unlock-session 2" in a separate session. I will attach my journal logs. My system's details: Operating System: Manjaro Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.6.30-2-MANJARO (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-8600K CPU @ 3.60GHz Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6800 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B46 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084 Brian M changed: What|Removed |Added CC||squashyna...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084 smow changed: What|Removed |Added CC||smowten...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
