Unable to create the Foomatic driver HP LaserJet 4P hpijs

Bug #42123 reported by Thomas Jollans
22
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Medium
Unassigned
cupsys (Ubuntu)
New
Undecided
Unassigned

Bug Description

I am attempting to add a printer queue with samba, HP LaserJet 4P in the KDE printer admin. When I select the driver, I get a message saying
"Unable to load the requested driver:

Unable to create the Foomatic driver [HP-LaserJet_4P,hpijs]. Either that driver does not exist, or you don't have the required permissions to perform the operation."

I have also tried all other LaserJet 4P backends and a few other printers drivers.
This is on newest dapper, recently installed (=>pretty clean system).

Revision history for this message
randcoop (rcooper) wrote :

The problem is with the CUPS access to the database. I got the same error when trying to install the HP 7110. Many others have gotten the error as well.

I downloaded the PPD file and then installed using that file instead of asking CUPS to access the data base and it worked perfectly.

Revision history for this message
Paul Grant (paulgrant) wrote :

I got the same error. I followed randcoop's instructions and clicked "Other" and selected the printer driver manually, and everything worked fine.

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

Please upgrade uptodate your system and retest your bug. Cause here and with gnome i'v no problem.
If it's still present, put steps to do to reproduce your problem.
If you can, install gnome and use gnome-cups-manager to install your printer.
I suspect a problem with kde printing configuration tool.

Changed in cupsys:
status: Unconfirmed → Needs Info
Revision history for this message
randcoop (rcooper) wrote :

Upgraded today and bug is still there. The data base search in the kcontrol print installation process claims that the printer driver isn't on the system. In fact, when I force the program to look in the correct folder for the driver, it works.

The suggestion that those of us who use KDE should install gnome and then use gnome-cups-manager is not particularly helpful. Ubuntu supports Kubuntu and KDE; this program should work in Dapper as it has all this time in Breezy.

Revision history for this message
Paul Grant (paulgrant) wrote :

I still get this error today after Dapper was officially released. I've installed all updates to date. I agree with randcoop that it is not helpful to suggest we install gnome-cups-manager. It should work in KDE as well as Gnome since Ubuntu supports both.

Someone please tell me that you've figured this bug out?!

Revision history for this message
Manuel López-Ibáñez (manuellopezibanez) wrote :

Hi Paul, I guess that what VETSEL Patrice meant is:

"Please, could you try by using gnome-cups-manager? If it works, then we know that the bug is in KDE printing, otherwise the reason must be somewhere below both GNOME and KDE like cups".

Would you mind to do that so we can help you? Thanks in advance.

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

@manu :
exactly ! :)

Revision history for this message
WalterNicholls (walter-nic) wrote :

This affects a LOT of printers - mine was an Epson Stylus Color 400 + foomatic+gimp-print. I never solved this satisfactorily in Breezy and resorted to the stcolor driver, which had far fewer options (no draft/economy modes etc).

In Dapper, this was a problem on an initial install, the recommend driver was foomatic+gimpprint but this fell over as described in the bug description.

foomatic-cleanupdrivers removed the missing driver, and as far as I know the Gutenprint-5.0.0.-rc2 is working well (with all the economy options we could ask for). Although, it was still not the recommended driver (in fact, none were recommended)

So it would seem from what other people are saying that there are two problems here:
 * Dapper is installing with a whole pile of broken/missing drivers listed
 * and it is _recommending_ those broken drivers
.. and "foomatic-cleanupdrivers" may be solve the problem

Revision history for this message
Paul Grant (paulgrant) wrote :

Oh the drivers are there, the printer install program just doesn't know where they are. If one clicks other and selects the correct driver manually it works.

gnome-cups-manager seems to work btw, but I'm pretty sure everyone expected it to. I'm not switching to Gnome though, but good try.

Revision history for this message
Ante Karamatić (ivoks) wrote :

As far as I can see, this is KDE issue, not CUPS.

Revision history for this message
Luka Renko (lure) wrote :

Does running "sudo foomatic-cleanupdriver" help?
In that case this can be closed as duplicate of bug 42965

Revision history for this message
Manuel López-Ibáñez (manuellopezibanez) wrote :

