[Gutsy] GNOME takes too much time to load during system boot

Thanks for your report, does that happens with another new user? Which video card do you have? Are you using Visual Effects? Does it happen without it?

Hi, Pedro. Yes, it happens with a newly created user. I have an nVidia GeForce 7300 LE video card. I'm not using any visual effect, but the problem happens with & without it.

Hope this helps.

This is also happens here, using nvidia-glx-new, compiz fusion and emerald

i have a Nvidia Go 7600

I confirm it too!

I'm running the official release of ubuntu gutsy 7.10 i386 and my boot time is VERY long...

I installed the OS twice and in a fresh install, even after several reboots, my boot time between the grub menu and the login screen lasts 56sec. (!!!)

My specs:
- ACER 5051 -
AMD Turion 64 2000+
1.5 Gb RAM (-128Mb video card)
ATI X1100
bcm4318

This is a fairly recent computer!

I hope you guys can check what's happening here... Please request if you want me to run some commands or something!

Thanks!

I am attaching my bootchart...

Do you see anything wrong?

I have this problem. However Vitor I think you have made a mistake. The issue you raise and the one in this ticket are different.

I have a Dell Latitude D620 with 512 RAM and an Intel Core 2 Duo Processor. I have an integrated Intel Graphics card. I have Compiz with Emerald enabled as well as screenlets and the AWN dock (these start at startup). After I've entered my password it takes so much longer to get to a working desktop than it did in Feisty. If you need more information then please let me know.

I have the same problem, it took almost 3 minutes today from login to complete display of the desktop. I've never had this issue in previous versions. I have a Toshiba Satellite 2450-S201 with 512 RAM, no Compiz/Beryl or any other eyecandy due to issues with drivers for the Nvidia GeForce4 420Go graphics card.

I have the same problem.

From grub to login page : very fast. But from login to desktop, I need about one minute, with the hard drive always working.

I have a fresh install of Gutsy. I don't use compiz. I have a nvidia 7900Go GS with nvidia drivers, 2Go ram. It has never done that with previous Ubuntu releases neither other distros.

Hi I also have this problem.

I'm using Gutsy for AMD64 with compiz. I imported my /home directory from an installation of Feisty x86 so i'll try with a new user tonight, but I red that the problem happens even with a new user.

For me the problem seems sporadic. Often (not always) just after a restart Gnome load pretty fast, but usually it takes a couples of minutes to load.

I have a Athlon 64 with 1.25go of RAM and a nvidia carg (with the nvidia-glx-new drivers).

If any other informations are required, just ask.

From login screen to desktop also takes a very long time for me. I'm using Gutsy on a fresh install. Nvidia FX5200. This happens with or without Compiz active. Feisty was fast but there is a real slowdown on Gutsy.

Confirmed:

One thing i noticed too, is if you do nosmp in the boot line, the gnome-panel will load, then disappear, only to reappear after a lifetime of waiting.

AMD64, nVidia Go 7600GT

here's part of my dmesg:

[ 43.920271] ACPI: AC Adapter [ACAD] (on-line)
[ 44.112234] powernow-k8: Found 1 AMD Turion(tm) 64 X2 Mobile Technology TL-60 processors (version 2.00.00)
[ 44.112270] powernow-k8: 0 : fid 0xc (2000 MHz), vid 0x12
[ 44.112273] powernow-k8: 1 : fid 0xa (1800 MHz), vid 0x14
[ 44.112276] powernow-k8: 2 : fid 0x8 (1600 MHz), vid 0x16
[ 44.112278] powernow-k8: 3 : fid 0x0 (800 MHz), vid 0x1e
[ 47.590236] NET: Registered protocol family 10
[ 47.590318] lo: Disabled Privacy Extensions
[ 47.590484] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 47.590498] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 48.406898] lp: driver loaded but no devices found
[ 48.437377] ppdev: user-space parallel port driver
[ 48.634720] audit(1193246854.105:3): type=1503 operation="inode_permission" requested_mask="a" denied_mask="a" name="/dev/tty" pid=5227 profile="/usr/sbin/cupsd"
[ 54.857942] Failure registering capabilities with primary security module.
[ 55.118531] Bluetooth: L2CAP ver 2.8
[ 55.118535] Bluetooth: L2CAP socket layer initialized
[ 55.146530] Bluetooth: RFCOMM socket layer initialized
[ 55.146645] Bluetooth: RFCOMM TTY layer initialized
[ 55.146648] Bluetooth: RFCOMM ver 1.8
[ 74.595043] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 85.817824] wlan0: no IPv6 routers present

I have the same problem on Dell Inspiron 9400 with an Nvidia 7900GS using Gutsy with Compiz Fusion.
It takes unusual long to load the desktop after the first login when fresh booted. Disabling startup programs doesn't help, also turning on the Compiz Fusion starting splash-screen to see when Compiz loads leads me to believe, that the delay happens before the actual loading of the desktop.

Same problem here.

Updated from Feisty to Gutsy.

Some people suggested to clean install, but others had the problem even after that.

Using AMD64.

Just throwing a suggestion out there. If i rememebr right, in tribe 4, there was a bug that was milestoned too late to make the final release, that had to do with an audit of the cupsd daemon. It wouldnt allow printing because of a conflict with apparmor. Looking at this line from dmesg

[ 48.634720] audit(1193246854.105:3): type=1503 operation="inode_permission" requested_mask="a" denied_mask="a" name="/dev/tty" pid=5227 profile="/usr/sbin/cupsd"
[ 54.857942] Failure registering capabilities with primary security module.

It seems to be doing the same. It's something so far, that i noticed everyone had in common who posted their dmesg on the forums

Not everyone had the audit line. But, everyone experiencing the problem, from the collected data had the failure registering capabilities with primary security module.

I installed Gutsy, fresh clean install, on my two HP laptop computers, both AMD64. I then installed it on my desktop, clean, with the i386 kernel. The desktop boots fine, the two laptops dont. The laptops have a message in their dmesg:
[code][ 53.940709] Failure registering capabilities with primary security module.[/code]

