SlackwareThis Forum is for the discussion of Slackware 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.
windows and macs (at least untill OS X) gave a lot of people a set of bad habits. such as whiping out a lot of stuff and installing it fresh, frequent reboots for no reason at all etc. we have a lot of power at our hands error logs, monitoring programs, human readable configuration files, editors, compilers, various scripting environments and, well, a very good operating system itself. reboot is justifiable only on two cases: system crash and kernel recompile.
If something did not work and you just reinstalled it without figuring out what went wrong moust probably you set yourself up to repeat this procedure in the near future.
Thanks notAcoolNick for your suggestions. I guess I had already tried why you mention especially viewing the log file for error message. I cant find any error message thats the problem as I need to use the printer urgently thus I used the lazy method.
Thanx man.
Sorry for getting on the runt though (I try not to do that very often).
Next time you see a problem you can change level and verbosity of error and debug messages in the log through /etc/cups/cupsd.conf file (the amount of messages can become pretty overwhelming but under closer consideration you'll be able to find required information). Don't forget to restart cupsd every time you change config. file and, afeter you figure out what is wrong, to dercrease or turn off the verbosity level (or our /var/log directory will fill up pretty quikly).
Best regards.
Great forum here. I, likewise, have gone through the Slackware 9.0 printer purgatory. I wonder if this nugget offers any insight....If i try to print buffer from Emacs, I get a valid printout...but if i select "POSTSCRIPT print buffer" I get reams of trash. THis sort of puts to rest any particular problem with Abiwork, StarOffice, etc, since it's the same EMACS program for each. Something is not triggering APSFILTER to recognize Postscript, except during the printer test. Very odd IMSMHO.
Other than that, KDE3 is far prettier than anything "Widows" has put out, and the driver-locating algorithms are every bit as user friendly as Mandrake.
Now...all I'm looking for is an open source version of Labview.....ha ha ha he he he ho ho ho!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.