Hi everyone, I've been experiencing a bit of an annoying problem lately, and was wondering if anyone else has ran into anything similar, and possibly found a solution. I'm running debian testing with gnome 3.4. The first time I start my GUI on a particular boot be it at boot up via gdm, invoking the gdm init script manually by hand after logging into the console or by using startx it takes an incredibly long time for the gnome-shell to load and become ready. I have auto-log in enabled and it takes about 50-60 seconds from the point I start gdm or startx until the gui is ready to use. I'm using a core I5 2.4 GHZ machine with 4 GB of ram so there is a bit of power. I presumed it should probably be quicker than this. Or is gnome-shell just really slow? I've also tried disabling different apps which I thought might be causing problems such as network-manager, but it really didn't change anything. I've also tried creating a fresh user account to see if there is any difference, but it took just as long. Finally, I looked through my syslog and /var/log/messages, but nothing particularly obvious appeared to me. So is this normal behaviour for gnome-shell? Otherwise any ideas where I should continue to investigate would be greatly appreciated. Thanks in advance, Daniel
Slower than my 3.5 year old desktop with fedora. I'd investigate. Bianca - on my phone, please excuse my brevity. On Nov 22, 2012 12:15 AM, "Daniel Dalton" <d.dalton@iinet.net.au> wrote:
Hi everyone,
I've been experiencing a bit of an annoying problem lately, and was wondering if anyone else has ran into anything similar, and possibly found a solution.
I'm running debian testing with gnome 3.4.
The first time I start my GUI on a particular boot be it at boot up via gdm, invoking the gdm init script manually by hand after logging into the console or by using startx it takes an incredibly long time for the gnome-shell to load and become ready. I have auto-log in enabled and it takes about 50-60 seconds from the point I start gdm or startx until the gui is ready to use. I'm using a core I5 2.4 GHZ machine with 4 GB of ram so there is a bit of power.
I presumed it should probably be quicker than this. Or is gnome-shell just really slow? I've also tried disabling different apps which I thought might be causing problems such as network-manager, but it really didn't change anything. I've also tried creating a fresh user account to see if there is any difference, but it took just as long. Finally, I looked through my syslog and /var/log/messages, but nothing particularly obvious appeared to me.
So is this normal behaviour for gnome-shell? Otherwise any ideas where I should continue to investigate would be greatly appreciated.
Thanks in advance, Daniel _______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main
I spy this in an old revision on the Arch wiki: https://wiki.archlinux.org/index.php?title=GNOME&diff=222213&oldid=212660#GN... which suggests a possible sound issue. It might be worth trying to dig through all the alterations to that page to see why it isn't suggested in the current wiki.
On Thu, Nov 22, 2012 at 12:10:15PM +1100, Andrew Spiers wrote:
I spy this in an old revision on the Arch wiki: https://wiki.archlinux.org/index.php?title=GNOME&diff=222213&oldid=212660#GN... which suggests a possible sound issue. It might be worth trying to dig through all the alterations to that page to see why it isn't suggested in the current wiki.
Yes, I saw something similar. I created a new user account though and the problem still exists, sigh. Also, I'm not using pulseaudio. Thanks for your suggestions. Cheers, Dan
Daniel Dalton writes:
[gnome3 is slow]
Since no one else has mentioned it... bootchart. Two parts, one that makes a tarball of /proc every tenth of a second, the other turns that into a pretty Gantt-style chart so you can see what is taking all the clock time. You ought to be able to start it up *post* boot to graph gnome3's startup instead of the initrd-to-rc.local processes. There are multiple implementations of both bits. IMO the easiest for the former is the one included in busybox. The latter try pybootchart2 (from git? can't remember if it has been released). There is an older version in java which I automatically dismiss. IIRC you're also visually impaired, so I dunno how helpful it is. Hopefully at least as good as the existing "buy fastar hardware" and "don't run gnome3" responses :-)
On Thu, Nov 22, 2012 at 04:30:09PM +1100, Trent W. Buck wrote:
Daniel Dalton writes:
[gnome3 is slow]
Since no one else has mentioned it... bootchart.
Yes, I thought it was only good for the boot not the log in stage. Perhaps I was wrong though and should try it.
Two parts, one that makes a tarball of /proc every tenth of a second, the other turns that into a pretty Gantt-style chart so you can see what is taking all the clock time.
You ought to be able to start it up *post* boot to graph gnome3's startup instead of the initrd-to-rc.local processes.
There are multiple implementations of both bits. IMO the easiest for the former is the one included in busybox. The latter try pybootchart2 (from git? can't remember if it has been released). There is an older version in java which I automatically dismiss.
Hmm, I'll need to investigate it a bit :)
IIRC you're also visually impaired, so I dunno how helpful it is.
Yes - good memory :) I'll try and use it and perhaps seek some sighted help to view the graph. Thanks, Dan
participants (4)
-
Andrew Spiers -
Bianca Gibson -
Daniel Dalton -
trentbuck＠gmail.com