Bug 1319341 - Crash when creating new keyring (possibly only with empty password) in live session
Summary: Crash when creating new keyring (possibly only with empty password) in live s...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: seahorse
Version: 24
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-18 21:46 UTC by Adam Williamson
Modified: 2017-08-08 13:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 13:59:13 UTC
Type: Bug


Attachments (Terms of Use)

Description Adam Williamson 2016-03-18 21:46:55 UTC
Steps that produced the crash: boot the F24 Alpha 1.5 Workstation x86_64 live in a KVM. See that there were a couple of crashes in abrt, go to report one. During the process, it asks for a Bugzilla username / password. When I enter one, a pop-up tells me GNOME's creating a keyring and asks for a password. I leave the password blank and hit OK, then (IIRC) click through a warning about not setting a password. Shortly after that, I see a crash notification from seahorse.

abrt refuses to report the crash because "The process has locked memory which usually indicates efforts to protect sensitive data (passwords) from being written to disk", which sounds about right. I can obtain a backtrace manually and send it by email if desired, I guess.

The BZ password did seem to be stored and re-used for a second report submission, so it seems like the crash didn't prevent the keyring actually being created and the password saved.

Comment 1 Adam Williamson 2016-03-18 21:47:39 UTC
Another seahorse crash showed up after I quit abrt and reloaded it, too.

Comment 2 Fedora End Of Life 2017-07-25 20:21:30 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-08-08 13:59:13 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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