From Fedora Project Wiki

Revision as of 21:42, 19 September 2016 by Jibecfed (talk | contribs) (internal link cleaning)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Fedora Test Days

Date 2013-11-05
Time all day

Website QA/Fedora_20_test_days
IRC #fedora-test-day (webirc)

Mailing list

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?[edit]

Today's instalment of Fedora Test Day will focus on Printing.

This test day is for testing all aspects of printing, including setting up the printer, sharing printers on the network, and printing jobs.

The changes in Fedora 20 are relatively minor: switching to CUPS 1.7 and Ghostscript 9.10, and some improvements to cups-filters and the "Printers" part of GNOME Settings.

Note that since Fedora 19, printer sharing and discovery uses mDNS/DNS-SD rather than the CUPS Browsing method that's been the default in older releases. The cups-browsed service provides backwards compatibility for CUPS Browsing/BrowsePoll. One of the changes in Fedora 20 is for cups-browsed to use a more efficient method for BrowsePoll (asking for new/removed printers rather than fetching the entire list each time).

Remember that CUPS unit testing is only one small part of the story: printing is very much in need of integration testing. Try printing with different applications, using options you don't normally use in the print dialog. Try to see how many different ways you can break it!

If you see a problem and are not sure which component is to blame, the Debugging Printing page can help you to diagnose it.

Who's available[edit]

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

Prerequisite for Test Day[edit]

All you need is:

How to test?[edit]

First, make sure you have applied updates from the updates-testing repository.

  • Configuring a printer not yet known to the system
  • Printing a test page
  • Printing something more complicated, e.g. LibreOffice document, PDF, email
  • Taking advantage of extra print features of your printer e.g. duplexing, stapling

Test Cases[edit]

Use the TestDayApp to view test case instructions and submit test results. When it asks you about your "Hardware", enter your printer make and model name.

Checking the Device ID is correctly listed
The hpijs, gutenprint-cups, foomatic-db-ppds and foomatic packages all contain tags that associate them with the Device IDs for the printers they support. If you are not given the opportunity to install one of these packages when your printer is supported by them, it may be that they do not list its Device ID correctly. You can check this by running /usr/share/system-config-printer/ as root.

Test Results[edit]

If you have problems with any of the tests, report a bug to Bugzilla. Choose the correct component:

  • gnome-settings-daemon for problems relating to job reporting and printer status feedback in GNOME Shell
  • control-center for problems specific to printer administration in GNOME Shell e.g. the new system settings module
  • cups for printing problems that persist even when using command line utilities such as lp
  • gtk2 for printing problems common to all GTK+ applications using the GTK+ print dialog
  • system-config-printer for bugs in the printing configuration program used in GNOME fallback mode and in other graphical environments
  • selinux-policy if there is some selinux issues

If you see something unexpected, even if you are not entirely sure whether it's a bug, please take the time to report it as one. Without doing that, it may be difficult to follow up and fix.

Basic Tests[edit]

User Hardware Connect a local printer Reconnect a local printer Print to network printer Print dialog options Status feedback SELinux AVCs KDE printer setup References
lnie Lenovo Thinkstation S20
Pass pass
Pass pass
twaugh HP DeskJet 990Cxi
Pass pass
Pass pass
Pass pass
[long 1]
  1. Configured as A4 automatically (correct). Uses hpcups... right/bottom margins look a little wide though.
twaugh HP Photosmart 5510 (hp backend)
Pass pass
  1. Out of paper notification works correctly when hp backend is used (not dnssd).
twaugh HP Photosmart 5510
Fail fail [1]
Fail fail [3]
  1. RHBZ #1026940
  2. Hard to set up printer because the dnssd backend is unreliable.
  3. RHBZ #1026949
twaugh HP PSC 2210
Pass pass
Pass pass
Fail fail [1]
Fail fail [2] [3]
  1. RHBZ #1026928
  2. RHBZ #1026909
  3. RHBZ #1026914
  4. No status feedback. In addition, print was corrupted after paper replaced.
Roshi HP Deskjet 1000 j110 on i386 RC3 installation Xfce
Pass pass
Pass pass
Pass pass
Pass pass
  1. All options not available on my printer were blurred out.
Roshi HP Deskjet 1000 j110 on x86_64 RC2 Live KDE
Warning warn [1]
Fail fail
Fail fail
  1. RHBZ #1027425
  2. KDE from the live image recognizes the printer and configures it. When you attempt to print - you get a 'filter failed' error.
  3. Printer get recognized and configured correctly by KDE - printing fails with 'filter error.'
satellit system76 laptop i7
Pass pass
Warning warn
  1. wireless connectio to HP 6100 turned off/on prints successfully
  2. printed from pdf file 15 pages and then cancelled running job sucessfully
Astrik HP C4180 All in One
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
  1. Printer recognized and pop up stated it was configuring printer.
  2. Different options selected all seemed to work as expected.
luya HP Photosmart eStation C510
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass

Long comments[edit]

  1. Tested 2 collated copies of 3-page document, duplexed, with libreoffice, evince, and firefox. Also same test of 1-page document with evolution.