ARGH... Just did the latest update. Stuck on zynthian logo screen

My vanilla V3 (with RPi4) Zynthian has been running along well for quite some time now and this afternoon I did a software update. That was the end of that. Rebooted to the Zynthian logo and there was no way out of it.

Instead of spending hours messing around with it I backed up my Snapshots and decided to just do a clean install. Downloaded the latest stable image, burned it with Balena and now I’m dealing with a Zynthian that shows the UI for a few seconds, shows the Zynthian Logo and repeats. I hooked up via the webconfig over ethernet. The webconfig works fine except when I make changes to the config and it requires a reboot it never reboots. It just keeps cycling the UI. So even though I change it to Custom Kit, Zynscreen 3.5, etc, none of these changes stick because it won’t reboot.

This isn’t fun.

As I could not get it to reboot or shutdown, I finally just got mad and yanked the power to shut it down. Strangely, when I plugged it back in, it came up but no longer in the infinite UI reboot loop. It appears my changes stuck after a power cycle.

I’m not filled with confidence but at least I appear to have gained control again.

Any thoughts on why I was stuck in a UI cycling loop like that?

Please post a screenshot of your webconf dashboard.

Zynthian has a supervisor wrapper that detects the exit code of the core python code and reacts accordingly. If there is a bug in the python code then it may exit with the wrong code and result in unexpected results including showing the error screen, failing to reboot, etc. The cause of this is often recorded in the log so it may also be beneficial to provide logs which can be viewed in webconf.

1 Like

Dashboard snapshots, from my tablet, are below.

Captured initial log, went into debug mode, and back to normal UI mode below.

– Logs begin at Fri 2023-02-24 02:24:55 GMT. –
Feb 24 14:20:30 zynthian startx[5574]: [1B blob data]
Feb 24 14:20:30 zynthian startx[5574]: waiting for X server to shut down XIO: fatal IO error 11 (Resource temporarily unavailable) on X server “:0”
Feb 24 14:20:30 zynthian startx[5574]: after 1844 requests (1777 known processed) with 0 events remaining.
Feb 24 14:20:30 zynthian startx[5574]: WARNING:zynthian_autoconnect.cb_jack_xrun: Jack Audio XRUN! => delayed 0.0us
Feb 24 14:20:30 zynthian startx[5574]: WARNING:zynthian_autoconnect.cb_jack_xrun: Jack Audio XRUN! => delayed 0.0us
Feb 24 14:20:30 zynthian startx[5574]: (II) Server terminated successfully (0). Closing log file.
Feb 24 14:20:31 zynthian startx[5574]: xinit: unexpected signal 15
Feb 24 14:20:31 zynthian systemd[1]: zynthian.service: Main process exited, code=exited, status=1/FAILURE
Feb 24 14:20:31 zynthian systemd[1]: zynthian.service: Failed with result ‘exit-code’.
Feb 24 14:20:31 zynthian systemd[1]: Stopped Zynthian User Interface.

Restarting UI in debug mode
– Logs begin at Fri 2023-02-24 02:24:55 GMT. –
Feb 24 14:21:00 zynthian startx[6161]: INFO:zynthian_audio_recorder.unarm: Channel 11 not armed
Feb 24 14:21:00 zynthian startx[6161]: INFO:zynthian_audio_recorder.unarm: Channel 12 not armed
Feb 24 14:21:00 zynthian startx[6161]: INFO:zynthian_audio_recorder.unarm: Channel 13 not armed
Feb 24 14:21:00 zynthian startx[6161]: INFO:zynthian_audio_recorder.unarm: Channel 14 not armed
Feb 24 14:21:00 zynthian startx[6161]: INFO:zynthian_audio_recorder.unarm: Channel 15 not armed
Feb 24 14:21:00 zynthian startx[6161]: INFO:zynthian_audio_recorder.unarm: Channel 256 not armed
Feb 24 14:21:00 zynthian startx[6161]: INFO:zynthian_gui_layer.restore_state_snapshot: Setting curlayer to 0
Feb 24 14:21:00 zynthian startx[6161]: DEBUG:zynthian_gui.set_active_channel: ACTIVE CHAN: -1 => 0
Feb 24 14:21:00 zynthian startx[6161]: INFO:zynthian_gui.zynswitches_midi_setup: CUSTOM I/O SETUP…
Feb 24 14:21:00 zynthian startx[6161]: INFO:zynseq.restore_riff_data: Restoring RIFF data…

UI Log

SHOW DEBUG LOGGING

