Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
MX is not a rolling distribution, so MX-21 will not get Qt updated.
We are based on debian stable, so the next version after bookworm becomes stable will most likely have Qt 5.15.8
However I also notice that debian has backported some Qt crash related fixes into their 5.15.8 from upstream, so the problem may be resolved before the bookworm release.
timkb4cq wrote: Mon Feb 20, 2023 11:18 amHowever I also notice that debian has backported some Qt crash related fixes into their 5.15.8 from upstream, so the problem may be resolved before the bookworm release.
https://bugs.debian.org/cgi-bin/pkgrepo ... source-src
For closed bugs select "archived" in misc options near the bottom of the page.
It's kinda dense reading and there are lots of old bugs from versions prior to 5.15.4 so look at the higher numbers first.
Since bookworm won't include nvida-legacy-340.x there won't be bugs referencing it - but that sort of crash will probably be triggered by other software that uses the same calls.
timkb4cq wrote: Mon Feb 20, 2023 6:37 pm
Since bookworm won't include nvida-legacy-340.x there won't be bugs referencing it - but that sort of crash will probably be triggered by other software that uses the same calls.
Thanks!
They drop 340.108 at stable but still support it at sid officially, why they ignore such bugs?
Sid isn't really supported. It's other name is Unstable. It's where most packages start out in debian (some start in experimental before maybe making it to sid). When they work out enough bugs they move to Testing. Not every package makes it.
The debian versions (bullseye, buster, stretch, woody, etc) are named after characters in the Toy Story movies. Sid was the kid who liked to break toys. You use Sid at your own risk.
Ok:) Thanks!
I mean that officially Sid yet have support 340.108 but bullseye not. And i am interesting what chance that Qt 5.15.4 - 5.15.8 and 340.108 driver will fix in future?