• [deleted]

  • Post #1
It's simple, because the GnuLinux graphics stack and GUI are faulty. At any time it can explode in your face, leaving you with a black screen with USB keyboard and mice peripherals that no longer respond. So think, you are doing important backup between hard drives, like me, with 4 mounted hard drive which contain important data, and after an hour when you come back to your computer to check the result, the monitor doesn't wake up anymore, you keyboard and mouse stop to respond. I let you imagine what you may feel at this moment and the disastrous consequences on your data because your disk will not be unmounted properly before you attempt to shutdown or reboot.
Can you imagine that in 2020 GnuLinux does not even come close to what it was doing in 1985 under Amiga and AmigaOS? What a shame. An Xorg crap and a damn wayland development which is now over 12 years with a result simply unacceptable to be taken seriously and be an Xorg replacement.

So, thx to ssh I was able to connect from another computer on my LAN to my desktop on which was running the ssh daemon, I was able to unmount my hard drives in a safe way and reboot my computer.

You SHOULD always have an ssh daemon running on your desktop.
You mean even other consoles don't work, is it an X failure or total graphics failure? Can it be related to screenlock ? It hasn't happened to me but I don't use DM, screenlock, just wm. The leaner the better. But then again when I mount volumes from other machines I usually also run ssh so I can mount my cache and update those systems as well without redownloading pkgs.

  • [deleted]

  • Post #3
Can it be related to screenlock ?
No. Screenlocking is disable as hybernation. Only screen energy saving is enable but I never got any issues with that before.
You mean even other consoles don't work, is it an X failure or total graphics failure?
It's hard to say if it was a total graphics failure, because the keyboard and mice was not responding anymore.
The leaner the better
Not totally agree of this philosophy. A GUI is supposed to works and not drive the rest of the peripheral with it and even better, in case of a crash the GUI should be able to restart automatically and recover the previous state. https://www.youtube.com/watch?v=nqi7KlTl6Uc

It is not by changing ingredients ( xorg > wayland ) that we necessarily obtain a better dish, it may also be necessary to replace the chef.
Sorry, I can't relate. Any X problems I ever had in arch-based systems I was able to switch tty and kill it. The only such problem of losing keyboard and mouse through X had been with antix-sid and this has been recent problem that came and went and came back with some upgrades. It happened as X was started not through the session. I didn't bother reporting it anywhere and didn't find similar problems but the system was running s6/66. Strange enough, chrooting from obarun to that installation and starting X as user didn't have the problem. Openbox worked better than it did ever before on antix. So I suspect some eudev problem, not X. When X would freeze on antix and rebooted, without starting X, the Xorg..log didn't report anything ... it was like the whole system was frozen still.

Powered by Obarun