|
Description
Not all users are savvy enough for Control-Alt-Fx. There should be a user friendly failsafe/bailout/etc GUI for when X becomes unresponsive due to the user becoming trapped inside an application, or when X freezes. Also, sometimes Control-Alt-Fx isn't even possible and my guess is that X is preventing this somehow (as the mouse pointer is usually still movable). Both of these problems should be addressed with a rock-solid failsafe system (or two). Perhaps this could be done by extending the bullet-proof-X project somehow for ending programs while stuck in X and X is still functioning, and there has to be some way that X can be terminated or restarted when X is so borked that even a Control-Alt-Backspace isn't working.
Problem #1 specifics (desktop inaccessible): When X is still functional enough, you can use Ctrl-Alt-Bksp, but this may destroy some unsaved work, but some type of failsafe to use before that happens would be better. Adding the System Monitor as an option to the shutdown menu which is accessible by Control-Alt-Delete may be one solution as long as that shutdown window will override and work in any and all screen modes or resolutions X may be in. Whatever the solution, it needs to be easy and obvious for new users to perform, so Ctrl-Alt-Del is the obvious choice.
Problem #2 specifics (X lockup, or shortcut keys unresponsive): Perhaps an additional program which does a very simple check on the X server periodically could address this second problem. Linux should be virtually crash-proof, lets help keep that image. Using the reset button should be a no-no, and logging in remotely shouldn't have to be done. You can't count on X not to crash, but the kernel is usually rock solid. Yes, X should be fixed to not crash, but something to back it up wouldn't hurt. This would help add polish to the system.
Tags:
(none)
Attachments
No attachments.
Duplicates
Comments
|
Eldmannen wrote on the 9 Jun 08 at 00:06
| |
Yeah, X needs to be improved that it is rock solid.
|
|
Primož Papič wrote on the 9 Jun 08 at 09:42
|
Yes I agree...
For problem #1:
Even though if you choose (at least in KDE) to continue the last session you will not loose any of unsaved work.
I had to do that and every thing worked and was as it were before. Even music that I listened before I had to restart started playing from there where it stop...
For problem #2:
I might once had this, and had to push the reboot button, but again after it booted again it worked fine, and everything was there...
But still +1; I don't want a X freezing...
|
|
tgape wrote on the 10 Jun 08 at 01:59
|
There are two basic reasons X becomes stuck that I am aware of.
The first of these is sheer system resource utilization. Most fixes I've seen for this reduce the perceived responsiveness of the active program - the opposite of what most users want. There is probably a potential fix out there that will make everyone happy, but it'll be tricky. This issue can cause either level of problem that you've noticed. Normally, when it causes an apparent lockup, the shortcut keys will still work - but it could be hours before the system gets to the point of actually responding to them.
The second of these is that an application (usually the active one) remaps keys, such that the various abort mechanisms don't work. I would personally solve this one by making one key combination (for example, the universal control-alt-delete) be protected from this. This sequence should be smart enough to recognize when an application has modified the screen in such a way that it cannot display, and either change it back, or kill the application in question (preferably the former, of course - resorting to the later only if it is the only option.) If such a remap is then followed by the application having problems, the system basically requires a reboot. This is frequently associated with applications that want to run in full screen mode.
|
|
leprasmurf wrote on the 19 Aug 08 at 00:30
| |
Additionally, it may be useful to some to have the ability to boot into this failsafe mode from the bootloader. A single user mode GUI?
|
|
Auzy wrote on the 19 Aug 08 at 06:47
|
I changed to the wrong graphics card driver in X, and it would no longer start. In windows, doing so simply leaves the user with a lame 16color desktop.
We should NEVER drop into a terminal if X has problems. Because the people who need X the most, will be the least likely to be able to fix from terminal.
|
Post your comment
|