Paul, no one is asking you to switch to gnome. However, knowing what works and what doesn't work helps to triage the bug. I think it is all very well explained in this article "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

Now, please, could you switch back to KDE and run in Konsole "sudo foomatic-cleanupdriver" and then try to add the printer? Thanks in advance.

Revision history for this message
Paul Grant (paulgrant) wrote :

paul@ubuntu:~$ sudo foomatic-cleanupdriver
Password:
sudo: foomatic-cleanupdriver: command not found

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

it's :
sudo foomatic-cleanupdrivers

Revision history for this message
Paul Grant (paulgrant) wrote :
Download full text (4.1 KiB)

"paul@ubuntu:~$ sudo foomatic-cleanupdrivers
Password:
PM760pl.upp.xml has an empty command line, deleted!
PM820pl.upp.xml has an empty command line, deleted!
Stc680pl.upp.xml has an empty command line, deleted!
Stc760pl.upp.xml has an empty command line, deleted!
Stc777pl.upp.xml has an empty command line, deleted!
Stp720pl.upp.xml has an empty command line, deleted!
Stp870pl.upp.xml has an empty command line, deleted!
bj8gc12f.upp.xml has an empty command line, deleted!
bj8hg12f.upp.xml has an empty command line, deleted!
bj8oh06n.upp.xml has an empty command line, deleted!
bj8pp12f.upp.xml has an empty command line, deleted!
bj8ts06n.upp.xml has an empty command line, deleted!
bjc6000b1.upp.xml has an empty command line, deleted!
bjc610a1.upp.xml has an empty command line, deleted!
bjc610a2.upp.xml has an empty command line, deleted!
bjc610a3.upp.xml has an empty command line, deleted!
bjc610a4.upp.xml has an empty command line, deleted!
bjc610a5.upp.xml has an empty command line, deleted!
bjc610a6.upp.xml has an empty command line, deleted!
bjc610a7.upp.xml has an empty command line, deleted!
bjc610a8.upp.xml has an empty command line, deleted!
bjc610b1.upp.xml has an empty command line, deleted!
bjc610b2.upp.xml has an empty command line, deleted!
bjc610b3.upp.xml has an empty command line, deleted!
bjc610b4.upp.xml has an empty command line, deleted!
bjc610b6.upp.xml has an empty command line, deleted!
bjc610b7.upp.xml has an empty command line, deleted!
bjc610b8.upp.xml has an empty command line, deleted!
capt.xml has an empty command line, deleted!
cljet5c.xml has an empty command line, deleted!
gimp-print.xml has an empty command line, deleted!
gutenprint.xml has an empty command line, deleted!
iwlo.xml has an empty command line, deleted!
iwlq.xml has an empty command line, deleted!
la70t.xml has an empty command line, deleted!
lbp660.xml has an empty command line, deleted!
lj5mono.xml has an empty command line, deleted!
lxm3200m.xml has an empty command line, deleted!
lxm3200p.xml has an empty command line, deleted!
lxx74.xml has an empty command line, deleted!
m2300w.xml has an empty command line, deleted!
m2400w.xml has an empty command line, deleted!
necp2x6.upp.xml has an empty command line, deleted!
nwp533.xml has an empty command line, deleted!
omni.xml has an empty command line, deleted!
pbm2ppa.xml has an empty command line, deleted!
pegg.xml has an empty command line, deleted!
pxlcolor.xml has an empty command line, deleted!
ras1.upp.xml has an empty command line, deleted!
ras24.upp.xml has an empty command line, deleted!
ras3.upp.xml has an empty command line, deleted!
ras32.upp.xml has an empty command line, deleted!
ras4.upp.xml has an empty command line, deleted!
ras8m.upp.xml has an empty command line, deleted!
s400b1.upp.xml has an empty command line, deleted!
slap.xml has an empty command line, deleted!
sparc.xml has an empty command line, deleted!
st640ihg.upp.xml has an empty command line, deleted!
st640p.upp.xml has an empty command line, deleted!
st640pg.upp.xml has an empty command line, deleted!
st640pl.upp.xml has an empty command line, deleted!
st...

Read more...

Revision history for this message
Ante Karamatić (ivoks) wrote :

This is duplicate of bug 42965 - closing bug.

Changed in kcontrol:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.