Update: here's an interesting post on the same topic: http://downfromthetrees.com/linux-installing-a-proprietrary-hp-printer-driver.html The only thing I would add is that instead of using sudo as described in that post you may have to use gksu in order to avoid the Magic Cookie error.
The short guide:
You NEED a binary plugin. It blows, but you do. Blowing harder: there's a lot of references to letting hp-setup download it for you -- but I'm willing to bet that it will fail for you.
Anyway, do this:
wget http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/hplip-3.12.6-plugin.run
chmod +x hplip-3.12.6-plugin.run
gksudo ./hplip-3.12.6-plugin.run
Hopefully that's good enough to take you through to system-config-printer and/or hp-setup. I did a lot of things, but it was the gksudo ./hplip-3.12.6-plugin.run that did it in the end.
And don't forget to add yourself to the lpadmin and perhaps lp groups:
cat /etc/group|grep lp
lp:x:7:verahill
lpadmin:x:111:verahill
I don't know how necessary it is, but heck, why not?
Here's the full, painful (and probably embarrassing) route I took:
It should not be this difficult to get a bloody printer to work. With older printer models it's been quick and easy, without having to download any 'binary plugins'. This is just effing ridiculous. Guess who's not buying another HP printer...
I reorganised my office, and as part of that decided to move my printer from my desktop to one of my networked boxes to free up some space on my desk. My desktop is running GNOME, while the target box is running KDE.
If you install the hplip packages in debian you end up with a very helpful script called hp-setup. You can run that as a user, but try running it as root via sudo, and you get
Invalid MIT-MAGIC-COOKIE-1 keyhp-setup: cannot connect to X server :0
OK, so you can run it as user. Everything looks great, BUT...you'll find that in this case the install will fail at the step of downloading the magical, mythological 'binary plugin'.
Also, as a user you're unlikely to be able to be able to put files in the places where they belong anyway, so there's that (see e.g. the first comment below).
You then do a bit of googling for hplip-3.12.6-plugin.run, and end up here: https://aur.archlinux.org/packages.php?ID=44646
You do
wget http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/hplip-3.12.6-plugin.run
chmod +x hplip-3.12.6-plugin.run
./hplip-3.12.6-plugin.run
This opens a gui where you get to accept the T&C. Not much seems to happen beyond that though. Oh, and you can't do the sudo-thingy because, well, you get the magic cookie error.
OK, take a step back.
sudo lpstat -a
global-mfp accepting requests since Mon 20 Aug 2012 10:46:48 EST
HP-LaserJet-Professional-P1102w-2 accepting requests since Mon 20 Aug 2012 13:49:19 EST
lpoptions -d HP-LaserJet-Professional-P1102w-2
lpq
HP-LaserJet-Professional-P1102w-2 is ready
Test it:
lp /etc/fstab
request id is HP-LaserJet-Professional-P1102w-2-1 (1 file(s))
lpq
HP-LaserJet-Professional-P1102w-2 is ready and printing
Rank Owner Job File(s) Total Size
active (null) 1 untitled 2048 bytes
Printing my foot it is.
Hmm...
cat /etc/group|grep lpadmin
lpadmin:x:114:OK, edit /etc/group and add myself to lpadmin.
I can open system-config-printer, but I can't 1) delete any printers (which would've been nice) or 2) start it with sudo.
I can use http://localhost:631, but as a user I'm somehow not allowed to remove printers, and I use sudo -- there's no 'root' password.
At this point I was getting frustrated and nuked all printers clear of my system.
sudo lpadmin -x HP-LaserJet-Professional-P1102w-2
sudo apt-get install system-config-printer-kde
Now I had both 'printing' (= vanilla CUPS system-config-printer) and 'Printer Configuration' in the KDE menu.
Still no dice.
OK, another step back.
mkdir hp
./hplip-3.12.6-plugin.run --target hp
cd hp/
sudo cp 86-hpmud-sysfs_hp_laserjet_professional_p1102w.rules /etc/udev/rules.d
Still no effing luck.
Tried one last desperate thing:
gksudo ./hplip-3.12.6-plugin.run
Clicked the agreement. Said done.
Hit 'print test page' and...it printed!
So...you need to be root...but the MIT magic cookie issue combined with the requirement to have a friggin' gui (why???) made that painful. Well, I guess that's why we're told to use gksu whend oing graphical stuff...
OK, only things remaining: network sharing. Should be simple. Opened up all ports on print-host box to accept traffic from my desktop (and desktop only). No luck.
gksu system-config-printer
Click on server, settings -> check Publish shared printers connected to this system.
On my desktop it was then just add a matter of adding the printer in GNOME (ipp://192.168.1.101:631/printers/HP-LaserJet-Professional-P1102w)
Sweet.
SOLVED.
I have the same printer and it is a pain to install until you figure out you really do need that HP plugin. To make matters worse, it's often available in a distribution's repositories, but is typically executed as the user. So, of course, it fails, leaving the typical user profoundly perplexed.
ReplyDeleteI agree. Once you've figured it out it's easy enough -- but getting to the point where it's working requires that you 1) have an idea of where to start in your attempts to set it up (which is really the stumbling stone for many casual users) and 2) are persistent enough to hammer it out.
DeleteGiven that many of the older HP models do not require a binary plugin and 'just work' on plugging them in, this is definitely a step in the wrong direction.
Same printer here. Fedora 13 has an RPM of hplip that works, and I was able to configure the printer in USB mode, but it wouldn't configure the thing in wireless mode (a known bug). Further, my Ubuntu 9.10 systems are old enough that the installed version of hplip doesn't support this printer, and the newest version won't install at all.
ReplyDeleteSolution - forget hplip. There is a "foo2zjs" driver (google for it) that supports this printer, and it compiles and installs just fine. Configuring the wireless can be also done using vanilla Linux tools, but it is an interesting exercise in ad-hoc wireless networks and Zeroconf. What worked for me was configuring a wireless card in ad-hoc mode and running a dhcp server. I can provide more details if anyone is interested.
The foo2zjs rings a bell, however vaguely. I think I may have used the foo2zjs package on my old desktop.
DeleteTo those using debian and reading this, it is available in the debian repos (foo2zjs -> printer-driver-foo2zjs) and appears to be up to date.