From the Clients I can see ALL the Printers, however they remain (on the
Despite a relatively easy setting up of a CUPS Print Server when I open ANY browser on that PC Http://localhost:631 I just get the error "404 Not Found" Yes cups is running as a service. I have performed an unconditional update from disk and available cups update I think I may have to delete all, however this is no problem if it will fix the issue. I use KDE and now I really do not understand the need for the KDE Print Manager front end I can view. print servers cue) AND I cannot print locally off course. Any one else got any ideas, if you have please don't give me a whole lot of command line entries if you don't need to. If I don't test the user interface, I never find bugs - I know we all would love just to quickly fix things from the console, but this does not help us identifying and fixing bugs in the UI. Cheers to all Scott
On Wednesday 02 May 2007, Registration Account wrote:
Despite a relatively easy setting up of a CUPS Print Server when I open ANY browser on that PC Http://localhost:631 I just get the error "404 Not Found" Yes cups is running as a service.
/etc/cups/cupsd.conf check near the bottom to see if permissions are correct. And be sure you are attempting to log in as the proper person, (which is usually not root). Technically, to be pedantically correct, there should be a trailing / but it should work anyway. Run netstat -anp and verify that something (cupsd) is listening on 631 (usually, but not always on all interfaces). -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
The .RPM database is corrupt and now repaired. This is the second PC in which this has happened.All you tests confirm and I am logged in as a normal user. If worst things come to worse I will delete the version and re-install 10.1 - is a far more stable, but cannot update itself - you must use online update as you should do and both version will go down in history as versions that a buggy are cannot update them selves reliably without using online update. cheers and thanks your advise Scott >:o John Andersen wrote:
On Wednesday 02 May 2007, Registration Account wrote:
Despite a relatively easy setting up of a CUPS Print Server when I open ANY browser on that PC Http://localhost:631 I just get the error "404 Not Found" Yes cups is running as a service.
/etc/cups/cupsd.conf check near the bottom to see if permissions are correct. And be sure you are attempting to log in as the proper person, (which is usually not root).
Technically, to be pedantically correct, there should be a trailing / but it should work anyway.
Run netstat -anp and verify that something (cupsd) is listening on 631 (usually, but not always on all interfaces).
I have been able to duplicate the problem by opening Yast>Security and Users>Local Security>set file permission to secure. There must be a cron job that runs sometime after this that causes the problem. Port 631 has a listed listening device. There are 3 versions of cupsd.conf/.default.conf O - The files are all owned by root, however respectively Grouped root/nobody/nobody. ALL files have -rw-r----- rights There are 2 x classes.conf and classes.conf O and printers.conf and printers.conf O Am I possibly correct in assuming by changing this global file permission I have stuffed this cups server twice in a row????? If so I will issue a bug report, however what's with this O extension.....I.E file.nnn / file.nnn O Scott Am I seeing what I John Andersen wrote:
On Wednesday 02 May 2007, Registration Account wrote:
Despite a relatively easy setting up of a CUPS Print Server when I open ANY browser on that PC Http://localhost:631 I just get the error "404 Not Found" Yes cups is running as a service.
/etc/cups/cupsd.conf check near the bottom to see if permissions are correct. And be sure you are attempting to log in as the proper person, (which is usually not root).
Technically, to be pedantically correct, there should be a trailing / but it should work anyway.
Run netstat -anp and verify that something (cupsd) is listening on 631 (usually, but not always on all interfaces).
participants (2)
-
John Andersen
-
Registration Account