Frank

> `pkg2appimage` was working fine on arch until the release of `glib2 2.70` (I think). I've opened a [PR](https://github.com/AppImage/pkg2appimage/pull/500) that should fix this problem :)

Removing `libgmodule-2.0.so.0*` from `usr/lib/x86_64-linux-gnu` should be enough, because that's what causes the issue. I've linked a very in depth analysis of the problem in the PR. The analysis also mentions...

That's because of the new glib 2.70 :( Here you can find a very good analysis of the problem: https://github.com/project-slippi/Ishiiruka/issues/323 As a workaround for now, you can start SmuView like...

Could you please start SmuView (and sigrok-cli) with the option `-l 5` and provide the output. Maybe this will give a hint what the problem is.

I will add this to my ToDo list :)

The Maynuo M9812 is already supported by libsigrok and can be connected to SmuView, but the driver needs some small modifications (adding a mutex to make the driver thread safe)...

For reference: Here I've already added the mutex for an other modbus device: https://github.com/sigrokproject/libsigrok/commit/7c0891b0b82049b4cc3c0dd70b8483d037dab36f The modifications to the Maynuo driver should be similar.

This is a known problem with the underlying libsigrok or libserialport, but it's not very high on my priority list atm :) A workaround is to disconnect the device in...

Could you please start SmuView with full log output and attach the whole output here? This is for connecting the load with the (factory) default serial settings (9600/8n1). Maybe you...

Fixed :) The cause of this issue was, that SmuView couldn't handle the unexpected AC flag for the power channel. Now signals can be added to "fixed" channels: https://github.com/knarfS/smuview/commit/ca7951b2cc9db614c152123171960b883aaa9bc5 And...