Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
It does not work headless. I built from repo yesterday and did not get it to work. Works with X forwarding, which I can only temporary use. Thought it was something wrong with my build environment. Downloaded .deb today, same thing. Locks and needs to be killed, when looking with strace just sitting waiting on a futex.
Debugging info gave little, locks output at different places.
Copying old libde_rest_plugin.so gets it working again.
Raspberry 3, raspbian buster. Conbee I.
I cut and pasted your line.
This is exceptionally wierd because if I open a terminal from another raspberry running KDE, I don't even get that error message and deconz needs to be killed. From my workstation I get clean shutdown after error message. Very odd. Must be som env at play. Attaching output:
Edit: Again, replacing the plugin with .69 solves it.
This is the vanilla version from your .deb
I used to be a developer some decade ago, so I’m a bit rusty. Can some qt version screw it up?
How do I check out the .69 version with git?
By “replacing the plugin” I mean that I copy the .so file from the .69 deb to plugins/ , starts right up.
@manup It's difficult to say for me, since I don't know the code and don't have the source for the launcher, can't run it in a debugger.
Something happens when it tries to reconnect. It starts looking for ttyS0 and so on. When finally connecting to ttyUSB0 it triggers. I am wildly guessing that maybe the Qapp restarts and the option -platform which is not a standard longopts gets tossed.
Is there a option for device? --device= does not work..
Anyway, if I rename ttyUSB0 to ttyS0 so it connects straight away, the bug is not triggered.
Edit: Ah, see that you already figured it out in #2020