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 667886 - Save as CSV broken for Google calendar: Prints first line repeatedly
Save as CSV broken for Google calendar: Prints first line repeatedly
Status: RESOLVED DUPLICATE of bug 663615
Product: evolution
Classification: Applications
Component: Calendar
3.2.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2012-01-13 18:22 UTC by Steve
Modified: 2012-01-14 15:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Steve 2012-01-13 18:22:00 UTC 
I have a gmail calendar attached in Evolution. In the past, I could right click the calendar and choose "Save As", set the format as CSV, and save the calendar. I have several applications that run against these csv files for time reporting, etc. It no longer works. 

When doing the above process, I now get a csv export with 3123 lines, yet every line in the file is the same. I get 3123 of the following:

20080909T123312Z-9437-500-1-1183@t60.localhost.com, IFX - ADS1 - siezed FSMO rolls from ads1 to ads2 - backed up ad on ads2 - set up IAS / DHCP on ads2 - force demote ads1 - clean metadata - imported phone info into exch - rebuilt drive in san - john h treo, , , , , 2008-09-09 12:31:47, , 2007-02-13 14:45:00, 2007-02-13 21:45:00, , , , , , , 1970-01-01 00:00:00

The above is an appointment from 2007 with a client. 

I have been using the calendaring system in Evolution since May of 2003 so there is a lot of historical data in there converting it into a gmail account when I moved to Andriod on my phone. Everything worked fine before upgrading to Fedora 16 with Evolution 3.2.2
Comment 1 André Klapper 2012-01-14 13:33:24 UTC 
Confirming (same line repeated all over)
Comment 2 Matthew Barnes 2012-01-14 15:00:34 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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