Bug 9606 - Long delay from login to Gnome3 shell
Summary: Long delay from login to Gnome3 shell
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-03 20:19 CEST by Marcus Zurhorst
Modified: 2015-03-31 16:05 CEST (History)
4 users (show)

See Also:
Source RPM: gnome-shell-3.6.3.1-2.mga3.src.rpm
CVE:
Status comment:


Attachments

Description Marcus Zurhorst 2013-04-03 20:19:48 CEST
Description of problem:
Every time I log from GDM into Gnome3, I have to wait a very long time.
It takes ~65-70 seconds to get the top panel of the Gnome-Shell loaded.

Any further action does not accelerate this (actions like moving the cursor into the upper left "hot corner" etc)

I have no clue where this delay is coming from.  Afterwards, the environment is quite responsive.



Version-Release number of selected component (if applicable):
gnome-shell-3.6.3.1-2.mga3.src.rpm


How reproducible:
100%  (every login the same delay)


Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2013-05-28 23:14:14 CEST
is this still valid ?

Version: Cauldron => 3

Comment 2 Marcus Zurhorst 2013-05-28 23:37:32 CEST
Yes, it is.

I see it every time I start my computer.
Today I booted the laptop, but did not log on for ~10-15min.
When I now log into the Gnome3 session for my user, I have to wait for the above mentioned period.

==> thus, I assume it is not related to the system not being ready yet.
Instead, it needs to be related to the particular session.

I logged into TTY2 with root, but "top" did not show anything sticking out with CPU load.   Also, I did "ping google.com", and had network available.  This was my first suspect that Gnome3 is waiting for network etc.

I would like to provide further information, but I need some help to fetch this info.   How can I monitor what the system is doing in this time?
Manuel Hiebel 2013-05-28 23:47:06 CEST

CC: (none) => fundawang, mageia, olav

Comment 3 Sander Lepik 2013-05-29 09:43:28 CEST
Does it happen with new user too?
If yes, then can you _attach_ the output of this command:
systemd-analyze plot > boot.svg

Keywords: (none) => NEEDINFO
CC: (none) => sander.lepik

Comment 4 Marcus Zurhorst 2013-06-01 08:10:25 CEST
I tried a new user "testuser" and gathered these times (always from GDM logon button to appearing of the black Gnome3 "menu bar" on top of the screen)

testuser login after boot:  23 seconds
testuser 1st re-login:  7 seconds
testuser 2nd re-login:  7 seconds

marcus 1st re-login:  9 seconds
marcus 2nd re-login:  7 seconds


When I flip the procecure and start with user "marcus" after booting, I see the above mentioned >60 seconds delay.  Loging off and re-login with "testuser" will directly yield the 7 seconds.

I compared the svg files for both users, and they are identical.
According to the graphics, the boot time takes ~45 seconds.   I think, the graphics stops which GDM, but my "problem" happens afterwards.


When I visually compare the two logins with "testuser" and "marcus", I realize that the swirl around the mouse pointer is more present with "testuser".  But maybe, this is pure reception problem, because it is percentagewise longer present within the shorter login time.


Can I somehow instrument the login sequence as well?
-- I tried root access from TTY2, but top did not give me any hint.  Top may not be the right tool.  How can I check this better from there?


Thanks for your support,
   Marcus


PS:  I understood that you don't need the svg file now.  If you still like to see it, please let me know.
Manuel Hiebel 2013-06-08 16:49:38 CEST

Keywords: NEEDINFO => (none)

Comment 5 Marja Van Waes 2015-03-31 16:05:43 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.