| View previous topic :: View next topic |
| Author |
Message |
csteeves
n00b
Joined: 20 Aug 2007
Posts: 61
|
 Posted: Tue Mar 11, 2014 8:42 pm Post subject: Gnome 3.10 fails to start [WORKAROUND] |
 |
|
Yesterday when emerging world, I had an upgrade of Gnome from 3.8 to 3.10. Previously, Gnome 3.8 was working normally for me, and I had made many tweaks to the configuration (fonts, extensions etc). After successful completion of emerge -avDuN world and revdep-rebuild and reboot, startx produced only a black screen, although I could see the mouse cursor arrow and move it normally. I could drop out to a terminal and kill the xserver with Cntl-c. journalctl -rb produced this output during a start of Gnome (starting, at the bottom, from the first message tagged gnome-session):
| Code: |
Mar 11 11:36:48 talisker gnome-session[330]: (gnome-shell:418): Gjs-WARNING **: JS ERROR: Error: Argument 'text' (type utf8) may not be null
Mar 11 11:36:47 talisker gnome-session[330]: wrapper@/usr/share/gjs-1.0/lang.js:213
Mar 11 11:36:47 talisker gnome-session[330]: DateMenuButton<._updateClockAndDate@/usr/share/gnome-shell/js/ui/dateMenu.js:198
Mar 11 11:36:47 talisker gnome-session[330]: (gnome-shell:418): Gjs-WARNING **: JS ERROR: Error: Argument 'text' (type utf8) may not be null
Mar 11 11:36:46 talisker gnome-session[330]: wrapper@/usr/share/gjs-1.0/lang.js:213
Mar 11 11:36:46 talisker gnome-session[330]: DateMenuButton<._updateClockAndDate@/usr/share/gnome-shell/js/ui/dateMenu.js:198
Mar 11 11:36:46 talisker gnome-session[330]: (gnome-shell:418): Gjs-WARNING **: JS ERROR: Error: Argument 'text' (type utf8) may not be null
Mar 11 11:36:45 talisker gnome-session[330]: wrapper@/usr/share/gjs-1.0/lang.js:213
Mar 11 11:36:45 talisker gnome-session[330]: DateMenuButton<._updateClockAndDate@/usr/share/gnome-shell/js/ui/dateMenu.js:198
Mar 11 11:36:45 talisker gnome-session[330]: (gnome-shell:418): Gjs-WARNING **: JS ERROR: Error: Argument 'text' (type utf8) may not be null
Mar 11 11:36:44 talisker gnome-session[330]: wrapper@/usr/share/gjs-1.0/lang.js:213
Mar 11 11:36:44 talisker gnome-session[330]: DateMenuButton<._updateClockAndDate@/usr/share/gnome-shell/js/ui/dateMenu.js:198
Mar 11 11:36:44 talisker gnome-session[330]: (gnome-shell:418): Gjs-WARNING **: JS ERROR: Error: Argument 'text' (type utf8) may not be null
Mar 11 11:36:43 talisker gnome-session[330]: wrapper@/usr/share/gjs-1.0/lang.js:213
Mar 11 11:36:43 talisker gnome-session[330]: DateMenuButton<._updateClockAndDate@/usr/share/gnome-shell/js/ui/dateMenu.js:198
Mar 11 11:36:43 talisker gnome-session[330]: (gnome-shell:418): Gjs-WARNING **: JS ERROR: Error: Argument 'text' (type utf8) may not be null
Mar 11 11:36:42 talisker gnome-session[330]: (gnome-settings-daemon:355): color-plugin-WARNING **: failed to create device: failed to obtain org.freedesktop.color-manager.create-de
Mar 11 11:36:42 talisker gnome-session[330]: onNextFileComplete@/usr/share/gnome-shell/js/misc/fileUtils.js:21
Mar 11 11:36:42 talisker gnome-session[330]: @/usr/share/gnome-shell/js/misc/fileUtils.js:51
Mar 11 11:36:42 talisker gnome-session[330]: done@/usr/share/gnome-shell/js/misc/fileUtils.js:33
Mar 11 11:36:42 talisker gnome-session[330]: SessionMode<.init/<@/usr/share/gnome-shell/js/ui/sessionMode.js:166
Mar 11 11:36:42 talisker gnome-session[330]: _emit@/usr/share/gjs-1.0/signals.js:124
Mar 11 11:36:42 talisker gnome-session[330]: _sessionsLoaded@/usr/share/gnome-shell/js/ui/main.js:122
Mar 11 11:36:42 talisker gnome-session[330]: _initializeUI@/usr/share/gnome-shell/js/ui/main.js:173
Mar 11 11:36:42 talisker gnome-session[330]: Class._construct/newClass@/usr/share/gjs-1.0/lang.js:248
Mar 11 11:36:42 talisker gnome-session[330]: _Base._construct@/usr/share/gjs-1.0/lang.js:154
Mar 11 11:36:42 talisker gnome-session[330]: wrapper@/usr/share/gjs-1.0/lang.js:213
Mar 11 11:36:42 talisker gnome-session[330]: Panel<._init@/usr/share/gnome-shell/js/ui/panel.js:913
Mar 11 11:36:42 talisker gnome-session[330]: wrapper@/usr/share/gjs-1.0/lang.js:213
Mar 11 11:36:42 talisker gnome-session[330]: Panel<._updatePanel@/usr/share/gnome-shell/js/ui/panel.js:1068
Mar 11 11:36:42 talisker gnome-session[330]: wrapper@/usr/share/gjs-1.0/lang.js:213
Mar 11 11:36:42 talisker gnome-session[330]: Panel<._updateBox@/usr/share/gnome-shell/js/ui/panel.js:1117
Mar 11 11:36:42 talisker gnome-session[330]: wrapper@/usr/share/gjs-1.0/lang.js:213
Mar 11 11:36:42 talisker gnome-session[330]: Panel<._ensureIndicator@/usr/share/gnome-shell/js/ui/panel.js:1106
Mar 11 11:36:42 talisker gnome-session[330]: Class._construct/newClass@/usr/share/gjs-1.0/lang.js:248
Mar 11 11:36:42 talisker gnome-session[330]: _Base._construct@/usr/share/gjs-1.0/lang.js:154
Mar 11 11:36:42 talisker gnome-session[330]: wrapper@/usr/share/gjs-1.0/lang.js:213
Mar 11 11:36:42 talisker gnome-session[330]: DateMenuButton<._init@/usr/share/gnome-shell/js/ui/dateMenu.js:139
Mar 11 11:36:42 talisker gnome-session[330]: wrapper@/usr/share/gjs-1.0/lang.js:213
Mar 11 11:36:42 talisker gnome-session[330]: DateMenuButton<._updateClockAndDate@/usr/share/gnome-shell/js/ui/dateMenu.js:198
Mar 11 11:36:42 talisker gnome-session[330]: (gnome-shell:418): Gjs-WARNING **: JS ERROR: Exception in callback for signal: sessions-loaded: Error: Argument 'text' (type utf8) may
Mar 11 11:36:36 talisker metalog[191]: 0>Mar 11 11:36:35 colord: Using device database file /var/lib/colord/storage.db<29>Mar 11 11:36:35 dbus[190]: [system] Activating via systemd
Mar 11 11:36:36 talisker colord[424]: (colord:424): libcolord-WARNING **: lcms2(profile): Failed with error: Corrupted tag 'meta' [12]
Mar 11 11:36:36 talisker colord[424]: (colord:424): libcolord-WARNING **: lcms2(profile): Failed with error: Bad dictionary Name/Value [12]
Mar 11 11:36:36 talisker gnome-session[330]: (gnome-settings-daemon:355): IBUS-WARNING **: Unable to connect to ibus: Could not connect: Connection refused
Mar 11 11:36:36 talisker colord[424]: (colord:424): libcolord-WARNING **: lcms2(profile): Failed with error: Corrupted tag 'meta' [12]
Mar 11 11:36:36 talisker colord[424]: (colord:424): libcolord-WARNING **: lcms2(profile): Failed with error: Bad dictionary Name/Value [12]
Mar 11 11:36:36 talisker colord[424]: (colord:424): libcolord-WARNING **: lcms2(profile): Failed with error: Corrupted tag 'meta' [12]
Mar 11 11:36:36 talisker colord[424]: (colord:424): libcolord-WARNING **: lcms2(profile): Failed with error: Bad dictionary Name/Value [12]
Mar 11 11:36:35 talisker systemd[1]: Started Manage, Install and Generate Color Profiles.
Mar 11 11:36:35 talisker dbus-daemon[190]: dbus[190]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Mar 11 11:36:35 talisker systemd[1]: Started Locale Service.
Mar 11 11:36:35 talisker dbus-daemon[190]: dbus[190]: [system] Successfully activated service 'org.freedesktop.locale1'
Mar 11 11:36:35 talisker systemd[1]: Starting Locale Service...
Mar 11 11:36:35 talisker dbus-daemon[190]: dbus[190]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Mar 11 11:36:35 talisker metalog[191]: <37>Mar 11 11:36:29 gnome-keyring-daemon[353]: couldn't access control socket: /run/user/1000/keyring-JQIjZT/control: No such file or directo
Mar 11 11:36:34 talisker systemd[1]: Starting Manage, Install and Generate Color Profiles...
Mar 11 11:36:34 talisker dbus-daemon[190]: dbus[190]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Mar 11 11:36:32 talisker systemd[1]: Started Authorization Manager.
Mar 11 11:36:32 talisker dbus-daemon[190]: dbus[190]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Mar 11 11:36:31 talisker dbus-daemon[190]: dbus[190]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service
Mar 11 11:36:31 talisker dbus-daemon[190]: dbus[190]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Mar 11 11:36:31 talisker systemd[1]: Starting Authorization Manager...
Mar 11 11:36:31 talisker dbus-daemon[190]: dbus[190]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Mar 11 11:36:31 talisker systemd[1]: Started Daemon for power management.
Mar 11 11:36:31 talisker dbus-daemon[190]: dbus[190]: [system] Successfully activated service 'org.freedesktop.UPower'
Mar 11 11:36:30 talisker systemd[1]: Starting Daemon for power management...
Mar 11 11:36:30 talisker dbus-daemon[190]: dbus[190]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Mar 11 11:36:29 talisker gnome-session[330]: GPG_AGENT_INFO=/run/user/1000/keyring-SoxKnK/gpg:0:1
Mar 11 11:36:29 talisker gnome-session[330]: SSH_AUTH_SOCK=/run/user/1000/keyring-SoxKnK/ssh
Mar 11 11:36:29 talisker gnome-session[330]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring-SoxKnK
Mar 11 11:36:29 talisker gnome-session[330]: GPG_AGENT_INFO=/run/user/1000/keyring-SoxKnK/gpg:0:1
Mar 11 11:36:29 talisker gnome-session[330]: SSH_AUTH_SOCK=/run/user/1000/keyring-SoxKnK/ssh
Mar 11 11:36:29 talisker gnome-session[330]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring-SoxKnK
Mar 11 11:36:29 talisker gnome-session[330]: SSH_AUTH_SOCK=/run/user/1000/keyring-SoxKnK/ssh
Mar 11 11:36:29 talisker gnome-session[330]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring-SoxKnK
Mar 11 11:36:29 talisker gnome-session[330]: ** Message: couldn't access control socket: /run/user/1000/keyring-JQIjZT/control: No such file or directory
Mar 11 11:36:29 talisker gnome-session[330]: ** Message: couldn't access control socket: /run/user/1000/keyring-JQIjZT/control: No such file or directory
Mar 11 11:36:29 talisker gnome-session[330]: GNOME_KEYRING_PID=356
Mar 11 11:36:29 talisker gnome-session[330]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring-SoxKnK
Mar 11 11:36:29 talisker gnome-session[330]: ** Message: couldn't access control socket: /run/user/1000/keyring-JQIjZT/control: No such file or directory
Mar 11 11:36:29 talisker gnome-session[330]: ** Message: couldn't access control socket: /run/user/1000/keyring-JQIjZT/control: No such file or directory
Mar 11 11:36:29 talisker metalog[191]: (uid=1000)<86>Mar 11 11:36:18 su[284]: pam_unix(su:session): session closed for user root<28>Mar 11 11:36:29 gnome-session[330]: WARNING: Cou
Mar 11 11:36:29 talisker gnome-session[330]: gnome-session[330]: WARNING: Could not parse desktop file OpenOffice.org 3.4.desktop or it references a not found TryExec binary
|
After this I get hundreds of identical messages, repeating:
| Code: |
Mar 11 11:36:44 talisker gnome-session[330]: DateMenuButton<._updateClockAndDate@/usr/share/gnome-shell/js/ui/dateMenu.js:198
Mar 11 11:36:44 talisker gnome-session[330]: (gnome-shell:418): Gjs-WARNING **: JS ERROR: Error: Argument 'text' (type utf8) may not be null
Mar 11 11:36:43 talisker gnome-session[330]: wrapper@/usr/share/gjs-1.0/lang.js:213
|
I am guessing that the problem is being caused by some aspect of the clock applet (although this is just a guess), or the tweak that placed it in the top right hand corner of my desktop. I can start Gnome 3.10 by removing my configuration (mv .config/dconf/user .config/dconf/user.old) and running startx. This is the result from journalctl -rb; note the lack of the warnings related to utf8 and ClockAndDate.
| Code: |
Mar 11 12:04:46 talisker gnome-session[1096]: Entering running state
Mar 11 12:04:46 talisker gnome-session[1096]: Gjs-Message: JS LOG: GNOME Shell started at Tue Mar 11 2014 12:04:46 GMT-0400 (EDT)
Mar 11 12:04:44 talisker systemd[1]: Started Accounts Service.
Mar 11 12:04:44 talisker dbus-daemon[190]: dbus[190]: [system] Successfully activated service 'org.freedesktop.Accounts'
Mar 11 12:04:44 talisker systemd[1]: Starting Accounts Service...
Mar 11 12:04:44 talisker dbus-daemon[190]: dbus[190]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
Mar 11 12:04:43 talisker systemd[1]: Started Locale Service.
Mar 11 12:04:43 talisker dbus-daemon[190]: dbus[190]: [system] Successfully activated service 'org.freedesktop.locale1'
Mar 11 12:04:43 talisker systemd[1]: Starting Locale Service...
Mar 11 12:04:43 talisker dbus-daemon[190]: dbus[190]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Mar 11 12:04:43 talisker dbus-daemon[190]: dbus[190]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service
Mar 11 12:04:43 talisker dbus-daemon[190]: dbus[190]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Mar 11 12:04:42 talisker pulseaudio[1136]: Stale PID file, overwriting.
Mar 11 12:04:42 talisker metalog[191]: r 11 11:59:02 fcron[1037]: pam_unix(fcron:session): session closed for user root<77>Mar 11 11:59:02 fcron[1039]: Job rm -f /var/spool/cron/la
Mar 11 12:04:42 talisker gnome-session[1096]: GPG_AGENT_INFO=/run/user/1000/keyring-szvOfe/gpg:0:1
Mar 11 12:04:42 talisker gnome-session[1096]: SSH_AUTH_SOCK=/run/user/1000/keyring-szvOfe/ssh
Mar 11 12:04:42 talisker gnome-session[1096]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring-szvOfe
Mar 11 12:04:42 talisker gnome-session[1096]: ** Message: couldn't access control socket: /run/user/1000/keyring-JQIjZT/control: No such file or directory
Mar 11 12:04:42 talisker gnome-session[1096]: SSH_AUTH_SOCK=/run/user/1000/keyring-szvOfe/ssh
Mar 11 12:04:42 talisker gnome-session[1096]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring-szvOfe
Mar 11 12:04:42 talisker gnome-session[1096]: SSH_AUTH_SOCK=/run/user/1000/keyring-szvOfe/ssh
Mar 11 12:04:42 talisker gnome-session[1096]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring-szvOfe
Mar 11 12:04:42 talisker gnome-session[1096]: ** Message: couldn't access control socket: /run/user/1000/keyring-JQIjZT/control: No such file or directory
Mar 11 12:04:42 talisker gnome-session[1096]: ** Message: couldn't access control socket: /run/user/1000/keyring-JQIjZT/control: No such file or directory
Mar 11 12:04:42 talisker gnome-session[1096]: GNOME_KEYRING_PID=1123
Mar 11 12:04:42 talisker gnome-session[1096]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring-szvOfe
Mar 11 12:04:42 talisker gnome-session[1096]: ** Message: couldn't access control socket: /run/user/1000/keyring-JQIjZT/control: No such file or directory
Mar 11 12:04:42 talisker gnome-session[1096]: gnome-session[1096]: WARNING: Could not parse desktop file OpenOffice.org 3.4.desktop or it references a not found TryExec binary
|
Gnome 3.10 works as it should, but of course I have lost all of my configuration. While I would like to solve this problem, I would also be happy to find a way to disable the clock extension (or, at least, progressively disabling the various customisations I have made to Gnome) from the terminal before starting Gnome 3.10 so that at least I can retrieve the remainder of my configuration. How can I do this? Is there a manual with instructions for configuring Gnome 3 through terminal commands?
Thanks very much if you can answer this question or others related.
Craig
Last edited by csteeves on Sun Apr 13, 2014 5:15 pm; edited 2 times in total |
|
| Back to top |
|
 |
