GNOME desktop slow to fully start

[azolkipl]

The gnome desktop was very slow to fully load. The window borders did not come up when starting any terminal or app. The applets on the gnome-panel also didn't fully finish loading until after a few minutes

ProblemType: Bug
Architecture: i386
Date: Sat Apr 28 20:26:44 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 1:2.18.1-0ubuntu3.1
PackageArchitecture: i386
ProcCmdline: gnome-panel --sm-client-id default1
ProcCwd: /home/azolkipl
ProcEnviron:
 LANGUAGE=en_MY:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-panel
Uname: Linux JudJud 2.6.20-15-386 #2 Sun Apr 15 07:34:00 UTC 2007 i686 GNU/Linux

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

The slow login/desktop bug appears to have been around for a while. The bug is reported in edgy & feisty and they are mostly unconfirmed and mostly of undecided importance. Although I'm very happy with feisty, I am finding this bug a bit bothersome so I thought I'd do some research through the bug archives.

I think this bug has been reported numerous times. The bug list that follows, I think are reports of effectively the same bug.

Bug #78263 - claims workaround (feisty)
Bug #78493 (edgy)
Bug #79466 (edgy)
Bug #80827 - claims workaround (edgy)
Bug #92997 - claims workaround (feisty)
Bug #94048 (feisty)
Bug #110616 (feisty?)
Bug #110775 (feisty)
Bug #110187 - reports slow desktop as a side effect of other network config issues. (feisty)
---------------
Bug #95264 - Maybe related (not clear) (feisty)
Bug #93447 - Maybe related (not clear) (edgy)
---------------
It seems most discussions are blaming this bug on one or more of:
Network-manager
avahi
hosts file
resolve file
static IP addresses
no network connection.

I can't vouch for the claimed workarounds - but I intend on investigating them further.

The person who solves this one will likely 'kill a number of bugs with one stone'.

I hope I'm not being too forward by presenting such a list but I am rather keen to see this bug solved. I hope this list helps to unify further discussion & prompts some further thought on the matter.

(note: I have posted it to all above bug reports so that all are in the loop)

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

Add Bug #79661 (edgy) to above list.

[Nanley Chery (nanoman)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

[Ali Sabil (asabil)]

yes this is reproductible, but unfortuantely no one seems to know where the problem comes from, personally I suspect some gnome library to be doing a dns request or so ...

[trollord (trollenlord)]

Both your short dns name and fqdn must resolve correctly and be connectable via network. Gnome has for years slowed to crawl if they haven't. It is not a bug, it is a reasonable assumption that every host has a properly working name. If you have a special networking needs, add the hostname(s) to your /etc/hosts to point to 127.0.0.1 .

Most likely you have enabled some non-default networking configuration (enabling firewalls, have bad working dns servers around, vpn's or such).

[Ali Sabil (asabil)]

This bug is *not* invalid, my /etc/hosts seems to be fine, and the problem still occurs:

127.0.0.1 localhost asabil-laptop

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

[Trifon Trifonov (triffon)]

For me this was resolved with the fixing of #78263, which was actually #256480.
Can anyone really reproduce this in intrepid?