All presets are empty after update to 2.0.109

[mockbot]

Sorry, but after update to 2.0.109, all presets are empty.
Fallback to 2.0.108 shows again all presets.

I've cleaned all previous packages and tried 2.0.109 again and I've noticed, that own presets still exists...
(sudo rm -rf /etc/pipedal).

Are there any locations, which need to cleaned or checked? Browser cache ? I've used several other browsers.

any idea?

[FoolHen]

/etc/pipedal is for pipedal storage, /var/pipedal is for user storage (your custom presets, downloads etc). Are there errors in the web console? or in pipedal logs (run journalctl -u pipedald -n 100)

[mockbot]

I've purged pipedal (apt purge pipedal) cleaned up /etc/pipedal and /var/pipedal () rm -rf /etc/pipedal /var/pipedal) and rebooted. After installing 2.0.109 (AMD) and configuring alsa devices, it is still the same issue with empty presets. It looks like 2.0.108 with access from other different subnet, the backend cannot be accessed. Please find attached the journalctl output, where you can find some core dumps... Jul 21 22:30:45 nam systemd[1]: Started *pipedal*d.service - PiPedal Web Service. Jul 21 22:30:45 nam *pipedal*d[5004]: Found ALSA device hw:USB. Jul 21 22:30:45 nam *pipedal*d[5004]: Audio started. ALSA, hw:USB, 32-bit integer little-endian, 48000, 64x3, device: 2/2, main: 1/2, aux: 0/0 Jul 21 22:30:45 nam systemd[1]: *pipedal*d.service: Main process exited, code=dumped, status=4/ILL Jul 21 22:30:45 nam systemd[1]: *pipedal*d.service: Failed with result 'core-dump'. Jul 21 22:30:50 nam systemd[1]: *pipedal*d.service: Scheduled restart job, restart counter is at 24. Jul 21 22:30:50 nam systemd[1]: Starting *pipedal*d.service - PiPedal Web Service... Jul 21 22:30:50 nam *pipedal*d[5021]: Document root: /etc/*pipedal*/config Threads: 5 Jul 21 22:30:50 nam *pipedal*d[5021]: Locale: de_DE Jul 21 22:30:50 nam *pipedal*d[5021]: Updater: Next update check at 2026-07-22 06:08:33 Jul 21 22:30:50 nam *pipedal*d[5021]: Scanning for LV2 Plugins Jul 21 22:30:50 nam systemd[1]: Started *pipedal*d.service - PiPedal Web Service. Jul 21 22:30:50 nam *pipedal*d[5021]: Found ALSA device hw:USB. Jul 21 22:30:50 nam *pipedal*d[5021]: CrashGuard: Detected previous crash, count = 1 Jul 21 22:30:50 nam *pipedal*d[5021]: Audio started. ALSA, hw:USB, 32-bit integer little-endian, 48000, 64x3, device: 2/2, main: 1/2, aux: 0/0 Jul 21 22:30:51 nam systemd[1]: *pipedal*d.service: Main process exited, code=dumped, status=4/ILL Jul 21 22:30:51 nam systemd[1]: *pipedal*d.service: Failed with result 'core-dump'. Jul 21 22:30:56 nam systemd[1]: *pipedal*d.service: Scheduled restart job, restart counter is at 25. Jul 21 22:30:56 nam systemd[1]: Starting *pipedal*d.service - PiPedal Web Service... Jul 21 22:30:56 nam *pipedal*d[5036]: Document root: /etc/*pipedal*/config Threads: 5 Jul 21 22:30:56 nam *pipedal*d[5036]: Locale: de_DE Jul 21 22:30:56 nam *pipedal*d[5036]: Updater: Next update check at 2026-07-22 06:08:33 Jul 21 22:30:56 nam *pipedal*d[5036]: Scanning for LV2 Plugins Jul 21 22:30:56 nam systemd[1]: Started *pipedal*d.service - PiPedal Web Service. Jul 21 22:30:56 nam *pipedal*d[5036]: Found ALSA device hw:USB. Jul 21 22:30:56 nam *pipedal*d[5036]: CrashGuard: Detected previous crash, count = 2 Jul 21 22:30:56 nam *pipedal*d[5036]: Audio started. ALSA, hw:USB, 32-bit integer little-endian, 48000, 64x3, device: 2/2, main: 1/2, aux: 0/0 Jul 21 22:30:57 nam systemd[1]: *pipedal*d.service: Main process exited, code=dumped, status=4/ILL Jul 21 22:30:57 nam systemd[1]: *pipedal*d.service: Failed with result 'core-dump'. Jul 21 22:31:02 nam systemd[1]: *pipedal*d.service: Scheduled restart job, restart counter is at 26. Jul 21 22:31:02 nam systemd[1]: Starting *pipedal*d.service - PiPedal Web Service... Jul 21 22:31:02 nam *pipedal*d[5052]: Document root: /etc/*pipedal*/config Threads: 5 Jul 21 22:31:02 nam *pipedal*d[5052]: Locale: de_DE Jul 21 22:31:02 nam *pipedal*d[5052]: Updater: Next update check at 2026-07-22 06:08:33 Jul 21 22:31:02 nam *pipedal*d[5052]: Scanning for LV2 Plugins Jul 21 22:31:02 nam systemd[1]: Started *pipedal*d.service - PiPedal Web Service. Jul 21 22:31:02 nam *pipedal*d[5052]: Found ALSA device hw:USB. Jul 21 22:31:02 nam *pipedal*d[5052]: CrashGuard: Detected previous crash, count = 3 Jul 21 22:31:02 nam *pipedal*d[5052]: Audio started. ALSA, hw:USB, 32-bit integer little-endian, 48000, 64x3, device: 2/2, main: 1/2, aux: 0/0 Jul 21 22:31:02 nam systemd[1]: *pipedal*d.service: Main process exited, code=dumped, status=4/ILL Jul 21 22:31:02 nam systemd[1]: *pipedal*d.service: Failed with result 'core-dump'. Jul 21 22:31:07 nam systemd[1]: *pipedal*d.service: Scheduled restart job, restart counter is at 27. Jul 21 22:31:07 nam systemd[1]: Starting *pipedal*d.service - PiPedal Web Service... Jul 21 22:31:07 nam *pipedal*d[5067]: Document root: /etc/*pipedal*/config Threads: 5 Jul 21 22:31:07 nam *pipedal*d[5067]: Locale: de_DE Jul 21 22:31:07 nam *pipedal*d[5067]: Updater: Next update check at 2026-07-22 06:08:33 Jul 21 22:31:07 nam *pipedal*d[5067]: Scanning for LV2 Plugins Jul 21 22:31:08 nam systemd[1]: Started *pipedal*d.service - PiPedal Web Service. Jul 21 22:31:08 nam *pipedal*d[5067]: Found ALSA device hw:USB. Jul 21 22:31:08 nam *pipedal*d[5067]: CrashGuard: Detected previous crash, count = 4 Jul 21 22:31:08 nam *pipedal*d[5067]: Audio started. ALSA, hw:USB, 32-bit integer little-endian, 48000, 64x3, device: 2/2, main: 1/2, aux: 0/0 Jul 21 22:31:08 nam systemd[1]: *pipedal*d.service: Main process exited, code=dumped, status=4/ILL Jul 21 22:31:08 nam systemd[1]: *pipedal*d.service: Failed with result 'core-dump'. Jul 21 22:31:13 nam systemd[1]: *pipedal*d.service: Scheduled restart job, restart counter is at 28. Jul 21 22:31:13 nam systemd[1]: Starting *pipedal*d.service - PiPedal Web Service... Jul 21 22:31:13 nam *pipedal*d[5082]: Document root: /etc/*pipedal*/config Threads: 5 Jul 21 22:31:13 nam *pipedal*d[5082]: Locale: de_DE Jul 21 22:31:13 nam *pipedal*d[5082]: Updater: Next update check at 2026-07-22 06:08:33 Jul 21 22:31:13 nam *pipedal*d[5082]: Scanning for LV2 Plugins Jul 21 22:31:13 nam systemd[1]: Started *pipedal*d.service - PiPedal Web Service. Jul 21 22:31:13 nam *pipedal*d[5082]: Found ALSA device hw:USB. Jul 21 22:31:13 nam *pipedal*d[5082]: CrashGuard: Detected previous crash, count = 5 Jul 21 22:31:13 nam *pipedal*d[5082]: Audio started. ALSA, hw:USB, 32-bit integer little-endian, 48000, 64x3, device: 2/2, main: 1/2, aux: 0/0 Jul 21 22:31:13 nam *pipedal*d[5082]: Listening on mDns address nam.local:80 Jul 21 22:31:13 nam *pipedal*d[5082]: Listening on Wi-Fi address 10.17.42.155:80 Jul 21 22:31:14 nam *pipedal*d[5082]: DNS/SD service announced. (*pipedal*) Jul 21 22:31:14 nam *pipedal*d[5082]: DNS/SD group established. Jul 21 22:31:19 nam *pipedal*d[5082]: WebSocketSession opened. ([::ffff:10.17.42.178]:51766) Am Di., 21. Juli 2026 um 12:03 Uhr schrieb Fulgen ***@***.***

