Bug 758693 - printer detected but cannot print test page
Summary: printer detected but cannot print test page
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 16
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-30 13:31 UTC by efreeti
Modified: 2013-02-13 19:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 19:02:28 UTC
Type: ---


Attachments (Terms of Use)
It contains two log files from /var/cups/log/ and a printscreen. (648.57 KB, application/x-gzip)
2011-11-30 13:31 UTC, efreeti
no flags Details

Description efreeti 2011-11-30 13:31:05 UTC
Created attachment 538566 [details]
It contains two log files from /var/cups/log/   and a printscreen.

Description of problem:
My printer model is hp-laserjet-1010. After plugging in usb, it automatically configured the printer drivers. System settings show the driver detected normally (see pic), but clicking "Print test page" results in nothing. I cannot print any documents also.


I attach contents from /var/cups/log/access_log and error_log.

Version-Release number of selected component (if applicable):
3.11.10-7.fc16


Additional info: I have another Fedora 16 desktop in xfce, that machine works fine, however.

Comment 1 Jiri Popelka 2011-11-30 14:02:41 UTC
The screenshot shows that the selected driver is 'Generic text-only printer'.

Comment 2 efreeti 2011-11-30 14:15:52 UTC
I thought the bold letters beside the icon was sufficient to display the printer model. I am not sure what to expect from there, as the xcfe interface looks different from gnome3.

Comment 3 efreeti 2011-12-18 15:17:19 UTC
I have updated packages hpijps, hplip, hplip-common to version 3.11.10-11.fc16, still does not work.

Comment 4 Tim Waugh 2011-12-19 18:03:25 UTC
What output do you see from this command?:

su -c /usr/share/system-config-printer/check-device-ids.py

Comment 5 efreeti 2011-12-26 05:25:41 UTC
su -c /usr/share/system-config-printer/check-device-ids.py
Password: 

If you have not already done so, you may get more results
by temporarily disabling your firewall (or by allowing
incoming UDP packets on port 161).

Examining connected devices
Installing relevant drivers using system service
Fetching driver list
├── HP LaserJet 1010 (usb): MFG:Hewlett-Packard;MDL:hp LaserJet 1010;CMD:PJL,MLC,BIDI-ECP,DW-PCL;
│   ├── drv:///hp/hpcups.drv/hp-laserjet_1010.ppd [/usr/share/cups/drv/hp/hpcups.drv]
│   ├── drv:///hp/hpijs.drv/hp-laserjet_1010-hpijs.ppd [/usr/share/cups/drv/hp/hpijs.drv]
│   ├── gutenprint.5.2://hp-lj_1010/simple [/usr/lib/cups/driver/gutenprint.5.2]
│   └── gutenprint.5.2://hp-lj_1010/expert [/usr/lib/cups/driver/gutenprint.5.2]
└── HP LaserJet 1010 (hp): MFG:Hewlett-Packard;MDL:hp LaserJet 1010;
    ├── drv:///hp/hpcups.drv/hp-laserjet_1010.ppd [/usr/share/cups/drv/hp/hpcups.drv]
    ├── drv:///hp/hpijs.drv/hp-laserjet_1010-hpijs.ppd [/usr/share/cups/drv/hp/hpijs.drv]
    ├── gutenprint.5.2://hp-lj_1010/simple [/usr/lib/cups/driver/gutenprint.5.2]
    └── gutenprint.5.2://hp-lj_1010/expert [/usr/lib/cups/driver/gutenprint.5.2]

Comment 6 efreeti 2011-12-26 05:31:52 UTC
Updated packages hpijps, hplip, hplip-common to version 3.11.12-1.fc16, tried reconnect the printer, restart the printer etc, still cannot print/test print.

Comment 7 Jiri Popelka 2012-01-02 14:08:43 UTC
(In reply to comment #6)
> Updated packages hpijps, hplip, hplip-common to version 3.11.12-1.fc16, tried
> reconnect the printer, restart the printer etc, still cannot print/test print.

That's because you actually use 'Generic text-only printer' driver and not hplip.
I moved this BZ to control-center component in comment #1 as I think that's the one responsible for selecting that wrong driver.
Meanwhile you should be able to print after changing the driver to hplip (hpcups/hpijs).

Comment 8 efreeti 2012-01-30 15:06:13 UTC
The problem is solved after trying out the advice of comment #7. My mistake to expect too much from the interface of the "System Settings". Apparently it's still not a control-center for hardware settings. At least not for printers.

Comment 9 Fedora End Of Life 2013-01-16 15:53:27 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 10 Fedora End Of Life 2013-02-13 19:02:34 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.