September 2001 - openSUSE Users - openSUSE Mailing Lists

printing via usb and cups
by Richard Bos 30 Sep '01

30 Sep '01

When I initially setup my suse 7.2 machine I configured printing using USB and CUPS. The test page that is generated by YAST came out very well, and I was able to print from the command line. However, since sometime printing does not work anymore (don't know when it stopped exactly). Does anyone know what/how to investigate what might be wrong; dar:/var/log/cups # lpc status lp: printer is on device 'usb' speed -1 queuing is enabled printing is disabled no entries daemon present When I execute "lpr <file>" the file is being sent to queue, I can cancel it from queue as well. The cups error log tells me that cups is configured for 100 clients The access log tells: 127.0.0.1 - - [30/Sep/2001:21:59:53 +0100] "POST /jobs/ HTTP/1.1" 200 170 127.0.0.1 - - [30/Sep/2001:22:00:01 +0100] "POST / HTTP/1.1" 200 117 127.0.0.1 - - [30/Sep/2001:22:00:01 +0100] "POST / HTTP/1.1" 200 117 127.0.0.1 - - [30/Sep/2001:22:00:01 +0100] "POST / HTTP/1.1" 200 80 127.0.0.1 - - [30/Sep/2001:22:00:01 +0100] "POST /printers/lp HTTP/1.1" 200 363 127.0.0.1 - - [30/Sep/2001:22:00:05 +0100] "POST / HTTP/1.1" 200 232 127.0.0.1 - - [30/Sep/2001:22:00:39 +0100] "POST /printers/ HTTP/1.1" 200 176 The local loop is not switched on when the machine comes up, so I added the local route: 192.168.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 ippp0 127.0.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 lo 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 ippp0 I have: rpm -qa | grep -i usb usbmgr-0.4.6-33 usbview-1.0-53 rpm -qa | grep -i cups cups-drivers-1.1.6-34 cups-1.1.6-52 which seems to be the original (non updated packages) I hope that this a good starting point to provide some information/hints/directions to get printing back to operation.... -- Richard Bos For those who have no home the journey is endless

2 2

hd utility
by Landy Roman 30 Sep '01

30 Sep '01

i am really in need of a toold to examine the health of a hd? -- To sin by silence when they should protest makes cowards out of men. --Abraham Lincoln -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDuyaGQRBADuy5RgRve2BFembRa15NJOkIHlsUOQrsDazsLzTnvNIQanyuFy xRDS/aiRsnNEY9FY5Q9vpkn6FkC1kgGbu3IODFoA2IG6x5gWxu2ZrUXdzA+BCx5S 7TyB6o2slBc8scNCGrpZUwtPjfFrRQG0ScS3eDO+0D5imc9l+1vGNzq0VwCgpj/Q fCeeUUKnjBrj7KryVHwd6qMD/37IWO2vKgEgHmZ/hrkEDcd79lurxaknxmdzEoD9 evwEKhlHbxcg7AVS6UD5CowCDAIDK/88ygQLFK+3ZoG7pLormPNfEUlYH9pIDgUU X1aVElu656GM5Cr4g+6KuOOUIobfw4AM1yCyIrAakFMGQtGRu80f6X9ViaYInW9F m6ZxBADYJ/FwpWVHqCeaSLeSCnzpP3Jki/KiXgUF0/B6aWYTojo643d69vVjK6Ca IedAcAve3kk2InBWEzjFt8C7widt2G6aJYXsHDzRkzhhttHHXemoOlgCNKz2T23M ZD3tN2HC8YNE/ODoUF+1PM+FJ/h2guVCCMLCrlGakBE/xyomf7QsUm9sYW5kbyBS b21hbiAoZnJlZSkgPGxhbmR5QGRlc3BpZXJ0YXByLmNvbT6IXQQTEQIAHQUCO7Jo ZAUJAsfqAAULBwoDBAMVAwIDFgIBAheAAAoJEEZFYl4vkkomfs4Anij31JBfYFeB ZR7q4hN4Z9oQf5aWAJ9gzF42zDT2wDFlapTm/T2uIOb9t7kBDQQ7smhrEAQA8xWk 008LVtTnJadrvmhydU0Pa4sUgKNozeg7k0f0NpeZYDm1nY2oPuscM9+fPU9gZ+pc X6eMZzAF4oE6jOhoA7OnEFhl7zdVa1tjKOIITbadP3RgZHFRY/9dS34KNJlvuJYX x+XqSa6W/Y2fa2FOEs2q4DSekUYclx2Vpbd1E4sAAwYEAIB5tYHGm7lVzauO8O0K jTRzBLEZesgXu9B1aD/HGOlQ55Af9j1ZiiXY9IceiEWymfLpjTwhrM7/rYJC50lo /H+6AROoTFuyZ8GulQvdr5YSeGhW9gmrh+s/uj7PDYBgtbQh10zNefIXRI/W/QlR xYaB/Q/8N8LrpJ3TB8IPVcdmiEwEGBECAAwFAjuyaGsFCQLH6gAACgkQRkViXi+S SibQPACfbXb9XvrS9G3XTqUGnaTeGkA/w1wAniY/hTrnZdCrdLsG3ANDcTmZBioC =ZXxw -----END PGP PUBLIC KEY BLOCK-----

5 7

repost: [SLE] Is there a difference between YOU and
by Steven T. Hatton 30 Sep '01

30 Sep '01

On Friday 21 September 2001 12:46, Steven T. Hatton wrote: > Are the updates I fetch from YOU a subset of what I get from the following > mirrior configurations? > > cat suse_7.2_update > package=suse_7.2_update > comment=The base update tree for SuSE 7.2 > site=ftp2.suse.com > remote_dir=/pub/suse/i386/update/7.2 > local_dir+/suse/7.2 > exclude_patt=^zq > > cat suse_7.2_kde > package=suse_7.2_supplemental_KDE > comment=the KDE update > site=ftp2.suse.com > remote_dir=/pub/suse/i386/supplementary/KDE/update_for_7.2 > local_dir+/suse/supplementary/KDE/update_for_7.2 > exclude_patt=source > > cat suse_7.2_gs > package=suse_7.2_gs > comment=Ghost View updates > site=ftp2.suse.com > remote_dir=/pub/suse/i386/supplementary/Ghostscript/7.2 > local_dir+/suse/gs > exclude_patt=^zq > > cat suse_7.2_X > package=suse_7.2_supplemental_Xfree > comment=the XFree update > site=ftp2.suse.com > remote_dir=/pub/suse/i386/supplementary/X/XFree86/XFree86-4.1.0-SuSE/suse72 > local_dir+/suse/supplementary/X/XFree86/XFree86-4.1.0-SuSE/suse72 > exclude_patt=source > > I was rather surprized to run YOU and discover it wanted to apply some > updates. I didn't study the situation closely. I didn't see any date info > in YOU, but from watching the results form mirror I thought I was up to > date on everything. I'd also like to know if I can configure YOU to hit my > mirror rather than SuSE ftp. > > I still use YaST1 for my updates, but that too has its limitations. E.g., > no dependency checking. > > Steven At some point in the past a SuSE employee told us the YOU updates were from the same files as the other stuff on the FTP server. When I run YOU it seems to think otherwise. I have everything up to date from the mirror shown above, nonetheless, YOU thinks I have a bunch of stuff out of date. Is this a result of how YOU is tracking what has been updated? I'd really like to hit the ftp server once and do the rest from my local mirror. Any insights? Steven -- Open Source Software depends on your support. If you use it, be sure to give something back. http://www.suse.com | http://www.kde.org http://www.mozilla.org | http://www.xemacs.org

1 0

staroffice line spacing
by Donald Knecht 30 Sep '01

30 Sep '01

is it just me or does everone have this problem, when creating a html doc in star office (5.2), the text line spacing "looks" like it is more than one line, it looks like double spacing to me. this is with the properties set to "single line" spacing. TIA don

3 3

HELP!HELP! Online update chrashed! and now ldpstartproc is loaded!
by Tom Kostiainen 30 Sep '01

30 Sep '01

Yes sorry. Here is the message I get at startup: Starting lpdstartproc: cannot stat /usr/sbin/lpd: no such file or directory. Skipped Ain't lpd some kind of a printing manager? I don't know if lpd was loaded before the update. But will I still be able to print if I set START_LPD to 'no' ? If lpd is not a part of the standard install then I don't have it installed :) But doesn't the online update only mark updates recommended if you have the prog installed? - tk ----- Original Message ----- From: Anders Johansson <andjoh(a)cicada.linux-site.net> To: <suse-linux-e(a)suse.com> Sent: Saturday, September 29, 2001 1:28 PM Subject: Re: [SLE] HELP!HELP! Online update chrashed! and now ldpstartproc is loaded! > On Sunday 30 September 2001 08.23, Tom Kostiainen wrote: > > Hi! > > > > I was letting Online Update do some updating when the screen went black and > > I had to reboot my system. > > > > Now when Linux loads it tries to load a service/deamon called ldpsartproc > > and gets a "cannot find" message for that so it's skipped. > > > > How can I get everything back to normal. Is that ldpstartproc usually > > loaded? If not, how can I remove it? If, how can I restore my old one? > > > > And how about the other updates I loaded, do I have to download them again? > > > > - tk > > Are you sure it's 'ldp' and not 'lpd'? The only abbreviation 'ldp' I've seen > is the linux documentation project, and that would make no sense. I think > it's a case of a missing newline, the script prints 'lpd' and then, > presumably because you don't have lpd installed, you get startproc: file not > found, or some such. > > Unless you were using lpd before the update, it's nothing to worry about. If > you find the message annoying, you can always set START_LPD to "no" in > /etc/rc.config > > If my assumptions are wrong, I'm sorry. > > regards > Anders > > -- > To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com > For additional commands send e-mail to suse-linux-e-help(a)suse.com > Also check the FAQ at http://www.suse.com/support/faq and the > archives at http://lists.suse.com > >

1 0

Jusb, jphoto - anyone successful?
by Adrian Burd 30 Sep '01

30 Sep '01

Hi, I'm trying to install jusb and jphoto http://jphoto.sourceforge.net/ so that I can download images from a Kodak digital camera. I have a PIII box running Suse 7.1 and kernel 2.4 with usb support included. I downloaded Suns jdk and jre environments (versions 1.3.1) and installed them fine. I compiled the jusb programs (jusb.jar and libjusb.so) ok. But installing them and compiling the jphoto programs is causing me major problems. Looking at the install script, it appears that jdk and jre from sun are for an i386 architecture, whereas the gcc in the Suse 7.1 distribution is for an i486 architecture. The install script fails because of this. If I go ahead and install the files manually and then try to compile jphoto I get a host of C errors about operations and structures not allowed on integers. All very strange. Has anyone got any clues as to how to get these codes working properly - I know a friend who compiled them out the box with both Redhat and Mandrake...is Suse THAT different? Has anyone had any success with jusb and jphoto? Many thanks. Adrian Adrian Burd, Dpt. Oceanography, Texas A&M University http://www-ocean.tamu.edu/~ecomodel

1 0

Re: Re: [SLE] Print job queued, but can't start daemon
by THOMAS ADAM 30 Sep '01

30 Sep '01

> Who know the file name and location for the 'lprold' (or something akin > to this) BSD spooler. I looked in "Programs that don't need X" and > could not find it. I'd check the rpm repository: http://www.rpmfind.net --Thomas Adam

2 1

Is this a record?
by Piet le Roux 30 Sep '01

30 Sep '01

This week I upgraded a NT server to SuSE 7.2. Server: Compaq with 2 X P3/600Mhz, 1Gb RAM, 18+36Gb SCSI Raid disks Application: Squid + DNS + Sendmail for 200 users Except for using a nuclear reactor to boil an egg, is this a record for over specifying hardware? Or do you *realy* need a box like this for doing the same on NT? -- Groete | Greetings | Grüßen | Salutations Piet le Roux

2 1

Re: [SLE] Print job queued, but can't start daemon
by Rafael E. Herrera 30 Sep '01

30 Sep '01

It seems that you have a non-empty queue. A way to empty it is to use the utility "lpc". Someone sent me this a while ago, it's always worked for me. > Here is something Jim Hatridge sent me once that worked, hope it helps: > The big problem comes in when you have a large print job to > delete and lpq (the queue) says it's empty. As long as lpq says > it's empty lprm will not work, remember it only works on the que. > What to do when the queue is empty? > First turn off the printer to save paper and ink. Normally > this will not cause any errors on the monitor. You may get an > out-of-paper or printer-offline error in /var/log/messages file, > no problem. > Now try the lpc command. Using the "lpc clean all" command > with option will delete all unprintable jobs with their data and > control files. Unfortunately this only works if the files were > bad to begin with. If they are fine, you just changed your mind, > then we have problems. > The final solution is to go into the spool and delete the > files by hand. As root cd over to /var/spool/lpd, when you list the > files you will find at least 3 difference dir's for each printer. > There is one dir for the printer's ascii files, one for the PS > files, and one for raw data. Now cd to the correct dir, in this > dir you should find two files for each print job one fd00000000 > and the other cd00000000. The first is the data file, ie what you > wanted printed and the other is the control file, ie how you > wanted it printed. Both of these must be deleted, "rm > cd00000000". While in this dir you should find a lock file, > delete it. This should clear your print job out of the system. > Now to be on the safe side, in root do "lpc restart all". This > will start new daemons and clear any old files out of each print > spool. At this point put your printer back on line. It should > print a few more lines, whatever was in it's buffer and then > stop. You will need to reset it. Rafael

2 1

Re: Re: [SLE] Print job queued, but can't start daemon
by THOMAS ADAM 30 Sep '01

30 Sep '01

> > Output of ps aux | grep ldp is: > > root 1159 0.0 0.3 1228 412 ttyp1 S 11:36 0:00 grep ldp > > I tried kiling 1159, 1228, and 412, and output for each said: No such > PID Umm, 1159 would obviously not die, since it used to be the process of the command "grep lpd". To avoid this again, try the following: ps aux | grep -v "grep lpd" the "-v" switch reverses the sense of the match. But this is a digression from your original question :-) You'll have to star the lpd daemon again (as root). This should have cleared the buffer by now. --Thomas Adam

2 1