[Bug 38986] Merge Call.DRAFT2 into master

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Jul 14 12:51:33 CEST 2011


https://bugs.freedesktop.org/show_bug.cgi?id=38986

--- Comment #5 from Will Thompson <will.thompson at collabora.co.uk> 2011-07-14 03:51:33 PDT ---
(In reply to comment #2)
> We will still need to upgrade things in lockstep though, and we still need to
> have a mechanism (probably in MC) for:
> * "Hey user: The version of [channel.type.call, channel.type.text] supported by
> the newly-installed [empathy-call, empathy-chat] is newer than that supported
> by the currently-running [gabble, salut, ...]. Click this button to restart
> these services. This will cause you to be disconnected from the network
> briefly"
> * "Hey empathy-chat. A new version of you has appeared in my list of
> activatible services. It supports a newer version of channel.interface.messages
> (required for chatting with the following accounts: [...]). Can you warn your
> user that you need to restart, and then do so please?

(In reply to comment #3)
> For the updating, I would just do a big "Restart everything" thing instead of
> trying to be smart and do it fine grained.

I think the only viable way is logging out and in of your desktop session,
really. We could add a way to have (say) MC tell all your CMs and clients to
die/reload themselves … and some clients like Gnome Shell can restart itself
without losing too much state, but the user might be a bit annoyed if they
upgrade Telepathy and AbiWord (say) commits seppuku in sympathy.

So I don't think it's entirely obvious how to solve this—but note that it's not
entirely a new problem, as we already have issues with MC not noticing new CMs
(bug 30210 and bug 24511). Definitely separate bug territory, and maybe should
only strike end-users on distro version upgrades, which we can assume will
involve logging out and in (or maybe a reboot)?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the telepathy-bugs mailing list