http://bugzilla.novell.com/show_bug.cgi?id=566286 http://bugzilla.novell.com/show_bug.cgi?id=566286#c1 --- Comment #1 from Ludwig Nussel 2009-12-20 11:46:53 CET --- The problem is known since quite a while obviously, see bug 555610 and bug 553272 and bug 522361. What's even worse is that if one re-enters all passwords and chooses to store them in gnome-keyring, pidgin will still prompt for the passwords on next start up. Apparently gnome-keyring integration only works with one account or when activating one account at a time. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=566286 http://bugzilla.novell.com/show_bug.cgi?id=566286#c3 --- Comment #3 from Ludwig Nussel 2010-01-07 09:58:58 CET --- I'll try but I'm not sure it will fix the issue. gnome-keyring sometimes just seems to be running for some reason. Maybe some random other program causes it to start. IMHO pidgin really should remember where it got the password from and store it there again. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=566286 http://bugzilla.novell.com/show_bug.cgi?id=566286#c5 --- Comment #5 from Ludwig Nussel 2010-01-07 11:33:44 CET --- Is a migration really needed? If so pidgin could just ask once whether to migrate all passwords then. If on first start gnome-keyring is running pidgin could of course try to use it but if the user presses cancel in the setup dialog of gnome-keyring it could fall back to the xml file (IIRC KDE programs behave that way if one rejects setting up kwallet). Is there a way to check whether gnome-keyring is already set up (without starting the setup procedure at the same time)? If gnome-keyring is not set up pidgin could just silently continue using the xml method. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=566286 http://bugzilla.novell.com/show_bug.cgi?id=566286#c6 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |567799 --- Comment #6 from Stanislav Brabec 2010-01-08 13:45:20 CET --- Guessing from product = openSUSE 11.0, Ludwig complains to introduction of gnome-keyring support in old products. And I agree, it should not happen. I propose to keep gnome-keyring support in products where it was enabled before the update. I'll prepare update that should return pre-upgrade behavior to all products. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=566286 http://bugzilla.novell.com/show_bug.cgi?id=566286#c8 Vincent Untz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|vuntz@novell.com | --- Comment #8 from Vincent Untz 2010-01-08 16:35:01 UTC --- (In reply to comment #7)

Summary for SLE10 and 11.0, 11.1:

Disable it there, it was never enabled there.

Makes sense.

Summary for SLE11, 11.2 and Factory:

Let somebody else decide, whether it is wanted there.

There is my opinion:

Let's either upstream or drop our long-time-off patches.

Well, I guess that the patch was made for SLE, so it'd probably make sense to keep for SLE11. But it's not my decision. Here's the upstream bug about using the keyring: http://developer.pidgin.im/ticket/673. It looks like they want to integrate something like this in 3.0.0 (no idea when it'll be released), but it's unlikely they'll go with our patch. So, yeah, for openSUSE, I'm fine removing the patch, I guess. On a general note, I'm not sure why we have so many patches for pidgin that are not upstream, so I'm all for upstreaming them, or removing them. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=566286 http://bugzilla.novell.com/show_bug.cgi?id=566286#c10 --- Comment #10 from Ludwig Nussel 2010-01-10 11:25:29 CET --- pidgin from home:vuntz:11.2-testing certainly works better if gnome-keyring is not running. the passwords are not wiped from the config anymore. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=566286 http://bugzilla.novell.com/show_bug.cgi?id=566286#c12 --- Comment #12 from Stanislav Brabec 2010-01-13 00:13:02 CET --- I guess I have to install and parse distribution-release. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=566286 http://bugzilla.novell.com/show_bug.cgi?id=566286#c15 --- Comment #15 from Stanislav Brabec 2010-01-13 12:29:53 CET --- I guess that there are different requrements. But please correct me if anybody has a different opinion. SLED: - Customers use GNOME+pidgin or KDE+kopete. In both cases, opening the appropriate keyring happens automatically during login. - Customers want to store IM passwords really safe. openSUSE: - Users use arbitrary combinations of pidgin and desktop environment. In some of these combinations, pidgin requires extra password to unlock the keyring and it is not possible to skip this dialog. - Encrypted local storage of passwords is not a top priority. Related discussion: bug 186189 It is marked as fixed, but I think that it is not. The current solution - KDE/GNOME unlocks its own keyring on login, other environments don't unlock anything, is far from an optimal solution. The same problems affects other users of keyrings: - evolution outside GNOME (but how many people do it?) - FATE outside KDE -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=566286 http://bugzilla.novell.com/show_bug.cgi?id=566286#c17 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #17 from Stanislav Brabec 2010-01-13 19:12:21 CET --- Use of distribution-release does not work as well: have choice for distribution-release: dummy-release sles-release sled-release Summary: Our build system makes impossible to keep this patch for SLE11 and not apply for openSUSE. So there remains several bad solutions: 1. Implement an incredibly ugly hack to discriminate between openSUSE 11.1 and SLED11 during compile time. 2. Drop the patch breaking a small piece of privacy on SLED. 3. Keep this patch in openSUSE and consider this report as INVALID, at least for openSUSE versions that perform code base for SLED. 4. Keep things as they are for now and start working on another solution and provide it with the next security issue. If there are no objections, I'll go for 3, as it means least effort. It will fix openSUSE complains for 11.0 and 11.2, but not for 11.1. Going to 2 would be even better, but requires approval from the SLED managers. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=566286 http://bugzilla.novell.com/show_bug.cgi?id=566286#c19 Vincent Untz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |btaylor1@novell.com --- Comment #19 from Vincent Untz 2010-01-27 17:33:01 UTC --- *** Bug 574419 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=574419 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=566286 http://bugzilla.novell.com/show_bug.cgi?id=566286#c21 Wolfgang Rosenauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wolfgang@rosenauer.org --- Comment #21 from Wolfgang Rosenauer 2010-03-04 08:08:58 UTC --- Just got the 11.2 update and suddenly all my accounts are not working anymore. This cannot be a solution! I like that openSUSE takes updates a bit more relaxed than before but this type of change really must be avoided and if really not possible be documented in the patch description. I cannot even find anything about it in the rpm changelog. That's nothing I expect from an official security online update. Not amused. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.