gnome-keyring-daemon crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Keyring |
Fix Released
|
Critical
|
|||
gnome-keyring (Ubuntu) |
Fix Released
|
Medium
|
Sebastien Bacher | ||
Lucid |
Fix Released
|
Medium
|
Sebastien Bacher |
Bug Description
Binary package hint: gnome-keyring
I just change my password
ProblemType: Crash
Architecture: i386
Date: Sun Feb 21 19:18:32 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha i386 (20100213)
Package: gnome-keyring 2.29.90git20100
ProcCmdline: /usr/bin/
ProcEnviron:
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x806b763: mov 0x8(%eax),%eax
PC (0x0806b763) ok
source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-keyring
StacktraceTop:
?? ()
?? ()
?? () from /lib/libglib-
g_main_
?? () from /lib/libglib-
Title: gnome-keyring-
Uname: Linux 2.6.32-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Related branches
Changed in gnome-keyring (Ubuntu): | |
importance: | Undecided → Medium |
tags: | removed: need-i386-retrace |
visibility: | private → public |
Changed in gnome-keyring (Ubuntu Lucid): | |
assignee: | Ubuntu Desktop Bugs (desktop-bugs) → Sebastien Bacher (seb128) |
Changed in gnome-keyring: | |
importance: | Unknown → Critical |
status: | Unknown → Fix Released |
Thank you for your bug report and helping to make Ubuntu better. We are only able to remove your passwords from the attached files. There is a password in the comment by apport, and as we continue with this bug report, there will be a few others who will be accessing this bug (as developers and bug triagers), before we can get the comment removed. Although the password is safe with the individuals who will be accessing it, it is highly recommended that you change your password anyways. We look forward to your future bug reports.