Bug 33769 - Crash recovery does not preserve RequestedPresence
Summary: Crash recovery does not preserve RequestedPresence
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: mission-control (show other bugs)
Version: 5.7
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-31 08:59 UTC by Will Thompson
Modified: 2019-12-03 19:35 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Will Thompson 2011-01-31 08:59:25 UTC 
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) ""
   ...
Comment 1 Simon McVittie 2011-04-19 04:26:58 UTC 
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?
Comment 2 GitLab Migration User 2019-12-03 19:35:03 UTC 
-- 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.