This bug was fixed in the package vino - 3.6.1-0ubuntu1
---
vino (3.6.1-0ubuntu1) raring; urgency=low
* New upstream bugfix release (LP: #1070618).
* debian/rules:
- Explicitly build --with-secret
-- Jeremy BichaSun, 04 Nov 2012 08:44:05 -0500
** Changed in: vino (Ubuntu
** Branch linked: lp:ubuntu/raring-proposed/vino
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070618
Title:
Update vino to 3.6.1
To manage notifications about this bug go to:
https://bugs.launchp
If the SRU team doesn't want to add libsecret to vino at this point for
Quantal, then there really isn't any reason to bother with 3.6.1.
I'll upload to raring instead.
** Changed in: vino (Ubuntu Quantal)
Status: Incomplete => Won't Fix
--
You received this bug notification because you
Note that there's at least one crasher bug in libsecret in 12.10 for
which an SRU is in progress, lending credence to the argument that vino
should not add support for it in SRU.
I'm rejecting the uploaded SRU from the queue, pending resolution of
this issue. If you believe the package should be
Because vino was previously not building with libsecret support (for
whatever reason), this amounts to the introduction of a new feature in
the SRU. I think an explicit test case is needed for libsecret if it's
going to be enabled in SRU, as well as some explicit analysis of the
possible sources o
** Branch linked: lp:~ubuntu-desktop/vino/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070618
Title:
Update vino to 3.6.1
To manage notifications about this bug go to:
https://bugs.launchp
