musescore/MuseScore

Crash when accessing OS file dialog (Linux)

Open

#25,349 opened on Oct 28, 2024

View on GitHub
 (11 comments) (1 reaction) (4 assignees)C++ (11,122 stars) (2,432 forks)batch import
communitycrashhelp wantedneeds infoos: linuxregression MS4

Description

Issue type

Crash or freeze

Description with steps to reproduce

  1. Start AppImage from the command line
  2. Choose File | Open
  3. Musescore crashes without showing a file dialog

Expected behaviour: it should show a file dialog

Supporting files, videos and screenshots

MuseScore_241028_154448.log

https://github.com/user-attachments/assets/6ce830bd-e7f8-4f39-8582-5d9b244bc907

What is the latest version of MuseScore Studio where this issue is present?

4.4.3

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

Manjaro Linux, Cinnamon Desktop

Additional context

I’ve previously used the package from the official repo (i.e. the Arch package), but it’s currently at version 4.3.2. I’ve also used the Flatpak version (currently 4.4.2), which generally works fine, but does not export SVG correctly. It was after noticing this problem that I tried the AppImage which crashed when I tried to export. If you re-open a file from the main window, no file dialog is required.

Checklist

  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Contributor guide

Tech stack
cpp
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C++ experienceLinux GUI developmentDebugging skills
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the crash when opening file dialog on Linux. Start by examining the attached log file (MuseScore 241028 154448.log) for crash details. Look at the code that handles file opening on Linux, particularly the integration with the system file dialog. Compare with previous working version to identify what changed.