October 2018 - Syncevolution-issues

[Bug 52767] command line + syncevo-dbus-server: avoid hard-coding env variables

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=52767 GitLab Migration User <gitlab-migration(a)fdo.invalid> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|ASSIGNED |RESOLVED --- Comment #1 from GitLab Migration User <gitlab-migration(a)fdo.invalid> --- -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/25. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.

3 years, 11 months

1
0
0 / 0

[Bug 87190] New: Syncevolution is crashing during synchronization with highest log level

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=87190 Bug ID: 87190 Summary: Syncevolution is crashing during synchronization with highest log level Product: SyncEvolution Version: 1.4 Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: SyncEvolution Assignee: syncevolution-issues(a)syncevolution.org Reporter: mateusz.polrola(a)gmail.com CC: syncevolution-issues(a)syncevolution.org When synchronizing using highest log level and running out of disk space on partition where logs are stored, Syncevolution is crashing with such backtrace (from 1.3.99.5 version, but issue can be reproduced also with 1.4.99.4): #0 0xb6dfd746 in __strlen_sse2_bsf () from /lib/libc.so.6 #1 0xb6bbf093 in length (this=0x9ef1680, aEntryType=sysync::mapentry_normal, aLocalID=0x0, aRemoteID=0xa337434 "4457", aMapFlags=0, aDelete=false, aClearFlags=4294967295) from /usr/lib/libsynthesis.so.0 #2 assign (this=0x9ef1680, aEntryType=sysync::mapentry_normal, aLocalID=0x0, aRemoteID=0xa337434 "4457", aMapFlags=0, aDelete=false, aClearFlags=4294967295) at /usr/include/c++/4.5.3/bits/basic_string.h:1078 #3 operator= (this=0x9ef1680, aEntryType=sysync::mapentry_normal, aLocalID=0x0, aRemoteID=0xa337434 "4457", aMapFlags=0, aDelete=false, aClearFlags=4294967295) at /usr/include/c++/4.5.3/bits/basic_string.h:541 #4 sysync::TCustomImplDS::modifyMap (this=0x9ef1680, aEntryType=sysync::mapentry_normal, aLocalID=0x0, aRemoteID=0xa337434 "4457", aMapFlags=0, aDelete=false, aClearFlags=4294967295) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/customimplds.cpp:1301 #5 0xb6bc0e32 in sysync::TCustomImplDS::implProcessItem (this=0x9ef1680, aItemP=0xa4b9c90, aStatusCommand=...) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/customimplds.cpp:3112 #6 0xb6c2519d in sysync::TStdLogicDS::logicProcessRemoteItem (this=0x9ef1680, syncitemP=0xa4b9c90, aStatusCommand=..., aVisibleInSyncset=@0xbff0a5ad, aGUID=0x0) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/stdlogicds.cpp:1445 #7 0xb6be68ec in sysync::TLocalEngineDS::engProcessRemoteItemAsServer (this=0x9ef1680, aSyncItemP=0xa4b9c90, aStatusCommand=...) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/localengineds.cpp:6396 #8 0xb6bf05b3 in sysync::TLocalEngineDS::engProcessRemoteItem (this=0x9ef1680, syncitemP=0xa4b9c90, aStatusCommand=...) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/localengineds.cpp:5055 #9 0xb6be4f7d in sysync::TLocalEngineDS::engProcessSyncOpItem (this=0x9ef1680, aSyncOp=sysync::sop_add, aItemP=0xa849f28, aMetaP=0xa9324c8, aStatusCommand=...) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/localengineds.cpp:5275 #10 0xb6c5021c in sysync::TSyncSession::processSyncOpItem (this=0x9f60800, aSyncOp=sysync::sop_add, aItemP=0xa849f28, aMetaP=0xa9324c8, aLocalSyncDatastore=0x9ef1680, aStatusCommand=..., aQueueForLater=@0xbff0a76f) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/syncsession.cpp:3993 #11 0xb6c459dd in sysync::TSyncOpCommand::execute (this=0xaaf09a8) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/synccommand.cpp:2625 #12 0xb6c5a000 in sysync::TSyncSession::executeDelayedCmd (this=0x9f60800, aCmdP=0xaaf09a8) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/syncsession.cpp:2904 #13 0xb6c5a1f8 in sysync::TSyncSession::tryDelayedExecutionCommands (this=0x9f60800) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/syncsession.cpp:2831 #14 0xb6c5bbc6 in sysync::TSyncSession::processHeader (this=0x9f60800, aSyncHdrP=0xa63bdc8) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/syncsession.cpp:2698 #15 0xb6c5c1c9 in sysync::TSyncSession::StartMessage (this=0x9f60800, aContentP=0xa713e00) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/syncsession.cpp:5499 #16 0xb6ba3060 in sysync::TEngineSessionDispatch::StartMessage (this=0x9ecfa78, aSmlWorkspaceID=0x9ef35a8, aUserData=0x9f60800, aContentP=0xa713e00) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/Transport_interfaces/engine/enginesessiondispatch.cpp:125 #17 0xb6c356da in sysync::smlStartMessageCallback (id=0x9ef35a8, userData=0x9ef15b0, pContent=0xa713e00) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/syncappbase.cpp:2394 #18 0xb6b4e2d7 in mgrProcessStartMessage (id=0x9ef35a8, mode=SML_NEXT_COMMAND) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/syncml_tk/src/sml/mgr/all/mgrcmddispatcher.c:247 #19 smlProcessData (id=0x9ef35a8, mode=SML_NEXT_COMMAND) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/syncml_tk/src/sml/mgr/all/mgrcmddispatcher.c:138 #20 0xb6c33ea5 in sysync::TSyncAgent::ServerProcessingStep (this=0x9f60800, aStepCmd=@0xbff0b0d8, aInfoP=0xbff0acb0) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/syncagent.cpp:3292 #21 0xb6c3428e in sysync::TSyncAgent::ServerSessionStep (this=0x9f60800, aStepCmd=@0xbff0b0d8, aInfoP=0xbff0acb0) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/syncagent.cpp:3257 #22 0xb6c34ad0 in sysync::TSyncAgent::SessionStep (this=0x9f60800, aStepCmd=@0xbff0b0d8, aInfoP=0xbff0acb0) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/syncagent.cpp:3058 #23 0xb6ba2b9f in sysync::TServerEngineInterface::SessionStep (this=0x9ecf958, aSessionH=0x9f31ec8, aStepCmd=@0xbff0b0d8, aInfoP=0xbff0acb0) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/Transport_interfaces/engine/enginesessiondispatch.cpp:477 #24 0xb6bd15fa in sysync::SessionStep (aCB=0x9ecf95c, aSessionH=0x9f31ec8, aStepCmd=0xbff0b0d8, aInfoP=0xbff0acb0) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync/engineentry.cpp:88 #25 0xb740d266 in sysync::TEngineModuleBridge::SessionStep (this=0x9ecf730, aSessionH=0x9f31ec8, aStepCmd=@0xbff0b0d8, aInfoP=0xbff0acb0) at /usr/src/debug/syncevolution-1.3.99.5+20131030+SE+05e5911+SYSYNC+69de386/src/synthesis/src/sysync_SDK/Sources/enginemodulebridge.cpp:109 #26 0xb729d507 in SyncEvo::SharedEngine::SessionStep (this=0x9ebfed8, aSessionH=..., aStepCmd=@0xbff0b0d8, aInfoP=0xbff0acb0) at src/syncevo/SynthesisEngine.cpp:96 #27 0xb73942fd in SyncEvo::SyncContext::doSync (this=0x9ebfde0) at src/syncevo/SyncContext.cpp:3973 #28 0xb73a1cbd in SyncEvo::SyncContext::sync (this=0x9ebfde0, report=0xbff0c624) at src/syncevo/SyncContext.cpp:3414 #29 0xb7302a40 in SyncEvo::Cmdline::run (this=0xbff0c608) at src/syncevo/Cmdline.cpp:1702 #30 0x08065165 in SyncEvo::main (argc=6, argv=0xbff0c7f4) at src/syncevolution.cpp:531 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

