| Summary: | [abrt] gnome-keyring-2.32.1-1.fc14: on_io_completed: Process /usr/bin/gnome-keyring-daemon was killed by signal 6 (SIGABRT) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | kxra | ||||
| Component: | gnome-keyring | Assignee: | Tomáš Bžatek <tbzatek> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14 | CC: | emanmc, liana, oleg, tbzatek, tsmetana, walters | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:af8cb8b6be190d90b07f199e198689f73a4ae63c | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-03-21 15:22:25 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
kxra
2011-06-05 15:31:25 UTC
Created attachment 503100 [details]
File: backtrace
Package: gnome-keyring-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.?? 2. 3. Package: gnome-keyring-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Nothing 2. Nothing 3. Nothing Package: gnome-keyring-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I have no idea. (I only first saw the crash notice more than a week after it happened). 2. 3. Backtrace analysis found this bug to be similar to bug #656475, closing as duplicate. Bugs which were found to be similar to this bug: bug #655235, bug #656475 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 656475 *** |