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 537445 - Start of week in applet does not match Evolution's settings
Start of week in applet does not match Evolution's settings
Status: RESOLVED DUPLICATE of bug 270578
Product: evolution
Classification: Applications
Component: Calendar
2.12.x (obsolete)
Other All
: Normal enhancement
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-06-09 17:40 UTC by Jacob
Modified: 2010-10-14 06:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2


Description Jacob 2008-06-09 17:40:44 UTC 
Please describe the problem:
The clock applet, which I believe is part of the Evolution suite, does not follow the start_of_week Evolution setting found in gconf.

Steps to reproduce:
Just try and change the starting day of the week...

Actual results:
...and notice how the applet doesn't follow along.

Expected results:
The applet should update so that the start of the week is on Sunday when start_of_week is set to 0 instead of (in my case) Monday.

Does this happen every time?
You bet.

Other information:
Running Gentoo 2007.0, fully updated.
Comment 1 Akhil Laddha 2008-06-10 04:40:01 UTC 
Evolution is integrated with clock applet for just to show events and alarm pop ups. You cann't change/sync clock applets settings from evolution.
Comment 2 Jacob 2008-06-10 12:20:38 UTC 
Well, the request for a way to change that for the applet at least is still valid.

If there's already another bug report like this, please refer me to it so I can watch it. Thanks!
Comment 3 Havard Bjastad 2008-09-10 14:28:00 UTC 
Jacob, check out http://bugzilla.gnome.org/show_bug.cgi?id=401053
Comment 4 Jacob 2008-09-10 15:12:02 UTC 
Thanks Havard for pointing that out. I've added my comments there.

I think the reason this bug is taking so long to fix is because it requires a bigger group of people besides just one or two to decide on a proper solution.
Comment 5 Milan Crha 2010-10-14 06:54:39 UTC 

*** This bug has been marked as a duplicate of bug 270578 ***