Could not save user profile image after fresh install of garuda

Hey community,

I have been using garuda for over half a year now and suddenly due to some misconfiguration or something (i'm yet not sure what caused it), my installation got messed up and wouldn't boot.

I decided to go for a fresh install and using a bootable USB drive, i installed everything.

Following is some information that i have so far -

  • Most of my stuff is working
  • Terminal works awesome
  • I can install stuff from the aur
  • I can use octopi well
  • I am signed in as the correct user.

Now the PROBLEM ---

I am not able to change the profile image to anything else. For now it shows a simple user icon (default) and in the user settings the "S" for the image (referring to the username "syslog"). Whatever I try to do, it says the following error ---

"There was an error while saving changes"

For the time being, I am not using any custom images, just the default ones that come with the installation.

Thanks for the help in advance

*and sorry for joining the community late, just a college student - pardon me :smiley: *.

Hi there, welcome.
Please always remember to include the output of your garuda-inxi, as requested in the new topic template.
Anyway, I assume you're on KDE, because there there is a know bug, already fixed in an update which should be released shortly (it was planned for today).
Actually it is already available, but in the Arch "testing" repository, so it should "arrive" soon.


Hey @filo,

Thanks for the quick reply. I'll remember to add the inxi output to my further queries for sure.

Should I run a system update right now or later tomorrow ? If it was planned for today, I might as well wait for it to "arrive" and try again.

Also, my current KDE version is 5.23.5

No, at the moment it would not be downloaded/installed.
If you want, you can check here:
When 5.24 will be in Extra instead of Testing, you will be able to download the version fixing that bug.
Of course an update in a rolling release distro is always an important thing to do.
Do not necessarily wait for that before the next update.
I don't know, being 5.24 a big, massive and Long Term Support KDE release, maybe it will stay there for a few days?

1 Like

Thanks for the reference. Hope the update comes out quick.

Just for future reference, formatting and reinstalling every six months is a bad habit carried over from Windows. The whole point of a rolling distro is your install can last many years. Best not to reinstall any time you hit a minor speed bump along the way, as this teaches you nothing about troubleshooting or maintaining your system properly.

Just FYI.


A short update on this, although, once again, this seems to me really minor stuff, but I rechecked after the release of KDE 5.24, for completeness.
The issue persists there. As can be read on the KDE bug tracker entry 449385 – User changes can't be saved with accountsservice-22.04.62, it is fixed as far as KDE is concerned. What we are seeing is a different, upstream issue.
Unable to set profile picture via gnome control center, because /tmp is marked private in accountsservice service file (#98) · Issues · accountsservice / accountsservice
Bugreport on GNOME bugtracker: User profile picture can't be set to an own picture file, because /tmp is not readable by accountsservices (#1629) · Issues · GNOME / Settings · GitLab


I believe there is a workaround to this issue. I think you can overwrite the default image with a picture you desire (using the preexisting name). I could be wrong, but I'm pretty sure there's more than one way to skin a cat.


Said and done.
My simple way of skinning the cat is: copy your avatar (as .png, I think) into a file named ~/.face
Done, works :slight_smile:
Edit / bonus tip:
To use the picture also for sddm (but this was not part of the bug), you can check the
directory (default is /usr/share/sddm/faces) in /etc/sddm.conf and copy there the avatar file as <username>.face.icon (or of course you can create e.g. /etc/sddm.conf.d/avatar.conf with a different folder)


Agreed. That is actually a bad habit carried over by a lot many people. I don't prefer running a fresh install unless necessary.

The reason I had to do it was that during an update, my Linux kernel was busted and the OS wasn't able to boot stating that the kernel was not found. Being pretty new to this problem and having urgency, I went ahead with a fresh install (while also investigating the issue).

For a pretty weird reason, my whole workstation lives on a single partition of 48 GB which is why the update effed up. Lack of disk space.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.