It's time for Buster RC-2. Testers Needed!

HI @zynthianers!
It seems that last images have problems. As i’m in a little country house, my band is really small and i can’t test the latest SD images. This is the reason i have not released a new SD image. I will visit Barcelona in the next days, so ii will download and test some of the latest SD images. Mean while, could some “advanced” user help me to confirm/identify the problem?

Thanks a lot!


I’ve been working from 2020-05-14-zynthianos-buster-lite-1.0.0.img

and that seems ok for me.

Please, could you test this image, or better, the last one from today. If you and somebody with a v3 zynthian could confirm it works OK, i could mark it as RC2 and avoid more headaches with recent SD images until i can do my own test …

Of course, the more testers, the better …

Let’s concentrate on yesterday’s image that seems to be good:

If this doesn’t work, we can try with 2020-05-14 or any other recent SD image that somebody had already tested.

Thanks a lot!

This is really a very useful idea, I’m switching to 2020-05-22.

And there we have a candidate! After an hour I give up. I can’t get it to run. 2020-05-14 was deleted?

Could you be more specific about the problems you found?

Ups! Regarding 2020-05-14, the auto-delete system probably get ride of it. It deletes SD-images older than a week if they are not marked as RC.

But if we don’t find another working SD image, @wyleu can upload his copy to the server :wink:


of course I can be specific:

start with a new image: display error
Followed by about 5 minutes of black screen
Then very slowly fading in and out - zynthian - ERROR IP:
Zynthian directly connected to the router via LAN.
Display: ERROR IP:
webconf does not work over zynthian.local or over IP
continue via console:

Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
Please contact your system administrator.
Add correct host key in /home/“user”/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /home/“user”/.ssh/known_hosts:1
You can use following command to remove the offending key:
ssh-keygen -R -f /home/“user”/.ssh/known_hosts
ECDSA host key for has changed and you have requested strict checking.
Host key verification failed.

ssh-keygen -R -f /home/“user”/.ssh/known_hosts

no further connection via browser - continue via console

display console: Update complete -
but still flashing display - error: IP

in console: reboot

on startup: flashing display - error: IP

and again:
ssh-keygen -R zynthian.local -f /home/“user”/.ssh/known_hosts

webconf now possible in firefox
once angain Software Update - now with firefox

reboot -
on startup: again: flashing display - error: IP

->given up

Hi @spurkopf,

Please, could you send the webconf log?
Simply type:

journalctl -u zynthian-webconf -f 

And try to access from the browser. Then copy/paste the output from the console. With this i could figure where the problem is and try to solve it for the next SD image builds.


No sorry, 2020_05_22 is already deleted. I have a copy of the 2020_05_17 UI log - I’m uploading it. But why mess with it, wouldn’t it be easier if you could say - this image worked for me - please test it?
Zynthian_17052020Ui_log.txt (31.2 KB)

testing 2020_05_16:

  • o.k. this time webconf works out of the box
  • again displaying ERROR
  • but this time it detected a V3PRO
    while 2020_05_22 and 2020_05_17 detected Raspberry Pi 3 Model B Plus Rev 1.3
  • changed to Raspberry Pi 3 Model B Plus Rev 1.3 and reboot, now ZynScreen ist working - but no encoders
  • changed to custom kit and Mcp23017 Encoders - now they are working too
  • switching of single mode, activating midi clock internal and setup wifi
    Now it should all working. :sweat:

3 posts were split to a new topic: Qmidinet feedback

Zynthian doesn’t detect hardware, apart from the RBPi. SD images are pre-configured for a given hardware combination, depending on the image date. The latest ones are pre-configured for “Kit V3 - Pro”. What is your kit version @spurkopf?

According to your bill, I have:

  • Aluminum Case Kit v2
  • 4 x Controller Module Kit v2
  • All-In-One Module Kit
  • Ribbon Bus cable v2
  • Wiring Kit v2
  • RaspBerry Pi 3 B+ (computer board)
  • HifiBerry DAC+ Kit (soundcard)
  • OzzMaker PiScreen 3.5’ (touchscreen)

Build from today(2020-05-23) is no candidate.

@jofemodo, webconf doesn’t start…mutagen

WARNING:zynthian_gui_config: No Display!
Traceback (most recent call last):
File “./”, line 42, in
from lib.ui_keybind_handler import UiKeybindHandler
File “/home/pi/zynthian-webconf/lib/”, line 31, in
from zyngui.zynthian_gui_keybinding import zynthian_gui_keybinding
File “/zynthian/zynthian-ui/zyngui/”, line 53, in
from zyngui.zynthian_gui_audio_recorder import zynthian_gui_audio_recorder
File “/zynthian/zynthian-ui/zyngui/”, line 29, in
import mutagen
ModuleNotFoundError: No module named ‘mutagen’

ah @jofemodo and I didn’t check…Pianoteq…there is a 6.7.1
Is the free trial updated already?

OK! I found the problem with mutagen and the SD build script:

# Install Mutagen (when available, use pip3 install)

I just launched a new build for today (2020-05-24). It will finish in about 4 hours, about 21:00.


@jofemodo Were you typing too fast when you wrote that?
:face_with_raised_eyebrow: :grin: :rofl:


Hi José,
is that the one we should test in priority ?

Nope, that’s from yesterday and still has the mutagen bug (tested this morning)
[In reply to “
is that the one we should test in priority ?”, hit the wrong reply button :frowning: ]

Ok, thank you.
So far, I think running


should solve the problem.
So except that “mutagen” bug, this version should be like the next one.