3 years, 11 months

1
3
0 / 0

[Bug 52800] rewrite synccompare in C++

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=52800 GitLab Migration User <gitlab-migration(a)fdo.invalid> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |MOVED --- Comment #1 from GitLab Migration User <gitlab-migration(a)fdo.invalid> --- -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/23. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. You reported the bug.

3 years, 11 months

1
0
0 / 0

[Bug 52674] integrate SyncEvolution into Evolution

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=52674 GitLab Migration User <gitlab-migration(a)fdo.invalid> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |MOVED --- Comment #1 from GitLab Migration User <gitlab-migration(a)fdo.invalid> --- -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/22. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

3 years, 11 months

1
0
0 / 0

[Bug 76516] New: Support activesync protocol version 14.0

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=76516 Priority: medium Bug ID: 76516 CC: syncevolution-issues(a)syncevolution.org Assignee: syncevolution-issues(a)syncevolution.org Summary: Support activesync protocol version 14.0 Severity: enhancement Classification: Unclassified OS: All Reporter: g+syncevolution(a)cobb.uk.net Hardware: Other Status: NEW Version: 1.4 Component: ActiveSync Product: SyncEvolution Connecting to outlook.com requires protocol version 14.0. Consideration is required to determine if it is good enough to just support 14.0 or whether negotiation must happen, with fallback to 12.1. If negotiation is required, does that mean using OPTIONS and/or the FolderSync version reporting? By the way, http://msdn.microsoft.com/en-us/library/ee157980%28EXCHG.80%29.aspx seems to describe many of the protocol differences between 12.1, 14.0 and 14.1. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

