| Summary: | no login after computer screen timedd out | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | laurie jarden <lauriej> |
| Component: | Screen locking | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | minor | CC: | cwo.kde, kdedev, nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | result of automated bug report | ||
|
Description
laurie jarden
2025-02-18 13:25:36 UTC
Created attachment 178516 [details]
result of automated bug report
No idea why screen went to sleep, all known systems set for computer to stay awake.
a common occurrence is the wrong screen is primary on login & boot-up.
> no typing of password was possible.
Can you clarify what this means? Were you able to type letters and see dots appear in the password field, but hitting return didn't work? Or else no dots ever appeared in the password field? Or else there was never a password field at all? Or else the screen was black with a movable cursor? Or else the screen was black with no cursor?
Let us know which one of these happened. Thanks!
The login window was visible, left mouse click left a vertical line for the curser but typing left no dots or text. Login was attempted on both monitors (Dell, different sizes & models) with the same effect. A different wireless mouse was attached and the pointer moved across the screen but still no login typing achieved. New login by mouse selecting a different person icon brought up that icon but still nothing typed in the login area. Mouse selecting the restart text worked as expected and login was achieved when the new login screen appeared. If you blindly type your password and press Enter or Return, does it work? Thank you for the replies. restart with both screens black no restart with both login screens login field showing no restart with both screens showing & moving mouse pointer to right screen yes login with right hand screen showing login area yes login with both screens showing login area yes login after lock screen with at least one login area showing yes login after lock screen with no login area showing no Backtrace Thread 1 (Thread 0x7f3a80e4e0c0 (LWP 2671)): [KCrash Handler] #4 0x00007f3a8669a13c in __pthread_kill_implementation () at /lib64/libc.so.6 #5 0x00007f3a86641436 in raise () at /lib64/libc.so.6 #6 0x00007f3a8662891a in abort () at /lib64/libc.so.6 #7 0x00007f3a86ef310c in ??? () at /lib64/libQt6Core.so.6 #8 0x00007f3a86ef4022 in QMessageLogger::fatal(char const*, ...) const () at /lib64/libQt6Core.so.6 #9 0x00007f3a7c5bdc80 in ??? () at /usr/lib64/qt6/plugins/kf6/kscreen/KSC_KWayland.so #10 0x00007f3a8700ebe1 in ??? () at /lib64/libQt6Core.so.6 #11 0x00007f3a8521fba2 in ??? () at /lib64/libffi.so.8 #12 0x00007f3a8521c3ed in ??? () at /lib64/libffi.so.8 #13 0x00007f3a8521f1ae in ffi_call () at /lib64/libffi.so.8 #14 0x00007f3a863fcc13 in ??? () at /lib64/libwayland-client.so.0 #15 0x00007f3a863fd3c9 in ??? () at /lib64/libwayland-client.so.0 #16 0x00007f3a863fd78b in wl_display_dispatch_queue_pending () at /lib64/libwayland-client.so.0 #17 0x00007f3a8648c492 in QtWaylandClient::QWaylandDisplay::flushRequests() () at /lib64/libQt6WaylandClient.so.6 #18 0x00007f3a86ff4f87 in QObject::event(QEvent*) () at /lib64/libQt6Core.so.6 #19 0x00007f3a86fada30 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt6Core.so.6 #20 0x00007f3a86fb3a20 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt6Core.so.6 #21 0x00007f3a87207a47 in ??? () at /lib64/libQt6Core.so.6 #22 0x00007f3a860ffef8 in ??? () at /lib64/libglib-2.0.so.0 #23 0x00007f3a86101ce8 in ??? () at /lib64/libglib-2.0.so.0 #24 0x00007f3a861024fc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #25 0x00007f3a87204ee3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt6Core.so.6 #26 0x00007f3a86fb58db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt6Core.so.6 #27 0x00007f3a86fb759a in QCoreApplication::exec() () at /lib64/libQt6Core.so.6 #28 0x0000560d2320923d in ??? () #29 0x00007f3a8662a2ae in __libc_start_call_main () at /lib64/libc.so.6 #30 0x00007f3a8662a379 in __libc_start_main_impl () at /lib64/libc.so.6 #31 0x0000560d232094b5 in ??? () Backtrace matches bug 496589. From the duplicates of that bug, it seems to be either harmless or potentially related to a system freeze, but I don't see reports of password entry not working. So the crash/backtrace may be unrelated to the actual issue. Bug 500441 is about problems unlocking in a rather narrow circumstance, but in that case the report says that login was possible after pressing "switch user" which does not seem to be the case here. Bug 482181 reports about problems unlocking if the keyboard is changed in between. Is this possibly involved here somehow? Bug 498709 seems to have a similar issue but on Plasma 5.27 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! Sorry for the delay. On the most recent run of zipper dup the problem disappeared. My system seems to be OK now. Thanks for the concern & help. Laurie |