[Bug 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
** Changed in: gnome-keyring Importance: Unknown = Critical -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
Note that this bug also occurs in Gutsy (7.10) with current updates. The proposed work-around (marking the root device as non-removable) seems to solve the problem here as well. Thanks! -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
** Tags added: verification-done ** Tags removed: verification-needed -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
The proposed update seems to have fixed the problem for me. I haven't seen gnome-keyring-daemon segfaults ever since yesterday afternoon when I enabled the hardy-proposed channel and applied all the updates therein. Hardy is installed on an IDE disk, which is attached to the following IDE controller: 00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01) Prior to the proposed update, gnome-keyring-daemon often segfaulted upon gnome login. I was able to login gnome though. $ zgrep keyring /var/log/messages.1.gz May 14 06:59:28 thinkpad kernel: [ 81.939465] gnome-keyring-d[5345]: segfault at ba7ab81a eip 080ab018 esp bfac48ac error 4 May 15 21:07:37 thinkpad kernel: [ 195.836481] gnome-keyring-d[5286]: segfault at 4394db4d eip 080ad140 esp 4394db51 error 6 May 15 21:15:52 thinkpad kernel: [ 258.633868] gnome-keyring-d[5754]: segfault at ba7ab81a eip 080ab018 esp bf9d7c0c error 4 May 16 14:08:54 thinkpad kernel: [ 111.294674] gnome-keyring-d[5207]: segfault at ba7ab81a eip 080ab018 esp bfd1b63c error 4 May 16 22:21:15 thinkpad kernel: [ 77.757725] gnome-keyring-d[5245]: segfault at ba7ab81a eip 080ab018 esp bfdbb13c error 4 May 16 22:28:28 thinkpad kernel: [ 336.826516] gnome-keyring-d[7783]: segfault at ba7ab81a eip 080ab018 esp bf86e4fc error 4 May 17 07:19:22 thinkpad kernel: [ 95.575549] gnome-keyring-d[5265]: segfault at ba7ab81a eip 080ab018 esp bfb0322c error 4 -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
Accepted into -proposed, please test and give feedback here ** Changed in: gnome-keyring (Ubuntu Hardy) Status: Triaged = Fix Committed Target: ubuntu-8.04.1 = None ** Tags added: verification-needed -- 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 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
Re: [Bug 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
Hi, MattPie [2008-05-20 17:16 -]: 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. If it is actually removable (such as a CD, or an SD-Card in a card reader), why should we poke false information into Hal? It should reflect the physical reality, not what we'd like it to be. :-) -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
Thank you for finding a fix. When will 2.22.2 be out? -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
** Changed in: gnome-keyring (Ubuntu) Status: Triaged = Fix Committed -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
** Attachment added: the debdiff for the update http://launchpadlibrarian.net/14603989/gnome-keyring.debdiff -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
** Changed in: gnome-keyring Status: New = Fix Released -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
** Changed in: gnome-keyring (Ubuntu Hardy) Target: None = ubuntu-8.04.1 ** Changed in: gnome-keyring (Ubuntu) Target: ubuntu-8.04.1 = None -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
The method of setting the boot device as not removable described by Stewart and nyamap above worked well for my system with an Adaptec 5405 RAID controller, with the exception that I had to do this for the parent of the device with volume.mount_point = '/'. In my case both the root file system (with volume.mount_point = '/') on device 12, and swap on device 13, had a line in their hal-device listing: info.parent ='/org/freedesktop/Hal/devices/storage_serial_SAdapter_mylabel_2E2B5983' where the string after the = was the uid of device 14, which had the storage.removable property true until changed. -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
Thanks nyamap. Your fix worked well for my 4GB hitachi microdrive attached to a IDE-CFII adapter. -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
** Changed in: gnome-keyring (Ubuntu Hardy) Importance: Undecided = High Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs) Status: New = Triaged -- 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
Re: [Bug 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
Thanks! It worked for me as well... sön 2008-05-04 klockan 01:19 + skrev Robin: Likewise, adding that line in to /etc/rc.local on an Asus PC701 (eee) allowed me to boot from a 4G USB stick, and then in to Gnome. Thanks to all. -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
Confirmed the bug on a fresh install on AMD x86_64 SMP. Confirmed that the nyamap's workaround allows me to log in as expected. -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
Stewart, MattPie, bbauto: I am sorry. hal-set-property is right. In my case, it is same as MattPie. The volume entry does not have storage.removable key. How about this: hal-get-property --key block.storage_device --udi `hal-find-by-property --key volume.mount_point --string /` | xargs -l1 hal-set-property --key storage.removable --bool false --udi I hope this will help until it fixed in upstream. -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
Thanks nyamap, that one worked for me. -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
Likewise, adding that line in to /etc/rc.local on an Asus PC701 (eee) allowed me to boot from a 4G USB stick, and then in to Gnome. Thanks to all. -- 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
Re: [Bug 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
Did not find any man pages for hal-device is it possible to write to file, edit the file and write it back again -- hal-device Hal.txt edit the file Hal.txt and write back hal-device Hal.txt Best regards Bengt Berglund fre 2008-05-02 klockan 03:03 + skrev nyamap: Hi, All. I encountered this problem on my asus eee pc with 8G SDHC card. My quick and dirty workaround is make root filesystem not removable. 1. Login with Ctrl-Alt-F2 or Xterm session. 2. run 'hal-device' to find device which contains root file system. (device means not media but controller device) 3. mark that device to unremovable using 'hal-set-priority --udi /org/freedesktop/Hal/devices/storage_USB2_0_CardReader... --key storage.removable --bool false' I temporary added this line to /etc/rc.local. I could get login to my laptop. -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
@nyamap, thanks for your tip which has allowed me (with a mod) to log in to Gnome desktop on EeePC. You have two errors in your step 3 (you must use hal-set-property, not hal-set-priority; also, you need to use the UUID string, not the info.udi string), so here are the corrected steps to follow: 1. Login with Ctrl-Alt-F2 or Xterm session. 2. run 'hal-device' to find device which contains root file system. (device means not media but controller device) on my EeePC, it is device 2. Look for the device that has volume.mount_point = '/'. Make a note of the udi string. 3. mark that device to unremovable using 'hal-set-property --udi /org/freedesktop/Hal/devices/volume_uuid_6662900c --key storage.removable --bool false' Your own device will have a different string beginning with volume_uuid_ Run this in the shell and if it works, put in rc.local, then restart gdm with 'sudo /etc/init.d/gdm restart' -- 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 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
[Bug 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
Same problem compact flash drive on a cf/ide adapter in a Thinkpad R40. After reading comments above, I have a temporary workaround for this is, stop hal. Ctrl-Alt-F1, sudo /etc/init.d/hal stop, sudo /etc/init.d/gdm restart. This allowed me to login and do some stuff. Network Manager would come up and wireless worked. Several things not working because hal missing but it will enable one to get on a wireless network to do and update when ever the fix becomes available, for those with wireless only. -- 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
Re: [Bug 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
If you -- Ctrl-Alt-F2 -- login -- rm /tmp/X0-lock -- startx Then everything seems to work, even Gnome-keyring You can also Click: System--Administration--Login window--Saftey-- Click Automatic Login -- user x, This works great until you need to change user, then you will have to make the same manover again. tor 2008-05-01 klockan 14:15 + skrev Bigm8: Same problem compact flash drive on a cf/ide adapter in a Thinkpad R40. After reading comments above, I have a temporary workaround for this is, stop hal. Ctrl-Alt-F1, sudo /etc/init.d/hal stop, sudo /etc/init.d/gdm restart. This allowed me to login and do some stuff. Network Manager would come up and wireless worked. Several things not working because hal missing but it will enable one to get on a wireless network to do and update when ever the fix becomes available, for those with wireless only. -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
Hi, All. I encountered this problem on my asus eee pc with 8G SDHC card. My quick and dirty workaround is make root filesystem not removable. 1. Login with Ctrl-Alt-F2 or Xterm session. 2. run 'hal-device' to find device which contains root file system. (device means not media but controller device) 3. mark that device to unremovable using 'hal-set-priority --udi /org/freedesktop/Hal/devices/storage_USB2_0_CardReader... --key storage.removable --bool false' I temporary added this line to /etc/rc.local. I could get login to my laptop. -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
Thank you for your work on the issue. i've opened the bug upstream on http://bugzilla.gnome.org/show_bug.cgi?id=530316 and I think it has enough informations to be debugged ** Changed in: gnome-keyring (Ubuntu) Status: Confirmed = Triaged Target: None = ubuntu-8.04.1 ** Also affects: gnome-keyring via http://bugzilla.gnome.org/show_bug.cgi?id=530316 Importance: Unknown Status: Unknown ** Tags removed: need-i386-retrace -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
There is no code change upstream which seem likely to do a change there, maybe the people building from svn didn't build the pam integration code though? ** Changed in: gnome-keyring (Ubuntu) Importance: Medium = High -- 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
Re: [Bug 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
Sebastien - that could well be it. I don't have a log of precisely what I did, but it boils down to roughly: - install gnome-devel - download gnome-keyring from svn - configure with prefix = /usr - install I doubt gnome-devel installs any PAM headers, so gnome-keyring probably didn't attempt to build any pam integration code. An ldd of my /usr/bin/gnome-keyring-daemon gives: linux-gate.so.1 = (0xb7f93000) libgthread-2.0.so.0 = /usr/lib/libgthread-2.0.so.0 (0xb7f7d000) librt.so.1 = /lib/tls/i686/cmov/librt.so.1 (0xb7f74000) libgconf-2.so.4 = /usr/lib/libgconf-2.so.4 (0xb7f43000) libdbus-1.so.3 = /usr/lib/libdbus-1.so.3 (0xb7f0d000) libgcrypt.so.11 = /lib/libgcrypt.so.11 (0xb7ec) libtasn1.so.3 = /usr/lib/libtasn1.so.3 (0xb7eb) libgobject-2.0.so.0 = /usr/lib/libgobject-2.0.so.0 (0xb7e74000) libglib-2.0.so.0 = /usr/lib/libglib-2.0.so.0 (0xb7dc3000) libpthread.so.0 = /lib/tls/i686/cmov/libpthread.so.0 (0xb7daa000) libc.so.6 = /lib/tls/i686/cmov/libc.so.6 (0xb7c5b000) libselinux.so.1 = /lib/libselinux.so.1 (0xb7c42000) /lib/ld-linux.so.2 (0xb7f94000) libgmodule-2.0.so.0 = /usr/lib/libgmodule-2.0.so.0 (0xb7c3e000) libdl.so.2 = /lib/tls/i686/cmov/libdl.so.2 (0xb7c3a000) libORBit-2.so.0 = /usr/lib/libORBit-2.so.0 (0xb7be7000) libgpg-error.so.0 = /lib/libgpg-error.so.0 (0xb7be3000) libpcre.so.3 = /usr/lib/libpcre.so.3 (0xb7bbc000) I don't see anything mentioning PAM. But I'm a perl hacker, not a C coder, and I have no dev experience of gnome, so this may not prove a thing! Please shout if there are any tests on my setup that anybody needs me to perform. Ta, Karl Sebastien Bacher wrote: There is no code change upstream which seem likely to do a change there, maybe the people building from svn didn't build the pam integration code though? ** Changed in: gnome-keyring (Ubuntu) Importance: Medium = High -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
the configure summary shows you if the pam module is built or not -- 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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
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 = /usr
- install
I believe PAM has nothing to do with this problem, except it is the
gnome-keyring PAM module which executes 'gnome-keyring-daemon -d
--login' . It is 'gnome-keyring-daemon' itself which crashes and
unfortunately the -d option means it deamonizes and returns exit 0,
before the crash occurrs causing PAM (or anything else which cares like
gdb) to think it exited normally. Then the sneaky little bugger goes and
dies and the only thing which seems to notice it is the kernel.
The actual problem lies within the gnome-keyring-daemon code while it
tries to manage removeable storage and you'll only hit this part of the
code if gnome-keyring-daemon was built with HAL Support for Removable
Devices enabled.
The reason that the work-around using 'auto-login' works is that GDM
uses a different pam config for automatic login (/etc/pam.d/gdm-
autologin) which for some reason does not include the gnome-keyring
module. Hence it's the same as deleting the gnome-keyring references
from /etc/pam.d/gdm
Having discussed this bug with a few knowledgable colleagues the
concensus is that regardless of why g_hash_table_lookup() returns null
or whether it ever should, we should always check the return code:
at hal_device_property() in gkr-location.c
323 locvol = g_hash_table_lookup (pv-volumes_by_name, name);
324 locvol-hal_volume = TRUE;
Between 323 and 324 we need a check that 'locvol' is not null before using it
as an address.
If g_hash_table_lookup should never return 'null' then perhaps an
'assert(locvol != null)' should be added, but if 'null' is a valid retun then
we need extra code to check it and handle it within this function, the simplest
being 'if (locvol != null ) { locvol-hal_volume=TRUE; }'
--
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
Re: [Bug 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
- install gnome-devel
done
- download gnome-keyring from svn
actually used the copy I had already downloaded; my copy is at revision
1137.
- configure with prefix = /usr
done - full output of configure is attached, but the summary is:
OPTIONAL DEPENDENCIES
PAM: no
DBus: 1.1.20
HAL: no
CONFIGURATION
SSH Agent:yes
Root Certificates:none
BUILD
Debug Build: no
Unit Tests: no
- install
done - restarted gnome, and everything still works great. e.g. my ssh
keys were automatically unlocked as you'd expect. No crashes reported.
Hope this helps. Let me know if you need me to build and install with
PAM and / or HAL supported.
Cheerio,
Karl
I believe PAM has nothing to do with this problem, except it is the
gnome-keyring PAM module which executes 'gnome-keyring-daemon -d
--login' . It is 'gnome-keyring-daemon' itself which crashes and
unfortunately the -d option means it deamonizes and returns exit 0,
before the crash occurrs causing PAM (or anything else which cares like
gdb) to think it exited normally. Then the sneaky little bugger goes and
dies and the only thing which seems to notice it is the kernel.
The actual problem lies within the gnome-keyring-daemon code while it
tries to manage removeable storage and you'll only hit this part of the
code if gnome-keyring-daemon was built with HAL Support for Removable
Devices enabled.
The reason that the work-around using 'auto-login' works is that GDM
uses a different pam config for automatic login (/etc/pam.d/gdm-
autologin) which for some reason does not include the gnome-keyring
module. Hence it's the same as deleting the gnome-keyring references
from /etc/pam.d/gdm
Having discussed this bug with a few knowledgable colleagues the
concensus is that regardless of why g_hash_table_lookup() returns null
or whether it ever should, we should always check the return code:
at hal_device_property() in gkr-location.c
323 locvol = g_hash_table_lookup (pv-volumes_by_name, name);
324 locvol-hal_volume = TRUE;
Between 323 and 324 we need a check that 'locvol' is not null before using it
as an address.
If g_hash_table_lookup should never return 'null' then perhaps an
'assert(locvol != null)' should be added, but if 'null' is a valid retun then
we need extra code to check it and handle it within this function, the
simplest being 'if (locvol != null ) { locvol-hal_volume=TRUE; }'
** Attachment added: config-output.txt
http://launchpadlibrarian.net/13988714/config-output.txt
--
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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
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 struct is defined:
44 typedef struct _GkrLocationVolume {
45 GQuark volume_loc;
46 gchar *name;
47 gchar *prefix;
48 gchar *friendly;
49 gboolean hidden;
50 #ifdef WITH_HAL
51 gboolean hal_volume;
52 #endif
53 } GkrLocationVolume;
'hal_volume' is only included in the structure if we're compiling with
HAL support, so whatever code branches are called should never reach
line 324 in your configuration ( and if it did it would probably crash
with an undefined symbol error of some kind).
If I get some more free time I'll see if I can diagnose further - I assume that
I now need to submit proposed fixes or root-cause analysis to the upstream bug
at http://bugzilla.gnome.org/show_bug.cgi?id=530316
(This is my first involvement in any linux bugs so forgive me if I don't know
the process yet..)
--
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 218434] Re: gnome-keyring-daemon crashed with SIGSEGV in location_manager_hal_init()
** Changed in: gnome-keyring Status: Unknown = New -- 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
