The Linux Thread - The Autist's OS of Choice

[Dread First]

Am I the only person here who enjoys and prefers a manual install? pacstrap does most of the work for you anyway.

It's not that I hate doing a manual install for Arch... it's the fact that there's no comprehensive resource that explicitly outlines both how to do something and why you're doing it anymore, let alone how to get yourself out of a text console and why you need stuff like Mesa. I've bootstrapped FreeBSD to a graphical environment multiple times, but it ain't like the FreeBSD handbook leaves you high and dry.

Ironically, I would argue that pacstrap doing most of the work for me is, in itself, a bad thing because Arch is otherwise consistent and homogeneous enough with mainline Linux distros (re: anything with systemd) such that a true "full manual" install process would allow me to cultivate the skillset necessary to get Ubuntu, Debian, or even Fedora up and running from a minimal netinstall image.

 

[Akerman]

Seems like accountservices got Poettered in the newest update that was shat out yesterday. Whatever they did made it stricter so now you cant edit your user avatar on Plasma because of some permissions hell. Whenever I tried to do it via the GUI in SystemSettings or in the terminal I got this error:

org.freedesktop.Accounts.Error.Failed:
creating temporary icon file failed: Read-only file system

At first I thought my bullshitting around the system had messed up permissions of my folders, but nope. After some A/B testing I concluded it's a systemd issue. Something with the ProtectSystem being set to strict along with an issue with how Plasma passes along the avatar images using tmp, idk. I was only able to fix it by adding the /tmp directory explicitly with sudo systemctl edit accounts-daemon.service :

[Service]
ReadWritePaths=/tmp

 

[Anime Waifu NFT collector]

I installed Linux Mint two days ago, I'm oficially a hacker now.

Spoiler: me rn

 

[Dread First]

Seems like accountservices got Poettered in the newest update that was shat out yesterday. Whatever they did made it stricter so now you cant edit your user avatar on Plasma because of some permissions hell. Whenever I tried to do it via the GUI in SystemSettings or in the terminal I got this error:

org.freedesktop.Accounts.Error.Failed:
creating temporary icon file failed: Read-only file system

At first I thought my bullshitting around the system had messed up permissions of my folders, but nope. After some A/B testing I concluded it's a systemd issue. Something with the ProtectSystem being set to strict along with an issue with how Plasma passes along the avatar images using tmp, idk. I was only able to fix it by adding the /tmp directory explicitly with sudo systemctl edit accounts-daemon.service :

[Service]
ReadWritePaths=/tmp

Isn't this more of a self-inflicted Plasma problem rather than a systemd problem? I would assume it's a systemd issue if you recently updated it and then Plasma borked. From the way you phrased it, it sounds like the Plasma team, yet again, decided to introduce another fucking regression that never existed before... let alone in Plasma 5/4/3 etc

 

[Betonhaus]

Seems like accountservices got Poettered in the newest update that was shat out yesterday. Whatever they did made it stricter so now you cant edit your user avatar on Plasma because of some permissions hell. Whenever I tried to do it via the GUI in SystemSettings or in the terminal I got this error:

org.freedesktop.Accounts.Error.Failed:
creating temporary icon file failed: Read-only file system

At first I thought my bullshitting around the system had messed up permissions of my folders, but nope. After some A/B testing I concluded it's a systemd issue. Something with the ProtectSystem being set to strict along with an issue with how Plasma passes along the avatar images using tmp, idk. I was only able to fix it by adding the /tmp directory explicitly with sudo systemctl edit accounts-daemon.service :

[Service]
ReadWritePaths=/tmp

I might be wrong, but isn’t any app with the org.freedesktop.*.* nomenclature a flatpak?

 

[Akerman]

Isn't this more of a self-inflicted Plasma problem rather than a systemd problem? I would assume it's a systemd issue if you recently updated it and then Plasma borked. From the way you phrased it, it sounds like the Plasma team, yet again, decided to introduce another fucking regression that never existed before... let alone in Plasma 5/4/3 etc

AFAIK Plasma hasn't changed how they do this. It first stages an icon file and calls the AccountsService DBus method which has worked fine until accountsservices updated yesterday. Plasma is only passing a caller-visible icon path to SetIconFile. The failure is in AccountsService’s own open_temporary_icon_file() path after it receives that file because its writable allowlist does not include /tmp.

With ProtectSystem=strict, systemd makes the filesystem hierarchy read-only except explicit writable paths; ReadWritePaths= is the intended allow-list mechanism. The unit therefore needs ReadWritePaths=/tmp, or the new icon import path fails with creating temporary icon file failed: Read-only file system.