| GNOME Software with DNF5 | |
|---|---|
| |
| Date | 2025-02-10 to 2025-02-17 |
| Time | all day |
| Website | QA/Test Days |
| Matrix | #workstation:fedoraproject.org |
| IRC | #fedora-workstation (webirc) |
| Mailing list | test |
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
What to test?[edit]
This Test Day will focus on GNOME 48 Desktop and Core Apps.
Who's available?[edit]
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion:
- Development - jkolarik (jkolarik)
- Quality Assurance - Sumantro Mukherjee (sumantrom), Kamil Paral (kparal), Adam Williamson (adamw)
You can chat with us on Matrix or IRC. See the infobox on top of the page to learn where to join.
Prerequisites for Test Day[edit]
- Fedora 42 nightly ISO image installed on either bare metal or in a virtual machine. (Make sure you have no important data on that system. Things might go wrong -- don't do this on your production machine!)
- If you already have Fedora 42 Workstation installed, there's no need to reinstall, but just make sure you have the latest updates installed.
- Use this COPR
- Make sure the GNOME Software version
gnome-software-48~testday-dnf5.001is installed on the system (e.g. Menu -> About Software; orrpm -q gnome-softwarein CLI)
How to test?[edit]
Use Fedora 42 Workstation and see if you can find anything that's crashing or not working correctly. In that case, file a bug!
Visit the results page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.
Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases.
Reporting bugs[edit]
Perhaps you've found an already-reported bug. Please look at:
Vast majority of bugs are likely going to be upstream code issues and should be reported into the GNOME gitlab bug tracker. General desktop issues are generally reported against gnome-shell, and applications have their own separate projects.
In cases where issues stem from downstream packaging (outdated components, broken dependencies) they should be filed into Red Hat Bugzilla.
Please note that just mentioning your problem into the comments section on the results page is not very helpful. Very often those problems only happen in specific circumstances, or with specific steps taken. We need the logs and screenshots, and we need to be able to ask you followup questions. Please file bug reports, it's much more useful than a short comment. Thank you!
When filing the bug, it's very helpful to include:
- exact steps you've performed (and whether you can reproduce it again)
- screenshots or videos, if applicable
- system journal (log), which you can retrieve by
journalctl -b > journal.txt - all output in a terminal, if started from a terminal
- your system description
If you are unsure about exactly how to file the report or what other information to include, just ask us.
Please make sure to link to the bug when submitting your test result, thanks!
Test Results[edit]
The results will be transferred onc the test day is done
