# Vangelis Stable, shutdown/reboot no longer works depending on snapshot

**URL:** <https://discourse.zynthian.org/t/vangelis-stable-shutdown-reboot-no-longer-works-depending-on-snapshot/13790>\
**Category:** Software\
**Tags:** vangelis\
**Created:** [October 25, 2026, 8:59am UTC](https://discourse.zynthian.org/t/vangelis-stable-shutdown-reboot-no-longer-works-depending-on-snapshot/13790 "2026-10-25T08:59:02Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![HansR](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/hansr/32/15102_2.png) [@HansR](https://discourse.zynthian.org/u/HansR)\
**Post date:** [October 25, 2026, 8:59am UTC](https://discourse.zynthian.org/t/vangelis-stable-shutdown-reboot-no-longer-works-depending-on-snapshot/13790/1 "2026-10-25T08:59:02Z")

</div>

I’m installing Vangelis Stable on my 5.1 kit.

Until now everything worked as expected.  
But after changing some settings in `Webconf Hardware Wiring` Zynthian no longer shuts down properly but restarts on an error 134.

When stopping Zynthian service the following message appears in the log, apparently there is a corrupted pointer somewhere.

```auto
Oct 25 08:36:40 zynthian systemd[1]: Stopping zynthian.service - Zynthian User Interface...
Oct 25 08:36:41 zynthian startx[2045]: ====================== ZYNSEQ MIMALLOC STATS ====================
Oct 25 08:36:41 zynthian startx[2045]: heap stats: peak total freed current unit count
Oct 25 08:36:41 zynthian startx[2045]: reserved: 1.0 GiB 1.0 GiB 64.2 KiB 1.0 GiB
Oct 25 08:36:41 zynthian startx[2045]: committed: 3.4 MiB 3.6 MiB 2.0 MiB 1.6 MiB
Oct 25 08:36:41 zynthian startx[2045]: reset: 0
Oct 25 08:36:41 zynthian startx[2045]: purged: 1.9 MiB
Oct 25 08:36:41 zynthian startx[2045]: touched: 0 0 0 0 ok
Oct 25 08:36:41 zynthian startx[2045]: pages: 745 745 0 745
Oct 25 08:36:41 zynthian startx[2045]: -abandoned: 9 287 278 9 not all freed
Oct 25 08:36:41 zynthian startx[2045]: -reclaima: 5
Oct 25 08:36:41 zynthian startx[2045]: -reclaimf: 0
Oct 25 08:36:41 zynthian startx[2045]: -reabandon: 0
Oct 25 08:36:41 zynthian startx[2045]: -waits: 0
Oct 25 08:36:41 zynthian startx[2045]: -extended: 0
Oct 25 08:36:41 zynthian startx[2045]: -noretire: 0
Oct 25 08:36:41 zynthian startx[2045]: arenas: 1
Oct 25 08:36:41 zynthian startx[2045]: -purges: 4
Oct 25 08:36:41 zynthian startx[2045]: mmap calls: 2
Oct 25 08:36:41 zynthian startx[2045]: -commit: 0
Oct 25 08:36:41 zynthian startx[2045]: -reset: 0
Oct 25 08:36:41 zynthian startx[2045]: -purge: 17
Oct 25 08:36:41 zynthian startx[2045]: guarded: 0
Oct 25 08:36:41 zynthian startx[2045]: threads: 1 2 2 0 ok
Oct 25 08:36:41 zynthian startx[2045]: searches: 0.0 avg
Oct 25 08:36:41 zynthian startx[2045]: numa nodes: 8
Oct 25 08:36:41 zynthian startx[2045]: elapsed: 796.877 s
Oct 25 08:36:41 zynthian startx[2045]: process: user: 68.167 s, system: 51.363 s, faults: 0, rss: 250.0 MiB, commit: 3.4 MiB
Oct 25 08:36:44 zynthian startx[2045]: zynmixer_bus mixbuses ended
Oct 25 08:36:44 zynthian startx[2045]: free(): invalid pointer
Oct 25 08:36:44 zynthian startx[1250]: ./zynthian.sh: line 381: 2045 Aborted ./zynthian_main.py
Oct 25 08:36:44 zynthian startx[1250]: *******************
Oct 25 08:36:44 zynthian startx[1250]: EXIT STATUS => 134
Oct 25 08:36:44 zynthian startx[1250]: *******************

```

I guess this has something to do with [this issue](https://discourse.zynthian.org/t/error-after-changing-p1-button-wiring-on-webconf-hardware-wiring-advanced/13655).

In the past I had a comparable problem that was fixed by running a `Webconf Update` again (even if there were no updates) but that no longer works.

I already went back to the original `Customization Profile` but that does not work either.

Any help would be greatly appreciated. I don’t want to re-flash the SD card as that would take more than 3 hours to configure everything. Plus when I am finished it starts all over…

Regards,  
Hans.

Edit: UI log is here:  
[UIlog.zip](https://discourse.zynthian.org/uploads/short-url/23ZVJ1nMc9R9jWfGUl2bQ2IS4TV.zip) (1.6 KB)

---

<div class="post-metadata">

**Author:** ![HansR](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/hansr/32/15102_2.png) [@HansR](https://discourse.zynthian.org/u/HansR)\
**Post date:** [October 26, 2026, 11:14am UTC](https://discourse.zynthian.org/t/vangelis-stable-shutdown-reboot-no-longer-works-depending-on-snapshot/13790/2 "2026-10-26T11:14:22Z")

</div>

It looks like this is not only caused by a wiring change, but is dependent on the snapshot that is loaded.  
For some snapshots the shutdown/reboot is performed normal, for others it is not and runs in an `invalid pointer error 134`.

These two prevent normal shutdown:  
[Snapshots.zip](https://discourse.zynthian.org/uploads/short-url/3SuzMCEwosZoPlogxWb0V1msYuZ.zip) (11.7 KB)

This problem occurs only on my official V5.1 Kit. On the V5 clone everything works normal.

 ![image](https://discourse.zynthian.org/uploads/default/original/3X/5/5/55e62f86ac0a4b626e827f870919354167c10450.png)

---

<div class="post-metadata">

**Author:** ![HansR](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/hansr/32/15102_2.png) [@HansR](https://discourse.zynthian.org/u/HansR)\
**Post date:** [October 26, 2026, 1:42pm UTC](https://discourse.zynthian.org/t/vangelis-stable-shutdown-reboot-no-longer-works-depending-on-snapshot/13790/3 "2026-10-26T13:42:24Z")

</div>

I thought the problem was solved when I removed the `.backup` directory and `last_state.zss`, but the problem has returned.

It’s a pity the only message was `invalid pointer` because that is almost impossible to trace.

---

<div class="post-metadata">

**Author:** ![travelrec](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/travelrec/32/11382_2.png) [@travelrec](https://discourse.zynthian.org/u/travelrec)\
**Post date:** [October 26, 2026, 2:57pm UTC](https://discourse.zynthian.org/t/vangelis-stable-shutdown-reboot-no-longer-works-depending-on-snapshot/13790/4 "2026-10-26T14:57:55Z")

</div>

Got the same issue on a beta to stable update. After using a fresh image, the issue is no longer present.  
Reported also here: [ZynthianOS Vangelis Stable 2610 is released - #15 by travelrec](https://discourse.zynthian.org/t/zynthianos-vangelis-stable-2610-is-released/13765/15)

---

<div class="post-metadata">

**Author:** ![HansR](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/hansr/32/15102_2.png) [@HansR](https://discourse.zynthian.org/u/HansR)\
**Post date:** [October 26, 2026, 5:20pm UTC](https://discourse.zynthian.org/t/vangelis-stable-shutdown-reboot-no-longer-works-depending-on-snapshot/13790/5 "2026-10-26T17:20:09Z")

</div>

~~For me it’s the opposite. The update from beta to stable works fine, the fresh image has the problem.~~

Now both have the same problem 😭.

There is some weird bug that reacts to snapshots (and is perhaps(?) triggered by wiring changes).

I think I’ll go back to Oram for the time being.

---

<div class="post-metadata">

**Author:** ![travelrec](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/travelrec/32/11382_2.png) [@travelrec](https://discourse.zynthian.org/u/travelrec)\
**Post date:** [October 26, 2026, 7:19pm UTC](https://discourse.zynthian.org/t/vangelis-stable-shutdown-reboot-no-longer-works-depending-on-snapshot/13790/6 "2026-10-26T19:19:37Z")

</div>

Then, I think, it is triggered by any internal chain, FX, whatever setting and the image itself doesn’t matter whether it’s a fresh or updated one.