- Package:
- src:systemd
- Source:
- src:systemd
- Submitter:
- e829dce
- Date:
- 2026-02-28 12:45:03 UTC
- Severity:
- normal
- Tags:
Dear Maintainer, It seems like this issue started happening after upgrading to Debian 13.2. I couldn't find a consistent way to reproduce it, but once it happens, I can't start most graphical utilities, Firefox logs me out of pretty much every website, and the system generally becomes unusable until I either log out or restart. I can kind of start Ptyxis (since I use it as my terminal emulator), but it throws this error: Failed to start transient scope unit: Unit ptyxis- spawn-2120119d-e343-4c78-b079-6ff0b9fcb101.scope not found.
It looks like the bug report got filed under a completely wrong package, and I found the problematic package either way, so I'd like to request this bug report closed or marked invalid. Sorry if that caused some trouble for you =)
Ok, but this isn't ptyxis' fault either, since ptyxis is only an app and isn't responsible for launching apps and services. systemd was updated in Debian 13.2 so I'm re-assigning there, but this bug doesn't yet have enough information for us to do much with it. There don't seem to have been any relevant changes in GNOME components themselves for Debian 13.2. https://wiki.debian.org/Gnome/TrixieUpdates Thank you, Jeremy Bícha
I used AI ( / sales rep) intelligence level here :-) I did not knew what was ptyxis one hour ago
There might just be something very wrong with the individual's Debian install or even their hardware. I think we would have noticed if this was a widespread issue, we would have heard about this sooner. Thank you, Jeremy Bícha
Hello there, thanks for reassigning the bug report. Indeed, Ptyxis is not responsible for anything, but it's the only program that could output something searchable, like an error that I've included in the original post. Nautilus stops working as well. I've tried using Chromium (taken from the stable repository), and it also seems to be encountering the same issue, except it actually complains about profiles (forgotten the details, but I can try to replicate it again). About an issue with my hardware... I think that's out of the question - SMART logs look alright to me, there are no errors. Sorry if I'm doing anything wrong right now - this is my first time filing a bug report
Hello there. Turns out the issue was related to `profile-sync-daemon`, AKA `psd`. Removing the package and creating a new Firefox profile fixed it completely - no more failing applications.
Control: reassign -1 profile-sync-daemon 6.50-1
Control: tags -1 + trixie moreinfo
Reassigning this to profile-sync-daemon.
smcv
I can confirm this bug on Debian testing with the unstable firefox, Mozilla upstream firefox, and chromium. After a power crash it is not possible for to reinstanciate psd on all these browser without data loss. It also does not matter if I use a recovered profile (if the recovery worked which most of the time didn't (!) of a complete fresh setup without any config directories existing. I got messages of the type:Feb 28 01:07:32 ash profile-sync-daemon[55291]: Error: Failed to sync /run/user/1000/psd/user-firefox-p8ln6yus.default to /home/user/.config/mozilla/firefox/p8ln6yus.default-back-ovfs during unsync On firefox it does not matter if the profile is in ~/.mozilla or in the new XDG paths. firefox 148.0~build1 (Mozilla) firefox 148.0-1 (Debian) chromium 145.0.7632.109-1 (Debian) profile-sync-daemon 7.00-1 Deinstallation of psd makes the whole system stable again.