Bug 2267822

Summary:	Closing frozen bubble crashes gnome
Product:	[Fedora] Fedora	Reporter:	romulasry
Component:	frozen-bubble	Assignee:	David King <amigadave>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	amigadave, hdegoede, kparal
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-03-11 13:08:25 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:

Description romulasry 2024-03-04 21:55:25 UTC

Crashes rawhide Mon Mar 1th 1:55PM

Reproducible: Always

Steps to Reproduce:
1.Open Frozen bubble
2. Close it via the X
3. Crashes
Actual Results:  
Crashes

Expected Results:  
Exits cleanly

Comment 1 Hans de Goede 2024-03-06 13:32:47 UTC

I think this may be a duplicate of bug 2265402.

Does the crash happen every time you close Frozen bubble?

Can you run "journalctl --user" after reproducing the crash and then see if you have a
"libmutter:ERROR:../src/x11/group.c:76:meta_group_new: assertion failed: (g_hash_table_lookup (x11_display->groups_by_leader, &group_leader) == NULL)"

message in there ?

Comment 2 romulasry 2024-03-06 23:11:04 UTC

journalctl --user
Jan 22 13:35:45 fedora systemd[1031]: Queued start job for default target defau>
Jan 22 13:35:45 fedora systemd[1031]: Created slice app.slice - User Applicatio>
Jan 22 13:35:45 fedora systemd[1031]: Started grub-boot-success.timer - Mark bo>
Jan 22 13:35:45 fedora systemd[1031]: Started systemd-tmpfiles-clean.timer - Da>
Jan 22 13:35:45 fedora systemd[1031]: Reached target paths.target - Paths.
Jan 22 13:35:45 fedora systemd[1031]: Reached target timers.target - Timers.
Jan 22 13:35:46 fedora dbus-broker-launch[1051]: Policy to allow eavesdropping >
Jan 22 13:35:46 fedora dbus-broker-launch[1051]: Policy to allow eavesdropping >
Jan 22 13:35:45 fedora systemd[1031]: Starting dbus.socket - D-Bus User Message>
Jan 22 13:35:45 fedora systemd[1031]: Listening on pipewire-pulse.socket - Pipe>
Jan 22 13:35:45 fedora systemd[1031]: Listening on pipewire.socket - PipeWire M>
Jan 22 13:35:45 fedora systemd[1031]: Starting systemd-tmpfiles-setup.service ->
Jan 22 13:35:45 fedora systemd[1031]: Listening on dbus.socket - D-Bus User Mes>
Jan 22 13:35:45 fedora systemd[1031]: Reached target sockets.target - Sockets.
Jan 22 13:35:45 fedora systemd[1031]: Finished systemd-tmpfiles-setup.service ->
Jan 22 13:35:45 fedora systemd[1031]: Reached target basic.target - Basic Syste>
Jan 22 13:35:45 fedora systemd[1031]: Reached target default.target - Main User>
Jan 22 13:35:45 fedora systemd[1031]: Startup finished in 565ms.
Jan 22 13:35:45 fedora systemd[1031]: Created slice session.slice - User Core S>
Jan 22 13:35:45 fedora systemd[1031]: Starting dbus-broker.service - D-Bus User>
Jan 22 13:35:45 fedora systemd[1031]: Started dbus-broker.service - D-Bus User >
Jan 22 13:35:45 fedora dbus-broker-launch[1051]: Ready

Comment 3 Kamil Páral 2024-03-11 13:08:25 UTC

I can reproduce this consistently. A full backtrace is in bug 2268998. Let's close this one as a duplicate of bug 2268998, because it has better info.

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