Bug 1694832

Summary:	Seahorse Segmentation Faults After Updating Default Password
Product:	[Fedora] Fedora	Reporter:	Richard Myers <rmm>
Component:	seahorse	Assignee:	Matthias Clasen <mclasen>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	29	CC:	debarshir, gnome-sig, mclasen, stefw
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-27 21:47:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Richard Myers 2019-04-01 19:32:24 UTC

Description of problem:
Seahorse segmentation faults after updating the default password.
[rmm@crank ~] $ seahorse
Segmentation fault (core dumped)

Version-Release number of selected component (if applicable):

seahorse-3.30.1.1-1.fc29.x86_64

How reproducible:

Every time.

Steps to Reproduce:
1. Open Seahorse
2. Right-click on Default Keyring, and select 'Change Password'.
3. Go through the steps... (Old PW, then new, then confirm)
4. Tapping 'Continue' after filling out the form in 3. leads to the Seg fault.

Also: I just cancelled out of the PW change at either step and still got the seg fault. Easy to reproduce.

Actual results:

Segmentation fault

Expected results:

Return to Seahorse GUI after updating the PW.

Additional info:

I just updated a bunch of packages that came out today related to sssd and nss.

Name : seahorse
Version : 3.30.1.1
Release : 1.fc29
Architecture: x86_64
Install Date: Sat 19 Jan 2019 03:04:30 AM PST
Group : Unspecified
Size : 6983659
License : GPLv2+ and LGPLv2+
Signature : RSA/SHA256, Wed 19 Dec 2018 04:20:58 AM PST, Key ID a20aa56b429476b4
Source RPM : seahorse-3.30.1.1-1.fc29.src.rpm
Build Date : Tue 18 Dec 2018 08:07:15 AM PST
Build Host : buildvm-31.phx2.fedoraproject.org
Relocations : (not relocatable)
Packager : Fedora Project
Vendor : Fedora Project
URL : https://wiki.gnome.org/Apps/Seahorse
Bug URL : https://bugz.fedoraproject.org/seahorse
Summary : A GNOME application for managing encryption keys
Description :
Seahorse is a graphical interface for managing and using encryption keys.
It also integrates with nautilus, gedit and other places for encryption
operations. It is a keyring manager.

Comment 1 Ben Cotton 2019-10-31 19:40:58 UTC

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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 2 Ben Cotton 2019-11-27 21:47:14 UTC

Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.