Closed simonbcn closed 3 years ago
If you're syncing multiple profiles, and something goes wrong that is to be expected. Look at the date-time stamps across the profiles. Seems consistent to me.
Something I don't understand.
Have the Chromium
/Vivaldi
recovery dirs same name as those of Google Chrome
? Or is it a bug in psd
that it is printing the same recovery dirs for all Chromium-based browsers?
browser/psname: chromium/chromium
.....
recovery dirs: 3 <- delete with the c option
dir path/size: /home/juan/.config/google-chrome-backup-crashrecovery-20201114_233820 (513M)
dir path/size: /home/juan/.config/google-chrome-backup-crashrecovery-20201114_233617 (513M)
dir path/size: /home/juan/.config/google-chrome-backup-crashrecovery-20201114_233455 (513M)
.......
.......
.......
browser/psname: vivaldi/vivaldi-bin
.......
recovery dirs: 3 <- delete with the c option
dir path/size: /home/juan/.config/google-chrome-backup-crashrecovery-20201114_233820 (513M)
dir path/size: /home/juan/.config/google-chrome-backup-crashrecovery-20201114_233617 (513M)
dir path/size: /home/juan/.config/google-chrome-backup-crashrecovery-20201114_233455 (513M)
That is unexpected. I will need to play with it.
Today I see this:
$ psd p
Profile-sync-daemon v6.42
systemd service: active
resync-timer: active
sync on sleep: enabled
use overlayfs: enabled
Psd will manage the following per /home/juan/.config/psd/.psd.conf:
browser/psname: chromium/chromium
owner/group id: juan/1000
sync target: /home/juan/.config/chromium
tmpfs dir: /run/user/1000/juan-chromium
profile size: 1,8G
overlayfs size: 0
recovery dirs: 3 <- delete with the c option
dir path/size: /home/juan/.config/vivaldi-backup-crashrecovery-20201118_093546 (189M)
dir path/size: /home/juan/.config/google-chrome-backup-crashrecovery-20201118_093754 (377M)
dir path/size: /home/juan/.config/google-chrome-backup-crashrecovery-20201117_131055 (377M)
browser/psname: firefox/firefox
.....
browser/psname: google-chrome/chrome
owner/group id: juan/1000
sync target: /home/juan/.config/google-chrome
tmpfs dir: /run/user/1000/juan-google-chrome
profile size: 396M
overlayfs size: 0
recovery dirs: 3 <- delete with the c option
dir path/size: /home/juan/.config/vivaldi-backup-crashrecovery-20201118_093546 (189M)
dir path/size: /home/juan/.config/google-chrome-backup-crashrecovery-20201118_093754 (377M)
dir path/size: /home/juan/.config/google-chrome-backup-crashrecovery-20201117_131055 (377M)
browser/psname: vivaldi/vivaldi-bin
owner/group id: juan/1000
sync target: /home/juan/.config/vivaldi
tmpfs dir: /run/user/1000/juan-vivaldi
profile size: 205M
overlayfs size: 31M
recovery dirs: 3 <- delete with the c option
dir path/size: /home/juan/.config/vivaldi-backup-crashrecovery-20201118_093546 (189M)
dir path/size: /home/juan/.config/google-chrome-backup-crashrecovery-20201118_093754 (377M)
dir path/size: /home/juan/.config/google-chrome-backup-crashrecovery-20201117_131055 (377M)
Do you mind trying the latest release and verifying that the issue still exists?
I no longer use it.
psd
shows mixed recovery-dirs betweenchrome
/chromium
/vivaldi
: