Bug 2415195 - Crash on startup
Summary: Crash on startup
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: calls
Version: 43
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Tomi Lähteenmäki
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-11-15 16:35 UTC by Christian Glombek
Modified: 2025-12-05 02:11 UTC (History)
3 users (show)

Fixed In Version: calls-49.1.1-3.fc44 calls-49.1.1-4.fc43
Clone Of:
Environment:
Last Closed: 2025-12-05 02:11:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Christian Glombek 2025-11-15 16:35:42 UTC
The calls rpm crashes reproducibly on startup.

The issue has been filed upstream under https://gitlab.gnome.org/GNOME/calls/-/issues/724.
Backtraces have been provided there, too.

The Flatpak as well as local builds are not affected, so this seems to be a problem related to the RPM build alone.

Reproducible: Always

Steps to Reproduce:
1. Open Calls
2. Crash with `*** buffer overflow detected ***: terminated`

Actual Results:
Crash

Expected Results:
No crash

Comment 1 Christian Glombek 2025-12-01 11:12:09 UTC
https://gitlab.gnome.org/GNOME/calls/-/merge_requests/808 fixes it, but I haven't head back from maintainers whether porting Calls to NetworkManager is acceptable for them.

Comment 2 Fedora Update System 2025-12-01 19:11:53 UTC
FEDORA-2025-1f4aa23523 (calls-49.1.1-3.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-1f4aa23523

Comment 3 Fedora Update System 2025-12-01 19:16:14 UTC
FEDORA-2025-1f4aa23523 (calls-49.1.1-3.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Fedora Update System 2025-12-01 19:56:11 UTC
FEDORA-2025-c248200b63 (calls-49.1.1-3.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-c248200b63

Comment 5 Tomi Lähteenmäki 2025-12-01 19:56:55 UTC
I applied the https://gitlab.gnome.org/GNOME/calls/-/merge_requests/807 until upstream comments is NetworkManager acceptable or not.

Update for F43: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c248200b63

Comment 6 Fedora Update System 2025-12-02 02:10:43 UTC
FEDORA-2025-c248200b63 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-2025-c248200b63`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c248200b63

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

Comment 7 Fedora Update System 2025-12-02 18:59:40 UTC
FEDORA-2025-618a463b98 (calls-49.1.1-4.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-618a463b98

Comment 8 Fedora Update System 2025-12-03 01:48:49 UTC
FEDORA-2025-618a463b98 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-2025-618a463b98`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-618a463b98

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

Comment 9 Tomi Lähteenmäki 2025-12-04 20:10:41 UTC
Thanks for reporting and fixing this bug!

Comment 10 Fedora Update System 2025-12-05 02:11:25 UTC
FEDORA-2025-618a463b98 (calls-49.1.1-4.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.


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