27 Jan
2013
27 Jan
'13
7:23 a.m.
On Friday 25 January 2013 22:54:55 Nick Leverton wrote:
In article
<201301240054.50984.slavek.banko(a)axis.cz>cz>,
Slávek Banko <trinity-devel(a)lists.pearsoncomputing.net> wrote:
this is exactly the
reason why we have not integrated the patch into KWin.
Hi all,
I have a problem to discuss:
Before long time I prepared a patch, which is included in the commit
9e3f8a7f. It was based on a completely broken patch for KDE4 - commit
c24ea2b4. Our patch works correctly, but contains one potential risk - is
dependent on DNS => on the network delays.
First question is, how big is this risk, because we have a patch
incorporated nearly a year ago and no problems observed. The fact is that
if the user will have a problem with the network, probably will not even
be able to open a remote window. However, this risk actually exists.
It is possible that one DNS lookup may freeze for a while on a generally
working link, if you hit a DNS server that does not respond.
I have my suspicions about Plasma on KDE4
sorry I do not get what you want to say
with this comment
but I haven't noticed this
causing any general hang on Trinity up to 3.5.13.
which says exactly: nothing. You
would only be able to hit the problem if you
start an application setting a FQDN name (e.g. libre office) and DNS not
working at this time. Most probably chance: session restore.
--
Martin Gräßlin