Device registration broken with certain actions present in profiles
Moving discussion from #OpenDeck on Arch Linux
8 Replies
So this is what I've understood @Percy_Ikana:
- 2.whatever you were on before works
- 2.2.1 from AUR is working fine
- 2.3.0 AppImage is blank (could you try the steps in #25?)
- 2.3.1/-git device does not register
That means 13860cd (a commit you said worked https://discord.com/channels/1143819637897834571/1143819638732505130/1306023316959789117) and below are safe, bug introduced somewhere later than that
I think that seeing whether 2.3.0 works or not would be the next most productive step, and if you can't get the AppImage working in a couple of minutes then building from source will be helpful anyway so that we can go back commit by commit very easily (
git reset --hard HEAD~1
)
Commands to run from source:
- git clone --recurse-submodules https://github.com/ninjadev64/OpenDeck.git
- cd OpenDeck
- deno install
- deno task tauri build
@Terrorwolf as well sorry@Percy_Ikana Is it all Materialdeck actions or just certain? And with what configuration of the button does it happen?
While terrorwolf's suggestion is not unhelpful I do request that we first try determining the opendeck commit in which this started occurring because it will be much easier for me to resolve the issue that way - ultimately, this is an opendeck bug and not a material deck one, whether certain MD actions work or not may simply be coincidence, as well as the fact that this issue almost certainly concerns other plugins
I am just asking, because with my pc its not yet reproducible and I had hoped that maybe with a specific setting I can force the problem. Maybe we can also find a helpful information when my VM is ready.
Yes, when I get back to my computer I will attempt to get 2.3.0 working, (what is #25 in this context)
Thank you both for helping
no problem
#25 is GitHub issue 25, it's to do with blank windows
Thanks.