** Changed in: gnome-calendar
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906059
Title:
Gnome calendar mishandles timezone during moving across calendars
I've sent that upstream now on https://gitlab.gnome.org/GNOME/gnome-
calendar/-/issues/675
** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/-/issues #675
https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/675
** Changed in: gnome-calendar (Ubuntu)
Status: Confirmed =>
No worry for upstreaming, I've confirmed the issue (or a similar one at
least) on 3.38.1
- on a system configure on an european timezone
- imported that ICS in a new calendar in evolution
https://archive.fosdem.org/2020/schedule/track/history.ics
- evolution displays the events starting at 11am
Sorry I can spend my free time on debuging the issue but not on double
paperwork. There should be automated proces for proxying launchpad content
to upstream
wt., 1 gru 2020, 11:31 użytkownik Sebastien Bacher <
1906...@bugs.launchpad.net> napisał:
> Could you maybe report it directly upstream on
Could you maybe report it directly upstream on gitlab as well too?
** Changed in: gnome-calendar (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906059
No its different issue. My happens during import from ICS file. Syncing
with Google is after that. Regarding your question it doesnt happen whem I
manually create event so its somehow related to how this event is
imtermally stored in way common to gnome-calemdar and Evolution
pon., 30 lis 2020,
Thank you for your bug report. Can you trigger the issue by creating an
event manually or is that, step 1 and the rest of description seem to
somewhat disagree.
It would be nice to also report upstream on
https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues , or at least check
existing issues
