[MeeGo Projects - Bug 11998] New: adapt to ConnMan D-Bus API change
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=11998
Summary: adapt to ConnMan D-Bus API change
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: major
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
Between MeeGo 1.1 and 1.2, the ConnMan D-Bus API will (has?) changed from
org.moblin to org.connman as identifier for the service.
Need to adapt syncevo-dbus-server, otherwise the "Sync Now" button in the UI
will always stay enabled, regardless whether we are online or not.
I don't think we need to do it in a backwards-compatible fashion, just
search/replace. It implies that SyncEvolution 1.2 cannot be used in MeeGo 1.1,
though.
--
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 6346] New: command line: different --source-property values for each source (type@addressbook)
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=6346
Summary: command line: different --source-property values for
each source (type@addressbook)
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: enhancement
Priority: Undecided
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
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
http://syncevolution.org/development/http-server-howto currently lists multiple
different invocations to configure the server:
syncevolution --configure \
--source-property type=file:text/vcard:3.0 \
--source-property uri= \
--source-property evolutionsource=file://${datapath}/addressbook \
${peer} addressbook
syncevolution --configure \
--source-property type=file:text/calendar:2.0 \
--source-property uri= \
--source-property evolutionsource=file://${datapath}/calendar \
${peer} calendar
syncevolution --configure \
--source-property type=file:text/calendar:2.0 \
--source-property uri= \
--source-property evolutionsource=file://${datapath}/todo \
${peer} todo
syncevolution --configure \
--source-property type=file:text/plain:1.0 \
--source-property uri= \
--source-property evolutionsource=file://${datapath}/memo \
${peer} memo
syncevolution --configure \
--source-property type=virtual:text/calendar:2.0 \
--source-property uri= \
--source-property evolutionsource=calendar,todo \
${peer} calendar+todo
This would be much nicer using the following syntax:
syncevolution --configure \
--source-property uri= \
--source-property type@addressbook=file:text/vcard:3.0 \
--source-property evolutionsource@addressbook=file://${datapath}/addressbook
\
--source-property type@calendar=file:text/calendar:2.0 \
--source-property evolutionsource@calendar=file://${datapath}/calendar \
...
${peer}
Usually caveats apply when implementing this:
- deal with @<source> where <source> contains an = sign
- print errors where @<source> does not match an existing or listed source,
to detect typos
--
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 Platform - Bug 9041] New: bluetooth-sync with Evolution fails
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=9041
Summary: bluetooth-sync with Evolution fails
Classification: MeeGo Platform
Product: OS Middleware
Version: 1.1
Platform: Notebook
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: patrick.ohly(a)intel.com
ReportedBy: juergenoschumacher(a)gmx.de
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-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): Laptop (Thinkpad X301)
running Ubuntu Linux 10.10, Nokia N900 with fremantle 1.3 (updated on 26th of
October 2010)
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))
===========================================================
I tried to perform a bluetooth-sync of calender and addressbook data on a Nokia
N900 with Evolution running on an Ubuntu 10.10 OS.
1. Updated syncevolution on N900 (version 1.0) and on Ubuntu (version 1.1)
2. Installed GTK sync-UI on Ubuntu 10.10
3. Successfully performed bluetooth-pairing of Laptop and N900
4. Successfully went through the configuration steps to sync Mobile phone over
Bluetooth in Ubuntu as described here:
http://mobileyog.blogspot.com/2010/06/easiest-way-to-sync-your-mobile-pho...
5. Started sync from sync-ui in Ubuntu
6. N900 and sync-ui show the symbols that a synchronization is started
7. After a couple of minutes an error message appears that the synchronization
failed
How can I track this error?
Tried to debug on the command line, and issued the command
syncevolution --configure --template Nokia\ N900 --sync-property
syncURL=obex-bt://<My-Blutooth-MAC-Address> MyPhone
This command works OK, no error message, but to me it is unclear where
syncevolution stores this new profile?
EXPECTED OUTCOME: Successful bluetooth-sync between N900 and Evolution
===================
ACTUAL OUTCOME:
===================
USER IMPACT:
===================
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 someone on the CC list of the bug.
11 years, 4 months
[Bug 1371] New: SAN fail when syncing with N900 phone
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=1371
Summary: SAN fail when syncing with N900 phone
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: Netbook
OS/Version: IA
Status: ASSIGNED
Severity: major
Priority: High
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: jingke.zhang(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
This is from http://bugzilla.moblin.org/show_bug.cgi?id=10483
Description From ZhangJingke 2010-04-15 22:39:19 PST (-) [reply]
Created an attachment (id=4684)
--> (http://bugs.meego.com/attachment.cgi?id=4684) [details]
N900 connection failure log
syncevolution 0.9.99.20
Description:
===============
This is a regression. Sync with N900 will meet "SANFormat 12 failed", please
see the attachment.
------- Comment #1 From Chen Congwu 2010-04-15 22:57:08 PST (-) [reply] -------
It might be the phone is not responding for some reason, try reboot it..
------- Comment #2 From ZhangJingke 2010-04-15 23:12:37 PST (-) [reply] -------
(In reply to comment #1)
> It might be the phone is not responding for some reason, try reboot it..
I reboot phone, re-pair N900. Then it still fail with the same reason. :(
------- Comment #3 From Chen Congwu 2010-04-16 00:53:30 PST (-) [reply] -------
(In reply to comment #2)
That's strange, works on my environment..
> (In reply to comment #1)
> > It might be the phone is not responding for some reason, try reboot it..
>
> I reboot phone, re-pair N900. Then it still fail with the same reason. :(
------- Comment #4 From Chen Congwu 2010-04-16 02:17:38 PST (-) [reply] -------
(In reply to comment #2)
The connect system call will fail immediately with error code '104' (that is
'Connection reset by peer'),
that's different when failed with pairing problem, error code '111'
('Connection refused')
Any way, since it failed early enough before involving the Obex library, I
suspect it might be:
1) Phone side mess
2) Bluez library or driver change in the image
Jingke, could you
1) retest with another N900?
2) retest with an older image?
> (In reply to comment #1)
> > It might be the phone is not responding for some reason, try reboot it..
>
> I reboot phone, re-pair N900. Then it still fail with the same reason. :(
------- Comment #5 From ZhangJingke 2010-04-19 20:12:18 PST (-) [reply] -------
(In reply to comment #4)
> (In reply to comment #2)
> The connect system call will fail immediately with error code '104' (that is
> 'Connection reset by peer'),
> that's different when failed with pairing problem, error code '111'
> ('Connection refused')
> Any way, since it failed early enough before involving the Obex library, I
> suspect it might be:
> 1) Phone side mess
> 2) Bluez library or driver change in the image
>
> Jingke, could you
> 1) retest with another N900?
> 2) retest with an older image?
I tried another N900, still the same failure. So, is it the error of "Nokia
N900" template? I am sure N900 could sync in some old image.
------- Comment #6 From Chen Congwu 2010-04-20 00:44:36 PST (-) [reply] -------
(In reply to comment #5)
right, this is a real problem
>
> I tried another N900, still the same failure. So, is it the error of "Nokia
> N900" template? I am sure N900 could sync in some old image.
Actually the failing scenario is as following:
Moblin:
connect() OK
write() OBEX_Connect cmd
read() --104 (Connection reset by peer)
My PC:
connect() OK
write() OBEX_Connect cmd
read() OK
------
see the detailed strace log:
---Moblin---
bind(8, {sa_family=AF_BLUETOOTH, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 10) =
0
fcntl64(8, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(8, F_SETFL, O_RDWR) = 0
fstat64(8, {st_mode=S_IFSOCK|0777, st_size=0, ...}) = 0
fcntl64(8, F_GETFL) = 0x2 (flags O_RDWR)
connect(8, {sa_family=AF_BLUETOOTH, sa_data="KO\324:\275\0\31\0\37\0\0\0\0\0"},
10) = 0
time(NULL) = 1271795229
write(8, "\200\0\25\20\0\177\377F\0\16SYNCML-SYNC", 21) = 21
gettimeofday({1271795229, 351568}, {240, 0}) = 0
open("/home/moblin/.cache/syncevolution/nokia
n900-2010-04-20-16-27/syncevolution-log.html", O_WRONLY|O_CREAT|O_APPEND, 0666)
= 9
fstat64(9, {st_mode=S_IFREG|0644, st_size=21384, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb745b000
fstat64(9, {st_mode=S_IFREG|0644, st_size=21384, ...}) = 0
_llseek(9, 21384, [21384], SEEK_SET) = 0
write(9, "<li><i>[2010-04-20 16:27:09.351]"..., 61) = 61
close(9) = 0
munmap(0xb745b000, 4096) = 0
recv(5, 0x88cf218, 1023, MSG_PEEK|MSG_DONTWAIT) = -1 EAGAIN (Resource
temporarily unavailable)
poll([{fd=6, events=POLLIN}, {fd=8, events=POLLIN|POLLOUT}], 2, -1) = 1
([{fd=8, revents=POLLOUT}])
time(NULL) = 1271795229
select(9, [8], NULL, NULL, {1, 0}) = 1 (in [8], left {0, 986552})
read(8, 0x88b2ce8, 3) = -1 ECONNRESET (Connection reset by
peer)
-----------
--PC--
bind(8, {sa_family=AF_BLUETOOTH, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 10) =
0
fcntl64(8, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(8, F_SETFL, O_RDWR) = 0
fstat64(8, {st_mode=S_IFSOCK|0777, st_size=0, ...}) = 0
fcntl64(8, F_GETFL) = 0x2 (flags O_RDWR)
connect(8, {sa_family=AF_BLUETOOTH, sa_data="KO\324:\275\0\31\0\37\0\0\0\0\0"},
10) = 0
time(NULL) = 1271748604
write(8, "\200\0\25\20\0\177\377F\0\16SYNCML-SYNC", 21) = 21
gettimeofday({1271748604, 731927}, {4294966816, 0}) = 0
open("/home/cchen35/.cache/syncevolution/n900-2010-04-20-15-30/syncevolution-log.html",
O_WRONLY|O_CREAT|O_APPEND, 0666) = 9
fstat64(9, {st_mode=S_IFREG|0644, st_size=21220, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7851000
fstat64(9, {st_mode=S_IFREG|0644, st_size=21220, ...}) = 0
_llseek(9, 21220, [21220], SEEK_SET) = 0
write(9, "<li><i>[2010-04-20 01:30:04.731]"..., 61) = 61
close(9) = 0
munmap(0xb7851000, 4096) = 0
recv(5, 0x9c61160, 1023, MSG_PEEK|MSG_DONTWAIT) = -1 EAGAIN (Resource
temporarily unavailable)
poll([{fd=6, events=POLLIN}, {fd=8, events=POLLIN|POLLOUT}], 2, -1) = 1
([{fd=8, revents=POLLOUT}])
time(NULL) = 1271748604
select(9, [8], NULL, NULL, {1, 0}) = 1 (in [8], left {0, 911726})
read(8, "\240\0\32", 3) = 3
read(8, "\20\0\4\0\313K\315Y\241J\0\16SYNCML-SYNC", 23) = 23
----------
------- Comment #7 From pohly 2010-04-26 06:43:34 PST (-) [reply] -------
Congwu, Jingke, what is the status regarding this issue?
We agreed that this looks like a regression in the underlying Bluetooth
transports (Bluez, kernel). To proof that, we need to find an old image where
this kind of sync still works, then install the same SyncEvolution version on a
recent image and show that it fails. If SyncEvolution is the same in this test
but the OS is not, then it should be investigated by the OS maintainers.
--
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 12002] New: contacts phone->Evolution: use <last name, first name> sorting
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=12002
Summary: contacts phone->Evolution: use <last name, first name>
sorting
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: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
The default sort order in the "file-as" field (aka X-EVOLUTION-FILE-AS) is
<last name, first name>.
SyncEvolution should emulate that when importing from phones (like Nokia N95,
see "[SyncEvolution] error message SOLVED", or E71, see "[SyncEvolution]
device->desktop sync not stable").
Exact details to be sorted out (unconditionally? configurable order?).
--
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 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