Arch Linux

DracoAdvigilat

Member

Registered: 2012-07-29

Posts: 4

GNOME Shell 3.8 crashes when time is set to use AM/PM...?

I'm reaching out to the community here because this one is just confusing me to no end, and I'm hoping someone might have an idea for a fix/work around. Plus, knowing about this might be helpful to some users having problems with the recent upgrade to GNOME 3.8...

To summarize:

1 - GNOME Shell wouldn't load for me, so I wiped my settings by moving everything in my home folder to a backup location.
2 - I began to manually change the settings that I wanted back to what they were before.
3 - After noticing my clock was using a 24 hour clock (e.g. 14:15), I set it to use AM/PM.
4 - The clock didn't update after saving the setting... so I did Alt+F2, r, enter to restart Shell. It crashed.
5 - Trying to log back in gives me nothing but the GNOME Shell login wallpaper and a cursor.

I have tested this again with a brand new user--log in, change the time to use AM/PM, log out, log in again--and have the same results: a cursor, login wallpaper, and nothing else. It looks like--of all things--trying to set the clock to use AM/PM breaks GNOME Shell 3.8. I haven't a clue why.

Anyone have an idea of how to fix this, beyond the obvious "use the 24 hour clock for now" solution?

mbone

Member

Registered: 2012-04-23

Posts: 9

Re: GNOME Shell 3.8 crashes when time is set to use AM/PM...?

When I switched to AM/PM, I'm getting the same problem.  Just prior to this test, I have a similar/if not the same issue when upgrading from 3.6 due to the fact that seconds were enabled via gnome-tweak-tool.  24 hour clock seems to work, but I haven't been able to click on details in gnome-control-center without getting a segfault.

OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
OpenGL Warning: crPixelCopy3D:  simply crMemcpy'ing from srcPtr to dstPtr
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Compat map for group 2 redefined
>                   Using new definition
> Warning:          Compat map for group 3 redefined
>                   Using new definition
> Warning:          Compat map for group 4 redefined
>                   Using new definition
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Compat map for group 2 redefined
>                   Using new definition
> Warning:          Compat map for group 3 redefined
>                   Using new definition
> Warning:          Compat map for group 4 redefined
>                   Using new definition
Errors from xkbcomp are not fatal to the X server
    JS ERROR: !!!   Exception in callback for signal: sessions-loaded
    JS ERROR: !!!     message = '"Argument 'text' (type utf8) may not be null"'
    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/dateMenu.js"'
    JS ERROR: !!!     lineNumber = '211'
    JS ERROR: !!!     stack = '"DateMenuButton<._updateClockAndDate@/usr/share/gnome-shell/js/ui/dateMenu.js:211
wrapper@/usr/share/gjs-1.0/lang.js:213
DateMenuButton<._init@/usr/share/gnome-shell/js/ui/dateMenu.js:153
wrapper@/usr/share/gjs-1.0/lang.js:213
_Base._construct@/usr/share/gjs-1.0/lang.js:154
Class._construct/newClass@/usr/share/gjs-1.0/lang.js:248
Panel<._ensureIndicator@/usr/share/gnome-shell/js/ui/panel.js:1150
wrapper@/usr/share/gjs-1.0/lang.js:213
Panel<._updateBox@/usr/share/gnome-shell/js/ui/panel.js:1161
wrapper@/usr/share/gjs-1.0/lang.js:213
Panel<._updatePanel@/usr/share/gnome-shell/js/ui/panel.js:1112
wrapper@/usr/share/gjs-1.0/lang.js:213
Panel<._init@/usr/share/gnome-shell/js/ui/panel.js:958
wrapper@/usr/share/gjs-1.0/lang.js:213
_Base._construct@/usr/share/gjs-1.0/lang.js:154
Class._construct/newClass@/usr/share/gjs-1.0/lang.js:248
_initializeUI@/usr/share/gnome-shell/js/ui/main.js:150
_sessionsLoaded@/usr/share/gnome-shell/js/ui/main.js:109
_emit@/usr/share/gjs-1.0/signals.js:124
SessionMode<.init/<@/usr/share/gnome-shell/js/ui/sessionMode.js:171
done@/usr/share/gnome-shell/js/misc/fileUtils.js:33
@/usr/share/gnome-shell/js/misc/fileUtils.js:43
"'
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Compat map for group 2 redefined
>                   Using new definition
> Warning:          Compat map for group 3 redefined
>                   Using new definition
> Warning:          Compat map for group 4 redefined
>                   Using new definition
Errors from xkbcomp are not fatal to the X server

