| Summary: | unable to retrieve printer list | ||
|---|---|---|---|
| Product: | [Unmaintained] kdeprint | Reporter: | VTVL <john.sved> |
| Component: | general | Assignee: | KDEPrint Devel Mailinglist <kde-print-devel> |
| Status: | CLOSED NOT A BUG | ||
| Severity: | normal | CC: | jlayt |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
VTVL
2006-04-21 12:20:10 UTC
On 21 April 2006 06:20, t-poppy wrote: > When starting a print job, the initializing manager message appears, time > out and the error message "unable to retrieve printer list" appears. Please post that user's ~/.lpoptions file. Also, specify what permissions that file has. > This behaviour only occurs for one user. Creating a second user account > and logging into session to test gives a normal - error free - behaviour. > Another PC host on the LAN also works fine. This another PC works fine for the user which has the error on the first PC? If yes, is its account shared from a server by NFS? > The problem started after an upgrade from SuSE 9.3 to 10.0. Was this upgrade on the PC or on the print server? Or both? You migh want to look at configuration files in /etc/cups. E.g. client.conf on the client PC and printers.conf, cupsdconf on the server PC. > Please post that user's ~/.lpoptions file. Also, specify what permissions that > file has. > The user ~/.lpoptions file has permissions -rw-r--r-- user group users the contents of the file: Default styluscolor600 lpoptions in /etc/cups just lists the various instances that I set-up as root > > This another PC works fine for the user which has the error on the first PC? > If yes, is its account shared from a server by NFS? > There are different users on each PC. All other users can print with kdeprint. > > Was this upgrade on the PC or on the print server? Or both? > The upgrade was on all PCs. as a clean new installation. All the /home/user/ files we backed-up and then restored selectively. It may be that some /.kde files were restored. (e.g. kopete contact list and similar) > You migh want to look at configuration files in /etc/cups. E.g. client.conf on > the client PC and printers.conf, cupsdconf on the server PC. > On the client PC etc/cups/client.conf is empty The cupsd.conf om the server is OK. At least all other client users can print. (Note that AuthType was BasicDigest which is wrong. I changed it to None and commented AuthClass and AuthGroupName ) The present problem of just one particular client user not able to retrieve the printer list continues. <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-15" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#330033"> <br> <blockquote cite="mid20060421105646.23247.qmail@ktown.kde.org" type="cite"> <pre wrap=""> Please post that user's ~/.lpoptions file. Also, specify what permissions that file has. </pre> </blockquote> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <meta name="Generator" content="Kate, the KDE Advanced Text Editor"> <pre>The user ~/.lpoptions file has permissions -rw-r--r-- user group users the contents of the file: Default styluscolor600 lpoptions in /etc/cups just lists the various instances that I set-up as root </pre> <blockquote cite="mid20060421105646.23247.qmail@ktown.kde.org" type="cite"> <pre wrap=""> This another PC works fine for the user which has the error on the first PC? If yes, is its account shared from a server by NFS? </pre> </blockquote> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <meta name="Generator" content="Kate, the KDE Advanced Text Editor"> <pre>There are different users on each PC. All other users can print with kdeprint. </pre> <blockquote cite="mid20060421105646.23247.qmail@ktown.kde.org" type="cite"> <pre wrap=""> Was this upgrade on the PC or on the print server? Or both? </pre> </blockquote> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <meta name="Generator" content="Kate, the KDE Advanced Text Editor"> <pre>The upgrade was on all PCs. as a clean new installation. All the /home/user/ files we backed-up and then restored selectively. It may be that some /.kde files were restored. (e.g. kopete contact list and similar) </pre> <blockquote cite="mid20060421105646.23247.qmail@ktown.kde.org" type="cite"> <pre wrap=""> You migh want to look at configuration files in /etc/cups. E.g. client.conf on the client PC and printers.conf, cupsdconf on the server PC. </pre> </blockquote> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <meta name="Generator" content="Kate, the KDE Advanced Text Editor"> <pre>On the client PC etc/cups/client.conf is empty The cupsd.conf om the server is OK. At least all other client users can print. (Note that AuthType was BasicDigest which is wrong. I changed it to None and commented AuthClass and AuthGroupName ) The present problem of just one particular client user not able to retrieve the printer list continues.</pre> </body> </html> Can you check on the client PC which CUPS server kdeprint is trying to connect to? Normally, it should be mentionned in ~/.kde/share/config/kdeprintrc (or whatever directory where KDE stores its config files). Michael Goffioul wrote: [bugs.kde.org quoted mail] [CUPS] Host=hostname InstallDir= Login= Port=631 SavePassword=false Note: the actual hostname is correct. It is a name and not an IP number. Note 2. on the test user kdeprintrc and the /root kdeprintrc the above is not listed. Can you try to remove the kdeprintrc file and restart KDE? Is the actual hostname known to the PC where the problem occurs? I mean, can it be resolved without requesting a DNS server? If you use an IP number instead of the hostname, or add an alias in the /etc/hosts file, does it change anything? Michael. Michael Goffioul wrote: [bugs.kde.org quoted mail] I first experimented with Host=serverhostname using name, name.domain and 192.168.1.2 The first case caused the error described. The second and third caused the printer list error not to be reported but no remote printer was listed. Then I compared the kdeprintrc files in root and the test user. The items commented out below were not present at all. So I commented these out. The next test worked correctly ! :) So the kdeprintrc may have been a restored older version. The odd thing is that this worked OK with SuSE 9.3. I do not know what KDE version change has occurred with SuSE 10.0. A interesting question is whether this problem occurs if one just performs an upgrade over SuSE 9.3 to 10.0. I certainly am not going to do this experiment. [$Version] update_info=kdeprintrc.upd:kde-3.1-toolbar #[CUPS] #Host=severhostname #InstallDir= #Login= #Port=631 #SavePassword=false #[Filter] #LocationRe= #Printers= #[General] #ExternalPreview=false #PreviewCommand=gv #ShowStatusMsg=true #TestPage= #TimerDelay=5 #UseLast=true [Jobs] Limit=0 Size=857,250 -- John Under your test user (when it's working), what do you get as CUPS server when you open the kdeprint settings dialog (print dialog -> System Options -> CUPS tab)? Michael. Sorry for delayed reply: As test user when CUPS was invoked via kdeprint, the first time it reported the printer list error. On the second try it worked correctly ! In both cases and with normal user the Server is indicated as localhost:631 -- John Michael Goffioul wrote: [bugs.kde.org quoted mail] I assume this bug can be closed. Looks like a fault configuration, caused through an upgrade. Closing old Resolved status bug. |