…

: *FoolHen* left a comment (rerdavies/pipedal#537) <#537 (comment)> /etc/pipedal is for pipedal storage, /var/pipedal is for user storage (your custom presets, downloads etc). Are there errors in the web console? or in pipedal logs (run journalctl -u pipedald -n 100) — Reply to this email directly, view it on GitHub <#537?email_source=notifications&email_token=AAIRDAFQGFP7UW2GYZPTIR35F45YTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBTGI3DKMJUGIZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5032651423>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIRDADEE7PDXWIJ3U4UT235F45YTAVCNFSNUABFKJSXA33TNF2G64TZHMZTSNRTHE4DGNJTHNEXG43VMU5TIOJTGA2DCNJYGEZ2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AAIRDACOG25C3RKRREXBZRL5F45YTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBTGI3DKMJUGIZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AAIRDAGIDBTZSXT3IWE5PDD5F45YTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBTGI3DKMJUGIZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[ac1176]

There might be an issue with 2.0.109 - it doesn't appear to be available to download from github at the moment.

I'd stick with 2.0.108 for now. It's still available on the releases page.

[rerdavies]

Apologies. I'm away on vacation. With limited connectivity.

I retracted the 109 release for the moment, because of the preset upgrade problem. t I will take a look at it as soon as I get back on Friday. In the meantime, I would recommend that you use the 108 build, which of course does not have the fix for a cross subnet access that is in the 109 release.

[mockbot]

Enjoy your vacation first! Million thanks for your amazing private support!!! Am Mi., 22. Juli 2026 um 16:14 Uhr schrieb Robin Davies < ***@***.***>:

…

*rerdavies* left a comment (rerdavies/pipedal#537) <#537 (comment)> Apologies. I'm away on vacation. With limited connectivity. I retracted the 109 release for the moment, because of the preset upgrade problem. t I will take a look at it as soon as I get back on Friday. In the meantime, I would recommend that you use the 108 build, which of course does not have the fix for a cross subnet access that is in the 109 release. — Reply to this email directly, view it on GitHub <#537?email_source=notifications&email_token=AAIRDAFSMPCFLYQGLU2AQHD5GDD4TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBUG4ZDAOBVGM4KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5047208538>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIRDAHFWGUBXMJAJSPFKGT5GDD4TAVCNFSNUABFKJSXA33TNF2G64TZHMZTSNRTHE4DGNJTHNEXG43VMU5TIOJTGA2DCNJYGEZ2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AAIRDACU34MQFAOPQGDFXUL5GDD4TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBUG4ZDAOBVGM4KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AAIRDAFVKN6UMCLZQGLUJAL5GDD4TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBUG4ZDAOBVGM4KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[rerdavies]

@mockbot

Back, and catching up....

The empty presets occur because the PiPedal server has crashed more than five times consecutively. (It allows users to recover if they load a 3rd party plugin that crashes). And that's certainly what your logs indicate.

PiPedal seems to be executing an illegal instruction each time it tries to start up, most likely in plugin code, perhaps in the TooB Neural Amp Modeler plugin.

By design, after 5 crashes in a row, PiPedal deliberately chooses to NOT load the current preset, and shows an empty preset instead. And that seems to be what's in the logs. PiPedal has crashed 29 times since last reboot; and the portion of the logs you sent me indicate the Crash Guard count incrementing from 1 to 5, after which the service starts successfully, but with an empty preset.

My best theory: Toob Neural Amp Modeler has incorrectly decided that your processor supports AVX, and used the AVX-optimized dynamic library, instead of the non-AVX dynamic library. (AVX optimization is a new feature in v2.0.109).

First things first:

1. System info

What exact CPU are you using?

Run the following command:

cat /proc/cpuinfo  | grep 'name'| uniq

(PiPedal should run on pretty much any x64/amd64 processor, so don't panic).

2. Confirm that TooB NAM is running AVX code when it should not.

Install v2.0.109 from

https://rerdavies.github.io/pipedal/img/pipedal_2.0.109_amd64.deb

(since the 109 build has been retracted).

Delete the following file:

sudo rm /usr/lib/lv2/ToobAmp.lv2/bin/ToobAmp-x86-64-avx.so

This will cause TooB NAM to fall back to the non-AVX-optimized .so

Let me know whether that works.

[edit] In fact, it's a little bit more complicated. The "avx-enabled" .so also requires several other optional instruction sets, so it's possible that TooB NAM code has missed a corner case on an instruction set other than AVX256.

[rerdavies]

Supplementary question: Is the pipedal server running in a VM? It looks like there's a potential bug if PiPedal is running in some VM hosts. .

[mockbot]

Hello again and many thanks! The pipedal tests are all executed at a small physical ASUS PN40 device, no VM. cat /proc/cpuinfo | grep 'name'| uniq model name : Intel(R) Celeron(R) N4000 CPU @ 1.10GHz The device has 2 CPU cores, 4G memory cat /proc/meminfo |grep -i mem *Mem*Total: 3823956 kB *Mem*Free: 1658832 kB *Mem*Available: 2717316 kB Sh*mem*: 84532 kB Sh*mem*HugePages: 75776 kB Sh*mem*PmdMapped: 0 kB Am So., 26. Juli 2026 um 19:50 Uhr schrieb Robin Davies < ***@***.***>:

…

*rerdavies* left a comment (rerdavies/pipedal#537) <#537 (comment)> Supplementary question: Is the pipedal server running in a VM? It looks like there's a potential bug if PiPedal is running in a some VM hosts. . — Reply to this email directly, view it on GitHub <#537?email_source=notifications&email_token=AAIRDACKFMO5POLIVLZTXTL5GZAIFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBYGQ3DONBQGUY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5084674051>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIRDAEREA7QXXKQXKUFRET5GZAIFAVCNFSNUABFKJSXA33TNF2G64TZHMZTSNRTHE4DGNJTHNEXG43VMU5TIOJTGA2DCNJYGEZ2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AAIRDAGC6BICD2U6LBV2UY35GZAIFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBYGQ3DONBQGUY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/AAIRDABVNJOF3IIVTPCVGUD5GZAIFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBYGQ3DONBQGUY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[mockbot]

I've noticed the following issue between pipedal versions: pipedal_2.0.108_amd64.deb installs -rw-r--r-- 1 root root 6341032 Jun 29 20:58 ToobAmp-x86-64-avx.so -rw-r--r-- 1 root root 5515896 Jun 29 21:00 ToobAmp-x86-64.so *pipedal_2.0.109_amd64.deb installs the avx lib only -rw-r--r-- 1 root root 5823160 Jul 17 20:40 ToobAmp-x86-64-avx.so Your suggestion: sudo rm /usr/lib/lv2/ToobAmp.lv2/bin/ToobAmp-x86-64-avx.so This will cause TooB NAM to fall back to the non-AVX-optimized .so Will this fail, because of missing ToobAmp-x86-64.so ??? Am Mo., 27. Juli 2026 um 08:16 Uhr schrieb Christian Mock < ***@***.***>:

…

Hello again and many thanks! The pipedal tests are all executed at a small physical ASUS PN40 device, no VM. cat /proc/cpuinfo | grep 'name'| uniq model name : Intel(R) Celeron(R) N4000 CPU @ 1.10GHz The device has 2 CPU cores, 4G memory cat /proc/meminfo |grep -i mem *Mem*Total: 3823956 kB *Mem*Free: 1658832 kB *Mem*Available: 2717316 kB Sh*mem*: 84532 kB Sh*mem*HugePages: 75776 kB Sh*mem*PmdMapped: 0 kB Am So., 26. Juli 2026 um 19:50 Uhr schrieb Robin Davies < ***@***.***>: > *rerdavies* left a comment (rerdavies/pipedal#537) > <#537 (comment)> > > Supplementary question: Is the pipedal server running in a VM? It looks > like there's a potential bug if PiPedal is running in a some VM hosts. . > > — > Reply to this email directly, view it on GitHub > <#537?email_source=notifications&email_token=AAIRDACKFMO5POLIVLZTXTL5GZAIFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBYGQ3DONBQGUY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5084674051>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAIRDAEREA7QXXKQXKUFRET5GZAIFAVCNFSNUABFKJSXA33TNF2G64TZHMZTSNRTHE4DGNJTHNEXG43VMU5TIOJTGA2DCNJYGEZ2C5QC> > . > Triage notifications, keep track of coding agent tasks and review pull > requests on the go with GitHub Mobile for iOS > <https://github.com/notifications/mobile/ios/AAIRDAGC6BICD2U6LBV2UY35GZAIFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBYGQ3DONBQGUY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> > and Android > <https://github.com/notifications/mobile/android/AAIRDABVNJOF3IIVTPCVGUD5GZAIFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBYGQ3DONBQGUY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. > Download it today! > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[rerdavies]

[edit:] Huh. Let me look at that and get back to you.

[rerdavies]

Good catch, thanks. The .109 release wasn't build properly. Fix coming up.

[mockbot]

hmmm, I did not 100% understand your answer... sorry... how is the fallback possible, when ToobAmp-x86-64.so is not available? like at 2.0.109 debian package, it is not installed. FYI: I've installed pipedal 2.0.109 on another Intel NUC i5 (4 cores, 16GB mem, 500GB SSD) and it works perfectly!!! model name : Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz My personal private issue with this NUC, it has an internal fan and I did not like the noise ;-( Congratulations!!!!! access from different subnets via firewall works now as expected!!!! :-) PERFECT JOB! Million thanks!!!!!!!!!!! Am Mo., 27. Juli 2026 um 14:14 Uhr schrieb Robin Davies < ***@***.***>:

…

*rerdavies* left a comment (rerdavies/pipedal#537) <#537 (comment)> The code always falls back to ToobAmp-x86-64.so. Either because the processor doesn't meet instruction set requirements, or because the *.-avx.so file is missing.That's the point of the test: to force the plugin to use the non-avx binaries. On Mon, Jul 27, 2026 at 2:31 AM Christian Mock ***@***.***> wrote: > *mockbot* left a comment (rerdavies/pipedal#537) > <#537 (comment)> > I've noticed the following issue between pipedal versions: > > pipedal_2.0.108_amd64.deb installs > > > -rw-r--r-- 1 root root 6341032 Jun 29 20:58 ToobAmp-x86-64-avx.so > > -rw-r--r-- 1 root root 5515896 Jun 29 21:00 ToobAmp-x86-64.so > > > *pipedal_2.0.109_amd64.deb installs* > > > -rw-r--r-- 1 root root 5823160 Jul 17 20:40 ToobAmp-x86-64-avx.so > > > > Your suggestion: > > sudo rm /usr/lib/lv2/ToobAmp.lv2/bin/ToobAmp-x86-64-avx.so > This will cause TooB NAM to fall back to the non-AVX-optimized .so > > Will this fail, because of missing ToobAmp-x86-64.so ??? > > > > Am Mo., 27. Juli 2026 um 08:16 Uhr schrieb Christian Mock < > ***@***.***>: > > > Hello again and many thanks! > > > > The pipedal tests are all executed at a small physical ASUS PN40 device, > > no VM. > > cat /proc/cpuinfo | grep 'name'| uniq > > > > model name : Intel(R) Celeron(R) N4000 CPU @ 1.10GHz > > > > > > The device has 2 CPU cores, 4G memory > > > > cat /proc/meminfo |grep -i mem > > > > *Mem*Total: 3823956 kB > > > > *Mem*Free: 1658832 kB > > > > *Mem*Available: 2717316 kB > > > > Sh*mem*: 84532 kB > > > > Sh*mem*HugePages: 75776 kB > > > > Sh*mem*PmdMapped: 0 kB > > > > > > > > Am So., 26. Juli 2026 um 19:50 Uhr schrieb Robin Davies < > > ***@***.***>: > > > >> *rerdavies* left a comment (rerdavies/pipedal#537) > >> < > #537 (comment)> > >> > >> Supplementary question: Is the pipedal server running in a VM? It looks > >> like there's a potential bug if PiPedal is running in a some VM hosts. > . > >> > >> — > >> Reply to this email directly, view it on GitHub > >> < > #537?email_source=notifications&email_token=AAIRDACKFMO5POLIVLZTXTL5GZAIFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBYGQ3DONBQGUY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5084674051>, > > >> or unsubscribe > >> < > https://github.com/notifications/unsubscribe-auth/AAIRDAEREA7QXXKQXKUFRET5GZAIFAVCNFSNUABFKJSXA33TNF2G64TZHMZTSNRTHE4DGNJTHNEXG43VMU5TIOJTGA2DCNJYGEZ2C5QC> > > >> . > >> Triage notifications, keep track of coding agent tasks and review pull > >> requests on the go with GitHub Mobile for iOS > >> < > https://github.com/notifications/mobile/ios/AAIRDAGC6BICD2U6LBV2UY35GZAIFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBYGQ3DONBQGUY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> > > >> and Android > >> < > https://github.com/notifications/mobile/android/AAIRDABVNJOF3IIVTPCVGUD5GZAIFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBYGQ3DONBQGUY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. > > >> Download it today! > >> You are receiving this because you were mentioned.Message ID: > >> ***@***.***> > >> > > > > — > Reply to this email directly, view it on GitHub > < #537?email_source=notifications&email_token=ACXK2DEPN5TCRX3DLUXFA7L5G3ZM3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBYHAYDIMJYGY42M4TFMFZW63VGNVQW45LBNSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5088041869>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/ACXK2DC74J433A5HX4W24L35G3ZM3AVCNFSNUABFKJSXA33TNF2G64TZHMZTSNRTHE4DGNJTHNEXG43VMU5TIOJTGA2DCNJYGEZ2C5QC> > . > Triage notifications, keep track of coding agent tasks and review pull > requests on the go with GitHub Mobile for iOS > < https://github.com/notifications/mobile/ios/ACXK2DFKATG3XM5A7XYY6TT5G3ZM3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBYHAYDIMJYGY42M4TFMFZW63VGNVQW45LBNSSWK5TFNZ2KUZTPN52GK4S7NFXXG> > and Android > < https://github.com/notifications/mobile/android/ACXK2DD6QF4JMS6TBXPIJA35G3ZM3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBYHAYDIMJYGY42M4TFMFZW63VGNVQW45LBNSSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. > Download it today! > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> > — Reply to this email directly, view it on GitHub <#537?email_source=notifications&email_token=AAIRDAFEU5FCXFMCBEDZ6RD5G5BRRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBZGEYTINBVGAY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5091144501>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIRDAFTQ4N7LKWNDTJYVUT5G5BRRAVCNFSNUABFKJSXA33TNF2G64TZHMZTSNRTHE4DGNJTHNEXG43VMU5TIOJTGA2DCNJYGEZ2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AAIRDAGBM3DKKZAU46S2KA35G5BRRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBZGEYTINBVGAY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/AAIRDACHMEG6VAPCDDMWEXL5G5BRRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBZGEYTINBVGAY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>