[opensuse] 11.0 cusrses mode yast printer config fail
Although I've been using 11.0 since it came out on several boxes, I haven't happened to need a print spooler on any of those until yesterday, when I discovered that the yast cups interface is broken, at least for me at least in the curses interface. Starting with an 11.0 install with up to the minute online updates applied, and the cups service running (though never been configurd yet): yast, Printer, Printers & queues, add, (x) Network Printers (x) Print Directly to a Network Printer (x) Direct TCP Port Printing ┌Connection Information────────────────────────────────────┐ │ Hostname of Print Server │ │ mycustomer.dyndns.biz▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒↓[Look Up↓] │ │ TCP Port Number │ │ 9100▒▒▒▒▒▒▒▒▒▒▒ │ │ │ └──────────────────────────────────────────────────────────┘ [Test Remote Socket Access] ┌──────────────────────────────────┐ │ │ │ The print server is accessible. │ │ └───────────│ [OK] │ ──────────┘ └──────────────────────────────────┘ ┌Queue Name and Spooler Settings───────────────────────────────────┐ │Name for Printing │ │printer▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │ │ │Printer Description │ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │Printer Location │ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │[ ] Share Printer │ │ │ │[ ] Do Local Filtering │ │ │ └──────────────────────────────────────────────────────────────────┘ Now it brings you back to the screen where you can add/edit/delete more queues, or test printing or finish. At this point there is still no /etc/cups/printers.conf When you either finish or if you try to test printing, either way it tries to save the config you just defined and fails. (x) Test Text Printing │ ┌─────────────────────────────────────────────────────┐ │ │ │ Error │ │ │ │ An error occurred while communicating with the │ │ │ │ CUPS server while saving queue y2test. │ │ │ │ │ │ │ │ cups(File)DoRequest error: client-error-bad-request │ │ │ │ [OK] │ ────┤───┘ │ └─────────────────────────────────────────────────────┘ ────────┐ Then this error which is unimportant, it's expected given above. The queue was not actually created, and so of course the lpd client can't use it. │ ┌────────────────────────────────────────────────────┐ │ │ │ Unable to print the test page. │ │ │ │ │ │ │ │ Output from lpr: │ │ │ │ /usr/bin/lpr: The printer or class was not found. │ │ │ │ [OK] │ ────┤───┘ │ └────────────────────────────────────────────────────┘ ────────┐ You have to choose Abort to get out of the printer setup screen since Finish just fails the same way forever. I also tried variations on the specific config options, like, although I very much should be able to say no local filtering (ie: don't use any kind of printer driver or ppd file) maybe that's not so common and some part of the tool just assumes theres always a driver. etc.. So I also tried with local filtering and selecting an appropriate printer model (HP LaserJet 1320, totally common pcl driver), tried enabling sharing, tried lpd as well as raw tcp, to a known good and accessible lpd server. In all cases I got the same error above when it came time to actually save the config at the end. However, when I copied the printers.conf from the working 10.2 box, it worked. just a straight rsync copy, no edits at all. Then rccups stop, rccups start. And printing to those printers immediately worked. printers.conf just has this, one lpd printer and two jetdirect, no sharing, no filters/drivers. The comment shows a recent write because I had gone into yast-printers on the old box to delete a printer. The 3 remaining printers haven't been touched in around a year. The cups version shows it didn't come from the 11.0 box that's using it. The new box has cups 1.3.7. Obviousy I rewrote the customer name and their hostname in the email. ---TOF--- # Printer configuration file for CUPS v1.2.7 # Written by cupsd on 2008-10-14 10:08 <DefaultPrinter mycustomer_checks> Info HP DeskJet 540 Location My Customer, Eileen's Office, winxp psu share DeviceURI lpd://mycustomer.dyndns.biz/checks State Idle StateTime 1229696182 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy retry-job </Printer> <Printer mycustomer_laser> Info HP LaserJet 1320 Location My Customer DeviceURI socket://mycustomer.dyndns.biz:9100 State Idle StateTime 1229727065 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy retry-job </Printer> <Printer mycustomer_matrix> Info Okidata Microline 421 Location My Customer DeviceURI socket://mycustomer.dyndns.biz:9101 State Idle StateTime 1229726894 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy retry-job </Printer> ---EOF--- I looked at cupsd.conf too but I never made any changes to that on either the old or new boxes and they looked about the same on both boxes. Both boxes have the same rules in susefirewall and it's active on the old box and disabling the firewall didn't help the new box, nor did reenabling the firewall break it. I reproduced the problem on 4 boxes, but, they are all practically clones of each other. Installed at the same time onto identical hardware from the same install source using the same install recipe. This all works fine in at least 10.0, 10.1, 10.2, 10.3, not just 10.2. 9.3 and 9.1 the interface is a little different but I don't have any problems there either. I haven't istalled 11.1 anywhere yet. Can anyone else confirm this or know about it and know what the problem is and a work-around other than manually creating & editing printers.conf? Pretend I only have serial console access and that http://localhost:631 can't be operated well enough via lynx. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2008-12-23 at 06:54 -0500, Brian K. White wrote: ...
I reproduced the problem on 4 boxes, but, they are all practically clones of each other.
Then you could write a bugzilla, the problem can be confirmed.
Can anyone else confirm this or know about it and know what the problem is and a work-around other than manually creating & editing printers.conf? Pretend I only have serial console access and that http://localhost:631 can't be operated well enough via lynx.
Well, the workaround is http://localhost:631. If lynx is not good enough, there are more: links, w3m... and of course, you can use mozilla from another computer with graphical interface, but first you have to edit the security settings of cups so that it allows remote access. You do have a network, so it should be feasible. And, if the network is secure and not accessible, then you can get another network through the serial port (ppp), instead of console. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklQ3y8ACgkQtTMYHG2NR9Um4QCgjIZGzXq1ssbjq925gh0CvKuM +K4AnjT+UFfamFNvDqoC/2GKKHEYG6qC =mvNo -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
----- Original Message ----- From: "Carlos E. R." <robin.listas@telefonica.net> To: "OS-en" <opensuse@opensuse.org> Sent: Tuesday, December 23, 2008 7:53 AM Subject: Re: [opensuse] 11.0 cusrses mode yast printer config fail
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday, 2008-12-23 at 06:54 -0500, Brian K. White wrote:
...
I reproduced the problem on 4 boxes, but, they are all practically clones of each other.
Then you could write a bugzilla, the problem can be confirmed.
Can anyone else confirm this or know about it and know what the problem is and a work-around other than manually creating & editing printers.conf? Pretend I only have serial console access and that http://localhost:631 can't be operated well enough via lynx.
Well, the workaround is http://localhost:631. If lynx is not good enough, there are more: links, w3m... and of course, you can use mozilla from another computer with graphical interface, but first you have to edit the security settings of cups so that it allows remote access. You do have a network, so it should be feasible.
And, if the network is secure and not accessible, then you can get another network through the serial port (ppp), instead of console.
I know all that but the problem is not get a printer working. I did that a lot easier than setting up ppp over a series of serial, telnet & ssh connections and getting all the intervening connections into binary modes that wouldn't choke on ppp protocol data (or munge it). The problem is yast curses interface should work. I originally wrote this whole big tirade pointing out why it should work and why none of those options are any sort of excuse, but really it just comes down to, a) lynx actually seems to work ok, so maybe that wouldn't be such a bad answer, and/or b) Sure I can also just create/edit the files directly without yast or any other front end, which is exactly what I did here, but if that's a valid argument for one thing then it's a valid argument for everything and if I have to do that as a rule, then I should be using debian or gentoo where I can -really- do it myself. Suse, as an rpm based distro that isn't redhat, without yast being really really excellent way above anything anyone else has, is just a lemon. 11.0 is pretty well peppered with breakages and downgrades in yast curses interface. And I only use the curses interface. I don't have gui's on my servers and don't want to enable remote access to the http based things like swat/cups/apcupsd. Setting up a single form of protected shell access, and only having to worry about the security that one thing, and having text based utils that are used locally via that shell access, and without any ^%$# vpns, the same app, working the same way, the same interface, whether you're remote, local, via telnet, via serial, via ssh to serial console appliace, via direct modem dialup, via the servers vga console, etc... is SO the only sane way to go untill you scale up so far that the only sane way to go is centralized administration systems (ie, neither yast nor direct admin). -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2008-12-23 at 09:46 -0500, Brian K. White wrote:
I know all that but the problem is not get a printer working. I did that a lot easier than setting up ppp over a series of serial, telnet & ssh connections and getting all the intervening connections into binary modes that wouldn't choke on ppp protocol data (or munge it). The problem is yast curses interface should work.
Right, so then you should write a Bugzilla to get the issue attended to by the appropiate people. Here, on the list, we can do nothing, but offer you workarounds. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklRAIkACgkQtTMYHG2NR9VbtACeLTr9Ac3T8wlouyU+F0NN6eWU 5PMAoJFR1LAZlI0H03yfxVRmOXYaG5zR =E5YK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2008/12/23 Carlos E. R. <robin.listas@telefonica.net>:
On Tuesday, 2008-12-23 at 09:46 -0500, Brian K. White wrote:
I know all that but the problem is not get a printer working. I did that a lot easier than setting up ppp over a series of serial, telnet & ssh connections and getting all the intervening connections into binary modes that wouldn't choke on ppp protocol data (or munge it). The problem is yast curses interface should work.
Right, so then you should write a Bugzilla to get the issue attended to by the appropiate people. Here, on the list, we can do nothing, but offer you workarounds.
Good point! I noticed preparing to submit Partitioner Bugzilla's that the developer, actually said she used the ncurses interface, as it's convenient I guess for testing. However somethings she'd noticed as frustrating. But and here's the rub, they don't get fixed, until there's a real user noticing and giving bug input. So basically rather than sound off about bugs in this list, Bugzilla though it can be frustrating, is the way to try and get a change for the better. With no feedback, managers will presume something is little used or not really necessary, and it's hard to interest journos' in non-graphical hoopla. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
----- Original Message ----- From: "Carlos E. R." <robin.listas@telefonica.net> To: "OS-en" <opensuse@opensuse.org> Sent: Tuesday, December 23, 2008 10:15 AM Subject: Re: [opensuse] 11.0 cusrses mode yast printer config fail
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday, 2008-12-23 at 09:46 -0500, Brian K. White wrote:
I know all that but the problem is not get a printer working. I did that a lot easier than setting up ppp over a series of serial, telnet & ssh connections and getting all the intervening connections into binary modes that wouldn't choke on ppp protocol data (or munge it). The problem is yast curses interface should work.
Right, so then you should write a Bugzilla to get the issue attended to by the appropiate people. Here, on the list, we can do nothing, but offer you workarounds.
I consider it wasteful of developers time to submit a bugzilla without first at least trying to see if it's just me. Perhaps this is not the right way to think of bugzilla. I can see that it could be treated like a database where it doesn't really matter if my problem is a real problem with the software, or merely a problem with the ui's intuitiveness, or if the user is just a complete idiot, and the reports are all just data, the more the better, and mostly only looked at statistically. But I don't know if developers actually treat it that way or if every single report costs somebody time. Perhaps either of those ways to think of bugzilla is correct, depending on the project in question. What I do know is I have submitted only very few bugzilla reports to different projects, and I know in each case I spent a lot of time constructing exact tests that prove and reproduce the problem in the most succinct yet unambiguous way. And I know that they each received a few different peoples actual attention and eventually a resolution. So, sure, bugzilla, but here (or similar) first is all. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2008/12/24 Brian K. White <brian@aljex.com>:
I consider it wasteful of developers time to submit a bugzilla without first at least trying to see if it's just me.
It's very good. The suggestions to submit it to Bugzilla, weren't intended as personal criticism, just that the problem you found, seemed most likely to get a real resolution that way. Searching Bugzilla is useful however, sometimes you find it's been submitted, but all too often the Bug Reporter appears to have lost interest and fails to provide "Needed Info". So a common sense approach, on case by case, like you do does seem very sensible. I personally don't want to put a huge amount of effort, into a Bugzilla report, until I've actually got the attention of someone who likely can fix the problem. So I try to start with the clearest description I can, and include obviously relevant info. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello, On Dec 23 06:54 Brian K. White wrote (shortened):
... using 11.0 ... ... yast, Printer, Printers & queues, add, ... ... cups(File)DoRequest error: client-error-bad-request ...
Usually a client-error-bad-request error since openSUSE 11.0 is caused by what we described in our release notes, see /usr/share/doc/release-notes/openSUSE/RELEASE-NOTES.en.html "CUPS (Common UNIX Printing System) and UTF-8 Encoding". Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Brian K. White
-
Carlos E. R.
-
Johannes Meixner
-
Rob OpenSuSE