[RESOLVED] Bitwig crashes since 5.14
gelabs
Status: Interested
Joined: 02 May 2017
Posts: 16
Reply Quote
Hello dear devs,

Since 5.14 Bitwig crashes upon startup (and trying to activate audio engine). On 5.13 (all versions) this was not present.

Jack log says :
:: Code ::

ERROR: JackEngine::XRun: client = Bitwig Studio was not finished, state = Triggered
ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error

then a bunch of :
:: Code ::

ERROR: Cannot write socket fd = 26 err = Broken pipe
ERROR: CheckRes error
ERROR: Could not write notification
ERROR: ClientNotify fails name = Bitwig Studio notification = 10 val1 = 77 val2 = 0

Jack is configured with SR=44100/Buffer size = 512/periods = 2

Is it because of the change of CPU scheduler from MuQSS to PDS ?
Can I configure something to make it work again with 5.14 ?

Thank you.
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 914
Reply Quote
Huh, I installed bitwig-studio through the AUR in Arch Linux and launched it using the pipewire wrapper with pw-jack bitwig-studio. It came up and in a few minutes I had access to play piano and drums with working sound.

Can you provide more information about your system? Bare minimum, show us the output of inxi -b so that we know more about your software / hardware combination.
Back to top
gelabs
Status: Interested
Joined: 02 May 2017
Posts: 16
Reply Quote
Mmmhhh ... ok, now it's working I dont' undestand what was wrong.
For the record :
inxi -b
:: Code ::

System:    Host: xxxxxx Kernel: 5.14.0-9.5-liquorix-amd64 x86_64 bits: 64 Console: tty pts/0
           Distro: Debian GNU/Linux bookworm/sid
Machine:   Type: Desktop System: ASUS product: All Series v: N/A serial: N/A
           Mobo: ASUSTeK model: Z97-K v: Rev X.0x serial: xxxxxxxxxxx UEFI-[Legacy]: American Megatrends v: 2902
           date: 03/31/2016
CPU:       Info: Quad Core Intel Core i7-4790K [MCP] speed: 3998 MHz min/max: 800/4001 MHz
Graphics:  Device-1: NVIDIA TU116 [GeForce GTX 1660 Ti] driver: nvidia v: 470.63.01
           Display: server: X.Org 1.20.11 driver: loaded: nvidia resolution: 2560x1440~60Hz
           OpenGL: renderer: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 470.63.01
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
Drives:    Local Storage: total: 2.51 TiB used: 1.24 TiB (49.6%)
Info:      Processes: 227 Uptime: 3m Memory: 15.58 GiB used: 1.6 GiB (10.2%) Shell: Bash inxi: 3.3.06

Last updates from this morning:
:: Code ::

