It's possible that it's the same bug as bug #1302416 , but I don't know that there's specific evidence supporting that.
- Most (though not all) of the users reporting that bug experience it in conjunction with Chrome Remote Desktop, which I don't use and don't have installed as far as I know.
- Most of the users reporting that bug seem to indicate that it behaves this way consistently -- or at least consistently after an upgrade. The bug I experienced was novel to my system, and it had been over a week since deja-dup was upgraded. The last update of packages generally was many hours before this problem showed up.
- This bug appeared in conjunction with what I think is a separate underlying error -- something interfering with applications' ability to create the /run/user/1000/dconf/user file. A lot of "critical" errors were/are being logged in various terminals/logs about it during this session. However, deja-dup appears to be the only application whose handling of the problem generated thousands of failure messages and was accompanied by drastic consumption of system resources and resulting instability.
It's possible that it's the same bug as bug #1302416 , but I don't know that there's specific evidence supporting that.
- Most (though not all) of the users reporting that bug experience it in conjunction with Chrome Remote Desktop, which I don't use and don't have installed as far as I know.
- Most of the users reporting that bug seem to indicate that it behaves this way consistently -- or at least consistently after an upgrade. The bug I experienced was novel to my system, and it had been over a week since deja-dup was upgraded. The last update of packages generally was many hours before this problem showed up.
- This bug appeared in conjunction with what I think is a separate underlying error -- something interfering with applications' ability to create the /run/user/ 1000/dconf/ user file. A lot of "critical" errors were/are being logged in various terminals/logs about it during this session. However, deja-dup appears to be the only application whose handling of the problem generated thousands of failure messages and was accompanied by drastic consumption of system resources and resulting instability.