You are not logged in.

#1 2022-02-05 17:48:36

joegrammer
Member
Registered: 2022-02-05
Posts: 2

Very strange silent crash with Bitwig

I am at my wit's end here. I'm having the strangest issue with Bitwig, whether installed via package or run through the extracted .deb file. I had been running it just fine since I setup Arch months ago, but all of a sudden the other day this issue started. It seems like it's starting up but then exits before showing the GUI. I see the window show up in my WM's bar, but it goes away before I see the actual UI. I've tried everything I can think of:

  • contacting support (they had me try flatpak, which also exhibited the same behavior

  • looking through pacman logs and removing packages I installed between the last time Bitwig worked and when this started

  • running from terminal to see log output

  • using the early access release

  • removing ~/.BitwigStudio, ~/Bitwig Studio, ~/.BitwigPosix, /dev/shm/bitwig-posix-{user}

  • downgrading to older versions (1.x worked, but 2.x starts breaking)

  • I use yabridge for VSTs via wine, I tried removing the wine prefix folder

  • reinstalling dependencies

  • changing between window managers & display servers (qtile with X, sway, plasma with X)

  • running with and without midi controllers plugged in

  • switching audio from pipewire back to pulse

There's probably more, I've tried a lot. I don't see any errors in the log output except for something around slf4j not being on class path. I That makes me think there could be log output I'm missing. I did try putting `slf4j-simple.jar` in

/opt/bitwig-studio/lib/cp

and

/opt/bitwig-studio/bin

but I still get that message. I'm pasting the output that I see below.

Does anyone have any ideas of what might be going on here? I'm at a complete loss.

Thanks!

About to start the following process:  /opt/bitwig-studio/bin/show-splash-gtk /opt/bitwig-studio/resources/splash-bitwig-studio.png
About to start the following process:  /opt/bitwig-studio/bin/BitwigStudio -cp /opt/bitwig-studio/bin/bitwig.jar:/opt/bitwig-studio/lib/cp:/opt/bitwig-studio/bin/libs.jar:/opt/bitwig-studio/bin/lwjgl.jar -Dorg.sqlite.lib.path=/opt/bitwig-studio/lib/bitwig-studio -XX:+UseZGC -Xms300m -XX:SoftMaxHeapSize=2048m -Xmx3072m -Djava.io.tmpdir=/tmp/bitwig-joe -DinstallationRoot=/opt/bitwig-studio -DsplashPid=547834 -Djava.awt.headless=true -XX:ErrorFile=/home/joe/.BitwigStudio/bitwig-studio-jvm-crash.log com.bitwig.flt.app.BitwigStudioMain
Using log directory /home/joe/.BitwigStudio/log
[2022-02-05 12:45:43.221 float-main-app info] Starting application version 4.1.6 revision 4e9e934ae066e9b1cfc8e7b149373242f1522d8f
[2022-02-05 12:45:43.231 float-main-app info] Using Java version 17.0.1 from Oracle Corporation installed at /opt/bitwig-studio/lib/jre
[2022-02-05 12:45:43.231 float-main-app info] Starting with arguments 
[2022-02-05 12:45:45.690 gui-toolkit-core info] Using locale en
[2022-02-05 12:45:45.879 base-platform info] Using /dev/shm/bitwig-posix-joe/BitwigStudio for POSIX resource tracking
[2022-02-05 12:45:46.056 float-main-app info] Loaded preferences from file /home/joe/.BitwigStudio/prefs/4.1.6.prefs
[2022-02-05 12:45:46.057 float-telemetry info] Starting Telemetry
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See [url]http://www.slf4j.org/codes.html#StaticLoggerBinder[/url] for further details.
Using overridden package repository location: "[url]http://packs.bitwig.com/repository[/url]"
[2022-02-05 12:45:47.797 float-document-master info] Starting engine for New 1
[2022-02-05 12:45:47.799 float-gui-widgets info] Connecting audio engine to project New 1

Last edited by joegrammer (2022-02-05 17:53:03)

Offline

#2 2022-02-06 15:43:57

joegrammer
Member
Registered: 2022-02-05
Posts: 2

Re: Very strange silent crash with Bitwig

Fixed it. Turns out I had a corrupt plugin in my `.vst3` directory.

Some detail for those running into a similar issue:

I decided to try watching my system log with

dmesg -w

. Although I had done this previously, I apparently had missed something about a coredump. This led me to learning about

coredumpctl

and using that I found that it was crashing on a particular file (

libbase-file-notification-linux.so

). A quick Google for this file brought me to a previous post, https://bbs.archlinux.org/viewtopic.php?id=271906. Lesson: I should have searched here first. All good now though.

Offline

Board footer

Powered by FluxBB