[Bug 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
The -proposed package, 2.22.1-1ubuntu1, appears to have fixed the issue for me. My config is a Hardy 8.04-release installed on a PNY USB Flash Drive with a swap and root partition. As a matter of correctness (but not really in the scope of this big), should the device that holds the root partition be allowed to be flagged as removable at all? Maybe there should be a HAL update to force the root device to be non-removable. -- gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init() https://bugs.launchpad.net/bugs/218434 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 64301] Re: Unable to unlock screen when using ldap
Problem still exists in Hardy 8.04-Release. Sigh. Note that this is a basic LDAP server, with no SSL/TLS or password required to access the server. I really like Ubuntu, but this seems like Enterprise Computing 101... RHEL5/CentOS5 has a patch in their SRPM named 'better-pam-integration' (attached) and LDAP+Gnome-screensaver works. I'll look into it, but the patch is for g-ss 2.16.1, so I'm not sure how compatible it'll be with 2.22.2 that Ubuntu is using. ** Attachment added: Patch relating to PAM from CentOS5 SRPM http://launchpadlibrarian.net/14090473/gnome-screensaver-2.16.1-better-pam-integration.patch -- Unable to unlock screen when using ldap https://bugs.launchpad.net/bugs/64301 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gnome-screensaver. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 64301] Re: Unable to unlock screen when using ldap
The patch above didn't go smoothly, and I can't justify working more on it during work time. :) But I've found a workaround: If you add 'auth sufficient pam_ldap.so' to the BEGINNING on /etc/pam.d/gnome-screensaver, gnome-screensaver unlocks properly for LDAP users. BUT, there's an odd effect on local users. If you're logged in as a local user and screen locks, you have to enter your password twice*. The first time, it'll go to 'checking...' but it doesn't gray-out the text box. Type you password in again and hit enter and the screen will unlock. Note that I'm not expert in PAM, but I don't think this will leave gaping holes in your system. * I forgot to test if you could just hit return or enter garbage for the first entry, I suspect you can. -- Unable to unlock screen when using ldap https://bugs.launchpad.net/bugs/64301 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gnome-screensaver. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
@Stewart, nyamap: This seems to be the solution, thanks a ton! GDM must
get confused when the root device is classified by hal to be removable.
Perhaps the solution is to add some logic to HAL to force the root
device to be non-removable. It doesn't make much sense to be able to
remove / anyways.
In my case, the odd thing is my USB external hard disk, OK; my USB
external flash disk, not OK. HAL must classify them differently for
some reason.
In any case, for my configuration I had to use a line closer to
nyamap's, using the storage device instead of the volume like Stewart's.
On the USB Flash, the volume_uuid_... entry didn't have
storage.removable defined, and setting it to false had no effect. The
USB Flash Device (storage_serial_PNY...) had storage.removable set to
true. Setting that to false allows me to log in properly. There's
probably slight difference based on CF cards, odd SCSI controllers, USB,
etc.
Oh, and for people testing, a one-liner that helps extract the udi:
hal-device | grep ^8: | awk '{print $4;};' | sed s/\'//g
In this case, 8 is the device number for my device. You have to figure
that part by looking at the hal-device output first. :)
--
gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
https://bugs.launchpad.net/bugs/218434
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
