[Bug 954161] New: The Gnome/Evolution Calendar mix years
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 Bug ID: 954161 Summary: The Gnome/Evolution Calendar mix years Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: i686 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome@forge.provo.novell.com Reporter: iron.bone@wp.pl QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- When added a Google account to Gnome. The Gnome Calendar(in the clock) and the Evolution calendar mix years. In a given day (say 11.01.2015) shows events from all other years i.e. 11.01.2014, 11.01.2013 ...... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 Iron Bone <iron.bone@wp.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iron.bone@wp.pl Target Milestone|--- |Leap 42.1 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 http://bugzilla.opensuse.org/show_bug.cgi?id=954161#c1 Bjørn Lie <zaitor@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zaitor@opensuse.org Flags| |needinfo?(iron.bone@wp.pl) --- Comment #1 from Bjørn Lie <zaitor@opensuse.org> --- Would you mind doing a screenshot of this? Also add some more info on how to reproduce (type of event, how it was "set", and whatever more info you can give). I'm unable to reproduce your issue, so looking a bit in the blind here. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 http://bugzilla.opensuse.org/show_bug.cgi?id=954161#c2 --- Comment #2 from Iron Bone <iron.bone@wp.pl> --- Created attachment 655371 --> http://bugzilla.opensuse.org/attachment.cgi?id=655371&action=edit My online acount config -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 http://bugzilla.opensuse.org/show_bug.cgi?id=954161#c3 --- Comment #3 from Iron Bone <iron.bone@wp.pl> --- Created attachment 655372 --> http://bugzilla.opensuse.org/attachment.cgi?id=655372&action=edit Calendar in Gonome -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 http://bugzilla.opensuse.org/show_bug.cgi?id=954161#c4 --- Comment #4 from Iron Bone <iron.bone@wp.pl> --- Created attachment 655373 --> http://bugzilla.opensuse.org/attachment.cgi?id=655373&action=edit Calendar in Google - the same day -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 http://bugzilla.opensuse.org/show_bug.cgi?id=954161#c5 --- Comment #5 from Iron Bone <iron.bone@wp.pl> --- After checking, I can see that the additional items are not exactly from the same day and different years. They are just from other days. Sometimes 6 years ago. See the attached screen-shot with my configuration, the Gnome calender from 9/11 and the Google calender from 9/11 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 http://bugzilla.opensuse.org/show_bug.cgi?id=954161#c6 --- Comment #6 from Iron Bone <iron.bone@wp.pl> --- But the pop-up messages in gnome seams to be connected only with current items. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 http://bugzilla.opensuse.org/show_bug.cgi?id=954161#c7 Robin Roevens <robin.roevens1@pandora.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |robin.roevens1@pandora.be Flags|needinfo?(iron.bone@wp.pl) | --- Comment #7 from Robin Roevens <robin.roevens1@pandora.be> --- I'm seeing this too It appears both on all my google calendars as well as the company's exchange server (owa connected using Gnome online accounts).. So it doesn't seem to be google or calendar-type specific. I see this problem on all my LEAP installed computers/laptops. The Tumbleweed version of Evolution doesn't seem to have this problem however. I also narrowed down what type of events causes this: All recurring events that are defined as "repeat x days/weeks/months/years for _X instances_" are repeated forever by evolution instead of only for the defined X instances. When the events are defined to repeat until a certain date, they do correctly stop repeating after that certain date. So it seems that Evolution as it is provided by LEAP 42.1 ignores the "for X instances" setting of recurring events and treads them as "repeating for eternity"-type recurring events. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 Robin Roevens <robin.roevens1@pandora.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Hardware|i686 |x86-64 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P5 - None CC| |dimstar@opensuse.org -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 http://bugzilla.opensuse.org/show_bug.cgi?id=954161#c8 --- Comment #8 from Robin Roevens <robin.roevens1@pandora.be> --- Please set this bug to a higher priority as this currently causes evolution calendering to be completely useless when repeating events where created in the past. My current overview containing a 4-some calenders from different sources causes every day to be filled with 5 to 10 items, very slow responsiveness and very frequent calendar backend crashed-messages , probably caused by this hughe amount of faulty displayed repeating items. There even is no workaround for this. Changing past recurring events to not repeat 'for X days' but 'until a set date' is not a functional workaround as many of those items are created as meeting requests by other persons for which I don't have access rights to change the events. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 http://bugzilla.opensuse.org/show_bug.cgi?id=954161#c9 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #9 from Dominique Leuenberger <dimstar@opensuse.org> --- (In reply to Robin Roevens from comment #8)
Please set this bug to a higher priority as this currently causes evolution calendering to be completely useless when repeating events where created in the past.
Feel free to work on it - then you can assign youself the priority you want. There is actually a good chance that libical 1.0 is at fault here too - we had seen identified other bugs caused by it. please test to upgrade based on the repository:; http://download.opensuse.org/repositories/home:/fcrozat:/branches:/openSUSE:... And report back -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 http://bugzilla.opensuse.org/show_bug.cgi?id=954161#c10 Robin Roevens <robin.roevens1@pandora.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #10 from Robin Roevens <robin.roevens1@pandora.be> --- (In reply to Dominique Leuenberger from comment #9)
Feel free to work on it - then you can assign youself the priority you want.
Thanks for that gentle reminder. If I would have had the possibilities, knowledge and capabilities I would have certainly done that, but that is currently not the case. I already tried cooperating the best I can by analyzing the problem and provide as much relevant information as possible for those with the correct knowledge and/or capabilities (#c7). And I offer further cooperation in finding the cause for this problem by testing and/or providing any additional information if I know what to test or provide.. But absolutely no reaction came in over a month of time, hence I tried shaking the tree a bit since this bug looks too serious and visible for an "enterprise-grade stable" distro as Leap is supposed to be. And I didn't think it would be too hard to fix as Tumbleweed does not have this problem. Only the right person has had to give it a look..
There is actually a good chance that libical 1.0 is at fault here too - we had seen identified other bugs caused by it.
please test to upgrade based on the repository:; http://download.opensuse.org/repositories/home:/fcrozat:/branches:/openSUSE:... Leap:/42.1:/Update/standard/
And report back
And it seems you where that right person since I upgraded the packages from that repo per your suggestion and indeed this seems to fix the problem. I no longer see the recurring events from the past. Also browsing the calendar in evolution now is again quite fluent without constantly crashing the calendar back-ends. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 http://bugzilla.opensuse.org/show_bug.cgi?id=954161#c11 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Assignee|bnc-team-gnome@forge.provo. |fcrozat@suse.com |novell.com | --- Comment #11 from Dominique Leuenberger <dimstar@opensuse.org> --- assigning to fcrozat: your evo/ical branch has been tested to solve this issue here. Would be nice to get that stack released as maintenance updated -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 http://bugzilla.opensuse.org/show_bug.cgi?id=954161#c12 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sreeves@suse.com Flags| |needinfo?(sreeves@suse.com) --- Comment #12 from Frederic Crozat <fcrozat@suse.com> --- Scott, could somebody in your team have a look at libical update for SLE12 to 1.0.1, so it would be propagated to Leap ? We have to be careful because it looks like ABI is somehow broken between 1.0 and 1.0.1, we need to fix this : according to Milan Chra (evolution upstream developer): <@mcrha> it still can be a libical issue, there had been an issue with enum generation, new build could reorder the enum values, which caused misbehaviour (similar to yours). Unless the libical was fixed (to preserver the order in some way), each time libical was rebuild all users of it should be rebuild too. If we are taling about 3.16.5, then it basically matches the time frame Thanks ! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 http://bugzilla.opensuse.org/show_bug.cgi?id=954161#c13 --- Comment #13 from Iron Bone <iron.bone@wp.pl> ---
please test to upgrade based on the repository:; http://download.opensuse.org/repositories/home:/fcrozat:/branches:/openSUSE:... Leap:/42.1:/Update/standard/
And report back
It works well for me -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954161 http://bugzilla.opensuse.org/show_bug.cgi?id=954161#c14 Scott Reeves <sreeves@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|fcrozat@suse.com |mgorse@suse.com Flags|needinfo?(sreeves@suse.com) | --- Comment #14 from Scott Reeves <sreeves@suse.com> --- Mike - as we discussed can you look into this. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com