The desktop does not reference anything of that nature. After gathering this information, i don't know what my next step should be. Kind of hit a road block.

I am running AMD 64 with 32 bit Gutsy upgraded from Feisty. I also take about 45 seconds to go from login to desktop. I have 2 gig ram and Nvidia 7800 GT running nvidia-glx-new drivers. Here is the out put of 2 dmesg greps:
marty@tux:~$ dmesg | grep audit
[ 38.451889] audit: initializing netlink socket (disabled)
[ 38.451902] audit(1193268681.132:1): initialized
marty@tux:~$ dmesg | grep error
[ 37.605494] ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not found.
[ 68.340902] VIA 82xx Modem: probe of 0000:00:11.6 failed with error -13
[ 78.468779] powernow-k8: BIOS error - no PSB or ACPI _PSS objects

dmesg | grep failure returned no output, so the primary security module does not seem to be an issue for me.
In fact, here is the output of dmesg searches for primary security and module:
marty@tux:~$ dmesg | grep failure
marty@tux:~$ dmesg | grep primary
marty@tux:~$ dmesg | grep security
marty@tux:~$ dmesg | grep module
[ 66.544455] nvidia: module license 'NVIDIA' taints kernel.

I know it's off topic, but I wonder if the <<powernow-k8: BIOS error - no PSB or ACPI _PSS objects>> message is a clue as to why I can't do S3 sleep on this machine.

Same problem here, upgraded from Feity to Gusty and now after I login it takes longer for the desktop and icons to show up

Same problem here, loading takes about 30-40 secsm; deskbar applet and tracker are turned off.
Clean install Ubuntu 7.10, using compiz with nv 8600gt card, P4 3Ghz cpu 1 Gb RAM.

I have the same problem as well on my laptop, Asus S5n, P-M 1.5Ghz, 768 MB Ram, Intel integrated graphics.

Same problem on 2 computers
slow gdm logon. After upgrade to gutsy gibbon

one hp laptop hpnx9420
dual core 2,2 ghz processr
2gb ram
ati x1600

Desktop:
p4 2.8Gh
512mb ram
ati radeon 9000

Both systems were running fast.
But after the upgrade...
same proble as most of you here.

Same problem here. Inspirom 1420n, upgraded to Gutsy. Initial logon takes a good 45 seconds, but all logoffs and logons after that come up very quickly. I have the Integrated video Intel GM965 and am NOT using compiz at all.

Could some of you post their session file ?

Thanks

For the record here are some forum threads where many users are reporting the issue, unfortunately they don't use launchpad :
http://ubuntuforums.org/showthread.php?t=585635
http://ubuntuforums.org/showthread.php?t=568995

This is the last posti made in the forums.

Ok. In Failsafe Gnome, it still took some time, but it basically seemed to come right up.

Altering the session script made no change.

Changing the session from xclient to gnome made no change.

Disabling compiz made no change. Although, i still think compiz is part of the problem.

Keyring manager, doesn't ask me for a password, whcih is nice, but it's odd behavior for keyring manager.

There is no gnome-splash screen, even after install, gnome-splash-manager.

I cannot log out, and log back in, or restart x. On re-log in, it will just sit on the desktop, with nothing. Only thing to do is to restart gracefully, since i can access vty's.

My session file
---- BEGIN FILE -----

[Default]
0,id=117f000101000119375950400000059790000
0,RestartStyleHint=1
0,Priority=40
0,Program=gnome-volume-manager
0,CurrentDirectory=/home/mike
0,CloneCommand=gnome-volume-manager --sm-config-prefix /gnome-volume-manager-vuFDxi/
0,RestartCommand=gnome-volume-manager --sm-config-prefix /gnome-volume-manager-vuFDxi/ --sm-client-id 117f000101000119375950400000059790000 --screen 0
1,id=117f000101000119375951100000059790004
1,RestartStyleHint=2
1,Priority=5
1,Program=vino-session
1,CurrentDirectory=/home/mike
1,CloneCommand=vino-session --sm-config-prefix /vino-session-cUvnig/
1,RestartCommand=vino-session --sm-config-prefix /vino-session-cUvnig/ --sm-client-id 117f000101000119375951100000059790004 --screen 0
#2,id=117f000101000119375951200000059790005
#2,RestartStyleHint=1
#2,Program=update-notifier
#2,CurrentDirectory=/home/mike
#2,CloneCommand=update-notifier --sm-config-prefix /update-notifier-4RG3wg/
#2,RestartCommand=update-notifier --sm-config-prefix /update-notifier-4RG3wg/ --sm-client-id 117f000101000119375951200000059790005 --screen 0
#3,id=117f000101000119375951200000059790006
#3,Program=gnome-power-manager
#3,CurrentDirectory=/home/mike
#3,CloneCommand=gnome-power-manager --sm-config-prefix /gnome-power-manager-u2Ikvg/
#3,RestartCommand=gnome-power-manager --sm-config-prefix /gnome-power-manager-u2Ikvg/ --sm-client-id 117f000101000119375951200000059790006 --screen 0
4,id=117f000101000119375950400000059790002
4,RestartStyleHint=2a
4,Priority=40
4,Program=nautilus
4,CurrentDirectory=/home/mike
4,CloneCommand=nautilus --sm-config-prefix /nautilus-yiyu9u/
4,RestartCommand=nautilus --sm-config-prefix /nautilus-yiyu9u/ --sm-client-id 117f000101000119375950400000059790002 --screen 0 --load-session /home/mike/.nautilus/saved-session-WW2T0T
#5,id=117f000101000119375983500000059790008
#5,Program=rhythmbox
#5,CurrentDirectory=/home/mike
#5,CloneCommand=rhythmbox --sm-config-prefix /rhythmbox-NetXLg/
#5,RestartCommand=rhythmbox --sm-config-prefix /rhythmbox-NetXLg/ --sm-client-id 117f000101000119375983500000059790008 --screen 0
6,id=117f000101000119375950800000059790003
6,RestartStyleHint=0
6,Priority=10
6,CloneCommand=compiz
6,RestartCommand=compiz --sm-client-id 117f000101000119375950800000059790003
##7,id=117f000101000119376207500000059790009
#7,Program=term
#7,CurrentDirectory=/home/mike
#7,CloneCommand=term --sm-config-prefix /term-bCu3Ig/
#7,RestartCommand=gnome-terminal --sm-config-prefix /term-bCu3Ig...

