Hi Karl,
If you still have the stuff below installed, please can you rerun your
configure command and post back whether your build enables or disables HAL
support (you could just attach the configure output):
- install gnome-devel
- download gnome-keyring from svn
- configure with prefix =
Thanks for that Karl - this confirms my suspicions that you're not
compiling with HAL support so should not see this bug (but won't be able
to store keyrings on removeable media).
The code where the bug is is:
324 locvol-hal_volume = TRUE;
and earlier in the same file, the GkrLocationVolume
I've been doing a bit of investigation into this where I can spare the time.
The gnome-keyring-daemon is getting started by the gdm PAM module:
gnome-keyring-2.22.1/pam/gkr-pam-module.c
In function setup_child()
Line
274 char *args[] = { GNOME_KEYRING_DAEMON, -d, --login, NULL};
then
I've done a lot more work on this tonight and have the following
information to submit:
Workaround
---
This isn't really a workaround as you won't have any keyring functionality but
at least you can log in.
1) Enable login by disabling the gnome keyring PAM Module:
# cp
I'm possibly noticing a trend here I've seen someone say that this bug
happens on an Asus EePC which has a flash-based hard disk. Some of the above
comments suggest that the bug occurs on a USB Flash drive booted with Hard but
not on a real internal disk.
And in my case, my laptop has some
I've also hit the same bug after live upgrading from Ubuntu Gutsy to
Hardy. The Live CD also works fine for me but GDM hangs on login for my
disk environment.
I removed the following line from /etc/pam.d/gdm :
session optionalpam_gnome_keyring.so auto_start
But obviously now, although my
