CielitoLindux
14-09-2015, 09:33
Buongiorno.
Gdm è diventato veramente lento ad avviarmi gnome. C'è da dire che la stessa cosa mi accade sul portatile con arch, quindi non credo proprio sia un problema legato a Fedora di per sè, ma vorrei comunque iniziare ad indagare qui.
Ci mette più tempo gdm ad avviarmi gnome che il pc ad avviarsi da 0 a gdm.
Ho creato un altro utente e l'avvio di gnome è immediato quindi il problema è strettamente legato all'utente principale. No ho particolari servizi all'avvio, o quanto meno sono sempre gli stessi da F17 su questo pc.
So che poteri sostituirlo con altri manager ma prima vorrei comunque provare a sistemare.
Suggerimenti?
[root@Fodora ~]# systemctl -all|grep not-found
● apparmor.service not-found inactive dead apparmor.service
● livesys.service not-found inactive dead livesys.service
● lvm2-activation-early.service not-found inactive dead lvm2-activation-early.service
● lvm2-activation.service not-found inactive dead lvm2-activation.service
● systemd-readahead-collect.service not-found inactive dead systemd-readahead-collect.service
● systemd-readahead-replay.service not-found inactive dead systemd-readahead-replay.service
● ypbind.service not-found inactive dead ypbind.service
● syslog.target not-found inactive dead syslog.target
[root@Fodora ~]# systemctl -all|grep error
[root@Fodora ~]# systemd-analyze blame
19.898s plymouth-quit-wait.service
11.648s cups.service
9.465s dev-sda2.device
8.002s systemd-journald.service
7.270s systemd-udev-settle.service
7.139s NetworkManager-wait-online.service
6.682s firewalld.service
5.175s vboxdrv.service
5.102s accounts-daemon.service
4.246s dnf-makecache.service
4.103s libvirtd.service
3.685s abrtd.service
2.824s NetworkManager-dispatcher.service
2.252s systemd-fsck@dev-disk-by\x2duuid-63c83c32\x2d3508\x2d4365\x2d82
2.155s systemd-tmpfiles-clean.service
2.118s lvm2-monitor.service
1.906s rsyslog.service
1.885s systemd-udevd.service
1.626s packagekit.service
1.492s systemd-fsck@dev-disk-by\x2duuid-1cc86f97\x2dd6f0\x2d42b5\x2d8d
1.292s systemd-tmpfiles-setup-dev.service
915ms systemd-binfmt.service
895ms plymouth-start.service
892ms abrt-ccpp.service
872ms systemd-journal-flush.service
814ms systemd-sysctl.service
800ms lm_sensors.service
767ms dev-disk-by\x2duuid-17efda43\x2d329f\x2d4cbc\x2d9494\x2d1cf079d
763ms systemd-logind.service
757ms mnt-server.mount
734ms proc-sys-fs-binfmt_misc.mount
701ms systemd-random-seed.service
675ms rpcbind.service
608ms dmraid-activation.service
588ms NetworkManager.service
520ms polkit.service
516ms fedora-readonly.service
503ms mcelog.service
347ms udisks2.service
339ms netcf-transaction.service
311ms systemd-remount-fs.service
302ms systemd-tmpfiles-setup.service
230ms colord.service
213ms fedora-import-state.service
185ms dev-hugepages.mount
162ms boot.mount
161ms gdm.service
157ms kmod-static-nodes.service
131ms wpa_supplicant.service
109ms systemd-fsck-root.service
102ms [email protected]
92ms auditd.service
85ms rtkit-daemon.service
77ms dracut-shutdown.service
76ms plymouth-read-write.service
76ms dev-mqueue.mount
74ms sys-kernel-debug.mount
71ms [email protected]
64ms systemd-udev-trigger.service
61ms tmp.mount
59ms home.mount
51ms upower.service
41ms systemd-update-utmp.service
16ms systemd-vconsole-setup.service
11ms vboxballoonctrl-service.service
10ms vboxweb-service.service
9ms systemd-user-sessions.service
9ms vboxautostart-service.service
3ms systemd-update-utmp-runlevel.service
2ms sys-fs-fuse-connections.mount
1ms sys-kernel-config.mount
Gdm è diventato veramente lento ad avviarmi gnome. C'è da dire che la stessa cosa mi accade sul portatile con arch, quindi non credo proprio sia un problema legato a Fedora di per sè, ma vorrei comunque iniziare ad indagare qui.
Ci mette più tempo gdm ad avviarmi gnome che il pc ad avviarsi da 0 a gdm.
Ho creato un altro utente e l'avvio di gnome è immediato quindi il problema è strettamente legato all'utente principale. No ho particolari servizi all'avvio, o quanto meno sono sempre gli stessi da F17 su questo pc.
So che poteri sostituirlo con altri manager ma prima vorrei comunque provare a sistemare.
Suggerimenti?
[root@Fodora ~]# systemctl -all|grep not-found
● apparmor.service not-found inactive dead apparmor.service
● livesys.service not-found inactive dead livesys.service
● lvm2-activation-early.service not-found inactive dead lvm2-activation-early.service
● lvm2-activation.service not-found inactive dead lvm2-activation.service
● systemd-readahead-collect.service not-found inactive dead systemd-readahead-collect.service
● systemd-readahead-replay.service not-found inactive dead systemd-readahead-replay.service
● ypbind.service not-found inactive dead ypbind.service
● syslog.target not-found inactive dead syslog.target
[root@Fodora ~]# systemctl -all|grep error
[root@Fodora ~]# systemd-analyze blame
19.898s plymouth-quit-wait.service
11.648s cups.service
9.465s dev-sda2.device
8.002s systemd-journald.service
7.270s systemd-udev-settle.service
7.139s NetworkManager-wait-online.service
6.682s firewalld.service
5.175s vboxdrv.service
5.102s accounts-daemon.service
4.246s dnf-makecache.service
4.103s libvirtd.service
3.685s abrtd.service
2.824s NetworkManager-dispatcher.service
2.252s systemd-fsck@dev-disk-by\x2duuid-63c83c32\x2d3508\x2d4365\x2d82
2.155s systemd-tmpfiles-clean.service
2.118s lvm2-monitor.service
1.906s rsyslog.service
1.885s systemd-udevd.service
1.626s packagekit.service
1.492s systemd-fsck@dev-disk-by\x2duuid-1cc86f97\x2dd6f0\x2d42b5\x2d8d
1.292s systemd-tmpfiles-setup-dev.service
915ms systemd-binfmt.service
895ms plymouth-start.service
892ms abrt-ccpp.service
872ms systemd-journal-flush.service
814ms systemd-sysctl.service
800ms lm_sensors.service
767ms dev-disk-by\x2duuid-17efda43\x2d329f\x2d4cbc\x2d9494\x2d1cf079d
763ms systemd-logind.service
757ms mnt-server.mount
734ms proc-sys-fs-binfmt_misc.mount
701ms systemd-random-seed.service
675ms rpcbind.service
608ms dmraid-activation.service
588ms NetworkManager.service
520ms polkit.service
516ms fedora-readonly.service
503ms mcelog.service
347ms udisks2.service
339ms netcf-transaction.service
311ms systemd-remount-fs.service
302ms systemd-tmpfiles-setup.service
230ms colord.service
213ms fedora-import-state.service
185ms dev-hugepages.mount
162ms boot.mount
161ms gdm.service
157ms kmod-static-nodes.service
131ms wpa_supplicant.service
109ms systemd-fsck-root.service
102ms [email protected]
92ms auditd.service
85ms rtkit-daemon.service
77ms dracut-shutdown.service
76ms plymouth-read-write.service
76ms dev-mqueue.mount
74ms sys-kernel-debug.mount
71ms [email protected]
64ms systemd-udev-trigger.service
61ms tmp.mount
59ms home.mount
51ms upower.service
41ms systemd-update-utmp.service
16ms systemd-vconsole-setup.service
11ms vboxballoonctrl-service.service
10ms vboxweb-service.service
9ms systemd-user-sessions.service
9ms vboxautostart-service.service
3ms systemd-update-utmp-runlevel.service
2ms sys-fs-fuse-connections.mount
1ms sys-kernel-config.mount