Comment 1 for bug 120392

I saw the same behavior, came here to report it, and found this and similar bugs. I had created calendars I could not delete. However, I could not reproduce it until I deleted the calendar manually (by going into the .evolution/calendar/local directory and deleting the directory containing the calendar). Once I did that, I could not delete the calendar. The events did go away on the next start of evolution, and I could then delete the calendar. Starting manually or with a gui entry made no difference.

This problem is triggered by the lack of good documentation for evolution. The docs say what each button does, but that is not good documentation, that is a cop-out. Good documentation describes how a program is used. The problem I had leading up to this was that I thought (and this makes total sense to me as a 20+-year unix user) that I could transport the .evolution directory from one machine to another. This lost most of my calendar entries. I did not know about going into my .evolution and reading the files as ICAL files, because I did not know anything about how evolution stores its data, and this is hidden from the user in the docs. This common problem of how to move calendars from one machine to another should be covered prominently in the docs.

Also, when I converted from FC3 to Ubuntu 7.04, the Personal tasks survived but the Work tasks did not. This may have to do with FC using an FQDN and Ubuntu using just the hostname without the domain as the hostname. I see that the work tasks are there under the FQDN in the .evolution directory, but they have become separated from the application. This behavior should be fixed somehow. Perhaps it should look for calendars in its directory tree that it doesn't know about and ask the user to import them. Now that I know about importing calendars, it seems simple to do manually, but it has been months since I lost my work tasks and I only now learned about what I should have done.

So, I'm confirming this bug:
start evolution
make a calendar
add a task
delete the file containing the task
try to delete the calendar
it won't let you
quit
restart
the task is done and you can delete the calendar.

Suggestions:
1. make it so it can delete the calendar in this case.
2. document how to move calendars from one machine to another in a prominent place. Ditto what happens if machine names change.

--jh--