FMOD Studio 2.03.13 startup crash on Ubuntu 24.04 with SIGABRT

FMOD Studio
1

Hi, I’ve completely switched from Windows to Linux. Most of my workflow and tools have already migrated and are working correctly, with the exception of Fmod Studio (well there are other minor itchy things, but Fmod Studio is having a major impact). In an attempt to fix the issue, I let my copilot analyze the crash, however, it suggested reporting it here with a well-formatted report instead. so next line generated stuff. :sweat_smile:

Report
Immediate startup crash with FMOD Studio on Ubuntu 24.04. The attached crash report shows SIGABRT during Qt GUI initialization, with the stack going through qAbort, QMessageLogger::fatal, and QGuiApplicationPrivate::createPlatformIntegration.

Environment

  • Ubuntu 24.04

  • Kernel 6.17.0-22-generic x86_64

  • FMOD Studio 2.03.13

Steps to Reproduce

  1. Launch FMOD Studio.

  2. The process aborts before the main UI appears.

Observed Behavior
The failure happens during Qt platform setup, so this looks more like a Linux runtime or platform plugin issue than a project-specific FMOD crash.

_opt_fmodstudio_fmodstudio.1000.log (85.3 KB)

2

Hi,

Thank you for bringing this to our attention. Are you using the .deb or .AppImage? If using the .AppImage would it be possible to launch it from a terminal and share the complete logs?

3

Yes, I can confirm .appimage works. It opened directly without needing installation, everything is working normally. I would still prefer .deb, though, to pin the app launcher icon in my workspace, but this will do for now.

I found this log in the .local folder, not sure how complete it is, and it didn’t crash, so it’s different from that other crash log.

2026-04-28-09-48-42_log.txt (27.4 KB)

4

Good to hear the .AppImage is working and thank you for the logs.

Can you confirm if FMOD Studio was installed here:

/opt/fmodstudio/fmodstudio

And if you run that from a terminal windows can you share the out put:

/opt/fmodstudio$ ./fmodstudio
[Initialize Sound System 0x000000001d6aab50]: Time started
[Initialize Sound System 0x000000001d6aab50]: Time taken is 4.85ms (0.004s)
[Uninitialize Sound System 0x000000001d6aab50]: Time started
[Uninitialize Sound System 0x000000001d6aab50]: Time taken is 199.20ms (0.199s)
[Initialize Sound System 0x000000001d6aab50]: Time started
[Initialize Sound System 0x000000001d6aab50]: Time taken is 3.18ms (0.003s)
ScriptServer started on 0.0.0.0 (3663)

This will hopefully give us some more info.

5

Yes there is entire folder, upon try to launch executable in there, it still crashes.
Upon launching from terminal i got this output

qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb, minimal, wayland.

Aborted (core dumped)

so i ran sudo apt install libxcb-cursor0 and Now it working, mostly dependency need to be fixed in deb installer, that’s all it was.

6

Good to hear it is solved, thanks for sharing the solution.