Created attachment 136872 [details] There is a log in moment freeze on the picture SUMMARY The working environment freezes STEPS TO REPRODUCE The system can freeze both without open programs, and with a large number of open ones. So I don't know how to repeat it. OBSERVED RESULT Periodically, system freezes, and no buttons on panels work. At this time, the CPU load is 2-5%, the memory is used by 10-20%. Swapfs works. Additional packages haven't installed (used default settings of system). I use an additional monitor that is connected via a thunderbolt 3-hdmi cable, but without this monitor, the system also freezes. Only a hard reboot of the system helps - by holding down the shutdown key or restarting plasma (killall plasmashell && kstart5 plasmashell). The program panel freezes completely, the clipboard doesn't work, I cursor selection can't switch of the cursor to another program, but the keyboard shortcuts work, so I can call the console and use the restart plasmashell command EXPECTED RESULT The panel with open programs doesn't freeze. The clipboard works. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION * Laptop: Razer Blade Stealth 13 RZ09-0327 (2020 year) * Operating System: Manjaro Linux * KDE Plasma Version: 5.21.3 * KDE Frameworks Version: 5.80.0 * Qt Version: 5.15.2 * Kernel Version: 5.11.6-1-MANJARO * OS Type: 64-bit * Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz * Memory: 15.4 Gb of RAM * Graphics Processors: Mesa Intel® Xe Graphics; NVIDIA GeForce GTX 1650 Ti Max-Q (4GB GDDR6 VRAM)
Have you logged in as root?
no
(In reply to Alex from comment #2) > no (In reply to Nate Graham from comment #1) > Have you logged in as root? No, I logged in as user.
Thanks.
Could you speak date when will be fix this problem? This bug isn't giving working in normal mode.
10:16 AM, August 24th, 2021
(In reply to Nate Graham from comment #6) > 10:16 AM, August 24th, 2021 Is it joke?))
When frozen can you run sudo gdb --pid `pidof plasmahell` wait for it to attach then type "bt" and attach the log
(In reply to David Edmundson from comment #8) > When frozen can you run > > sudo gdb --pid `pidof plasmahell` > > wait for it to attach then type "bt" > > and attach the log Yes, I can. When will be frozen I will do this.
(In reply to David Edmundson from comment #8) > When frozen can you run > > sudo gdb --pid `pidof plasmahell` > > wait for it to attach then type "bt" > > and attach the log Your command is not working sudo gdb --pid `pidof plasmahell` "gdb: option '--pid' requires an argument Use `gdb --help' for a complete list of options." sudo gdb --pid=`pidof plasmahell` "...Type "apropos word" to search for commands related to "word". Argument required (process-id to attach). (gdb) bt No stack. (gdb) " What should I do?
>What should I do? Fix my spelling of "plasmashell" in the gdb line.
(In reply to David Edmundson from comment #11) > Fix my spelling of "plasmashell" in the gdb line. (gdb) plasmashell Undefined command: "plasmashell". Try "help". (gdb) Command is not working What is next?)))
(In reply to David Edmundson from comment #8) > When frozen can you run > > sudo gdb --pid `pidof plasmahell` > > wait for it to attach then type "bt" > > and attach the log [New LWP 32336] [New LWP 32337] [New LWP 33999] [New LWP 35480] [New LWP 41903] [New LWP 41904] [New LWP 43984] Error while reading shared library symbols for /usr/lib/libpthread.so.0: Cannot find user-level thread for LWP 43984: generic error --Type <RET> for more, q to quit, c to continue without paging-- 0x00007fbb0437a9ba in __futex_abstimed_wait_common64 () from /usr/lib/libpthread.so.0 (gdb) bt #0 0x00007fbb0437a9ba in __futex_abstimed_wait_common64 () at /usr/lib/libpthread.so.0 #1 0x00007fbb04374260 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #2 0x00007fbb05345254 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x00007fbb06f89277 in () at /usr/lib/libQt5Quick.so.5 #4 0x00007fbb06ff2d67 in QQuickWindow::event(QEvent*) () at /usr/lib/libQt5Quick.so.5 #5 0x00007fbb061c8762 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #6 0x00007fbb0552781a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #7 0x00007fbb058f1319 in QPlatformWindow::windowEvent(QEvent*) () at /usr/lib/libQt5Gui.so.5 #8 0x00007fbb061cf447 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #9 0x00007fbb0552781a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #10 0x00007fbb0557f6a5 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #11 0x00007fbb0557ff8a in () at /usr/lib/libQt5Core.so.5 #12 0x00007fbb038f702c in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #13 0x00007fbb0394ab59 in () at /usr/lib/libglib-2.0.so.0 #14 0x00007fbb038f4781 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #15 0x00007fbb05580321 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #16 0x00007fbb0552617c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #17 0x00007fbb0552e634 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #18 0x000055efe6d6120b in () #19 0x00007fbb04eecb25 in __libc_start_main () at /usr/lib/libc.so.6 #20 0x000055efe6d6133e in () (gdb) Did I do the right? Is this information enough?
David Edmundson ??
Help me please. My current system: Operating System: Manjaro Linux KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.11.19-1-MANJARO Problem's actual
Information was added; changing status. David, does this help at all?
Who can help me?
Patience is appreciated. :) See https://community.kde.org/Get_Involved/Issue_Reporting#Have_realistic_expectations
(In reply to Nate Graham from comment #18) > Patience is appreciated. :) See > https://community.kde.org/Get_Involved/ > Issue_Reporting#Have_realistic_expectations Ok, Thanks. I will be wait
Hello and thank you again for the bug report! Unfortunately we were not able to address it yet, nor even manage to reproduce the issue ourselves. Can we ask you to please check if this issue is still happening with Plasma 5.27? If it is, please change the status to REPORTED. Thanks a lot!
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!