Attachment 901128 Details for Bug 1101312 – log messages from journalctl for a crashed gnome-session

log messages from journalctl for a crashed gnome-session

failed.txt (text/plain), 9.23 KB, created by Michal Jaegermann on 2014-05-31 19:29:12 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Michal Jaegermann

Created: 2014-05-31 19:29:12 UTC

Size: 9.23 KB

patch

obsolete

>May 31 13:03:11 ... colord[5187]: Profile added: icc-1586a685031fd11aaf179afc88ad0c00
>May 31 13:03:11 ... colord[5187]: Profile added: icc-35b8494d37d8d233acc53f12d988f307
>May 31 13:03:11 ... gnome-session[5131]: (gnome-settings-daemon:5143): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
>May 31 13:03:12 ... colord[5187]: Automatic metadata add icc-35b8494d37d8d233acc53f12d988f307 to xrandr-Samsung Electric Company-SyncMaster-HCHY305114
>May 31 13:03:12 ... colord[5187]: Device added: xrandr-Samsung Electric Company-SyncMaster-HCHY305114
>May 31 13:03:12 ... gnome-session[5131]: Window manager warning: Log level 16: Couldn't register with accessibility bus: 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 31 13:03:12 ... gnome-session[5131]: Window manager warning: Log level 6: AT-SPI: COuldn't connect to accessibility bus. Is at-spi-bus-launcher running?
>May 31 13:03:12 ... kernel: traps: gnome-shell[5186] trap int3 ip:3cda8504e9 sp:7fff04d5de20 error:0
>May 31 13:03:12 ... gnome-session[5131]: gnome-session[5131]: WARNING: Application 'gnome-shell.desktop' killed by signal 5
>May 31 13:03:12 ... gnome-session[5131]: WARNING: Application 'gnome-shell.desktop' killed by signal 5
>May 31 13:03:12 ... gnome-session[5131]: (gnome-settings-daemon:5143): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
>May 31 13:03:12 ... gnome-session[5131]: ** (gnome-shell:5238): WARNING **: Couldn't register with accessibility bus: 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 31 13:03:13 ... gnome-session[5131]: Window manager warning: Log level 16: Couldn't register with accessibility bus: 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 31 13:03:13 ... gnome-session[5131]: Window manager warning: Log level 6: AT-SPI: COuldn't connect to accessibility bus. Is at-spi-bus-launcher running?
>May 31 13:03:13 ... kernel: traps: gnome-shell[5238] trap int3 ip:3cda8504e9 sp:7fff6d461d30 error:0
>May 31 13:03:13 ... gnome-session[5131]: gnome-session[5131]: WARNING: Application 'gnome-shell.desktop' killed by signal 5
>May 31 13:03:13 ... gnome-session[5131]: WARNING: Application 'gnome-shell.desktop' killed by signal 5
>May 31 13:03:13 ... gnome-session[5131]: gnome-session[5131]: WARNING: App 'gnome-shell.desktop' respawning too quickly
>May 31 13:03:13 ... gnome-session[5131]: WARNING: App 'gnome-shell.desktop' respawning too quickly
>May 31 13:03:13 ... gnome-session[5131]: Unrecoverable failure in required component gnome-shell.desktop
>May 31 13:03:13 ... gnome-session[5131]: ** (gnome-session-failed:5250): WARNING **: Couldn't register with accessibility bus: 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 31 13:03:13 ... gnome-session[5131]: (gnome-settings-daemon:5143): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
>May 31 13:03:14 ... gnome-session[5131]: ** (nautilus:5252): WARNING **: Couldn't register with accessibility bus: 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 31 13:03:14 ... gnome-session[5131]: ** (nm-applet:5251): WARNING **: Couldn't register with accessibility bus: 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 31 13:03:14 ... gnome-session[5131]: Entering running state
>May 31 13:03:14 ... gnome-session[5131]: ** (gnome-terminal:5259): WARNING **: Couldn't register with accessibility bus: 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 31 13:03:14 ... gnome-session[5131]: ** (canberra-gtk-play:5264): WARNING **: Couldn't register with accessibility bus: 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 31 13:03:14 ... gnome-session[5131]: ** (krb5-auth-dialog:5267): WARNING **: Couldn't register with accessibility bus: 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 31 13:03:14 ... gnome-session[5131]: ** (gnome-screensaver:5275): WARNING **: Couldn't register with accessibility bus: 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 31 13:03:14 ... gnome-session[5131]: ** (abrt:5256): WARNING **: Couldn't register with accessibility bus: 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 31 13:03:14 ... pcscd[5201]: 03386759 winscard.c:240:SCardConnect() Reader E-Gate 0 0 Not Found
>May 31 13:03:14 ... pcscd[5201]: 00001642 winscard.c:240:SCardConnect() Reader E-Gate 0 0 Not Found
>May 31 13:03:14 ... pcscd[5201]: 00000758 winscard.c:240:SCardConnect() Reader E-Gate 0 0 Not Found
>May 31 13:03:15 ... gnome-session[5131]: Initializing nautilus-open-terminal extension
>May 31 13:03:15 ... gnome-session[5131]: Failed to play sound: File or data not found
>May 31 13:03:15 ... gnome-session[5131]: (krb5-auth-dialog:5267): libnotify-WARNING **: Failed to connect to proxy
>May 31 13:03:15 ... gnome-session[5131]: ** (krb5-auth-dialog:5267): WARNING **: Failed to read server caps
>May 31 13:03:15 ... dbus-daemon[736]: dbus[736]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
>May 31 13:03:15 ... dbus[736]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
>May 31 13:03:15 ... dbus[736]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
>May 31 13:03:15 ... dbus-daemon[736]: dbus[736]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
>May 31 13:03:15 ... gnome-session[5131]: (nm-applet:5251): nm-applet-WARNING **: Error connecting to ModemManager: Error calling StartServiceByName for org.freedesktop.ModemManager1: GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
>May 31 13:03:16 ... gnome-session[5131]: (krb5-auth-dialog:5267): libnotify-WARNING **: Failed to connect to proxy
>May 31 13:03:16 ... gnome-session[5131]: ** (krb5-auth-dialog:5267): WARNING **: Failed to read server caps
>May 31 13:03:16 ... gnome-session[5131]: ** (nautilus:5252): WARNING **: Can not get _NET_WORKAREA
>May 31 13:03:16 ... gnome-session[5131]: ** (nautilus:5252): WARNING **: Can not determine workarea, guessing at layout
>May 31 13:03:17 ... gnome-session[5131]: (krb5-auth-dialog:5267): libnotify-WARNING **: Failed to connect to proxy
>May 31 13:03:17 ... gnome-session[5131]: ** (krb5-auth-dialog:5267): WARNING **: Failed to read server caps
>May 31 13:03:17 ... pcscd[5201]: 03016640 winscard.c:240:SCardConnect() Reader E-Gate 0 0 Not Found
>May 31 13:03:18 ... gnome-session[5131]: (krb5-auth-dialog:5267): libnotify-WARNING **: Failed to connect to proxy
>May 31 13:03:18 ... gnome-session[5131]: ** (krb5-auth-dialog:5267): WARNING **: Failed to read server caps
>May 31 13:03:19 ... gnome-session[5131]: (krb5-auth-dialog:5267): libnotify-WARNING **: Failed to connect to proxy
>May 31 13:03:19 ... gnome-session[5131]: ** (krb5-auth-dialog:5267): WARNING **: Failed to read server caps
>May 31 13:03:20 ... gnome-session[5131]: ** Message: No plugins to load
>May 31 13:03:20 ... gnome-session[5131]: ** (krb5-auth-dialog:5267): WARNING **: Unsupported cache type for 'KEYRING:persistent:400'
>May 31 13:03:20 ... gnome-session[5131]: ** (krb5-auth-dialog:5267): CRITICAL **: monitor_ccache: assertion 'ccache_name != NULL' failed
>May 31 13:03:20 ... gnome-session[5131]: (krb5-auth-dialog:5267): GLib-GIO-CRITICAL **: GApplication subclass 'KaApplet' failed to chain up on ::startup (from start of override function)

Actions: View

Attachments on bug 1101312: 901119 | 901120 | 901128