Last edited by mbone (2013-04-22 20:11:22)

murffatksig

Member

From: Atl

Registered: 2004-05-17

Posts: 358

Re: GNOME Shell 3.8 crashes when time is set to use AM/PM...?

Ditto here.  When I set the clock off of 24 hour time Gnome wouldn't load.  I wouldn't get any message on the screen, just a black background.  I could switch to ctl+alt+F2 and then read the .xsession-errors and saw the following.  It lead me to realized I had recently turned off 24hour time.  As soon as I turned it back on (via cinnamon, which worked) Gnome worked again.

** (gnome-session-check-accelerated:311): 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.

** (gnome-session:299): 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.
gnome-session[299]: WARNING: Could not parse desktop file /etc/xdg/autostart/xscreensaver.desktop or it references a not found TryExec binary
gnome-session[299]: WARNING: could not read /etc/xdg/autostart/xscreensaver.desktop

** (gnome-settings-daemon:320): 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.

** (gnome-shell:361): 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.
    JS ERROR: !!!   Exception in callback for signal: sessions-loaded
    JS ERROR: !!!     message = '"Argument 'text' (type utf8) may not be null"'
    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/dateMenu.js"'
    JS ERROR: !!!     lineNumber = '211'
    JS ERROR: !!!     stack = '"DateMenuButton<._updateClockAndDate@/usr/share/gnome-shell/js/ui/dateMenu.js:211
wrapper@/usr/share/gjs-1.0/lang.js:213
DateMenuButton<._init@/usr/share/gnome-shell/js/ui/dateMenu.js:153
wrapper@/usr/share/gjs-1.0/lang.js:213
_Base._construct@/usr/share/gjs-1.0/lang.js:154
Class._construct/newClass@/usr/share/gjs-1.0/lang.js:248
Panel<._ensureIndicator@/usr/share/gnome-shell/js/ui/panel.js:1150
wrapper@/usr/share/gjs-1.0/lang.js:213
Panel<._updateBox@/usr/share/gnome-shell/js/ui/panel.js:1161
wrapper@/usr/share/gjs-1.0/lang.js:213
Panel<._updatePanel@/usr/share/gnome-shell/js/ui/panel.js:1112
wrapper@/usr/share/gjs-1.0/lang.js:213
Panel<._init@/usr/share/gnome-shell/js/ui/panel.js:958
wrapper@/usr/share/gjs-1.0/lang.js:213
_Base._construct@/usr/share/gjs-1.0/lang.js:154
Class._construct/newClass@/usr/share/gjs-1.0/lang.js:248
_initializeUI@/usr/share/gnome-shell/js/ui/main.js:150
_sessionsLoaded@/usr/share/gnome-shell/js/ui/main.js:109
_emit@/usr/share/gjs-1.0/signals.js:124
SessionMode<.init/<@/usr/share/gnome-shell/js/ui/sessionMode.js:171
done@/usr/share/gnome-shell/js/misc/fileUtils.js:33
@/usr/share/gnome-shell/js/misc/fileUtils.js:43
"'
    JS ERROR: !!!   Exception was: Error: Argument 'text' (type utf8) may not be null
    JS ERROR: !!!     message = '"Argument 'text' (type utf8) may not be null"'
    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/dateMenu.js"'
    JS ERROR: !!!     lineNumber = '211'
    JS ERROR: !!!     stack = '"DateMenuButton<._updateClockAndDate@/usr/share/gnome-shell/js/ui/dateMenu.js:211
