Bug 2124341

Summary: gnome-shell crashes when closing pidgin
Product: [Fedora] Fedora Reporter: Pablo Greco <pablo>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 37CC: adscvr, fmuellner, gnome-sig, jadahl, kparal, mironov.ivan, otaylor, philip.wyett
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-26 20:18:46 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
backtrace
none
journalctl from the pid none

Description Pablo Greco 2022-09-05 18:16:02 UTC
Description of problem:
In branched 37, beta 1.4, closing pidgin crashes gnome-shell (and with it, the whole session because of wayland)

Version-Release number of selected component (if applicable):
gnome-shell-43~beta-3.fc37.x86_64
gnome-shell-extension-appindicator-42-3.fc37.noarch


How reproducible:
Always in my setup, haven't tested in others

Steps to Reproduce:
1. have gnome-shell-extension-appindicator installed and enabled
2. run pidgin (in my case, open libera)
3. Close pidgin, either from the appindicator icon or from Quit in the menu

Actual results:
gnome-shell crashes (SIGABRT) and the session is closed


Expected results:
Pidgin is closed without issues

Additional info:

Comment 1 Jonas Ådahl 2022-09-06 10:31:00 UTC
Can you attach a debug backtrace? Do so by running

sudo dnf install gdb
sudo dnf debuginfo-install mutter gnome-shell glib2 gjs
coredumpctl gdb -r gnome-shell

then in the (gdb) prompt run

backtrace full

then attach the output as a file here.

Comment 2 Pablo Greco 2022-09-06 11:49:38 UTC
Created attachment 1909769 [details]
backtrace

This backtrace is from yesterday's crash, let me know if that's ok or if you want me to generate it again

Comment 3 Jonas Ådahl 2022-09-06 11:56:46 UTC
Looks like https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5832. Can you see if you can find the journal logs from gnome-shell from when the crash happened?

If you look up the pid from coredumpctl, it might be available if you do

    journalctl _PID=pid-of-gnome-shell

Comment 4 Pablo Greco 2022-09-06 12:09:57 UTC
Created attachment 1909772 [details]
journalctl from the pid

Indeed it looks like the same thing

Clutter:ERROR:../clutter/clutter/clutter-actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_children < prev_n_children)

Comment 5 Pablo Greco 2022-09-06 12:42:03 UTC
Jonas, I have a feeling (but absolutely no evidence) that this might be related https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/294 , since pidgin is also what triggers that problem for me.

Comment 6 Jonas Ådahl 2022-09-06 13:17:34 UTC
(In reply to Pablo Greco from comment #5)
> Jonas, I have a feeling (but absolutely no evidence) that this might be
> related
> https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/294 ,
> since pidgin is also what triggers that problem for me.

I have no idea, but if this is something you can reproduce, there seems to be a potential fix available if you install the extension from one of the commenters.

Comment 7 Pablo Greco 2022-09-07 16:58:56 UTC
Just confirmed that updating gnome-shell-extension-appindicator to the code in the "ubuntu/jammy" branch makes the crash disappear

Comment 8 Kamil Páral 2022-09-21 05:52:05 UTC
Possibly related? https://bugzilla.redhat.com/show_bug.cgi?id=2127826

Comment 9 Jonas Ådahl 2022-09-21 07:39:51 UTC
(In reply to Kamil Páral from comment #8)
> Possibly related? https://bugzilla.redhat.com/show_bug.cgi?id=2127826

Probably the same.

Comment 10 Pablo Greco 2023-02-26 20:18:46 UTC
Fixed a long time ago, closing

*** This bug has been marked as a duplicate of bug 2127826 ***