Description of problem: If I start mscore, doing nothing (not opening some score) and the exiting mscore by file menu lets mscore crash (as reported in the notification area). gdb: gdb /usr/bin/mscore GNU gdb (GDB) Fedora 7.11.1-75.fc24 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/mscore...Reading symbols from /usr/bin/mscore...(no debugging symbols found)...done. (no debugging symbols found)...done. Missing separate debuginfos, use: dnf debuginfo-install mscore-2.0.3-3.fc24.x86_64 (gdb) run Starting program: /usr/bin/mscore [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffd927c700 (LWP 16648)] [New Thread 0x7fffd1112700 (LWP 16649)] [New Thread 0x7fffd0911700 (LWP 16650)] [New Thread 0x7fffcbfff700 (LWP 16651)] [New Thread 0x7fffcb06c700 (LWP 16652)] QDir::mkpath: Empty or null file name QDir::mkpath: Empty or null file name QDir::mkpath: Empty or null file name QDir::mkpath: Empty or null file name [New Thread 0x7fffbffff700 (LWP 16654)] [New Thread 0x7fffbf7fe700 (LWP 16655)] [New Thread 0x7fffbeffd700 (LWP 16656)] [New Thread 0x7fffbe7fc700 (LWP 16657)] [New Thread 0x7fffb198a700 (LWP 16658)] [Thread 0x7fffbeffd700 (LWP 16656) exited] [Thread 0x7fffbffff700 (LWP 16654) exited] Thread 6 "QDBusConnection" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffcb06c700 (LWP 16652)] 0x00007ffff1c5d88d in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /lib64/libQt5Core.so.5 (gdb) bt #0 0x00007ffff1c5d88d in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () at /lib64/libQt5Core.so.5 #1 0x00007fffdbaddd30 in QDBusConnectionPrivate::closeConnection() () at /lib64/libQt5DBus.so.5 #2 0x00007fffdbace4d2 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #3 0x00007ffff1a9503a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #4 0x00007ffff5f9d5ca in start_thread () at /lib64/libpthread.so.0 #5 0x00007ffff1192ead in clone () at /lib64/libc.so.6 Version-Release number of selected component (if applicable): mscore-2.0.3-3.fc24.x86_64 How reproducible: always Steps to Reproduce: 1.See description 2. 3. Actual results: Crash Expected results: no crash Additional info:
Created attachment 1191753 [details] Test to open the mscore and execute a tablature
Probable duplicates: bug 1336203, bug 1352381, and bug 1364759.
See also bug 1330173.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
seems to be fixed in F26!
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.