December 2013 - Syncevolution-issues

[Bug 57145] New: invalid operations on target config

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=57145 Priority: high Bug ID: 57145 CC: syncevolution-issues(a)syncevolution.org Assignee: syncevolution-issues(a)syncevolution.org Summary: invalid operations on target config Severity: normal Classification: Unclassified OS: All Reporter: patrick.ohly(a)gmx.de Hardware: Other Status: ASSIGNED Version: unspecified Component: SyncEvolution Product: SyncEvolution Several operations do not make sense for a target config. Trying them should trigger dedicated error messages: - syncing (see bug #56263 comment #0 for an example of lacking error reporting) - status (see #56263 comment #10) -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

3 years, 7 months

1
1
0 / 0

[Bug 59571] New: use normalized phone numbers in EDS

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=59571 Priority: high Bug ID: 59571 CC: syncevolution-issues(a)syncevolution.org Assignee: patrick.ohly(a)intel.com Blocks: 55918 Summary: use normalized phone numbers in EDS Severity: normal Classification: Unclassified OS: All Reporter: patrick.ohly(a)gmx.de Hardware: Other Status: ASSIGNED Version: unspecified Component: SyncEvolution Product: SyncEvolution The PIM Manager can use normalized phone numbers in EDS for two things: - avoid calculating the normalized numbers after reading a contact - search via normalized string when doing a direct search -- You are receiving this mail because: You are on the CC list for the bug.

3 years, 7 months

1
23
0 / 0

[Bug 67244] New: sync android to pc, bad alarm sync

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=67244 Priority: medium Bug ID: 67244 CC: syncevolution-issues(a)syncevolution.org Assignee: syncevolution-issues(a)syncevolution.org Summary: sync android to pc, bad alarm sync Severity: normal Classification: Unclassified OS: All Reporter: epistemepromeneur(a)free.fr Hardware: Other Status: NEW Version: unspecified Component: KDE Product: SyncEvolution hello i have a pb when synchronizing android calendar to korganizer i send a long report to bugs.kde but i want to be sure it is not a pb from syncevolution-kde 1.3.99.4-2 can you examine the report ? https://bugs.kde.org/show_bug.cgi?id=322738 thanks -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

3 years, 7 months

1
2
0 / 0

[Bug 63882] New: WebDAV: re-import uploaded item

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=63882 Priority: medium Bug ID: 63882 CC: syncevolution-issues(a)syncevolution.org Assignee: syncevolution-issues(a)syncevolution.org Summary: WebDAV: re-import uploaded item Severity: normal Classification: Unclassified OS: All Reporter: patrick.ohly(a)gmx.de Hardware: Other Status: ASSIGNED Version: 1.3.99.3 Component: CalDAV/CardDAV Product: SyncEvolution A WebDAV server is allowed to modify items during a PUT, in which case it won't return an eTag. SyncEvolution should treat the missing eTag as "server has updated data" and import that changed item in a second cycle. This can be made more efficient with the prefer=return-representation header. http://tools.ietf.org/html/draft-snell-http-prefer-12#page-6 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

3 years, 7 months

1
2
0 / 0

[Bug 64177] New: PIM: more complex searching and sorting

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=64177 Priority: medium Bug ID: 64177 CC: syncevolution-issues(a)syncevolution.org Assignee: syncevolution-issues(a)syncevolution.org Blocks: 56141 Summary: PIM: more complex searching and sorting Severity: enhancement Classification: Unclassified OS: All Reporter: patrick.ohly(a)gmx.de Hardware: Other Status: ASSIGNED Version: 1.3.99.3 Component: SyncEvolution Product: SyncEvolution Searching could be extended with and/or operations and more complex match terms, like "field X contains/starts-with/ends-with Y". Sorting could be extended to sort ascending and descending and with a list of fields to use for comparison. Need full specification for the desired feature. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

3 years, 7 months

1
11
0 / 0

[Bug 70693] New: Problem with repeateable event not on a fixed day

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=70693 Priority: medium Bug ID: 70693 CC: syncevolution-issues(a)syncevolution.org Assignee: syncevolution-issues(a)syncevolution.org Summary: Problem with repeateable event not on a fixed day Severity: normal Classification: Unclassified OS: Linux (All) Reporter: dbet1(a)gmx.net Hardware: x86 (IA32) Status: NEW Version: 1.3 Component: SyncEvolution Product: SyncEvolution In Memotoo I have two events with yearly interval, but at the first thuesday of the month instead of a fixed day. In Evolution these events are non repeatable events after sync. I downloaded my data from Memotoo, opened the calendar file and searched the event. The rule are: RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1TH If I change this in Evolution, after sync the repeats are lost at Memotoo. The same is with frequency monthly and interval 12. It seems there is some misunderstanding between Memotoo, Syncevolution and Evolution. And in Evolution I can only choose monthly if I have not a fixed day. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

3 years, 7 months

1
6
0 / 0

[Bug 66038] New: label conflict

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=66038 Priority: medium Bug ID: 66038 CC: syncevolution-issues(a)syncevolution.org Assignee: syncevolution-issues(a)syncevolution.org Summary: label conflict Severity: normal Classification: Unclassified OS: Linux (All) Reporter: epistemepromeneur(a)free.fr Hardware: x86 (IA32) Status: NEW Version: 1.4 Component: KDE Product: SyncEvolution 1. first pb kde label for a personal fax : <no label> kde label for a professional fax : <no label> kde label for a fax : fax android label for a personal fax : fax personnel android label for a professional fax : fax professionnel android label for a fax : <no label> when i synchronize from kde to android then all kde card with "fax" "<number>" are changed to "<no label>" "<number>" then i must manualy change "<no label>" to <fax personnel" or "fax professionnel" this is a big pb when you have many fax note : i say "android" but i don't know if it is "samsung" or "android" or google label. 2. second pb if in android i change in a card "<no label>" "<number>" to "fax personnel" "<number>" or "fax professionnel" then i synchronize from android to kde then in kde "fax" "<number>" is changed to "fax personnel" "<number>" or "fax professionnel" this is a problem for app accessing to kde addressbook and expecting kde label "fax" and not "fax personnel" "<number>" or "fax professionnel" 3 there is the same pb for telephone kde personal phone : "téléphone personnel" kde professional phone : "téléphone professionnel" android personal phone : "téléphone personnel/boîte vocale" android professional phone : "téléphone professionnel/boîte vocale" 4 there is perhaps some pb for other fields 5. perhaps also funambol has their own labels then labels may changed between funambol and kde ! -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

3 years, 7 months

1
21
0 / 0

[Bug 59985] New: Feature Request: Setting up Owncloud within GUI

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=59985 Priority: medium Bug ID: 59985 CC: syncevolution-issues(a)syncevolution.org Assignee: syncevolution-issues(a)syncevolution.org Summary: Feature Request: Setting up Owncloud within GUI Severity: enhancement Classification: Unclassified OS: All Reporter: lebochequirit(a)gmail.com Hardware: All Status: NEW Version: unspecified Component: GTK UI Product: SyncEvolution Syncing with Owncloud does work via command line, but it's quite an effort and way beyond many users knowledge. Also, setting up auto-sync is much easier from within the GUI. A predefined Owncloud Service would be of major use for many, many users. I'm sorry to say so, but the usability of Evolution and in parts Owncloud depends on you, as both platforms seem not to care about each other :-) Thanks for your excellent work so far, L.B.Q.R. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

