You are not logged in.
Hello.
Since it is now the default solution, I have migrated from initscripts to pure systemd. I have followed wiki and it was relatively painless. Then I upgraded to Gnome 3.6.
Even before the upgrade from Gnome 3.4 to Gnome 3.6 I have noticed that after I type my password into GDM, it takes noticeably long to get to the working environment. Only my wallpaper is visible and my hdd appears to be idle according to the led diode.
So I assume this is a systemd issue.
Tried systemd-analyze blame and it looks like Network manager takes quite a time to start.
I have the same problem in Cinnamon and Gnome shell. Also, in Gnome shell, the bottom hiding notification area is missing, not sure if that is related, but I guess it is not.
I am also using radeon and I see similar modeline records in logs as in this thread: https://bbs.archlinux.org/viewtopic.php?id=151378
Last edited by Raqua (2012-11-06 08:49:40)
Offline
Are you sure the notification area is missing? It takes a while to popup when you use the mouse (this is design). Try using the shortcut 'windows key + m' and see if it shows up.
Offline
Well, I tried it and it is definitely not working as before the upgrade. If this has not changed significantly, then it is just not there. I am pretty sure, I have waited at least 3 seconds for it to appear.
But since I use Cinnamon anyway, I do not care really. My problem is the slow start after login.
Thank you for your effort though.
Offline
Why does it take so long for network manager to start ?
# systemd-analyze blame
30238ms NetworkManager.service
20795ms polkit.service
5536ms gdm.service
3337ms systemd-logind.service
2996ms shorewall.service
1931ms dev-mqueue.mount
1864ms sys-kernel-debug.mount
1824ms dev-hugepages.mount
1781ms systemd-remount-fs.service
1760ms lm_sensors.service
1633ms systemd-tmpfiles-setup.service
1616ms systemd-modules-load.service
1270ms accounts-daemon.service
1219ms systemd-udevd.service
1154ms systemd-sysctl.service
1091ms systemd-udev-trigger.service
910ms cpupower.service
623ms dcron.service
473ms rtkit-daemon.service
400ms udisks2.service
254ms systemd-vconsole-setup.service
216ms systemd-readahead-collect.service
160ms ntpd.service
147ms systemd-readahead-replay.service
132ms colord.service
130ms systemd-user-sessions.service
48ms media-Storage.mount
11ms upower.service
5ms tmp.mount
4ms wpa_supplicant.service
2ms proc-sys-fs-binfmt_misc.mount
2ms sys-fs-fuse-connections.mount
Offline
Ok, according to this, in order to start service sooner I just need to do
systemd enable XXX.service
I have NetworkManager enabled like this.
I am thinking of setting the boot target from multi-user environment to single user to force it starting sooner. Not sure it is a good idea.
I can not believe I am the only one having this problem.
Offline
Here is the boot proces plot chart. You can see that Polkit and NetworkManager are indeed to blame.
http://min.us/lMMGSqu1vpKow (you need to download the pic to see it)
Offline
Moving from gnome 3.4 to 3.6 I have noticed that gdm takes a lot longer to start, as well as actually logging in to gnome takes much longer, also full systemd.
I have just re-installed because I needed a MBR setup for Windows dual boot, Ill install gnome and see what happens
bitcoin: 1G62YGRFkMDwhGr5T5YGovfsxLx44eZo7U
Offline
Ok, please report back if anything changed. I would hate to reinstall though, haven't done it for years...
Offline
For a start, while installing gnome I get frequent:
[2012-11-15 21:29] (gconftool-2:4701): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
[2012-11-15 21:29] Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
bitcoin: 1G62YGRFkMDwhGr5T5YGovfsxLx44eZo7U
Offline
Ok, fresh install, here we are:
[jason@jason-laptop ~]$ sudo systemd-analyze blame
[sudo] password for jason:
5999ms NetworkManager.service
4792ms gdm.service
2555ms systemd-logind.service
793ms systemd-udev-trigger.service
693ms polkit.service
527ms systemd-remount-fs.service
480ms systemd-vconsole-setup.service
468ms sys-kernel-debug.mount
452ms dev-hugepages.mount
443ms systemd-udevd.service
438ms dev-mqueue.mount
404ms wpa_supplicant.service
243ms systemd-tmpfiles-setup.service
135ms colord.service
128ms rtkit-daemon.service
73ms systemd-user-sessions.service
73ms systemd-sysctl.service
66ms upower.service
55ms udisks2.service
37ms accounts-daemon.service
26ms tmp.mount
1ms sys-fs-fuse-connections.mount
[jason@jason-laptop ~]$
Getting crashes opening nautilis....
Last edited by jrussell (2012-11-15 19:39:15)
bitcoin: 1G62YGRFkMDwhGr5T5YGovfsxLx44eZo7U
Offline
After setting up everything again, I dont really notice much change in start up time of gdm from boot, but logging in to gnome seems a bit faster, I'll post another blame later
bitcoin: 1G62YGRFkMDwhGr5T5YGovfsxLx44eZo7U
Offline
I have experimented yesterday and replaced gdm with lxdm, but nothing really changed, Gnome/Cinnamon was still very slow to show.
I also disabled network manager but no change again, although analyze-blame was now ok and much faster.
Since it is not GDM to blame, I think there was some change (Gnome/GTK internals?) that makes the environment start very slow.
Offline