[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 84261] kcontrol can't nitialize itself if accessing remote
From:       carl <gooly () gmx ! at>
Date:       2004-07-02 10:17:44
Message-ID: 20040702101744.15530.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=84261      




------- Additional Comments From gooly gmx at  2004-07-02 12:17 -------
hmm, 
at a first glance and before trying what you ask me to do,
OpenOffice can print with NO problems with NO delay.
Even Yast2 (Suse 9.1) installs the remote printer correctly,
according to its behaviour. So here is no network problem!
10.10.10.1 the printer-server has 'rosemary' as pc-name


Am Freitag, 2. Juli 2004 10:36 schrieb Michael Goffioul:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=84261
>
>
>
>
> ------- Additional Comments From kdeprint_bugs swing be  2004-07-02 10:36
> ------- It looks like the hang up appears when trying to download the
> driver file from the print server. This might be a network configuration
> problem. Could you start kwrite within gdb and generate a backtrace when
> the problem appears: 1) # gdb $KDEDIR/bin/kwrite
> 2) # (gdb) run
> 3) try for example to open the printer properties dialog and when kwrite
> hangs up, go back to the terminal where you started it and hit CTRL-C 4) #
> (gdb) bt
>
> Could you tell me the URI used for your printer (you can find it in the
> lower panel of the KDE print manager in kcontrol)? 

the remote printer in KDE is correctly 'announced' as 
Verbunden mit 10.10.10.1:631
(eng: connected with 10.10.10.1:631)
During the whole configuration I only used th IP-Addr. 10.10.10.1 and not the 
network name 'rosemary'

> From your log files, it 
> looks like your print server is "rosemary". Is this network name known to
> your client?
yes, should be!
	ping rosemary 
(just this) works perfectly!
> What you can try as well is to edit /etc/cups/cupsd.conf on 
> the print server, set "ServerName" to the real server IP, then restart CUPS
> on the server.
hmm, neither the ip-Addr 10.10.10.1 nor its net-name I can fin in cupsd.conf.
On the client the /ect/cups/client.conf has ServerName 10.10.10.1
In cupsd.conf ServerName is commented (disabled)
[prev in list] [next in list] [prev in thread] [next in thread]