Bug 675393 - [abrt] gnome-keyring-2.91.4-5.fc15: Process /usr/libexec/gnome-keyring-prompt-3 was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-keyring-2.91.4-5.fc15: Process /usr/libexec/gnome-keyring-prompt...
Keywords:
Status: CLOSED DUPLICATE of bug 745662
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-keyring
Version: rawhide
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:eac84ceade471647ab8e5d6cd8d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-05 11:29 UTC by Alexander Ivanov
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-21 16:31:08 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (15.30 KB, text/plain)
2011-02-05 11:29 UTC, Alexander Ivanov
no flags Details

Description Alexander Ivanov 2011-02-05 11:29:28 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gnome-keyring-prompt
component: gnome-keyring
executable: /usr/libexec/gnome-keyring-prompt-3
kernel: 2.6.38-0.rc3.git3.1.fc15.x86_64
package: gnome-keyring-2.91.4-5.fc15
reason: Process /usr/libexec/gnome-keyring-prompt-3 was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Rawhide)
time: 1296902867
uid: 500

How to reproduce
-----
1. Enable wireless network
2. Enter password 
3. Enter password in keyring-manager

Comment 1 Alexander Ivanov 2011-02-05 11:29:31 UTC
Created attachment 477184 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-21 16:31:08 UTC
Backtrace analysis found this bug to be similar to bug #745662, closing as duplicate.

Bugs which were found to be similar to this bug: 
  at-spi2-atk: bug #675392
  gnome-shell: bug #745662
  nautilus: bug #747909
  xulrunner: bug #675969

This comment is automatically generated.

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


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