Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segmentation fault on Manjaro Linux after installing MuseSounds #22951

Open
Schweini07 opened this issue May 23, 2024 · 6 comments
Open

Segmentation fault on Manjaro Linux after installing MuseSounds #22951

Schweini07 opened this issue May 23, 2024 · 6 comments
Assignees
Labels
community Issues we would like the community to address crash Issues involving a crash of MuseScore os: linux Potentially specific to Linux-based operating systems

Comments

@Schweini07
Copy link

Schweini07 commented May 23, 2024

Issue type

Crash or freeze

Bug description

I've freshly downloaded MuseScore from pacman, and after working on a piece for a while I wanted to get MuseSounds for a piano to properly play staccato notes.
After the installation I wasn't able to start MuseScore anymore though, and after running it through the terminal it seems like a segfault is the culprit here.

Steps to reproduce

  1. Download MuseScore from the official repositories via pacman
  2. Install MuseSound Manager from AUR
  3. Install Keys sound suite
  4. Try to start Musescore

Screenshots/Screen recordings

No response

MuseScore Version

MuseScore4 4.2.1

Regression

I don't know

Operating system

Manjaro Linux

Additional context

I ran the core file with gdb, to look at the backtrace, but I don't think I can provide much more info. If there is still anything I can provide, please do tell.
bt:

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f37bfb09af1 in ms_InstrumentList_get_next () from /home/laurenz/.local/share/MuseSampler/lib/libMuseSamplerCoreLib.so
[Current thread is 1 (Thread 0x7f37f1dfb6c0 (LWP 16757))]
(gdb) bt
#0  0x00007f37bfb09af1 in ms_InstrumentList_get_next () at /home/laurenz/.local/share/MuseSampler/lib/libMuseSamplerCoreLib.so
#1  0x000055c5d9fbd1f9 in ??? ()
#2  0x000055c5d952963d in ??? ()
#3  0x000055c5d9575633 in ??? ()
#4  0x000055c5d958bd5e in ??? ()
#5  0x000055c5d8e86da4 in ??? ()
#6  0x000055c5d8e941ca in ??? ()
#7  0x000055c5d8b3d6a6 in ??? ()
#8  0x00007f38236dcb63 in std::execute_native_thread_routine (__p=0x55c5de106690) at /usr/src/debug/gcc/gcc/libstdc++-v3/src/c++11/thread.cc:104
#9  0x00007f3824f3d1cf in ??? () at /usr/lib/libc.so.6
#10 0x00007f3824fbe6ec in ??? () at /usr/lib/libc.so.6

bt full:

#0  0x00007f37bfb09af1 in ms_InstrumentList_get_next () at /home/laurenz/.local/share/MuseSampler/lib/libMuseSamplerCoreLib.so
#1  0x000055c5d9fbd1f9 in ??? ()
#2  0x000055c5d952963d in ??? ()
#3  0x000055c5d9575633 in ??? ()
#4  0x000055c5d958bd5e in ??? ()
#5  0x000055c5d8e86da4 in ??? ()
#6  0x000055c5d8e941ca in ??? ()
#7  0x000055c5d8b3d6a6 in ??? ()
#8  0x00007f38236dcb63 in std::execute_native_thread_routine (__p=0x55c5de106690) at /usr/src/debug/gcc/gcc/libstdc++-v3/src/c++11/thread.cc:104
        __t = std::unique_ptr<std::thread::_State> = {get() = <optimized out>}
#9  0x00007f3824f3d1cf in ??? () at /usr/lib/libc.so.6
#10 0x00007f3824fbe6ec in ??? () at /usr/lib/libc.so.6

info threads:

  Id   Target Id                         Frame 