VoidMage
Watchman
Joined: 14 Oct 2006
Posts: 6196
|
| Posted: Wed Mar 12, 2014 11:38 am Post subject: |
|
|
| I don't think there is such guide, but I suspect the settings are (almost) lal in dconf, so try playing with gsettings. |
|
| Back to top |
|
|
csteeves
n00b
Joined: 20 Aug 2007
Posts: 61
|
| Posted: Wed Mar 12, 2014 1:41 pm Post subject: |
|
|
| Quote: |
try playing with gsettings
|
Thanks - this is what I was looking for. .config/dconf/user is a binary so I can't modify it directly. If I figure out which extension / tweak / configuration caused Gnome to fail to start, I will post here, but for the moment this will likely provide a workaround.
Craig |
|
| Back to top |
|
|
csteeves
n00b
Joined: 20 Aug 2007
Posts: 61
|
| Posted: Sun Apr 13, 2014 5:14 pm Post subject: |
|
|
The answer was that the tweak tool option to show seconds in the clock was causing Gnome 3.10 not to start. From a terminal (with Gnome and X not running) I used:
| Code: |
dbus-launch gsettings set org.gnome.desktop.interface clock-seconds-show false
|
Relaunching Gnome and turning seconds back on caused the behaviour to recur (ie black screen, but with a movable mouse pointer). Also, all the extensions that I had activated were deactivated. |
|
| Back to top |
|
|
sedorox
Apprentice
Joined: 13 Feb 2004
Posts: 206
|
| Posted: Sat Apr 19, 2014 3:04 pm Post subject: |
|
|
I think this applies here too. I had an issue with a blank/black screen, even with seconds turned off. The fix for me was actually the locales settings.
I've detailed everything in this post: https://forums.gentoo.org/viewtopic-p-7538254.html#7538254
Basically I found that the system locale had to be UTF8, so for me, I had to switch from en_US, to en_US.utf8.
_________________
Home Desktop: Ryzen 3900X 3.8ghz | 32G Ram | 2x 1TB NVMe
Previous 7 Year Build: Intel i5-2400 3.1ghz | 16G Ram | 1x 60G SSD, 1x 1TB HDD |
|
| 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
