The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: gnome-keyring (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: gnome-keyring (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to multiarch
@caf4926: this should be fixed in trusty (and mint 17).
Please check if these packages installed.
apt-cache policy p11-kit-modules:i386
apt-cache policy libp11-kit-gnome-keyring:i386
If not, install them.
sudo apt-get install p11-kit-modules:i386 libp11-kit-gnome-keyring:i386
--
You received
I'm guessing this is related from Mint 17.3
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so:
/usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object
file: No such file or directory
p11-kit: couldn't load module:
Is it really still important to be able to upgrade from 12.04 to 12.10?
12.04 is supported for 3 more years, 12.10 for something like a month.
Once 14.04 is out, you will be able to upgrade from 12.04 directly.
--
You received this bug notification because you are a member of Desktop
Packages,
** Branch linked: lp:ubuntu/trusty-proposed/wine1.6
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to multiarch
Status in
I ran 'wine notepad' and saw the following:
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-
keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-
pkcs11.so: cannot open shared object file: No such file or directory
I installed gnome-keyring and
@mterry: thanks for the fixes and the upload.
I can update my patch for precise, but as it stands, it also converts gcr,
which was split out of gnome-keyring into its own package in quantal, to
multiarch.
Before we can convert gnome-keyring (including gcr) to multiarch in precise, we
would
This bug was fixed in the package gnome-keyring - 3.6.1-0ubuntu1.1
---
gnome-keyring (3.6.1-0ubuntu1.1) quantal; urgency=low
* Backport the following changes from gnome-keyring in Raring:
- Move the PKCS#11 module into a separate package. (LP: #1094319)
- Convert
Hello Riku, or anyone else affected,
Accepted gnome-keyring into quantal-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/gnome-
keyring/3.6.1-0ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
OK, quick update on status for Quantal and Precise. The Quantal patch
was never uploaded to the archive. The Precise patch was uploaded by
xnox, but was rejected because of the ${binary:Version} issue below.
I've just uploaded a modified patch from comment 75 to Quantal only.
I'd like to get
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-keyring (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
@Adam Conrad (adconrad)
Updated SRU uploaded into precise-proposed queue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to multiarch
Marking 'new' in Quantal and Precise.
** Changed in: gnome-keyring (Ubuntu Precise)
Status: In Progress = New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
** Changed in: gnome-keyring (Ubuntu Quantal)
Status: Won't Fix = In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring
This is Rodney's Quantal patch from comment #41 with the following changes:
The gnome-keyring package depends on libp11-kit-gnome-keyring instead of
recommends.
The libp11-kit-gnome-keyring package now breaks and replaces gnome-keying (
${binary:Version}).
I believe this needs to be fixed in
This patch for Precise includes the same changes as in the Quantal patch
above, and includes the multi-arch changes in the gcr package from Saucy
( see LP: #859600).
** Patch added: gnome-keyring-gcr-multiarch-precise.debdiff
I will be able to work on this and gcr again in a couple of days' time.
Hopefully early next week I'll attach debdiffs.
In the meantime, you are welcome to test gnome-keyring from my PPA.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
@graham: I think the usual way to do this is that you crate a debdiff to
the current version in precise. Attach it to this bugreport and
subscribe ubuntu-sponsors when done. Name/Version of the patch should be
something like that:
gnome-keyring_3.2.2-2ubuntu4.3.precise.debdiff
** Patch removed:
I've updated the description with more specific instructions on how to
test this SRU.
As for Depends vs Recommends from debian policy manual:
The Depends field should be used if the depended-on package is required for the
depending package to provide a significant amount of functionality.
The
For the gnome-keyring package to be considered multi-arch in Precise, surely
libgck and libgcr need to be multi-arch as well?
Then we can close LP: #998715 for Precise in this SRU.
My other concern is what will happen when someone picks up
libp11-kit-gnome-keyring in Precise and then upgrades
So, the solution imagined here is not to fix the two duplicates of this
bug, but to introduce a new feature, namely make every library in gnome-
keyring multiarch? What's to be gained by this?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
OK. Everyone, just relax. First of all, this bug is not for the p11kit
issue. That bug is #1094319 as clearly mentioned in the changelog entry.
This bug is specifically about enabling Multi-Arch for the gnome-keyring
source package, so that some of its binaries may be co-installable as
needed.
I've built another gnome-keyring package for Precise in my PPA that I
hope fixes all three issues (multi-arch gnome-keyring, multi-arch gcr
and split libp11-kit-gnome-keyring).
The test case (on an x86_64 system) would be something like:
$ wine notepad
You should see the error message:
p11-kit:
To be clear the error message isn't the annoyance part, it's that it's a
real error that does prevent some apps from running (and there's no way
to make them run on 64-bit at all in current precise).
--
You received this bug notification because you are a member of Desktop
Packages, which is
@eraserix: gnome-keyring is marked Multi-Arch: foreign so that, for
example, an amd64 gnome-keyring can satisfy an i386 package's dependency
on it.
The version numbers in Breaks and Replaces look wrong to me too.
As jhansonxi wrote in comment 48, libp11-kit-gnome-keyring:i386 won't be
So, my take ;). This patch just splits the pkcs11 library away from
gnome-keyring binary package and leaves the rest of the packages alone.
I still don't see the use case for doing more, the warning when wine is
started will be gone with this patch. And as far as I can tell, libgcr
is still not
I also had a go at this today. :)
I built a gnome-keyring package for Precise in my PPA:
https://launchpad.net/~ginggs/+archive/sru
It is adam-stokes' last attempt plus the following changes:
- Change gnome-keyring's Recommends on libp11-kit-gnome-keyring
to Depends.
- Change
@eraserix: as for how is the new libp11-kit-gnome-keyring supposed to find it's
way
to the affected users?
Both wine and cups got updates in Raring to Recommends and Depends the
new libp11-kit-gnome-keyring respectively:
wine1.4 (1.4.1-0ubuntu5) raring; urgency=low
* Add new
Yes, I've been holding back on a Wine SRU because I wanted it to
integrate this fix.
Similarly, I will also want to backport wine1.6 to precise when it releases
within a few weeks, and it would be very nice to have this done by then.
--
You received this bug notification because you are a
** Description changed:
[Impact]
Several applications are relying on this package as seen in comments 5 and 6.
[Test case]
- Attempt to install both i386/amd64 versions and preferably verify if the
reported applications in this bug are able to run successfully
+ Attempt to install both
Why change pam/gnome-keyring to mutliarch if it would be enough to just
split of the pkcs11 package and make it multiarch?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
@eraserix have you looked at the diff? That's exactly what is done in
13.04, and what the diff is meant to backport to the older releases..
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
Yes, I did. But I don't see why gnome-keyring is marked as Multi-Arch:
foreign and libpam-gnome-keyring is converted to Mutli-Arch: same. As
I see it, it is sufficient to make 'libp11-kit-gnome-keyring' as
Multi-Arch: same and be done with it. To resolve the warning from wine
you would have to
Looks like sid has quite a bit of changes to gnome-keyring compared with
what's in precise, but multiarch is not one of them. However, the wine
version in sid does not seem to suffer this problem with the library.
'wine notepad' only gives me an error in precise, but not in sid. sid
has wine
Please resuscrbibe the sponsoring team once fixed. Thanks :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to multiarch
Status in
Looks odd, this is gnome-keyring 3.2.2, but libp11-kit-gnome-keyring has in the
d/control:
Breaks: gnome-keyring ( 3.6.2-0ubuntu2~)
Replaces: gnome-keyring ( 3.6.2-0ubuntu2~)
This two should contain the version of THIS package, e.g.
3.2.2-2ubuntu4.2.
--
You received this bug notification
And for coinstalling x86_64 and i386 variants, see below. I've added
proposed as suggested in https://wiki.ubuntu.com/Testing/EnableProposed.
# sudo apt-get install gnome-keyring:i386/precise-proposed
Reading package lists... Done
Building dependency tree
Reading state information... Done
Removed from precise-proposed due to the above regression. Please fix
and reupload with a bumped version number.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: gnome-keyring (Ubuntu Precise)
Status: Fix Committed = In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert
Hello Riku, or anyone else affected,
Accepted gnome-keyring into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/gnome-
keyring/3.2.2-2ubuntu4.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Branch linked: lp:ubuntu/precise-proposed/gnome-keyring
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to multiarch
Status in
At this point I think we can say that a quantal SRU is out of scope now.
Precise has a longer life-time, so keeping that one open.
** Changed in: gnome-keyring (Ubuntu Quantal)
Status: In Progress = Won't Fix
--
You received this bug notification because you are a member of Desktop
@Martin, Quantal is still supported for almost a full 12 months more. Is
it really out of scope to push SRUs to it after only 6 months in? If
this were Raring, and there were only a couple months left of support,
then I would agree it might be out of scope to push such a change. But
given the work
** Changed in: gnome-keyring (Ubuntu Quantal)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring
You wouldn't be able to install gnome-keyring:i386 on x86_64 with these
changes in raring either even, without replacing a very large portion of
the system with the 32-bit packages. Nor do I see any reason why one
would ever want to, either. There's no reason do that.
--
You received this bug
I'm unsure if an updated package has been released for Ubuntu 12.04
(Precise Pangolin) yet but the currently available version of gnome-
keyring:i386 is not installable due to libgcr-3-common not being
multiarch (bug #998715).
--
You received this bug notification because you are a member of
Thanks jhansonxi,
I'll see about getting libgcr multiarch this week.
Adam
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to
Should be fix in precise debdiff now
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to multiarch
Status in “gnome-keyring” package
** Patch added: gnome-keyring_3.6.0-0ubuntu1.1.raring.debdiff
https://bugs.launchpad.net/ubuntu/precise/+source/gnome-keyring/+bug/859600/+attachment/3631032/+files/gnome-keyring_3.6.0-0ubuntu1.1.raring.debdiff
--
You received this bug notification because you are a member of Desktop
** Patch removed: gnome-keyring_3.2.2-2ubuntu4.1.precise.debdiff
https://bugs.launchpad.net/ubuntu/precise/+source/gnome-keyring/+bug/859600/+attachment/3618267/+files/gnome-keyring_3.2.2-2ubuntu4.1.precise.debdiff
** Patch removed: gnome-keyring_3.6.0-0ubuntu1.1.raring.debdiff
** Patch added: gnome-keyring_3.6.0-0ubuntu1.1.quantal.debdiff
https://bugs.launchpad.net/ubuntu/precise/+source/gnome-keyring/+bug/859600/+attachment/3631021/+files/gnome-keyring_3.6.0-0ubuntu1.1.quantal.debdiff
--
You received this bug notification because you are a member of Desktop
Why are you making debdiffs against an older gnome-keyring package, that
are incompatible with the changes already in raring?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
The quantal debdiff you posted is against an older version as well, as
is the precise version. Also, if the proposed debdiffs were pushed out
as updates on those platforms, it would break upgrades to the newer
Ubuntu versions, as the changes are incompatible.
--
You received this bug
My bad, was on autopilot for a moment. The other's still apply I
believe.
Thanks
Adam
** Patch removed: gnome-keyring_3.6.0-0ubuntu1.1.raring.debdiff
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+attachment/3631032/+files/gnome-keyring_3.6.0-0ubuntu1.1.raring.debdiff
Here's a debdiff for Quantal with the same changes that are in Raring
already.
** Patch added: Quantal multiarch backport
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+attachment/3631352/+files/kerying-quantal-multiarch.debdiff
--
You received this bug notification
** Patch removed: gnome-keyring_3.2.2-2ubuntu4.1.precise.debdiff
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+attachment/3631020/+files/gnome-keyring_3.2.2-2ubuntu4.1.precise.debdiff
** Patch removed: gnome-keyring_3.6.0-0ubuntu1.1.quantal.debdiff
Hopefully these dont suck :)
Thanks!
Adam
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to multiarch
Status in “gnome-keyring”
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/08/2013 11:02 AM, Rodney Dawes wrote:
The quantal debdiff you posted is against an older version as well,
as is the precise version. Also, if the proposed debdiffs were
pushed out as updates on those platforms, it would break upgrades
to the
** Patch added: gnome-keyring_3.6.0-0ubuntu1.1.quantal.debdiff
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+attachment/3631380/+files/gnome-keyring_3.6.0-0ubuntu1.1.quantal.debdiff
--
You received this bug notification because you are a member of Desktop
Packages,
** Patch removed: gnome-keyring_3.6.0-0ubuntu1.1.quantal.debdiff
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+attachment/3631380/+files/gnome-keyring_3.6.0-0ubuntu1.1.quantal.debdiff
--
You received this bug notification because you are a member of Desktop
Packages,
Looks like you are pulling the gnome-keyring from the release pocket,
and not from -proposed, as should be. So you now just applied my changes
to the release packages, rather than the updated versions that were
released on Quantal/Precise. See the Quantal backport patch I attached
for the
** Patch removed: gnome-keyring_3.2.2-2ubuntu4.1.precise.debdiff
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+attachment/3631370/+files/gnome-keyring_3.2.2-2ubuntu4.1.precise.debdiff
--
You received this bug notification because you are a member of Desktop
Packages,
** Patch added: gnome-keyring_3.2.2-2ubuntu4.2.precise.debdiff
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+attachment/3631426/+files/gnome-keyring_3.2.2-2ubuntu4.2.precise.debdiff
--
You received this bug notification because you are a member of Desktop
Packages,
Thanks for the patch, I have two comments about it though:
- d/control is autogenerated, please modify d/control.in instead;
- shouldn't usr/bin be removed from gnome-keyring.install now that you moved
it to -bin package?
--
You received this bug notification because you are a member of
- d/control is autogenerated, please modify d/control.in instead;
I only altered control.in, however, I believe d/control was auto-updated
during the source package build.
- shouldn't usr/bin be removed from gnome-keyring.install now that
you moved it to -bin package?
Nice catch Ill fix that
** Patch added: gnome-keyring_3.2.2-2ubuntu4.1.precise.debdiff
https://bugs.launchpad.net/ubuntu/precise/+source/gnome-keyring/+bug/859600/+attachment/3618267/+files/gnome-keyring_3.2.2-2ubuntu4.1.precise.debdiff
--
You received this bug notification because you are a member of Desktop
I apologize for the delay, all debdiffs are uploaded and proper teams
subscribed. I'll check back on its progress next week and push harder
for review if not done by next Wednesday.
Thanks
Adam
--
You received this bug notification because you are a member of Desktop
Packages, which is
s/uploaded/attached to bug/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to multiarch
Status in “gnome-keyring” package in Ubuntu:
please fix for ubuntu 12.10 also, i have same bug for 1.5.27 wine
versions too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to
What about precise (said to be LTS)?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to multiarch
Status in “gnome-keyring” package
Is this going to be fixed for quantal too?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to multiarch
Status in “gnome-keyring”
** Branch linked: lp:ubuntu/wine1.4
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to multiarch
Status in “gnome-keyring” package in
64-bit Wine no longer throws an error message every time it runs with
new libp11-kit-gnome-keyring:i386 package installed. Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
** Branch linked: lp:ubuntu/raring-proposed/gnome-keyring
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to multiarch
Status in
This bug was fixed in the package gnome-keyring - 3.6.2-0ubuntu2
---
gnome-keyring (3.6.2-0ubuntu2) raring; urgency=low
* debian/control:
- Move the PKCS#11 module into a separate package. (LP: #1094319)
- Convert to use multi-arch. (LP: #859600)
*
Andreas, that seems like it should be a separate patch, and something
that should go upstream in GNOME (and possibly is already fixed there),
while this multiarch patch currently only affects the packaging.
--
You received this bug notification because you are a member of Desktop
Packages, which
Please be sure to doublecheck compatibilty with p11-kit 0.14 which
requires a .module extension for PKCS#11 autoloading while you are
making large changes to this package.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in
This is a better patch to add multi-arch support for gnome-keyring. It
moves the p11-kit module to a new package, moves the pam module to
multi-arch, and correctly marks the gnome-keyring package as multi-arch
foreign, as it includes the main binary, and data files.
** Patch added: Better
I don't think the two proposed debdiffs here are correct for
implementing multi-arch for gnome-keyring. While the plug-ins for gnome-
keyring itself, and the pam module, could be built as multi-arch, it
isn't necessary to do so. In fact, building the gnome-keyring plug-ins
(currently in
Hi, for me the dirty workaround was to download the
gnome-keyring_3.2.2-2ubuntu4_i386.deb
from https://launchpad.net/ubuntu/precise/i386/gnome-keyring, and extract just
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so and drop it into the
right place.
Yours, Steffen
--
You received this
Didn't work for me as Spotify still isn't able to validate server certificate:
err:ole:marshal_object couldn't get IPSFactory buffer for interface
{0131---c000-0046}
err:ole:marshal_object couldn't get IPSFactory buffer for interface
{0122---c000-0046}
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-keyring (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-keyring (Ubuntu Quantal)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
Your diff for raring doesn't appear to add gnome-keyring-bin as a
dependency fo gnome-keyring. I'd add this myself, but there may be a
better way to go about this, and you would need to make the same change
for precise and quantal as well.
Unsubscribing ubuntu-sponsors for now, please
** Also affects: gnome-keyring (Ubuntu Raring)
Importance: High
Assignee: Adam Stokes (adam-stokes)
Status: In Progress
** Also affects: gnome-keyring (Ubuntu Quantal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
** Changed in: gnome-keyring (Ubuntu)
Milestone: quantal-updates = None
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to
** Patch added: gnome-keyring_3.6.0-0ubuntu1.1.raring.debdiff
https://bugs.launchpad.net/ubuntu/precise/+source/gnome-keyring/+bug/859600/+attachment/3428276/+files/gnome-keyring_3.6.0-0ubuntu1.1.raring.debdiff
--
You received this bug notification because you are a member of Desktop
Packaging changes from precise 3.2 to quantal/raring 3.6.0 will take me
some more time to get sorted out for mult-arch.
** Changed in: gnome-keyring (Ubuntu Precise)
Milestone: ubuntu-12.04.2 = precise-updates
--
You received this bug notification because you are a member of Desktop
svn also affected:
karp@karp:~/tmp/prj$ svn up
p11-kit: couldn't load module:
/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so:
/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared
object file: No such file or directory
after upgrade from 11.10 to 12.04
--
You
Thanks I'm going to do a precise diff today so sponsors team can look at
them both.
Adam
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to
** Patch removed: gnome-keyring_3.6.0-0ubuntu1.1.quantal.debdiff
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+attachment/3399536/+files/gnome-keyring_3.6.0-0ubuntu1.1.quantal.debdiff
--
You received this bug notification because you are a member of Desktop
Packages,
** Patch added: gnome-keyring_3.6.0-0ubuntu1.1.quantal.debdiff
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+attachment/3404478/+files/gnome-keyring_3.6.0-0ubuntu1.1.quantal.debdiff
--
You received this bug notification because you are a member of Desktop
Packages,
** Bug watch added: Debian Bug tracker #686843
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686843
** Also affects: gnome-keyring (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686843
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Changed in: gnome-keyring (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to multiarch
** Patch added: gnome-keyring_3.6.0-0ubuntu1.1.quantal.debdiff
https://bugs.launchpad.net/ubuntu/precise/+source/gnome-keyring/+bug/859600/+attachment/3399536/+files/gnome-keyring_3.6.0-0ubuntu1.1.quantal.debdiff
--
You received this bug notification because you are a member of Desktop
rdeps testing
gksu_2.0.2-6ubuntu2-amd64-20121015-1720:Status: successful
gnome-python-desktop_2.32.0+dfsg-2ubuntu1-amd64-20121015-1724:Status: successful
gnome-session_3.6.0-0ubuntu1-amd64-20121015-1729:Status: successful
gvfs_1.14.0-0ubuntu6-amd64-20121015-1733:Status: successful
Is this still in progress? Is it deferred to after Quantal release?
(Quantal needs it too I believe)
I've got some Wine apps in the wild that are breaking cause of it (see
linked duplicate bugs), plus the aforementioned apps in this report.
--
You received this bug notification because you are
This is on my radar to do but will probably make it in Quantal updates
at a later date. I should have some free cycles next week to look more
into this issue.
Thank you for your patience
Adam
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
1 - 100 of 112 matches
Mail list logo
