| Better Switchable Graphics Support | |
|---|---|
| |
| Date | TBA |
| Time | all day |
| Website | QA/Test Days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
This event was postponed from 2016-10-26. 2016-11-03 is the correct date, so you haven't missed it. Stay tuned! We are still working on the test instructions and test cases below, so please wait until they're done before testing!
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 at Bugzilla, 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?
Today's installment of Fedora Test Day will focus on Better Switchable Graphics Support - for Fedora 25, there are some changes to switchable graphics support and today we will be testing that it works well enough, especially for Wayland on Fedora Workstation.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Hans (Jwrdegoede)
- Quality Assurance - Adam Williamson (adamw), Sumantro Mukherjee (sumantro)
Prerequisite for Test Day
- An updated installation of a Fedora Workstation 25 pre-release, or a Fedora 25 nightly image
- A system with switchable graphics. The switchcheck script will error out if you do not have one
How to test?
Using an existing Fedora 25 installation
Using an existing Fedora 25 install to test is fine, but please ensure you are using the default GNOME session (listed as just 'GNOME' in the login screen session chooser). Please also ensure you have fully updated the system.
It may also be a good idea to create a fresh user account for testing, though issues experienced with your regular user account are also of interest.
FIXME: Should we instruct testers to disable proprietary drivers?
Live image
Instead of testing with an installed system, you may download a non-destructive nightly live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live image links can be found here: please be sure to download one for the correct release. Please boot the live image normally without changing kernel parameters etc.
Download switchcheck and get your system profile
For this event we have written a script to gather some information on your system. Before running any tests, please download and run the script.
The script inspects nothing but your hardware information and whether or not X.org is running, and sends no data out from your system. It is free software and written in Python, so you can easily inspect it before running it if you wish.
- Install the script by running, at a console:
curl -o /tmp/switchcheck https://pagure.io/fedora-qa/switchcheck/raw/master/f/switchcheck && chmod ugo+x /tmp/switchcheck - Run the script, as a regular user from a terminal in the Workstation desktop:
/tmp/switchcheck- If it prints an error message with instructions, please follow them.
- If it prints any other kind of error, please ask for help in IRC.
- If you have switchable graphics and the script works correctly, it should display Paste the following line as your 'profile' in the results page:, and then a line of text. That line of text is your profile.
Run the tests
Visit the result page (currently under construction, link will appear when it's ready) 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. In the Profile section, please enter the profile text produced by the switchcheck script. You can add your system's model number before or after the profile text if you like. If you test on multiple systems, please enter a new row of results for each tested system, with the correct profile text for each one.
Reporting bugs
If you have problems with any of the tests, report a bug to Bugzilla. The component will depend on the bug - FIXME: ask Hans for some simple way for people to decide what component to file on. Please ask in IRC if you encountered an issue but are not sure where to report it. Please include in the bug report:
- The output of
lshw -c displayorlspci -nn - The output of
xrandr --listproviders - The output of
journalctl -b(you can runjournalctl -b > /tmp/journaland then attach/tmp/journalto the bug) - The output of
sudo dmidecode(again, you can runsudo dmidecode > /tmp/dmidecodeand attach/tmp/dmidecodeto the bug)
FIXME: any other stock data, Hans?
If you encounter a crash, you should be able to use the ABRT system to file a high-quality bug report. Run gnome-abrt - 'Problem Reporting' in the overview - look for the crash in the list you see, and click the Report button.
Test Results
Results will be transferred here from the result page after testing is complete. Please enter results in the result page (currently under construction, link will appear when it's ready).