| Summary: | Crash recovery does not preserve RequestedPresence | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Will Thompson <will> |
| Component: | mission-control | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | 5.7 | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
RequestedPresence is transient: IMO, saving it just so we can crash-recover it doesn't make sense. Perhaps crash-recovery could assume that the CurrentPresence is also the RequestedPresence of any recovered connections? -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-mission-control/issues/36. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
I just upgraded MC, and wanted to switch to the new version. So I killed it, and double-clicked someone in Empathy, which I thought would service-activate the new version. (It didn't. I don't know why not.) So then I started it manually, and got a bunch of this: (process:24453): mcd-WARNING **: presence_set_status_cb: Setting presence of gabble/jabber/will_2ethompson_40collabora_2eco_2euk0 failed: cannot set status 'offline' on yourself So yeah, it looks like MC doesn't remember RequestedPresence across crashes: 2011 % mc-tool show gabble/jabber/will_2ethompson_40collabora_2eco_2euk0 ... Automatic: available (2) "" Current: dnd (6) "♙" Requested: offline (1) "" ...