Bug 327391 - Pidgin doesn't use keyring
Summary: Pidgin doesn't use keyring
Status: VERIFIED FIXED
: 408743 463024 463975 (view as bug list)
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Alpha 0
Hardware: Other openSUSE 10.3
: P4 - Low : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL: http://developer.pidgin.im/ticket/673
Whiteboard: gnome-function-does-not-work
Keywords: should_go_upstream
Depends on:
Blocks:
 
Reported: 2007-09-21 23:08 UTC by Alberto Passalacqua
Modified: 2009-03-06 09:27 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alberto Passalacqua 2007-09-21 23:08:31 UTC
Pidgin doesn't save passwords in GNOME keyring, but it uses its own file.
Comment 1 Mark Gordon 2007-09-24 15:43:20 UTC
The upstream version of this bug is http://developer.pidgin.im/ticket/673
Comment 2 JP Rosevear 2007-09-24 22:50:48 UTC
We had our own patch for gaim 1.5 that never got taken upstream and the upstream code base changed a lot.  We probably just have to push upstream to take this on.
Comment 3 Magnus Boman 2008-03-19 09:21:03 UTC
Closing as Later as per our should_go_upstream guidelines
Comment 4 JP Rosevear 2008-03-19 14:06:51 UTC
Keeping this one alive here as it was our patch that died off causing the regression on suse.
Comment 5 JP Rosevear 2008-05-15 19:07:13 UTC
Will not be done for 11.0.
Comment 6 JP Rosevear 2008-07-16 13:01:16 UTC
*** Bug 408743 has been marked as a duplicate of this bug. ***
Comment 7 JP Rosevear 2009-01-06 16:42:39 UTC
*** Bug 463024 has been marked as a duplicate of this bug. ***
Comment 8 JP Rosevear 2009-01-06 18:03:12 UTC
Turns out maw had already ported the patch, but it was a little bit broken.  Submitted a fix for SLED 11 and openSUSE 11.2.
Comment 9 Gabriel Burt 2009-01-06 23:08:10 UTC
*** Bug 463975 has been marked as a duplicate of this bug. ***