| {{result|warn}} <ref>It is possible to move windows outside display and leave them there.</ref> <ref>Not possible to move windows from top display to bottom, if bottom is main.</ref> <ref>{{bz|684855}}</ref> <ref>{{bz|684858}}</ref>

| {{result|warn}} <ref>Works after some cajoling, but buggy. Calling system-config-date often produces two windows, and both system-config-date and control-center crashed on occassion when connecting to ntp servers.</ref>

+

| {{result|none}}

+

| {{result|pass}}

+

| {{result|none}}

+

| {{result|none}}

+

| {{result|pass}}

+

| {{result|pass}}

+

| {{result|warn}} <ref>Icons for system-config-* are not high-res enough for the <Ctrl>-<tab> task switcher, they look pixellated</ref>

+

| {{result|none}}

+

| {{result|pass}}

| {{result|none}}

| {{result|none}}

| <references/>

| <references/>

Line 599:

Line 617:

| {{result|warn}}<ref>no duplications from dash for gedit</ref>

| {{result|warn}}<ref>no duplications from dash for gedit</ref>

| {{result|pass}}

| {{result|pass}}

−

| {{result|fail}}<ref>Selecting the ''solid'' color (I one) in Colors & Gradients enters in infinite cicles of duration 7-10 sec, in which the desktop becomes unusable. In the very short time between each cycle it is possible to restore the desktop. The wallpaper' selection changes or not, only causally</ref>

+

| {{result|fail}}<ref>Selecting the ''solid'' color (I one) in Colors & Gradients enters in infinite cicles of duration 7-10 sec, in which the desktop becomes unusable. In the very short time between each cycle it is possible to restore the desktop. The wallpaper' selection changes or not, only causally '''Solution''': delete the folowing directories: ''.gnome2'' and ''.gconf''</ref>

Revision as of 13:08, 3 April 2011

Can't make the date? 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 GNOME 3. This is the second of three Fedora 15 Test Days focusing on GNOME 3. The goal of these events is to test as much as possible of the functionality of GNOME 3 to ensure that it works correctly and provides the necessary basic features for a day-to-day usable desktop.

Big changes ahead Remember, this ain't your momma's GNOME - the overall user experience of GNOME 3 is very different from GNOME 2. It's fine to ask about the changes and make feature requests, but before filing a bug on something that's 'missing' from GNOME 2, please ask in #fedora-test-day to make sure it's not an intended change. There should always be someone there who can answer your question. Thanks!

Who's available

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day

For most testing, a graphics adapter capable of compositing: we are aiming to support all NVIDIA GeForce adapters, all Intel adapters except for GMA 500 (Poulsbo) and pre-i915 (i8xx) adapters, and all ATI/AMD Radeon adapters. If you are using an unsupported adapter, you can still help us with fallback testing - see below.

Unsupported adaptersSome adapters are known to be currently not working or problematic with the Shell. NVIDIA GeForce 400 series (Fermi / NVC0) adapters currently have no acceleration support and should fall back to compatibility mode (see the fallback testing section below). GeForce FX adapters may exhibit poor performance. Interaction may fail with GeForce 2 / GeForce 4 MX adapters, making the desktop effectively unusable.

Shell will not work in VirtualBox or virt-manager / KVMVirtual machines without 3D acceleration pass-through support will not be suitable for most testing: the Shell will not run in these configurations. Also, even though some VirtualBox editions have passthrough support, the current Fedora implementation does not support it, so Shell will not work in VirtualBox either. If you are using a virtual machine, you can still help us with fallback testing - see below.

How to test?

Live image

Getting the right Live imageThe live images for the Test Day are in progress. The x86_64 and i686 images are will be uploaded for the Test day itself, but please check the SHA256SUM is correct before booting!

You may download a non-destructive pre-Fedora 15 live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Note that these 2 images are not CD-sized so should be used either on a DVD or a thumb drive.

Using the live image is the easiest way to participate in testing for most people, but alternatively you can:

Update your machine to Fedora 15

If you are already running or want to try the pre-release of Fedora 15, install Fedora 15 Alpha and then update to the latest packages. As of 2011-03-09, all the necessary packages for the Test Day should be available in the fedora or updates-testing repositories. Using the live image is easier and highly recommended.

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 testing

This test case will test that GNOME falls back correctly to a 'classic' environment if your hardware does not support the GNOME Shell. If your hardware starts GNOME Shell correctly, please leave the fallback test column empty, and fill in the other test result columns. If your hardware is unable to start GNOME Shell, but falls back correctly to a classic environment, please mark the fallback test in the results table as 'pass', and leave the other test columns empty. If your hardware is unable to start GNOME Shell, and does not fall back correctly to a classic environment, please mark the fallback test in the results table as 'fail', file a bug against gnome-session, and leave the other test columns empty.

Regular tests

Desktop test set

These test are targeted at the new desktop environment, probing areas specific to the new GNOME 3 itself.

Application specific test set

Following are tests that focus on specific applications that are an important part of the default GNOME 3 experience. Please note that these are of the same importance for GNOME as previous ones. This separation addresses primarily just the issue of single results table size.

Unplanned testing

As well as running the formal test cases, you can help simply by running GNOME 3 and reporting any problems you come across in the course of your typical use, even if they do not match up with any of the test cases. Please remember, though, that just being different from GNOME 2 is not necessarily a problem, and 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. Most bugs in this event should be reported to GNOME Bugzilla. Bugs that are clearly issues in Fedora GNOME integration should be reported to Fedora Bugzilla. 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. For each test case, use the result template to describe your result, following the examples in the Sample user row.

↑I can change default browser and mail client via System Info -> Default Applications, but looks like Firefox caches the old value until it's restarted. Chrome actually is updated automatically. When selecting Thunderbird and then entering a mailto: link from either Chrome or gvfs-open, Thunderbird is started but a compose window is *not* opened -- it appears the correct arguments are not being passed

↑With the latest nouveau driver from Koji, Shell no longer crashes X. With X 1.9.99 and the previous nouveau from before March 10, repeatedly triggering the Activities view eventually causes a crash, and some apps (Chrome, Kindle -- using Wine) trigger the crash really fast. But the Alt-Tab interface gets corrupted after a while -- see RHBZ #683932.

↑Selecting the solid color (I one) in Colors & Gradients enters in infinite cicles of duration 7-10 sec, in which the desktop becomes unusable. In the very short time between each cycle it is possible to restore the desktop. The wallpaper' selection changes or not, only causally Solution: delete the folowing directories: .gnome2 and .gconf