[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Fabian Beutel changed: What|Removed |Added Blocks|474811 | Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=474811 [Bug 474811] kscreenlocker breaks randomly (multiscreen setup), needs manual unlock -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Fabian Beutel changed: What|Removed |Added Blocks||474811 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=474811 [Bug 474811] kscreenlocker breaks randomly (multiscreen setup), needs manual unlock -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #54 from Nate Graham --- These seem suspicious: Sep 21 08:01:27 latitude kscreenlocker_greet[14825]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Sep 21 08:01:27 latitude kscreenlocker_greet[14825]: The Wayland connection experienced a fatal error: Das Argument ist ungültig [Invalid argument] Sep 21 08:01:27 latitude kscreenlocker_greet[14837]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Sep 21 08:01:27 latitude kscreenlocker_greet[14837]: The Wayland connection broke. Did the Wayland compositor die? Maybe a Wayland protocol error is causing kwin_wayland to crash, which caused the issue to happen. That said, I doubt that this is what was happening to Christian in the original bug report from 2017. So would you mind submitting a new bug report for that issue? Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Fabian Beutel changed: What|Removed |Added CC||f...@hedgeware.net --- Comment #53 from Fabian Beutel --- Created attachment 161773 --> https://bugs.kde.org/attachment.cgi?id=161773&action=edit output of journalctl after the issue occurs I also have this problem semi-regularly on Arch-Linux and Plasma 5.27.8. I suspect that it occurs more often when a multiscreen setup (docking station) is involved, but I think I also experienced it in the past just from waking up with only the laptop screen (but I'm not certain about this). Here is the relevant part from journalctl. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 idoitprone changed: What|Removed |Added CC||monkeyboy...@yahoo.com --- Comment #52 from idoitprone --- Is this bug related to the bug in plasma mobile? https://invent.kde.org/teams/plasma-mobile/issues/-/issues/236 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #51 from Hugh Phoenix-Hulme --- Killing one is working for me, but it's not a great solution. To minimise hassle one could write a script to kill the first process if there are multiple and run it as a cron job every second, but that's obviously not ideal. I'm also seeing this on Ubuntu, not Arch. But generally only after resuming, not just from locking, and not consistently. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 aux...@gmail.com changed: What|Removed |Added CC||aux...@gmail.com --- Comment #50 from aux...@gmail.com --- An easy way to unlock the screen if the locker freezes as root is: loginctl unlock-sessions. An issue I've been having for a long time with the locker with a dual monitor setup is that if I try to unlock immediately as it attempts to lock the screen, there is a high probability that the displays will freeze empty, only the mouse cursor will be visible and if I move the mouse cursor to the primary monitor, it will be leaving a trail of mouse cursors behind, which has limited length, i.e. the more I move the mouse, the older parts of the trail are erased. loginctl unlock-sessions does nothing when this occurs, I can only restart the session. I'm not certain it is the same issue as this one, though. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Hugh Phoenix-Hulme changed: What|Removed |Added CC||h...@webnet.org.uk --- Comment #49 from Hugh Phoenix-Hulme --- I'm getting this now, and I do see two instances of kscreenlocker_greet. I also see plasmashell and dolphin using high CPU at the same time. Next time it occurs I'll kill one and see if that solves for the other. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #48 from Vitaliy Filippov --- I don't think there are 2 of them... I always check processes with `ps ax|grep kscr` when I'm killing a stuck kscreenlocker_greet and I always see 2 processes: 1) /usr/lib/x86_64-linux-gnu/libexec/kf5/kscreen_backend_launcher 2) kscreenlocker_greet And I always kill the second one after which it restarts and I log back in :) So maybe threads lock each other, but not processes... -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #47 from Nate Graham --- Thanks! Looks like two kscreenlocker_greet processes are running and one is stuck in a futex while the other is in a pselect64 syscall. Maybe they're blocking one another. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Vitaliy Filippov changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #46 from Vitaliy Filippov --- Created attachment 15 --> https://bugs.kde.org/attachment.cgi?id=15&action=edit hung kscreenlocker stack traces with debug info -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #45 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 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #44 from Vincent PINON --- > The error occurred several times again, and actually "kscreenlocker" line > doesn't appear every time in journalctl, whereas kwin_wayland failure is > always here. > It was still on 5.26.90 (latest available in Debian testing) ; I'm > installing 5.27.2 from Debian unstable, will see in the next days and let > you know... I forgot to report back: I still had the crash with plasma 5.27.2. It is always in kwin_wayland, so *not this bug*. Since then I reverted to X11 session to avoid this annoyance, so I don't track the problem anymore, sorry. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #43 from Harald Sitter --- Works fine for me :| -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #42 from Vitaliy Filippov --- Ok, I can do that, the bug still reproduces almost every time when compositing is disabled -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Harald Sitter changed: What|Removed |Added CC||sit...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #41 from Harald Sitter --- Unfortunately that backtrace isn't terribly useful. Please check https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Install_debugging_packages -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 zellox changed: What|Removed |Added CC||zel...@fastmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #40 from Vitaliy Filippov --- Seems that it still hangs when compositing is disabled, yeah. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #39 from Vitaliy Filippov --- Created attachment 157143 --> https://bugs.kde.org/attachment.cgi?id=157143&action=edit Stack traces of hung kscreenlocker_greet Ok, finally I got another hang with 5.27.2. Attaching stack traces of all threads... -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #38 from Vitaliy Filippov --- In fact it hasn't reproduced for me more since that 1 time. So it seems that it's almost fixed. Only 1 failure in 5 days with 5.27.2 by now :) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #37 from Vincent PINON --- (In reply to Vincent PINON from comment #29) > I have 2 laptops on Debian testing (plasma 5.26.90-1, qt 5.15.8+dfsg-2), > that regularly fail to unlock after sleep (but not always, haven't > identified the exact situation yet). > Here is a journalctl extract that seems relevant (note the "kernel: traps: > kscreenlocker_g"): The error occurred several times again, and actually "kscreenlocker" line doesn't appear every time in journalctl, whereas kwin_wayland failure is always here. It was still on 5.26.90 (latest available in Debian testing) ; I'm installing 5.27.2 from Debian unstable, will see in the next days and let you know... Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Rick Scholten changed: What|Removed |Added CC|khr...@proton.me| -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #36 from Vitaliy Filippov --- I almost thought it was fixed :) but it reproduced with 5.27.2 again, after a day of usage. :) I tend to think that it's still slightly better because today I only had to kill -9 it one time instead of several times as it was with <= 5.26.90... But it seems the bug is still there -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #35 from Vitaliy Filippov --- (In reply to Simon B from comment #34) > Is it still occurring with plasma 5.27.x? Some similar bugs got resolved > with this release Thanks for the information, I just installed 5.27.2, will check if the bug still persists -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Simon B changed: What|Removed |Added CC||sbutcher+b...@gmail.com --- Comment #34 from Simon B --- Is it still occurring with plasma 5.27.x? Some similar bugs got resolved with this release -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #33 from Vitaliy Filippov --- By the way, I don't use a multiscreen setup - for me it reproduces on a laptop without the external monitor, and with Intel integrated graphics (I also have nvidia proprietary driver installed but I don't think it's related to it). Vendor: Intel (0x8086) Device: Mesa Intel(R) HD Graphics 530 (SKL GT2) (0x191b) Version: 22.3.5 Accelerated: yes Video memory: 15889MB -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Vitaliy Filippov changed: What|Removed |Added CC||vita...@yourcmc.ru --- Comment #32 from Vitaliy Filippov --- I'm observing the same issue for something like 1-2 YEARS. Now I'm killing it with -9 multiple times a day :-/. If I remember correctly it started when Intel replaced the old driver with Iris. But I'm not sure 100%, maybe it reproduced even before it. Please fix it at last...) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #31 from Nate Graham --- (In reply to d.brown from comment #30) > Hello, I am coming from #456210. > > 1. Enter password at lock screen > 2. The login UI closes > 3. Instead of going to desktop as normal, a button that says "Unlock" appears > 4. Pressing it does nothing > > Resolution: 1920x1080, 1920x1080 > DE: Plasma 5.26.5 (Wayland) > > kscreenlocker_greet[30842]: kscreenlocker_greet: Greeter tried to quit > without being unlocked > kscreenlocker_greet[30842]: kscreenlocker_greet: Greeter tried to quit > without being unlocked > kscreenlocker_greet[30842]: kscreenlocker_greet: Greeter tried to quit > without being unlocked > > Unrelated: Could someone confirm if Wayland does or does not have Virtual > Consoles (ctrl+alt+fn)? That's Bug 456210, not related to this one. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 d.br...@hackion.com changed: What|Removed |Added CC||d.br...@hackion.com --- Comment #30 from d.br...@hackion.com --- Hello, I am coming from #456210. 1. Enter password at lock screen 2. The login UI closes 3. Instead of going to desktop as normal, a button that says "Unlock" appears 4. Pressing it does nothing Resolution: 1920x1080, 1920x1080 DE: Plasma 5.26.5 (Wayland) kscreenlocker_greet[30842]: kscreenlocker_greet: Greeter tried to quit without being unlocked kscreenlocker_greet[30842]: kscreenlocker_greet: Greeter tried to quit without being unlocked kscreenlocker_greet[30842]: kscreenlocker_greet: Greeter tried to quit without being unlocked Unrelated: Could someone confirm if Wayland does or does not have Virtual Consoles (ctrl+alt+fn)? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Vincent PINON changed: What|Removed |Added CC||vpi...@kde.org --- Comment #29 from Vincent PINON --- Hello, I have 2 laptops on Debian testing (plasma 5.26.90-1, qt 5.15.8+dfsg-2), that regularly fail to unlock after sleep (but not always, haven't identified the exact situation yet). Here is a journalctl extract that seems relevant (note the "kernel: traps: kscreenlocker_g"): 21:30:03 plasmashell[1236]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() 21:30:03 plasmashell[1236]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() 21:30:03 plasmashell[1236]: Checking screens: available: (QScreen(0x56222c70e3a0, name="HDMI-A-1")) redundant: QHash() fake: QSet() all: (QScreen(0x56222a3c13e0, name="eDP-1"), QScreen(0x56222c70e3a0, name="HDMI-A-> 21:30:03 plasmashell[1236]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:20: TypeError: Cannot read property 'pluginName' of null 21:30:03 plasmashell[1236]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75: TypeError: Cannot read property 'configuration' of null 21:30:03 plasmashell[1236]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:78: TypeError: Cannot read property 'pluginName' of null 21:30:03 plasmashell[1236]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:80: TypeError: Cannot read property 'configuration' of null 21:30:03 plasmashell[1236]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:81: TypeError: Cannot read property 'configuration' of null 21:30:03 plasmashell[1236]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:82: TypeError: Cannot read property 'configuration' of null 21:30:03 plasmashell[1236]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:83: TypeError: Cannot read property 'configuration' of null 21:30:03 plasmashell[1236]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:84: TypeError: Cannot read property 'configuration' of null 21:30:03 plasmashell[1236]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:16: TypeError: Cannot read property 'configuration' of null 21:30:03 plasmashell[1236]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:17: TypeError: Cannot read property 'configuration' of null 21:30:03 plasmashell[1236]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:18: TypeError: Cannot read property 'configuration' of null 21:30:03 bluetoothd[733]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. 21:30:03 bluetoothd[733]: sap-server: Operation not permitted (1) 21:30:03 kernel: Bluetooth: MGMT ver 1.22 21:30:03 bluetoothd[733]: Failed to set mode: Failed (0x03) 21:30:03 org_kde_powerdevil[14410]: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so" 21:30:03 kernel: traps: kscreenlocker_g[14218] general protection fault ip:7fa918e8bff4 sp:7ffd482882b8 error:0 in libQt5Qml.so.5.15.8[7fa918ca+2f1000] 21:30:03 org_kde_powerdevil[14416]: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so" 21:30:03 kded5[14411]: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so" 21:30:03 plasmashell[1236]: file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/FullRepresentation.qml:133:13: QML Loader: Possible anchor loop detected on centerIn. 21:30:03 plasmashell[14422]: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so" 21:30:03 kded5[14424]: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so" 21:30:03 plasmashell[14430]: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so" 21:30:03 kwin_wayland_wrapper[]: not a valid new object id (2), message get_registry(n) 21:30:03 kwin_wayland_wrapper[]: error in client communication (pid ) 21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id (43) 21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id (47) 21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id (44) 21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id (45) 21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id (39) 21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id (53) 21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id (38) 21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id (41) 21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id f
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #28 from Nate Graham --- It mostly shows that the NVIDIA driver is involved. Beyond that, I can't tell. But the issue doesn't seem NVIDIA-specific, as people with Intel GPUs and open-source Mesa drivers have reported experiencing it too. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #27 from jkallinge...@gmx.at --- Created attachment 156229 --> https://bugs.kde.org/attachment.cgi?id=156229&action=edit gdb backtrace coming from Bug 465113, hopefully this is somewhat helpful -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Rick Scholten changed: What|Removed |Added CC||khr...@proton.me -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Nate Graham changed: What|Removed |Added CC||jkallinge...@gmx.at --- Comment #26 from Nate Graham --- *** Bug 465113 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 soredake changed: What|Removed |Added CC|ndrzj1...@relay.firefox.com | -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Ferry changed: What|Removed |Added CC||ferry.t...@elsinga.info --- Comment #25 from Ferry --- I have this since I just updated from Kubuntu 22.04 to 22.10. I have multiple machine all with Intel gfx but this is the only one with dual monitors. Not sure if it is related to dual monitors or if I missed updating some conf file during the update. I have been monitoring processes (htop) and logs (journalctl) on the console (crtl-alt F2), but nothing seems to be consuming lots of cpu or spitting sensible messages. Switching to console and back after I typed the password does make the screen onlock. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Nate Graham changed: What|Removed |Added CC||alexander.fieroch@mpi-dortm ||und.mpg.de --- Comment #24 from Nate Graham --- *** Bug 442736 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Nate Graham changed: What|Removed |Added Priority|NOR |VHI -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Nate Graham changed: What|Removed |Added CC||ke...@myplaceonline.com --- Comment #23 from Nate Graham --- *** Bug 437520 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Nate Graham changed: What|Removed |Added CC||php4...@gmail.com --- Comment #22 from Nate Graham --- *** Bug 460353 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Nate Graham changed: What|Removed |Added Component|greeter |general -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Nate Graham changed: What|Removed |Added CC||n...@kde.org Severity|normal |critical Summary|kscreenlocker_greet freezes |kscreenlocker_greet freezes ||with multiscreen setup and ||blocks unlocking --- Comment #21 from Nate Graham --- I suppose there's a chance that Bug 409226 could automatically fix this. -- You are receiving this mail because: You are watching all bug changes.
