| Fedora Test Days | |
|---|---|
| |
| gnome-shell and extensions | |
| Date | 2012-03-15 |
| Time | all day |
| Website | http://extensions.gnome.org/ |
| IRC | #fedora-test-day (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 at GNOME 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 instalment of Fedora Test Day will focus on gnome-shell extension management. Since the release of GNOME 3 about a year ago there's been a great progress in ways one can customize it. Remember applets, desktop widgets etc. back in GNOME 2? Missed them? Now we have all that back in form of gnome-shell extensions! Shell's architecture makes it relatively painless to make them and lots of useful extensions are already out.
There are several ways one can manage gnome-shell extensions. In addition to having gnome-tweak-tool, extension management has also been integrated with Firefox and https://extensions.gnome.org/, where you can search for and install extensions as well as enable/disable them. Haven't tried it yet? Go on, it's really nice! And while you're at it, please help us test these various ways of extension management by following the few test cases over here, catching bugs and thus contributing in efforts of making gnome-shell with extensions what all have been waiting for!
Who's available
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
- Quality Assurance - Martin Holec (Martix), Vítězslav Humpa (vhumpa), Adam Williamson (adamw)
Prerequisite for Test Day
- An updated Fedora 17 pre-release, or the specific Test Day live image.
- Your hardware profile uploaded to Smolt according to these instructions
- For most testing, a graphics adapter capable of compositing. If you have an adapter that doesn't support HW acceleration, you can still proceed if the all new software rendering kicks in. However you can still expect frequent lags and crashes, especially if you're having software rendering due to running Fedora in virtual environment.
Until now only modern and 3D capable cards were able to run gnome-shell. Most modern CPUs are in principle powerful enough to run gnome-shell and a full GNOME 3 session without 3D support and only via software rendering. Thanks to updates in several packages software rendering will be available from Fedora 17. This means that a full desktop session can now be run inside VMs as well using vesa, cirrus or qxl drivers. If it's inconvenient for you to install Fedora or use the Live CD on 'real' HW, you can take advantage of VMs. However be warned that you are still likely to experience crashes at this point (in case of KVM especially with QXL/Spice - with Cirrus/VNC the situation is much better and you can probably use such setup). This is also why the next GNOME Test Day will focus on software rendering. If you can, please join us then as well: 2012-03-29
How to test?
Live image
Please check the SHA256SUM is correct before booting!
You may download a non-destructive pre-Fedora 17 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.
| Architecture | SHA256SUM |
|---|---|
| x86_64 | 4ee9523cf832043fe73cd57743dacb82f5ae4240d98016a4ccd12314724dfd30
|
| i686 | 5a0f70bd863f95e016c93e01556c058e4faea63c04dc1a3e56ec25ecd7cecbd1
|
If you are using the live image, please run these commands in terminal: su -c 'yum remove empathy' followed by su -c 'yum update gnome-shell' . Please logout and login again before you start testing. GNOME Shell has been updated very recently and empathy should be removed to do so as it breaks the repository right now (March 14).
Using the live image is the easiest way to participate in testing for most people, but alternatively you can:
Update your machine to Fedora 17
If you are already running or want to try the pre-release of Fedora 17, install Fedora 17 Alpha and then update to the latest packages. As of 2012-03-14, please note you should remove empathy before updating your installation.
Perform testing
Please perform as many of the test cases listed as you have the time and the resources to complete, and fill out your results in the table below. You do not need a Fedora account to fill in the table.
Fallback
If you are unable to run a full GNOME 3 session either through HW or SW rendering and fallback mode kicks in you won't be able to run gnome-shell and any of its extensions. In this case, please, don't hesitate to ask on IRC as there might be a way we can help you start a regular session.
Regular tests
In current Fedora 17, there are problems with the gnome-shell integration. Most often Firefox won't "see" any extensions, available as well as already installed. If this happens to you, please, install (su -c 'yum install epiphany' ) epiphany to do the rest of testing.
- QA:Testcase_gnome-shell_extensions_install
- QA:Testcase_gnome-shell_extensions_tweak_tool
- QA:Testcase_gnome-shell_extensions_gnome_org
- QA:Testcase_gnome-shell_extensions_remove
Unplanned testing
As well as running the formal test cases, you can help simply by running gnome-shell and reporting any problems you come across in the course of your typical usage of extensions, even if this does not match up with any of the test cases. If you are unsure to what any discovered problem relates, please check in #fedora-test-day before you file a bug.
Test Results
If you have problems with any of the tests, try and report a bug. Bugs clearly related to GNOME Shell and it's browser integration as well as to extensions.gnome.org should be reported to GNOME Bugzilla. Bugs that are clearly issues in Fedora GNOME integration should be reported to Fedora Bugzilla. If you are unsure, please report into Fedora Bugzilla or ask on #fedora-test-day or #fedora-qa. You will need an account to report bugs, but creating one is easy, and we will help you do this if you ask in IRC.
If you are not sure of the appropriate component, please check in IRC before filing, there are many possibilities. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.
Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. If you are running Fedora in VM, please, at least state the name of VM hypervisor(kvm/VirtualBox...). For each test case, use the result template to describe your result, following the examples in the Sample user row.
| User | Smolt Profile | Installation | Gnome tweak tool | Online management | Removal | Unplaned | References |
|---|---|---|---|---|---|---|---|
| Sample User | HW |  |
 |
 |
|
| |
| swabe | HW | |
|
|
|
| |
| pschindl | HW | |
|
|
|
||
| sagitter | HW | |
|
|
|
| |
| vhumpa | KVM | |
|
||||
| eischmann | VirtualBox | |
|
|
|
||
| jkoten | HW | |
|
|
|
||
| Martix | T420s | |
|
|
|
| |
| User | Smolt Profile | Installation | Gnome tweak tool | Online management | Removal | Unplaned | References |