After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 410025 - Session should alert user that clock is completely wrong
Session should alert user that clock is completely wrong
Status: RESOLVED FIXED
Product: gnome-session
Classification: Core
Component: general
2.16.x
Other All
: Normal minor
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-20 14:24 UTC by Joshua Ginsberg
Modified: 2007-05-09 15:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Joshua Ginsberg 2007-02-20 14:24:31 UTC
The clock on my laptop somehow got reset to like 1901, and because of the ridiculous clock skew, bonobo-activation-server just wouldn't work. Nautilus wouldn't launch, the panel would not launch, and all of my applets crashed upon launch. This was bad.

I didn't figure out it was the clock until I poked around for a while on the shell -- since the panel and the clock applet wouldn't launch, I had no way to obviously see the skew. On my Mac, if my clock is seriously skewed it will warn me -- GNOME should do the same thing.

So perhaps if the system clock is set to a month or more before the version of GNOME's release date, gnome-session upon login will provide the user a notice that their clock appears seriously skewed and that it will likely break much of the functionality of the desktop. It probably should offer to launch the system tool for changing the computer's clock setting.

Thanks!

-jag

Other information:
Comment 1 Vincent Untz 2007-05-09 12:37:37 UTC
I committed a dialog to do this. The only thing I'm not sure about is that it's launched late right now (after gnome-settings-daemon is launched), and maybe it should be done sooner.

Do you have the possibility to try GNOME 2.19 and see if it works well?
Comment 2 Dan Winship 2007-05-09 14:17:02 UTC
(In reply to comment #1)
> I committed a dialog to do this. The only thing I'm not sure about is that it's
> launched late right now (after gnome-settings-daemon is launched), and maybe it
> should be done sooner.

Nah. The user might require an accessibility gtk theme (or just a large font
size to deal with his high-res monitor), and that won't be set up until after
g-s-d starts.
Comment 3 Joshua Ginsberg 2007-05-09 14:38:04 UTC
> Do you have the possibility to try GNOME 2.19 and see if it works well?

Not without a lot of pain. I'm running a relatively stock Gnewsense deltad install right now. But if you need this, I'll see what I can do.

-jag
Comment 4 Vincent Untz 2007-05-09 15:57:40 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > I committed a dialog to do this. The only thing I'm not sure about is that it's
> > launched late right now (after gnome-settings-daemon is launched), and maybe it
> > should be done sooner.
> 
> Nah. The user might require an accessibility gtk theme (or just a large font
> size to deal with his high-res monitor), and that won't be set up until after
> g-s-d starts.

Well, that's the reason why I put the call after g-s-d has been started :-) But if everything is broken, gconf might not even start, for example.

(In reply to comment #3)
> > Do you have the possibility to try GNOME 2.19 and see if it works well?
> 
> Not without a lot of pain. I'm running a relatively stock Gnewsense deltad
> install right now. But if you need this, I'll see what I can do.

Ok, it's not a big problem. I did some small tests, and it seemed to work for me. I'd love to see you test this when you get 2.20, though (since you know how broken that was before). Just a sanity check.

Thanks.