I believe I am having the same problem. Boot to GDM is great, maybe even faster than Feisty. But from login to usable desktop is at least twice as slow as Feisty, even without the splash screen (which I guess was removed to help desktop load times?). It's not a minute or more like some people are reporting, but it's definitely a regression from feisty.

I'm running a clean install of Gutsy on a dual core intel machine, 1GB RAM, integrated intel video. Desktop effects enabled.

Same problem, hp dv2412ca with AMD-64.

Long time to login, no splash screen, I can see the panel appear in plain gtk (grey, not themed) and then I see the theme being applied. Overall, gnome feels slow, dialogs takes time to appear, apps freeze for a few seconds from time to time. I also noticed heavy hard-drive activity at login.

In breef, the experience is really poor.

I installed from i386 image instead of amd64, gnome loads much faster now. I get a usable desktop after 20 seconds and there is far less HD activity on login as well.

This problem was always reported on amd systems in the forum, so I guess that the problem is related to the 64 bits system.

DrCurl -> I installed an i386 image on another computer, and noticed the same (That it was running smoother, faster, load times decreased), only after some updates, did i notice the reported behavior. Currently investigating.

Reistlehr -> there was indeed an update today. If you compare 64 and i386, please report the results, I would be glade to go back on 64 bits. For now, i386 is blazing fast.

Same problem here, HP Compaq NX7400 laptop. At least 30 secs between login and usable desktop. This is new, in Feisty this prob didn't exist. Interestingly, I don't use 64 bit, since the CPU isn't capable of this. So I guess the cause of the prob is something different.
Looking at dmesg, it seems to have something to do with the network interface:

.....
[ 24.200000] apm: BIOS not found.
[ 24.756000] Failure registering capabilities with primary security module.
[ 25.892000] [drm] Initialized drm 1.1.0 20060810
[ 25.896000] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16
[ 25.896000] [drm] Initialized i915 1.6.0 20060119 on minor 0
[ 27.120000] NET: Registered protocol family 10
[ 27.120000] lo: Disabled Privacy Extensions
[ 27.120000] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 27.120000] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 74.624000] NET: Registered protocol family 17
[ 74.640000] usb 2-2: new low speed USB device using uhci_hcd and address 2
[ 74.812000] usb 2-2: configuration #1 chosen from 1 choice
[ 75.044000] input: Logitech USB RECEIVER as /class/input/input7
[ 75.044000] lmpcm_usb.c: Detected device: Logitech USB RECEIVER
[ 75.044000] usbcore: registered new interface driver lmpcm_usb
[ 75.044000] /build/buildd/linux-ubuntu-modules-2.6.22-2.6.22/debian/build/build-generic/misc/lmpcm_usb.c: v0.5.5:USB Logitech MediaPlay Cordless Mouse driver
[ 75.632000] usbcore: registered new interface driver hiddev
[ 75.636000] usbcore: registered new interface driver usbhid
[ 75.636000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[ 78.220000] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 95.476000] eth1: no IPv6 routers present
.....

Although I do have a 64 bit CPU I'm NOT using the 64 bit version of Ubuntu and I still get this problem. It worked fine with Fiesty but after upgrading to Gutsy it is slow.

Problem reproducible on my laptop as well.
Around a couple of minutes between login and usable state.
Problem disappears if I booted with a network connection.

Laptop configuration is : Compaq V2375TU, 1.4 Ghz Intel Celeron, 2 GB DDR 333, Intel 915 GM chipset.

I dont seem to face this problem in Feisty. In Gutsy, the issue doesnt appear immediately after installation. A few logins later (probably after a patch installation as well), this problem raises its head.

My Acer Aspire 3638 laptop computer is booting up very slow as well. It was way faster with Feisty Fawn.

I got Compiz Fusion up and working, but if I turn it off, the booting is still very slow.

Same problem here on a Lenovo T61 Core2Duo, Nvidia NVS 140m (512MB) and 1 GB DDR2.
As the others, boot time from login to desktop was much faster on my Feisty.

This problem does not occurs on my old Athlon 1800+ with nvidia GeForce 6800 GS with 1 GB DDR.

I also face the same problem. As of now, I have found no stable solution.

The boot from grub menu to the login screen is fast. But GDM takes too long to load.

I notice the following:

