** No longer affects: null
--
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/573387
Title:
gnome-keyring-daemon fails to start
To manage notifications about this bug go to:
Marking this bug as fixed since I'm no longer able to reproduce the bug.
If anyone else is still affected by the bug, please reopen it.
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop
Milan: I don't have the issue at the moment. However, I think I had it
for a while after upgrading, IIRC it was fixed by a maintenance upgrade.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
xlash911: are you seeing the same messages as the ones from the
description of this bug in /var/log/auth.log?
Andreas: does your problem still happen in 10.10?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
I am having the same problem... very annoying. Since upgrading to 10.10,
I get promted like 10 times for Keyring password, due to the unability
to communicate to g-k-d.
I can see it's started, but Seahorse can't seem to communicate with it.
I am using auto login also.
Thanks,
--
You received
HP: and what does 'ps x | grep keyring' returns on your box after
booting without your script?
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in
Seems to be the same issue then. Are you using autologin or password-
less login?
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
Yes, but that doesn't change the problem. Bug 583428 is about g-k-d
hanging when started without a password, whether it actually needs one
or not. ;-) BTW, let's comment this on that report rather than here,
which may not be the same issue.
--
gnome-keyring-daemon fails to start
g-k-d should be started by it's PAM module. If it's not started on login
before any app tries to use it, then it's the problem. What does
/etc/pam.d/gdm contains?
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a
Maybe you should remove the .service file you added manually. Bug 525642
is fixed now, and manual tweaks like that can lead to problems. It's
possible that gnome-keyring is started via D-Bus before the PAM module
loads it, so it lacks the --login option that automatically unlocks the
keyring. But
Tried to remove the service file, this resulted in the original problem with
GKD not starting when logging in through GDM with a password. Seahorse produces
the following error message on the terminal:
** Message: secret service operation failed: The name org.freedesktop.secrets
was not
Btw, I checked the patch on
https://bugzilla.gnome.org/show_bug.cgi?id=619209. I It won't work, the
difference is mainly that they always pass the --login option to GKD
independent of whether a password was entered or not. In my case, i.e.
logging in with a password, there shouldn't be any
Yeah, I know, normally the --login option should be present in your case, but
for some reason it's not. I don't really see why it should work differently on
your system than on mine (say). Do you have a personal config starting g-k?
e.g. check with:
ls ~/.config/autostart/*keyring*
Else, you
The problem is that it seems like the daemon doesn't start correctly
early in the login process. The reason I lack the --login option is
because it, in the case where I have the .service file present, is
started when the first client requests the service. I really think, and
this seems to be
Without auto-login I get the following error messages in auth.log:
May 24 21:58:18 minotaur gnome-keyring-daemon[3045]: couldn't connect to dbus
session bus: /bin/dbus-launch terminated abnormally with the following error:
No protocol specified#012Autolaunch error: X11 initialization failed.
May
Is that without autologin and without password-less enabled?! That seems
very similar to what we get when it's on.
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
That was without auto-login and without password-less login.
I get the messages in the original description when auto-login is enabled.
Output from 'ps x | grep keyring' in this case is:
gnome-keyring-daemon --start --components=secrets
But that is likely only due to the fact that I added a
** Summary changed:
- gnome-keyring-daemon fails to start
+ gnome-keyring-daemon fails to start when password-less login is enabled
** Changed in: gnome-keyring (Ubuntu)
Status: New = Triaged
** Changed in: gnome-keyring (Ubuntu)
Importance: Low = Medium
--
gnome-keyring-daemon
I was using automatic login (but the account is not a member of the
nopasswdlogin group) when I filed the original bug report. I tried
disabling auto login, but that only made things worse, now every
application using the g-k-d just hangs when it tries to communicate with
the daemon.
--
Ah, that was what I feared: your bug is different from the password-less
issue. So let's say the latter is bug 525642, and deal with your problem
here. What does 'ps x|grep keyring' return, with and without autologin
enabled? What errors do you get in /var/log/auth.log in both cases?
(The logs
I am using password-less login.
I have exactly the same lines appearing in the auth.log file. I tried the
solution in bug 525642 (adding the missing .service file), but since
gnome-keyring-daemon doesn't communicate with dbus, it didn't help.
--
gnome-keyring-daemon fails to start
** Changed in: gnome-keyring
Status: New = Incomplete
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
desktop-bugs mailing
I think the upstream report is not related, see bug 525642 instead.
You're not using users-admin's password-less login option (Password:
Not asked on login), are you?
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are
** Bug watch added: GNOME Bug Tracker #619209
https://bugzilla.gnome.org/show_bug.cgi?id=619209
** Also affects: gnome-keyring via
https://bugzilla.gnome.org/show_bug.cgi?id=619209
Importance: Unknown
Status: Unknown
--
gnome-keyring-daemon fails to start
** Changed in: gnome-keyring
Status: Unknown = New
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
desktop-bugs mailing
closing if that's a duplicate
** Changed in: gnome-keyring (Ubuntu)
Importance: Undecided = Low
** Changed in: gnome-keyring (Ubuntu)
Status: New = Invalid
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are
I would argue that this is a separate bug . Bug #525642 deals with the
missing service file, which, had it existed, would only have solved
parts of the problem. For example, ssh-agent functionality does not work
if the daemon is started by dbus since it relies on setting environment
variables.
--
Thank you for your bug report. The issue is an upstream one and it would
be nice if somebody having it could send the bug the to the people
writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)
** Changed in: gnome-keyring (Ubuntu)
Status: Invalid = New
--
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/47098478/Dependencies.txt
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring
It seems like this bug may be a duplicate of bug #525642. However, even
though creating a new service for the org.freedesktop.secrets.service
fixes most of this issue, the start scripts in /etc/xdg/autostart/gnome-
keyring-* are still broken. The ssh-agent functionality will probably
not work
30 matches
Mail list logo
