| View previous topic :: View next topic |
| Author |
Message |
amasidlover
Apprentice
Joined: 16 Jun 2002
Posts: 293
Location: Manchester, UK
|
 Posted: Thu May 15, 2014 3:45 pm Post subject: gdm and now gnome-shell won't start - may be systemd-logind |
 |
|
I updated to gnome 3.8 when it went stable and had a working system for a while. A couple of weeks ago I updated to Gnome 3.10 (as part of a world update).
Initially I couldn't get gdm to load, it appeared to be related to systemd-logind not loading, eventually I gave up and installed slim and was able to log in and carry on working.
I have now rebooted the machine and I get a grey screen with 'Something has gone wrong'...
I don't know if/where gnome 3 is debugging or logging to there are a few messages in /var/log/messages and nothing in .xsession-errors
Since installing systemd /var/log/messages is constantly filled with various messages; I don't know which are relevant to this issue so below are the highlights:
| Code: |
May 15 16:13:06 lamech slim: pam_unix(slim:session): session opened for user alex by alex(uid=0)
May 15 16:13:31 lamech slim: pam_systemd(slim:session): Failed to create session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 15 16:13:31 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
May 15 16:13:31 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
May 15 16:13:31 lamech systemd-logind[20707]: Failed to start unit user-1000.slice: Activation of org.freedesktop.systemd1 timed out
May 15 16:13:31 lamech systemd-logind[20707]: Failed to start user slice: Activation of org.freedesktop.systemd1 timed out
May 15 16:13:32 lamech slim: pam_ck_connector(slim:session): nox11 mode, ignoring PAM_TTY :0.0
May 15 16:13:32 lamech slim[20675]: /usr/bin/xauth: file /home/alex/.Xauthority does not exist
May 15 16:13:32 lamech dbus-daemon[17669]: missing action
May 15 16:13:48 lamech dnsmasq-dhcp[17674]: DHCPREQUEST(eth0) 192.168.15.34 00:08:5d:12:65:40
May 15 16:13:48 lamech dnsmasq-dhcp[17674]: DHCPACK(eth0) 192.168.15.34 00:08:5d:12:65:40 53i00085D126540
May 15 16:13:57 lamech systemd-logind[20707]: Failed to start unit user@1000.service: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 15 16:13:57 lamech systemd-logind[20707]: Failed to start user service: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 15 16:13:57 lamech systemd-logind[20707]: Assertion 's->user->slice' failed at /var/tmp/portage/sys-apps/systemd-208-r2/work/systemd-208/src/login/logind-session.c:502, function session_start_scope(). Aborting.
May 15 16:13:57 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
May 15 16:13:57 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
May 15 16:13:57 lamech gnome-session[20740]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
May 15 16:13:57 lamech gnome-session[20740]: gnome-session[20740]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
May 15 16:13:57 lamech gnome-session[20740]: gnome-session[20740]: WARNING: Could not parse desktop file gdu-notification-daemon.desktop or it references a not found TryExec binary
May 15 16:13:57 lamech gnome-session[20740]: WARNING: Could not parse desktop file gdu-notification-daemon.desktop or it references a not found TryExec binary
May 15 16:13:57 lamech gnome-session[20740]: WARNING: Could not parse desktop file gnome-do.desktop or it references a not found TryExec binary
May 15 16:13:57 lamech gnome-session[20740]: gnome-session[20740]: WARNING: Could not parse desktop file gnome-do.desktop or it references a not found TryExec binary
May 15 16:13:57 lamech gnome-session[20740]: GNOME_KEYRING_CONTROL=/home/alex/.cache/keyring-rM5ua5
May 15 16:13:57 lamech gnome-session[20740]: GNOME_KEYRING_CONTROL=/home/alex/.cache/keyring-rM5ua5
May 15 16:13:57 lamech gnome-session[20740]: GNOME_KEYRING_CONTROL=/home/alex/.cache/keyring-rM5ua5
May 15 16:13:57 lamech gnome-session[20740]: GPG_AGENT_INFO=/home/alex/.cache/keyring-rM5ua5/gpg:0:1
May 15 16:13:57 lamech gnome-session[20740]: SSH_AUTH_SOCK=/home/alex/.cache/keyring-rM5ua5/ssh
May 15 16:13:57 lamech gnome-session[20740]: GNOME_KEYRING_CONTROL=/home/alex/.cache/keyring-rM5ua5
May 15 16:13:57 lamech gnome-session[20740]: GPG_AGENT_INFO=/home/alex/.cache/keyring-rM5ua5/gpg:0:1
May 15 16:13:57 lamech pulseaudio[20781]: Stale PID file, overwriting.
May 15 16:13:57 lamech systemd[1]: systemd-logind.service: main process exited, code=killed, status=6/ABRT
May 15 16:13:57 lamech systemd[1]: Failed to start Login Service.
May 15 16:13:57 lamech systemd[1]: Unit systemd-logind.service entered failed state.
May 15 16:13:57 lamech systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
May 15 16:13:57 lamech kernel: 7:3:1: cannot get freq at ep 0x84
May 15 16:13:57 lamech systemd[1]: Stopping Login Service...
May 15 16:13:57 lamech systemd[1]: Starting Login Service...
May 15 16:13:57 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
May 15 16:13:57 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
May 15 16:13:57 lamech kernel: 7:3:1: cannot get freq at ep 0x84
May 15 16:13:57 lamech kernel: 7:3:1: cannot get freq at ep 0x84
May 15 16:13:57 lamech kernel: 7:3:1: cannot get freq at ep 0x84
May 15 16:13:57 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.bluez' unit='dbus-org.bluez.service'
May 15 16:13:57 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.bluez' unit='dbus-org.bluez.service'
May 15 16:14:22 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
May 15 16:14:22 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
May 15 16:14:22 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
May 15 16:14:22 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
May 15 16:14:22 lamech systemd-logind[20785]: Failed to enable subscription: Activation of org.freedesktop.systemd1 timed out
May 15 16:14:22 lamech systemd-logind[20785]: Watching system buttons on /dev/input/event5 (Power Button)
May 15 16:14:22 lamech systemd-logind[20785]: Watching system buttons on /dev/input/event4 (Power Button)
May 15 16:14:22 lamech systemd-logind[20785]: New seat seat0.
May 15 16:14:22 lamech gnome-session[20740]: (gnome-settings-daemon:20767): media-keys-plugin-WARNING **: Unable to inhibit keypresses: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Operation not permitted
May 15 16:14:22 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.ColorManager' unit='colord.service'
May 15 16:14:22 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.ColorManager' unit='colord.service'
May 15 16:14:22 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.UDisks2' unit='udisks2.service'
May 15 16:14:22 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.UDisks2' unit='udisks2.service'
May 15 16:14:22 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
May 15 16:14:22 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
May 15 16:14:22 lamech slim[20675]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 15 16:14:22 lamech slim[20675]: > Warning: Compat map for group 2 redefined
May 15 16:14:22 lamech slim[20675]: > Using new definition
May 15 16:14:22 lamech slim[20675]: > Warning: Compat map for group 3 redefined
May 15 16:14:22 lamech slim[20675]: > Using new definition
May 15 16:14:22 lamech slim[20675]: > Warning: Compat map for group 4 redefined
May 15 16:14:22 lamech slim[20675]: > Using new definition
May 15 16:14:22 lamech slim[20675]: Errors from xkbcomp are not fatal to the X server
May 15 16:14:22 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
May 15 16:14:22 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
May 15 16:14:22 lamech pulseaudio[20781]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 15 16:14:22 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.bluez': timed out
May 15 16:14:22 lamech dbus[17669]: [system] Failed to activate service 'org.bluez': timed out
May 15 16:14:47 lamech gnome-session[20740]: (gnome-settings-daemon:20767): color-plugin-WARNING **: failed to connect to colord: Error calling StartServiceByName for org.freedesktop.ColorManager: Timeout was reached
May 15 16:14:47 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.ColorManager': timed out
May 15 16:14:47 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
May 15 16:14:47 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.UDisks2': timed out
May 15 16:14:47 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.ColorManager': timed out
May 15 16:14:47 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
May 15 16:14:47 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.UDisks2': timed out
May 15 16:14:47 lamech gnome-session[20740]: ** (gnome-settings-daemon:20767): WARNING **: Error initializing udisks client: Error calling StartServiceByName for org.freedesktop.UDisks2: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.UDisks2 timed out (g-dbus-error-quark, 20)
May 15 16:14:47 lamech gnome-session[20740]: (gnome-settings-daemon:20767): GLib-GObject-WARNING **: invalid (NULL) pointer instance
May 15 16:14:47 lamech gnome-session[20740]: (gnome-settings-daemon:20767): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
May 15 16:14:47 lamech gnome-session[20740]: (gnome-settings-daemon:20767): GLib-GObject-WARNING **: invalid (NULL) pointer instance
May 15 16:14:47 lamech gnome-session[20740]: (gnome-settings-daemon:20767): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
May 15 16:14:47 lamech gnome-session[20740]: (gnome-settings-daemon:20767): GLib-GObject-WARNING **: invalid (NULL) pointer instance
May 15 16:14:47 lamech gnome-session[20740]: (gnome-settings-daemon:20767): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
May 15 16:14:47 lamech gnome-session[20740]: (gnome-settings-daemon:20767): GLib-GObject-WARNING **: invalid (NULL) pointer instance
May 15 16:14:47 lamech gnome-session[20740]: (gnome-settings-daemon:20767): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
May 15 16:14:47 lamech gnome-session[20740]: (gnome-settings-daemon:20767): GLib-GObject-WARNING **: invalid (NULL) pointer instance
May 15 16:14:47 lamech gnome-session[20740]: (gnome-settings-daemon:20767): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
May 15 16:14:47 lamech gnome-session[20740]: (gnome-settings-daemon:20767): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
May 15 16:14:47 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.locale1': timed out
May 15 16:14:47 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.locale1': timed out
May 15 16:14:47 lamech gnome-session[20740]: (gnome-settings-daemon:20767): keyboard-plugin-WARNING **: Failed to contact localed: Error calling StartServiceByName for org.freedesktop.locale1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.locale1 timed out
May 15 16:14:47 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
May 15 16:14:47 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
May 15 16:14:47 lamech slim[20675]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 15 16:14:47 lamech slim[20675]: > Warning: Compat map for group 2 redefined
May 15 16:14:47 lamech slim[20675]: > Using new definition
May 15 16:14:47 lamech slim[20675]: > Warning: Compat map for group 3 redefined
May 15 16:14:47 lamech slim[20675]: > Using new definition
May 15 16:14:47 lamech slim[20675]: > Warning: Compat map for group 4 redefined
May 15 16:14:47 lamech slim[20675]: > Using new definition
May 15 16:14:47 lamech slim[20675]: Errors from xkbcomp are not fatal to the X server
May 15 16:14:48 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
May 15 16:14:48 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
May 15 16:14:48 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
May 15 16:14:48 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
May 15 16:14:48 lamech goa[20861]: goa-daemon version 3.10.2 starting [main.c:117, main()]
May 15 16:15:13 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
May 15 16:15:13 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
May 15 16:15:13 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
May 15 16:15:13 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
May 15 16:15:13 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
May 15 16:15:13 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
May 15 16:15:13 lamech gnome-session[20740]: (gnome-settings-daemon:20767): libupower-glib-WARNING **: Couldn't enumerate devices: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 15 16:15:13 lamech gnome-session[20740]: (gnome-settings-daemon:20767): power-plugin-WARNING **: failed to get device list: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 15 16:15:13 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.Accounts': timed out
May 15 16:15:13 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.Accounts': timed out
May 15 16:15:13 lamech gnome-session[20740]: (gnome-shell:20806): AccountsService-WARNING **: Failed to create accounts proxy: Error calling StartServiceByName for org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.Accounts timed out
May 15 16:15:13 lamech gnome-session[20740]: Gjs-Message: JS LOG: Failed to register AuthenticationAgent
May 15 16:15:13 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.UDisks2' unit='udisks2.service'
May 15 16:15:13 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.UDisks2' unit='udisks2.service'
May 15 16:15:27 lamech systemd[1]: systemd-logind.service operation timed out. Terminating.
May 15 16:15:27 lamech systemd[1]: Failed to start Login Service.
May 15 16:15:27 lamech systemd[1]: Unit systemd-logind.service entered failed state.
May 15 16:15:27 lamech systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
May 15 16:15:27 lamech systemd[1]: Stopping Login Service...
May 15 16:15:27 lamech systemd[1]: Starting Login Service...
May 15 16:15:38 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
May 15 16:15:38 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
May 15 16:15:38 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
May 15 16:15:38 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
May 15 16:15:38 lamech systemd-logind[20879]: Failed to enable subscription: Activation of org.freedesktop.systemd1 timed out
May 15 16:15:38 lamech systemd-logind[20879]: Watching system buttons on /dev/input/event5 (Power Button)
May 15 16:15:38 lamech systemd-logind[20879]: Watching system buttons on /dev/input/event4 (Power Button)
May 15 16:15:38 lamech systemd-logind[20879]: New seat seat0.
May 15 16:15:38 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.UDisks2': timed out
May 15 16:15:38 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.UDisks2': timed out
May 15 16:15:38 lamech gnome-session[20740]: (gnome-shell:20806): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
May 15 16:15:38 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.UDisks' unit='udisks.service'
May 15 16:15:38 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.UDisks' unit='udisks.service'
May 15 16:15:52 lamech gnome-session[20740]: gnome-session[20740]: WARNING: Application 'gnome-shell.desktop' failed to register before timeout
May 15 16:15:52 lamech gnome-session[20740]: WARNING: Application 'gnome-shell.desktop' failed to register before timeout
May 15 16:15:52 lamech gnome-session[20740]: Unrecoverable failure in required component gnome-shell.desktop
May 15 16:15:52 lamech gnome-session[20740]: Entering running state
May 15 16:15:52 lamech gnome-session[20740]: system-config-printer-applet: failed to start NewPrinterNotification service
May 15 16:15:52 lamech gnome-session[20740]: system-config-printer-applet: failed to start PrinterDriversInstaller service: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.205" is not allowed to own the service "com.redhat.PrinterDriversInstaller" due to security policies in the configuration file
May 15 16:15:52 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service'
May 15 16:15:52 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service'
May 15 16:15:52 lamech gnome-session[20740]: (tracker-miner-fs:20900): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
May 15 16:15:52 lamech gnome-session[20740]: Failed to play sound: File or data not found
May 15 16:15:53 lamech gnome-keyring-daemon[20727]: keyring alias directory: /home/alex/.local/share/keyrings
May 15 16:16:03 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
May 15 16:16:03 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
May 15 16:16:03 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.UDisks': timed out
May 15 16:16:03 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.UDisks': timed out
May 15 16:16:03 lamech gnome-session[20740]: Error creating proxy: Error calling StartServiceByName for org.gtk.Private.GduVolumeMonitor: Timeout was reached (g-io-error-quark, 24)
May 15 16:16:03 lamech gnome-session[20740]: Gjs-Message: JS LOG: GNOME Shell started at Thu May 15 2014 16:16:03 GMT+0100 (BST)
May 15 16:16:04 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.bluez' unit='dbus-org.bluez.service'
May 15 16:16:04 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.bluez' unit='dbus-org.bluez.service'
May 15 16:16:04 lamech gnome-keyring-daemon[20727]: certReference certReference: decoded tag did not match expected
May 15 16:16:04 lamech gnome-keyring-daemon[20727]: certReference certReference: decoded tag did not match expected
May 15 16:16:04 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
May 15 16:16:04 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
May 15 16:16:17 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.NetworkManager': timed out
May 15 16:16:17 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.NetworkManager': timed out
May 15 16:16:17 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service'
May 15 16:16:17 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
May 15 16:16:17 lamech dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.ColorManager' unit='colord.service'
May 15 16:16:17 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service'
May 15 16:16:17 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
May 15 16:16:17 lamech dbus-daemon[17669]: dbus[17669]: [system] Activating systemd to hand-off: service name='org.freedesktop.ColorManager' unit='colord.service'
May 15 16:16:17 lamech gnome-session[20740]: Window manager warning: Log level 16: Could not initialize NMClient /org/freedesktop/NetworkManager: Activation of org.freedesktop.NetworkManager timed out
May 15 16:16:17 lamech gnome-session[20740]: ** (nm-applet:20896): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Activation of org.freedesktop.NetworkManager timed out
May 15 16:16:17 lamech gnome-session[20740]: (gnome-settings-daemon:20767): power-plugin-WARNING **: Unable to inhibit suspend: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Operation not permitted
May 15 16:16:17 lamech gnome-session[20740]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1200064 (Buddy List)
May 15 16:16:17 lamech gnome-session[20740]: Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
May 15 16:16:17 lamech gnome-session[20740]: Error creating proxy: Error calling StartServiceByName for org.gtk.Private.GduVolumeMonitor: Timeout was reached (g-io-error-quark, 24)
May 15 16:16:17 lamech slim[20675]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 15 16:16:17 lamech slim[20675]: > Warning: Compat map for group 2 redefined
May 15 16:16:17 lamech slim[20675]: > Using new definition
May 15 16:16:17 lamech slim[20675]: > Warning: Compat map for group 3 redefined
May 15 16:16:17 lamech slim[20675]: > Using new definition
May 15 16:16:17 lamech slim[20675]: > Warning: Compat map for group 4 redefined
May 15 16:16:17 lamech slim[20675]: > Using new definition
May 15 16:16:17 lamech slim[20675]: Errors from xkbcomp are not fatal to the X server
May 15 16:16:18 lamech gnome-session[20740]: **
May 15 16:16:18 lamech gnome-session[20740]: AccountsService:ERROR:act-user-manager.c:2517:load_users: assertion failed: (manager->priv->accounts_proxy != NULL)
May 15 16:16:18 lamech gnome-session[20740]: gnome-session[20740]: WARNING: Application 'gnome-shell.desktop' killed by signal 6
May 15 16:16:18 lamech gnome-session[20740]: WARNING: Application 'gnome-shell.desktop' killed by signal 6
May 15 16:16:18 lamech gnome-keyring-daemon[20727]: couldn't prompt for password: The operation was cancelled
May 15 16:16:18 lamech slim[20675]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 15 16:16:18 lamech slim[20675]: > Warning: Compat map for group 2 redefined
May 15 16:16:18 lamech slim[20675]: > Using new definition
May 15 16:16:18 lamech slim[20675]: > Warning: Compat map for group 3 redefined
May 15 16:16:18 lamech slim[20675]: > Using new definition
May 15 16:16:18 lamech slim[20675]: > Warning: Compat map for group 4 redefined
May 15 16:16:18 lamech slim[20675]: > Using new definition
May 15 16:16:18 lamech slim[20675]: Errors from xkbcomp are not fatal to the X server
May 15 16:16:26 lamech sshd[17906]: SSH: Server;Ltype: Version;Remote: 192.168.6.53-51546;Protocol: 2.0;Client: check_ssh_1.4.16
May 15 16:16:26 lamech sshd[17906]: Connection closed by 192.168.6.53 [preauth]
May 15 16:16:29 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.bluez': timed out
May 15 16:16:29 lamech dbus[17669]: [system] Failed to activate service 'org.bluez': timed out
May 15 16:16:29 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
May 15 16:16:29 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
May 15 16:16:29 lamech dbus-daemon[17669]: dbus[17669]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
May 15 16:16:29 lamech dbus[17669]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
|
I initially thought it was DBUS, but my searches suggest its actually something to do with consolekit, polkit or systemd-logind - I no longer know which I'm supposed to have installed and have a system with all 3 on - I believe systemd-logind is supposed to replace consolekit (and polkit?) but that doesn't seem to start so that may be part of the problem...
Help!!! Please!!!
_________________
http://www.axiomtech.co.uk
http://www.zednax.com |
|
| Back to top |
|
 |
