Bug#730160: solved: really bad bug

Wendy J. Elmer webe3vt at aim.com
Mon Nov 25 02:11:12 UTC 2013


I figured out what the problem is.  This is a really bad bug.  I had my
time setting in the date and time settings set to am/pm when I upgraded
to gnome-shell 3.8 in jessie.  When I changed it to 24 hour, gnome
started.  I found this on google that helped me figure it out.
https://bbs.archlinux.org/viewtopic.php?pid=1281584

What helped me find the fix was by looking in my session.log file and
finding this:

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 = '212'
    JS ERROR: !!!     stack = '"([object GObject_Object],[object
GObject_ParamSpec])@/usr/share/gnome-shell/js/ui/dateMenu.js:212


am/pm time worked fine with gnome 3.4 that was in jessie before 3.8 was
moved there.  I don't know if is is specific to certain hardware or
setup or what but it has potential to be very bad for people that
upgrade to gnome 3.8 with their time set to am/pm.

Brent
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20131124/d24a13bd/attachment.html>


More information about the pkg-gnome-maintainers mailing list