Budgie dconf/user recovery needed randomly

Desktop Environments Budgie
1

I think Budgie has a target audience.
During reliability testing I have encountered this vulnerability at login :

Oh no!

Something has gone wrong
A problem has occurred and the system can’t recover.
Please logout and try again

For the time being my shortest workaround is a recovery from a backup copy of
~/.config/dconf/user
I had to create a 2nd administrator account for this maintance.
Fresh installation, random occurance, once experienced with Arco as well.

2

In my brief experiments with Budgie I’ve not had this problem. Given it’s occurred with two distros (albeit both Arch-based) it might be worth opening an issue at https://github.com/BuddiesOfBudgie

3

Thank you @r0ckhopper I started reading the issues arrived at BuddiesOfBudgie and
do not want to elevate my stories to that level.
journalctl -ae --full > crash.txt
will be the log if this happens again.
I gave up using external SSD-s via USB3 for Budgie. I can’t exclude that a write problem to dconf/user caused the trouble. Now I use an internal SSD.
Edit: Should you use ibus and different keyboard layouts a delay may be needed at startup as written among BuddiesOfBudgie cases

[Desktop Entry]
Type=Application
Name=budgie-panel
Description=
Exec=budgie-panel --replace & sleep 3 && ibus-daemon -d
1 Like