I found an old Nexus 5x and installed the linageos-fork from the e.foundation on it.
All is working fine except some WiFi-Access Points where the Phone connects itself to disconnect itself right afterwards and tries the same game again.
Long story short, thanks to reddit.com, the answer is to enable Bluetooth.
With Bluetooth turned on, the wifi connection is table.
After doing an upgrade of my Antergos VM with an IceWM, I've lost all relevant entries in the menu.
"No problem" I thought, "i just need to recreate them" and did it with >>mmaker -f icewm<< but nothing was generated. Actually, the file >>~/.icewm/menu<< was missing totally.
After running things again and having an eye on the output, the mmaker was telling me:
mmaker no suitable terminal emulator found
After searching around, the quickest solution was to install >>xterm<< and rerun the menu creation again to solve this issue.
Give is, that you get an error message while booting up your system from "systemd-tmpfiles-setup.service" with the description "Failed to start Create Volatile Files and Directories.".
By using systemctl with
systemctl status systemd-tmpfiles-setup.service, you get the same description.
A quick look into the archlinux wiki offers you the solution named enable acl in your file system.
If you are running zfs as your root, you have to execute
zfs set acltype=posixacl #your_pool_name. To validate if it is working, execute
zfs get acltype before and after the set.
If you want to know more, you can read the following links:
Once in a day, my network printer stopped working. All he was printing on a paper was:
A quick look to the cups service turned out the following message.
systemctl status org.cups.cupsd.service
error: Failed to create /var/spool/cups/tmp/.hplip
If you run into this problem, it is an easy one.
Do a "df -h | grep /var" and with a high chance, you will see a "100%" or something close by right before "/var". So whats the problem? Your "/var" is running out of disk space. Use a tool like "ncdu" to check what can be removed. Printing should work right after fighting the disk space issue.