1. GDM loads only nautilus of late. It used to load several other components as well. Is something broken? How do I know and what file do I attach as a report for this?
2. gnome-panel does not start at all. It is frustrating that it does not start at all. I wonder if you people face this or not. Let me explain. I am currently using Compiz-Fusion and full effect. But that does not seem to matter at all. This problem has been there ever since.
3. I had run into another problem prior to this: device-mapper: table: 254:1: linear: dm-linear: Device lookup failed which keeps getting spammed on my tty screen and prevents gnome from loading properly. I noticed this by pressing Ctrl+Alt+F1. So I uninstalled evms as has been suggested in other bugs: eg: Bug# 115616 in linux-source-2.6.22 However, this problem does not seem to have gone at all.
4. I have tried this several times now and am actually scared to shut down my laptop since I am completely uncertain if it will reload. In fact, Pidgin loads automatically since I have it on the session start-up programs list. This time around I was saved because for some reason Gutsy was kind enough to give me a terminal at start-up by default. I loaded Firefox through that. I am a normal user and so don't know the command name to start the gnome panel. I searched on the net and found that it is 'gnome-panel'. Note that I am also a contributor to the CPAN pages and also contribute some software to the community. I still don't know all Linux commands. I completely disagree that a hacker must be knowing everything about this and this problem is simply bugging. I as even a hacker (I hacked several problems for my mom and dad at home on Dapper) think that sometimes the hacker community acts way too arrogantly in dealing with problems. Instead of helping people by using their expertise they expect people to do some debugging, but how will they do it if they don't know where to look for error messages at all!!? In this particular case for example, NO ERROR MESSAGE IS FLAGGED BY ANY PROGRAM except security modules. I ONLY FIND SOME ERRORS IN THE .xsession-errors BUT THAT IS A KNOWN BUG IN GTK+ and some messages in dmesg. There is nothing apparent at all that I can figure that is directly liked with GNOME-panel, but for some reason gnome is broken. This is an emergency problem and not something that needs 1000 confirmations before some hacker begins solving it. That way we will never have a solution.
5. I have not installed anything new. If Ubuntu installed something in the process of having installed Gutsy Gibbon I am not responsible and that is the sole responsibility of the developers. I myself am a developer of some Electrical Engineering CAD tools, but NEVER EVER release a new version without having had complete confidence on it. This is totally irresponsible of Canonical to have released a version of Ubuntu without any proper solution to these problems with GNOME.
6. I recreated the initramfs linux image for my platform. The out...

A "me too" comment.

Acer Aspire 5021WLMi, was running Ubuntu Fiesty and upgraded to Gutsy. Since upgrade gdm login takes a long time.

I also have another issue, that I do not know if others have. Logging into GDM works once. It takes quite a while. If I log out and try to login a second time, the panels and applets never appear. Login hangs and I need to reboot. Restarting gdm from a tty does not help.

I confirm it too!

I'm running Ubuntu gutsy 7.10 i386 and my boot time after GDM is VERY long... The boot from grub menu to the login screen is faster as Feisty.

I installed the OS twice and in a fresh install, even after several reboots, my boot time after the GDM : 30 sec

My specs:
AMD ATLON XP 2000+
1 Gb RAM
NVidia AGP GEFORCE 6200 128 Mo

Thanks!

I confirm this too.

In my case, restarting after one successful boot will surely hang. The
gnome-panel does not come up, some services take too long and it is simply
unknown as to how we can debug this problem at all since even after
Ctrl+Alt+F1 I only get a blank screen and no login prompt or shell at all.

This problem is very critical and the severity level of this problem needs
to be raised to "Very high" immediately. I have been using Ubuntu since the
Dapper days. I don't have Windows on my machine at all. With this bug in, I
want to go back to using Microsoft Windows and pay for the licenses. I don't
want unreliability. An upgrade should make things better, not worse.

-Balaji

On Nov 12, 2007 2:27 PM, Andrew Henry <email address hidden> wrote:

> A "me too" comment.
>
> Acer Aspire 5021WLMi, was running Ubuntu Fiesty and upgraded to Gutsy.
> Since upgrade gdm login takes a long time.
>
> I also have another issue, that I do not know if others have. Logging
> into GDM works once. It takes quite a while. If I log out and try to
> login a second time, the panels and applets never appear. Login hangs
> and I need to reboot. Restarting gdm from a tty does not help.
>
> --
> [Gutsy] GNOME takes too much time to load during system boot
> https://bugs.launchpad.net/bugs/151544
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Balaji

Now I upgraded my HP Pavilion dv9297ea (Core2Duo 7200, 2GB RAM, nVidia Go 7600) from Feisty amd64 to Gutsy amd64 and I get the same problem as I had with my Acer Aspire... a much longer login time than with Feisty. From login box to working desktop takes much longer than with Feisty.

Any Ubuntu developer here?

when i had the same prob this morning i moved my homedrive and freshed it up with a brand new directory
so i had a clean config ...

now when i restarted 'gdm' i got the message that my $home was created and then after i logged in it took me again a while ...

now when i went back to tty1 to look at my 'top' i noticed that 'gnome-panel' was using 97% CPU ... i don't think that's kinda normal ?

hardware specs for this computer :
AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
5gb ram
nvidia 7xxx (pci-x)

I confirm this bug too.

But, maybe i found something, well i dont know what exactly i do, but here.

I reinstalled nvidia-glx-new, and ccsm. In CCSM / preferences / i made new profile, he reset all to default values, i think this default values are different from ubuntu default values, login is now faster and less messy. And in CCSM i configure settings how i want in my new profile.
Or I also tryed there to change backend from "gconf configuration backend" to "flat file configuration backend" - same result, or on general options, general tab click on every "reset setting to default value", or in display settings - outputs - put your resolution, so people try and let me know.

Maybe compiz and ccsm, had conflicts with "gnome compiz manager" which i have installed at the same time, and then removed. Dont know what exactly i do, but now is better...

I am having having exactly the same problem. The boot is swift. However, I experience delay getting to the login screen. Sometimes it is logging in (i.e. getting to a Desktop) and sometimes I am able to get a desktop in about 2-3 mins, but then my desktop freezes. All of this happens in random order.

I am running a Sony VAIO PCG-K115Z (Intel Mobile Pentium 4, 1 Gig RAM, Mobility Radeon 9200).

I must also add that I was able to run the previous version of Ubuntu (v7.04 flawlessly). I have since upgraded, formatted and re-installed Gutsy.

Hey,

Having the same problem. Boot speed is the same as with edgy or feisty, but the time from login to usable desktop is far longer than what it was with previous versions.

I am running:

HP dv1000 laptop
integrated intel graphics card
Intel Pentium M 1.7GHz
1G ram

