Hi all,
I'm experiencing a slow login to KDE on any otherwise very fast desktop system. It happens on a new install of Wily with a new user profile.
Looking in the syslog I'm seeing
I see a delay of about 20 seconds after successfully starting backlighthelper. Looking at the log I've got no idea what might be causing this.
Things I've tried: Disabled screen dimming in power saving settings (because I saw backlighthelper near the delay), changing graphics drivers from nvidia binary blob to noveau (I'm using a GTX 970), purging akonadi and telepathy, logging in to another newly created user profile (same delay).
Does anyone here have ideas where to look further? I'm all out of ideas
Thanks in advance!
I'm experiencing a slow login to KDE on any otherwise very fast desktop system. It happens on a new install of Wily with a new user profile.
Looking in the syslog I'm seeing
12/17/15 11:10:37 AM localhostname systemd[1] Started User Manager for UID 1000.
12/17/15 11:10:38 AM localhostname sddm[1208] Checking for pam module
12/17/15 11:10:38 AM localhostname sddm[1208] Got pam-login
12/17/15 11:10:38 AM localhostname sddm[1208] kwalletd: Waiting for hash on 17-
12/17/15 11:10:38 AM localhostname sddm[1208] kwalletd: waitingForEnvironment on: 20
12/17/15 11:10:38 AM localhostname sddm[1208] kwalletd: client connected
12/17/15 11:10:38 AM localhostname sddm[1208] kwalletd: client disconnected
12/17/15 11:10:39 AM localhostname NetworkManager[1090] <info> WiFi hardware radio set disabled
12/17/15 11:10:39 AM localhostname NetworkManager[1090] <info> WWAN hardware radio set disabled
12/17/15 11:10:43 AM localhostname dbus[1103] [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
12/17/15 11:10:43 AM localhostname dbus[1103] [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
12/17/15 11:11:02 AM localhostname dbus[1103] [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
12/17/15 11:11:02 AM localhostname systemd[1] Starting RealtimeKit Scheduling Policy Service...
12/17/15 11:11:02 AM localhostname dbus[1103] [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
12/17/15 11:11:02 AM localhostname systemd[1] Started RealtimeKit Scheduling Policy Service.
12/17/15 11:11:02 AM localhostname rtkit-daemon[1710] Successfully called chroot.
12/17/15 11:11:02 AM localhostname rtkit-daemon[1710] Successfully dropped privileges.
12/17/15 11:11:02 AM localhostname rtkit-daemon[1710] Successfully limited resources.
12/17/15 11:11:02 AM localhostname rtkit-daemon[1710] Running.
12/17/15 11:11:02 AM localhostname rtkit-daemon[1710] Watchdog thread running.
12/17/15 11:11:02 AM localhostname rtkit-daemon[1710] Canary thread running.
12/17/15 11:11:02 AM localhostname rtkit-daemon[1710] Successfully made thread 1709 of process 1709 (n/a) owned by '1000' high priority at nice level -11.
12/17/15 11:11:02 AM localhostname rtkit-daemon[1710] Supervising 1 threads of 1 processes of 1 users.
12/17/15 11:10:38 AM localhostname sddm[1208] Checking for pam module
12/17/15 11:10:38 AM localhostname sddm[1208] Got pam-login
12/17/15 11:10:38 AM localhostname sddm[1208] kwalletd: Waiting for hash on 17-
12/17/15 11:10:38 AM localhostname sddm[1208] kwalletd: waitingForEnvironment on: 20
12/17/15 11:10:38 AM localhostname sddm[1208] kwalletd: client connected
12/17/15 11:10:38 AM localhostname sddm[1208] kwalletd: client disconnected
12/17/15 11:10:39 AM localhostname NetworkManager[1090] <info> WiFi hardware radio set disabled
12/17/15 11:10:39 AM localhostname NetworkManager[1090] <info> WWAN hardware radio set disabled
12/17/15 11:10:43 AM localhostname dbus[1103] [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
12/17/15 11:10:43 AM localhostname dbus[1103] [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
12/17/15 11:11:02 AM localhostname dbus[1103] [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
12/17/15 11:11:02 AM localhostname systemd[1] Starting RealtimeKit Scheduling Policy Service...
12/17/15 11:11:02 AM localhostname dbus[1103] [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
12/17/15 11:11:02 AM localhostname systemd[1] Started RealtimeKit Scheduling Policy Service.
12/17/15 11:11:02 AM localhostname rtkit-daemon[1710] Successfully called chroot.
12/17/15 11:11:02 AM localhostname rtkit-daemon[1710] Successfully dropped privileges.
12/17/15 11:11:02 AM localhostname rtkit-daemon[1710] Successfully limited resources.
12/17/15 11:11:02 AM localhostname rtkit-daemon[1710] Running.
12/17/15 11:11:02 AM localhostname rtkit-daemon[1710] Watchdog thread running.
12/17/15 11:11:02 AM localhostname rtkit-daemon[1710] Canary thread running.
12/17/15 11:11:02 AM localhostname rtkit-daemon[1710] Successfully made thread 1709 of process 1709 (n/a) owned by '1000' high priority at nice level -11.
12/17/15 11:11:02 AM localhostname rtkit-daemon[1710] Supervising 1 threads of 1 processes of 1 users.
Things I've tried: Disabled screen dimming in power saving settings (because I saw backlighthelper near the delay), changing graphics drivers from nvidia binary blob to noveau (I'm using a GTX 970), purging akonadi and telepathy, logging in to another newly created user profile (same delay).
Does anyone here have ideas where to look further? I'm all out of ideas
Thanks in advance!
Comment