Install: libgupnp-1.2-1:amd64 (1.4.0-2, automatic)
Upgrade: ruby-dev:amd64 (1:2.7+2, 1:2.7.5), libcanberra-gtk3-0:amd64 (0.30-7+b1, 0.30-8), exim4:amd64 (4.95~RC2-1, 4.95-1), libmtp-common:amd64 (1.1.18-2, 1.1.19-1), vim-gui-common:amd64 (2:8.2.3455-1, 2:8.2.3455-2), linux-perf:amd64 (5.14.6-3, 5.14.9-2), update-glx:amd64 (1.2.0, 1.2.1), libcanberra-gtk3-module:amd64 (0.30-7+b1, 0.30-8), tzdata:amd64 (2021b-1, 2021c-1), glx-alternative-nvidia:amd64 (1.2.0, 1.2.1), libcanberra-gstreamer:amd64 (0.30-7+b1, 0.30-8), vim:amd64 (2:8.2.3455-1, 2:8.2.3455-2), xxd:amd64 (2:8.2.3455-1, 2:8.2.3455-2), libp11-kit0:amd64 (0.24.0-2+b1, 0.24.0-3), libp11-kit0:i386 (0.24.0-2+b1, 0.24.0-3), glx-diversions:amd64 (1.2.0, 1.2.1), vim-gtk3:amd64 (2:8.2.3455-1, 2:8.2.3455-2), bison:amd64 (2:3.8.1+dfsg-1, 2:3.8.2+dfsg-1), vim-common:amd64 (2:8.2.3455-1, 2:8.2.3455-2), libkf5newstuff5:amd64 (5.86.0-2, 5.86.0-3), libtag1v5:amd64 (1.11.1+dfsg.1-3, 1.12-1), libtag1v5:i386 (1.11.1+dfsg.1-3, 1.12-1), linux-cpupower:amd64 (5.14.6-3, 5.14.9-2), libgupnp-igd-1.0-4:amd64 (1.2.0-1, 1.2.0-1+b1), exim4-config:amd64 (4.95~RC2-1, 4.95-1), libkf5attica5:amd64 (5.86.0-1, 5.86.0-2), libmtp9:amd64 (1.1.18-2, 1.1.19-1), p11-kit-modules:amd64 (0.24.0-2+b1, 0.24.0-3), p11-kit-modules:i386 (0.24.0-2+b1, 0.24.0-3), exim4-base:amd64 (4.95~RC2-1, 4.95-1), python3-apsw:amd64 (3.36.0-r1-1, 3.36.0-r1-2), docbook-xml:amd64 (4.5-9, 4.5-11), mtp-tools:amd64 (1.1.18-2, 1.1.19-1), gir1.2-nm-1.0:amd64 (1.30.6-1, 1.32.12-1), libpcsclite1:amd64 (1.9.3-2, 1.9.4-1), python3-soupsieve:amd64 (2.2.1-1, 2.2.1-2), dictionaries-common:amd64 (1.28.7, 1.28.10), vim-tiny:amd64 (2:8.2.3455-1, 2:8.2.3455-2), ruby:amd64 (1:2.7+2, 1:2.7.5), pcscd:amd64 (1.9.3-2, 1.9.4-1), libimage-exiftool-perl:amd64 (12.31+dfsg-1, 12.32+dfsg-1), glx-alternative-mesa:amd64 (1.2.0, 1.2.1), vim-runtime:amd64 (2:8.2.3455-1, 2:8.2.3455-2), libseccomp2:amd64 (2.5.2-1, 2.5.2-2), bash-completion:amd64 (1:2.11-3, 1:2.11-4), libkf5newstuffcore5:amd64 (5.86.0-2, 5.86.0-3), exim4-daemon-light:amd64 (4.95~RC2-1, 4.95-1), libhdf5-103-1:amd64 (1.10.7+repack-2, 1.10.7+repack-3), libtagc0:amd64 (1.11.1+dfsg.1-3, 1.12-1), libcpupower1:amd64 (5.14.6-3, 5.14.9-2), qml-module-org-kde-newstuff:amd64 (5.86.0-2, 5.86.0-3), libmtp-dev:amd64 (1.1.18-2, 1.1.19-1), libtag1v5-vanilla:amd64 (1.11.1+dfsg.1-3, 1.12-1), libtag1v5-vanilla:i386 (1.11.1+dfsg.1-3, 1.12-1), linux-perf-5.14:amd64 (5.14.6-3, 5.14.9-2), libnm0:amd64 (1.30.6-1, 1.32.12-1), libhdf5-hl-100:amd64 (1.10.7+repack-2, 1.10.7+repack-3), libcanberra0:amd64 (0.30-7+b1, 0.30-8), xdg-desktop-portal:amd64 (1.10.1-1, 1.10.1-2), p11-kit:amd64 (0.24.0-2+b1, 0.24.0-3), libkf5newstuff-data:amd64 (5.86.0-2, 5.86.0-3), intel-media-va-driver:amd64 (21.3.3+dfsg1-1, 21.3.4+dfsg1-1), libmtp-runtime:amd64 (1.1.18-2, 1.1.19-1), libtag1-dev:amd64 (1.11.1+dfsg.1-3, 1.12-1), linux-libc-dev:amd64 (5.14.6-3, 5.14.9-2)


And kernel 5.14.0-9.5 instead of 5.14.0-9.1

I don't use "pw-jack" at all, it's not installed on my system, I just usually launch bitwig-studio without any wrapper.

Anyway, it seems to be working correctly now.

Thank you damentz, for your time and for the kernel :)
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 914
Reply Quote
:: gelabs wrote ::
Mmmhhh ... ok, now it's working I dont' undestand what was wrong.


It could be the few changes I made recently. I tried backporting the tracing configuration from Zen Kernel, but I think it caused some stability issues, so I rolled that back and surgically only added the feature needed to support call graphing support in perf.

Also, last update included more stable updates that may have fixed the interaction with Bitwig.

But glad it works now! Marking as resolved.
Back to top
Display posts from previous:   

All times are GMT - 8 Hours