From: "Ludovic Courtès" <ludo@gnu.org>
To: Ben Sturmfels <ben@sturm.com.au>
Cc: 35746@debbugs.gnu.org
Subject: bug#35746: Evolution calendar gets the timezone wrong
Date: Thu, 16 May 2019 13:13:46 +0200 [thread overview]
Message-ID: <87y336hct1.fsf@gnu.org> (raw)
In-Reply-To: <8736lfrh6y.fsf@sturm.com.au> (Ben Sturmfels's message of "Wed, 15 May 2019 23:16:37 +1000")
Hi Ben,
Ben Sturmfels <ben@sturm.com.au> skribis:
> In Evolution though, all my calendar events show up in UTC time, so I
> have appointments showing up at eg. 1am.
>
> When I go to Edit, Preferences, Calendar and Task, General, under
> timezone it says:
>
> [x] Use system time (UTC)
Could you figure out how Evolution determines what the current time zone
is?
Guix provides /etc/localtime, which is what libc functions use, but I’m
guessing Evolution uses a custom framework, possibly involving a
hard-to-believe network of D-Bus services.
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-05-16 11:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 13:16 bug#35746: Evolution calendar gets the timezone wrong Ben Sturmfels
2019-05-16 11:13 ` Ludovic Courtès [this message]
2019-05-16 12:57 ` Ben Sturmfels
2019-05-16 13:18 ` Ben Sturmfels
2019-05-16 13:23 ` Ben Sturmfels
2019-05-16 17:18 ` Danny Milosavljevic
2019-05-17 9:02 ` bug#35746: IceCat/Chromium timezone is wrong Ludovic Courtès
2020-04-22 13:02 ` Ben Sturmfels
2020-04-22 13:43 ` Ben Sturmfels
[not found] ` <875zdrd4vv.fsf@sturm.com.au>
2020-04-22 15:13 ` Ludovic Courtès
2019-05-18 17:51 ` bug#35746: Evolution calendar gets the timezone wrong Ludovic Courtès
2019-09-12 10:00 ` Ludovic Courtès
2019-09-12 13:45 ` Ben Sturmfels
2019-05-18 17:21 ` Timothy Sample
2019-05-18 18:43 ` Timothy Sample
2019-05-19 21:17 ` sirmacik
2019-09-12 10:05 ` Ludovic Courtès
2020-02-06 11:27 ` Ben Sturmfels
2020-05-05 5:01 ` bug#35746: (no subject) Ben Sturmfels via web
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y336hct1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35746@debbugs.gnu.org \
--cc=ben@sturm.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).