KDE and CUPS . . . And system bloat
These are two unrelated questions but I didn't want to start two threads and waste the space on the board:
Background: KDE 3.5, Debian "mostly stable" with some unstable mixed in. Kernel 2.6.14. CUPS version 1.1.23-12 (not upgraded). This question is more out of curiosity than anything: On this particular system, to my surprise, my printer is detected automatically when I go to the KDE printers tab in the control center (I don't have the appropriate driver yet, but that's another issue). However, on another system which is basically the same except that it still has KDE 3.3, and fewer packages upgraded, In the control center when I try to switch it to CUPS it tells me it can not connect to the server. Weird. I'm not sure what's different. Another thing I've been curious about for a while: how can system bloat be resolved? I currently have 988 packages installed, up from around 700 when I first installed. It seems as though when something is installed with all the dependencies, it can be removed later but the dependencies remain. I'm not a fan of re-installing at all, so I was wondering if there is some way to do a thorough clean-up of everything that is unneeded, if for no other reason than to reduce the number of packages installed so they are easier to browse. Any thoughts? |
Quote:
On the one hand, unless you are hurting for hard drive space, having these floating around will not slog down your system. They will just take up space - and perhaps conflict with other libs contributing to "dependency hell" due to conflicting libs versions. The only way to avoid this is to use a distro that does not check dependencies for you ..... Slackware !!! Even then, unless you are keeping careful tabs on what gets installed, you will not know what to remove. At least with Slack, if you need to install a dependency, you installed it yourself so you know you did it. Also, since slackware does not split the source into appliction and developement packages, this whole mess is less of an issue. F |
Quote:
Quote:
|
Quote:
|
Quote:
|
You're right, CUPS wasn't even running! So that's working now with a Epson Stylus Color 600 printer, although nothing prints unless I set it on "raw printer", and then, of course, it only prints text. I tried using "postscript printer" but it said that the postscript driver could not be found!
|
You have to install additional printer driver package, I have a HP desejet, and installed hpijs which has a specific driver for my printer model, don't know exactly about Epson though, maybe gimp-print?
Regarding dependency cleaning-up, debfoster is really a handy tool. |
Quote:
Code:
>$ lsmod | grep lp |
Yes, lsmod gives me output like that. But it still won't print. It seems odd because my printer is listed and it claims to print successfully, but nothing ever comes out. The printer does work in DOS and Windows (I actually haven't used it in Windows for a while, though, but it works fine in DOS).
~$ lsmod | grep lp lp 11908 0 parport 37992 2 lp,parport_pc |
Quote:
Code:
parport: PnPBIOS parport detected. |
Yup, dmesg looks good. I tried EPP and SPP for my parallel port. Should I try ECP?
I don't know if I should download another driver, as has been suggested already, or if there's a problem with the cable or the printer itself. I'll try it in Windows again to see if it's still working there I guess. |
All times are GMT -5. The time now is 07:26 PM. |