** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
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
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
https://bugs.launch
*** This bug is a duplicate of bug 218434 ***
https://bugs.launchpad.net/bugs/218434
** This bug has been marked a duplicate of bug 218434
gnome-keyring-daemon crashed with SIGSEGV
--
Ubuntu 8.04 gnome-keyring-daemon closed unexpectedly
https://bugs.launchpad.net/bugs/221720
You received
*** This bug is a duplicate of bug 218434 ***
https://bugs.launchpad.net/bugs/218434
** This bug has been marked a duplicate of bug 218434
gnome-keyring-daemon crashed with SIGSEGV
--
Blank screen After Login from Gdm
https://bugs.launchpad.net/bugs/221850
You received this bug notificati
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 t
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
[ 451.
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
