I've reported it to SuSE and have had a ticket open on it for 8 weeks now. SuSE ships with the cups beta for my printer. Maybe red hut pizza went for the stable horse. THanks all the same. Steve. On Monday 17 February 2003 12:23, you wrote:
Printing must be either a cups version or a suse problem. I run suse 8.1 pro on my laptop and redhat 8 on my desktop , same printer, suse cannot get the page right and redhat prints perfect. Suse needs an update to fix the problem. I hope this helps Jim Jordan
On Sunday 16 February 2003 11:44, fsanta wrote:
We use kde in an international school under 8.1. I don't know whether schools count as desktop even though the clients are on desks. The transition was smooth. The only thing that doesn't work properly is the printing. In Linux I don't think it ever will. Yet.
On Sunday 16 February 2003 15:07, Paul Benjamin wrote:
It may come as a shock to you but no one says that Linux is ready for the desktop. I don't think Linux is ready for my Aunt either.
I am willing to put up with the problems because I am sick of Microsoft and every other box software "sellers" calling me a thief until I prove otherwise. I may be a freeloader who hasn't given anything back but no one is going to fine me because I lost my SuSE 8.1 box.
Check in every year or so because I have seen Linux improve over the last three years and I am sure that even your middle age non-computer type would be able to use it in another three years. Then I would have never allowed not-computer types to use Windows 3.1 ten years ago, but they still did some how. ;-)
pben
On Sunday 16 February 2003 08:51 am, Michael Satterwhite wrote:
As a general desktop, that is.
I was thinking of the problem I had yesterday trying to restart printing services (which I still haven't found in the documentation).
For Linux to be a general desktop system, it needs to be usable by the general population at large. A middle age non-computer type would *NEVER* be able to use Linux. Until it reaches the point that it can recover gracefully from something as simple as a printer running out of paper, it really isn't going to make large inroads against Windows. If you told an average user "just restart the print service", he'd reply "Why do I have to do that? Windows kept going automatically."
There is no question that in many ways, Linux is superior to Windows. Until it grows a bit more in the area of being able to recover from simple problems, the average person isn't going to use it.
I'm a Linux newbie, so I really don't know what's happening in this area. Is there work being done on this type of recovery?
From the remote I can see the server: adriel@orion:~> lpstat -h 192.168.0.4 -o lp_color -p lp_color
I have installed and uninstalled CUPS many times over the last few days but my problem persists. I'm using SuSE 8.1 Pro on two computers on a LAN. They both have CUPS installed in the server configuration. The one with the printer attached is the server and works fine. The other one is the remote. First I make sure cups is started on the remote machine: # /etc/init.d/cups restart Shutting down cupsd done Starting cupsd done printer lp_color is idle. enabled since Jan 01 00:00 I can access the cups server computer from the remote with my browser. But I can't print from the command line: adriel@orion:~> lpr -Plp_color mouse_howto.txt lpr: unable to print file: server-error-service-unavailable Unless I do this: # lpr -Plp_color@192.168.0.4 mouse_howto.txt In Yast2 when I start the printer configuration tool a little window opens saying:"Initializing cups server. This usually takes one or two minutes." It takes twelve minutes. In the edit configuration window if I select "clear current configuration" or any of the test printing options in the printer module. A little window opens saying: "Initializing cups server. This usually takes one or two minutes." It takes twelve minutes. After I hit the Finish button the same little window opens saying:"Initializing cups server. This usually takes one or two minutes." It takes twelve minutes. And just before it finishes I get this error message: "error occurred while saving queue lp_color. The configuration is saved but none of my printer queues are visable from the applications on the remote machine;instead there is a dotted line. If I use the client configuration on the remote machine I can print using: lpr -Plp_color mouse_howto.txt but I get the dotted line instead of a selection of print queues when I select print in the applications. There is no /etc/printcap file automatically generated. Here is my printers file: # cat /var/lib/YaST2/printers $["default":"lp_color", "deleted":[], "printers":[$["accepting":true, "allowusers":[], "bannerend":"none", "bannerstart":"none", "config":"gs-hpijs-dj970-color-low", "cups-state":"changed", "database":nil, "denyusers":[], "device":"hp-deskjet-970c", "device_ieee":"DeskJet 952C", "ff":false, "info":"", "location":"", "lprng-state":"void", "name":"lp_color", "newer_gs_upp":false, "options":$["papersize-all-inkjet":1], "ownppd":"", "raw":false, "saved":$["upp":"", "upp_fname":""], "state":"idle", "type":"yast2", "uri":"ipp://192.168.0.4/printers/lp_color", "vendor":"hp", "vendor_ieee":"HP"]]] Here is some of the error log: Listening to 0:631 I [17/Feb/2003:20:11:55 -0800] Sending browsing info to c0a800ff:631 I [17/Feb/2003:20:11:55 -0800] Configured for up to 100 clients. I [17/Feb/2003:20:11:55 -0800] LoadPPDs: Read "/etc/cups/ppds.dat", 1739 PPDs... I [17/Feb/2003:20:11:56 -0800] LoadPPDs: No new or changed PPDs... W [17/Feb/2003:20:12:26 -0800] LoadDevices: Backend did not respond within 30 seconds! E [17/Feb/2003:20:23:17 -0800] Scheduler shutting down due to SIGTERM. I've run out of ideas. Can anyone help me solve this problem? Jerome.
On Tue, 18 Feb 2003 19:53, Jerome Lyles wrote:
I have installed and uninstalled CUPS many times over the last few days but my problem persists. I'm using SuSE 8.1 Pro on two computers on a LAN. They both have CUPS installed in the server configuration. The one with the printer attached is the server and works fine. The other one is the remote.
------- Snipped ------------------
I can access the cups server computer from the remote with my browser. ------ Snipped -------------------- I've run out of ideas. Can anyone help me solve this problem? Jerome.
It appears you have permission problems with browsing. Yast does not really setup the configuration files properly for a LAN install. The easiest way to fix the problem is to edit the file /etc/cups/cupsd.conf on the machine which has the printer connected. This file is very well commented. Before you start please backup this file so that if you muck up anything you can revert back. Now with your favourite editor open /etc/cups/cupsd.conf and go down to about Line 50 you will see #ServerName myhost.domain.com Add a new entry after this line as ServerName <your full server name> e.g If your server is known as fred and your domain is linux you would add ServerName fred.linux At Line 420 you will see ######## ######## Browsing Options ########
From there go down to about Line 478 #BrowseAddress x.y.255.255 #BrowseAddress x.255.255.255 Now add in BrowseAddress <Your IP Address.255> eg if your ip address is say 10.11.12.1 you would enter BrowseAddress 10.11.12.255
Further down add in BrowseAllow
I've run out of ideas. Can anyone help me solve this problem? Jerome.
It appears you have permission problems with browsing. Yast does not really setup the configuration files properly for a LAN install.
The easiest way to fix the problem is to edit the file /etc/cups/cupsd.conf on the machine which has the printer connected. This file is very well commented.
Before you start please backup this file so that if you muck up anything you can revert back.
Now with your favourite editor open /etc/cups/cupsd.conf and go down to about Line 50 you will see #ServerName myhost.domain.com Add a new entry after this line as ServerName <your full server name> e.g If your server is known as fred and your domain is linux you would add ServerName fred.linux
At Line 420 you will see ######## ######## Browsing Options ########
From there go down to about Line 478 #BrowseAddress x.y.255.255 #BrowseAddress x.255.255.255 Now add in BrowseAddress <Your IP Address.255> eg if your ip address is say 10.11.12.1 you would enter BrowseAddress 10.11.12.255
Further down add in BrowseAllow
e.g as per above IP address BrowseAllow 10.11.12.* THat should get you going. There are a number of other options you can add in latter in this file. Save the file and restart cups.
-----------------------------------------------
On the client machine edit /etc/cups/client.conf and go to line 40 and add in your server name the same as you did before e.g ServerName fred.linux
You should now be able to print from the client machine now.
And so it is;I can! Thankyou, Jerome
participants (3)
-
fsanta -
Graham Smith -
Jerome Lyles