amasidlover
Apprentice
Joined: 16 Jun 2002
Posts: 293
Location: Manchester, UK
|
| Posted: Sun May 18, 2014 3:11 pm Post subject: |
|
|
I eventually gave up and did emerge -e world over the weekend when I didn't need the machine with USE flags systemd, policykit and -consolekit and I have Gnome back again.
First time in years of using Gentoo (since v1.2, I think) I've had to do a complete rebuild...
_________________
http://www.axiomtech.co.uk
http://www.zednax.com |
|
| Back to top |
|
|
amasidlover
Apprentice
Joined: 16 Jun 2002
Posts: 293
Location: Manchester, UK
|
| Posted: Sun Aug 31, 2014 10:58 am Post subject: |
|
|
Bang!! My system is dead again...
I'm pretty sure that I caused it by running a binhost set-up of 2 desktop machines here, I suspect one of them has a incorrect USE flag somewhere, but looks like I'm in to a complete rebuild again.
As far as I can tell the critical issues as reported by journalctl are:
| Code: |
Aug 31 10:39:26 lamech dbus[17803]: [system] Activating systemd to hand-off: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Aug 31 10:39:31 lamech rpc.statd[17855]: sm-notify: getaddrinfo(3): Name or service not known
Aug 31 10:39:31 lamech rpc.statd[17855]: sm-notify: DNS resolution of shem.o.zednax.com failed; retrying later
Aug 31 10:39:31 lamech rpc.statd[17855]: sm-notify: Added host shem.o.zednax.com to notify list
Aug 31 10:39:31 lamech rpc.statd[17855]: sm-notify: Host shem.o.zednax.com due in 120 seconds
Aug 31 10:39:46 lamech systemd-logind[18210]: Failed to enable subscription: Connection timed out
Aug 31 10:39:46 lamech systemd-logind[18210]: Failed to fully start up daemon: Connection timed out
Aug 31 10:39:46 lamech systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Aug 31 10:39:46 lamech dbus[17803]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Aug 31 10:39:46 lamech systemd[1]: Failed to start Login Service.
Aug 31 10:39:46 lamech systemd[1]: Unit systemd-logind.service entered failed state.
Aug 31 10:39:46 lamech systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
Aug 31 10:39:46 lamech systemd[1]: Stopping Login Service...
Aug 31 10:39:46 lamech systemd[1]: Starting Login Service...
Aug 31 10:39:51 lamech dbus[17803]: [system] Failed to activate service 'org.freedesktop.login1': timed out
|
I think the rpc.statd errors are co-incidental, the remaining errors repeatedly appear...
Frustratingly the output is verbose yet utterly meaningless... "systemd-logind[18210]: Failed to enable subscription: Connection timed out" - subscription to what? connection to what? at least if it told me that I could check whether whatever it is trying to subscribe/connect to is working!
_________________
http://www.axiomtech.co.uk
http://www.zednax.com |
|
| Back to top |
|
|
amasidlover
Apprentice
Joined: 16 Jun 2002
Posts: 293
Location: Manchester, UK
|
| Posted: Sun Oct 12, 2014 3:14 pm Post subject: |
|
|
Last time I managed to fix it with emerge -1 systemd (I think) not sure why I didn't update this thread.
However, yet again my system is dead thanks to systemd-logind... Sane logs as last time...
This is really annoying me now.
Help, please, somebody!!!
_________________
http://www.axiomtech.co.uk
http://www.zednax.com |
|
| Back to top |
|
|
amasidlover
Apprentice
Joined: 16 Jun 2002
Posts: 293
Location: Manchester, UK
|
| Posted: Mon Oct 13, 2014 8:08 am Post subject: |
|
|
Emerge -e system failed to fix it.
| Code: |
lamech ~ # /usr/lib64/systemd/systemd-logind
Failed to enable subscription: Activation of org.freedesktop.systemd1 timed out
Failed to fully start up daemon: Connection timed out
|
Strace (with much snipping shows):
| Code: |
connect(9, {sa_family=AF_LOCAL, sun_path="/var/run/dbus/system_bus_socket"}, 33) = 0
getsockopt(9, SOL_SOCKET, SO_PEERCRED, {pid=1, uid=0, gid=0}, [12]) = 0
...
recvmsg(9, 0x7fffde141440, MSG_DONTWAIT|MSG_NOSIGNAL|MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable)
ppoll([{fd=9, events=POLLIN}], 1, {24, 999977000}, NULL, 8) = 1 ([{fd=9, revents=POLLIN}], left {24, 999976422})
... |
The last message repeats several times and then the errors followed by exit appear.
My issues seem similar to this thread.
| Code: |
lamech ~ # systemctl status dbus.service
● dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib64/systemd/system/dbus.service; static)
Active: active (running) since Mon 2014-10-13 08:37:36 BST; 13min ago
Docs: man:dbus-daemon(1)
Main PID: 2845 (dbus-daemon)
CGroup: /system.slice/dbus.service
├─2845 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
└─3209 /usr/sbin/console-kit-daemon --no-daemon
Oct 13 08:48:38 lamech dbus[2845]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Oct 13 08:49:03 lamech dbus[2845]: [system] Activating systemd to hand-off: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Oct 13 08:49:03 lamech dbus[2845]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Oct 13 08:49:28 lamech dbus[2845]: [system] Failed to activate service 'org.freedesktop.login1': timed out
Oct 13 08:49:28 lamech dbus[2845]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Oct 13 08:49:53 lamech dbus[2845]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Oct 13 08:50:18 lamech dbus[2845]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Oct 13 08:50:33 lamech dbus[2845]: [system] Activating systemd to hand-off: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Oct 13 08:50:44 lamech dbus[2845]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Oct 13 08:50:58 lamech dbus[2845]: [system] Failed to activate service 'org.freedesktop.login1': timed out
|
Polkit says...
| Code: |
lamech ~ # systemctl status polkit
● polkit.service - Authorization Manager
Loaded: loaded (/usr/lib64/systemd/system/polkit.service; static)
Active: inactive (dead)
Docs: man:polkit(8)
|
After manually starting it I eventually get:
| Code: |
lamech ~ # systemctl status polkit
● polkit.service - Authorization Manager
Loaded: loaded (/usr/lib64/systemd/system/polkit.service; static)
Active: activating (start) since Mon 2014-10-13 08:55:43 BST; 6s ago
Docs: man:polkit(8)
Main PID: 3743 (polkitd)
CGroup: /system.slice/polkit.service
└─3743 /usr/lib/polkit-1/polkitd --no-debug
Oct 13 08:55:45 lamech polkitd[3743]: Started polkitd version 0.112
Oct 13 08:55:46 lamech polkitd[3743]: Loading rules from directory /etc/polkit-1/rules.d
Oct 13 08:55:46 lamech polkitd[3743]: Loading rules from directory /usr/share/polkit-1/rules.d
Oct 13 08:55:46 lamech polkitd[3743]: Finished loading, compiling and executing 4 rules
Oct 13 08:55:46 lamech polkitd[3743]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
|
I then started systemd-logind again and journalctl showed:
| Code: |
Oct 13 08:57:24 lamech dbus[2845]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Oct 13 08:57:24 lamech systemd[1]: Failed to start Login Service.
...
Oct 13 08:57:39 lamech dbus[2845]: [system] Failed to activate service 'org.freedesktop.login1': timed out
Oct 13 08:57:39 lamech gdm[3784]: GdmLocalDisplayFactory: Failed to issue method call: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.login1 timed o
|
So I wondered if systemd itself hadn't started properly due to polkit not starting properly (!!) and did:
| Code: |
lamech ~ # systemctl daemon-reload
|
That resulted in
| Code: |
lamech ~ # journalctl -xn
-- Logs begin at Wed 2014-04-30 15:40:44 BST, end at Mon 2014-10-13 09:03:54 BST. --
Oct 13 09:03:44 lamech systemd[1]: Looping too fast. Throttling execution a little.
Oct 13 09:03:45 lamech systemd[1]: Looping too fast. Throttling execution a little.
Oct 13 09:03:46 lamech systemd[1]: Looping too fast. Throttling execution a little.
Oct 13 09:03:48 lamech systemd[1]: Looping too fast. Throttling execution a little.
Oct 13 09:03:49 lamech systemd[1]: Looping too fast. Throttling execution a little.
Oct 13 09:03:50 lamech systemd[1]: Looping too fast. Throttling execution a little.
Oct 13 09:03:51 lamech systemd[1]: Looping too fast. Throttling execution a little.
Oct 13 09:03:52 lamech systemd[1]: Looping too fast. Throttling execution a little.
Oct 13 09:03:53 lamech systemd[1]: Looping too fast. Throttling execution a little.
|
However, I then went in to top and killed systemd (PID 1) !! and then the remaining services started starting properly...
stop and start of gdm and... I'm back up and running (I think...)
Someone remind me how this systemd thing is so much better than OpenRC...
_________________
http://www.axiomtech.co.uk
http://www.zednax.com |
|
| Back to top |
|
|
amasidlover
Apprentice
Joined: 16 Jun 2002
Posts: 293
Location: Manchester, UK
|
| Posted: Thu Aug 13, 2015 12:57 pm Post subject: |
|
|
I'm still getting this issue on both of our office machines...
I have to restart polkit, daemon-reload systemd, kill systemd before gdm starts - although its only 'occasional' ...
_________________
http://www.axiomtech.co.uk
http://www.zednax.com |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
