hi i found a bug when i enable profile sync daemon for the first time in cachyos hello
when you enable it you can’t open any other app and can need complete reinstalation if you close hello and didn’t unenable it result in unit -app “the app” service not found like i in this post can’t recreate the bug because if you imediately unenable and after enable it after the first installation it solved and i can’t reprodused it on my second PC
Cant reproduce this on a fresh install.
After install enable PSD and everything works fine.
Your installation might have been corrupted somehow.
I just experienced this problem. As i am an absolute beginner in Linux and completely new to CachyOS/Arch, firstly i had no idea what’s going on. I had to learn that you can start a terminal with strg+alt+F2, as i could not start any application as usually, to be able to do anything. The solution in the end was to stop the profile-sync-daemon: systemctl stop psd.service. psd creates a lot of files to store the profiles of browsers installed on the system and somehow this breaks KDE, It’s important to note that i had 5 browsers installed (testing, using now Vivaldi) each having many bookmarks, start tabs and so on and then enabled psd via CachyOS Welcome (and of course not disabled immediately after that) just to test this too. This may have met the conditions for a failure, you may try to reproduce. Reboot, COS started normally and even launched autostart apps but i could not start any application installed.
I also tried to delete new profile files from Chromium and Google-Chrome (i think this came with chromium) in /run/user/1000 where psd puts the files but that was a stupid idea and didn´t work.
systemctl stop psd.service did work, everything’s fine again. I won´t start psd again before this is fixed. Honestly i don´t know what it actually does, as profiles are stored in the browsers anyway. I shouldn´t enable anything without a clou what for… 
Found in this Reddit Post.
Is this service safe to use nowadays?
Always was.
Not even sure that I understand the opening post.
But I have used Plasma+PSD for .. well, since about the time of Plasma 5-point-something or so and it never broke the desktop, and I find it difficult to understand how it even could unless extremely misused.
Reading a late response to that reddit thread seems to show that users having huge amounts of browsers and not huge amounts of ram were surprised to find that PSD was doing what it was supposed to but, since that meant loading a half dozen or more browser profiles into volatile memory, that meant they had no memory left for desktop services.
In case it is instructive here is also a link to the Arch Wiki page;
It was supposed to work, nah? Anyway such programs just a ??? to me unless I read how they actually work. I mean a realization of such concept of RAM (tmpfs) used for browser profile(s). And I don’t blame those who don’t have 64gb of RAM, but expect it to work. Fortunately I have such amount.
Anyway even with 32gb I had problems with freezes (system doesn’t respond at all) and it was, and is for some who doesn’t know about it — because there’s no service to kill memory-hogging processes or warn you when RAM usage hits around 95-98%, before the system runs out completely. So I did install nohang[https://github.com/hakavlad/nohang\] back in the day.
I have used PSD with 8GB and 16GB (including currently).. but only a maximum of 3 or 4 browsers.
It sounds like these users had less memory and even more browsers.
There are, such as systemd-oomd.
But having OOM usually means something or other should be investigated.
I’m not sure — is it “Always was” or is it “sounds like”? Because how much you’re confident in the abstract but not confident in the exact.
*Sherlock Holmes theme playing*
“Always was” was in response to ‘is it safe’.
Lots of services are safe but can be implemented poorly.
You could install your desktop and then fill TMPFS a hundred other ways. Or configure ZRAM to create an (in-ram) swap 32 times the size of your memory - too much even for the compression to handle.
Being around a total of 3 different linux forums next to the rest of web and news, while personally I have seen PSD used on every major DE across a range of machines for something like a decade, and this thread is the first I have ever heard of any such issue …
So the ‘sounds like’ was based on the information provided by the few posts mentioning this issue combined with the benefit of the doubt that absolutely nothing else was at play - it would seem related to very specific cases - ie low memory while trying to use PSD for 6+ browsers already sounds like bad configuration but we also cant discount other bad configurations.
You may note the longstanding archwiki page already linked and that it is largely devoid of any troubleshooting section or warnings save for the off-by-default overlayfs possibility for privilege escalation. Which also inclines me to think that any PSD ‘problems’ are far from widespread.
Ahh, okay. I don’t want to try this kludgy service after all; to be a 0.001% as you probably think. No, thanks!
