[Akonadi] [Bug 318558] New: Endless loop fetching ICAL file from HTTPS when created read-only

David M. eewixaew at abanbytes.eu
Thu Apr 18 16:44:58 BST 2013


https://bugs.kde.org/show_bug.cgi?id=318558

            Bug ID: 318558
           Summary: Endless loop fetching ICAL file from HTTPS when
                    created read-only
    Classification: Unclassified
           Product: Akonadi
           Version: 1.9.1
          Platform: Archlinux Packages
               URL: http://pastebin.com/5sjafzez
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: ICal file resource
          Assignee: kdepim-bugs at kde.org
          Reporter: eewixaew at abanbytes.eu

I just tried creating a new calender in KOrganizer, selecting "ICal calendar
file" option.

As filename, I specified
"https://tiss.tuwien.ac.at/events/ical.xhtml?locale=de&token=my-top-secret-calendar-token"
with my real calendar token for the web service. I gave it a name, selected
"Read only" for "Access rights" and clicked OK.

After the procedure described below, there is a lot of disk and network I/O and
the appointments are "blinking" (appearing and disappearing) in KOrganizer.
Task manager shows akonadi and its mysql minions are responsible.

Somehow somewhere Google said

$ kcmshell4 kcm_akonadi

and that output a whole train of debug stuff with parse errors, it's in the URL
attached.

Checks that are OK:
Upon manual HTTPS request, the file looks like a regular ICAL text format and
has 1603 lines.
Upon ICal import of the saved file, all entries seem to get imported without
trouble.
If I import without selecting "Read only", the import works without trouble (no
extensive disk or network I/O).


Reproducible: Always

Steps to Reproduce:
1. Open KOrganizer
2. Settings -> Configure KOrganizer...
3. General page -> Calendars tab
4. Add...
5. pick "ICal calendar file"
6. As filename, specify
"https://tiss.tuwien.ac.at/events/ical.xhtml?locale=de&token=my-top-secret-calendar-token"
with my real calendar token for the web service.
7. (Give it a name)
8. select "Read only" for "Access rights"
9. Click OK
Actual Results:  
Calendar is created. There is a lot of disk and network I/O and the
appointments are "blinking" (appearing and disappearing) in KOrganizer. Task
manager shows akonadi and its mysql minions are responsible.

Expected Results:  
Create a calendar based on the remote ICAL file from HTTP, hopefully update it
in some time interval. Not request the ICAL file every second and parse it over
and over.

Needs a web service which provides ICAL files via HTTP.

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Kdepim-bugs mailing list