Topic by jimmi

  • Avatar
  • jimmi
  • Member
  • Offline
  • Registered: 20-12-2019
  • Posts: 33

Topic: Pianoteq 9 on Raspberry Pi5 goes segfault if started with VNC

I'm using Pianoteq 8 with a headless Raspberry Pi5 running Raspberry Pi OS. I use to start it with VNC and connect with my mobile or tablet.
This configuration is fine with PT8 but when I give a try with PT9 I read the following in VNC logs:

xstartup started
/home/pi/Pianoteq 9/arm-64bit/Pianoteq.sh: line 7:  1837 Segmentation fault      /home/pi/'Pianoteq 9'/arm-64bit/'Pianoteq 9' --fullscreen --multicore max
xstartup terminated

Started headless Pianoteq 9 runs fine.

Any suggestion how to debug it?

Last edited by jimmi (08-11-2025 08:19)

Reply by bazzo

  • Avatar
  • bazzo
  • Member
  • Offline
  • Registered: 13-09-2024
  • Posts: 13

Re: Pianoteq 9 on Raspberry Pi5 goes segfault if started with VNC

Hi Jimmi,

im not using Pianoteq via VNC but I have a similar issue when starting with the "--fullscreen" option. PT8 worked fine. Maybe try it without this option.

When PT9 is running windowed, it works. I can then switch to Fullscreen as long as the GUI is not in "Compact Mode".

Compact-Mode and Fullscreen-Mode both work exclusively, but when i try to combine them (both on at the same time) PT9 crashes instantly.

Regards Bazzo

Last edited by bazzo (08-11-2025 10:55)

Reply by jimmi

  • Avatar
  • jimmi
  • Member
  • Offline
  • Registered: 20-12-2019
  • Posts: 33

Re: Pianoteq 9 on Raspberry Pi5 goes segfault if started with VNC

bazzo wrote:

Hi Jimmi,
im not using Pianoteq via VNC but I have a similar issue when starting with the "--fullscreen" option.

This was the problem in fact, starting fullscreen make PT9 crashing. Unfortunately using PT via VNC windowed waste part of the screen for nothing, that is quite bad when using from small screen mobile.

I cannot find a way to file a bug report, I hope someone from the staff will have a look here and support.

Reply by bazzo

  • Avatar
  • bazzo
  • Member
  • Offline
  • Registered: 13-09-2024
  • Posts: 13

Re: Pianoteq 9 on Raspberry Pi5 goes segfault if started with VNC

jimmi wrote:

I cannot find a way to file a bug report, I hope someone from the staff will have a look here and support.

I filed one (#022960) on Oct. 21. :-)

Last edited by bazzo (09-11-2025 02:50)

Reply by revox

  • Avatar
  • revox
  • Member
  • Offline
  • Registered: 04-03-2024
  • Posts: 13

Re: Pianoteq 9 on Raspberry Pi5 goes segfault if started with VNC

jimmi wrote:

I'm using Pianoteq 8 with a headless Raspberry Pi5 running Raspberry Pi OS. I use to start it with VNC and connect with my mobile or tablet.
This configuration is fine with PT8 but when I give a try with PT9 I read the following in VNC logs:

xstartup started
/home/pi/Pianoteq 9/arm-64bit/Pianoteq.sh: line 7:  1837 Segmentation fault      /home/pi/'Pianoteq 9'/arm-64bit/'Pianoteq 9' --fullscreen --multicore max
xstartup terminated

Started headless Pianoteq 9 runs fine.

Any suggestion how to debug it?


Until this gets fixed, you can try a workaround to send a fullscreen keystroke Ctrl+Shift+F to the app.
install xdotool: 

apt-get install xdotool

Edit: /home/pi/Pianoteq 9/arm-64bit/Pianoteq.sh
and add (line 6):

(sleep 5; xdotool key ctrl+shift+F) &
/home/pi/Pianoteq\ 9/arm-64bit/Pianoteq\ 9 --multicore max
Last edited by revox (09-11-2025 16:06)

Reply by bazzo

  • Avatar
  • bazzo
  • Member
  • Offline
  • Registered: 13-09-2024
  • Posts: 13

Re: Pianoteq 9 on Raspberry Pi5 goes segfault if started with VNC

9.0.3 was released, the changelog states that this bug is fixed. I'm not at home and cant test myself right now.

Regards
Bazzo

Reply by jimmi

  • Avatar
  • jimmi
  • Member
  • Offline
  • Registered: 20-12-2019
  • Posts: 33

Re: Pianoteq 9 on Raspberry Pi5 goes segfault if started with VNC

bazzo wrote:

9.0.3 was released, the changelog states that this bug is fixed. I'm not at home and cant test myself right now.

I confirm that the new release 9.0.3 works for me, thanks to the developers

BTW Thanks to @revox as well, the workaround was useful.