[Gpe-list] Gpe-bugs Digest, Vol 3, Issue 16

Fri Jan 26 12:01:08 CET 2007

Send Gpe-bugs mailing list submissions to
	gpe-bugs at linuxtogo.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/gpe-bugs
or, via email, send a message with subject or body 'help' to
	gpe-bugs-request at linuxtogo.org

You can reach the person managing the list at
	gpe-bugs-owner at linuxtogo.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gpe-bugs digest..."

Today's Topics:

   1. [Bug 35] New: Annual repeating anniversary event does	not
      import/export correctly (bugzilla-daemon at linuxtogo.org)
   2. [Bug 36] New: Event DESCRIPTION does not quote semicolon
      character (bugzilla-daemon at linuxtogo.org)
   3. [Bug 37] New: use of ALARMS crashs gpe-calendar
      (bugzilla-daemon at linuxtogo.org)

----------------------------------------------------------------------

Message: 1
Date: Thu, 25 Jan 2007 16:36:45 +0100
From: bugzilla-daemon at linuxtogo.org
Subject: [Gpe-bugs] [Bug 35] New: Annual repeating anniversary event
	does	not import/export correctly
To: gpe-bugs at linuxtogo.org
Message-ID: <bug-35-7 at http.bugs.linuxtogo.org/>

http://bugs.linuxtogo.org/show_bug.cgi?id=35

           Summary: Annual repeating anniversary event does not
                    import/export correctly
           Product: gpesyncd
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P4
         Component: default
        AssignedTo: gpe-bugs at linuxtogo.org
        ReportedBy: g+gpe at cobb.uk.net
   Estimated Hours: 0.0

After inserting the following VEVENT using gpesyncd, it should appear on 4th
September 2006 in gpe-calendar but does not.  This is probably a problem with
the event parsing library code but it is entered here until I have a chance to
look into it in more detail.

BEGIN:VCALENDAR
VERSION:2.0
PRODID:Graham Cobb's OWA sync V0.6
BEGIN:VEVENT
CATEGORIES:Personal
CATEGORIES:X-OWA
BEGIN:VTIMEZONE
TZID:GMT -0000 (Standard) / GMT +0100 (Daylight)
BEGIN:STANDARD
DTSTART:19671029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZOFFSETFROM:+0100
TZOFFSETTO:-0000
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19670326T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZOFFSETFROM:-0000
TZOFFSETTO:+0100
END:DAYLIGHT
END:VTIMEZONE
DTSTART;VALUE=DATE:19990904
DTEND;VALUE=DATE:19990904
LAST-MODIFIED:20060905T120128Z
CREATED:20000111T235545Z
SUMMARY:Wedding Anniversary
STATUS:TENTATIVE
UID:CD0000008B9511D182D800C04FB1625DDFA911046EC8D3119D9E00A024A9418D
RRULE:FREQ=YEARLY;UNTIL=20400902T230000Z;INTERVAL=1;BYMONTHDAY=4;BYMONTH=9
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-PT86460S
DESCRIPTION:Wedding Anniversary
END:VALARM
END:VEVENT
END:VCALENDAR

Note that when it is read back again, using gpesyncd it appears as:

BEGIN:VEVENT
SUMMARY:Wedding Anniversary
DTEND:19990905
DTSTART:19990904
UID:1168434991.23101061284459 at nokia.home.cobb.me.uk
RRULE:FREQ=YEARLY;UNTIL=19691231;BYDAY=(NULL)
DTSTAMP:20070125T152226Z
LAST-MODIFIED:20070125T042918Z
END:VEVENT
END:VCALENDAR

The UNTIL and BYDAY are both bogus!

Graham

-- 
Configure bugmail: http://bugs.linuxtogo.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

------------------------------

Message: 2
Date: Thu, 25 Jan 2007 18:10:00 +0100
From: bugzilla-daemon at linuxtogo.org
Subject: [Gpe-bugs] [Bug 36] New: Event DESCRIPTION does not quote
	semicolon	character
To: gpe-bugs at linuxtogo.org
Message-ID: <bug-36-7 at http.bugs.linuxtogo.org/>

http://bugs.linuxtogo.org/show_bug.cgi?id=36

           Summary: Event DESCRIPTION does not quote semicolon character
           Product: gpesyncd
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P4
         Component: default
        AssignedTo: gpe-bugs at linuxtogo.org
        ReportedBy: g+gpe at cobb.uk.net
   Estimated Hours: 0.0

The GET VEVENT operation in gpesyncd outputs DESCRIPTION: lines that do not
have semicolon characters quoted.  Commas and newlines are quoted but not
semicolons.

For example, see the following gpesyncd output:

add vevent BEGIN:VCALENDAR
VERSION:2.0
BEGIN:VEVENT
DESCRIPTION:a b\;c\,e
DTEND:20060101T010000Z
DTSTART:20060101T010000Z
END:VEVENT
END:VCALENDAR
OK:1169744839:379

get vevent 379
BEGIN:VCALENDAR
PRODID:-//GNOME//NONSGML MIME Directory Library 0.4.0//EN
VERSION:2.0

BEGIN:VEVENT
DESCRIPTION:a b;c\,e
DTEND:20060101T010000Z
DTSTART:20060101T010000Z
UID:1169744839.39771029980137 at nokia.home.cobb.me.uk
DTSTAMP:20070125T170726Z
LAST-MODIFIED:20070125T170719Z
END:VEVENT
END:VCALENDAR

-- 
Configure bugmail: http://bugs.linuxtogo.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

------------------------------

Message: 3
Date: Thu, 25 Jan 2007 20:38:48 +0100
From: bugzilla-daemon at linuxtogo.org
Subject: [Gpe-bugs] [Bug 37] New: use of ALARMS crashs gpe-calendar
To: gpe-bugs at linuxtogo.org
Message-ID: <bug-37-7 at http.bugs.linuxtogo.org/>

http://bugs.linuxtogo.org/show_bug.cgi?id=37

           Summary: use of ALARMS crashs gpe-calendar
           Product: gpe-calendar
           Version: 0.73rc2
          Platform: Nokia 770
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P4
         Component: default
        AssignedTo: gpe-bugs at linuxtogo.org
        ReportedBy: gary at sharcnet.ca
   Estimated Hours: 0.0

If I add a new entry with an alarm enabled, gpe-calendar will crash at the time
the alarm was to go off.  Adding entries without alarm notification has no
problems.

Further,  if I try to start gpe-cal after an alarm was to have occured, the
first attempt to start the app will always crash.  The second attemp is (so
far) always successful.

-- 
Configure bugmail: http://bugs.linuxtogo.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

------------------------------

_______________________________________________
Gpe-bugs mailing list
Gpe-bugs at linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/gpe-bugs

End of Gpe-bugs Digest, Vol 3, Issue 16
***************************************