I was having the same problem UNTIL I disabled ipv6 (I don't use IPV6). Now it boots fast...

Disable IPV6:

gksudo gedit /etc/modprobe.d/aliases

from:

    alias net-pf-10 ipv6

to

    alias net-pf-10 off

There is a tweak for firefox that disables ipv6 also...

I hope this helps!

I've tried ensuring that /etc/usplash.conf resolution matches the scree resolution in System Preferences and I tried the ipv6 fix above. They made no difference. Looking at the attached bootchart log, it seems to me that SO1readahead & readahead take approx 0 seconds while nothing else happening except usplash. Anybody any ideas?

Well, as previously stated, there are multiple problems that can be causing this issue.

From what i have figured out, some systems experience a session problem after installing the nvidia drivers (official/glx-new)

Some others are having a problem with compiz itself

Other are experiencing network issues.

Since there could be more, but atleast there are 3 confirmed causes for this issue, i don't think the one bug report can solve all 3.

Well, there were no official answer to this problem and it's been a few weeks.

I'm going back to slack, which is way faster/more responsive on my system. It is a pain to see uge performance decrease after an upgrade...

why is this Low Importance?!

Hello,
I used to have this problem as well but I have recently 'fixed' it. I got so fed up of long load times I actually used fvwm-crystal instead of gnome for a while.

Anyways to fix it I disabled many start up services that start along gnome. To do this go to System->Preferences->Sessions from the top panel in gnome. This allows you to decide which service starts up. I deleted the standard ones so I do not know which ones I disabled but I remember disabling the bluetooth and I believe that it is the bluetooth that is causing the problem since everyone complaining from this seems to be a laptop user. Anyways services which I kept are attached as a screenshot. Let me know if this helps.

Manu

I always disable bluetooth, in sessions and deamons windows. But it's slow as well...

Originally i believed that blue tooth was part of the problem, so i completely removed it. Removed the modules, removed the daemons, removed from sessions, removed all references. The problem still exists.

 I switched back to Gentoo for now. The Dev's haven't even taken a stab at this.

I think this may have been fixed now! I just downloaded some updates
today but it was a while since I last updated..maybe 2-3 weeks, and now
on my server (Acer Aspire) login is just as fast as Fiesty.

All this stuff about ipv6, bluetooth and Compiz seem like red herrings.

hi,
I am having the same problem,
I updated from feisty to gusty and had a 30 sec load time from login to desktop. I disabled bluetooth and that did nothing. I also was using compiz.
I then did a clean install and have the same problem. still using compiz.
am running:
i386
ge force 400mx card
Intel Pent m. 2.4 ghz
768 ram

****Possible FIX.**** (It fixed it on my pc)
I had the same exact problem. To see more details please look at this thread: http://ubuntuforums.org/showthread.php?t=611711

Then I installed xamp for Linux (following the instructions on the page below):
http://www.apachefriends.org/en/xampp-linux.html
When I started xamp with the command "/opt/lampp/lampp start" I received an error saying that I had some problems in my "/etc/host" and a message saying that it was trying to fix the problem.
After that all my system was responsive as it should be, and the long time to boot was considerately shortened.

I don't know how this was fixed. I leave it to the uBuntu coders to figure it out. But is has something to do with etc/host ans xamp was able to fix it.

Thanks for the attention.

Regards,

vampire666

Could you post your actual /etc/host so we can take a look at what changed?

On Nov 26, 2007 4:49 PM, vampire666eng <email address hidden> wrote:
> ****Possible FIX.**** (It fixed it on my pc)
> I had the same exact problem. To see more details please look at this thread: http://ubuntuforums.org/showthread.php?t=611711
>
> Then I installed xamp for Linux (following the instructions on the page below):
> http://www.apachefriends.org/en/xampp-linux.html
> When I started xamp with the command "/opt/lampp/lampp start" I received an error saying that I had some problems in my "/etc/host" and a message saying that it was trying to fix the problem.
> After that all my system was responsive as it should be, and the long time to boot was considerately shortened.
>
> I don't know how this was fixed. I leave it to the uBuntu coders to
> figure it out. But is has something to do with etc/host ans xamp was
> able to fix it.
>
> Thanks for the attention.
>
> Regards,
>
> vampire666
>
>
> --
> [Gutsy] GNOME takes too much time to load during system boot
> https://bugs.launchpad.net/bugs/151544
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Sure thing:
Below is the content of "/etc/hosts" ---> but I don't know what it was before so I don't know what it changed.

127.0.0.1 localhost
127.0.1.1 VAMPIRE666-ubuntu.CASA

# 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
127.0.0.1 VAMPIRE666-ubuntu # added by Apache Friends XAMPP

I'm not sure what was the error. If it was etc/host or etc/hosts (I didn't pay enough attention to it. If I would have known that it was about to solve my problem, I would have taken the error more seriously).
Anyway, this is the content of "/etc/host.conf"

# The "order" line is only used by old versions of the C library.
order hosts,bind
multi on

Hope this helps to solve the problem.

Same issue.. after installing got the same as at the report was mention.

The GNOME desktop takes very long time to load during the system boot, i.e. the first time. Log out and login again is faster than light, though. Feisty is significantly faster at startup time.

My Gutsy desktop takes ~34 secs to fully load GNOME. The Feisty machines in my classroom (I'm a computer science teacher) takes ~12 secs to fully load GNOME, and these machines are significantly slower than my home desktop computer. Other Gutsy machines in the High School takes 25-30 secs.

IMHO, this is a very annoying bug, and, after a brief investigation, I think the problem only appears in machines with NVIDIA graphics cards.

Maybe a compiz - nvidia interaction?

I guess it's not that as the problem effects also users that have Ati cards, and removing completely compiz doesn't solve the problem (as said by users in the uBuntu forums).

I also have ATI.

In the ubuntu forums the conclusion was that there were several
problems causing the same symptom (slow log in). One was the hosts
file that vampire666 mentioned. It was fixed by adding you machine
name to the localhost.

Another problem was compiz beeing used as the window manager. Some
people reported that replacing compiz with metacity (feisty Window
Manager) the problem was solved... I guess I'll try that

On Nov 28, 2007 5:10 PM, vampire666eng <email address hidden> wrote:
> I guess it's not that as the problem effects also users that have Ati
> cards, and removing completely compiz doesn't solve the problem (as said
> by users in the uBuntu forums).
>
>
> --
> [Gutsy] GNOME takes too much time to load during system boot
> https://bugs.launchpad.net/bugs/151544
> You received this bug notification because you are a direct subscriber
> of the bug.
>