* 1    Thread 0x7f37f1dfb6c0 (LWP 16757) 0x00007f37bfb09af1 in ms_InstrumentList_get_next () from /home/laurenz/.local/share/MuseSampler/lib/libMuseSamplerCoreLib.so
  2    Thread 0x7f381f1356c0 (LWP 16739) 0x00007f3824fb09ed in poll () from /usr/lib/libc.so.6
  3    Thread 0x7f381f759940 (LWP 16738) 0x00007f3824f4d0ca in ?? () from /usr/lib/libc.so.6
  4    Thread 0x7f381cc9f6c0 (LWP 16741) 0x00007f3824fbc48d in syscall () from /usr/lib/libc.so.6
  5    Thread 0x7f38027fc6c0 (LWP 16748) 0x00007f3824f398d9 in ?? () from /usr/lib/libc.so.6
  6    Thread 0x7f381e9346c0 (LWP 16740) 0x00007f3824fb09ed in poll () from /usr/lib/libc.so.6
  7    Thread 0x7f3803fff6c0 (LWP 16745) 0x00007f3824f398d9 in ?? () from /usr/lib/libc.so.6
  8    Thread 0x7f38037fe6c0 (LWP 16746) 0x00007f3824f398d9 in ?? () from /usr/lib/libc.so.6
  9    Thread 0x7f38177fe6c0 (LWP 16743) 0x00007f3824fb09ed in poll () from /usr/lib/libc.so.6
  10   Thread 0x7f37f3dff6c0 (LWP 16752) 0x00007f3824fbeaf2 in epoll_wait () from /usr/lib/libc.so.6
  11   Thread 0x7f37bf4d86c0 (LWP 16760) 0x00007f3824fb09ed in poll () from /usr/lib/libc.so.6
  12   Thread 0x7f38017fa6c0 (LWP 16750) 0x00007f3824f398d9 in ?? () from /usr/lib/libc.so.6
  13   Thread 0x7f37f25fc6c0 (LWP 16756) 0x00007f3824fb09ed in poll () from /usr/lib/libc.so.6
  14   Thread 0x7f37f35fe6c0 (LWP 16753) 0x00007f3824fbeaf2 in epoll_wait () from /usr/lib/libc.so.6
  15   Thread 0x7f3802ffd6c0 (LWP 16747) 0x00007f3824f398d9 in ?? () from /usr/lib/libc.so.6
  16   Thread 0x7f3801ffb6c0 (LWP 16749) 0x00007f3824f398d9 in ?? () from /usr/lib/libc.so.6
  17   Thread 0x7f3817fff6c0 (LWP 16742) 0x00007f3824fb09ed in poll () from /usr/lib/libc.so.6
  18   Thread 0x7f3816ffd6c0 (LWP 16744) 0x00007f3824fb09ed in poll () from /usr/lib/libc.so.6
  19   Thread 0x7f3800cae6c0 (LWP 16751) 0x00007f3824f398d9 in ?? () from /usr/lib/libc.so.6
  20   Thread 0x7f37f2dfd6c0 (LWP 16754) 0x00007f3824fbeaf2 in epoll_wait () from /usr/lib/libc.so.6
  21   Thread 0x7f37f15fa6c0 (LWP 16758) 0x00007f3824f398d9 in ?? () from /usr/lib/libc.so.6
  22   Thread 0x7f37f0df96c0 (LWP 16759) 0x00007f3824f398d9 in ?? () from /usr/lib/libc.so.6
@muse-bot muse-bot added the crash Issues involving a crash of MuseScore label May 23, 2024
@MarcSabatella
Copy link
Contributor

Those third party builds often have errors that lead to problems like this. What happens if you instead use the official supported AppImage instead of that other build from the repository?

@Schweini07
Copy link
Author

The Appimage provided by the MuseScore download site, seems to only be MuseScore itself. Or do I have to look somewhere else?

Anyways, it might also be unrelated to that, as I tried deleting the manager and its installed instruments right now, and the crash still occurs. So maybe there is a different reason for the segfault?

@Schweini07
Copy link
Author

The program also still crashes after a complete reinstall with pacman, which is unfortunate 🥲

@MarcSabatella
Copy link
Contributor

Normally you should be installing the AppImage of MuseScore Studio, plus the DEB or RPM file for Muse Sounds Manager.
I gather there are other unofficial packages of Muse Sounds Manager for distributions that are unable to use DEB or RPM files, which you can use at your own risk but I'm not aware of any reported problems with them. MuseScore Studio itself is another matter, though. Definitely you should not be attempting to install thrid-party builds of MuseScore Studio, as many are known not to work. Only the AppImage is supported.

So if you see a crash using the AppImage, definitely followup and post more details. But if it only occurs with a third party build, that's a problem you'd need to report to the folks who produced it.

@bkunda bkunda added community Issues we would like the community to address os: linux Potentially specific to Linux-based operating systems labels May 24, 2024
@Schweini07
Copy link
Author

I see, actually with the appimage I am not experiencing any crashes anymore, so it might very well be the fault of the package. Although the package is from the official repositories, so I would have thought that works out of the box. I might try to contact the maintainer of the package.

@Schweini07
Copy link
Author

I looked a bit through arch linux related issues right now, and it seems that the problem might very well be related to this one: #22926
So I assume the fault lays with the official arch package.

@zacjansheski zacjansheski removed their assignment May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Issues we would like the community to address crash Issues involving a crash of MuseScore os: linux Potentially specific to Linux-based operating systems
Projects
Status: Available
Development

No branches or pull requests

7 participants