Bug#518862: vino-server needs to conflict with older gnome-session

[Josh Triplett]

On Wed, Apr 22, 2009 at 11:09:04PM +0200, Josselin Mouette wrote:
> Le mercredi 22 avril 2009 à 11:32 -0700, Josh Triplett a écrit :
> > Package: vino
> > Version: 2.24.1-3
> > Severity: normal
> > 
> > I still have this problem with vino 2.24.1-3.  However, I investigated
> > further, and I think I found the true cause of the problem.  The problem
> > *does* relate to session management, but not in the way previously
> > suggested in this bug.  Upgrading to gnome-session 2.26.1-1 from
> > experimental caused this problem to go away.
> 
> No, the problem does not go away with gnome-session 2.26, that is why
> upstream is considering adopting the --sm-disable change. The problem
> is, even if vino-server is not started thanks to AutostartCondition
> (which works perfectly fine in 2.22), it is restarted if it was saved in
> the session. Which explains why solely upgrading vino is not enough, you
> also have to purge it from your session.
> 
> The reason why you don’t have the issue with 2.26 is that your saved
> session was not kept across the upgrade.

Ah, I see.  Thanks for the explanation.

- Josh Triplett