That is not true. This is not a problem with nvidia.

I think let us stop beating around the bush and concentrate on the problem.
It was never a problem in Feisty. What has changed since October end is
Ubuntu. I have had the same laptop since October 2006 and have been running
Dapper, Edgy and Feisty with no issues whatsoever. It is only Gutsy that is
the problem.

So for goddamned sure. IT IS A PROBLEM WITH ONLY AND ONLY UBUNTU AND NO
OTHER DEVICE OR OBJECT AROUND. It is really disappointing to see two
phenomena here:

1. Ubuntu support is not taking enough action on this bug. This should be a
priority. It is a shame to the Ubuntu makers that they can't give an
important bug its rightful place.
2. They are simply beating around the bush to try to transfer the blame to
someone else. It is the kernel that is the culprit. The 386 kernel is very
very slow and I find that the generic kernel is not very much improved
either. The older kernel 2.6.17 or 2.6.20 were way better. Even now, if you
try using those kernels, GNOME loads fast.

Clearly it is a problem with the kernel. It is the haughtiness of the kernel
writers that they fail to recognized the problem and fix it. When Ubuntu has
almost no market share as against Microsoft, these guys act so pricey and
all as if they know everything about the problem and keep throwing the blame
from one to another. I have no doubt that they can NEVER EVER stand
Microsoft's competition, if things go down the path of ruin in this manner.

There is NOTHING (I wish I could write in bigger letters to make it clear)
significantly useful added in Gutsy at all. Why did they make this release?
Most people have gone back to Feisty. I don't want Compiz or any other
BULLSHIT - what I want is a fast useful machine.

Balaji

On Nov 29, 2007 12:29 AM, Ricardo Pérez López <email address hidden> wrote:

> My Gutsy desktop takes ~34 secs to fully load GNOME. The Feisty machines
> in my classroom (I'm a computer science teacher) takes ~12 secs to fully
> load GNOME, and these machines are significantly slower than my home
> desktop computer. Other Gutsy machines in the High School takes 25-30
> secs.
>
> IMHO, this is a very annoying bug, and, after a brief investigation, I
> think the problem only appears in machines with NVIDIA graphics cards.
>
> Maybe a compiz - nvidia interaction?
>
> --
> [Gutsy] GNOME takes too much time to load during system boot
> https://bugs.launchpad.net/bugs/151544
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Balaji

Balaji wrote:
> 1. Ubuntu support is not taking enough action on this bug. This should be a
> priority. It is a shame to the Ubuntu makers that they can't give an
> important bug its rightful place.
>
I agree that Canonical "attendance" on Launchpad seems quite poor, going
from the bugs i have followed. I do not even think there has been a
Canonical response to this bug yet! I said this earlier, but here it is
again: This issue was totally fixed for me on two seperate laptops
running amd64 Gutsy one day last week when a few updates came through
Update Manager, and I use full Compiz, AWN and have nVidia Go 7600 on
one of the laptops.. So if people have updated and still get this issue
then it must have different reasons, but obviously someone is trying to
fix it despite lack of communication on launchpad. By the way,
disabling ipv6 didn't do squat for me. I think it was the updates that
upgraded Gnome to 2.20.1 that did it.
> 2. They are simply beating around the bush to try to transfer the blame to
> someone else. It is the kernel that is the culprit. The 386 kernel is very
> very slow and I find that the generic kernel is not very much improved
> either. The older kernel 2.6.17 or 2.6.20 were way better. Even now, if you
> try using those kernels, GNOME loads fast.
>
> Clearly it is a problem with the kernel.

How do you come to this conclusion? My first thought would be GDM but
no, I am not sure either. To jump to the conclusion that it is the
kernel is a bit of a long shot though.
> It is the haughtiness of the kernel
> writers that they fail to recognized the problem and fix it. When Ubuntu has
> almost no market share as against Microsoft, these guys act so pricey and
> all as if they know everything about the problem and keep throwing the blame
> from one to another. I have no doubt that they can NEVER EVER stand
> Microsoft's competition, if things go down the path of ruin in this manner.
>
> There is NOTHING (I wish I could write in bigger letters to make it clear)
> significantly useful added in Gutsy at all. Why did they make this release?
> Most people have gone back to Feisty. I don't want Compiz or any other
> BULLSHIT - what I want is a fast useful machine.
>
>
They make new releases simply because Debians unstable repos have been
significantly updated ;) I think they relied too much on this fact with
Gutsy and I don't really see anything that Canonical have *added* to
Gutsy besides the stuff that came through from Debian. But then again,
there is so much to monitor and I only look at what interests me, which
i suspect most people do. But don't be fooled by the blandness of the
desktop! Yes, it may look like Fiesty but don't forget that all
packages are newer versions. To think that the desktop should look
significantly different between releases is a side effect of having used
Windows too long! Linux is a progressive development and many of the
tools I use have fixed issues I had in previous releases or added new
functions that I now use.
> Balaji
>

--
GnuPG Key ID: ECB18ABA
Fingerprint: FDF3 91FC F5BC 1164 E217 315E 337E 219B ECB1 8ABA

>In the ubuntu forums the conclusion was that there were several
>problems causing the same symptom (slow log in). One was the hosts
>file that vampire666 mentioned. It was fixed by adding you machine
>name to the localhost.

I've that in my machine, without luck.

>Another problem was compiz beeing used as the window manager. Some
>people reported that replacing compiz with metacity (feisty Window
>Manager) the problem was solved... I guess I'll try that

System->Preferences->Appearance->Desktop Effects->None changes compiz to metacity... without luck, too.

I've even replace "nvidia" to "nv" in the xorg.conf... without luck, too.

It's hopeless.

I do agree in one thing, is an anoying bug. It even feels like wndows
loading with a mcfee antivirus ;-)

