[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #31 from Henning --- sorry, I meant "I didnt have situations like this since reporting the FR", at least not well reproducible. I will use iostat if I find such a situation, but in general such a tool is really really needed for random edge cases where bugs simply occur. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 Henning changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #30 from Henning --- I did not have issues like this. This is a "whishlist" Feature request though so I dont think it is relevant. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #29 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.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #28 from Henning --- iostat is not installed on my system but I can layer it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 Harald Sitter changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #27 from Harald Sitter --- When your system is idle what is the output of iostat When you clone firefox what is the output of iostat -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 Henning changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #26 from Henning --- Created attachment 165779 --> https://bugs.kde.org/attachment.cgi?id=165779=edit the requested debug info -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 Harald Sitter changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #25 from Harald Sitter --- Please post the output of tail -n +1 /sys/block/*/queue/scheduler tail -n +1 /sys/block/*/queue/rotational ls /sys/block/*/mq mount lsblk sudo lshw -class disk -class storage grep -C 5 -r queue/scheduler /usr/lib/udev When your system is idle what is the output of iostat When you clone firefox what is the output of iostat -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 Henning changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #24 from Henning --- sorry, I should have used my own sysinfo tool, kinfo seems to have a bug. Wayland, always. what tail command, I didnt use any? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #23 from Harald Sitter --- The output of mount may also be useful -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 Harald Sitter changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #22 from Harald Sitter --- . -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #21 from Harald Sitter --- Wayland or X11? Please paste the entire output of the tail command. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 Henning changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #20 from Henning --- [none] mq-deadline kyber bfq Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 Kernel Version: 6.6.14-200.fc39.x86_64 (64-bit) Graphics Platform: offscreen Processors: 4 × AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx Memory: 5.7 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics systemd-oomd-defaults-254.8-2.fc39.noarch thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #19 from Harald Sitter --- Also, are you on wayland or x11? And what's the output of `kinfo`? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 Harald Sitter changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #18 from Harald Sitter --- Talking about, what are your schedulers? `tail -n +1 /sys/block/*/queue/scheduler` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #17 from Harald Sitter --- You should take that up with Fedora. It sounds like your IO scheduler is ill equipped to deal with your work load. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #16 from Henning --- for example I am currently building Firefox from source, and even before any compilation the damn Mercurial is using 23% of CPU and the Plasmapanel is just not reacting. This is what I mean by "plasmashell is randomly freezing on load" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #15 from Henning --- hey, yes @Nate that is what I meant. A process that allows opening a window that graphically kills apps. Maybe this would be an extra KWin with the interface and just launching this program? I dont know how Windows does it, but it always works, which is really needed. Also I dont understand why the Plasmashell would freeze if Firefox freezes. Why isnt the system more privileged? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #14 from Harald Sitter --- On second thought, we might get them from libinput directly (assuming appropriate permissions on the input devices) so we'd have to write some sort of helper that detects a shortcut and then restarts kwin. I am not sure a shortcut to restart kwin is all that meaningful though? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #13 from Harald Sitter --- We don't get keyboard input if kwin is stuck, do we? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #12 from Nate Graham --- We could kill it and spawn a new one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #11 from Harald Sitter --- When kwin (wayland) freezes we can't display anything I think. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #10 from Nate Graham --- I've had freezes where the window killer UI didn't appear. Probably because it was KWin that was frozen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #9 from Harald Sitter --- (In reply to Nate Graham from comment #8) > But it would help in the case of a graphical freeze. Isn't that covered by Ctrl-Esc? Or, it should anyway ^^ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #8 from Nate Graham --- Right, if we have to launch something new, it wouldn't help in the OOM case. But it would help in the case of a graphical freeze. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #7 from Harald Sitter --- (In reply to Nate Graham from comment #6) > and spawn Right, that's the problem. We cannot spawn anything, the system is out of memory. We cannot do anything that would allocate any new memory. That likely includes shortcut handling, which would probably do allocations somewhere under the hood. That is on top of the fact that the kernel also must allow a theoretical task manager to even do any work, which I am not convinced it will since it the kernel is busy trying to fix the OOM situation. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #6 from Nate Graham --- Some kind of low-level always running helper I guess. It could respond to a Ctrl+Alt+Delete (or whatever) and spawn a new kwin_wayland instance and System monitor. Or something like that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 --- Comment #5 from Harald Sitter --- I see. How would that work though? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479538] Some kind of always-accessible troubleshooting tool when parts of the system are unresponsive
https://bugs.kde.org/show_bug.cgi?id=479538 Nate Graham changed: What|Removed |Added Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Severity|major |wishlist CC||n...@kde.org Product|plasmashell |kwin Component|general |general Target Milestone|1.0 |--- Summary|Fix RAM management, make|Some kind of |Plasmashell a privileged|always-accessible |process |troubleshooting tool when ||parts of the system are ||unresponsive --- Comment #4 from Nate Graham --- I think what he means is that somehow, you should be able to show a GUI window capable of killing processes even when the rest of the system is unresponsive. The reference so Ctrl+Alt+Delete is a Windows-ism; on Windows, hitting this keyboard shortcut always shows a troubleshooting screen from which you can open the Task Manager even when everything else is frozen. My wife has expressed a similar desire in response to app and system freezes in the past. I think it's a reasonable thing to have, in some capacity at least. This is probably not something that would be done in plasmashell though; moving to KWin. -- You are receiving this mail because: You are watching all bug changes.
