From Fedora Project Wiki
Fedora Test Days
GNOME 3 (pre-F15 Final)

Date 2011-04-21
Time all day

Website http://www.gnome3.org
IRC #fedora-test-day (webirc)
Mailing list test


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 instalment of Fedora Test Day will focus on GNOME 3. This is the final of the 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 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!
Yay, 3.0 out!
This time, as GNOME 3 has been released recently, today's test day can provide a nice way for you to get familiar with the final version of the new desktop, its looks and all the important functionality - especially if you are new to it.

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 adapters
Some 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 / KVM
Virtual 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.

Also helpful, if you have or can get them:

  • Additional displays (monitors, TVs...)
  • As many storage devices as you can access
  • Optical media (burned, commercially pressed, and blank burnable, CDs, DVDs and Blu-Rays)
  • Wi-fi/bluetooth enabled networking devices
  • Graphics adapters, virtual machines, or driver configurations not capable of compositing, to test fallback support (see below)

How to test?

Live image

Verification
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.

Architecture SHA256SUM
i686 9af0d24337a435d9c3f10fb34d1f16af7d6496b10ca0facf1a0630b45a66d544
x86_64 7d69f8324afc3de809144ff4104879c2240f3017e4db84cf5ed0d0259abb83e1

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 Beta and then update to the latest packages. 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.

Network configuration problems
GNOME 3's network configuration interface is not yet feature complete and cannot handle some cases that GNOME 2's could. If a feature you need to set up your network is missing, use the nm-connection-editor tool. See this Common Bugs entry for more details.

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

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.

User Smolt Profile Fallback Date Keyring Totem Multihead URIs Notification Dash Workspaces Search Login Terminal Shortcuts References
Sample User HW
none
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345
Andre Robatino HW
Pass pass
none
none
none
none
none
none
none
none
none
none
none
none
David Le Sage (Red Hat) HW
Pass pass
Pass pass
Warning warn
[1]
none
Warning warn
[2]
Pass pass
none
Pass pass
Fail fail
[3]
Pass pass
Pass pass
Fail fail
[4]
Pass pass
  1. Test pass, but abrt cannot save passwords: RHBZ #692340
  2. Test pass for GNOME 3, but FWIW, KDE 4.6 cannot detect dual monitors.
  3. RHBZ #695222 RHBZ #695227
  4. Making background transparent still doesn't work: RHBZ #683274
Tao Wu HW
none
Pass pass
Pass pass
Pass pass
none
Pass pass
Pass pass
Pass pass
Fail fail
[1]
Pass pass
Pass pass
Fail fail
[2]
Warning warn
[3]
  1. RHBZ #698585
  2. RHBZ #683274
  3. The F1 shortcut doesn't work on my system: RHBZ #683274
Walter Justen HW
none
Pass pass
Pass pass
Pass pass
none
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Fail fail
[1]
Pass pass
  1. Making background transparent still doesn't work: RHBZ #683274
Pavol Celuch HW
none
none
Pass pass
Pass pass
Pass pass
[1]
Pass pass
Pass pass
Pass pass
Fail fail
[2]
Pass pass
Pass pass
[3]
Fail fail
[4]
Pass pass
  1. Test pass for GNOME 3.
  2. RHBZ #695222
  3. RHBZ #680147
  4. Transparent background doesn't work: RHBZ #683274
Nicolas Kaiser HW
none
Pass pass
Pass pass
none
none
Pass pass
Pass pass
[1]
Pass pass
none
none
none
none
none
  1. Creating a new jabber.org account failed with "network error". Connecting to an existing jabber.org account worked nicely.
User Smolt Profile Fallback Date Keyring Totem Multihead URIs Notification Dash Workspaces Search Login Terminal Shortcuts References


User Smolt Profile Web media Menus Bluetooth Browse VNC Background NonGtk Lock Mount Volume Evince Burn GL References
Sample User HW
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345
David Le Sage (Red Hat) HW
Pass pass
Pass pass
none
Pass pass
none
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
none
none
Tao Wu HW
Pass pass
Pass pass
none
Pass pass
none
Pass pass
none
Pass pass
none
none
none
none
none
Walter Justen HW
Pass pass
Pass pass
none
Pass pass
none
none
none
none
none
none
none
none
none
Pavol Celuch HW
Pass pass
Pass pass
[1]
Fail fail
[2]
Pass pass
none
Pass pass
Pass pass
Warning warn
[3]
Pass pass
Pass pass
Pass pass
none
Pass pass
  1. system-config-authentication icon is fuzzy RHBZ #698244
  2. RHBZ #698556
  3. Doesn't lock the screen after set interval
Nicolas Kaiser HW
none
none
none
none
none
none
none
none
none
none
none
none
none
User Smolt Profile Web media Menus Bluetooth Browse VNC Background NonGtk Lock Mount Volume Evince Burn GL References