** Changed in: gnome-session
Importance: Unknown = Medium
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I am using jaunty x86_64 and found a quick fix by just deleting
$HOME/.gconfd/saved_state
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Afaict, the bootcharts are pretty old. It could be interesting if
someone could make new login bootcharts for current versions (gutsy?
really!?) such as Karmic and Jaunty. And perhaps with gnome-shell in
karmic too.
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You
** Changed in: gnome-session (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
Status: New = Triaged
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: gnome-session
Status: Unknown = New
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
a (small) part of the problem *might* be due to the recent documents? I
have no idea if .recently-used.xbel is used during startup, but if it
is, it is possible that it contributes to making the login time worse.
http://jeff.ecchi.ca/blog/?p=317
Examples of performance decrease because of this
** Also affects: gnome-session via
http://bugzilla.gnome.org/show_bug.cgi?id=484358
Importance: Unknown
Status: Unknown
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Here's my one, not completely sure how to read it. Hope it helps.
** Attachment added: gutsy-20080318-1.png
http://launchpadlibrarian.net/12719297/gutsy-20080318-1.png
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are
the bug is not a nautilus one
** Changed in: nautilus (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
Status: New = Invalid
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug
You can install bootchart, move the init.d stop-bootchart somewhere
else, use autologin and run the stop-bootchart start manually after
login
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs,
Would be nice to try again on hardy beta and note if the issue is
resolved, we have been doing several changes recently:
- jockey and update-manager delay their update to no slow the login
- deskbar-applet is not in the default configuration and tracker indexing is
not enabled by default
- gdm
Thanks, Sebastien. I attach my bootchart I've generated following your
instructions. Hope this helps.
** Attachment added: hardy-20080317-1.png
http://launchpadlibrarian.net/12709104/hardy-20080317-1.png
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received
I'm glad to say that now, in Hardy, GNOME takes ~35 secs to load... It's
as fast (or better say, as slow) as Gutsy...
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
im not sure but i think the problem comes from GDM and not gnome.
when starting X via startx, i got the feeling that gnome boots much faster.
but i could be wrong...
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a
how exactly do I use the .diff file to patch it?
I know I need the source and need to use the 'patch' command, but that's
about all I know :P
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs,
How can I patch bootchart (for gnome login time) ?
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Is this this patch in http://www.gnome.org/~lcolitti/gnome-startup/analysis/
that we should use ?
Is it possible to have an already bootchart packaged ?
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of
Added nautilus. I believe this is the offending application.
** Changed in: nautilus (Ubuntu)
Sourcepackagename: gnome-session = nautilus
Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned)
Status: Incomplete = New
** Changed in: gnome-session (Ubuntu)
Sourcepackagename:
Could someone try this for me:
open a console and do killall nautilus.
If it works (like it does for me), the whole desktop will freeze for
roughly the same time as when starting up.
I'm pretty sure that this is a nautilus issue, as my system freezes
right before nautilus comes up (no desktop
On Mon, 2008-03-10 at 18:30 +, enigma_0Z wrote:
If it works (like it does for me), the whole desktop will freeze for
roughly the same time as when starting up.
I tried it, but nautilus resumes in normal times... so it's something
else for me.
I have a gut feeling:
I am trying kernel
I've created an image of the GNOME logging process with bootchart, I'm
attaching the image, hope it helps.
** Attachment added: bootchart graph of the GNOME logging process.
http://launchpadlibrarian.net/1255/bootchart.svgz
--
[Gutsy] very slow gnome startup
It seems that Hardy is even slower than Gutsy... In my computer, Gutsy
took ~34 secs to load, but now Hardy takes ~1 minute. Almost twice!
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which
Yes I agree, HARDY TAKES FOREVER TO BOOT! gosh! it really sucks lol,
but hardy looks nice tho :]
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
could users having the issue try to get startup graphs similar to the
one sent before?
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I'll be glad to send you those graphs. How can I generate them? Thanks.
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
yes I'll be glade as well, how can I graph my startup as well?
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
did you read the graph correctly? it indicates that feisty login takes
15 seconds where gutsy takes 22 seconds and hardy 29 seconds
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Sat, Mar 8, 2008 at 9:24 AM, Sebastien Bacher [EMAIL PROTECTED]
wrote:
did you read the graph correctly? it indicates that feisty login takes
15 seconds where gutsy takes 22 seconds and hardy 29 seconds
Yes, but it has been the experience of a large part of this thread that
Gutsy is
you have to consider that is a stock installation and that the machine
might be faster than yours, on a some years old a default gusty
installation takes around 26 seconds there
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because
Just for informations :
http://blog.kagou.fr/post/2008/03/06/Chronos-US-version
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks for taking the time to make such comparisons.
I, however, cannot believe they are 100% correct. At least on my
machines (and all others I saw) feistys gdm-login was much faster than
gutsys...
regards
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received
Thank you for your work on that, those are useful informations we can
use to try working on the login speed
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I have created a graph of a login to gnome in hardy using the method described
here:
http://www.gnome.org/~federico/news-2008-02.html
I have applied the patch there to the ubuntu version of gnome-panel (I have
actually dropped ubuntu patch 16_* because I was to lazy to have a look why
that
** Tags added: qa-hardy-desktop
** Tags removed: qa-hardy-list
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
And attached the strace logfile which I have used to create that graph.
it says there for the esd pulseaudio wrapper
8107 1203029028.058727 read(18, [esd]\n# autospawning is not reco..., 4096)
= 368
** Attachment added: strace gnome-session
if you want it free youve got to be willing to spend some time wrestling
with it..
luckily ubuntu has worked very well on the several machines i have
installed it on, for myself and others. however every single one of
them had quirks, some of which took a LONG time to figure out, and other
less
personally bootchart won't do anything for me since the problem is not
on booting but on gnome login. I believe someone above was able to make
it work all the way through the desktop loading, but i don't think i
have the technical skills to make that work. If there is an easier way
that you know
Your comments were not really constructive, helpful, or nor do they in
anyway acknowledge a very real problem with an ubuntu installation
gone very wrong. It takes nearly 5 minutes to boot. Nothing that I
have done changed any configuration other then stock installation. I
have enjoyed
On Feb 7, 2008, at 4:52 AM, Sebastien Bacher wrote:
Those comments are not really constructive, there is no obvious bug
there and the issues described might be a collection of different
things
and incorrect user configurations. I did new dapper, feisty and gutsy
installation on a
sorry!
I posted in the wrong forum...
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
some people have this problem since gutsy:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/128803
there's someone who has tricked with bootchart to let it log login process
too...
On Feb 8, 2008 4:10 AM, sweetsinse [EMAIL PROTECTED] wrote:
agreed that tip/link from Jean-François
Seb, just out of curosity, what are your criteria for a usable desktop
loaded? Do you mean when everything (ie panel applets) is in place
*and* the hard drive is quiet? 'cause I based all my numbers on the
moment at which the hard drive stops hammering (since I think there is
no other way to get
Thanks for that tip Jean-François: that has my time from login down to
~40 seconds. Most acceptable!
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
well, i read on ubuntuforums.org that this issue seems solved in hardy.
i guess there wont be a fix for gutsy.
concerning the gdm login...
id rather wait a bit more on the complete boot process than after the gdm login.
that readahead thingy had some positive impact here.
before i had to wait a
agreed that tip/link from Jean-François worked very well.
i still get the flashing gnome-panels and am seeking a solution to that,
the readahead hack sped everything up.. i would make a bootchart but i
have changed things, but the blackout after my gnome-panels dissapears
is less than 10 seconds
Those comments are not really constructive, there is no obvious bug
there and the issues described might be a collection of different things
and incorrect user configurations. I did new dapper, feisty and gutsy
installation on a non-too-new machine some days ago using the same
partition and looked
hmpf, no solution yet? this is pretty annoying.
the devs seem not really to care...
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Actually I gave up a long time ago. I went out and bought a mac. At least
it's version of unix is supported. Support from Ubuntu is a little sad...
On Feb 6, 2008 8:30 PM, Stevie [EMAIL PROTECTED] wrote:
hmpf, no solution yet? this is pretty annoying.
the devs seem not really to care...
I've been using Fluxbox for the last couple weeks, but then, I don't think
this (borrowed) laptop would handle GNOME too well. Mine needs to have a
lot of hardware replaced :(
On Feb 6, 2008 9:48 PM, bereanone [EMAIL PROTECTED] wrote:
Actually I gave up a long time ago. I went out and bought a
Hi all,
I have a very similar problem. After a bit of digging I found an entry
for 127.0.1.1 (notice: .1.1, not .0.1) in my /etc/hosts. I commented it
and now the gnome starts fast like in Feisty.
But: why that entry is needed? localhost is on 127.0.0.1, no? Since
1986, no :-)?
--
[Gutsy] very
@Romano: tried your fix, didn't work.
I also tried Debian Lenny which has Gnome 2.20 also, and login takes
about 20 seconds compared to more than 60 seconds in Ubuntu Hardy.
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you
You mean the one that tells your system's hostname?
On Jan 14, 2008 6:31 AM, Romano Giannetti [EMAIL PROTECTED]
wrote:
Hi all,
I have a very similar problem. After a bit of digging I found an entry
for 127.0.1.1 (notice: .1.1, not .0.1) in my /etc/hosts. I commented it
and now the gnome
Yes: what normally there was (at least, when /etc/hosts was written by
hand):
127.0.0.1 localhost my_fancy_hostname_not_qualified_here
...and if you have a fixed IP:
127.0.0.1 localhost
10.1.2.3 hostname.domain
...and on our Debian server it's still like that. This 127.0.1.1
thing is
OK, I was wrong. It did not fix the first login for me, just the second
and following one. On the first login after boot, entering in gnome is
slow as a crawl (20+ seconds). Sorry for the confusion. I will try to
dig this more (it didn't happen at all in Feisty).
--
[Gutsy] very slow gnome
i since ditched feisty and went back to messing with gutsy. gutsy is in
all a very good developmental release and i hope to see splendiferous
things from hardy.
this time however i installed xubuntu.
i enabled compiz/emerald/NetworkManager, and have not had any of the
problems described herein.
So, does anyone have a fix for this problem yet? pepito seems to have
found something that works for him, but I'm not finding this compiz-
start thing anywhere. I myself am a relative newb to Linux, so any
step-by-step instructions would be greatly, greatly appreciated.
I'm sorry that I can't
That's what I have too, but I think if you comment out the part where it
picks between ccp and gconf, and you use ccp, then you don't get any of the
advanced configuration stuff. Actually, if you don't let either load, it'd
probably just freak out and not load because it wouldn't have any
pepito,
In my PC there is a /usr/bin/compiz script (not compiz.start).
The only thing about gconf in the script is:
# load the ccp plugin if present and fallback to plain gconf if not
if [ -f ${PLUGIN_PATH}libccp.so ]; then
COMPIZ_PLUGINS=$COMPIZ_PLUGINS ccp
elif [ -f
EDIT TO MY POST:
I was wrong:
gnome was not 15 secs, but 35 secs as many of you.
I updated the config, removed an env variable that was dodgy and also edited
/usr/bin/compiz-start and removed in it the gconf option as it was telling me
this was already set up.
Then I added to my gnome session
/usr/bin/compiz-start? That file doesn't exist for me. I'm not using gconf
bindings for my compiz either--I'm using ccsm's settings, so my compiz line
in ps -aef is
compiz.real --replace --sm-disable --ignore-desktop-hints ccp
--indirect-rendering
On Dec 18, 2007 11:28 AM, pepito [EMAIL
@pepito
Measure the login time after a doing a reboot first.
This has been mentioned a number of times in this thread.
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Hi guys
Hi Sebastien
Just for info:
I m using gentoo.
$ sudo emerge --info
Portage 2.1.3.19 (default-linux/x86/2007.0/desktop, gcc-4.1.2, glibc-2.6.1-r0,
2.6.22-gentoo-r2 i686)
=
System uname: 2.6.22-gentoo-r2 i686 Intel(R)
** Tags added: qa-hardy-list
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have this problem too, but not just with GNOME. In GNOME, the panels
don't load sometimes and alt+f2 doesn't work. I use Compiz so if I hit
super+t to get a terminal, the GTK parts of the terminal never load (and
then it goes black because it's non-responsive and Compiz knows it). If
I then
I am still having the same problem as everyone else. I cannot pin point
this problem to compiz, network-manager or awn. I don't have many gnome
applets running either. Here is a copy of my .xession-errors.
** Attachment added: .xsession-errors
Removing networkmanager didn't work for me.
Still 50 second login.
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Perhaps dependent of this bug ?
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/78263
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Mathieu Laurent:
My laptop is connected to the same network all the time, so that bug is
the cause of this bug.
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
correction: *not* the cause of this bug.
@Seb: even though edgy login is slower than Arch, it is difficult to
compare when it was another kernel, gnome version etc.
Gutsy definitely has a regression.
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this
there is a duplicate comment suggesting that network-manager is creating
the issue, could whoever has the issue try if uninstalling it makes a
difference there?
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member
there is a duplicate comment suggesting that network-manager is creating
the issue, could whoever has the issue try if uninstalling it makes a
difference there?
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member
Oh yeah and I forgot to mention that of course all these tests were done
~empirically (cold boot, one thing changed at a time). The second 34
seconds! time is, of course, not significative compared to no network
interace configured.
Furthermore, removing compiz + awn reduces the login time by 5
I am not perfectly sure that it is network-managers fault either.
I properly removed it but the difference wasn't that huge.
I still need to check that on other systems, though.
Isn't there any proper way to tell which process takes how long during login?
If that was possible we could easily find
Sorry, but the fix didn't work for me. I tried removing network-manager
network-manager-gnome, but GNOME takes the same time to load fully...
:(
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs,
Holy COW! That guy nailed it! As much as I *love* network manager, I
never *suspected* it at all.
Here are my benchmarks on my desktop computer. It uses a DHCP wired network
interface.
with network-manager =
splash start to login ready: 32.48 seconds
login to fully loaded*: 51.07
Actually I am having the same problem too...
From GDM login until my desktop is fully loaded, i takes about 40 seconds.
I spent whole day trying to find out the problem (including following the
instructions in the bug report) but none work for me...
Jeff, 34 seconds is still considered a long
thats one way to do itmaybe devs will realize how annoying this can
be.
this bug needs instructions on how to approach self-diagnosing the
problem. many people have removed all applets with no results.
sweetsinse seemed to do an extremely thorough job and suggested it may
be a problem with
The issue is not to realize how annoying the bug can be, it's to get
useful datas on what is creating the slowness. The code used is mostly
the upstream one and the issue is likely to happen on other distribution
using GNOME 2.20, switching distribution is not going to fix anything
and let to an
to the contrary, YES, switching to other distros also running Gnome 2.20
has made a big difference to some of the users above. I believe one
person tried Arch linux with more panel aplets and still had 10sec less
than Ubuntu. Then as you saw, anibal switched to Mandriva and seems to
not have
1. Has anybody tried downgrading the kernel version, using the Feisty kernel in
Gutsy? Is there any difference in the startup time?
2. Has anybody tried another distribution that uses GNOME 2.20, as Ubuntu Gutsy
does? Is there any difference in the startup time?
--
[Gutsy] very slow gnome
I have switched to KDE from Gnome because Gnome was taking too long to
start up, and this did fix the problem for me. So I think it is a
problem related to Gnome. In either case Compiz didn't make a
difference.
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You
Those user comments are not clear. Are mandriva users running GNOME? Do
they have compiz fusion activated or not? Does it make a difference to
not run it on Ubuntu? Did they use the same user configuration?
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received
Trying to look at the KDE startup speed difference could also be useful,
maybe the issue is not a GNOME one
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
do you consider that edgy already had the issue then and that's not
something gutsy specific there?
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
On average it took 38 seconds using the beta (trackerd disabled, no
deskbar applet).
However, with the latest updates it takes about 50 seconds.
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs,
i agree, do remember a good drop in time with feisty as well, which
would make this a regression more than anything. not as comparable to
edgy
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs,
Since the gnome-session starts gnome processes, how can it not be
related to gnome?
I have used Arch Linux with the 2.6.22 kernel and it logged in in 20
seconds, about 10 seconds less than edgy and even less than gutsy.
Removing compiz in ubuntu does not make a difference.
--
[Gutsy] very slow
Christoffer, what time takes GNOME in your gutsy to load fully?
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I don't know if edgy already had the issue, but feisty is considerably
faster than gutsy, and I think the issue is about the regression from
feisty to gutsy.
Maybe feisty is abnormally fast comparing with edgy gutsy?
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You
Same problem here...but take a look xt my xsessions errors file.
Interesting.
** Attachment added: Xsessions errors file after slow startup
http://launchpadlibrarian.net/10777167/.xsession-errors
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug
I just want to say i have fixed !!
What i did ?
I have disabled the whole UBUNTU replaced for a working fine by
default linux distro.. Mandriva 2008.
Im out of this bug repport
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification
seb128, do you know how we can help you to solve this bug ?
try to figure why it's slow for you, maybe remove applets, don't use the
desktop effects and note if that's quicker
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because
I forgot it: I tried removing restricted-drivers-manager, tracker daemon
bluetooth manager from GNOME startup, without luck.
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I tried removing applets, removing desktop icons, disabling nvidia
driver, disabling desktop effects... but I only got 3-4 secs of
difference...
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs,
i just installed hardy alpha 1...problem persists in the same way.
again gnome panels appear right away just like feisty, only to be near
immediately killed, then reappear 10+ seconds later. occurs in the same
way as gutsy, but maybe to be expected since this is only alpha 1.
i will be reverting
downgrading the version is not likely going to make the new version be
quicker
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I have tried to strace gnome-session as stated in
http://live.gnome.org/GnomePerformance/LoginTime
The session died quickly, so this approach didn't wok.
I added a new session type in /usr/share/xsessions/ and replaced 'gnome-
session' with 'strace -ttt -f -o /tmp/login.strace
I have found this link in the compiz fusion forum that seems to speak
about the same problem:
http://forum.compiz-fusion.org/showthread.php?t=337highlight=login+slow
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a
shz, I tried disabling my nvidia driver, using the nv one instead,
therefore disabling the hardware support, so compiz doesn't loads during
GNOME startup... but GNOME takes the same time to load, then (~34 secs).
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You
For me, if i disable the nvidia driver, gnome does not slow on boot.
Only when the driver is initialized, do i experience problems.
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
1 - 100 of 191 matches
Mail list logo
