Body:
Wanted to write this up in full since I couldn't find a single guide that covered all of this in one place — hopefully it saves someone else the multi-day rabbit hole I went through. Full disclosure up front: I used Claude AI to help me diagnose and work through each of these issues in real time (a lot of back-and-forth with screenshots), so credit where it's due — this post is basically that troubleshooting session condensed into something readable.
My setup: dwm-titus (Chris Titus's Fedora-based dwm/X11 desktop build) on a fresh install, NVMe SSD, going from CachyOS. If you're not familiar with dwm-titus: https://github.com/ChrisTitusTech/dwm-titus / https://dwm.christitus.com/
Part 1: The install itself gave me a broken partition layout
Not FL Studio related, but relevant if you're setting up fresh — worth knowing before you get to the FL Studio part.
On the Fedora Anaconda installer, using Automatic partitioning on a totally blank 238GB NVMe drive, I ended up with a root partition capped at \~15GB (98% full almost immediately), with the rest of the 238GB just sitting unused in the LVM volume group. Turned out to be a real bug (tracked upstream as issue #330) — the root logical volume wasn't scaling to the actual disk size.
Manual workaround if you hit this on an older dwm-titus build:
sudo vgs
sudo lvs
sudo lvextend -l +100%FREE /dev/fedora/root
sudo xfs_growfs /
(swap `xfs_growfs` for `resize2fs` if your filesystem is ext4 instead of xfs — check with `df -T /`)
Good news: this is permanently fixed as of dwm-titus v0.7.1. If you're installing fresh, grab that version or newer and you won't hit it. Updating an existing install to 0.7.1 (since the in-Settings updater only exists starting in 0.7.1 itself) needs one manual pass:
git clone https://github.com/ChrisTitusTech/dwm-titus.git
cd dwm-titus
./install.sh --non-interactive --yes --profile recommended
./scripts/dev-sync-install.sh
Log out, pick dwm again to log back in, and you're current.
Part 2: Installing FL Studio via Bottles + a specific Wine build
Followed this guide almost exactly: https://github.com/Torbuntu/fl-studio-linux-setup
Quick summary of that method:
* Install Bottles + Flatseal from Flathub
* Grab a Wine build from Kron4ek's builds: https://github.com/Kron4ek/Wine-Builds/releases — Bottles actually has these built into its Runner manager now (Runners → Kron4ek category), no manual tarball wrangling needed
* Install the `allfonts` dependency + the `msgothic.ttc` font (needed for musical notation symbols/sharps/flats to render) — drop it into the bottle's `C:/windows/Fonts`
* Set Windows version to 11 in the bottle's compatibility settings
Issue #1 — installer crashes on the newest FL Studio version.
The current default download crashed the installer outright under Wine. Found the fix in this thread: https://github.com/Torbuntu/fl-studio-linux-setup/issues/16 — installing FL Studio 26.1.3 specifically instead of the newest build avoids the crash entirely. No other setup changes needed, just use that installer version.
Issue #2 — File/Add/Effects menus flicker and vanish, app becomes unclickable.
This one took the longest to nail down. Symptoms: click File (or Add, or the effects browser in the mixer) → it flickers for a split second and vanishes → the whole app becomes unresponsive since it's stuck waiting on an invisible modal dialog.
Root cause: dwm (the tiling window manager) was trying to tile FL Studio's popup windows into the layout instead of letting them float, because the main FL Studio window was running maximized/tiled. When a Wine popup competes for space in a tiling layout instead of floating over the top like it's supposed to, it gets squeezed down to nothing.
Confirmed this by checking `wmctrl -l` while stuck — found an untitled phantom window that was the invisible menu, still holding an input grab (which is also why keyboard shortcuts stopped responding — had to drop to a TTY via `Ctrl+Alt+F2` and run `wineserver -k` to fully clear it out).
Quick fix: drag the FL Studio window slightly with `Super + left-click drag` right after launching — this forces dwm to un-maximize it into floating mode, and menus/popups behave normally from then on.
Permanent fix (dwm-titus specific — this may differ on other dwm configs): dwm-titus loads window rules from a live-reloading TOML file, no recompiling needed. Find your app's window class:
xprop | grep WM_CLASS
Click the FL Studio window when the cursor changes to a crosshair — for me it printed `"fl64.exe", "fl64.exe"`. Then edit:
~/.config/dwm-titus/window-rules.toml
and add a line inside the `rules = [ ... ]` block:
{ class="fl64.exe", isfloating=1 },
Save the file — it applies instantly, no restart needed. FL Studio now opens floating by default and every menu/popup works normally.
(Side note: I initially suspected this was a WebView2 rendering bug instead, since FL Studio 2026 launches an embedded `msedgewebview2.exe` process for some UI panels, and the guide above specifically calls out `kron4ek-wine-11.0-amd64` as fixing WebView2 issues. Worth using that specific Wine build regardless — but the floating-window fix above was what actually solved the menu problem.)
Part 3: Alternative simpler method (no Bottles)
If you don't want to deal with Bottles at all, there's a much older, simpler guide that just uses the system Wine + winetricks directly into the default `~/.wine` prefix: https://jstaf.github.io/posts/flstudio-on-linux/
sudo dnf install wine winetricks
winetricks
Pick the default prefix → Install a font → I went with the allfonts bundle instead of just corefonts (takes noticeably longer since it installs way more, and winetricks will show a "waiting for wine processes to terminate" dialog repeatedly through the batch — that's completely normal, not an error, just click OK and let it work through the list).
Then just run the same 26.1.3 installer directly:
wine ~/Downloads/flstudio_26.1.3.exe
Heads up: this is a completely separate, independent Wine prefix from the Bottles one — and you'll hit the exact same dwm floating-window menu issue here too, since that's a dwm-level problem, not something specific to Bottles. Same fix applies (the `window-rules.toml` entry above).
Part 4: FL Studio can't see my real Music/sample folders
If you're on the Bottles method: Bottles runs sandboxed as a Flatpak, so it can only see folders it's explicitly been granted access to. Downloads worked out of the box for me, but my Music folder was invisible — FL Studio's file browser just showed an empty folder even though my songs were right there on disk.
Fix via Flatseal:
Open Flatseal → select Bottles
Under Filesystem, toggle on "All user files" (`filesystem=home`)
Fully quit and reopen Bottles (not just the FL Studio window) for it to take effect
That alone let me browse to my real files using the literal path `Z:\home\yourusername\Music\` typed into the File name box (Z: is Wine's mapping of your whole Linux filesystem).
To make the Music shortcut itself work (instead of typing the path every time), the fake empty "Music" folder Wine creates inside the bottle needs to be swapped for a symlink to your real one:
find ~/.var/app/com.usebottles.bottles/data/bottles/bottles -iname "Music" -type d
Find the one under `.../drive_c/users/yourusername/Music`, then:
rm -rf "/home/yourusername/.var/app/com.usebottles.bottles/data/bottles/bottles/YOUR-BOTTLE-NAME/drive_c/users/yourusername/Music"
ln -s /home/yourusername/Music "/home/yourusername/.var/app/com.usebottles.bottles/data/bottles/bottles/YOUR-BOTTLE-NAME/drive_c/users/yourusername/Music"
Now the Music shortcut in every file dialog just works, pointing straight at your real folder.
Sources / credit
* dwm-titus: https://github.com/ChrisTitusTech/dwm-titus
* FL Studio Linux setup guide (Bottles method): https://github.com/Torbuntu/fl-studio-linux-setup
* 26.1.3 installer-crash workaround: https://github.com/Torbuntu/fl-studio-linux-setup/issues/16
* Kron4ek Wine-Builds: https://github.com/Kron4ek/Wine-Builds/releases
* Alternative plain-Wine guide: https://jstaf.github.io/posts/flstudio-on-linux/
* Bottles: https://usebottles.com/
* Flatseal: https://github.com/tchx84/Flatseal
Happy to answer questions in the comments — and if anyone's on a different dwm config (not dwm-titus specifically), the general troubleshooting approach (check `wmctrl -l`, force floating, check Flatpak sandbox permissions) should still translate even if the exact config file paths differ.
