Bug 2112810 - Pidgin crashes when trying to remove a channel: (pidgin) crashed in g_malloc0()
Summary: Pidgin crashes when trying to remove a channel: (pidgin) crashed in g_malloc0()
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pidgin
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2144929 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-01 08:10 UTC by Jarek Prokop
Modified: 2022-12-20 01:28 UTC (History)
3 users (show)

Fixed In Version: pidgin-2.14.10-3.fc38 pidgin-2.14.10-3.fc37
Clone Of:
Environment:
Last Closed: 2022-12-12 23:31:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Coredump backtrace obtained by `bt f` (32.32 KB, text/plain)
2022-08-01 08:10 UTC, Jarek Prokop
no flags Details

Description Jarek Prokop 2022-08-01 08:10:52 UTC
Created attachment 1900478 [details]
Coredump backtrace obtained by `bt f`

Description of problem:
Pidgin crashes when I try to close a chat in the conversation window.

Version-Release number of selected component (if applicable):
pidgin-2.14.10-2.fc37.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Open Pidgin channels
2. Close any channel
3. observe the error/crash

Actual results:
Pidgin crashes

Expected results:
Pidgin lets me close any chat without crashes

Additional info:
backtrace from ABRT in journal:
```
pidgin killed by SIGTRAP
#1 [libglib-2.0.so.0] g_malloc0
#2 [libglib-2.0.so.0] g_hash_table_resize
#3 [libglib-2.0.so.0] g_hash_table_destroy
#4 [pidgin] gtk_imhtml_finalize
#5 [libgtk-x11-2.0.so.0] gtk_text_view_set_buffer
```

Not sure if relevant, but I am running it on Wayland using Sway WM NVR: sway-1.7-3.fc37.x86_64

Comment 1 Ben Cotton 2022-08-09 13:23:31 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

Comment 2 Jarek Prokop 2022-12-10 12:15:28 UTC
This is a problem with using the default spellchk plugin, being connected to multiple channels and then disconnecting from one of them.

Upstream seems to have a fix, see:
Upstream ticket: https://issues.imfreedom.org/issue/PIDGIN-17702/
Upstream review: https://reviews.imfreedom.org/r/1951/diff/2/
Upstream commit: https://keep.imfreedom.org/pidgin/pidgin/rev/bf6049713e98

I have verified the fix for me using the upstream patch in copr: https://copr.fedorainfracloud.org/coprs/jackorp/pidgin_spellchk/ 

I made a PR with the fix: https://src.fedoraproject.org/rpms/pidgin/pull-request/4

Comment 3 Fedora Update System 2022-12-12 23:28:08 UTC
FEDORA-2022-5dcfa2a425 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5dcfa2a425

Comment 4 Fedora Update System 2022-12-12 23:31:09 UTC
FEDORA-2022-5dcfa2a425 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2022-12-13 00:36:36 UTC
FEDORA-2022-da20dfbcfb has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-da20dfbcfb

Comment 6 Fedora Update System 2022-12-14 02:09:06 UTC
FEDORA-2022-da20dfbcfb has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-da20dfbcfb`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-da20dfbcfb

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

Comment 7 Michael Catanzaro 2022-12-19 17:52:57 UTC
*** Bug 2144929 has been marked as a duplicate of this bug. ***

Comment 8 Fedora Update System 2022-12-20 01:28:31 UTC
FEDORA-2022-da20dfbcfb has been pushed to the Fedora 37 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.