** Changed in: gnome-keyring
Importance: Unknown = Medium
--
gnome-keyring-manager requires non-empty password
https://bugs.launchpad.net/bugs/108993
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I've deleted my user password completely, set the nullok directive in PAM and
now everything works ok without asking for password every five minutes EXCEPT
gnome-keyring. It still asks for my password and is unusable for me for this
reason. I think this is a bug and it should be fixed.
And yes,
Christian is right. What he wrote has nothing to with what you have
done. I have this problem too.
THIS IS A BUG! Open the ticket again!
--
gnome-keyring-manager requires non-empty password
https://bugs.launchpad.net/bugs/108993
You received this bug notification because you are a member of
This has nothing to do with this bug. The bug was - you can't choose an EMPTY
password.
Have you chosen a password or did you leave it empty (the keyring password!)?
--
gnome-keyring-manager requires non-empty password
https://bugs.launchpad.net/bugs/108993
You received this bug notification
I am still getting asked for my keyring password on 8.04 with gnome-
keyring 2.22.1-1 when I have automatic login on.
It says: Enter password for default keyring to unlock
The application 'nm-applet' (/usr/bin/nm-applet) wants access to the default
keyring, but it is locked
It does not ask me
Can this package (gnome-keyring - 2.21.5-0ubuntu1) be backported to
Gutsy?
--
gnome-keyring-manager requires non-empty password
https://bugs.launchpad.net/bugs/108993
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This bug was fixed in the package gnome-keyring - 2.21.5-0ubuntu1
---
gnome-keyring (2.21.5-0ubuntu1) hardy; urgency=low
* New upstream version:
- Proper support for creating and destroying objects through PKCS#11.
- Support for setting PKCS#11 attributes.
- Fix hanging
** Changed in: gnome-keyring
Status: In Progress = Fix Released
--
gnome-keyring-manager requires non-empty password
https://bugs.launchpad.net/bugs/108993
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Fixed upstream, thanks.
** Changed in: gnome-keyring (Ubuntu)
Status: Invalid = Fix Committed
--
gnome-keyring-manager requires non-empty password
https://bugs.launchpad.net/bugs/108993
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Changed in: gnome-keyring
Status: Won't Fix = In Progress
--
gnome-keyring-manager requires non-empty password
https://bugs.launchpad.net/bugs/108993
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
LEVIS,
Upstream has reopened the bug. I suspect eventually we'll end up with
the ability to enter a null password for the keyring.
As for the gnome-screensaver problem... yes I agree. Gnome screen saver
needs to properly use PAM to generate it's password prompts (or lack of
password prompts). If
I use a fingerprint reader so I have create a bash file which launch :
echo PASSWORD | /path/to/pam-keyring-tool -u -s
but I have another problem maybe you can help me, so I use fingerprint, and I
have tweak for gnome-screensaver for use fingerprint with it.
But for unlock the screensaver I must
pam keyring does not solve the problem. It only solves the problem if
the login password is supplied as plain text and the login password is
the same as the keyring password.
Those of us using fingerprints to login aren't supplying a plain text
password and hence get prompted. Those using other
** Changed in: gnome-keyring (upstream)
Status: Confirmed = Won't Fix
--
gnome-keyring-manager requires non-empty password
https://bugs.launchpad.net/bugs/108993
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Upstream closed the bug with this comment:
Gnome Keyring now uses PAM and ties into the user's login password. This will
be included in the next release of gnome-keyring and Gnome.
It seems this would solve the problem you're experiencing. It fits in very well
with single sign on now.
BTW, if
** Changed in: gnome-keyring (upstream)
Status: Unknown = Confirmed
--
gnome-keyring-manager requires non-empty password
https://bugs.launchpad.net/bugs/108993
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
That's known upstream, http://bugzilla.gnome.org/show_bug.cgi?id=386866
** Changed in: gnome-keyring (Ubuntu)
Sourcepackagename: gnome-keyring-manager = gnome-keyring
Status: Needs Info = Confirmed
** Bug watch added: GNOME Bug Tracker #386866
Thank you for your bug. What version of Ubuntu do you use. How do you
trigger the bug? How do you try to set the password there?
** Changed in: gnome-keyring-manager (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs
Status: Unconfirmed = Needs Info
I am using Ubuntu Feisty.
Steps to reproduce:
Hm - first - I think it is no bug, just a missing feature or something the
developers forgot - or didn't want to implement.
OK.
Using a Computer with WLAN ability, , with a fresh user without previour
gnome-keyring-manager use, just connect with
** Summary changed:
- nm-applet asks for non-empty password
+ gnome-keyring-manager requires non-empty password
--
gnome-keyring-manager requires non-empty password
https://bugs.launchpad.net/bugs/108993
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Also of note, your request is quite similar to bug 34898 , which seeks
to remove the keyring-manager functionality from network-manager
altogether. Your point was slightly different and valid though so that
is why I am moving it over.
--
gnome-keyring-manager requires non-empty password
21 matches
Mail list logo
