LXQt will be broken in the next few days because of a general namespace fix - both siduction and debian - so unless one would have fun don't upgrade the LXQt packages (including qlipper, screengrab and pcmanfm-qt) - i will post if the upgrade of LXQt Packages is save again so stay tuned. Btw - If one break his installation there is no snapshot nor support - your only chance will be the local apt cache. if it don't work the only other option is: Patience.
Bitte LXQt in den nächsten Tagen nicht upgraden, wir (Upstream) haben uns getraut, den LXQt-Namespace zu fixen. Es wird also Kleinholz geben. Ich geb Entwarnung, wenn die Umstellung durch ist - btw, falls Ihr Euch die Installation zerschießen solltet, dann habt Ihr halt Pech, die einzige Chance sind dann lokale Pakete im apt-cache und es wird keine weitere Hilfestellung ausser die beruhigenden Worte: 'Abwarten und Tee trinken!' geben
New packages are uploaded - if LXQt don't work for you that may be a upstream fault :)
Could we hope to get new thunderstruck (64/32) images? ;-)
A dist-upgrade today with some lxqt items did not fix the losses (panel, lxqt keyboard shortcuts, etc.) that yesterdays dist-upgrade caused. Selecting the Openbox wm via sddm is also missing the keyboard shortcuts. However it happened in testing (SparkyLinux uses lxqt siduction repos) on a 686 atom netbook. Maybe tomorrow it will fix itself.
Dist-upgrades in testing have been uneventful these few weeks, but the numbers of updates and upgrades is on the rise.
lxqt working quite well for me in siduction, but I have done no dist-upgrades since August01, no apt-get upgrade since about August04 and just apt update and selected apt-get install "foo" after investigating foo.
Sidenote - I just want to say I really like lxqt and it's development.
Lxqt seems to be back as it was a few weeks ago. I have just noticed ( may have been there before) that "configure application menu" lets you choose the menu file, this has now sorted my menu out, removing entries for applications that I had removed and adding new ones I had installed, looking good.
Sparky uses the siduction repos for lxqt. My little atom that also has lxqt reverted back to having the lxqtpanel and the keybindings resumed working after the gcc++ transition went through testing. Working for me also there.
I suppose I will dist-upgrade my siduction lxqt for the first time since August one of these days.