[Bug 859600] Re: Please convert gnome-keyring to multiarch
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 Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/859600 Title: Please convert gnome-keyring to multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 859600] Re: Please convert gnome-keyring to multiarch
@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: "gnome-keyring_3.2.2-2ubuntu4.3.precise.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+attachment/3712483/+files/gnome-keyring_3.2.2-2ubuntu4.3.precise.debdiff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/859600 Title: Please convert gnome-keyring to multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 859600] Re: Please convert gnome-keyring to multiarch
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 Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/859600 Title: Please convert gnome-keyring to multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 859600] Re: Please convert gnome-keyring to multiarch
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 Recommends field should list packages that would be found together with this one in all but unusual installations. I'm kind of inclined to stay with recommends. I can still store passwords in the keyring without the pkcs11 library, no? @graham: Thanks for the info about how the new multiarched package finds its way to the users. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/859600 Title: Please convert gnome-keyring to multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 859600] Re: Please convert gnome-keyring to multiarch
** 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 i386/amd64 versions of libp11-kit-gnome-keyring and preferably verify if the reported applications in this bug are able to run successfully. + + 1. Run the command 'wine notepad'. Notice the warning from p11-kit. + 2. sudo apt-get install libp11-kit-gnome-keyring:i386 + 3. Run the command 'wine notepad' again. Notice that the warning is gone. [Regression Potential] Minimal, several rdepends build testing have been completed successfully and nothing in the keyring code is attempting to dlopen any hardcoded library paths. gnome-keyring is still installing libraries to /usr/lib instead of the multarch compatible /usr/lib/$(DEB_HOST_MULTIARCH) directory. The attached patch does the conversion. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/859600 Title: Please convert gnome-keyring to multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 859600] Re: Please convert gnome-keyring to multiarch
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 multiarch on raring. For the testcase, I'd say this should be something like that: [Test case] (on an amd64 system) 1. Run the command 'wine notepad'. Notice the warning from p11-kit. 2. sudo apt-get install libp11-kit-gnome-keyring:i386 3. Run the command 'wine notepad' again. Notice that the warning is gone. ** Patch added: "gnome-keyring_3.2.2-2ubuntu4.3.precise.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+attachment/3712483/+files/gnome-keyring_3.2.2-2ubuntu4.3.precise.debdiff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/859600 Title: Please convert gnome-keyring to multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 859600] Re: Please convert gnome-keyring to multiarch
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 explicitly install the new libp11-kit package for i386. I hope I'll get around to posting a working patch for 12.04 later today. BTW, how is the new libp11-kit-gnome-keyring supposed to find it's way to the affected users? Will wine declare a dependency on libp11-kit-gnome-keyring:i386 or something? On Mon, Jun 24, 2013 at 2:14 AM, Rodney Dawes <859...@bugs.launchpad.net> wrote: > @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 subscribed to the bug > report. > https://bugs.launchpad.net/bugs/859600 > > Title: > Please convert gnome-keyring to multiarch > > Status in “gnome-keyring” package in Ubuntu: > Fix Released > Status in “gnome-keyring” source package in Precise: > In Progress > Status in “gnome-keyring” source package in Quantal: > Won't Fix > Status in “gnome-keyring” source package in Raring: > Fix Released > Status in “gnome-keyring” package in Debian: > New > > Bug description: > [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 > > [Regression Potential] > Minimal, several rdepends build testing have been completed successfully > and nothing in the keyring code is attempting to dlopen any hardcoded library > paths. > > gnome-keyring is still installing libraries to /usr/lib instead of the > multarch compatible /usr/lib/$(DEB_HOST_MULTIARCH) directory. The > attached patch does the conversion. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+subscriptions -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/859600 Title: Please convert gnome-keyring to multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 859600] Re: Please convert gnome-keyring to multiarch
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 Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/859600 Title: Please convert gnome-keyring to multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 859600] Re: Please convert gnome-keyring to multiarch
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 1.4.1. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/859600 Title: Please convert gnome-keyring to multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 859600] Re: Please convert gnome-keyring to multiarch
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 Selected version '3.2.2-2ubuntu4.2' (Ubuntu:12.04/precise-proposed [i386]) for 'gnome-keyring:i386' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: gnome-keyring:i386 : Depends: libcap-ng0:i386 but it is not going to be installed Depends: libgck-1-0:i386 (>= 2.91.1) but it is not going to be installed Depends: libgcr-3-1:i386 (>= 3.2.2) but it is not going to be installed Depends: libcap2-bin:i386 but it is not going to be installed Recommends: libp11-kit-gnome-keyring:i386 but it is not going to be installed E: Unable to correct problems, you have held broken packages. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/859600 Title: Please convert gnome-keyring to multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 859600] Re: Please convert gnome-keyring to multiarch
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 because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/859600 Title: Please convert gnome-keyring to multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 544570] Re: Changing password to something similar hangs
When will this be fixed in lucid? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/544570 Title: Changing password to something similar hangs To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/544570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 802968] Re: Changing password to something similar in gnome-about-me hangs
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/802968 Title: Changing password to something similar in gnome-about-me hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/802968/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 802968] [NEW] Changing password to something similar in gnome-about-me hangs
Public bug reported: 1. Start gnome-about-me. 2. Choose 'Change password' 3. Authenticate and try to set a new password, changeing only one position. The dialog will hang forever. passwd correctly reports the following error immediately: Bad: new password must be different than the old one ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-system-tools 2.30.0-0ubuntu3 Uname: Linux 2.6.39.2-lowlatency-1 x86_64 Architecture: amd64 Date: Tue Jun 28 14:35:29 2011 InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.3) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-system-tools ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/802968 Title: Changing password to something similar in gnome-about-me hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/802968/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 665115] Re: changing "Visual Effects" leads to login-screen
I'll have another look into it. You are right, it is the video driver which is the problem. glx gears also quits with a strange error, but I think it did not crash. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/665115 Title: changing "Visual Effects" leads to login-screen -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 665115] Re: changing "Visual Effects" leads to login-screen
-- changing "Visual Effects" leads to login-screen https://bugs.launchpad.net/bugs/665115 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 665115] [NEW] changing "Visual Effects" leads to login-screen
Public bug reported: Binary package hint: gnome-control-center I tried to change Visual Effects from None to Normal and was brought back to the Login screen without a warning (gnome restart?). I would at least expect a warning if a simple mouseclick can have such "devastating" sideeffects. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-control-center 1:2.30.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.31-11.154-rt Uname: Linux 2.6.31-11-rt x86_64 Architecture: amd64 Date: Fri Oct 22 15:16:30 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-control-center ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- changing "Visual Effects" leads to login-screen https://bugs.launchpad.net/bugs/665115 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 568484] Re: evolution / groupwise access only possible by hostname
This weird reason was that I named the host mail.local. And by default, *.local are in ignored hosts. -- evolution / groupwise access only possible by hostname https://bugs.launchpad.net/bugs/568484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 568484] Re: evolution / groupwise access only possible by hostname
Out of some weird reason, evolution used the proxy if the name was not in /etc/hosts. When I add the servers IP to System->Preferences->Network proxy->Ignored Hosts, it works. -- evolution / groupwise access only possible by hostname https://bugs.launchpad.net/bugs/568484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 568484] Re: evolution / groupwise access only possible by hostname
Just tried the DNS hostname of the server. Does not work either, even though ping/dig/hostname all give the correct result. Even reverse lookups work properly. The only way it works here is with an entry in /etc/hosts -- evolution / groupwise access only possible by hostname https://bugs.launchpad.net/bugs/568484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 568484] Re: evolution / groupwise access only possible by hostname
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/45026104/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/45026105/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/45026106/ProcStatus.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/45026107/XsessionErrors.txt -- evolution / groupwise access only possible by hostname https://bugs.launchpad.net/bugs/568484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 568484] [NEW] evolution / groupwise access only possible by hostname
Public bug reported: Binary package hint: evolution I use evolution to access our groupwise 7 server. Until now (that is on hardy) we had just specified the servers IP address. In lucid, this seems to be broken as I could not access the server when I entered its IP. After I made an entry in hosts and changing the server field in account setup accordingly it works. (By server field I mean Edit->Preferences->[Account]->Receiving Email->Server: ) ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: evolution 2.28.3-0ubuntu9 ProcVersionSignature: Ubuntu 2.6.31-10.153-rt Uname: Linux 2.6.31-10-rt i686 Architecture: i386 Date: Thu Apr 22 17:18:31 2010 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: evolution ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- evolution / groupwise access only possible by hostname https://bugs.launchpad.net/bugs/568484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