I do not agree is an envidia problem. I use an internal onboard video
card no nvidia things.
For one moment i was thinking it was a network problem, but my network
is working correctly hosts files is correct network files also. Others X
env are working properly.. im even thinking to switch to kbuntu but kde
can be also really buggy.. so i will wait..

Ricardo Pérez López wrote:
> My Gutsy desktop takes ~34 secs to fully load GNOME. The Feisty machines
> in my classroom (I'm a computer science teacher) takes ~12 secs to fully
> load GNOME, and these machines are significantly slower than my home
> desktop computer. Other Gutsy machines in the High School takes 25-30
> secs.
>
> IMHO, this is a very annoying bug, and, after a brief investigation, I
> think the problem only appears in machines with NVIDIA graphics cards.
>
> Maybe a compiz - nvidia interaction?
>
>

Andrew>
To think that the desktop should look
significantly different between releases is a side effect of having used
Windows too long! Linux is a progressive development and many of the
tools I use have fixed issues I had in previous releases or added new
functions that I now use.

Balaji>
I'm not expecting a significant change in the desktop. In fact between
Feisty and Gutsy there IS a change in the desktop - Compiz. But I don't care
about it. What I'm looking for is:
1. Better driver support for different printer, scanner models etc.
2. Better support of Wireless. My wireless connection setup is still a very
complex procedure.
3. Bettter VPN support
4. POWER MANAGEMENT - This was promised to have improved in Gutsy. I see NO
improvement at all.
5. Better Bluetooth support - I still can't send stuff to my laptop from my
mobile. I don't know when I will send SMSes from my laptop.

I know each one of them have a different software now, like vpnc or
kbluetoothd etc. The thing is I want to use the GNOME version of these and
reduce the disk space involved in installing multiple software. GNOME
promised better work on this.

Power management is a matter of the kernel. In the Gutsy release notes they
said that the use of the new kernel improves power management. BULLSHIT.

Driver support is dependent on their relationship with the community of
programmers writing drivers like SANE or ALSA etc. I don't think they have
good contacts anymore. Almost everything is broken once you migrate from
Feisty. In migrating from one version of OS to the next, I don't want to
keep redoing all the setup activities to work on every software and driver.

Even restricted drivers was a problem. They don't have a generic kernel
based driver from my laptop modem, but a 386 kernel based driver for the
same modem is there! This is bad support indeed.

There is no significant work for which UBUNTU charges for the services. I'm
sure their services suck as much as Gutsy. Till Feisty I was a string
supported of Ubuntu and loved it better than ANY OS. Gutsy is a gross
disappointment indeed. They'll lose patrons at the rate they are rushing to
ruin Linux.

-Balaji

On Nov 29, 2007 2:48 AM, anibal <email address hidden> wrote:

> I do agree in one thing, is an anoying bug. It even feels like wndows
> loading with a mcfee antivirus ;-)
>
> I do not agree is an envidia problem. I use an internal onboard video
> card no nvidia things.
> For one moment i was thinking it was a network problem, but my network
> is working correctly hosts files is correct network files also. Others X
> env are working properly.. im even thinking to switch to kbuntu but kde
> can be also really buggy.. so i will wait..
>
>
>
> Ricardo Pérez López wrote:
> > My Gutsy desktop takes ~34 secs to fully load GNOME. The Feisty machines
> > in my classroom (I'm a computer science teacher) takes ~12 secs to fully
> > load GNOME, and these machines are significantly slower than my home
> > desktop computer. Other Gutsy machines in the High School takes 25-30
> > secs.
> >
> > IMHO, this is a very annoying bug, and, after a brief investigation, I
> > think the problem only appears in machines with NVIDIA graphics ca...

This would be my last comment. I have just remove Ubuntu 7.10 from my
system.. this thing is to buggy.. The whole thing about ubuntu was to have
an out of the box working properly linux distro. 7.10 is far from this..

it was fun to see some new features, we are going the right direction..
but still not there. As the linux thing is mainly based on freedom of
choice, im free to choose other distro in the meanwhile that will do
exactly what i want.

I will check new future releases.

--
With Kind Regards,

> Andrew>
> To think that the desktop should look
> significantly different between releases is a side effect of having used
> Windows too long! Linux is a progressive development and many of the
> tools I use have fixed issues I had in previous releases or added new
> functions that I now use.
>
> Balaji>
> I'm not expecting a significant change in the desktop. In fact between
> Feisty and Gutsy there IS a change in the desktop - Compiz. But I don't
> care
> about it. What I'm looking for is:
> 1. Better driver support for different printer, scanner models etc.
> 2. Better support of Wireless. My wireless connection setup is still a
> very
> complex procedure.
> 3. Bettter VPN support
> 4. POWER MANAGEMENT - This was promised to have improved in Gutsy. I see
> NO
> improvement at all.
> 5. Better Bluetooth support - I still can't send stuff to my laptop from
> my
> mobile. I don't know when I will send SMSes from my laptop.
>
> I know each one of them have a different software now, like vpnc or
> kbluetoothd etc. The thing is I want to use the GNOME version of these and
> reduce the disk space involved in installing multiple software. GNOME
> promised better work on this.
>
> Power management is a matter of the kernel. In the Gutsy release notes
> they
> said that the use of the new kernel improves power management. BULLSHIT.
>
> Driver support is dependent on their relationship with the community of
> programmers writing drivers like SANE or ALSA etc. I don't think they have
> good contacts anymore. Almost everything is broken once you migrate from
> Feisty. In migrating from one version of OS to the next, I don't want to
> keep redoing all the setup activities to work on every software and
> driver.
>
> Even restricted drivers was a problem. They don't have a generic kernel
> based driver from my laptop modem, but a 386 kernel based driver for the
> same modem is there! This is bad support indeed.
>
> There is no significant work for which UBUNTU charges for the services.
> I'm
> sure their services suck as much as Gutsy. Till Feisty I was a string
> supported of Ubuntu and loved it better than ANY OS. Gutsy is a gross
> disappointment indeed. They'll lose patrons at the rate they are rushing
> to
> ruin Linux.
>
> -Balaji
>
>
> On Nov 29, 2007 2:48 AM, anibal <email address hidden> wrote:
>
>> I do agree in one thing, is an anoying bug. It even feels like wndows
>> loading with a mcfee antivirus ;-)
>>
>> I do not agree is an envidia problem. I use an internal onboard video
>> card no nvidia things.
>> For one moment i was thinking it was a network problem, but my network
>> is working correctly hosts files is correct network files also....

