https://bugs.kde.org/show_bug.cgi?id=521008
Serhii Hatsan <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from Serhii Hatsan <[email protected]> --- (In reply to zivirkari from comment #6) > On my end, it seems like /var/lib/plasmalogin/wallpaper is owned by > root:root somehow. #chown plasmalogin:plasmalogin > /var/lib/plasmalogin/wallpapers/ merrily fixes it, thanks for the tip! > > no idea whether it makes sense to set confirmed status, while we have > several confirmations here already this could either be an issue with Plasma > itself or the packaging by Arch, in the latter case the issue should be > reported to them, it would be helpful to know whether anyone is seeing this > permissions issue on non-arch-based systems as well Also observed this behavior (/var/lib/plasmalogin/wallpaper was owned by root:root) on Gentoo. Seems that prior to some change in the code, this folder was saved with root access but now it should be with plasmalogin metauser access, but it newer was able to fix it on its own. It general there should've been some kind of warning message at least in console that some folder failed to write, but I have never seen it. After quick glance at commit history - it might be caused because of this commit: 7b4a086c71779ebf4df80a2f681928cfeba3bf87. There was a change to use dedicated plasmalogin user as a security concern, which assumes that all files in /var/lib/plasmalogin should be accessible only with plasmalogin user. But before that commit - only /var/lib/plasmalogin/.config was forced to have plasmalogin:plasmalogin access rights via chownPath wrapper. >From my quick glance (correct me if I'm wrong) - /var/lib/plasmalogin/wallpapers prior to this commit was always created with root access and not with plasmalogin. Thus, after commit change - some installations (especially bleeding edge testers) failed to properly update wallpapers through the settings kcm. -- You are receiving this mail because: You are watching all bug changes.
