You are not logged in.

#1 2013-04-28 08:29:51

jrussell
Member
From: Cape Town, South Africa
Registered: 2012-08-16
Posts: 510

GDM 3.8 blank grey background after screensaver interupt

Hi, I think I have found a bug in GDM, If you interupt the animated fade out with a mouse movement, just before the screen fades to black, GDM will wake up again but only with a plan grey background, no login names to login to, but the calender and sound and power options are still on the top of the screen.

Any one else seeing this happen? This was on a fresh start of my laptop. fully up-to-date.

journalctl:

Apr 28 10:18:13 jason-laptop colord[177]: Device added: sysfs-OmniVision_Technologies__Inc._-2640-07.07.20.3-Laptop_Integrated_Webcam
Apr 28 10:18:13 jason-laptop colord[177]: Profile added: HP_PSC_1500_series-Gray..
Apr 28 10:18:13 jason-laptop colord[177]: Profile added: HP_PSC_1500_series-RGB..
Apr 28 10:18:13 jason-laptop colord[177]: (colord:177): Cd-WARNING **: failed to get session [pid 137]: Unknown error -2
Apr 28 10:18:13 jason-laptop colord[177]: Device added: cups-HP_PSC_1500_series
Apr 28 10:18:13 jason-laptop gdm[151]: Failed to give slave programs access to the display. Trying to proceed.
Apr 28 10:18:14 jason-laptop systemd-logind[142]: New session c1 of user gdm.
Apr 28 10:18:14 jason-laptop systemd-logind[142]: Linked /tmp/.X11-unix/X0 to /run/user/120/X11-display.
Apr 28 10:18:17 jason-laptop /usr/bin/dbus-launch[256]: gnome-session[256]: WARNING: Could not parse desktop file /usr/share/gdm/greeter/autostart/orca-autost
Apr 28 10:18:17 jason-laptop gnome-session[256]: WARNING: Could not parse desktop file /usr/share/gdm/greeter/autostart/orca-autostart.desktop or it reference
Apr 28 10:18:17 jason-laptop gnome-session[256]: WARNING: could not read /usr/share/gdm/greeter/autostart/orca-autostart.desktop
Apr 28 10:18:17 jason-laptop /usr/bin/dbus-launch[256]: gnome-session[256]: WARNING: could not read /usr/share/gdm/greeter/autostart/orca-autostart.desktop
Apr 28 10:18:18 jason-laptop dbus-daemon[143]: dbus[143]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Apr 28 10:18:18 jason-laptop dbus[143]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Apr 28 10:18:18 jason-laptop systemd[1]: Starting Daemon for power management...
Apr 28 10:18:18 jason-laptop dbus-daemon[143]: dbus[143]: [system] Successfully activated service 'org.freedesktop.UPower'
Apr 28 10:18:18 jason-laptop dbus[143]: [system] Successfully activated service 'org.freedesktop.UPower'
Apr 28 10:18:18 jason-laptop systemd[1]: Started Daemon for power management.
Apr 28 10:18:19 jason-laptop gnome-session[256]: Entering running state
Apr 28 10:18:19 jason-laptop colord[177]: Automatic metadata add icc-2927396d048bf9f6cf9bafb6cc5812bd to xrandr-cPATH
Apr 28 10:18:19 jason-laptop colord[177]: Device added: xrandr-cPATH
Apr 28 10:18:19 jason-laptop /usr/bin/dbus-launch[256]: (gnome-settings-daemon:276): Gvc-WARNING **: Failed to connect context: OK
Apr 28 10:18:19 jason-laptop dbus-daemon[143]: dbus[143]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.l
Apr 28 10:18:19 jason-laptop dbus[143]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Apr 28 10:18:19 jason-laptop dbus[143]: [system] Successfully activated service 'org.freedesktop.locale1'
Apr 28 10:18:20 jason-laptop colord[177]: Automatic metadata add icc-adce9e59cf896c1faca0224e3c21c8fd to xrandr-cPATH
Apr 28 10:18:20 jason-laptop colord[177]: Profile added: icc-adce9e59cf896c1faca0224e3c21c8fd
Apr 28 10:18:21 jason-laptop dbus-daemon[143]: dbus[143]: [system] Successfully activated service 'org.freedesktop.locale1'
Apr 28 10:18:19 jason-laptop systemd[1]: Starting Locale Service...
Apr 28 10:18:19 jason-laptop systemd[1]: Started Locale Service.
Apr 28 10:18:23 jason-laptop kernel: EXT4-fs (sda1): re-mounted. Opts: commit=0
Apr 28 10:18:27 jason-laptop /usr/bin/dbus-launch[256]: (gnome-shell:320): Gvc-WARNING **: Failed to connect context: OK
Apr 28 10:18:27 jason-laptop polkitd[181]: Registered Authentication Agent for unix-session:c1 (system bus name :1.23 [gnome-shell --mode=gdm], object path /o
Apr 28 10:18:27 jason-laptop /usr/bin/dbus-launch[256]: JS LOG: GNOME Shell started at Sun Apr 28 2013 10:18:27 GMT+0200 (SAST)
Apr 28 10:18:35 jason-laptop NetworkManager[136]: <info> Auto-activating connection 'Auto Russell Home'.
Apr 28 10:18:35 jason-laptop NetworkManager[136]: <info> Activation (wlan0) starting connection 'Auto Russell Home'
Apr 28 10:18:35 jason-laptop NetworkManager[136]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 28 10:18:35 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 28 10:18:35 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 28 10:18:35 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 28 10:18:35 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 28 10:18:35 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 28 10:18:35 jason-laptop NetworkManager[136]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 28 10:18:35 jason-laptop NetworkManager[136]: <info> Activation (wlan0/wireless): connection 'Auto Russell Home' requires no security.  No secrets needed.
Apr 28 10:18:35 jason-laptop NetworkManager[136]: <info> Config: added 'ssid' value 'Russell Home'
Apr 28 10:18:35 jason-laptop NetworkManager[136]: <info> Config: added 'scan_ssid' value '1'
Apr 28 10:18:35 jason-laptop NetworkManager[136]: <info> Config: added 'key_mgmt' value 'NONE'
Apr 28 10:18:35 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 28 10:18:35 jason-laptop NetworkManager[136]: <info> Config: set interface ap_scan to 1
Apr 28 10:18:35 jason-laptop NetworkManager[136]: <info> (wlan0): supplicant interface state: inactive -> scanning
Apr 28 10:18:36 jason-laptop kernel: wlan0: authenticate with 00:1c:10:08:b7:a5
Apr 28 10:18:36 jason-laptop kernel: wlan0: send auth to 00:1c:10:08:b7:a5 (try 1/3)
Apr 28 10:18:36 jason-laptop NetworkManager[136]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Apr 28 10:18:36 jason-laptop kernel: wlan0: send auth to 00:1c:10:08:b7:a5 (try 2/3)
Apr 28 10:18:36 jason-laptop kernel: wlan0: authenticated
Apr 28 10:18:36 jason-laptop kernel: wlan0: associate with 00:1c:10:08:b7:a5 (try 1/3)
Apr 28 10:18:36 jason-laptop kernel: wlan0: RX AssocResp from 00:1c:10:08:b7:a5 (capab=0x401 status=0 aid=2)
Apr 28 10:18:36 jason-laptop kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Apr 28 10:18:36 jason-laptop kernel: wlan0: associated
Apr 28 10:18:36 jason-laptop NetworkManager[136]: <info> (wlan0): supplicant interface state: authenticating -> associating
Apr 28 10:18:36 jason-laptop NetworkManager[136]: <info> (wlan0): supplicant interface state: associating -> completed
Apr 28 10:18:36 jason-laptop NetworkManager[136]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless networ
Apr 28 10:18:36 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 28 10:18:36 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Apr 28 10:18:36 jason-laptop NetworkManager[136]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Apr 28 10:18:36 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Apr 28 10:18:36 jason-laptop NetworkManager[136]: <info> dhclient started with pid 355
Apr 28 10:18:36 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Beginning IP6 addrconf.
Apr 28 10:18:36 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Apr 28 10:18:37 jason-laptop dhclient[355]: Internet Systems Consortium DHCP Client 4.2.5
Apr 28 10:18:37 jason-laptop dhclient[355]: Copyright 2004-2013 Internet Systems Consortium.
Apr 28 10:18:37 jason-laptop dhclient[355]: All rights reserved.
Apr 28 10:18:37 jason-laptop dhclient[355]: For info, please visit https://www.isc.org/software/dhcp/
Apr 28 10:18:37 jason-laptop dhclient[355]: 
Apr 28 10:18:37 jason-laptop NetworkManager[136]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Apr 28 10:18:37 jason-laptop dhclient[355]: Listening on LPF/wlan0/00:1c:26:ca:be:4b
Apr 28 10:18:37 jason-laptop dhclient[355]: Sending on   LPF/wlan0/00:1c:26:ca:be:4b
Apr 28 10:18:37 jason-laptop dhclient[355]: Sending on   Socket/fallback
Apr 28 10:18:37 jason-laptop dhclient[355]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Apr 28 10:18:37 jason-laptop dhclient[355]: DHCPACK from 10.0.0.2
Apr 28 10:18:37 jason-laptop dhclient[355]: bound to 10.0.0.39 -- renewal in 41062 seconds.
Apr 28 10:18:37 jason-laptop NetworkManager[136]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
Apr 28 10:18:37 jason-laptop NetworkManager[136]: <info>   address 10.0.0.39
Apr 28 10:18:37 jason-laptop NetworkManager[136]: <info>   prefix 24 (255.255.255.0)
Apr 28 10:18:37 jason-laptop NetworkManager[136]: <info>   gateway 10.0.0.2
Apr 28 10:18:37 jason-laptop NetworkManager[136]: <info>   nameserver '10.0.0.2'
Apr 28 10:18:37 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Apr 28 10:18:37 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Apr 28 10:18:37 jason-laptop avahi-daemon[141]: Joining mDNS multicast group on interface wlan0.IPv4 with address 10.0.0.39.
Apr 28 10:18:37 jason-laptop avahi-daemon[141]: New relevant interface wlan0.IPv4 for mDNS.
Apr 28 10:18:37 jason-laptop avahi-daemon[141]: Registering new address record for 10.0.0.39 on wlan0.IPv4.
Apr 28 10:18:38 jason-laptop NetworkManager[136]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Apr 28 10:18:38 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Apr 28 10:18:38 jason-laptop NetworkManager[136]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 28 10:18:38 jason-laptop avahi-daemon[141]: Registering new address record for fe80::21c:26ff:feca:be4b on wlan0.*.
Apr 28 10:18:38 jason-laptop NetworkManager[136]: <info> Policy set 'Auto Russell Home' (wlan0) as default for IPv4 routing and DNS.
Apr 28 10:18:38 jason-laptop NetworkManager[136]: <info> Writing DNS information to /usr/sbin/resolvconf
Apr 28 10:18:38 jason-laptop NetworkManager[136]: <info> (wlan0): roamed from BSSID 00:19:70:08:BA:F1 (Russell Home) to 00:1C:10:08:B7:A5 (Russell Home)
Apr 28 10:18:38 jason-laptop NetworkManager[136]: <info> Activation (wlan0) successful, device activated.
Apr 28 10:18:38 jason-laptop dbus-daemon[143]: dbus[143]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Apr 28 10:18:38 jason-laptop dbus[143]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Apr 28 10:18:38 jason-laptop dbus-daemon[143]: dbus[143]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 28 10:18:38 jason-laptop dbus[143]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 28 10:18:39 jason-laptop ntpd[240]: Listen normally on 4 wlan0 10.0.0.39 UDP 123
Apr 28 10:18:39 jason-laptop ntpd[240]: Listen normally on 5 wlan0 fe80::21c:26ff:feca:be4b UDP 123
Apr 28 10:18:39 jason-laptop ntpd[240]: peers refreshed
Apr 28 10:18:39 jason-laptop ntpd[240]: new interface(s) found: waking up resolver
Apr 28 10:18:41 jason-laptop ntpd_intres[244]: DNS 0.pool.ntp.org -> 41.73.42.10
Apr 28 10:18:42 jason-laptop ntpd_intres[244]: DNS 1.pool.ntp.org -> 196.43.208.18
Apr 28 10:18:42 jason-laptop ntpd_intres[244]: DNS 2.pool.ntp.org -> 196.24.99.44
Apr 28 10:18:57 jason-laptop NetworkManager[136]: <info> (wlan0): IP6 addrconf timed out or failed.
Apr 28 10:18:57 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Apr 28 10:18:57 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Apr 28 10:18:57 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Apr 28 10:21:55 jason-laptop systemd[1]: Time has been changed
Apr 28 10:23:56 jason-laptop systemd[1]: Starting Getty on tty2...
Apr 28 10:23:56 jason-laptop systemd[1]: Started Getty on tty2.
Apr 28 10:24:03 jason-laptop login[398]: pam_unix(login:session): session opened for user jason by LOGIN(uid=0)
Apr 28 10:24:03 jason-laptop systemd-logind[142]: New session 1 of user jason.
Apr 28 10:24:03 jason-laptop login[398]: LOGIN ON tty2 BY jason
Apr 28 10:24:13 jason-laptop sudo[438]: jason : TTY=tty2 ; PWD=/home/jason ; USER=root ; COMMAND=/usr/bin/journalctl --since=yesterday
Apr 28 10:24:13 jason-laptop sudo[438]: pam_unix(sudo:session): session opened for user root by jason(uid=0)
Apr 28 10:24:14 jason-laptop sudo[438]: pam_unix(sudo:session): session closed for user root
Apr 28 10:24:19 jason-laptop sudo[597]: jason : TTY=tty2 ; PWD=/home/jason ; USER=root ; COMMAND=/usr/bin/systemctl restart gdm.service
Apr 28 10:24:19 jason-laptop sudo[597]: pam_unix(sudo:session): session opened for user root by jason(uid=0)
Apr 28 10:24:19 jason-laptop systemd[1]: Stopping GNOME Display Manager...
Apr 28 10:24:19 jason-laptop gdm[151]: GLib-GObject: g_object_ref: assertion `object->ref_count > 0' failed
Apr 28 10:18:37 jason-laptop NetworkManager[136]: <info>   gateway 10.0.0.2
Apr 28 10:18:37 jason-laptop NetworkManager[136]: <info>   nameserver '10.0.0.2'
Apr 28 10:18:37 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Apr 28 10:18:37 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Apr 28 10:18:37 jason-laptop avahi-daemon[141]: Joining mDNS multicast group on interface wlan0.IPv4 with address 10.0.0.39.
Apr 28 10:18:37 jason-laptop avahi-daemon[141]: New relevant interface wlan0.IPv4 for mDNS.
Apr 28 10:18:37 jason-laptop avahi-daemon[141]: Registering new address record for 10.0.0.39 on wlan0.IPv4.
Apr 28 10:18:38 jason-laptop NetworkManager[136]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Apr 28 10:18:38 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Apr 28 10:18:38 jason-laptop NetworkManager[136]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 28 10:18:38 jason-laptop avahi-daemon[141]: Registering new address record for fe80::21c:26ff:feca:be4b on wlan0.*.
Apr 28 10:18:38 jason-laptop NetworkManager[136]: <info> Policy set 'Auto Russell Home' (wlan0) as default for IPv4 routing and DNS.
Apr 28 10:18:38 jason-laptop NetworkManager[136]: <info> Writing DNS information to /usr/sbin/resolvconf
Apr 28 10:18:38 jason-laptop NetworkManager[136]: <info> (wlan0): roamed from BSSID 00:19:70:08:BA:F1 (Russell Home) to 00:1C:10:08:B7:A5 (Russell Home)
Apr 28 10:18:38 jason-laptop NetworkManager[136]: <info> Activation (wlan0) successful, device activated.
Apr 28 10:18:38 jason-laptop dbus-daemon[143]: dbus[143]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Apr 28 10:18:38 jason-laptop dbus[143]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Apr 28 10:18:38 jason-laptop dbus-daemon[143]: dbus[143]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 28 10:18:38 jason-laptop dbus[143]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 28 10:18:39 jason-laptop ntpd[240]: Listen normally on 4 wlan0 10.0.0.39 UDP 123
Apr 28 10:18:39 jason-laptop ntpd[240]: Listen normally on 5 wlan0 fe80::21c:26ff:feca:be4b UDP 123
Apr 28 10:18:39 jason-laptop ntpd[240]: peers refreshed
Apr 28 10:18:39 jason-laptop ntpd[240]: new interface(s) found: waking up resolver
Apr 28 10:18:41 jason-laptop ntpd_intres[244]: DNS 0.pool.ntp.org -> 41.73.42.10
Apr 28 10:18:42 jason-laptop ntpd_intres[244]: DNS 1.pool.ntp.org -> 196.43.208.18
Apr 28 10:18:42 jason-laptop ntpd_intres[244]: DNS 2.pool.ntp.org -> 196.24.99.44
Apr 28 10:18:57 jason-laptop NetworkManager[136]: <info> (wlan0): IP6 addrconf timed out or failed.
Apr 28 10:18:57 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Apr 28 10:18:57 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Apr 28 10:18:57 jason-laptop NetworkManager[136]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Apr 28 10:21:55 jason-laptop systemd[1]: Time has been changed
Apr 28 10:23:56 jason-laptop systemd[1]: Starting Getty on tty2...
Apr 28 10:23:56 jason-laptop systemd[1]: Started Getty on tty2.
Apr 28 10:24:03 jason-laptop login[398]: pam_unix(login:session): session opened for user jason by LOGIN(uid=0)
Apr 28 10:24:03 jason-laptop systemd-logind[142]: New session 1 of user jason.
Apr 28 10:24:03 jason-laptop login[398]: LOGIN ON tty2 BY jason
Apr 28 10:24:13 jason-laptop sudo[438]: jason : TTY=tty2 ; PWD=/home/jason ; USER=root ; COMMAND=/usr/bin/journalctl --since=yesterday
Apr 28 10:24:13 jason-laptop sudo[438]: pam_unix(sudo:session): session opened for user root by jason(uid=0)
Apr 28 10:24:14 jason-laptop sudo[438]: pam_unix(sudo:session): session closed for user root
Apr 28 10:24:19 jason-laptop sudo[597]: jason : TTY=tty2 ; PWD=/home/jason ; USER=root ; COMMAND=/usr/bin/systemctl restart gdm.service
Apr 28 10:24:19 jason-laptop sudo[597]: pam_unix(sudo:session): session opened for user root by jason(uid=0)
Apr 28 10:24:19 jason-laptop systemd[1]: Stopping GNOME Display Manager...
Apr 28 10:24:19 jason-laptop gdm[151]: GLib-GObject: g_object_ref: assertion `object->ref_count > 0' failed
Apr 28 10:24:19 jason-laptop /usr/bin/dbus-launch[256]: Window manager warning: Log level 16: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable
Apr 28 10:24:19 jason-laptop /usr/bin/dbus-launch[256]: gnome-session[256]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) o
Apr 28 10:24:19 jason-laptop /usr/bin/dbus-launch[256]: ** (gnome-settings-daemon:276): WARNING **: Name taken or bus went away - shutting down
Apr 28 10:24:19 jason-laptop gnome-session[256]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Apr 28 10:24:19 jason-laptop /usr/bin/dbus-launch[256]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes 
Apr 28 10:24:19 jason-laptop polkitd[181]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.23, object path /org/freedesktop/PolicyKi
Apr 28 10:24:19 jason-laptop /usr/bin/dbus-launch[256]: (gnome-settings-daemon:276): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 2 (No such file or 
Apr 28 10:24:19 jason-laptop systemd-logind[142]: Removed session c1.
Apr 28 10:24:19 jason-laptop colord[177]: device removed: xrandr-cPATH
Apr 28 10:24:19 jason-laptop colord[177]: Profile removed: icc-adce9e59cf896c1faca0224e3c21c8fd
Apr 28 10:24:19 jason-laptop gdm[151]: GLib-GObject: g_object_unref: assertion `object->ref_count > 0' failed
Apr 28 10:24:19 jason-laptop systemd[1]: Starting GNOME Display Manager...
Apr 28 10:24:19 jason-laptop systemd[1]: Started GNOME Display Manager.
Apr 28 10:24:19 jason-laptop sudo[597]: pam_unix(sudo:session): session closed for user root
Apr 28 10:24:19 jason-laptop dbus-daemon[143]: dbus[143]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.180" (uid=0 pid=602 
Apr 28 10:24:19 jason-laptop dbus[143]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.180" (uid=0 pid=602 comm="/usr/sbin/gd
Apr 28 10:24:20 jason-laptop gdm[602]: Failed to give slave programs access to the display. Trying to proceed.
Apr 28 10:24:20 jason-laptop systemd-logind[142]: New session c2 of user gdm.
Apr 28 10:24:20 jason-laptop systemd-logind[142]: Linked /tmp/.X11-unix/X0 to /run/user/120/X11-display.
Apr 28 10:24:20 jason-laptop /usr/bin/dbus-launch[622]: gnome-session[622]: WARNING: Could not parse desktop file /usr/share/gdm/greeter/autostart/orca-autost
Apr 28 10:24:20 jason-laptop /usr/bin/dbus-launch[622]: gnome-session[622]: WARNING: could not read /usr/share/gdm/greeter/autostart/orca-autostart.desktop
Apr 28 10:24:20 jason-laptop gnome-session[622]: WARNING: Could not parse desktop file /usr/share/gdm/greeter/autostart/orca-autostart.desktop or it reference
Apr 28 10:24:20 jason-laptop gnome-session[622]: WARNING: could not read /usr/share/gdm/greeter/autostart/orca-autostart.desktop
Apr 28 10:24:20 jason-laptop gnome-session[622]: Entering running state
Apr 28 10:24:20 jason-laptop colord[177]: Automatic metadata add icc-2927396d048bf9f6cf9bafb6cc5812bd to xrandr-cPATH
Apr 28 10:24:20 jason-laptop colord[177]: Device added: xrandr-cPATH
Apr 28 10:24:20 jason-laptop /usr/bin/dbus-launch[622]: (gnome-settings-daemon:642): Gvc-WARNING **: Failed to connect context: OK

Last edited by jrussell (2013-04-28 08:38:35)


bitcoin: 1G62YGRFkMDwhGr5T5YGovfsxLx44eZo7U

Offline

#2 2013-04-28 19:26:07

konfiot
Member
Registered: 2013-04-23
Posts: 13

Re: GDM 3.8 blank grey background after screensaver interupt

+1,
I've got the same grey screen, but I'm not sure that it is when I move the mouse when the screen is fading to black. it seems quite random in my case

Offline

#3 2013-05-04 16:34:47

kenny3794
Member
Registered: 2013-05-04
Posts: 20

Re: GDM 3.8 blank grey background after screensaver interupt

+1

happening to me also on occasion.  Is there a GDM Bug Report filed?

Offline

#4 2013-05-07 16:21:47

konfiot
Member
Registered: 2013-04-23
Posts: 13

Re: GDM 3.8 blank grey background after screensaver interupt

Not sure that it can make these kind of bugs, but what graphic card do you have, and what driver do you use ?

Offline

#5 2013-05-07 16:32:57

kenny3794
Member
Registered: 2013-05-04
Posts: 20

Re: GDM 3.8 blank grey background after screensaver interupt

I'm using the Open Source graphics stack with a integrated AMD Radeon HD3200 chipset.  Its not the quickest graphics, but works for desktop PC usage (mostly web browsing, document creation).  The solution I have is switching to another VT and killing the process associated with GDM.  Once this is done, GDM and X restart and it's like I just restarted the PC, but this is not a good workaround as I must logout all users first to avoid loss of data.

Offline

#6 2013-05-07 19:32:25

konfiot
Member
Registered: 2013-04-23
Posts: 13

Re: GDM 3.8 blank grey background after screensaver interupt

Also using the free driver, but with an nvidia card, did you try with the proprietary driver
And what does your journalctl tells ?

Offline

#7 2013-05-07 19:34:06

kenny3794
Member
Registered: 2013-05-04
Posts: 20

Re: GDM 3.8 blank grey background after screensaver interupt

I'm at work right now, will look at journal when I get home.  The proprietary drivers for the HD3200 now require a Kernel and X roll-back.  I'm not wanting to do that.

Offline

#8 2013-05-09 03:08:06

kenny3794
Member
Registered: 2013-05-04
Posts: 20

Re: GDM 3.8 blank grey background after screensaver interupt

In the below, you can find where I killed GDM by finding this command:

May 08 16:08:42 FamilyPC-Arch sudo[7877]: kjernigan : TTY=tty2 ; PWD=/home/kjernigan ; USER=root ; COMMAND=/bin/kill -KILL 10101


journalctl output:

May 08 16:03:07 FamilyPC-Arch /etc/gdm/Xsession[28679]: glibtop: statvfs '/run/user/2003/gvfs' failed
May 08 16:03:07 FamilyPC-Arch /etc/gdm/Xsession[28679]: glibtop: statvfs '/run/user/2002/gvfs' failed
May 08 16:03:08 FamilyPC-Arch /etc/gdm/Xsession[28679]: glibtop: statvfs '/run/user/2003/gvfs' failed
May 08 16:03:08 FamilyPC-Arch /etc/gdm/Xsession[28679]: glibtop: statvfs '/run/user/2002/gvfs' failed
May 08 16:03:31 FamilyPC-Arch /etc/gdm/Xsession[28679]: glibtop: statvfs '/run/user/2003/gvfs' failed
May 08 16:03:31 FamilyPC-Arch /etc/gdm/Xsession[28679]: glibtop: statvfs '/run/user/2002/gvfs' failed
May 08 16:03:38 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!   Invalid work id 6
May 08 16:03:38 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     message = '"Invalid work id 6"'
May 08 16:03:38 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/main.js"'
May 08 16:03:38 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     lineNumber = '775'
May 08 16:03:38 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     stack = '"queueDeferredWork@/usr/share/gnome-shell/js/ui/main.js:775
May 08 16:03:38 FamilyPC-Arch /etc/gdm/Xsession[28679]: myDash<._queueRedisplay@/home/kjernigan/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/myDash.js:170
May 08 16:03:38 FamilyPC-Arch /etc/gdm/Xsession[28679]: wrapper@/usr/share/gjs-1.0/lang.js:213
May 08 16:03:38 FamilyPC-Arch /etc/gdm/Xsession[28679]: "'
May 08 16:03:38 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!   Invalid work id 7
May 08 16:03:38 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     message = '"Invalid work id 7"'
May 08 16:03:38 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/main.js"'
May 08 16:03:38 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     lineNumber = '775'
May 08 16:03:38 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     stack = '"queueDeferredWork@/usr/share/gnome-shell/js/ui/main.js:775
May 08 16:03:38 FamilyPC-Arch /etc/gdm/Xsession[28679]: myDash<._queueRedisplay@/home/kjernigan/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/myDash.js:170
May 08 16:03:38 FamilyPC-Arch /etc/gdm/Xsession[28679]: wrapper@/usr/share/gjs-1.0/lang.js:213
May 08 16:03:38 FamilyPC-Arch /etc/gdm/Xsession[28679]: "'
May 08 16:03:39 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!   Invalid work id 6
May 08 16:03:39 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     message = '"Invalid work id 6"'
May 08 16:03:39 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/main.js"'
May 08 16:03:39 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     lineNumber = '775'
May 08 16:03:39 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     stack = '"queueDeferredWork@/usr/share/gnome-shell/js/ui/main.js:775
May 08 16:03:39 FamilyPC-Arch /etc/gdm/Xsession[28679]: myDash<._queueRedisplay@/home/kjernigan/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/myDash.js:170
May 08 16:03:39 FamilyPC-Arch /etc/gdm/Xsession[28679]: wrapper@/usr/share/gjs-1.0/lang.js:213
May 08 16:03:39 FamilyPC-Arch /etc/gdm/Xsession[28679]: "'
May 08 16:03:39 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!   Invalid work id 7
May 08 16:03:39 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     message = '"Invalid work id 7"'
May 08 16:03:39 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/main.js"'
May 08 16:03:39 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     lineNumber = '775'
May 08 16:03:39 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     stack = '"queueDeferredWork@/usr/share/gnome-shell/js/ui/main.js:775
May 08 16:03:39 FamilyPC-Arch /etc/gdm/Xsession[28679]: myDash<._queueRedisplay@/home/kjernigan/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/myDash.js:170
May 08 16:03:39 FamilyPC-Arch /etc/gdm/Xsession[28679]: wrapper@/usr/share/gjs-1.0/lang.js:213
May 08 16:03:39 FamilyPC-Arch /etc/gdm/Xsession[28679]: "'
May 08 16:03:57 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!   Invalid work id 6
May 08 16:03:57 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     message = '"Invalid work id 6"'
May 08 16:03:57 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/main.js"'
May 08 16:03:57 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     lineNumber = '775'
May 08 16:03:57 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     stack = '"queueDeferredWork@/usr/share/gnome-shell/js/ui/main.js:775
May 08 16:03:57 FamilyPC-Arch /etc/gdm/Xsession[28679]: myDash<._queueRedisplay@/home/kjernigan/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/myDash.js:170
May 08 16:03:57 FamilyPC-Arch /etc/gdm/Xsession[28679]: wrapper@/usr/share/gjs-1.0/lang.js:213
May 08 16:03:57 FamilyPC-Arch /etc/gdm/Xsession[28679]: "'
May 08 16:03:57 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!   Invalid work id 7
May 08 16:03:57 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     message = '"Invalid work id 7"'
May 08 16:03:57 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/main.js"'
May 08 16:03:57 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     lineNumber = '775'
May 08 16:03:57 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     stack = '"queueDeferredWork@/usr/share/gnome-shell/js/ui/main.js:775
May 08 16:03:57 FamilyPC-Arch /etc/gdm/Xsession[28679]: myDash<._queueRedisplay@/home/kjernigan/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/myDash.js:170
May 08 16:03:57 FamilyPC-Arch /etc/gdm/Xsession[28679]: wrapper@/usr/share/gjs-1.0/lang.js:213
May 08 16:03:57 FamilyPC-Arch /etc/gdm/Xsession[28679]: "'
May 08 16:04:00 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!   Invalid work id 6
May 08 16:04:00 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     message = '"Invalid work id 6"'
May 08 16:04:00 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/main.js"'
May 08 16:04:00 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     lineNumber = '775'
May 08 16:04:00 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     stack = '"queueDeferredWork@/usr/share/gnome-shell/js/ui/main.js:775
May 08 16:04:00 FamilyPC-Arch /etc/gdm/Xsession[28679]: myDash<._queueRedisplay@/home/kjernigan/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/myDash.js:170
May 08 16:04:00 FamilyPC-Arch /etc/gdm/Xsession[28679]: wrapper@/usr/share/gjs-1.0/lang.js:213
May 08 16:04:00 FamilyPC-Arch /etc/gdm/Xsession[28679]: "'
May 08 16:04:00 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!   Invalid work id 7
May 08 16:04:00 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     message = '"Invalid work id 7"'
May 08 16:04:00 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/main.js"'
May 08 16:04:00 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     lineNumber = '775'
May 08 16:04:00 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     stack = '"queueDeferredWork@/usr/share/gnome-shell/js/ui/main.js:775
May 08 16:04:00 FamilyPC-Arch /etc/gdm/Xsession[28679]: myDash<._queueRedisplay@/home/kjernigan/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/myDash.js:170
May 08 16:04:00 FamilyPC-Arch /etc/gdm/Xsession[28679]: wrapper@/usr/share/gjs-1.0/lang.js:213
May 08 16:04:00 FamilyPC-Arch /etc/gdm/Xsession[28679]: "'
May 08 16:04:02 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!   Invalid work id 6
May 08 16:04:02 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     message = '"Invalid work id 6"'
May 08 16:04:02 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/main.js"'
May 08 16:04:02 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     lineNumber = '775'
May 08 16:04:02 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     stack = '"queueDeferredWork@/usr/share/gnome-shell/js/ui/main.js:775
May 08 16:04:02 FamilyPC-Arch /etc/gdm/Xsession[28679]: myDash<._queueRedisplay@/home/kjernigan/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/myDash.js:170
May 08 16:04:02 FamilyPC-Arch /etc/gdm/Xsession[28679]: wrapper@/usr/share/gjs-1.0/lang.js:213
May 08 16:04:02 FamilyPC-Arch /etc/gdm/Xsession[28679]: "'
May 08 16:04:02 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!   Invalid work id 7
May 08 16:04:02 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     message = '"Invalid work id 7"'
May 08 16:04:02 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/main.js"'
May 08 16:04:02 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     lineNumber = '775'
May 08 16:04:02 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     stack = '"queueDeferredWork@/usr/share/gnome-shell/js/ui/main.js:775
May 08 16:04:02 FamilyPC-Arch /etc/gdm/Xsession[28679]: myDash<._queueRedisplay@/home/kjernigan/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/myDash.js:170
May 08 16:04:02 FamilyPC-Arch /etc/gdm/Xsession[28679]: wrapper@/usr/share/gjs-1.0/lang.js:213
May 08 16:04:02 FamilyPC-Arch /etc/gdm/Xsession[28679]: "'
May 08 16:04:04 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!   Invalid work id 6
May 08 16:04:04 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     message = '"Invalid work id 6"'
May 08 16:04:04 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/main.js"'
May 08 16:04:04 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     lineNumber = '775'
May 08 16:04:04 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     stack = '"queueDeferredWork@/usr/share/gnome-shell/js/ui/main.js:775
May 08 16:04:04 FamilyPC-Arch /etc/gdm/Xsession[28679]: myDash<._queueRedisplay@/home/kjernigan/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/myDash.js:170
May 08 16:04:04 FamilyPC-Arch /etc/gdm/Xsession[28679]: wrapper@/usr/share/gjs-1.0/lang.js:213
May 08 16:04:04 FamilyPC-Arch /etc/gdm/Xsession[28679]: "'
May 08 16:04:04 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!   Invalid work id 7
May 08 16:04:04 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     message = '"Invalid work id 7"'
May 08 16:04:04 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/main.js"'
May 08 16:04:04 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     lineNumber = '775'
May 08 16:04:04 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     stack = '"queueDeferredWork@/usr/share/gnome-shell/js/ui/main.js:775
May 08 16:04:04 FamilyPC-Arch /etc/gdm/Xsession[28679]: myDash<._queueRedisplay@/home/kjernigan/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/myDash.js:170
May 08 16:04:04 FamilyPC-Arch /etc/gdm/Xsession[28679]: wrapper@/usr/share/gjs-1.0/lang.js:213
May 08 16:04:04 FamilyPC-Arch /etc/gdm/Xsession[28679]: "'
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!   Invalid work id 6
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     message = '"Invalid work id 6"'
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/main.js"'
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     lineNumber = '775'
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     stack = '"queueDeferredWork@/usr/share/gnome-shell/js/ui/main.js:775
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: myDash<._queueRedisplay@/home/kjernigan/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/myDash.js:170
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: wrapper@/usr/share/gjs-1.0/lang.js:213
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: "'
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!   Invalid work id 7
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     message = '"Invalid work id 7"'
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/main.js"'
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     lineNumber = '775'
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS ERROR: !!!     stack = '"queueDeferredWork@/usr/share/gnome-shell/js/ui/main.js:775
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: myDash<._queueRedisplay@/home/kjernigan/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/myDash.js:170
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: wrapper@/usr/share/gjs-1.0/lang.js:213
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: "'
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
May 08 16:04:09 FamilyPC-Arch /etc/gdm/Xsession[28679]: (gnome-shell:29677): St-CRITICAL **: setup_framebuffers: assertion `width > 0' failed
May 08 16:04:13 FamilyPC-Arch /etc/gdm/Xsession[28679]: JS LOG: SM: Power proxy error: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Power was not provided by any .service files
May 08 16:04:13 FamilyPC-Arch /etc/gdm/Xsession[28679]: (gnome-settings-daemon:28712): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
May 08 16:04:13 FamilyPC-Arch /etc/gdm/Xsession[28679]: (gnome-settings-daemon:28712): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
May 08 16:04:13 FamilyPC-Arch /etc/gdm/Xsession[28679]: (gnome-settings-daemon:28712): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
May 08 16:04:13 FamilyPC-Arch /etc/gdm/Xsession[28679]: (gnome-settings-daemon:28712): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
May 08 16:04:13 FamilyPC-Arch /etc/gdm/Xsession[28679]: (gnome-settings-daemon:28712): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
May 08 16:04:13 FamilyPC-Arch /etc/gdm/Xsession[28679]: (gnome-settings-daemon:28712): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
May 08 16:08:24 FamilyPC-Arch sudo[7867]: pam_unix(sudo:auth): conversation failed
May 08 16:08:28 FamilyPC-Arch sudo[7868]: kjernigan : TTY=tty2 ; PWD=/home/kjernigan ; USER=root ; COMMAND=/bin/kill -KILL 7361
May 08 16:08:41 FamilyPC-Arch sudo[7875]: kjernigan : TTY=tty2 ; PWD=/home/kjernigan ; USER=root ; COMMAND=/bin/kill -KILL 101010
May 08 16:08:42 FamilyPC-Arch sudo[7877]: kjernigan : TTY=tty2 ; PWD=/home/kjernigan ; USER=root ; COMMAND=/bin/kill -KILL 10101
May 08 16:08:49 FamilyPC-Arch /etc/gdm/Xsession[7967]: /etc/gdm/Xsession: Beginning session setup...
May 08 16:08:49 FamilyPC-Arch /etc/gdm/Xsession[7967]: localuser:kjernigan being added to access control list
May 08 16:08:49 FamilyPC-Arch /etc/gdm/Xsession[7967]: /etc/gdm/Xsession: ssh-agent not found!
May 08 16:08:49 FamilyPC-Arch /etc/gdm/Xsession[7967]: /etc/gdm/Xsession: Setup done, will execute: gnome-session
May 08 16:08:49 FamilyPC-Arch /etc/gdm/Xsession[7967]: GNOME_KEYRING_CONTROL=/run/user/2001/keyring-8zoPBb
May 08 16:08:49 FamilyPC-Arch /etc/gdm/Xsession[7967]: GNOME_KEYRING_CONTROL=/run/user/2001/keyring-8zoPBb
May 08 16:08:49 FamilyPC-Arch /etc/gdm/Xsession[7967]: SSH_AUTH_SOCK=/run/user/2001/keyring-8zoPBb/ssh
May 08 16:08:49 FamilyPC-Arch /etc/gdm/Xsession[7967]: GNOME_KEYRING_CONTROL=/run/user/2001/keyring-8zoPBb
May 08 16:08:49 FamilyPC-Arch /etc/gdm/Xsession[7967]: SSH_AUTH_SOCK=/run/user/2001/keyring-8zoPBb/ssh
May 08 16:08:49 FamilyPC-Arch /etc/gdm/Xsession[7967]: GPG_AGENT_INFO=/run/user/2001/keyring-8zoPBb/gpg:0:1
May 08 16:08:49 FamilyPC-Arch /etc/gdm/Xsession[7967]: GNOME_KEYRING_CONTROL=/run/user/2001/keyring-8zoPBb
May 08 16:08:49 FamilyPC-Arch /etc/gdm/Xsession[7967]: SSH_AUTH_SOCK=/run/user/2001/keyring-8zoPBb/ssh
May 08 16:08:49 FamilyPC-Arch /etc/gdm/Xsession[7967]: Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
May 08 16:08:49 FamilyPC-Arch /etc/gdm/Xsession[7967]: (gnome-settings-daemon:8000): Gvc-WARNING **: Failed to connect context: OK
May 08 16:08:52 FamilyPC-Arch goa[8077]: goa-daemon version 3.8.1 starting [main.c:113, main()]
May 08 16:08:52 FamilyPC-Arch /etc/gdm/Xsession[7967]: Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
May 08 16:08:52 FamilyPC-Arch /etc/gdm/Xsession[7967]: Failed to play sound: File or data not found
May 08 16:08:52 FamilyPC-Arch gnome-session[7967]: Entering running state
May 08 16:08:52 FamilyPC-Arch /etc/gdm/Xsession[7967]: JS LOG: GNOME Shell started at Wed May 08 2013 16:08:52 GMT-0400 (EDT)
May 08 16:08:52 FamilyPC-Arch /etc/gdm/Xsession[7967]: Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
May 08 16:08:52 FamilyPC-Arch /etc/gdm/Xsession[7967]: ** (nm-applet:8093): 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. See system logs and 'systemctl status dbus-org.freedesktop.ModemManager1.service' for details.
May 08 16:08:52 FamilyPC-Arch /etc/gdm/Xsession[7967]: ** Message: applet now removed from the notification area
May 08 16:08:52 FamilyPC-Arch /etc/gdm/Xsession[7967]: ** Message: applet now embedded in the notification area
May 08 16:08:52 FamilyPC-Arch /etc/gdm/Xsession[7967]: LOGGER INIT...
May 08 16:08:52 FamilyPC-Arch /etc/gdm/Xsession[7967]: LOGGER:Using default configuration
May 08 16:08:53 FamilyPC-Arch /etc/gdm/Xsession[7967]: Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
May 08 16:08:53 FamilyPC-Arch /etc/gdm/Xsession[7967]: QObject::connect: Cannot connect QAction::triggered() to (null)::pay()
May 08 16:08:53 FamilyPC-Arch /etc/gdm/Xsession[7967]: JS LOG: System monitor applet init from /home/kjernigan/.local/share/gnome-shell/extensions/system-monitor@paradoxxx.zero.gmail.com
May 08 16:08:53 FamilyPC-Arch /etc/gdm/Xsession[7967]: JS LOG: System monitor applet enabling
May 08 16:08:53 FamilyPC-Arch /etc/gdm/Xsession[7967]: JS LOG: Error: Can't create a Javascript object for glibtop_sysinfo; no way to copy
May 08 16:08:53 FamilyPC-Arch /etc/gdm/Xsession[7967]: JS LOG: Error: Can't create a Javascript object for glibtop_sysinfo; no way to copy
May 08 16:08:53 FamilyPC-Arch /etc/gdm/Xsession[7967]: JS LOG: System monitor applet enabling done
May 08 16:08:54 FamilyPC-Arch /etc/gdm/Xsession[7967]: JS LOG: SM: No battery found
May 08 16:08:56 FamilyPC-Arch /etc/gdm/Xsession[7967]: (process:8160): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
May 08 16:08:56 FamilyPC-Arch /etc/gdm/Xsession[7967]: Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.

Offline

#9 2013-05-09 06:13:04

konfiot
Member
Registered: 2013-04-23
Posts: 13

Re: GDM 3.8 blank grey background after screensaver interupt

Hmm, I'll post my journalctl when the problem happens again, but as far as I remember, I didn't have the same messages, there were failed assertions but not the same as the ones on your journalctl ...
And did you install the last update of gnome-session, (3 may 2013), maybe it has been fixed

Offline

#10 2013-05-09 06:57:02

konfiot
Member
Registered: 2013-04-23
Posts: 13

Re: GDM 3.8 blank grey background after screensaver interupt

Here is my journalctl
And the update didn't help anything ...

May 09 08:44:29 pc-rdc /etc/gdm/Xsession[1371]: (gnome-settings-daemon:1406): color-plugin-WARNING **: failed to set screen _ICC_PROFILE: L'ouverture du fichier « /var/lib/gdm/.local/sh
May 09 08:44:29 pc-rdc /etc/gdm/Xsession[1371]: JS LOG: SM: No battery found
May 09 08:44:29 pc-rdc /etc/gdm/Xsession[1371]: JS LOG: SM: No battery found
May 09 08:44:29 pc-rdc /etc/gdm/Xsession[1371]: JS LOG: SM: No battery found
May 09 08:44:29 pc-rdc /etc/gdm/Xsession[1371]: JS LOG: SM: No battery found
May 09 08:44:29 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:29 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:29 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:29 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:29 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:29 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
(...)
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_editable: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:30 pc-rdc /etc/gdm/Xsession[1371]: (gnome-shell:1465): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
May 09 08:44:32 pc-rdc /etc/gdm/Xsession[1371]: JS LOG: System monitor applet enabling
May 09 08:44:32 pc-rdc /etc/gdm/Xsession[1371]: JS LOG: Error: Can't create a Javascript object for glibtop_sysinfo; no way to copy
May 09 08:44:32 pc-rdc /etc/gdm/Xsession[1371]: Avertissement du gestionnaire de fenêtres : Log level 16: Could not initialize NMClient /org/freedesktop/NetworkManager: Unit dbus-org.fr
May 09 08:44:32 pc-rdc /etc/gdm/Xsession[1371]: JS LOG: Please install Network Manager Gobject Introspection Bindings
May 09 08:44:33 pc-rdc /etc/gdm/Xsession[1371]: JS LOG: Please install Network Manager Gobject Introspection Bindings: TypeError: null has no properties
May 09 08:44:33 pc-rdc /etc/gdm/Xsession[1371]: JS LOG: System monitor applet enabling done
May 09 08:44:33 pc-rdc /etc/gdm/Xsession[1371]: JS LOG: SM: No battery found

Offline

#11 2013-05-09 18:53:11

konfiot
Member
Registered: 2013-04-23
Posts: 13

Re: GDM 3.8 blank grey background after screensaver interupt

Hmm, I have just tried with the proprietary drivers, and it didn't worked, the blank grey screen is still here ... and this time, there was no message in the journalctl ...
Did someone filled a GDM bug report ? otherwise I will do that asap.

Offline

#12 2013-05-12 03:16:05

kenny3794
Member
Registered: 2013-05-04
Posts: 20

Re: GDM 3.8 blank grey background after screensaver interupt

I have not filed one, please do.

Offline

#13 2013-05-12 08:20:25

amlw19
Member
Registered: 2013-05-07
Posts: 2

Re: GDM 3.8 blank grey background after screensaver interupt

konfiot wrote:

+1,
I've got the same grey screen, but I'm not sure that it is when I move the mouse when the screen is fading to black. it seems quite random in my case

The same situation here, however in most cases my system starts correctly.

Edit:
Sorry, I didn't read the first post precisely. I have a similar problem, but in my case I see only the grey background right after clicking "Sign in" during the logging to system, from time to time. One or two reboots usually solve it.

Last edited by amlw19 (2013-05-12 08:42:52)

Offline

Board footer

Powered by FluxBB