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 599424 - Lost data trying to move events from default calendar to another
Lost data trying to move events from default calendar to another
Status: RESOLVED DUPLICATE of bug 529331
Product: evolution
Classification: Applications
Component: Calendar
2.28.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-10-23 18:06 UTC by Thomas
Modified: 2009-10-26 05:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Thomas 2009-10-23 18:06:35 UTC
I could not reproduce this so far. I used a search to filter out events which had
certain category tags on it. Then I used the list view to see all remaining events. I used the right-mouse pop-up menu and "...move to calendar" to move these events from the default calendar to a different calendar. I first tried to select multiple events via Shift-Click, but that would move only one item anyway.
Having finished all my moving clicking to different months and coming back, certain events were gone. I closed evolution, even via the "--force shutdown" command line, reopened it and the events were gone. I used a grep on the ics files to confirm that the data was indeed gone. Then I re-imported the data from a backup and tried to reproduce this but could not.
Comment 1 Thomas 2009-10-24 01:49:28 UTC
Just tried again, and the reason was, that I moved the item to the same calendar, inadvertantly. But the data was definitely lost, I verified again.
Comment 2 Akhil Laddha 2009-10-26 05:05:42 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 529331 ***