Bug#825850: [systemd] Long time to load accounts-daemon.service and issue with X

[Fenix]

Package: systemd
Version: 230-1
Severity: normal

--- Please enter the report below this line. ---


    Dear maintainer:


After 229.6 (I waited that 230-1 fix it, but it is the same) update I 
have a strange issue. First, as you can see the accounts-daemon.service 
takes a lot of time to load:


--
         53.366s accounts-daemon.service
         15.657s ModemManager.service
         15.655s timidity.service
          14.075s loadcpufreq.service
          12.843s networking.service
           9.097s irqbalance.service
           9.041s dev-sda2.device
           8.415s fancontrol.service
           8.323s console-kit-log-system-start.service
           8.277s mono-xsp2.service
           8.243s firewall.service
           8.240s vboxdrv.service
           8.231s lm-sensors.service
           8.220s avahi-daemon.service
           8.208s alsa-restore.service
           8.160s gdomap.service
           8.159s iio-sensor-proxy.service
           8.159s klogd.service
           6.378s NetworkManager.service
           4.550s systemd-modules-load.service
           3.724s systemd-udevd.service
           3.213s console-screen.service
           2.988s polkitd.service
           2.452s packagekit.service
           2.282s binfmt-support.service
           1.684s gdm.service
           1.540s systemd-logind.service
           1.534s wpa_supplicant.service
           1.509s ntp.service
           1.486s keyboard-setup.service
           1.397s systemd-tmpfiles-setup-dev.service
           1.320s systemd-journald.service
           1.125s xfstt.service
           1.116s colord.service
            951ms dev-hugepages.mount
            950ms dev-mqueue.mount
            949ms sys-kernel-debug.mount
            923ms systemd-remount-fs.service
            895ms systemd-tmpfiles-setup.service
            830ms systemd-update-utmp.service
            796ms apt-daily.service
            480ms kmod-static-nodes.service
            478ms systemd-journal-flush.service
            441ms vboxautostart-service.service
            432ms vboxballoonctrl-service.service
            420ms systemd-udev-trigger.service
            407ms muroard.service
            393ms darkice.service
            354ms systemd-tmpfiles-clean.service
            345ms systemd-user-sessions.service
            307ms udisks2.service
            302ms rc-local.service
            265ms upower.service
            255ms systemd-sysctl.service
            243ms vboxweb-service.service
            233ms proc-sys-fs-binfmt_misc.mount
            218ms console-kit-daemon.service
            216ms 
dev-disk-by\x2duuid-91cc575f\x2d9cd7\x2d49c8\x2d91cd\x2d998cc528f7ef.swap
            143ms console-setup.service
            139ms user at 1000.service
            104ms systemd-random-seed.service
             75ms hddtemp.service
             53ms cpufrequtils.service
             41ms rtkit-daemon.service
             35ms decnet.service
             15ms nullmailer.service
             13ms autofs.service
             12ms sysklogd.service
              8ms systemd-update-utmp-runlevel.service
--


In the boot, systemd show me the message: A start job is running for 
Accouns Service ([a time counter up of one minute]).



Anyway, the gdm3 show me the login for the X and I can login right. But 
the real problem is that about one minute to be in the X, the system 
throws me out to the first text console. I need to enter again with 
ALT-F2. But in this situation only Gnome3 works (he reset one time after 
hang). If I use XFCE the system hangout.




Here is the critial-chain:

--
graphical.target @1min 4.934s
└─accounts-daemon.service @11.567s +53.366s
   └─basic.target @11.465s
     └─sockets.target @11.465s
       └─cups.socket @11.465s
         └─sysinit.target @11.386s
           └─swap.target @11.386s
 
└─dev-disk-by\x2duuid-91cc575f\x2d9cd7\x2d49c8\x2d91cd\x2d998cc528f7ef.swap 
@11.169s
 
└─dev-disk-by\x2duuid-91cc575f\x2d9cd7\x2d49c8\x2d91cd\x2d998cc528f7ef.device 
@11.1
--



I have not activate the systemd journal.



If you need more or extra information , please, feel free to ask.



Thanks.






--- System information. ---
Architecture: i386
Kernel:       Linux 4.5.0-2-686-pae

Debian Release: stretch/sid
   500 testing         www.deb-multimedia.org
   500 testing         ftp.de.debian.org
   500 stable          dl.google.com

--- Package information. ---
Depends                         (Version) | Installed
=========================================-+-==================
libacl1                     (>= 2.2.51-8) | 2.2.52-3
libaudit1                    (>= 1:2.2.1) | 1:2.5.2-1
libblkid1                     (>= 2.17.2) | 2.28-5
libcap2                       (>= 1:2.10) | 1:2.25-1
libcryptsetup4               (>= 2:1.4.3) | 2:1.7.0-2
libdbus-1-3                    (>= 1.1.1) | 1.10.8-1
libkmod2                          (>= 5~) | 22-1.1
libpam0g                    (>= 0.99.7.1) | 1.1.8-3.2
libselinux1                    (>= 2.1.9) | 2.5-3
libsystemd-journal0             (= 208-8) | 215-17
libudev1                         (>= 189) | 230-1
libwrap0                      (>= 7.6-4~) | 7.6.q-25
libsystemd-login0               (= 208-8) | 215-17
util-linux                  (>= 2.19.1-2) | 2.28-5
initscripts             (>= 2.88dsf-53.2) | 2.88dsf-59.4
sysv-rc                                   | 2.88dsf-59.4
udev                                      | 230-1
acl                                       | 2.2.52-3
adduser                                   | 3.114
libcap2-bin                               | 1:2.25-1


Package Status      (Version) | Installed
=============================-+-===========
udev                          | 230-1


Recommends          (Version) | Installed
=============================-+-===========
libpam-systemd                | 230-1


Suggests        (Version) | Installed
=========================-+-===========
systemd-ui                | 3-4



--- Output from package bug script ---