[MeeGo Projects - Bug 10092] New: Sony Ericsson doesnt handle repeat-rule: until in vevent
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=10092
Summary: Sony Ericsson doesnt handle repeat-rule: until in
vevent
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: karlrt(a)gmx.net
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
Created an attachment (id=3534)
--> (http://bugs.meego.com/attachment.cgi?id=3534)
with this file, SE wont use the repeat-values
BUILD IMAGE: 1.1-2
HARDWARE MODEL (on what HW this bug is uncovered): Sony Ericsson t700 in sync
with ubuntu 10.10 on thinkpad t61
BUG DETAILED DESCRIPTIONS
===========================================================
EXACT STEPS LEADING TO PROBLEM:
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
===========================================================
1.make a repeated event without a repeat end (see attachment)
2.sync it with mobilephone --> SE sees it as a repeated event
3.make a repeated event with an end
4.sync it with mobilephone
5.Not one repeat is shown
EXPECTED OUTCOME:
===================
SE should show repeated alarms also with an "until" value assigned
ACTUAL OUTCOME:
===================
SE doesnt show any repeated events, just the root-event
USER IMPACT:
===================
Cannot use repeated events for my sync
REPRODUCIBILITY:
(always, less than 1/10, 5/10, 9/10)
=====================================
EXTRA SOFTWARE INSTALLED:
============================
OTHER COMMENTS:
===================
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
11 years, 4 months
[MeeGo Projects - Bug 10270] New: [Wishlist] Have a single command for http-server
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=10270
Summary: [Wishlist] Have a single command for http-server
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ALL
Status: NEW
Severity: enhancement
Priority: Medium
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: meego(a)misc.lka.org.lu
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
BUILD IMAGE(X.X.XX.X.XXXXXXXX.X - (e.g.:
meego-netbook-ia32-1.0.90.0.20100831.1)):
Syncevolution 1.1
HARDWARE MODEL (on what HW this bug is uncovered):
PC
BUG DETAILED DESCRIPTIONS
===========================================================
Currently, for starting syncevolution as a http server, 2 commands must be
launched:
1. syncevolution-1.1/src/syncevo-dbus-server
2. syncevo-http-server
Apparently (unless I miss something), the only thing that the
syncevo-http-server frontend does is translate from http to dbus, and the
actual "work" is done by syncevo-dbus-server.
What is the purpose of this? Easy availability of an embeddable http server in
Python (twisted), but not in C++?
I've been googling around a bit, and came across libmicrohttpd:
http://www.gnu.org/software/libmicrohttpd/
This allows to embed a http server in any C or C++ application. Maybe this
would simplify usage of syncevolution in http server mode somewhat?
EXACT STEPS LEADING TO PROBLEM:
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
===========================================================
Not applicable
EXPECTED OUTCOME:
===================
A single executable for http server
ACTUAL OUTCOME:
===================
Currently, two programs must be launched to set up syncevolution in http server
mode.
USER IMPACT:
===================
Greater complexity.
REPRODUCIBILITY:
(always, less than 1/10, 5/10, 9/10)
=====================================
Always
EXTRA SOFTWARE INSTALLED:
============================
OTHER COMMENTS:
===================
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
11 years, 4 months
[MeeGo Projects - Bug 10031] New: syncevo-http-server: needs to be restarted after loss of connection
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=10031
Summary: syncevo-http-server: needs to be restarted after loss
of connection
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: patrick.ohly(a)intel.com
ReportedBy: patrick.ohly(a)intel.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
Originally reported on mailing list:
From: Valerio Pachera <>
To: syncevolution(a)syncevolution.org <syncevolution(a)syncevolution.org>
Subject: [SyncEvolution] Missing close function
Date: Fri, 5 Nov 2010 16:17:43 +0000 (05.11.2010 17:17:43)
Situation: syncevolution 1.1 on debian squeeze running as server.
Problem: stopping syncronization from mobile cause the following dbus error:
---
POST from 94.161.35.23 config type application/vnd.syncml+wbxml
session None args {} length 300
requesting new session
connection /org/syncevolution/Connection/2891296861288973221 went down
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 214, in
maybe_handle_message
self._handler(*args, **kwargs)
File "/usr/bin/syncevo-http-server", line 68, in abort
self.destruct(http.INTERNAL_SERVER_ERROR, "lost connection to
SyncEvolution")
File "/usr/bin/syncevo-http-server", line 60, in destruct
self.connection.Close(False, message)
File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
**keywords)
File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 630, in
call_blocking
message, timeout)
DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method
"Close" with signature "bs" on interface
"org.syncevolution.Connection" doesn't exist
SessionChanged: /org/syncevolution/Session/2891296861288973221 0
Unhandled error in Deferred:
Traceback (most recent call last):
Failure: twisted.internet.error.ConnectionDone: Connection was closed cleanly.
SessionChanged: /org/syncevolution/Session/17488680671288973222 1
reply session 17488680671288973222 final 0 data len 2675
dbus.Dictionary({dbus.UTF8String('URL'): dbus.UTF8String('')},
signature=dbus.Signature('ss'))
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 214, in
maybe_handle_message
self._handler(*args, **kwargs)
File "/usr/bin/syncevo-http-server", line 84, in reply
request.finish()
File "/usr/lib/python2.6/dist-packages/twisted/web/http.py", line
900, in finish
"Request.finish called on a request after its connection was lost; "
RuntimeError: Request.finish called on a request after its connection
was lost; use Request.notifyFinish to keep track of this.
---
The only way to make it work again is to reboot the machine.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
11 years, 4 months
[Bug 5819] New: syncevo-dbus-server: does not honor disabling of autosync
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=5819
Summary: syncevo-dbus-server: does not honor disabling of
autosync
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: major
Priority: High
Component: SyncEvolution
AssignedTo: yongsheng.zhu(a)intel.com
ReportedBy: patrick.ohly(a)intel.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
BUILD IMAGE(yyyy-mm-dd): MeeGo 1.0
HARDWARE MODEL (on what HW this bug is uncovered): na
BUG DETAILED DESCRIPTIONS
===========================================================
Enable automatic syncing. To simplify testing, set autoSyncInterval to
something small (1 min). Disable automatic syncing. Automatic syncing
continues.
EXACT STEPS LEADING TO PROBLEM:
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
===========================================================
1. syncevolution --configure --sync-property autoSync=1 --sync-property
autoSyncDelay=0 --sync-property autoSyncInterval=1m <config>
2. wait until syncing starts
3. syncevolution --configure --sync-property autoSync=0 <config>
EXPECTED OUTCOME:
===================
No more automatic syncs.
ACTUAL OUTCOME:
===================
Syncing continues at the selected interval.
Yongsheng, do you have time to look into this?
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
11 years, 4 months
[MeeGo Projects - Bug 6898] New: Backend: notebook missing in KCal backend
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=6898
Summary: Backend: notebook missing in KCal backend
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: normal
Priority: Medium
Component: SyncEvolution
AssignedTo: qiankun.miao(a)intel.com
ReportedBy: qiankun.miao(a)intel.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
Now, notebook is not available in KCal backend. Notebook can be used to
distinguish different types of calender/todo. It describes an item and allows
operating many items with the same notebook meanwhile. Items can be saved into
different databases according its notebook, which is useful.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
11 years, 4 months
[Bug 6369] New: Error reporting in HTTP server is sucky (Or: HTTP server ignores LogOutput dbus signals)
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=6369
Summary: Error reporting in HTTP server is sucky (Or: HTTP
server ignores LogOutput dbus signals)
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: matthijs(a)stdin.nl
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
I've been trying to get the HTTP server running, but I got the following output
after connecting with a client.
matthijs@login:~$ syncevo-http-server http://localhost:9000/sync
POST from 178.226.74.128 config type application/vnd.syncml+wbxml session None
args {} length 1795
requesting new session
SessionChanged: /org/syncevolution/Session/7414306401283853336 1
connection /org/syncevolution/Connection/7414306401283853336 went down
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/var/lib/python-support/python2.5/dbus/connection.py", line 214, in
maybe_handle_message
self._handler(*args, **kwargs)
File "/usr/bin/syncevo-http-server", line 68, in abort
self.destruct(http.INTERNAL_SERVER_ERROR, "lost connection to
SyncEvolution")
File "/usr/bin/syncevo-http-server", line 60, in destruct
self.connection.Close(False, message)
File "/var/lib/python-support/python2.5/dbus/proxies.py", line 140, in
__call__
**keywords)
File "/var/lib/python-support/python2.5/dbus/connection.py", line 607, in
call_blocking
message, timeout)
DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Close" with
signature "bs" on interface "org.syncevolution.Connection" doesn't exist
This seems like there is something wrong with the dbus interface specs or
something. However, it turns out there is a really simple configuration
problem. Running dbus-monitor shows the real error (the first two signals are
relevant).
signal sender=:1.46 -> dest=(null destination) path=/org/syncevolution/Server;
interface=org.syncevolution.Server; member=LogOutput
object path "/org/syncevolution/Session/7414306401283853336"
string "SHOW"
string "First ERROR encountered: no sources active, check configuration"
signal sender=:1.46 -> dest=(null destination) path=/org/syncevolution/Server;
interface=org.syncevolution.Server; member=LogOutput
object path "/org/syncevolution/Session/7414306401283853336"
string "SHOW"
string "
"
signal sender=:1.46 -> dest=(null destination) path=/org/syncevolution/Server;
interface=org.syncevolution.Server; member=LogOutput
object path "/org/syncevolution/Session/7414306401283853336"
string "DEBUG"
string "done with connection to 'syncevo-server-http.py (HTTP)'
unexpectedly"
signal sender=:1.46 -> dest=(null destination)
path=/org/syncevolution/Connection/7414306401283853336;
interface=org.syncevolution.Connection; member=Abort
signal sender=:1.46 -> dest=(null destination)
path=/org/syncevolution/Session/7414306401283853336;
interface=org.syncevolution.Session; member=StatusChanged
string "done"
uint32 10500
array [
dict entry(
string "addressbook"
struct {
string "none"
string "idle"
uint32 0
}
)
dict entry(
string "calendar"
struct {
string "none"
string "idle"
uint32 0
}
)
dict entry(
string "memo"
struct {
string "none"
string "idle"
uint32 0
}
)
dict entry(
string "todo"
struct {
string "none"
string "idle"
uint32 0
}
)
]
signal sender=:1.46 -> dest=(null destination) path=/org/syncevolution/Server;
interface=org.syncevolution.Server; member=SessionChanged
object path "/org/syncevolution/Session/7414306401283853336"
boolean false
method call sender=:1.51 -> dest=:1.46
path=/org/syncevolution/Connection/7414306401283853336;
interface=org.syncevolution.Connection; member=Close
boolean false
string "lost connection to SyncEvolution"
error sender=:1.46 -> dest=:1.51
error_name=org.freedesktop.DBus.Error.UnknownMethod reply_serial=17
string "Method "Close" with signature "bs" on interface
"org.syncevolution.Connection" doesn't exist
It seems like the dbus server uses signals to return log lines, but the http
server does not seem to show them, making them lost in the void. This makes
setting up the HTTP server a bit of challenge :-)
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
11 years, 4 months
[MeeGo Projects - Bug 10358] New: Duplicated events appear on the phone If I try to add two or more events in the same syncronization.
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=10358
Summary: Duplicated events appear on the phone If I try to add
two or more events in the same syncronization.
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: gorka(a)your-mail.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
Created an attachment (id=3616)
--> (http://bugs.meego.com/attachment.cgi?id=3616)
Client log where a duplicated event is generated. Edited to remove IMEI of my
mobile phone
version of SyncEvolution: 1:1.1-2
version of OS and Evolution (if applicable): Ubuntu 10.04.1 and Evolution 2.30
description:
When I do a direct sync through bluetooth with my Nokia 2720 (series 40) phone,
duplicated events appear on the phone If I try to add two or more events in the
same syncronization.
Steps to reproduce:
1. In Evolution, Add two events (Test1 and Test2). They don't have to be on the
same day.
2. Synchronize
3. Two new events appear in the mobile phone
4. Synchronize again
5. Test1 event is duplicated on the phone.
This follows a pattern when more than two events are added in Evolution. For
example:
1. In Evolution, Add three events (Test1, Test2 and Test3). They don't have to
be on the same day.
2. Synchronize
3. Three new events appear in the mobile phone
4. Synchronize again
5. Test1 and Test2 events are duplicated on the phone.
4. Synchronize again
5. Now Test1 appears three times, Test2 twice and Test1 once on the phone.
If each event is added on a consecutive synchronization, everything appears to
be correct:
1. Add Test 1 in Evolution
2. Synchronize
3. Add Test 2 in Evolution
4. Synchronize
5. Test1 and Test2 appear once on the mobile phone, so, this way, everything is
correct
client log: Attached a client log where a duplicated event is generated. Edited
to remove IMEI of my mobile phone
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
11 years, 4 months
[MeeGo Projects - Bug 11241] New: Nokia: recurring events: recurrence rule not understood by phone
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=11241
Summary: Nokia: recurring events: recurrence rule not
understood by phone
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: patrick.ohly(a)intel.com
QAContact: jingke.zhang(a)intel.com
CC: patrick.ohly(a)intel.com, syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Depends on: 11233
Estimated Hours: 0.0
This is how a Nokia N97 sends an event which was created on the phone with:
- daily recurrence until 30.12.2100
- start and end time 10:00, German time as system time
- first day 12.12.2010
- reminder time 9:45, on 12.12.2010
Note that the UI implies that only one reminder will be triggered, for the
first recurrence. I'm waiting for 9:45 to see whether there will be a reminder
for the second recurrence... yes, there was one.
BEGIN:VCALENDAR
VERSION:1.0
TZ:+01
DAYLIGHT:TRUE;+02;20100328T010000Z;20101031T010000Z;;
DAYLIGHT:TRUE;+02;20110327T010000Z;20111030T010000Z;;
DAYLIGHT:TRUE;+02;20120325T010000Z;20121028T010000Z;;
DAYLIGHT:TRUE;+02;20130331T010000Z;20131027T010000Z;;
DAYLIGHT:TRUE;+02;20140330T010000Z;20141026T010000Z;;
BEGIN:VEVENT
SUMMARY:Phone
DTSTART:20101212T090000Z
DTEND:20101212T090000Z
CLASS:PRIVATE
RRULE:D1 #0
AALARM;TYPE=X-EPOCSOUND:20101212T084500Z;;;
LAST-MODIFIED:20101213T081037Z
PRIORITY:2
END:VEVENT
END:VCALENDAR
There is no end date set.
The conversion into iCalendar 2.0 by the Synthesis engine almost correctly
preserves the original semantic. It picked the Europe/Zurich time zone instead
of Germany, but given no further hints by the phone, the engine cannot decide
which zone was used on the phone; in practice, the two can be considered
identical.
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Synthesis AG//NONSGML SyncML Engine V3.4.0.8//EN
BEGIN:VTIMEZONE
TZID:Europe/Zurich
BEGIN:STANDARD
DTSTART:19671029T030000
RRULE:FREQ=MONTHLY;INTERVAL=12;BYDAY=-1SU
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19870329T020000
RRULE:FREQ=MONTHLY;INTERVAL=12;BYDAY=-1SU
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
LAST-MODIFIED:20101213T081037Z
CLASS:PRIVATE
PRIORITY:2
SUMMARY:Phone
DESCRIPTION:Phone
DTSTART;TZID=Europe/Zurich:20101212T100000
RRULE:FREQ=DAILY;INTERVAL=1
DTEND;TZID=Europe/Zurich:20101212T100000
BEGIN:VALARM
TRIGGER;VALUE=DATE-TIME:20101212T084500Z
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
Setting 31.12.2011 as specific end date instead of 30.12.2100 leads to:
BEGIN:VCALENDAR
VERSION:1.0
TZ:+01
DAYLIGHT:TRUE;+02;20100328T010000Z;20101031T010000Z;;
DAYLIGHT:TRUE;+02;20110327T010000Z;20111030T010000Z;;
BEGIN:VEVENT
SUMMARY:Phone
DTSTART:20101212T090000Z
DTEND:20101212T090000Z
CLASS:PRIVATE
RRULE:D1 20111231T100000
AALARM;TYPE=X-EPOCSOUND:20101212T084500Z;;;
LAST-MODIFIED:20101213T081626Z
PRIORITY:2
END:VEVENT
END:VCALENDAR
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Synthesis AG//NONSGML SyncML Engine V3.4.0.8//EN
BEGIN:VTIMEZONE
TZID:Europe/Zurich
BEGIN:STANDARD
DTSTART:19671029T030000
RRULE:FREQ=MONTHLY;INTERVAL=12;BYDAY=-1SU
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19870329T020000
RRULE:FREQ=MONTHLY;INTERVAL=12;BYDAY=-1SU
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
LAST-MODIFIED:20101213T081626Z
CLASS:PRIVATE
PRIORITY:2
SUMMARY:Phone
DESCRIPTION:Phone
DTSTART;TZID=Europe/Zurich:20101212T100000
RRULE:FREQ=DAILY;INTERVAL=1;UNTIL=20111231T100000
DTEND;TZID=Europe/Zurich:20101212T100000
BEGIN:VALARM
TRIGGER;VALUE=DATE-TIME:20101212T084500Z
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
---------------------------
Conclusions:
- a fixed, one time alarm on a Nokia phone should better be interpreted
as a relative alarm, with a delta as between the first occurrence and
the alarm; that's how Nokia interprets it
This might be doable in conversion scripts when importing and exporting
vCalendar 1.0 data.
--- Comment #1 from pohly <patrick.ohly(a)intel.com> 2010-12-13 02:03:21 PST ---
+++ This bug was initially created as a clone of Bug #11233 +++
This was sent to us by the phone:
BEGIN:VCALENDAR
VERSION:1.0
TZ:+01
DAYLIGHT:TRUE;+02;20100328T010000Z;20101031T010000Z;;
DAYLIGHT:TRUE;+02;20110327T010000Z;20111030T010000Z;;
BEGIN:VEVENT
SUMMARY:Phone
DTSTART:20101212T090000Z
DTEND:20101212T090000Z
CLASS:PRIVATE
RRULE:D1 20111231T100000
AALARM;TYPE=X-EPOCSOUND:20101212T084500Z;;;
LAST-MODIFIED:20101213T081626Z
PRIORITY:2
END:VEVENT
END:VCALENDAR
Translated into:
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Synthesis AG//NONSGML SyncML Engine V3.4.0.8//EN
BEGIN:VTIMEZONE
TZID:Europe/Zurich
BEGIN:STANDARD
DTSTART:19671029T030000
RRULE:FREQ=MONTHLY;INTERVAL=12;BYDAY=-1SU
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19870329T020000
RRULE:FREQ=MONTHLY;INTERVAL=12;BYDAY=-1SU
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
LAST-MODIFIED:20101213T081626Z
CLASS:PRIVATE
PRIORITY:2
SUMMARY:Phone
DESCRIPTION:Phone
DTSTART;TZID=Europe/Zurich:20101212T100000
RRULE:FREQ=DAILY;INTERVAL=1;UNTIL=20111231T100000
DTEND;TZID=Europe/Zurich:20101212T100000
BEGIN:VALARM
TRIGGER;VALUE=DATE-TIME:20101212T084500Z
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
After changing the summary, it is sent back to the phone as an update as:
BEGIN:VCALENDAR
VERSION:1.0
TZ:+01:00
DAYLIGHT;ENCODING=QUOTED-PRINTABLE:TRUE;+02;20110327T010000Z;20111=
030T010000Z;CET;CEST
BEGIN:VEVENT
LAST-MODIFIED:20101213T091201Z
CLASS:PRIVATE
PRIORITY:2
SUMMARY:Phone mod
DESCRIPTION:Phone
DTSTART:20101212T090000Z
RRULE:D1 20111231
DTEND:20101212T090000Z
AALARM:20101212T084500Z;;;Phone mod
DALARM:20101212T084500Z;;;Phone mod
END:VEVENT
END:VCALENDAR
The phone now ignores the recurrence.
Disabling the alarm:
BEGIN:VCALENDAR
VERSION:1.0
TZ:+01:00
DAYLIGHT;ENCODING=QUOTED-PRINTABLE:TRUE;+02;20110327T010000Z;20111=
030T010000Z;CET;CEST
BEGIN:VEVENT
LAST-MODIFIED:20101213T091741Z
CLASS:PRIVATE
PRIORITY:2
SUMMARY:Phone mod
DESCRIPTION:Phone
DTSTART:20101212T090000Z
RRULE:D1 20111231
DTEND:20101212T090000Z
END:VEVENT
END:VCALENDAR
Still no recurrence on the phone. Switching to UTC also doesn't help.
One relevant difference might be the explicit time in the RRULE. The phone
includes it, the Synthesis engine doesn't. Yep, that seems to be it. Both
"forever" (RRULE:D1 #0) and "fixed number of times" work.
The later one is interesting, because the Synthesis engine internally converts
it into a fixed end date:
RRULE;X-EVOLUTION-ENDDATE=20101219T100000Z:FREQ=DAILY;COUNT=7
# [2010-12-13 10:34:44.466] - calculating end date now
# [2010-12-13 10:34:44.466] endDateFromCount: daily calc - same in all cases
# [2010-12-13 10:34:44.466] - leaving with freq D, freqmod , interval 1,
firstmask 0, lastmask 0
# [2010-12-13 10:34:44.466] RRULE2toInternal(): extracted until
'20101218T100000Z'
- 13 : string RR_FREQ [ 0, -1, 2] : "D "
- 14 : integer RR_INTERVAL [ 0, 0, 0] : 1
- 15 : integer RR_FMASK [ 0, 0, 0] : 0
- 16 : integer RR_LMASK [ 0, 0, 0] : 0
- 17 : timestamp RR_END [ 0, 0, 0] : 2010-12-18T10:00:00Z
(TZ: UTC)
BEGIN:VCALENDAR
VERSION:1.0
TZ:+00:00
DAYLIGHT:FALSE
BEGIN:VEVENT
LAST-MODIFIED:20101213T093438Z
CLASS:PRIVATE
PRIORITY:2
SUMMARY:Phone mod
DESCRIPTION:Phone
DTSTART:20101212T100000Z
RRULE:D1 20101218T100000Z
DTEND:20101212T100000Z
END:VEVENT
END:VCALENDAR
This is displayed fine on the phone, confirming that 20101218T100000Z is needed
in RRULE.
In comparison, here's the full conversion for "recurs until":
RRULE:FREQ=DAILY;UNTIL=20101231
# [2010-12-13 10:51:06.983] - extracted until 20101231T000000Z
# [2010-12-13 10:51:06.983] - leaving with freq D, freqmod , interval 1,
firstmask 0, lastmask 0
# [2010-12-13 10:51:06.983] RRULE2toInternal(): extracted until '20101231'
- 17 : timestamp RR_END [ 0, 0, 0] : 2010-12-31 (floating)
- 18 : timestamp DTSTART [ 0, -1, 0] : 2010-12-12T10:00:00Z
(TZ: UTC)
- 19 : timestamp DTEND [ 0, -1, 0] : 2010-12-12T10:00:00Z
(TZ: UTC)
RRULE:D1 20101231
The spec says that the end date must contain a time:
enddate::= ISO 8601_date_time value(e.g., 19940712T101530Z)
It does not say whether that end datetime is included in the recurrence, but
experiments show that this is the interpretation on the phone (vCalendar 1.0)
and in Evolution (iCalendar 2.0).
Given that vCalendar does not allow floating end dates, I think the encoder for
vCalendar RRULE should be fixed to not generate such broken rules. What time it
should insert as fallback might be a bit tricky, but I think the start time of
the event should do.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
11 years, 4 months
[MeeGo Projects - Bug 10266] New: Syncevolution fails to load /usr/lib/libedataserver-1.2.so.4
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=10266
Summary: Syncevolution fails to load
/usr/lib/libedataserver-1.2.so.4
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: Handset
Architecture: ARM
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: meego(a)misc.lka.org.lu
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
BUILD IMAGE(X.X.XX.X.XXXXXXXX.X - (e.g.:
meego-netbook-ia32-1.0.90.0.20100831.1)):
HARDWARE MODEL (on what HW this bug is uncovered):
Nokia N900
BUG DETAILED DESCRIPTIONS
===========================================================
Syncevolution fails to load /usr/lib/libedataserver-1.2.so.4, and hence
complains about undefined symbol: e_source_list_peek_groups (this symbol is
defined in /usr/lib/libedataserver-1.2.so.4).
This can be workaround by adding a symlink named 6.so into
/usr/lib/syncevolution/backends pointing to /usr/lib/libedataserver-1.2.so.4
The name 6.so has been chosen so as to show up first in the unsorted listing of
the directory, i.e. before libecal.so
EXACT STEPS LEADING TO PROBLEM:
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
===========================================================
1. Synchronize
2. Browse the syncevolution-log.html
EXPECTED OUTCOME:
===================
Every needed library should load without error
ACTUAL OUTCOME:
===================
libecal.so cannot be loaded(?) because of the missing e_source_list_peek_groups
symbol
USER IMPACT:
===================
None obvious...
REPRODUCIBILITY:
(always, less than 1/10, 5/10, 9/10)
=====================================
Always
EXTRA SOFTWARE INSTALLED:
============================
OTHER COMMENTS:
===================
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
11 years, 5 months
[MeeGo Projects - Bug 10267] New: N900 Calendar is not refreshed after synchronization
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=10267
Summary: N900 Calendar is not refreshed after synchronization
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: Handset
Architecture: ARM
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: meego(a)misc.lka.org.lu
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
BUILD IMAGE(X.X.XX.X.XXXXXXXX.X - (e.g.:
meego-netbook-ia32-1.0.90.0.20100831.1)):
syncevolution 1.0
HARDWARE MODEL (on what HW this bug is uncovered):
Nokia N900
BUG DETAILED DESCRIPTIONS
===========================================================
After synchronization, often the calendar display is not refreshed. Often
exiting and re-entering the calendar app is not enough. However,
Settings->EditCalendars->Done->Save seems to work most of the time.
Sometimes the problem occurs even if the calendar was not running during
synchronization.
EXACT STEPS LEADING TO PROBLEM:
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
===========================================================
1. Open Calendar
2. Synchronize (twice, in order to avoid bug 10265)
3. Check Calendar
EXPECTED OUTCOME:
===================
Any changes on peer should be visible
ACTUAL OUTCOME:
===================
Changes are not always visible
USER IMPACT:
===================
Annoyance, as user must do the EditCalendar magic to get a refreshed view. If
user unaware, this could lead to scheduling conflicts or missed meetings.
REPRODUCIBILITY:
(always, less than 1/10, 5/10, 9/10)
=====================================
3/10
EXTRA SOFTWARE INSTALLED:
============================
OTHER COMMENTS:
===================
Does not always happen. It happened almost all the time when I started playing
with syncevolution, and then I had a streak of a dozen synchronizations where
it didn't happen, and now it seems to be back...
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
11 years, 5 months