Bug 2480663

Summary:	Application shows splash screen, but doesn't open after that.
Product:	[Fedora] Fedora	Reporter:	Doczek <dokmiada>
Component:	musescore	Assignee:	Jerry James <loganjerry>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	44	CC:	loganjerry
Target Milestone:	---	Keywords:	Desktop, Regression
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-05-23 13:20: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 Doczek 2026-05-22 00:09:02 UTC

When opening MuseScore, no actual applicatio opens after the splash screen shows and disappears.

Reproducible: Always

Steps to Reproduce:
1. Open MuseScore from the application menu.
2. Observe the splash screen.
Actual Results:
Main MuseScore window doesn't open.

Expected Results:
Main MuseScore window opens.

Additional Information:
Running `sudo dnf downgrade musescore` brought it back to a version which opened successfuly.

Comment 1 Jerry James 2026-05-22 02:44:33 UTC

Yes, things are not happy in musescore-land right now.  We had a bug in Qt 6.10.3 that prevented even the splash screen from starting up.  That was just fixed a short time ago, and now MuseScore segfaults on startup.  Rather than try to figure out the cause of the segfault, I would prefer to move to version 4.7.1 and see if it behaves better.  I needed two new packages to do that.  The first (json-schema-validator) passed review and was built for Fedora about 12 hours ago.  The second still needs a review: mnxdom, bug 2477713.  If you are a packager, you could help things along by doing the package review.  Otherwise, I will try to find someone to do it tomorrow.

Comment 2 Jerry James 2026-05-23 13:20:25 UTC

This turns out to be the same as bug 2457799.  Please follow along in that bug instead.

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