From Fedora Project Wiki
(Drop direct Test Days category membership)
 
(24 intermediate revisions by 11 users not shown)
Line 35: Line 35:


* A printer
* A printer
* [https://dl.fedoraproject.org/pub/alt/stage/ Fedora 19 Alpha live image] (to install a virtual machine - currently bare metal installs are not supported [https://bugzilla.redhat.com/show_bug.cgi?id=928228 #928228]) or [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/ nightly live image]
* Fedora 19 live image ([https://dl.fedoraproject.org/pub/alt/stage/ pre-Alpha] or [http://alt.fedoraproject.org/pub/alt/nightly-composes/ nightly compose]) or [[Releases/Rawhide|Rawhide]]


* Clear your audit log (in case you aren't running from the live medium):
* Clear your audit log (in case you aren't running from the live medium):
Line 51: Line 51:
=== Update your machine ===
=== 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 [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:
If you're running Fedora 19, make sure you have all the current updates for it installed, using the update manager. If you are running Fedora 18 and want to try upgrading to Fedora 19, here is how:
 
yum update yum; yum clean all ; yum --releasever=19 distro-sync --nogpgcheck -y
 
Or:


=== Live image ===
=== 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 [http://alt.fedoraproject.org/pub/alt/nightly-composes/ here]. Live usb with Fedora-19-Nightly-20130401.13*.iso seems to be working on bare metal.
Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be found [https://dl.fedoraproject.org/pub/alt/stage/ here ] or [http://alt.fedoraproject.org/pub/alt/nightly-composes/ here]. Live usb with Fedora-19-Nightly-20130401.13*.iso seems to be working on bare metal.


=== CUPS-1.6 on Fedora 18 ===
=== CUPS-1.6 on Fedora 18 ===
Line 70: Line 74:
* [[QA:Testcase_Printing_Network_Printer|Printing to a network printer]]
* [[QA:Testcase_Printing_Network_Printer|Printing to a network printer]]
* [[QA:Testcase_Printing_Complex|Printing copies/pages/duplexing from the print dialog]]
* [[QA:Testcase_Printing_Complex|Printing copies/pages/duplexing from the print dialog]]
* [[QA:Testcase_Printing_Troubleshooting|Status feedback]]
* [[QA:Testcase_selinux-AVCs|Selinux-AVCs]]
* [[QA:Testcase_selinux-AVCs|Selinux-AVCs]]
* [[QA:Testcase_Printing_Troubleshooting|Status feedback]]


=== Desktop and applications integration ===
=== Desktop and applications integration ===
Line 94: Line 98:


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 [[Template:result|result template]] to enter your result, as shown in the example result line.
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 [[Template:result|result template]] to enter your result, as shown in the example result line.
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.


{|
{|
Line 102: Line 108:
! [[QA:Testcase_Printing_Network_Printer|Network printing]]
! [[QA:Testcase_Printing_Network_Printer|Network printing]]
! [[QA:Testcase_Printing_Complex|Copies/pages/duplex]]
! [[QA:Testcase_Printing_Complex|Copies/pages/duplex]]
! [[QA:Testcase_Printing_Troubleshooting|Status feedback]]
! [[QA:Testcase_selinux-AVCs|Selinux issues]]
! [[QA:Testcase_selinux-AVCs|Selinux issues]]
! [[QA:Testcase_Printing_Troubleshooting|Status feedback]]
! References
! References
|-
|-
Line 112: Line 118:
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|fail}} <ref>{{bz|12345}}</ref>
| {{result|pass}}
| <references/>
|-
| [[User:Mhradile|Miroslav Hradílek]]
| Brother HL-2150N
| {{result|fail}} <ref group="long">Identified as a right printer "HL-2150N-Series" but assigned wrong generic driver effectively acting like there is no problem. This caused other test cases to fail more or less. Also no notification about disconnecting. Further testing was performed by manually installing [http://welcome.solutions.brother.com/bsc/public_s/id/linux/en/instruction_prn1a.html manufacturers drivers].</ref>
| {{result|pass}} <ref>Again no notification about reconnecting.</ref>
| {{result|fail}} <ref group="long">I was able to see my network printer under a weird ID hash in printing dialog. This printer was showing printer messages in my mother language and was grayed out when printer had issues. When clicked on though, it displayed hourglass cursor and after a while printer reported "Service call indications
" error (the worst error) by blinking all leds. Obviously did not print. When attempting to add it manually it was constantly trying to use the ID hash in place of the IP. After full manual configuration it worked as expected. Also printing dialog did not offer a thing.</ref>
| {{result|pass}} <ref>But no print queue in notification area.</ref>
| {{result|fail}} <ref group="long">Except for the "disconnected printer", messages are flawed. Printing dialog states "sending data to printer" when "job completed" notification was already received while printer happily continues printing. Funny: the weird ID hash printer is always right.</ref>
| {{result|fail||946857}}
| <references/>
|-
| mbaldessari
| HP OfficeJet J4500
| {{result|pass}}
| {{result|pass}} <ref>no notification about reconnecting.</ref>
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| <references/>
|-
| [[User:Twaugh|Tim Waugh]]
| HP DeskJet 990Cxi
| {{result|pass}}
| {{result|pass}}
|
|
|
|
| <references/>
|-
| [[User:Twaugh|Tim Waugh]]
| HP Photosmart 5510
|
|
|  {{result|pass}} <ref> {{bz|948288}}, used alternative URI as work-around </ref>
|
|
|
| <references/>
|-
| [[User:jscotka|Jan Scotka]]
| HP DeskJet 2515 {{result|fail}} <ref>unable to download desktop copompose (actual koji builds), propably there should be permanent link to compose</ref>
|
|
|  {{result|pass}} <ref> via system-config-printer via "find network printer" found and job printer, and printed job from firefox  </ref>
|
|
|
| <references/>
|-
| [[User:Psklenar|Petr Sklenar]]
| HP OfficeJet Pro 8500
| {{result|pass}} <ref> {{bz|948240}} </ref>
|
|
|
|
|{{result|fail}} <ref>{{bz|946857}} (< dupe of some older bz)</ref>
| <references/>
|-
| [[User:jprokes|Jakub Prokes]]
| Cannon imageRunner c2020i
| 
|
| {{result|pass||919489}}
|
|
| {{result|fail||946857}}
| <references/>
|-
| [[User:luya|Luya Tshimbalanga]]
| [http://h10025.www1.hp.com/ewfrf/wc/product?cc=us&lc=en&dlc=en&product=5041262 HP Photosmart eStation C510a]
| {{result|pass}}
| {{result|pass}} <ref>no notification about reconnecting.</ref>
| {{result|pass}}
| {{result|pass}}<ref>Manual IP output for wireless printer</ref>
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|fail}} <ref>{{bz|12345}}</ref>
| <references/>
| <references/>
|-
|-
| [[User:dapospis|Dalibor Pospisil]]
| Samsung SCX-4200
| {{result|fail}} <ref>unable to print at all {{bz|949063}}</ref>
| {{result|}}
| {{result|}}
| {{result|}}
| {{result|}}
| {{result|}}
| <references/>
|-
|-
! User
! User
Line 123: Line 219:
! [[QA:Testcase_Printing_Network_Printer|Network printing]]
! [[QA:Testcase_Printing_Network_Printer|Network printing]]
! [[QA:Testcase_Printing_Complex|Copies/pages/duplex]]
! [[QA:Testcase_Printing_Complex|Copies/pages/duplex]]
! [[QA:Testcase_Printing_Troubleshooting|Status feedback]]
! [[QA:Testcase_selinux-AVCs|Selinux issues]]
! [[QA:Testcase_selinux-AVCs|Selinux issues]]
! [[QA:Testcase_Printing_Troubleshooting|Status feedback]]
! References
! References
|}
|}


[[Category:Test Days]]
== Long comments ==
[[Category:QA Templates]]
<references group="long" />
 
  [[Category:Fedora 19 Test Days]]

Latest revision as of 20:53, 26 June 2015

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

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

Prerequisite for Test Day[edit]

  • Clear your audit log (in case you aren't running from the live medium):
# echo -n > /var/log/audit/audit.log

How to test?[edit]

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

If you're running Fedora 19, make sure you have all the current updates for it installed, using the update manager. If you are running Fedora 18 and want to try upgrading to Fedora 19, here is how: 

yum update yum; yum clean all ; yum --releasever=19 distro-sync --nogpgcheck -y

Or:

Live image[edit]

Tips on using a live image are available at FedoraLiveCD. Live images can be found here or here. Live usb with Fedora-19-Nightly-20130401.13*.iso seems to be working on bare metal.

CUPS-1.6 on Fedora 18[edit]

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

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

Desktop and applications integration[edit]

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

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.

User Printer Connect local Reconnect local Network printing Copies/pages/duplex Status feedback Selinux issues References
Sample User HP LaserJet 5
none
none
Pass pass
Warning warn
[1]
Fail fail
[2]
Pass pass
  1. ↑ Test pass, but also encountered RHBZ #54321
  2. ↑ RHBZ #12345
Miroslav Hradílek Brother HL-2150N
Fail fail
[long 1]
Pass pass
[1]
Fail fail
[long 2]
Pass pass
[2]
Fail fail
[long 3]
Fail fail [3]
  1. ↑ Again no notification about reconnecting.
  2. ↑ But no print queue in notification area.
  3. ↑ RHBZ #946857
mbaldessari HP OfficeJet J4500
Pass pass
Pass pass
[1]
Pass pass
Pass pass
Pass pass
Pass pass
  1. ↑ no notification about reconnecting.
Tim Waugh HP DeskJet 990Cxi
Pass pass
Pass pass
Tim Waugh HP Photosmart 5510
Pass pass
[1]
  1. ↑ RHBZ #948288, used alternative URI as work-around
Jan Scotka HP DeskJet 2515
Fail fail
[1]
Pass pass
[2]
  1. ↑ unable to download desktop copompose (actual koji builds), propably there should be permanent link to compose
  2. ↑ via system-config-printer via "find network printer" found and job printer, and printed job from firefox
Petr Sklenar HP OfficeJet Pro 8500
Pass pass
[1]
Fail fail
[2]
  1. ↑ RHBZ #948240
  2. ↑ RHBZ #946857 (< dupe of some older bz)
Jakub Prokes Cannon imageRunner c2020i
Pass pass [1]
Fail fail [2]
  1. ↑ RHBZ #919489
  2. ↑ RHBZ #946857
Luya Tshimbalanga HP Photosmart eStation C510a
Pass pass
Pass pass
[1]
Pass pass
Pass pass
[2]
Pass pass
Pass pass
  1. ↑ no notification about reconnecting.
  2. ↑ Manual IP output for wireless printer
Dalibor Pospisil Samsung SCX-4200
Fail fail
[1]
  1. ↑ unable to print at all RHBZ #949063
User Printer Connect local Reconnect local Network printing Copies/pages/duplex Status feedback Selinux issues References

Long comments[edit]

  1. ↑ Identified as a right printer "HL-2150N-Series" but assigned wrong generic driver effectively acting like there is no problem. This caused other test cases to fail more or less. Also no notification about disconnecting. Further testing was performed by manually installing manufacturers drivers.
  2. ↑ I was able to see my network printer under a weird ID hash in printing dialog. This printer was showing printer messages in my mother language and was grayed out when printer had issues. When clicked on though, it displayed hourglass cursor and after a while printer reported "Service call indications " error (the worst error) by blinking all leds. Obviously did not print. When attempting to add it manually it was constantly trying to use the ID hash in place of the IP. After full manual configuration it worked as expected. Also printing dialog did not offer a thing.
  3. ↑ Except for the "disconnected printer", messages are flawed. Printing dialog states "sending data to printer" when "job completed" notification was already received while printer happily continues printing. Funny: the weird ID hash printer is always right.
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2013-04-04_Printing&oldid=416716"