Fedora Test Days | |
---|---|
Gnome 3.8 | |
Date | 2013-03-21 |
Time | all day |
Website | QA/Fedora_19_test_days |
IRC | #fedora-test-day (webirc) |
Mailing list | test |
What to test?
Today's instalment of Fedora Test Day will focus on new features in Gnome 3.8. Read more.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - hadess, rtcm
- Quality Assurance - Martin Holec (Martix), Vítězslav Humpa (vhumpa), Vladimír Beneš (vbenes), Adam Williamson (adamw), Vadim Rutkovsky (vrutkovs)
Prerequisite for Test Day
- bootable USB key or CD/DVD disk with latest Fedora 19 live image or:
- machine or VM with updated Fedora 19
- An updated Fedora F19 pre-release or a Test Day #Live image
Known issues
- There are two entries for the live image in the boot menu. This is a result of using a special non-debug kernel in the live image to make it run smoothly. I've no idea why it results in two entries on the boot menu, but never mind. Just use the one that's selected and it'll boot fine.
- It's known that the system doesn't wake up properly from the idle time out screen blank / lock at present. On the live image, pressing 'Esc' should wake it up. On an installed system, you can only escape by restarting GNOME Shell from a console. See bug #923364. To avoid this inconvenience, you can disable screen blanking and locking from the Power and Privacy panels in the control panel.
- If you have an Intel chipset system and find it freezes - possibly with a kernel trace visible - repeatedly during testing, try using the kernel parameter intel_pstate=disable. See bug #923102.
- There are known to be several problems in submitting crashes via the 'abrt' automated reporting tool. If you need to report a crash, someone in #fedora-test-day should be able to help you to report it manually.
How to test?
This Test Day has two parts. First part is covered by test cases and it's focused on initial setup and getting you familiar with basic functionality. Second is exploratory testing when you are free to use software how do you like. Don't worry and try to break Gnome in various ways which you expect to work.
Update your machine
If you're running Fedora 19, make sure you have all the current updates for it installed, using the update manager. Or:
Live image
Optionally, you may download a non-destructive live image for your architecture. Tips on using a live image are available at FedoraLiveCD.
Architecture | SHA256SUM |
---|---|
x86_64 | bda651c2ddba6102cc04197b8345beef9d0e128aeb8df0074857f3a630817829 |
i686 | 191a9fd5ada686909429b6dbfcaf4bfc882c442ec3d391385dd3d8fa5cc69cc9 |
Software Rendering
Computers with obsolete graphics with buggy 3D drivers and VM hypervisors like KVM or VirtualBox don't have complete 3D support yet. But you can run Gnome Shell using software rendering (llvmpipe driver) on the CPU.
- You may need to uninstall your GPU driver by running
yum remove xorg-x11-drv-nouveau
for example to force enable llvmpipe driver. You will need to restart X by logging out and back in for this to take effect. - Of lesser interest, but still worth checking, is whether GPUs already on the hardware blacklist work with their native driver instead. This can be checked by commenting out the appropriate entry from
/usr/share/gnome-session/hardware-compatibility
and logging out and back in to Gnome.
Test Cases
GNOME Shell
- Initial Setup
- Login Screen
- Gnome Shell Activities
- Lock Screen
- Message Tray
- Gnome Shell Extensions
- Accessibility
- Gnome Classic mode
System Settings
Online Accounts
- Online Accounts - Google
- Online Accounts - Facebook
- Online Accounts - Windows Live
- Online Accounts - MS Exchange
- Online Accounts - Kerberos
- Online Accounts - ownCloud
- Online Accounts - IMAP
Applications
- Web
- Documents
- Files
- Empathy
- Empathy - Audio Call with Jabber
- Empathy - Video Call with Jabber
- Evolution
- Boxes
- Font Viewer
- Clocks
- Photos
- Contacts
- Disks
- Disk Usage Analyzer
Test Results
If you have problems with any of the tests, report a bug to Bugzilla for the appropriate component. 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 enter your result, as shown in the example result lines.
GNOME Shell
User | Initial Setup | Login Screen | Activities | Lock Screen | Message Tray | Extensions | Accessibility | Gnome Classic mode | References |
---|---|---|---|---|---|---|---|---|---|
Sample User | |||||||||
vrutkovs | |||||||||
fholec | |||||||||
bnater |
System Settings
User | System Settings | Privacy Settings | Sharing Settings | Search Settings | Color Settings | References |
---|---|---|---|---|---|---|
Sample User | ||||||
vrutkovs | ||||||
fholec |
| |||||
vbenes |
Online Accounts
Applications
User | Web | Documents | Files | Empathy | Empathy (audio) | Empathy (video) | Evolution | Boxes | Font Viewer | References |
---|---|---|---|---|---|---|---|---|---|---|
Sample User | ||||||||||
vbenes |
User | Clocks | Photos | Contacts | Disks | Disk Usage Analyzer | Others | References |
---|---|---|---|---|---|---|---|
Sample User | |||||||
vbenes |