Bug 2427899

Summary: [abrt] [faf] nheko: __pthread_kill_implementation(): /usr/bin/nheko killed by 6
Product: [Fedora] Fedora Reporter: Dominik 'Rathann' Mierzejewski <dominik>
Component: nhekoAssignee: Dominik 'Rathann' Mierzejewski <dominik>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 42CC: dominik, yselkowi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/6f6dc7368c7fbc1102e28b8baf31c03642844427/
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-03-10 00:16:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2443507    
Bug Blocks:    

Description Dominik 'Rathann' Mierzejewski 2026-01-08 11:58:17 UTC
This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: https://retrace.fedoraproject.org/faf/reports/bthash/6f6dc7368c7fbc1102e28b8baf31c03642844427/

Reproducible: Always

Steps to Reproduce:
1. Start nheko.
2. Wait for conversations to sync.
3. Exit/close nheko.
Actual Results:
Crashes on exit.

Expected Results:
No crash.

Comment 1 Dominik 'Rathann' Mierzejewski 2026-03-01 22:41:36 UTC
This is fixed by updating coeurl to 0.3.2.

Comment 2 Fedora Update System 2026-03-01 23:07:13 UTC
FEDORA-2026-e13f857e4f (coeurl-0.3.2-2.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-e13f857e4f

Comment 3 Fedora Update System 2026-03-01 23:07:13 UTC
FEDORA-2026-5ba3a6084d (coeurl-0.3.2-2.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-5ba3a6084d

Comment 4 Fedora Update System 2026-03-02 01:22:43 UTC
FEDORA-2026-e13f857e4f has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-e13f857e4f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-e13f857e4f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2026-03-02 01:40:52 UTC
FEDORA-2026-5ba3a6084d has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-5ba3a6084d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-5ba3a6084d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2026-03-02 02:03:27 UTC
FEDORA-2026-87234683f9 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-87234683f9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-87234683f9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2026-03-10 00:16:38 UTC
FEDORA-2026-87234683f9 (coeurl-0.3.2-2.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2026-03-10 00:54:07 UTC
FEDORA-2026-e13f857e4f (coeurl-0.3.2-2.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2026-03-10 01:10:23 UTC
FEDORA-2026-5ba3a6084d (coeurl-0.3.2-2.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.