© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
OK, I've found some weird stuff w/ this problem.
So I log in, and see that the time-zone changes. I go ahead and change it back to America/Chicago.
If I log out, and press Ctrl-Alt-F1 to go to a console and type in "date", it shows me CDT as it should (so the problem doesn't happen on logging out, it's on logging in).
If I log out, and log back in to my same user name (note: I'm not restarting the computer here), I see that the time zone is incorrect again.
However, if I log out of my normal user name "sareen", and log into another account that I created: "guest", the time zone remains as America/Chicago as it should.
If I log out of my normal user name "sareen", and log back into "sareen," then something a bit strange happens. If immediately upon entering my password I press Ctrl-Alt-F1 and go to console, then wait for a few seconds and press Ctrl-Alt-F7 when everything is loaded up in X, then the time zone is America/Chicago as it should be!
So I think it's related to another problem I've been having which I haven't reported yet because I was trying to figure it out a bit. Everytime I log in, gnome-panel crashes with an error similar to https:/
The title of that one is: [hardy] gnome-panel crashed with SIGSEV in clock_map_
The title of mine would've been (based on Apport): gnome-panel crashed with SIGSEGV in clock_map_refresh()
The difference is that they go through the calendar/clock applet to reproduce the crash, mine happens whenever I log in to "sareen" (but never when I log into "guest")
Unfortunately I did not report it, and the dialog which kept asking me to "Report the problem..." is not showing up anymore, even though gnome-panel seems to still be crashing upon login (it appears, disappears, then re-appears). I guess because I had hit "Report the problem..." before but didn't continue on with it. If anyone knows how I can bring that dialog back, I'll report the problem this time and link to that bug report so you can see the automatically generated info.
Then again, I don't know if it still is crashing in the background when I go to Ctrl-Alt-F1 immediately, so that may just be a red herring.