Bug 641469 - [abrt] gnome-keyring-2.32.0-1.fc14: raise: Process /usr/bin/gnome-keyring-daemon was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-keyring-2.32.0-1.fc14: raise: Process /usr/bin/gnome-keyring-dae...
Keywords:
Status: CLOSED DUPLICATE of bug 610303
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-keyring
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:64b4e8095b493dc95238d38bfc5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-08 19:25 UTC by Adam Williamson
Modified: 2015-03-03 22:53 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-09 16:06:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (16.78 KB, text/plain)
2010-10-08 19:25 UTC, Adam Williamson
no flags Details

Description Adam Williamson 2010-10-08 19:25:12 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/gnome-keyring-daemon --start --components=pkcs11
comment: Happened on boot. It seems intermittent - it doesn't happen every boot. I have auto-login enabled via gdm, so when it logs in, I am prompted for my password to unlock the keyring. It prompts me three times usually (which in itself sucks, it should prompt once and apply the password to each operation). It crashes after, IIRC, the second time I enter the password.
component: gnome-keyring
crash_function: raise
executable: /usr/bin/gnome-keyring-daemon
kernel: 2.6.36-0.20.1.rc3.git4.fc14.x86_64
package: gnome-keyring-2.32.0-1.fc14
rating: 4
reason: Process /usr/bin/gnome-keyring-daemon was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1286565695
uid: 501

Comment 1 Adam Williamson 2010-10-08 19:25:14 UTC
Created attachment 452420 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 16:06:53 UTC

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

Comment 3 Karel Klíč 2010-11-09 16:06:53 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #610303.

Sorry for the inconvenience.


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