Test Day:2013-04-04 Printing

Fedora Test Days
Printing
Date	2013-04-04
Time	all day
Website	QA/Fedora_19_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 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 major change in Fedora 19 is the switch to CUPS 1.6.

This brings with it a change to the default set of filters used to converting documents: rather than performing transformations in PostScript it is now done in PDF.

Additionally, printer sharing and discover now uses mDNS/DNS-SD rather than the CUPS Browsing method that's been the default in prior releases. The cups-browsed service provides backwards compatibility for CUPS Browsing/BrowsePoll, and both methods (mDNS and CUPS Browsing) could use some testing.

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

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

• Development - Tim Waugh (twaugh), Marek Kasik (mkasik), Jiri Popelka (jpopelka)
• Quality Assurance - Petr Sklenar (psklenar),

Prerequisite for Test Day

• A printer
• Fedora 19 Alpha live image (to install a virtual machine - currently bare metal installs are not supported #928228) or Rawhide (tips on installing Rawhide below), or a nightly live image

• Clear your audit log (in case you aren't running from the live medium):

# echo -n > /var/log/audit/audit.log

How to test?

A variety of printing tasks should be attempted, including:

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

Update your machine

If you're running Fedora 19, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:

Live image

Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here. Live usb with Fedora-19-Nightly-20130401.13*.iso seems to be working on bare metal.

CUPS-1.6 on Fedora 18

As a last resort if you're having problems with live images/rawhide you can test CUPS-1.6 on Fedora 18 (x86_64 only).

Test Cases

• Connecting a local printer: Expected behavior is that when a new local printer is connected, drivers will be installed as needed, a queue will be created for it, and the user will see a notification message about it.

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/check-device-ids.py as root.

• Reconnecting a local printer
• Printing to a network printer
• Printing copies/pages/duplexing from the print dialog
• Status feedback
• Selinux-AVCs

Desktop and applications integration

• KDE Printers Settings <FIXME>
• KDE Applications Printing <FIXME>
• Gnome Printers Settings <FIXME>
• Gnome Applications Printing <FIXME>
• LibreOffice Printing <FIXME>
• Firefox Printing <FIXME>
• Java Applications Printing <FIXME>

Test Results

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 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 line.

User	Printer	Connect local	Reconnect local	Network printing	Copies/pages/duplex	Status feedback	Selinux issues	References
Sample User	HP LaserJet 5	none	none	pass	warn	fail	pass
User	Printer	Connect local	Reconnect local	Network printing	Copies/pages/duplex	Status feedback	Selinux issues	References