before moving away from Manjaro and switching to KDE Neon (which I really do not want to do, mainly because I like rolling releases and do not trust Ubuntu/Canonical), let me try to tell you about my increasingly troublesome relationship with Arch distros.
Over the past few months with Manjaro (KDE), the following issues started to show:
· After a while (really that vague, sometimes very quickly, sometimes only after a half hour or more) any program stops opening, no matter if tried from the menu (Application Launcher) or by clicking on an associated file, without any error message except when I click on a text file, then it says KDEinit can not open Kate.
· Related to that, although the menu (Application Launcher) is still opening, even basic OS functions stop working, like reboot and poweroff. The only chance is to open Yakuake (F12, that does still work) and type the respective command, which then mostly is replied with a “watchdog did not stop” warning and a few others (not always, and not always the same) before the machine restarts/shuts down.
· ISO files are sometimes recognised as such, sometimes are treated as text files (did you ever wait for Kate to open 3.2 GB?)
· Startup has become much slower. I have Manjaro installed on an external SSD drive (Angelbird SSD2GO, a real gem!) via USB3/USB3.1-C, which in the beginning responded in about 20 secs from turning on to login screen and another 7 secs from password confirmation to desktop; now it takes at least a minute or more, I didn’t take the time. Especially the second part, after login confirmation, has become disturbingly slow.
· Many times, or rather, almost every other time, the wired network connection fails. I have set it to not connect automatically, and when I click “connect”, after a few seconds of spinning the red symbol shows, then going back to the not-connected symbol. Sometimes I have to try three, four times before I am actually connected.
· Sometimes (vague again, because not consistent) when leaving the machine for a while (long enough for a screen lock, that is), coming back would give me a black screen with the message
The screen locker is broken and unlocking is not possible anymore. In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2), log in and execute the command
loginctl unlock-session c2
Afterwards switch back to the running session (Ctrl+Alt+F1),
That never works for me because I am not using an English keyboard layout which yet seems to be the default for the virtual terminal at this stage, so, my password doesn’t match. My temporary work-around here was to deactivate screen locking altogether — yet that must not be a permanent solution. Sometimes I need the locking.
· Most worrisome, though, is the warning that sometimes shows on startup, between GRUB and login, which reads something like
Delayed block allocation failed for inode 2753385 at logical offset 1378 with max blocks 3 with error -5 This should not happen!! Data will be lost
The numbers are never the same, the disk tests fine, and the message does not display every time. It does never display when I start Manjaro using kernel 4.9.66-1 (switching kernels appears to help with the programs-not-opening issue), but with my standard, 4.14.3-1.
To be fair, the programs-not-opening issue I have experienced with USB thumb drive installs of both SwagArch (XFCE) and Antergos (KDE), too. So, it’s more likely an Arch issue, but I do not find anything in their forum. The KDEinit message from above might also point to a Plasma related situation, but I didn’t find anything there, either (and it’s happening on a non-Plasma system, too).
So, should anyone have any idea what might be the cause here, please let me know. I’m desperate.
Thanks, and of course thanks to Manjaro’s developers, too! Apart from those annoying issues, I love Manjaro!