3 years, 7 months

1
8
0 / 0

[Bug 54998] New: disable PHOTO syncing for specific peers

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=54998 Bug #: 54998 Summary: disable PHOTO syncing for specific peers Classification: Unclassified Product: SyncEvolution Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: enhancement Priority: high Component: SyncML AssignedTo: syncevolution-issues(a)syncevolution.org ReportedBy: patrick.ohly(a)gmx.de CC: syncevolution-issues(a)syncevolution.org Some peers, in particular older phones, have problems when being sent lots of photo data. It may be more useful to exclude photo data altogether for such peers. See "[SyncEvolution] Sync failure due to large addressbook entires." A possible solution would be: - introduce a new session variable in the <sessioninitscript> - set that variable in remote rules (see stripUID for an example) or based on a new config property (see preventSlowSync) - extend the <outgoingscript> for contacts such that it unsets the PHOTO property before encoding a contact for the peer if that session variable is set - see VCARD_OUTGOING_PHOTO_INLINING_SCRIPT That should take care of sending data to the phone. Ensuring that the photo doesn't get lost when receiving an update is harder. Something might be possible with a custom <mergescript>, but I am not sure whether it really gets invoked during a normal import. Alternatively, dynamically updating the field attributes after parsing the peer's CtCap would be a more elegant solution, because it would use existing libsynthesis mechanisms: - don't send properties to a peer which the peer doesn't support (strip PHOTO when sending) - preserve local properties not supported by the peer (preserve PHOTO) However, implementing that will require considerable changes in libsynthesis: - expose the field list attributes to scripts - ensure that a script is called after parsing CtCap and before using the field list (perhaps <datastoreinitscript> is suitable) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.

3 years, 7 months

1
2
0 / 0

[Bug 57004] New: preventing slow syncs must not cause slow syncs

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=57004 Priority: highest Bug ID: 57004 CC: syncevolution-issues(a)syncevolution.org Assignee: patrick.ohly(a)intel.com Summary: preventing slow syncs must not cause slow syncs Severity: normal Classification: Unclassified OS: All Reporter: patrick.ohly(a)gmx.de Hardware: Other Status: ASSIGNED Version: unspecified Component: SyncML Product: SyncEvolution When one source in a sync with multiple sources encounters a slow sync and thus aborts the sync, the other sources must not be affected. What happens instead is that they are forced into a slow sync in the next sync. Steps to reproduce: syncevolution --configure preventslowsync=1 memotoo_1 syncevolution memotoo_1 eds_contact eds_event cp -a ~/.config/syncevolution/ ~/.config/syncevolution_old syncevolution memotoo_1 eds_contact rm -rf ~/.config/syncevolution mv ~/.config/syncevolution_old ~/.config/syncevolution syncevolution memotoo_1 eds_contact => prevents slow sync due to wrong anchors on client, as expected syncevolution memotoo_1 eds_event => works syncevolution memotoo_1 eds_event eds_contact => prevents slow sync for eds_contact syncevolution memotoo_1 eds_event => should have worked, but now also encounters slow sync -- You are receiving this mail because: You are on the CC list for the bug.

3 years, 7 months

1
5
0 / 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Syncevolution-issues December 2013