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 515998 - It isn't possible to remove a calendar
It isn't possible to remove a calendar
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.12.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 480552 508387 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-02-12 12:22 UTC by Martin Picek
Modified: 2009-04-02 18:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Attachments
proposed evo patch (2.34 KB, patch)
2008-02-14 12:49 UTC, Milan Crha
rejected Details | Review
proposed eds patch (6.33 KB, patch)
2008-06-18 14:22 UTC, Milan Crha
committed Details | Review

Description Martin Picek 2008-02-12 12:22:35 UTC
Please describe the problem:
I can't remove my calendars, stored on my computer (not on WWW, etc.).

I get a window "Do you really want to remove..." (or something similar) but after  confirmation, the calendar is still present...

The problems started when I copied one calendar to other one. Every events were duplicated but they had some dependencies on themselves (new event in one calendar were created in the second one too, removing an event from one calendar caused removing the "second" event from the second calendar, etc.).

I can remove new calendars (created after this problem) but the old ones not.

(I think some Evolution's internal data are broken...)

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 André Klapper 2008-02-12 13:00:33 UTC
> The problems started when I copied one calendar to other one.
within evolution? or on the file system?

which distro, which exact version?
Comment 2 Martin Picek 2008-02-12 13:26:20 UTC
Within Evolution (no my own manipulating with Evolution's files).

Ubuntu 7.10 Gutsy Gibbon, GNOME 2.20.1, Evolution 2.12.1.
Comment 3 André Klapper 2008-02-12 13:39:44 UTC
now if you could describe what exactly you did...? ;-)
Comment 4 Martin Picek 2008-02-12 15:37:33 UTC
OK, in points:

 1. I copied whole calendar A to calendar B (through right click on the cal.)
 2. cal. B had all events from cal. A (everything OK)
 3. but it wasn't possible to remove cal. A
 4. so I tried to remove the events manually
 5. but removing of event C (from the cal. A) caused removing of event C' (from the cal. B)
 6. it wasn't still possible to remove cal. A (it was empty at the time)
 7. if I created an event in cal. B, the event was created in cal. A too

I hope this description will help you better (I'm not so good in English)...
Comment 5 Martin Picek 2008-02-12 15:39:34 UTC
By the way... I couldn't (now I can) change the calendar's color too.
Comment 6 Milan Crha 2008-02-14 12:42:12 UTC
Logic in code is that if we cannot remove calendar from our storage, then we will not remove it from source list either. I think this can be changed.
Comment 7 Milan Crha 2008-02-14 12:49:18 UTC
Created attachment 105228 [details] [review]
proposed evo patch

for evolution;

Maybe it's not good idea, I'm not sure. Let Chen decide.
Comment 8 Srinivasa Ragavan 2008-02-19 18:37:29 UTC
Chen.. before 2.21.91?
Comment 9 Chenthill P 2008-04-29 13:23:43 UTC
I think it should be ok to do this. Please commit the patch.
Comment 10 Chenthill P 2008-04-29 13:25:27 UTC
Nope sorry, it might cause problems with calendars which should not be removed. Like for example, exchange calendars cannot be removed in offline. The fix should be made at the backend. It is good to print the error message received while remove cal.
Comment 11 Milan Crha 2008-06-18 14:22:56 UTC
Created attachment 112983 [details] [review]
proposed eds patch

for evolution-data-server;

So the backend takes care of this. I can create similar patch for exchange too, but I guess it's not required there.
Comment 12 Milan Crha 2008-07-17 12:24:27 UTC
*** Bug 508387 has been marked as a duplicate of this bug. ***
Comment 13 Chenthill P 2008-07-17 14:15:33 UTC
The patch looks good. Just a small thought, is it good to notify a error message to the user that some happened wrong there ?
Comment 14 Milan Crha 2008-07-18 14:06:04 UTC
Committed to trunk. Committed revision 9134.

It prints the info on the console (which is nothing special, I know), but is there any option to report success and also show a message? Also, we do not know the exact error anyway, so what would you show there? :)
Comment 15 Milan Crha 2009-04-02 18:34:11 UTC
*** Bug 480552 has been marked as a duplicate of this bug. ***