Ubuntu and its various flavours will be participating in another Ubuntu Testing Week from March 2nd to March 9th!
Soon we will be releasing the Ubuntu 23.04 Beta after halting all new changes and between then and the final release 3 weeks later, all efforts are focused on ISO testing, bug reporting, and fixing bugs.
How to Get Involved
Testing is easy! Start by simply downloading the Daily Ubuntu ISO image, perform the variety of test cases found on the ISO tracker and report your results. Tests can be performed in a virtual environment or directly on hardware. Testers can perform as few or as many test cases as they like.
With the exciting Desktop installer built on Subiquity and Flutter arriving in Ubuntu 23.04, we’re calling on our Community Testers to help identify any issues that may appear. Look for the various ‘Canary Install’ tasks under Ubuntu Desktop amd64 to get started.
It’s important that we capture a broad spectrum of test results, so we encourage testers to evaluate and document various configurations such as:
We also need testers to evaluate the legacy desktop image that comes preloaded with the classic Ubuntu Desktop installer. You can perform these tests by downloading the Ubuntu Legacy ISO and following the steps outlined in the various Ubuntu Desktop (Legacy) amd64 test cases.
Great news. To help along, is there a specific command or format to report the hardware used? Like the steam system information box that grabs a lot of info about the hardware.
It provides clues as to what the current ISO date is for each product/architecture, and if you selected Ubuntu Desktop amd64 you’ll get to a list of testcases that can be run. Select one and enter the details there. Right now that page here but PLEASE NOTE that link is specific to that daily ISO build, so I’d suggest always start at the lunar page I used earlier & navigate down.
( FYI: Myself I always use the daily page; and let the iso.qa tracker record/classify it in the beta/final page for me )
I keep a list of my hardware in a text file, and on the first line of comments I copy/paste the line that represents the machine I used in the QA-test, eg. if I was using the box I’m using now it’d be
which is just cpu, ram & gpu details obtained from lshw.
I’m not saying you need to do it this way, just its what I do & we do over at Lubuntu QA (eg. I’ll provide a page for install tests for the recent 22.04.2 where you’ll note it used by myself & Leó; the first line is always the ‘box’ used; being a line I pasted from my ubuntu_hw_test_specs.txt file).
(FYI: I grabbed & used a jammy.2 page as it was easy for me; and had picked a page that had numerous entries… A quick look at a lunar page and I saw few filled pages).
Sorry for the confusion here. So I have the following problem and need to know how to submit this to the http://iso.qa.ubuntu.com/qatracker/milestones/441/builds page because I am lost on that page (Not intuitive for me) and also I can not submit from 23.04 because it fails the moment the GUI starts so all I could grab was the following (but need help in properly reporting on the qa site):
This is the hardware PC I am using for testing (I am writing on my old computer this):
If I do not change the custom.conf gdm to not use wayland, I can get in but I can not interact with any windows. Context menus and sub menus open but do not do anything. The only way for me to get to the terminal was to open nautilus/files from the Dock, then right click any empty space and select terminal. The moment I did that I had a couple of seconds before it crashed the terminal. But was able to get a picture of the hardware after my 3rd attempt.
If I do disable wayland (Because I have an nvidia card) and start normal X.org then this happens:
And it stays there, does not matter if i change tty, it always shows and needed to reinstall 23.04 to be able to go back to wayland. But if I use wayland I can actually feel the lag and the interaction with windows and all. This started happening all today after applying all the latest updates for 23.04 (I did not update since I think since several days back).
Here is the hardware if it helps:
CPU - 13900k
MOBO - Asus Z790 Hero
RAM: DDR5 128GB
VID: Nvidia 4090 (Drivers were automatically installed during setup)
SSD - SN850x
More important is doing the testing, and recording a test on iso.qa.tracker as a completed test (fail/pass & any bugs encountered reported in either ‘critical bug’ or ‘bug’ fields).
You can report bugs as you normally do (ubuntu-bug etc, or just file report online with browser & apport-collect on your box), then login to iso.qa.ubuntu.com and record a test in the appropriate testcase and add the bug ID (your bug report will have hardware details due to ubuntu-bug or apport-collect being run).
If a system fails to boot; that’s a critical error as I see it, so report the bug as best you can (online report) & then just add the bug report ID into the critical bug field on an appropriate testcase on the iso tracker, click FAILED and enter submit. The filed bug report will soon be linked with the ISO that failed to boot.
If you’re interested in recording hardware as the iso.qa.tracker like we do with Lubuntu (but please note: this is optional as the testing is more important than this details, reporting bugs using apport-collect/ubuntu-bug will get this detail & more) my current box if used I’d report as
If you have any problems, questions etc, and use IRC (telegram/discord); see the title post on this thread for rooms where you can ask questions, and I or others will assist you as we’re able to.
We’d like to thank all the incredible community members who participated in the Ubuntu 23.04 Testing Week! Whether you ran through testcases in the isotracker, submitted bugs on our github or just helped promote testing efforts, your contribution helped improve the next iteration of Ubuntu.
Special thanks to the following testers who made it to the top of the testing scoreboard:
The backlight couldn’t be adjusted via software after I upgraded Ubuntu 22.10 to 23.04, the 5.19.0-35-generic works well:
larry@zx:~/Downloads$ uname -a
Linux zx 5.19.0-35-generic #36-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 3 18:36:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
larry@zx:~/Downloads$ tree /sys/class/backlight/
/sys/class/backlight/
├── acpi_video0 -> ../../devices/pci0000:00/0000:00:01.0/backlight/acpi_video0
└── acpi_video1 -> ../../devices/pci0000:00/0000:00:01.0/backlight/acpi_video1
3 directories, 0 files
larry@zx:~/Downloads$ brightnessctl -l
Available devices:
Device 'acpi_video1' of class 'backlight':
Current brightness: 22 (22%)
Max brightness: 100
Device 'acpi_video0' of class 'backlight':
Current brightness: 2 (29%)
Max brightness: 7
......
larry@zx:~/Downloads$ light -L
Listing device targets:
sysfs/backlight/acpi_video1
sysfs/backlight/acpi_video0
sysfs/backlight/auto
sysfs/leds/input11::scrolllock
sysfs/leds/input4::capslock
sysfs/leds/phy0-led
sysfs/leds/input4::scrolllock
sysfs/leds/input11::capslock
sysfs/leds/input11::numlock
sysfs/leds/input4::numlock
sysfs/leds/input11::kana
sysfs/leds/input11::compose
util/test/dryrun
But the latest kernel shows:
larry@zx:~/Downloads$ uname -a
Linux zx 6.1.0-16-generic #16-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 24 14:37:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
larry@zx:~/Downloads$ tree /sys/class/backlight/
/sys/class/backlight/
0 directories, 0 files
larry@zx:~/Downloads$ brightnessctl -l
Available devices:
Device 'input4::capslock' of class 'leds':
Current brightness: 0 (0%)
Max brightness: 1
Device 'phy0-led' of class 'leds':
Current brightness: 1 (100%)
Max brightness: 1
Device 'input4::scrolllock' of class 'leds':
Current brightness: 0 (0%)
Max brightness: 1
Device 'input4::numlock' of class 'leds':
Current brightness: 0 (0%)
Max brightness: 1
Device 'mmc0::' of class 'leds':
Current brightness: 0 (0%)
Max brightness: 255
larry@zx:~/Downloads$ light -L
No backlight controller was found, so we could not decide an automatic target. The current command will have no effect. Please use -L to find a target and then specify it with -s.
Listing device targets:
sysfs/leds/input4::capslock
sysfs/leds/phy0-led
sysfs/leds/input4::scrolllock
sysfs/leds/input4::numlock
sysfs/leds/mmc0::
util/test/dryrun
My monitor has always been at maximum brightness now if the latest kernel is used, hope for help.
Before you do so, check the current reported bugs on Launchpad for the Lunar Lobster milestone to see if someone else has already reported the issue that you’ve experienced. If so, you can click the link at the top of the ticket that reads Does this bug affect you? and select Yes, it affects me. Doing this will help add HEAT to the bug report which helps our devs understand the issues significance.
I have problems with xboxdrv.
With previous versions (and kernel 5.x) the USB gamepad used to work OK.
Now its led lights up for a while but then immediately goes off. The pad is correctly recognized but no life sign.
I tried all, rmmod xpad, detach xboxdrv, etc.
I suspect it’s a 6.x kernel issue
from March 2nd to March 9th!
to the bug report which helps our devs understand the issues significance.