[ksysguard] [Bug 390671] Add "Kill X Server" including Keyboard shortcut to Tools menu

Gregor Mi bugzilla_noreply at kde.org
Sun Feb 18 16:43:41 UTC 2018


https://bugs.kde.org/show_bug.cgi?id=390671

--- Comment #3 from Gregor Mi <codestruct at posteo.org> ---
> As for system monitor if you can read system monitor and
> open a tools menu, your X is working fine.
True. On the other hand, I recently was in a situation where only Ctrl+Esc ->
System Monitor was working (panel was gone and KRunner was not working; I could
see no way how to enter a command or logout; reason was a messed up Tumbleweed
upgrade).

About Nate's blog post: I thought the cited review was about _configuring_ the
shortcut ("It is difficult to find the option to configure/enable the desktop
session restart (X kill), normally activated by the Ctrl + Alt + Backspace
combo."). Not about invoking it. This bug report/wish is only about making the
existence of the shortcut more transparent.

I speak from my perspective as a normal who sometimes happens to be in abnormal
situations. I would feel better if our users are equipped with all available
tools to help themselves. I consider the System Monitor -> Tools menu not that
prominent to have a negative impact on a user doing daily work.

> It's a feature that has less and less relevance,
As long as X is used, I think it is relevant. Ok, when the time for
implementation comes and X is no longer used, then it makes less sense to go
through with it :-). I would be interested how things are handled in Wayland.
Will there be no kill shortcut or so?

> and used to be hit accidentally all the time.
The solution to this would be to disable the shortcut, wouldn't it? But it is
enabled by default and if we would have more transparence about it, I could
imagine the following situation: The user accidently triggers the feature and
somewhen later he discovers the shortcut in the Tools menu: then he has an
additional chance to realize what happend in the past and prevent it in the
future. :-)

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Plasma-devel mailing list