3 years, 11 months

1
2
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, 11 months

1
6
0 / 0

[Bug 53778] notifications for automatic sync: suppress notifications when GUI active

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=53778 GitLab Migration User <gitlab-migration(a)fdo.invalid> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|ASSIGNED |RESOLVED --- Comment #1 from GitLab Migration User <gitlab-migration(a)fdo.invalid> --- -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/19. -- You are receiving this mail because: You are the assignee for the bug. You reported the bug. You are on the CC list for the bug.

3 years, 11 months

1
0
0 / 0

[Bug 52683] CalDAV: attachments

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=52683 GitLab Migration User <gitlab-migration(a)fdo.invalid> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |MOVED --- Comment #1 from GitLab Migration User <gitlab-migration(a)fdo.invalid> --- -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/18. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

3 years, 11 months

1
0
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, 11 months

1
21
0 / 0

[Bug 79014] New: EDS calendar performance

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=79014 Priority: medium Bug ID: 79014 CC: syncevolution-issues(a)syncevolution.org Assignee: renatox(a)gmail.com Summary: EDS calendar performance Severity: enhancement Classification: Unclassified OS: All Reporter: patrick.ohly(a)gmx.de Hardware: Other Status: ASSIGNED Version: 1.4 Component: SyncEvolution Product: SyncEvolution Created attachment 99502 --> https://bugs.freedesktop.org/attachment.cgi?id=99502&action=edit rebased and squashed enhancements from Renato Renato and I discussed some ways to enhance EDS calendar performance during sync. Some of the ideas were coded as patches by Renato, However, regression testing then found some regressions which I fixed. The patches need to be fixed, cleaned up and submitted again against current master. -- You are receiving this mail because: You are on the CC list for the bug.

3 years, 11 months

1
10
0 / 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Syncevolution-issues October 2018