** Changed in: gnome-keyring
Importance: Unknown => Critical
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/332342
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
** Changed in: gnome-keyring
Status: Incomplete => Fix Released
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/332342
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
Let's mark this closed as well, then; it hasn't recurred for me, I can
always reopen later if I find the problem recurs.
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged => Fix Released
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/332342
You received t
dropping the milestone there has been no other bug about that recently
and upstream thinks that's fixed in the current version
** Changed in: gnome-keyring (Ubuntu)
Milestone: ubuntu-9.04-beta => None
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/332342
You rec
Steve? did you get the issue again since the update?
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/332342
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
I haven't seen this crash again. I have no idea whether that means we
should consider it fixed, since the crash only happened the one time.
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/332342
You received this bug notification because you are a member of Ubuntu
Bu
** Changed in: gnome-keyring
Status: Unknown => Incomplete
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/332342
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
could you try if that's still an issue in 2.25.92 just uploaded to
jaunty?
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/332342
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
Thanks for your bug report. This bug has been reported to the developers
of the software. You can track it and make comments here:
http://bugzilla.gnome.org/show_bug.cgi?id=573767
** Changed in: gnome-keyring (Ubuntu)
Status: New => Triaged
** Also affects: gnome-keyring via
http://bugz
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete => New
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/332342
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
the apport-retrace command appears to be broken in jaunty, but here's a
backtrace from manually unpacking the apport report and running gdb with
the dbgsym packages installed.
(gdb) thread apply all bt full
Thread 2 (process 1322):
#0 0x7f84d11b8496 in poll () from /lib/libc.so.6
No symbol t
thank you for your bug report, could you run sudo apport-retrace crash
locally (use sudo if you want it to install the dbgsym required for the
retracing) and add the debug version cleaned of privated informations to
the bug?
** Changed in: gnome-keyring (Ubuntu)
Importance: Undecided => Medium
12 matches
Mail list logo
