From Fedora Project Wiki

Revision as of 12:48, 11 August 2009 by Hadess (talk | contribs) (add crasher fixed this morning)

DATE TIME WHERE
2009-08-11 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 peripherals. We are interesting in the problems you face when plugging anything into your computer, be it a mouse, a keyboard an external hard drive, a modem, a printer, a camera, a phone, a music player, a GPS or whatever.

Who's available

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion: Matthias Clasen, David Zeuthen, Bastien Nocera

Prerequisites for Test Day

  • An up-to-date rawhide installation. See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. If that feels too risky to you, we also have recent rawhide live images available that allow you to participate without risking your existing installation. Tips on using a live image are available at FedoraLiveCD.

Note that the images will be removed shortly after the test day, since they are strictly for test day usage only. Warning: I was bit by the bug having to do with notification area icons not showing up. I killed nm-applet and ran it directly to get onto my wireless network.

Architecture SHA1SUM
i586 e9ab9f9846bea2d0d0eb4514a4048d9365a07950
x86_64 6f49f3f7b6a3fab49514c73035bdfe42a8ca1416
  • For the Go online with a phone test, you'll need the latest versions of | NetworkManager and | gnome-bluetooth
  • A variety of gizmos that can be plugged into a computer. See above for a representative list of devices that might be good to test
  • A good mood. Remember; while we are poking into things that may make us angry or frustrated, we are doing it to make things better

How to test

In this test day, we want to find small and large issues that ruin the user experience of working with devices that can be (hot-)plugged into your computer.

Test cases:

Here are some things to look at:

  • Does the desktop react in the right way if you plug in your device ?
  • Is a suitable icon used to represent the device ?
  • Do the relevant applications 'see' the device, e.g. does a music player appear in rhythmbox ?
  • Do applications react appropriately to the device being unplugged ?
  • Do things work in the same way if the device is already plugged in before boot or before login ?

Issues that were identified

Tester Description Bug references
pfps Messages when inserting and unmounting/ejecting filesystems #516739
pfps PCMCIA to CF adaptor doesn't mount the card Worked in F11; not in F10 and F9; use old bug?
hadess Sony Ericsson K850i wired connection appears in NM, but can't connect not yet
hadess CUPS Bluetooth backend crashes when discovering a new printer fixed in F11, rawhide
jlaska Plugging in 2 USB keyboards, each with different keymaps, doesn't work as expected. Keypresses on the second keyboard diplays a character that doesn't correspond to the key pressed.
hadess crash when closing the wizard after setting PAN fixed in rawhide

Things that work alright

Tester Description
pfps USB sticks work as usual (surprise!), except I see "Aug 11 09:11:29 localhost gnome-keyring-daemon[2253]: mount_added: assertion `identifier' failed" and "Aug 11 09:12:05 localhost gnome-keyring-daemon[2253]: no volume registered at: /media/CF" on unmount plus "Aug 11 09:13:40 localhost usb_id[3250]: unable to access '/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/host12/target12:0:0/12:0:0:0/block/sdc'" on eject
pfps USB to SATA disk works (and eject option available!), except I see the second and third messages from USB stick test above
pfps USB multi card reader works, except I see the first and second messages from USB stick test above