Bug 678491 - [abrt] gnome-keyring-2.32.1-1.fc14: Process /usr/bin/gnome-keyring-daemon was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-keyring-2.32.1-1.fc14: Process /usr/bin/gnome-keyring-daemon was...
Keywords:
Status: CLOSED DUPLICATE of bug 657095
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-keyring
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:57ddf21a964f3eb2e67b665cffb...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-18 08:55 UTC by Alex Wajda
Modified: 2015-03-03 22:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 16:55:38 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (16.48 KB, text/plain)
2011-02-18 08:55 UTC, Alex Wajda
no flags Details

Description Alex Wajda 2011-02-18 08:55:44 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/gnome-keyring-daemon --start --components=pkcs11
component: gnome-keyring
executable: /usr/bin/gnome-keyring-daemon
kernel: 2.6.35.11-83.fc14.x86_64
package: gnome-keyring-2.32.1-1.fc14
reason: Process /usr/bin/gnome-keyring-daemon was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1298018816
uid: 500

How to reproduce
-----
1. Boot the system up
2. Log into Gnome profile using the fingerprint reader
3. Gnome key-ring pop up appeared and crashed

Comment 1 Alex Wajda 2011-02-18 08:55:47 UTC
Created attachment 479466 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-20 16:55:38 UTC
Backtrace analysis found this bug to be similar to bug #657095, closing as duplicate.

Bugs which were found to be similar to this bug: bug #638631, bug #641469, bug #643281, bug #643569, bug #650080, bug #655300, bug #657095, bug #701219

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 657095 ***


Note You need to log in before you can comment on or make changes to this bug.