DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Open a terminal window. Type "su", press Enter and type root user's password. Then type "aptitude install --with-recommends foomatic-bin cupsys-driver-gimpprint" and press Enter. This should install all the software you need for printing via CUPS.
Next, start your web browser and point it to the following address: http://localhost:631/admin The CUPS configuration program will ask you to login as root and to give the root user's password, and then it allows you to configure CUPS for your printer.
You may need to reboot before you can actually print anything.
note that your printer must also have a driver that can be used under linux. If your coming from windows then you will have to do some research on your printer. go to www.linuxprinting.org. They WILL explain everything to you, and they host tons of drivers, way more than the cups website. after that since cups is the "in" print server (and the most versatile) you can use the drivers that you download elsewhere to be used with CUPS.
***Newsflash***: if you have a Dell printer it is actually a Lexmark printer. It has just been renamed. and will work with the same drivers and ink cartridges for lexmark printers 99% of the time. the other 1% dell is fiddling the printers to hide the fact that their printers are actually lexmark by generating some incompatibilities between the clones. Check that on google! It's true.
If you have a Dell PhotoPrinter 720 or a Dell a920 then email me, tmantist@yahoo.com.
Dead Parrot, right on the nose!!
'have two printers:
1: HP Laserjet 4L, kind of a piece of junk that keeps going;
2: HP psc 1200, from last Xmas.
No way to get them working, but I followed your directions and got them installed, and, for the psc1200, doing OK.
The 4L is installed, but there must be some previous job somewhere in its memory that keeps going and going and going.. and it is unable to print the test page. I checked localhost:631, dleted both jobs, and they stand deleted, but the printer keeps going and going.... The first job, if keept, sould been finished long ago, 'cause it is a 94k job!
What's the solution?
turn off your printer and CUPS at the same time, then turn on CUPS and then the printer. That'll "sync" them up. It's a minor annoyance for me. Some guys still don't have documentation available for their printers.
it works for my Dell Photo Printer 720.
Back in the old Windoze XP days, when I turn off my Windoze boxen the printer driver would turn off my printer too. Now that's cool!
I use Window Maker that doesn't come with CUPS management tools, so I've installed gtklp that has a GUI for changing CUPS settings and for managing printer queues (gtklpq). (KDE and Gnome probably have better tools.)
Processes gone wild are best tamed using the traditional command line tools. Commands like "pstree", "top", and "ps aux" will tell you which processes are active, and you can use "kill -9 PID" (where PID is a process id number) or "killall process_name" (where process_name is, you guessed it, the name of the process you want to kill) to do the dirty part of the job. There are man pages for all these commands and there are also many howtos available for process management under GNU/Linux -- here's one usable howto: http://www.linuxcommand.org/lts0080.php
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.