Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#73980 - [accountsservice] Unable to set profile picture because /tmp is marked as private
Attached to Project:
Arch Linux
Opened by Nova Leary (NovaViper) - Sunday, 27 February 2022, 21:15 GMT
Last edited by Jan Alexander Steffens (heftig) - Tuesday, 01 March 2022, 23:53 GMT
Opened by Nova Leary (NovaViper) - Sunday, 27 February 2022, 21:15 GMT
Last edited by Jan Alexander Steffens (heftig) - Tuesday, 01 March 2022, 23:53 GMT
|
DetailsDescription:
Can no longer change the profile picture in KDE Plasma 5.24, resulting the error "Something went wrong while saving changes". Additional info: * package version(s): v22.04.62 - v22.07.5 * config and/or log files etc. Error reported in terminal: org.kde.kcm_users: "org.freedesktop.Accounts.Error.Failed" "file '/tmp/systemsettings.fbhsTy' is not a regular file" file:///usr/lib/qt/qml/org/kde/kirigami.2/Avatar.qml:262:9: QML Image: Cannot open: file:///home/novaviper/.face * link to upstream bug report, if any: https://gitlab.freedesktop.org/accountsservice/accountsservice/-/issues/98 Steps to reproduce: - Install offending versions onto system - Open user profile settings in KDE - Set a picture - Tell it the save, and error results |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Tuesday, 01 March 2022, 23:53 GMT
Reason for closing: Fixed
Additional comments about closing: accountsservice 22.08.8-1
Tuesday, 01 March 2022, 23:53 GMT
Reason for closing: Fixed
Additional comments about closing: accountsservice 22.08.8-1
Comment by Jan Alexander Steffens (heftig) -
Tuesday, 01 March 2022, 22:32 GMT
Should be fixed in 22.08.8-1?
Comment by Nova Leary (NovaViper) -
Tuesday, 01 March 2022, 23:50 GMT
Can confirm v22.08.8-1 fixes the bug, thanks!