For details of LXQt 1.1.0, please refer to the release announcement, as it includes many improvements and changes.
Download a daily and test. You can install the system on a spare machine if you have one, or just use it in a live session without installation. If you don’t have a spare machine, a VM will work too. All testing is welcome.
Lubuntu member David (KGIII/uninvolved) has written about his own beta testing here on linux-tips and it’s worth a read.
You can download the Kinetic Kudu daily build here.
To record your testing, you’ll need a Launchpad/Ubuntu One login. Go here to create one if you haven’t already got one.
To look at all teams testsuites for jammy, though our install testcases can be found here, and the primary ISO and QA testing tracker can be found here. Please note we aren’t yet ready for recording kinetic results on our own checklist yet, but they are recorded on the iso.qa.ubuntu.com website. We’ll start recording on the testing checklist later in the development cycle; right now our focus is finding issues in the new LXQt 1.1.0.
Our normal behavior when we run a QA-test install is to use the “Install using Calamares (entire disk)” testcase, where in the Comments section we use the first line to briefly list hardware used, the second line has an entry describing the testcase tested, like
Lenovo YG SL 7 14ITL05 i5-1135G7,16GB,Intel Iris Xe,WiFi, 512GB M2NVMe SSD testcase: full disk, encryption, secure-EFI, no-internet, no-swap
which highlights it was a full disk, encryption, Secure uEFI without internet and no swap; matching a testcase found on our checklist. This test performed by Lubuntu Council member Leó Kolbeinsson. The second testcase line can be just copy/pasted from our checklist.
Another example is from Lubuntu member David/KGIII
MSI Modern 15 (Intel Core i5-10210U, Intel UHD, 32 GB RAM) .
How you describe your hardware is up to you, I get details from
sudo lshw roughly in format
“Make model (cpu, ram, gpu)”
so my lenovo thinkpad x201 will show as
lenovo thinkpad x201 (i5-m520, 4gb, i915)
If you need help making sense of the testing checklist, then this wiki page may be helpful.
Follow the directions in the testsuite. If it does all of those things, great! If it doesn’t, we do need your help. Please file a bug on your testing box, and record the bug ID in the Bug (or Critical Bug) section in the iso.qa.ubuntu.com page when complete.
Follow the directions in the bug report, and be as specific as you can. This is a key step - an unreported bug will be an unfixed bug. For details on reporting bugs please refer to our wiki page and don’t forget to include the bug report number in the iso.qa.ubuntu.com test report.
Please note tests that complete okay, with only minor issues should still be PASSED, but the bug ID reported in the “Bugs” section. If you consider it a show-stopper bug, record it in the “Critical bugs” section (failing the test if you believe absolutely necessary).
Thanks in advance to those of you who can help, and please reply on discourse with any issues, concerns, or questions!
ISO and QA testing tracker - Kinetic Daily | Ubuntu QA
ISO testcases can take as little as 30 minutes to complete (including filing a report on the iso.qa tracker), and whilst we have only a single testcase for installs on the iso.qa site, we have an expanded checklist you can see at https://phab.lubuntu.me/w/release-team/testing-checklist/