Bug 1596781

Summary: at-spi2-launcher crashed in name_appeared_handler()
Product: [Fedora] Fedora Reporter: Loye Young <loye.young>
Component: at-spi2-coreAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: mclasen, tiagomatos
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-05-28 20:48:05 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:
Attachments:
Description Flags
Excerpt from /var/log/messages: grep -e "atspi\|at-spi" /var/log/messages | grep "Jun 28"
none
Environment variables
none
User Environment Variables
none
ABRT details none

Description Loye Young 2018-06-29 17:38:07 UTC
Created attachment 1455539 [details]
Excerpt from /var/log/messages: grep -e "atspi\|at-spi" /var/log/messages | grep "Jun 28"

Description of problem:
ABRT reports frequently a crash in at-spi2-core. 

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

# dnf info --installed at-spi* atspi* | grep -e "Name\|Version\|Release\|Arch\|"
Installed Packages
Name         : at-spi2-atk
Version      : 2.26.2
Release      : 1.fc28
Arch         : x86_64

Name         : at-spi2-core
Version      : 2.28.0
Release      : 1.fc28
Arch         : x86_64


How reproducible:
Seemingly random. 

Steps to Reproduce:
1. Log onto desktop.
2. Start doing stuff.
3. ABRT generates crash report, but core dump is unusable.

Actual results:


Expected results:


Additional info:

Comment 1 Loye Young 2018-06-29 17:49:27 UTC
Created attachment 1455541 [details]
Environment variables

Comment 2 Loye Young 2018-06-29 17:53:03 UTC
Created attachment 1455542 [details]
User Environment Variables

Comment 3 Loye Young 2018-06-29 18:05:35 UTC
Created attachment 1455543 [details]
ABRT details

Comment 4 Ben Cotton 2019-05-02 21:30:39 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 5 Ben Cotton 2019-05-28 20:48:05 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.