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

List:       kde-linux
Subject:    [kde-linux] RE: Rather odd KDE 2.2 Problem
From:       Michael Kalus <mkalus () expressvu ! com>
Date:       2001-08-30 20:01:59
[Download RAW message or body]

Interresting, but not the case in this case. The Notebook is on the same
Subnet and all of them are sitting behind a firewall.

Also the IP is static as such there is no Name Assigned or DHCP used.

Thanks for the hint though, I think it's a problem with Matrox and the KDE
Package....

Michael

> The reason I asked if you had cable is that cable connection 
> apps seem to like
> setting the hostname of the computer. If you load kde with 
> the hostname equal
> to localhost.localdomain and then connect through your cable 
> and its app
> changes your hostname to the name of its system ie: 
> user.cablenet.com; then the
> next time you try to load kde, dcop will fail because its 
> pipes/sockets etc
> have the wrong name. 
> The solution is to set your app so it doesnt do that anymore 
> or modify startkde
> like RH has in kde2.2 so it deletes all the 
> dcop-hostname-blah files in your
> home dir and in temp before it starts kde. That is what you 
> have to do by the
> way.
> 
> Andrew
> 
___________________________________________________
This message is from the kde-linux mailing list.
Account management:  http://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

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