From Fedora Project Wiki

Revision as of 11:58, 29 June 2009 by Ajax (talk | contribs) (more stuff to test)

DATE TIME WHERE
Tue July 7, 2009 From 12:00 to 21:00 UTC (8am -> 5pm EDT) #fedora-fit-and-finish)


What to test?

Today's instalment of Fedora Test Day will focus on user experience issues of display configuration, including multi-monitor setups, monitor hotplug, projectors, etc.

Who's available

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion: Matthias Clasen, Adam Jackson, Dave Airlie

Prerequisites for Test Day

  • An uptodate rawhide installation
  • A variety of display hardware: external monitors, projectors, etc.

How to test

In this test day, we want to find small and large issues that ruin the user experience of working with different displays. So in short, you should exercise the display configuration aspects of the desktop. The primary tool is gnome-display-properties, in the menus under System → Preferences → Display. Another important interface to the display configuration system is the 'display' hotkey (the key that produces the XF86Display keysym) that many laptops have. On Thinkpads, this is the key combination Fn-F7, on HP laptops it is Fn-F4.

Here are some things to look at:

  • Does boot work as expected with multiple displays ?
  • Does the login screen cope with multiple displays ?
  • Does the desktop 'fall apart' when a new display is plugged in ?
  • Do fullscreen apps handle extra displays in a good way ?
  • Does presentation software do the right thing with projectors ?
  • Does gnome-display-properties show the right names for your displays ?
  • Does gnome-display-properties let you arrange the monitors in the way you want ?
  • Do laptop display-switch keys do something sensible ?
  • Do multiple successive configuration changes work ?
  • Does rotation behave as expected with 3D apps, video, etc ?
  • Are there rendering issues when using large desktop configs with a compositor like gnome-shell or compiz ?
  • Are all expected outputs detected ?
  • Are any unexpected outputs detected ?

Issues that were identified

Tester Description Bug references
mclasen Label colors in capplet and status icon don't match #586193