More update issues

Hi

[tomita]
Since roughly a week or so I have some problems after updating.
It started with the update script hanging for ever after “Regenerating engines DB: engines …”.
Since around friday the update script finishes without errors but after the reboot I’m getting the error screen with Showing IP and SegFault (#counting upwards)
I can reach the zynthian via SSH, webconf is accessible, but the Zynthian UI itself is failing.

UI Log (repeating the same entries over and over again):
…
Nov 15 17:21:36 zynthian startx[6758]: ./zynthian.sh: line 381: 7001 Segmentation fault ./zynthian_main.py
Nov 15 17:21:36 zynthian startx[6758]: *******************
Nov 15 17:21:36 zynthian startx[6758]: EXIT STATUS => 139
Nov 15 17:21:36 zynthian startx[6758]: *******************
Nov 15 17:21:36 zynthian startx[7043]: /zynthian/config/img/fb_zynthian_message.jpg is a 800x480 JPEG image, color space YCbCr, 3 comps, Huffman coding.
Nov 15 17:21:36 zynthian startx[7043]: Zooming image by 100%…done
Nov 15 17:21:36 zynthian startx[7043]: Merging…done
Nov 15 17:21:36 zynthian startx[7043]: Building XImage…done
Nov 15 17:21:47 zynthian startx[7055]: ZynCore: Setting-up 20+4 x Zynswitches…
Nov 15 17:21:47 zynthian startx[7055]: ZynCore: Setting-up 2 x Zynswitches in RBPi GPIO…
Nov 15 17:21:47 zynthian startx[7055]: ZynCore: Setting-up Zynpots => 4 x PEC11 …
Nov 15 17:21:47 zynthian startx[7055]: Loaded libzynaudioplayer using libsndfile-1.2.2
Nov 15 17:21:47 zynthian startx[7055]: Started zynmixer_chan
Nov 15 17:21:47 zynthian startx[7055]: Started zynmixer_bus
Nov 15 17:21:47 zynthian startx[7055]: Started libzynseq
Nov 15 17:21:47 zynthian startx[6758]: ./zynthian.sh: line 381: 7055 Segmentation fault ./zynthian_main.py
Nov 15 17:21:47 zynthian startx[6758]: *******************
Nov 15 17:21:47 zynthian startx[6758]: EXIT STATUS => 139
Nov 15 17:21:47 zynthian startx[6758]: *******************
…

Not sure if this is a problem of my user interaction (which I assume) or a real tomita problem.
Just wanted to ask (I prefer understanding why something fails) before I go the fallback path of reimaging my test sd…

Any ideas?

Not sure if someone did some specific magic or if it was just a side effect of a regular update, but doing another update just magically fixed everything.

Still curious what was the reason, but at least its back on track again. THX!

1 Like

We probably fix it :wink:

1 Like