Bug 1746655 - gtkhash doesn't exit cleanly
Summary: gtkhash doesn't exit cleanly
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gtkhash
Version: 31
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Mukundan Ragavan
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-29 04:43 UTC by Ian Laurie
Modified: 2020-11-24 20:10 UTC (History)
3 users (show)

Fixed In Version: gtkhash-1.2-1.fc30 gtkhash-1.2-1.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-24 20:10:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
gdb backtrace (11.50 KB, text/plain)
2019-09-14 14:05 UTC, Chris Tao
no flags Details

Description Ian Laurie 2019-08-29 04:43:44 UTC
Description of problem:
When you quit gtkhash there is a notification indicating gtkhash crashed, and gnome-abrt also reports a gtkhash crash.

Version-Release number of selected component (if applicable):
gtkhash-1.1.1-4.fc30.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Launch gtkhash
2. Quit from gtkhash
3.

Actual results:
Notification indicating gtkhash has crashed.

Expected results:
Should exit cleanly.

Additional info:
Have the issue on two up-to-date Fedora 30 systems, both running Xfce.

Comment 1 Ian Laurie 2019-08-29 05:06:15 UTC
In Rawhide gtkhash-1.1.1-5.fc31.x86_64 has the same problem.

Comment 2 Fedora Update System 2019-09-03 16:11:17 UTC
FEDORA-2019-bd8971882e has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-bd8971882e

Comment 3 Fedora Update System 2019-09-03 16:11:21 UTC
FEDORA-2019-26d11fa5f7 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-26d11fa5f7

Comment 4 Fedora Update System 2019-09-03 18:46:08 UTC
gtkhash-1.2-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-26d11fa5f7

Comment 5 Fedora Update System 2019-09-04 04:58:12 UTC
gtkhash-1.2-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-bd8971882e

Comment 6 Ian Laurie 2019-09-05 01:12:11 UTC
For me on Xfce updated gtkhash-1.2-1.fc30.x86_64 on Fedora 30 still has the issue.

Also for me the updated gtkhash-1.2-1.fc32.x86_64 on Fedora Rawhide (identifying now as F32) still has the issue (also on Xfce).

Both systems tested with all updates applied as of this time

Comment 7 Fedora Update System 2019-09-11 19:24:09 UTC
gtkhash-1.2-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Ian Laurie 2019-09-11 22:21:10 UTC
As stated in Comment 6 this isn't fixed for me.

Comment 9 Fedora Update System 2019-09-14 00:09:27 UTC
gtkhash-1.2-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.

Comment 10 Chris Tao 2019-09-14 08:03:07 UTC
gtkhash-1.2-1.fc30 still crashes on exit. Strangely, it does not crash in Gnome.

Comment 11 Mukundan Ragavan 2019-09-14 12:18:48 UTC
Unfortunately, I cannot reproduce the crash. I will file this upstream.

Comment 12 Mukundan Ragavan 2019-09-14 12:19:23 UTC
Any chance there is a stack trace available for the crash?

Comment 13 Chris Tao 2019-09-14 14:05:28 UTC
Created attachment 1615137 [details]
gdb backtrace

Comment 14 Fedora Update System 2019-09-14 16:33:07 UTC
gtkhash-1.2-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.

Comment 15 Ian Laurie 2020-02-13 07:40:41 UTC
I am not seeing this issue currently on Rawhide with gtkhash-1.2-2.fc32.x86_64, however the problem persists in Fedora 31 gtkhash-1.2-1.fc31.x86_64.

Comment 16 Ben Cotton 2020-11-03 17:13:02 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-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 '31'.

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 31 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 17 Ben Cotton 2020-11-24 20:10:07 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.