Mailinglist Archive: opensuse-bugs (15090 mails)
| < Previous | Next > |
[Bug 304632] Apps takes 5-10 seconds to launch if hostname is not resolvable
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Wed, 19 Sep 2007 07:13:41 -0600 (MDT)
- Message-id: <20070919131341.A5572CC796@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=304632#c26
--- Comment #26 from JP Rosevear <jpr@xxxxxxxxxx> 2007-09-19 07:13:41 MST ---
(In reply to comment #24 from Magnus Boman)
> Damn! Can't reproduce it anymore :-/ I recently added DynDNS to my environment,
> so even though my hostname is not resolvable locally, it will go across the
> router and resolve it.
> So guess this bug is dependent on the env. If, after an install, it's possible
> to resolve ping <hostname>, then this issue will not be seen. But if it can't
> be resolved in anyway (and no, it does not help to unplug the network), then
> this issue will show.
> Perhaps anyone else that have seen this bug can confirm my theory?
That is the theory we have been looking at since #5, however its not always
replicable (at least for me, mtgordon or hpj). The gdm patch was a potential
issue, but did not seem to resolve Thiago's problem. Yast not writing out the
host as 127.0.0.2 is another potential problem.
I'm installing b3+ into vmware now to collect logs on the 127.0.0.2 issue right
now.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
--- Comment #26 from JP Rosevear <jpr@xxxxxxxxxx> 2007-09-19 07:13:41 MST ---
(In reply to comment #24 from Magnus Boman)
> Damn! Can't reproduce it anymore :-/ I recently added DynDNS to my environment,
> so even though my hostname is not resolvable locally, it will go across the
> router and resolve it.
> So guess this bug is dependent on the env. If, after an install, it's possible
> to resolve ping <hostname>, then this issue will not be seen. But if it can't
> be resolved in anyway (and no, it does not help to unplug the network), then
> this issue will show.
> Perhaps anyone else that have seen this bug can confirm my theory?
That is the theory we have been looking at since #5, however its not always
replicable (at least for me, mtgordon or hpj). The gdm patch was a potential
issue, but did not seem to resolve Thiago's problem. Yast not writing out the
host as 127.0.0.2 is another potential problem.
I'm installing b3+ into vmware now to collect logs on the 127.0.0.2 issue right
now.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |