** 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
It's worth noting that shortly after experiencing this problem, I
followed Grugnog's advice on this thread and checked out and compiled
the latest version of gnome-keyring from subversion. Since then, I've
had no issues, and gnome-keyring has worked like a charm. So it seems
that, whether by
Nevermind, it seems that Ovation is onto the answer...
Since it's been fixed upstream, should we attempt to solve it anyway?
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/218434
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Sebastian we've already tried both of those methods, they don't work
because the keyring only seems to fail when gdm is using it. Neither
backtracing or using valgrind produces the segfault when running from
terminal. Is there a different method I can try to help?
--
gnome-keyring-daemon crashed
the coredump attached to the bug gives this stacktrace
#0 hal_device_property (hal_ctx=0x80af768,
udi=0x80b0138
/org/freedesktop/Hal/devices/volume_uuid_744a680e_31d7_4045_bc59_111f6592138f,
key=0x808faf4 volume.is_mounted, is_removed=0, is_added=1)
at gkr-location.c:324
324
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.
--
I checked my syslogs and can confirm gnome-keyring-d [...] segfault... When
booting i also get usb1-2, device not accepting address 2, error -71, assuming
drive cash.. probably not relevant but those are the only err-messages i can
find.
Workaround (works for me cause i'm single user on a
I am getting the same problem. I do not use any flash based storage. I
have installed the hardy release the live cd boots up fine, i install,
restart log in then I'm confronted with the same problem of the original
bug post.
I did a clean install with a burned ISO of final release of hardy, not
I can confirm the same issue. I am not using any flash-based storage,
just a regular hdd.
I upgraded 7.10 x64 -- 8.04 x64 on my Macbook Pro 3,1. Upgrade appeared
to go okay, and the machine starts, but login hangs. I can access tty.
Without gdm, 8.04 is a no-go for me. I've reverted back to 7.10.
I'm using an Adaptec 2410sa controller and getting the same problems.
This problem only seems to affect USB drives, solid state discs and raid
controllers which i think are all are all SCSI devices.
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/218434
You received
SUMMARY
Hardware Affected
It seems to me, some people using eee pc's, adaptec raid cards models 2410sa
and 2610sa, usb drives.
IDE drives seem unaffected, thanks doobydave.
Two possible solutions have been found, perhaps someone could test them:
1. Grugnog suggest
I *was* running hardy on my macbook pro 3,1. Without a working gdm, I
was forced to revert to Gutsy because this is my primary OS. So, I can't
test these patches. Here's my hardware info:
description:IDE interface
product:82801HBM/HEM (ICH8M/ICH8M-E) SATA IDE Controller
vendor:
could people stop spaming this bug now, what is required is a debug
stracktrace or a valgrind log, not random comment about user getting the
issue, the bug tracker is not an user forum to add random comments it's
a tool to get bugs worked
--
gnome-keyring-daemon crashed with SIGSEGV
My valgrind log
** Attachment added: valgrind.log
http://launchpadlibrarian.net/13964363/valgrind.log
--
gnome-keyring-daemon crashed with SIGSEGV
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: valgrind.log
http://launchpadlibrarian.net/13964639/valgrind.log
--
gnome-keyring-daemon crashed with SIGSEGV
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.
--
Sebastien -
How can we get the program to crash in debug mode?
--
gnome-keyring-daemon crashed with SIGSEGV
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
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
Thanks for your work on that,
https://wiki.ubuntu.com/DebuggingProgramCrash has details on how to
install debug variants
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/218434
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
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
No issues when installed to internal drive.
--
gnome-keyring-daemon crashed with SIGSEGV
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
Does anyone know how to get a backtrace from gdb?
I've been following the guide from
https://wiki.ubuntu.com/DebuggingProgramCrash
https://wiki.ubuntu.com/Backtrace
As far as i know gdb only works if it is used on a application which is
already running or you start a application inside of gdb
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
bbauto has a temporary workaround - Bug #221850
Alt-Ctrl-F2 , Login by Textmode. sudo rm /tmp/.X0-lock , startx
then it starts up OK, after that i Enabled Automatic Login, under
System--Administration--Login Window.
--
gnome-keyring-daemon crashed with SIGSEGV
@Ovation1357 - I think you are correct that the USB/flash drive is a
correlation, however I don't think it is an absolute dependence, because
I was using a fresh Ubuntu install on a totally normal HP desktop
machine hard disk with no USB/flash in sight. The only factor I can
think of is perhaps
I'm booting 64-bit 8.04 off a USB stick and I have the same problem. I
have no physical sata/ide disk attached.
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/218434
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
I can confirm the usb-boot and nm-applet at 100%. I will try to install
on ide hd to see if any different.
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/218434
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Me too! Exactly the same...
[ 112.009494] gnome-keyring-d[5672]: segfault at 0014 eip 080759c7 esp
bfc629a0 error 6
[ 113.411076] gnome-keyring-d[5786]: segfault at 0014 eip 080759c7 esp
b79d6dc0 error 6
[ 319.909153] gnome-keyring-d[5977]: segfault at 0014 eip 080759c7 esp
Same exact problem here. 64-bit version on a dell poweredge server.
Problem started on upgrade to 8.04 this morning.
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/218434
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I'm getting the exact same problem, I've been using the release
candidate which worked perfectly until i did the last set of upgrades
about 4 days ago, so the problem is some where in the upgrades from the
release candidate to the final release.
The login screen comes up -- login -- Blank orange
Thanks for your bug report. Please try to obtain a backtrace
http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
bug report. This will greatly help us in tracking down your problem.
** Changed in: gnome-keyring (Ubuntu)
Importance: Undecided = Medium
Assignee:
you can also enable apport in /etc/defaults/apport and use it to send a
new bug
--
gnome-keyring-daemon crashed with SIGSEGV
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
I also have this now on a fresh install on a custom build desktop with
hardy, I can't install backtrace software because I have to log into the
network at school first.
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/218434
You received this bug notification because
I got the internet working on the custom build, but my backtrace isn't
capturing the segfaults.
I can run gnome-keyring-daemon inside of gdb, but it doesn't report any
problems, and it also exits normally after outputting the folder it created and
the PID of the task. I can't install valgrind,
apport-cli -p gnome-keyring-daemon doesn't find any bugs to be
reported either.. I'm still downloading valgrind.
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/218434
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Aso attached the /var/log/apport.log.1
** Attachment added: apport.log.1
http://launchpadlibrarian.net/13910871/apport.log.1
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/218434
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I'm getting the same results. After login 2 instances of gnome-keyring-
daemon open and close almost instantly, so i haven't been able to get
gdb to report any problems. the errors from dmesg are;
[ 451.243188] gnome-keyring-d[6769]: segfault at 0014 eip 080759c7 esp
bf91c9a0 error 6
[
I tried the insructions to do a backtrace but the hardy repositories
just give a 404 error. So I enabled apport. Not sure what you need but
I've attached the log messages and the /etc/crash messages
** Attachment added: _usr_bin_gnome-keyring-daemon.1000.crash
OK here's the valgrind output, not sure if it's going to help.
** Attachment added: valgrind.log
http://launchpadlibrarian.net/13911254/valgrind.log
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete = Confirmed
--
gnome-keyring-daemon crashed with SIGSEGV
jmar71n, sorry I didn't see you post before I uploaded the valgrind. No
I'm not using a RAID, I'm actually booting off of a USB drive. The live
cd worked fine as well.
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/218434
You received this bug notification because
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
Same error here booting ubuntu from an USB-Disk. I found another way to
initiliaze with gnome-keyring:
1 - Login in text mode (ctrl+alt+f1)
2 - Run:
$ xinit -- :1
3 - Run on the new window (ctrl+alt+f9 in my case):
$ gnome-session
--
gnome-keyring-daemon crashed with SIGSEGV
Can we rename Hardy Herron to Heartless Hyena?
--
gnome-keyring-daemon crashed with SIGSEGV
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
I'm getting the same thing.
Here is the tail of my /var/log/messages:
Apr 24 11:23:09 zehel-desktop dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Apr 24 11:23:09 zehel-desktop dhcdbd: message_handler: message handler not
Ditto, exact same situation as the above - login to gdm causes it to
halt permanently on beige screen (and I can still Ctrl-Alt-F1 and log in
fine on the terminal). Log messages are also identical, so I won't
bother reposting.
I can add however that this bug reproduces on a completely new hardy
I checked out the trunk for gnome-keyring-daemon from svn.gnome.org,
installed gnome-devel and recompiled (installing with --prefix=/usr -
ugly, but not likely to break things worse than they are now!). I
restarted gdm and could now log in fine (and the daemon did not even
crash after login).
The
Same problem with all updates applied to hardy heron 8.04rc:
[ 79.911924] [drm] Initialized i915 1.6.0 20060119 on minor 0
[ 79.912922] PCI: Enabling device :00:02.1 ( - 0002)
[ 79.912936] PCI: Setting latency timer of device :00:02.1 to 64
[ 79.915050] [drm] Initialized i915
I don't know if this helps, but here's my .xsession-errors:
/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=en_US.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to
/etc/X11/xinit/xinput.d/default.
SESSION_MANAGER=local/ubuntu:/tmp/.ICE-unix/5313
I can confirm this bug. Just installed Hardy on SDHC card of Asus eee
pc. Have to launch virtual terminal to get to desktop.
/var/log/messages shows:
[ 685.989640] gnome-keyring-d[10185]: segfault at 0014 eip 080759c7 esp
bfa29ab0 error 6
[ 686.809061] gnome-keyring-d[10250]: segfault at
I confirm this on my desktop, however not my laptop running the same
version, both with all updates.
i have been logging in fine, however now i look at dmesg and i see
gnome-keyring-d segfault...
no graphical login is possible, however i can login via Ctrl+Alt+F1
--
gnome-keyring-daemon
** Attachment added: dmesg
http://launchpadlibrarian.net/13530050/dmesg
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/13530051/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/13530052/Dependencies.txt
** Attachment added:
82 matches
Mail list logo
