[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 unimatrixzero changed: What|Removed |Added CC||u...@uwe-reese.de --- Comment #37 from unimatrixzero --- Same here Manjaro Linux KDE 6.1.5 amdgpu X11 After the system goes to hibernate, (hibernate works as it should, enough swap is there also) the system randomize freeze. Mean restore from hibernate there isn't a sddm-greeter. The system either starts only with a black screen or it shows a "snapshot" of the hibernate, you can see that because the clock isn't running. There is no keyboard or mouse. I can't use any key to switch to tty and restart the sddm session manually That issue is there since the update to plasma 6 with the 5th version everything works as it should -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 paperdiz...@gmail.com changed: What|Removed |Added CC||paperdiz...@gmail.com Version|6.1.4 |6.1.5 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Frederick Zhang changed: What|Removed |Added CC||frederick...@tsundere.moe -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #36 from Billy Messenger --- How do I go about getting the list of commits that happened between versions 6.0 and 6.1? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #35 from Billy Messenger --- I've also been having monitor troubles ever since Plasma 6.1. https://bugs.kde.org/show_bug.cgi?id=489457 There's definitely some kind of bug that has been introduced around that time, but I'm at a loss on what it could be. Annoying because I love Plasma, and I don't want to switch to a different DE just for this issue. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Billy Messenger changed: What|Removed |Added CC||u4fqdzbz@billydm.anonaddy.m ||e --- Comment #34 from Billy Messenger --- I am also having this issue, except that sometimes the system also locks up after logging in after booting. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Andrew changed: What|Removed |Added CC||travn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Dennis Schridde changed: What|Removed |Added CC||dschridde+...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #33 from Vedran Rodic --- (In reply to Ksenia Turek from comment #24) > I can confirm that the bug still happens on Plasma version 6.1.4. > I also found a simple temporary workaround. > > I commented out the entire Image object with id: albumArt, starting at line > 31 in the file > /usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/ > MediaControls.qml > > This will remove the album art from the lock screen, but will also stop the > bug from happening. Nope. that didn't help. And this is happening regardles of the album art being displayed or not (for me it's never showing). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Abubakar Yagoub changed: What|Removed |Added CC||abubakarya...@gmail.com --- Comment #32 from Abubakar Yagoub --- I am getting this error when using wallhaven wallpaper plugin, the network related action here is fetching a wallpaper from wallhaven, not even the initial wallpaper is fetched correctly, it fails everytime here is the link to the plugin https://github.com/Blacksuan19/plasma-wallpaper-wallhaven-reborn -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Yuxin Wu changed: What|Removed |Added CC||ppwwyy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Timothy B changed: What|Removed |Added CC||yule2...@live.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #31 from once-sol...@proton.me --- Nevermind, it is happening again. I've changed two things between then, and now, I moved the default panel to the top, switched it to "fit content", and then switched notification popups to the top right corner. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #30 from once-sol...@proton.me --- Well, this is kind of funny, but I can't replicate this anymore. I installed F40 to test the "solution" in Comment 24, but that file doesn't exist on this install. X11 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Mesa version: 24.1.5 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #29 from Nate Graham --- I just encountered this today on git master. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Karol Bryd changed: What|Removed |Added CC||karo...@gmail.com --- Comment #28 from Karol Bryd --- Happens for me as well. Super irritating...it happens 8 out of 10 cases. What helps for me is to switch to console and pkill -f -9 kscreenlocker_greet. As far I remember, it started happening around Plasma 6.1. Maybe it is related, or not but, often monitor blinks multiple times and displays information that frequency is out of range. Sometimes only one screen is detected (monitor has to be enabled via Nvidia settings app), sometimes monitors display the same screen. I have a two monitor setup. Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.4-200.fc40.x86_64 (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62,7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C91 System Version: 2.0 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #27 from Vedran Rodic --- I experience the same issue. Latest Arch Linux on Xorg, single monitor, open source Radeon drivers. Linux 6.10.4 kscreenlocker 6.1.4 xorg-server 21.1.13 xf86-video-amdgpu 23.0.0 sddm 0.21.0 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Vedran Rodic changed: What|Removed |Added CC||th...@ginkel.com --- Comment #26 from Vedran Rodic --- *** Bug 483722 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Vedran Rodic changed: What|Removed |Added CC||quickis...@gmail.com --- Comment #25 from Vedran Rodic --- *** Bug 489846 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Vedran Rodic changed: What|Removed |Added CC||vro...@gmail.com Version|6.1.1 |6.1.4 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 wire_witch changed: What|Removed |Added CC||eliza.ture...@tuta.io --- Comment #24 from wire_witch --- I can confirm that the bug still happens on Plasma version 6.1.4. I also found a simple temporary workaround. I commented out the entire Image object with id: albumArt, starting at line 31 in the file /usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/MediaControls.qml This will remove the album art from the lock screen, but will also stop the bug from happening. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #23 from once-sol...@proton.me --- I can confirm this still happens in Plasma 6.1.4 on AMD, mesa 24.1.5 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Andrew M changed: What|Removed |Added CC||quantumpha...@gmail.com --- Comment #22 from Andrew M --- Another Nvidia on X11 user here. Here's my observation: I get the described freeze/lag when the display is powered down but only when using the Nvidia proprietary driver on my work PC's GeForce GT 1030. Changing from proprietary driver to the nouveau driver solves the problem at the expense of everything else being generally laggy, nouveau being nouveau. No freezing issues seen on my 2 personal computers with AMD graphics on Wayland. Questions to ask others here are: * Does this (still) affect AMD and Intel graphics? I see the bug submitter was on AMD. * Does switching from nvidia proprietary to nouveau stop this from happening? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #21 from Antonio --- Important note (sorry I didn't include it earlier, I just noticed...). This only happens when I am using only nvidia. In hybrid or integrated mode, this does not happen. Is that the case for other people that had the problem? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #20 from Antonio --- (In reply to Nate Graham from comment #19) > (In reply to Antonio from comment #18) > > I am also having issues with this, without any programs open. Issues started > > when updating to Plasma 6.1. > > > > Hardware Information > > - 12th Gen Intel(R) Core(TM) i7-12700H (12+8) @ 4.70 GHz > > - Intel Iris Xe Graphics @ 1.40 GHz [Integrated] > > - NVIDIA GeForce RTX 3060 Mobile / Max-Q [Discrete] > > - Software Information > > - Arch Linux x86_64 > > - 6.9.10-arch1-1 > > - sddm 0.21.0 (X11) > > - KDE Plasma 6.1.3 > > With this exact same log messaging? > > MetaObject::invokeMethod: No such method > ScreenLocker::AccessDeniedNetworkReply::error(QNetworkReply::NetworkError) > QMetaObject::invokeMethod: No such method > ScreenLocker::AccessDeniedNetworkReply::error(QNetworkReply::NetworkError) > file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/ > lockscreen/MediaControls.qml:31:13: QML QQuickImage: Blocked request. > > Or no? I tried running the same file as comment #0, but that locked the screen for the root user and didn't output that. Are the logs for the normal flow stored somewhere? I don't know where to locate it, sorry. If this adds any value, when putting the pc to sleep, with the option of locking after wakeup, this problem doesn't happen. It also doesn't happen when locking with "super L" + "L". It only happens after automatic lock with any specified time (I set it to 1 minute for easy reproduction). Also, ocasionally, the password input will never pop up and will have to reboot through tty3. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #19 from Nate Graham --- (In reply to Antonio from comment #18) > I am also having issues with this, without any programs open. Issues started > when updating to Plasma 6.1. > > Hardware Information > - 12th Gen Intel(R) Core(TM) i7-12700H (12+8) @ 4.70 GHz > - Intel Iris Xe Graphics @ 1.40 GHz [Integrated] > - NVIDIA GeForce RTX 3060 Mobile / Max-Q [Discrete] > - Software Information > - Arch Linux x86_64 > - 6.9.10-arch1-1 > - sddm 0.21.0 (X11) > - KDE Plasma 6.1.3 With this exact same log messaging? MetaObject::invokeMethod: No such method ScreenLocker::AccessDeniedNetworkReply::error(QNetworkReply::NetworkError) QMetaObject::invokeMethod: No such method ScreenLocker::AccessDeniedNetworkReply::error(QNetworkReply::NetworkError) file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/MediaControls.qml:31:13: QML QQuickImage: Blocked request. Or no? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Antonio changed: What|Removed |Added CC||antonio.ti...@proton.me --- Comment #18 from Antonio --- I am also having issues with this, without any programs open. Issues started when updating to Plasma 6.1. Hardware Information - 12th Gen Intel(R) Core(TM) i7-12700H (12+8) @ 4.70 GHz - Intel Iris Xe Graphics @ 1.40 GHz [Integrated] - NVIDIA GeForce RTX 3060 Mobile / Max-Q [Discrete] - Software Information - Arch Linux x86_64 - 6.9.10-arch1-1 - sddm 0.21.0 (X11) - KDE Plasma 6.1.3 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #17 from once-sol...@proton.me --- (In reply to TraceyC from comment #16) > From the output, it looks like it's the media controls on the lock screen > that blocked the unlock request. It makes me wonder what was playing at the > time, and through what application > It makes me wonder if the network stack hadn't fully woken yet and was being > polled by the media widget, which hung waiting for the still sleeping > service? > > Setting to confirmed since the problem still happens for the OP I usually have Spotify running at pretty much at all times, but as far as I remember, I actually did run a test with Spotify closed where it still happened. Also tried with the .deb(AUR) version and Flatpak version. However, I don't recall if I had say, Firefox open, with youtube, which would still work with the media play widget, yes? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 TraceyC changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 --- Comment #16 from TraceyC --- >From the output, it looks like it's the media controls on the lock screen that blocked the unlock request. It makes me wonder what was playing at the time, and through what application It makes me wonder if the network stack hadn't fully woken yet and was being polled by the media widget, which hung waiting for the still sleeping service? Setting to confirmed since the problem still happens for the OP -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 once-sol...@proton.me changed: What|Removed |Added Version|6.1.0 |6.1.1 --- Comment #15 from once-sol...@proton.me --- (In reply to Nate Graham from comment #13) > That looks like a different issue. This one looks more likely to be related > to the odd network errors: > > giu 26 08:26:49 betelgeuse kscreenlocker_greet[126137]: > QMetaObject::invokeMethod: No such method > ScreenLocker::AccessDeniedNetworkReply::error(QNetworkReply::NetworkError) > > For anyone affected who sees those errors, are you using a non-default login > screen theme, or are you using a remote URL for your avatar image, or are > you on a network home directory or something? Is there *anything* > network-related that might be unusual with respect to your setup that you > can comment on? Nothing remote, and just the default lock screen. To be precise, it happens on both default, and non-default login themes. I probably won't be much help in the future, as I've had to switch desktop. But I did a quick test on 6.1.2, and can confirm it still happens there. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #14 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #13 from Nate Graham --- That looks like a different issue. This one looks more likely to be related to the odd network errors: giu 26 08:26:49 betelgeuse kscreenlocker_greet[126137]: QMetaObject::invokeMethod: No such method ScreenLocker::AccessDeniedNetworkReply::error(QNetworkReply::NetworkError) For anyone affected who sees those errors, are you using a non-default login screen theme, or are you using a remote URL for your avatar image, or are you on a network home directory or something? Is there *anything* network-related that might be unusual with respect to your setup that you can comment on? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #12 from Simone Lazzaris --- Likely a duplicate of https://bugs.kde.org/show_bug.cgi?id=485084 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Simone Lazzaris changed: What|Removed |Added Version|6.0.1 |6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094
Simone Lazzaris changed:
What|Removed |Added
CC||sim...@omni.it
--- Comment #11 from Simone Lazzaris ---
I think I'm starting to see the same issue: it happens when the screen saver
kicks in *and* the screen(s) turns off. If I try to log back in, I'm greeted
with a black screen and the writing
"the screen locker is broken and unlocking is not possible anymore". Then there
are instructions about switching to a console and "manually" unlock the screen
with the "loginctl unlock-session" command.
Which works, so that is an inconvenience but not a show stopper.
Journalctl reports:
```
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126137]:
QMetaObject::invokeMethod: No such method
ScreenLocker::AccessDeniedNetworkReply::error(QNetworkReply::NetworkError)
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126137]:
QMetaObject::invokeMethod: No such method
ScreenLocker::AccessDeniedNetworkReply::error(QNetworkReply::NetworkError)
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126303]: qt.qpa.wayland: Loading
shell integration failed.
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126303]: qt.qpa.wayland:
Attempted to load the following shells QList("layer-shell")
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126303]: qt.qpa.plugin: Could
not load the Qt platform plugin "wayland" in "" even though it was found.
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126303]: This application failed
to start because no Qt platform plugin could be initialized. Reinstalling the
application may fix this problem.
Available platform
plugins are: offscreen, vnc, linuxfb, eglfs, xcb, minimalegl, minimal, wayland,
wayland-egl, vkkhrdisplay.
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126307]: qt.qpa.wayland: Loading
shell integration failed.
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126307]: qt.qpa.wayland:
Attempted to load the following shells QList("layer-shell")
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126307]: qt.qpa.plugin: Could
not load the Qt platform plugin "wayland" in "" even though it was found.
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126307]: This application failed
to start because no Qt platform plugin could be initialized. Reinstalling the
application may fix this problem.
Available platform
plugins are: offscreen, vnc, linuxfb, eglfs, xcb, minimalegl, minimal, wayland,
wayland-egl, vkkhrdisplay.
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126314]: qt.qpa.wayland: Loading
shell integration failed.
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126314]: qt.qpa.wayland:
Attempted to load the following shells QList("layer-shell")
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126314]: qt.qpa.plugin: Could
not load the Qt platform plugin "wayland" in "" even though it was found.
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126314]: This application failed
to start because no Qt platform plugin could be initialized. Reinstalling the
application may fix this problem.
Available platform
plugins are: offscreen, vnc, linuxfb, eglfs, xcb, minimalegl, minimal, wayland,
wayland-egl, vkkhrdisplay.
```
I'm using archlinux, kde 6.1.0, framework 6.3.0 on wayland.
Note that this wasn't happening until I upgraded from the 6.0.X branch.
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 TraceyC changed: What|Removed |Added CC||kde...@tlcnet.info -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #10 from sta...@tuta.io --- Well, changing the Plasma style didn't change anything for me either. I'm honestly at a loss for how to really test this. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #9 from sta...@tuta.io --- It happened on both Wayland and X11, yes. I can't, currently, check whether switching the Plasma style "fixes" it, as I'm not near that machine, but will get back as soon as I've tried. :) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #8 from Cherkah --- > plasma style to something other than "Breeze"? For example "Breeze Dark?" Not > the global scheme or the color > scheme; just the Plasma style. my plasma style it is "lightly" & it happens The only way to overcome the problem is to " killall plasmashell && kstart plasmashell " -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #7 from Cherkah --- > plasma style to something other than "Breeze"? For example "Breeze Dark?" Not > the global scheme or the color > scheme; just the Plasma style. my plasma style it is "lightly" & it happens -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #6 from Nate Graham --- For people affected, does the issue go away if you change your Plasma style to something other than "Breeze"? For example "Breeze Dark?" Not the global scheme or the color scheme; just the Plasma style. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Cherkah changed: What|Removed |Added CC||cherifkah...@gmail.com --- Comment #5 from Cherkah --- i've the same issue && when i lock manually the screen with meta+L everything is OK. it happen on Wayland as i am using wayland. i was thinking that bug was related to my "resume kernel" setting or with my Graphics Processor unit but apparently it is not. Operating System: EndeavourOS KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 Gio of RAM Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Nate Graham changed: What|Removed |Added Summary|kscreenlocker becomes |When monitor goes to sleep |unresponsive/stuck when |and system locks, |unlocking |kscreenlocker becomes ||unresponsive/stuck when ||monitor wakes up --- Comment #4 from Nate Graham --- Thanks. Does it happen on Wayland too, or only X11? -- You are receiving this mail because: You are watching all bug changes.
