I can’t speak about SparkyLinux, but will say Debian GNU/Linux bookworm (or testing) is using the LXQt of Lubuntu 21.04 which is EOL (two releases ago), and I suspect that’s the LXQt you maybe using in Sparky.
It’s some Lubuntu members that are currently involved upstream in pushing the LXQt 1.1 available for some time to Lubuntu kinetic or via backports to existing Lubuntu jammy, or 22.04 users, to Debian sid (you’ll see parts of currently in experimental) so we’re [Lubuntu] back in sync with Debian.
The Debian intention from Simon/@tsimonq2 to Debian/LXQt highlights this
I intend on updating the entire LXQt stack to the latest version on June 30, 2022 (this is when I plan on uploading to Sid).
The entire stack builds, installs, and works in the Ubuntu development release. I would like to completely eliminate the vast majority of Ubuntu deltas.
Lubuntu & Debian are different distributions yes, but we do try and work together when we can, as that is work that benefits us both & reduces overall workload. (The LXQt release in Lubuntu 22.04 LTS had intended to be LXQt 1.0 from Debian, but they were unable to get it there & we ran out of time if you recall; thus were pushing LXQt 1.1 there ourselves)
lxqt-about | 0.17.0-0ubuntu1 | jammy/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
lxqt-about | 1.1.0-2 | kinetic/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
lxqt-about | 0.16.0-1 | stable | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
lxqt-about | 0.16.0-1 | testing | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
lxqt-about | 0.16.0-1 | unstable | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
lxqt-about | 0.16.0-1 | unstable-debug | source
lxqt-about | 1.1.0-2 | experimental | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
lxqt-about | 1.1.0-2 | experimental-debug | source