SUMMARY STEPS TO REPRODUCE 1. Let the computer stay idle for a bit, until it locks itself 2. Log in on the lock screen 3. Open the Application Menu OBSERVED RESULT Opened windows stay open, work just fine, but there is no background and the taskbar disappears. The only way to use the system again is to use "killall kwin_wayland" in tty, and launch the session again. EXPECTED RESULT The application menu should open and be usable. SOFTWARE/OS VERSIONS Artix Linux 64-bit, kernel 5.13.9-zen KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 HARDWARE AMD Ryzen 5 2600 AMD Radeon RX 560
NOTE: I have two displays, and it only happens, if I use it on my primary one. May have something to do with the two displays having different refresh rates. (One is 75Hz, the other one, on which it doesn't happen, is 60Hz)
Created attachment 140657 [details] Log from redirecting stderr into a file. This is the best I can do right now. It's kind of short, because I only started a session and triggered the crash manually by locking, signing in, and then opening the application menu a few times.
Are you really using Mangonel, and not Kickoff or some other menu? Also, can you please attach a backtrace of the crash? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Hello, thanks for your response. I'm sorry for the confusion that I have caused, as I'm using the default KDE application menu (which is Kickoff) rather than Mangonel. Quick question; how does one run gdb on Kickoff? Should I use plasma-desktop instead? ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, August 12th, 2021 at 4:41 PM, Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=440871 > > Nate Graham nate@kde.org changed: > > What |Removed |Added > ---------------------- > > CC| |nate@kde.org > Status|REPORTED |NEEDSINFO > Resolution|--- |BACKTRACE > > > --- Comment #3 from Nate Graham nate@kde.org --- > > Are you really using Mangonel, and not Kickoff or some other menu? > > Also, can you please attach a backtrace of the crash? See > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > You are receiving this mail because: > > You reported the bug.
Yep, you would run gdb on plasmashell itself.
What package contains plasmashell? Because plasma-desktop isn't it. Running gdb on plasmashell after compiling plasma-desktop with -DCMAKE_BUILD_TYPE=RelWithDebInfo makes plasmashell freeze. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, August 12th, 2021 at 6:21 PM, Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=440871 > > Nate Graham nate@kde.org changed: > > What |Removed |Added > ---------------------- > > Product|Mangonel |plasmashell > CC| |mikel5764@gmail.com, > | |plasma-bugs@kde.org > Keywords| |wayland > Component|mangonel |Application Launcher > | |(Kickoff) > Assignee|martin.sandsmark@kde.org |kde@davidedmundson.co.uk > > > Target Milestone|--- |1.0 > > Version|1.1 |5.22.4 > > --- Comment #5 from Nate Graham nate@kde.org --- > > Yep, you would run gdb on plasmashell itself. > > ---------------------------------------------- > > You are receiving this mail because: > > You reported the bug.
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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!