** 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.
--
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()
** 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.
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
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()
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
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
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
** 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
** 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
** 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.
--
** 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
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
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,
** 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
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
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
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
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
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
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
@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:
@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 /
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
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
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
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
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
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
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.
--
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 =
- 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:
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
** 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.
--
34 matches
Mail list logo