Restarting UI in normal mode
– Logs begin at Fri 2023-02-24 02:24:55 GMT. –
Feb 24 14:20:30 zynthian startx[5574]: waiting for X server to shut down XIO: fatal IO error 11 (Resource temporarily unavailable) on X server “:0”
Feb 24 14:20:30 zynthian startx[5574]: after 1844 requests (1777 known processed) with 0 events remaining.
Feb 24 14:20:30 zynthian startx[5574]: WARNING:zynthian_autoconnect.cb_jack_xrun: Jack Audio XRUN! => delayed 0.0us
Feb 24 14:20:30 zynthian startx[5574]: WARNING:zynthian_autoconnect.cb_jack_xrun: Jack Audio XRUN! => delayed 0.0us
Feb 24 14:20:30 zynthian startx[5574]: (II) Server terminated successfully (0). Closing log file.
Feb 24 14:20:31 zynthian startx[5574]: xinit: unexpected signal 15
Feb 24 14:20:31 zynthian systemd[1]: zynthian.service: Main process exited, code=exited, status=1/FAILURE
Feb 24 14:20:31 zynthian systemd[1]: zynthian.service: Failed with result ‘exit-code’.
Feb 24 14:20:31 zynthian systemd[1]: Stopped Zynthian User Interface.
Feb 24 14:25:37 zynthian systemd[1]: Started Zynthian User Interface.
Feb 24 14:25:37 zynthian startx[7982]: X.Org X Server 1.20.4
Feb 24 14:25:37 zynthian startx[7982]: X Protocol Version 11, Revision 0
Feb 24 14:25:37 zynthian startx[7982]: Build Operating System: Linux 5.4.0-109-generic armv8l Raspbian
Feb 24 14:25:37 zynthian startx[7982]: Current Operating System: Linux zynthian 5.15.70-v7l+ #1590 SMP Tue Sep 27 15:58:00 BST 2022 armv7l
Feb 24 14:25:37 zynthian startx[7982]: Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:62:87:23 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
Feb 24 14:25:37 zynthian startx[7982]: Build Date: 04 August 2022 12:56:42PM
Feb 24 14:25:37 zynthian startx[7982]: xorg-server 2:1.20.4-1+rpt4+deb10u5 (Debian -- User Support)
Feb 24 14:25:37 zynthian startx[7982]: Current version of pixman: 0.36.0
Feb 24 14:25:37 zynthian startx[7982]: Before reporting problems, check http://wiki.x.org
Feb 24 14:25:37 zynthian startx[7982]: to make sure that you have the latest version.
Feb 24 14:25:37 zynthian startx[7982]: Markers: (–) probed, (**) from config file, (==) default setting,
Feb 24 14:25:37 zynthian startx[7982]: (++) from command line, (!!) notice, (II) informational,
Feb 24 14:25:37 zynthian startx[7982]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Feb 24 14:25:37 zynthian startx[7982]: (==) Log file: “/var/log/Xorg.0.log”, Time: Fri Feb 24 14:25:37 2023
Feb 24 14:25:37 zynthian startx[7982]: (==) Using config directory: “/etc/X11/xorg.conf.d”
Feb 24 14:25:37 zynthian startx[7982]: (==) Using system config directory “/usr/share/X11/xorg.conf.d”
Feb 24 14:25:38 zynthian startx[7982]: /zynthian/config/img/fb_zynthian_boot.png is 480x320 PNG image, color type GRAY, 8 bit
Feb 24 14:25:38 zynthian startx[7982]: Zooming image by 100%…done
Feb 24 14:25:38 zynthian startx[7982]: Merging…didn’t find evidence of prior run.
Feb 24 14:25:38 zynthian startx[7982]: done
Feb 24 14:25:38 zynthian startx[7982]: Building XImage…done
Feb 24 14:25:38 zynthian startx[7982]: ----------------------------------------------
Feb 24 14:25:38 zynthian startx[7982]: Linux Version: buster
Feb 24 14:25:38 zynthian startx[7982]: Kernel Version: 5.15.70-v7l+
Feb 24 14:25:38 zynthian startx[7982]: ZynthianOS Version: 2211
Feb 24 14:25:38 zynthian startx[7982]: Virtualization: none
Feb 24 14:25:38 zynthian startx[7982]: Hardware Architecture: armv7l
Feb 24 14:25:38 zynthian startx[7982]: Hardware Model: Raspberry Pi 4 Model B Rev 1.2
Feb 24 14:25:38 zynthian startx[7982]: ----------------------------------------------
Feb 24 14:25:39 zynthian startx[7982]: ZynCore: Setting-up 8 x Zynswitches…
Feb 24 14:25:39 zynthian startx[7982]: ZynCore: Setting-up 4 x Zynpots (zyncoders)…
Feb 24 14:25:41 zynthian startx[7982]: Started libzynmixer
Feb 24 14:25:41 zynthian startx[7982]: Started libzynseq
Feb 24 14:25:43 zynthian startx[7982]: Started libzynsmf


Since it’s basically wiped, I could flash the stable image again and try to capture the issue for debugging purposes if you wish.

I did see the red Error screen a couple times when it was cycling through the UI reboots.

It’s stable now.