wrapper@/usr/share/gjs-1.0/lang.js:213
"'
    JS ERROR: !!!   Exception was: Error: Argument 'text' (type utf8) may not be null
    JS ERROR: !!!     message = '"Argument 'text' (type utf8) may not be null"'
    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/dateMenu.js"'
    JS ERROR: !!!     lineNumber = '211'
    JS ERROR: !!!     stack = '"DateMenuButton<._updateClockAndDate@/usr/share/gnome-shell/js/ui/dateMenu.js:211
wrapper@/usr/share/gjs-1.0/lang.js:213
"'
gnome-session[299]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.


(gnome-settings-daemon:320): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

---

"Oh, they have the internet on computers now."

donfrenchiano

Member

Registered: 2011-10-22

Posts: 13

Re: GNOME Shell 3.8 crashes when time is set to use AM/PM...?

I'm having the same problem. I even changed the clocked, then logged out and back in and it just doesn't change.

bond0087

Member

Registered: 2013-06-02

Posts: 10

Re: GNOME Shell 3.8 crashes when time is set to use AM/PM...?

I had the same issue. It was a real bitch to figure out that was the reason that my desktop environment wouldn't load. Interestingly enough, I have a few other Arch machines which display AM/PM with gnome shell 3.8 just fine. So after reading a few unrelated bug reports / developer posts, I took a stab in the dark, made a change, and I no longer have the problem. However, I can't say definitively that my change fixed it, because I deleted my entire ~/.config trying to get a working DE again, so a whole lot has changed from when it didn't work and now.
I'm running a Dell Inspiron 620 tower with a Core i3-2320 processor, 64 bit OS, nvidia graphics card, nvidia-ck-sandybridge driver, linux-ck-sandybridge kernel, and everything up to date with gnome shell 3.8

My stab in the dark was to look at the locale on my working machine and the locale on the machine which crashed gnome shell with the AM/PM change. On the working machine, the output of

 locale 

was :

 LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

When I ran locale on the machine with this problem, I got something like this:

 LANG=C
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=

So I went back and fixed the locale (I think that I must have skipped this step on this machine during installation or something). For some reason the changes didn't seem to take effect when I was working in a gnome-terminal session (I would try to change it, it would act normally, but then it would give me the same output when I typed locale) When I did CTRL+ALT+F2 and logged in as root, everything worked as expected, and locale run in a gnome-terminal looked right. I'm 99% sure that that's another story, though.

Anyway, after that, the locale settings displayed as expected, and I crossed my fingers, clicked the AM/PM button, and voila, it worked. 

So anyway, not sure if this is the fix or not, but it seems plausible until proven otherwise.

My half-baked working theory when I checked the locale was that gnome-shell might use the locale settings for the AM/PM label, and not handle unexpected locales gracefully. No clue if that theory holds water or not, but I was much less interested in learning than I was interested in having a working DE again, so I didn't do much research.

Last edited by bond0087 (2013-06-02 21:49:34)

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 19,771

Re: GNOME Shell 3.8 crashes when time is set to use AM/PM...?

I had the same problem when I tried to enable seconds on my clock.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

comeandtakeit

Member

Registered: 2013-06-07

Posts: 5

Re: GNOME Shell 3.8 crashes when time is set to use AM/PM...?

That fixed it!  Bond0087, thanks for sharing.  I was banging my head against for wall for about 3 days trying to figure this out.

mickours

Member

Registered: 2013-01-11

Posts: 6

Re: GNOME Shell 3.8 crashes when time is set to use AM/PM...?

only remove old config like this:

rm -R ~/.config/gnome-session

and it works fine!

Maybe it's packaging bug of gnome-session...