From Fedora Project Wiki
Fedora Test Days
KDE Plasma Workspaces
Date 2012-04-10
Time all day
Website QA/Fedora_17_test_days
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 KDE Plasma Workspaces

Who's available

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

Prerequisite for Test Day

Also helpful, if you have or can get them:

  • Additional displays (monitors, TVs...) for testing multihead setup
  • Wi-fi/bluetooth enabled networking devices
  • Graphics adapters, virtual machines, or driver configurations not capable of compositing

How to test?

Boot latest Fedora 17 into KDE 4.8 Plasma Workspaces.

Live image

Verification
Please check the SHA256SUM is correct before booting!

You may download a non-destructive pre-Fedora 17 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Architecture SHA256SUM
x86_64 8d81344ea3801f9a91a883af5b95831664b55509f79154c924ee34f1187e5742
i686 d435e6a37efe5819fcfa4615ba9c6d175ca96b5e143122de4bd0dfc7763e996b
Updating Live system
Do not attempt to run yum update it may break your running Live system. RHBZ [#741594]
Running in KVM
Due to known rendering problem, use QLX/Spice video option. If you're unsure how to set it up properly, ping us at #fedora-test-day. RHBZ [#810161]

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

Update your machine to Fedora 17

If you are already running or want to try the pre-release of Fedora 17, install Fedora 17 Alpha and then update to the latest packages.

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.

Regular tests

Here is the list of regular test. Some tests are optional as requires non-default settings and it's more difficult to set it up. The tests are divided into the four categories.

Basic desktop usage:

Hardware integration:

Essential apps:

  • kdepim
  • calligra
  • kde-telepathy
  • apper

Other features:

Tests without a test case are more freeform tests - try the basic usage and let us know on IRC. The tests are not limited on these proposed, feel free to contact us with any problem you encountered during the Test Day (and even after Test Day on #fedora-kde channel).

Unplanned testing

As well as running the formal test cases, you can help simply by running KDE 4 Plasma Workspaces and reporting any problems you come across in the course of your typical usage of desktop, even if this does not match up with any of the test cases. If you are unsure to what any discovered problem relates, please 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. Bugs clearly related to KDE Plasma Workspaces and it's rendering should be reported to KDE Bugzilla. Bugs that are clearly issues in Fedora KDE integration should be reported to Fedora Bugzilla. If you are unsure, please report into Fedora Bugzilla or ask on #fedora-test-day or #fedora-qa. 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. If you are running Fedora in VM, please, at least state the name of VM hypervisor(kvm/VirtualBox...). However uploading Smolt profile is useful even for VMs. For each test case, use the result template to describe your result, following the examples in the Sample user row.

Basic Desktop usage results:

User Smolt Profile Desktop Effects KDE4 Theming GDM Integration Session Management Applets/Plasmoids References
Sample User HW
none
Pass pass
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. ↑ Test pass, but also encountered RHBZ #54321
  2. ↑ RHBZ #12345
mkrizek Thinkpad W510
Pass pass
Pass pass
none
Pass pass
Pass pass
Steve HW
Pass pass
none
none
Pass pass
Pass pass
honza.s HW
Pass pass
none
none
Pass pass
none
Marcus HW
Pass pass
none
none
Pass pass
none
pavel Gigabyte Q1585n
Warning warn
[1]
none
none
Pass pass
Warning warn
[2]
  1. ↑ Poor graphical performance, desktop freezes sometimes.
  2. ↑ Solar system plasmoid have visual artefacts.
stepulka Acer 5630EZ
Pass pass
none
none
Pass pass
Pass pass

Hardware integration results:

User Smolt Profile Bluetooth NM applet Device notifier applet Volume applet (kmix) Battery Applet References
Sample User HW
none
Pass pass
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. ↑ Test pass, but also encountered RHBZ #54321
  2. ↑ RHBZ #12345
mkrizek Thinkpad W510
none
Pass pass
Pass pass
Pass pass
Pass pass

Essential apps and Other features results:

User Smolt Profile kdepim calligra kde-telepathy apper Sound System Settings References
Sample User HW
none
none
none
none
none
none
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2012-04-10_KDE_4.8&oldid=283627"