>This would be my last comment. I have just remove Ubuntu 7.10 from my system.

My "fix" for this has been to switch to KDE. It took a couple of days to get used to, but is probably worth trying out before switching distros.

I had the same problem and I solved it by adding my hostname to 127.0.0.1 in /etc/hosts, as mentioned above.
Now it loads in less than ~10sec.
It seams that this was a dns problem on my machine.

thx for the solution to vampire666eng

El dom, 02-12-2007 a las 12:47 +0000, jakommo escribió:
> *** This bug is a duplicate of bug 128803 ***
> https://bugs.launchpad.net/bugs/128803
>
> I had the same problem and I solved it by adding my hostname to 127.0.0.1 in /etc/hosts, as mentioned above.
> Now it loads in less than ~10sec.
> It seams that this was a dns problem on my machine.

By the way... what graphics card do you have?

Removing network-manager and network-manager-gnome seems to have solved the issue for me.

How do I do that, and what do I lose by doing that? What does Network
Manager etc. do?

On Dec 8, 2007 8:02 AM, AntoninoSabetta <email address hidden> wrote:

> *** This bug is a duplicate of bug 128803 ***
> https://bugs.launchpad.net/bugs/128803
>
> Removing network-manager and network-manager-gnome seems to have solved
> the issue for me.
>
> --
> [Gutsy] GNOME takes too much time to load during system boot
> https://bugs.launchpad.net/bugs/151544
> You received this bug notification because you are a direct subscriber
> of the bug (via bug 128803).
>

What do you use in place of network-manager-gnome? How can one connect to
the internet automatically without it, configure IP addresses etc? I may be
dumb. But this has worked so far in Ubuntu. Having to remove it to make
Ubuntu work is a clear indication of a problem with Ubuntu and not
network-manager-gnome. When will people own up the problem with Gutsy Ubuntu
and correct it? Don't shift the blame to network-manager-gnome.

-Balaji

On Dec 8, 2007 6:32 PM, AntoninoSabetta <email address hidden> wrote:

> *** This bug is a duplicate of bug 128803 ***
> https://bugs.launchpad.net/bugs/128803
>
> Removing network-manager and network-manager-gnome seems to have solved
> the issue for me.
>
> --
> [Gutsy] GNOME takes too much time to load during system boot
> https://bugs.launchpad.net/bugs/151544
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Balaji

You use system>admin>network. That way your interface is configured without network manager and it is fast. The only problem is for laptop users like me who need to switch between networks very often, network-manager is VERY much better at that.

By the way you should comment on the main bug, not in the duplicate?
To remove network manager, just find it in synaptic and remove it. You have to know how to configure your network with the other user interface afterwards however, so I suggest you practice with that first.

I've got the same problem as described above by others. I've had a look at my /etc/hosts and it all seems ok. I've just disabled bluetooth in the Sessions but havent restarted yet to see if it has any effect. I find the bug irritating, but not a show stopper. I'm glad someone posted an idea on how to change the color at least. The most annoying factor for me was that it was using the ubuntu brown which was messing my color theme. :)

Just to throw a curve ball here.....

I never had this problem until i fixed the shutdown hang problem. So any visual effects or anything cool i had setup remained the same before and after the shutdown fix.

I fixed the shutdown hang by the advice given in the first post here
http://ubuntuforums.org/showthread.php?t=591229&page=8

coulod the driver change be causing this?

cheers

AthlonXP 2400+, nvidia GeForce FX 5700LE, same problem, very long login, usually no error but sometime after hanging for a while with the yellow screen, it pops up an error in a small window saying:

"There was an error starting the GNOME Settings Daemon.

Some things, such as themes, sounds, or background settings may not work correctly.

The last error message was:

Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

GNOME will still try to restart the Settings Daemon next time you log in."

 I click "Close" and then my desktop appears with the wrong resolution; wide screen instead of 1280x1024.
I logout & login and it's fine.

@G. Tehcron

same here (although I don't use GDM anymore, I use the original Debian one)

On Sat, 2008-03-29 at 22:38 +0000, G. Tehcron wrote:
> *** This bug is a duplicate of bug 128803 ***
> I click "Close" and then my desktop appears with the wrong resolution; wide screen instead of 1280x1024.
> I logout & login and it's fine.
>

Try to install dbus-x11. It didn't solve the delay for me, but at least
it did resolve the errors.

I got a Macbook. Problem solved.

On Sun, Mar 30, 2008 at 4:06 PM, Romano Giannetti <
<email address hidden>> wrote:

> *** This bug is a duplicate of bug 128803 ***
> https://bugs.launchpad.net/bugs/128803
>
>
> On Sat, 2008-03-29 at 22:38 +0000, G. Tehcron wrote:
> > *** This bug is a duplicate of bug 128803 ***
> > I click "Close" and then my desktop appears with the wrong resolution;
> wide screen instead of 1280x1024.
> > I logout & login and it's fine.
> >
>
> Try to install dbus-x11. It didn't solve the delay for me, but at least
> it did resolve the errors.
>
> --
> [Gutsy] GNOME takes too much time to load during system boot
> https://bugs.launchpad.net/bugs/151544
> You received this bug notification because you are a direct subscriber
> of the bug (via bug 128803).
>

I did a clean install of Hardy Beta and installed Preload (which seamed to speed my Gutsy up slightly) and so far after a couple of days and several reboots this problem hasn't reared its ugly head. Hopefully it will stay like this!