[MeeGo Platform - Bug 12827] New: PATCH: sync-ui and autoSyncInterval
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=12827
Summary: PATCH: sync-ui and autoSyncInterval
Classification: MeeGo Platform
Product: OS Middleware
Version: 1.2
Platform: All
Architecture: ---
Status: NEW
Severity: enhancement
Priority: Undecided
Component: SyncEvolution
AssignedTo: patrick.ohly(a)intel.com
ReportedBy: ville.nummela(a)symbio.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
ext-iekku.huttunen(a)nokia.com
Estimated Hours: 0.0
vige <ville.nummela(a)symbio.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #4323| |copyright‑waived+
Flag| |
Created an attachment (id=4323)
--> (http://bugs.meego.com/attachment.cgi?id=4323)
patch, adds autoSyncInterval to sync-ui
I wrote a small patch, which enables the user to specify
autoSyncInterval via sync-ui.
--
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.
10 years, 8 months
[Bug 5609] New: nightly testing: integrate syncevo-dbus-server testing
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=5609
Summary: nightly testing: integrate syncevo-dbus-server testing
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: normal
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
Yongsheng, you were involved in setting up testing of syncevo-dbus-server in
the nightly testing, right?
Can you finish the work done by Junhui by:
- merging the relevant code into the main syncevolution repository,
in test or test/dbus (whatever is more suitable)
- integrating it properly into the cron job
At the moment, the cron job executes ~nightly/nightly.sh, which looks like
this:
rm -fr /tmp/test/*; cd ~/dbus-testing && sh dbus-session.sh python
getResult_send.py > run.log 2>&1
cd ~/syncevolution-testing; runtests all >run.log 2>&1
Doesn't that use the *old* syncevolution from the previous night for D-Bus
testing? That looks wrong.
Another problem is that D-Bus testing should be skipped if the necessary
binaries didn't compile.
--
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.
10 years, 8 months
[MeeGo Platform - Bug 10015] New: syncevolution doesn't use libproxy; fails to connect
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=10015
Summary: syncevolution doesn't use libproxy; fails to connect
Classification: MeeGo Platform
Product: OS Middleware
Version: 1.0
Platform: All
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: patrick.ohly(a)intel.com
ReportedBy: dwmw2(a)linux.intel.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs
Blocks: 1508
Estimated Hours: 0.0
Syncevolution doesn't use libproxy to find current proxy information as
provided by ConnMan; it seems to be looking at the static settings in gconf.
And even when those are *correct*, it's broken -- it seems to connect to port
*zero* of the host which GConf tells it is serving the proxy PAC script.
--
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.
10 years, 8 months
[MeeGo Projects - Bug 10166] New: Nokia X6: contact photo syncing problem
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=10166
Summary: Nokia X6: contact photo syncing problem
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: major
Priority: High
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
>From http://syncevolution.org/wiki/nokia-x6
-----------------------------------------
Something goes wrong with contact images.
First: There were no contact images in evolution. On phone ca. 6 persons got an
image.
Secondly: synchronization is done perfectly, the images appear in Evolution.
Thirdly: In Evolution a contact with image is changed.
Fourthly: The synchronization will not work.
Fix: Remove image in evolution. Perhaps delete contact on phone, try
synchronization again, perhaps slow-synchronization.
The same happens when a images is attached in Evolution. Perhaps photo type and
encoding differ: in Nokia created:
PHOTO;ENCODING=B;TYPE=JPEG:/9j/4AAQSkZJRgABAQAAAQABAAD/2wCEABALD.... in
Evolution created:
PHOTO;TYPE="X-EVOLUTION-UNKNOWN";ENCODING=b:/9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAg....
Fix: Again, remove photo in Evolution, after that sync again.
------------------------------------------
--
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.
10 years, 9 months
[Bug 4835] New: N900: fails to synchronize with some kernel versions
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=4835
Summary: N900: fails to synchronize with some kernel versions
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ALL
Status: WAITING FOR UPSTREAM
Severity: major
Priority: High
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: patrick.ohly(a)intel.com
QAContact: jingke.zhang(a)intel.com
CC: jingke.zhang(a)intel.com, syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Depends on: 1371
Estimated Hours: 0.0
This issue seems related to the kernel. SyncEvolution + N900 works on some host
platforms and fails on others with:
# [2010-07-18 21:54:21.915] Connecting Bluetooth device with address
0C:DD:EF:9C:94:8B and channel 25
# [2010-07-18 21:54:22.191] OBEX progress
# [2010-07-18 21:54:22.246] Cancel disconncting process
# [2010-07-18 21:54:22.247] Server Alerted Sync init with SANFormat 12 failed,
trying with legacy format
# [2010-07-18 21:54:22.288] Connecting Bluetooth device with address
0C:DD:EF:9C:94:8B and channel 25
# [2010-07-18 21:54:22.340] OBEX progress
# [2010-07-18 21:54:22.367] Cancel disconncting process
# [2010-07-18 21:54:22.370] TransportException thrown at
> /work/runtests/head/syncevolution/src/syncevo/ObexTransportAgent.cpp:376
# [2010-07-18 21:54:22.371] ObexTransprotAgent: Underlying transport error
This issue is just a reminder that the problem exists. We (= the SyncEvolution
developers) cannot do anything about it.
--
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.
10 years, 9 months
[MeeGo Projects - Bug 7091] New: In Direct Sync Settings the checkboxes for send and receive are interchanged
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=7091
Summary: In Direct Sync Settings the checkboxes for send and
receive are interchanged
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: major
Priority: Undecided
Component: GTK UI
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: oliver.joos(a)freenet.ch
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-gtk-ui-bugs(a)meego.bugs
Estimated Hours: 0.0
I use SyncEvolution 1.0.1 on a Notebook running Ubuntu 10.04.
BUG DETAILED DESCRIPTIONS
The settings of a Direct-Sync Service (Bluetooth) shows two checkboxes, one to
"Send changes to MYPHONE" the other to "Receive changes from MYPHONE". The
labels of these two buttons are interchanged.
EXACT STEPS LEADING TO PROBLEM:
1. Start sync-ui
2. Press "Change or edit sync service"
3. Unfold a Direct Sync service
4. Check "Send changes to MYPHONE"
5. "Save and use" this unidirectional service
6. Test the service with "Sync Now"
EXPECTED OUTCOME: Changes in Evolution are transfered to MYPHONE, while changes
in MYPHONE are ignored and not sent to Evolution
ACTUAL OUTCOME: It does the opposite of what the checked checkbox label says.
USER IMPACT: This might cause data loss! E.g when installing a new Linux and
then running a Sync only with "Receive changes from MYPHONE" checked.
REPRODUCIBILITY: always
EXTRA SOFTWARE INSTALLED: none
--
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.
10 years, 9 months
[Bug 2566] New: Evolution contacts loose "Other" email-addresses when synced two-way with a Nokia S60
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=2566
Summary: Evolution contacts loose "Other" email-addresses when
synced two-way with a Nokia S60
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
URL: http://bugzilla.moblin.org/show_bug.cgi?id=10505
OS/Version: ---
Status: ASSIGNED
Severity: enhancement
Priority: Medium
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
Copied from http://bugzilla.moblin.org/show_bug.cgi?id=10505
Description From oliver-joos 2010-05-28 15:24:05 PST (-) [reply]
I use Evolution 2.28.1 on Ubuntu 9.10 and SyncEvolution 1.0beta3, compiled from
sources. I tried to sync contacts with my Nokia N81 (Symbian S60v3).
In Evolution a contact may have upto 4 email-addresses, each of type Home, Work
or Other. Multiple Home or Work addresses are sync'ed ok. But my phone seems to
dispose addresses of type "Other" that come from Evolution! When I then modify
other items of such a contact, then it is sync'ed back to Evolution - without
the "Other" addresses. They get lost on both sides!
The output shows that Evolution addresses of type "Other" seem to have no
"TYPE=" at all. Perhaps Symbian S60v3 does not like that.
EMAIL;TYPE=HOME:my_home@mail.com
EMAIL:my_other@mail.com
I am not sure, but I think I experienced similar problems with "Other" phone
numbers.
--
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.
10 years, 9 months
[MeeGo Platform - Bug 11366] New: libsoup overrides http_proxy with invalid string: breaks SyncEvolution
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=11366
Summary: libsoup overrides http_proxy with invalid string:
breaks SyncEvolution
Classification: MeeGo Platform
Product: OS Middleware
Version: 1.2
Platform: All
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: patrick.ohly(a)intel.com
ReportedBy: han.dai(a)intel.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs, dwmw2(a)linux.intel.com
Blocks: 10015
Estimated Hours: 0.0
Syncevolution doesn't use libproxy to find current proxy information as
provided by ConnMan; it seems to be looking at the static settings in gconf.
And even when those are *correct*, it's broken -- it seems to connect to port
*zero* of the host which GConf tells it is serving the proxy PAC script.
--- Comment #1 from dwmw2intel <dwmw2(a)linux.intel.com> 2010-11-13 14:08:53 PST ---
Hm, it is using the proxy resolver from libsoup-gnome, which would have worked.
But then it's *overriding* the proxy with the string
'pac+http://autoproxy.intel.com/'.
Soup doesn't recognise 'pac+http' as a URL scheme, and that's probably what
leads to the attempt to contact port 0.
I can't quite work out where it's pulling that bogus override string from.
This is also happening in MeeGo 1.1.
--- Comment #2 from pohly <patrick.ohly(a)intel.com> 2010-11-14 11:58:31 PST ---
(In reply to comment #1)
> Hm, it is using the proxy resolver from libsoup-gnome, which would have worked.
> But then it's *overriding* the proxy with the string
> 'pac+http://autoproxy.intel.com/'.
>
> Soup doesn't recognise 'pac+http' as a URL scheme, and that's probably what
> leads to the attempt to contact port 0.
>
> I can't quite work out where it's pulling that bogus override string from.
Is it perhaps somewhere in your SyncEvolution config (proxyHost) or environment
(http_proxy). Those override the automatism in libsoup, if set (which normally
they shouldn't be in MeeGo).
I cannot think of any other reason why SyncEvolution should set the proxy
information.
--- Comment #3 from dwmw2intel <dwmw2(a)linux.intel.com> 2010-11-14 13:17:59 PST ---
Something seems to be automatically setting this. It certainly wasn't me --
this is a clean install of the current MeeGo IT Build.
--- Comment #4 from dwmw2intel <dwmw2(a)linux.intel.com> 2010-11-14 13:18:23 PST ---
I don't know where to find the syncevolution configuration files to check...
--- Comment #5 from pohly <patrick.ohly(a)intel.com> 2010-11-14 23:17:16 PST ---
(In reply to comment #4)
> I don't know where to find the syncevolution configuration files to check...
"syncevolution --print-configs" gives a list of configurations and their
location on disk, "syncevolution --print-config -q <config name>" summarizes
all relevant options for a config (takes properties from multiple files).
--- Comment #6 from dwmw2 <dwmw2(a)infradead.org> 2010-11-20 16:41:46 PST ---
[dwoodhou@dwoodhou-mobl4 ~]$ syncevolution --print-config google | grep proxy
# set to T to choose an HTTP proxy explicitly; otherwise the default
# proxy settings of the underlying HTTP transport mechanism are used;
# proxy URL (http://<host>:<port>)
# proxyHost =
# authentication for proxy: username
# proxyUsername =
# proxy password, can be specified in different ways,
# proxyPassword =
# per-peer (unshared) properties: syncURL, username, password, loglevel,
printChanges, autoSync, autoSyncInterval, autoSyncDelay, preventSlowSync,
useProxy, proxyHost, proxyUsername, proxyPassword, clientAuthType,
RetryDuration, RetryInterval, remoteIdentifier, PeerIsClient, SyncMLVersion,
PeerName, remoteDeviceId, enableWBXML, maxMsgSize, maxObjSize,
enableCompression, SSLServerCertificates, SSLVerifyServer, SSLVerifyHost,
WebURL, IconURI, ConsumerReady
--- Comment #7 from pohly <patrick.ohly(a)intel.com> 2010-11-21 05:39:19 PST ---
Is the "http_proxy" env variable set in the environment of the SyncEvolution
process?
--- Comment #8 from dwmw2 <dwmw2(a)infradead.org> 2010-11-21 12:16:32 PST ---
No.
This should be easy to reproduce with the image from
http://opensource.intel.com/linux-wiki/MeeGoITBuild
--- Comment #9 from pohly <patrick.ohly(a)intel.com> 2010-11-22 01:24:59 PST ---
(In reply to comment #8)
> This should be easy to reproduce with the image from
> http://opensource.intel.com/linux-wiki/MeeGoITBuild
I tried to reproduce it, but half-way through the install process realized that
it would probably only occur when inside Intel. At home, I cannot even set up
the Intel specific part of that image - at least not easily. I know about the
tricks with routing traffic through a connected machine, but that's too
involved for now. I'll be in the Ulm site tomorrow and will try again there.
--- Comment #10 from dwmw2 <dwmw2(a)infradead.org> 2010-11-22 03:08:14 PST ---
You don't have to route through a connected machine. Just use 'openconnect
--cookieonly' to get a VPN cookie on another machine, then use connman's
connect-vpn script to *connect* using that cookie from your test box.
Note that you have to transfer ~/.cert/intel-certchain.crt from your existing
machine to the MeeGo box, so that openconnect can validate the server's SSL
certificate. Then:
/usr/lib/connman/test/connect-vpn openconnect "my VPN" $SERVERIP intel.com
$COOKIE /where/you/put/intel-certchain.crt
You can ssh into the machine as root using the password 'meego' while it's
sitting at the firstboot screen. There's no way to make it tell you its IP
addresses from the UI, so watch for it doing mDNS or note its IP address before
you reinstall it (for IPv6 at least it should have a constant address; for
Legacy IP there are a lot of buggy DHCP servers out there which will move it
around).
--- Comment #11 from pohly <patrick.ohly(a)intel.com> 2010-11-24 03:38:26 PST ---
I found that getenv("http_proxy") returns the "pac+http://autoproxy.intel.com"
string. But is indeed not in the environment. That leaves a setenv() call at
runtime, and indeed, here it is:
Breakpoint 1, __setenv (name=0x4285a353 "http_proxy", value=0x82d56a8
"pac+http://autoproxy.intel.com/",
replace=1) at setenv.c:268
268 if (name == NULL || *name == '\0' || strchr (name, '=') != NULL)
(gdb) where
#0 __setenv (name=0x4285a353 "http_proxy", value=0x82d56a8
"pac+http://autoproxy.intel.com/", replace=1)
at setenv.c:268
#1 0x417e0b52 in g_setenv () from /lib/libglib-2.0.so.0
#2 0x4285913a in ?? () from /usr/lib/libsoup-gnome-2.4.so.1
#3 0x428595d4 in ?? () from /usr/lib/libsoup-gnome-2.4.so.1
#4 0x4285975c in ?? () from /usr/lib/libsoup-gnome-2.4.so.1
#5 0x41880be4 in g_type_create_instance () from /lib/libgobject-2.0.so.0
#6 0x41879047 in ?? () from /lib/libgobject-2.0.so.0
#7 0x4187954c in g_object_newv () from /lib/libgobject-2.0.so.0
#8 0x41879714 in g_object_new () from /lib/libgobject-2.0.so.0
#9 0x42cca3bd in soup_session_add_feature_by_type () from
/usr/lib/libsoup-2.4.so.1
#10 0x42f9f543 in SyncEvo::SoupTransportAgent::SoupTransportAgent (this=<value
optimized out>,
loop=<value optimized out>) at SoupTransportAgent.cpp:48
SyncEvolution then picks up that value and passes it to libsoup again.
Note that I wasn't even connected to the Intel intranet while doing the run
above. Therefore the sync failed with:
[INFO] SoupTransport Failure: https://m.google.com/syncml via libsoup: Cannot
resolve proxy hostname
I don't know why libsoup does that. /system/proxy/autoconfig_url is set to
http://autoproxy.intel.com, but /system/http_proxy/use_http_proxy is off.
Any suggestions how this should be fixed? Move the http_proxy check in
SyncEvolution to a point before libsoup has a chance to mess with the
environment? That feels like working around the issue instead of fixing it,
because other apps invoked indirectly will still inherit the wrong environment.
--- Comment #12 from pohly <patrick.ohly(a)intel.com> 2010-11-24 03:46:34 PST ---
Somehow I get the same "cannot connect to proxy host" even while VPN is up.
There's no telnet installed (or available?!), but Chrome has no problem
accessing http:://autoproxy.intel.com. Is it the pac+http scheme which is
causing that problem?
--- Comment #13 from dwmw2 <dwmw2(a)infradead.org> 2010-11-24 03:48:11 PST ---
Yeah, pac+http:// is complete nonsense.
--- Comment #14 from dwmw2 <dwmw2(a)infradead.org> 2010-11-24 03:53:13 PST ---
I'm confused. libsoup-gnome should only be doing this crappy setenv thing if
it's using a *really* old version of libproxy:
AC_MSG_CHECKING(libproxy version)
libproxy_version=`$PKG_CONFIG --modversion libproxy-1.0`
case $libproxy_version in
0.2.*)
AC_MSG_RESULT([$libproxy_version, using workarounds...])
AC_DEFINE(HAVE_LIBPROXY_WITH_NON_THREAD_SAFE_GNOME_MODULE, 1,
[Defined if libproxy is old and has a non-thread-safe gnome module])
/* If we have a "bad" libproxy, set environment variables
* and force it to use them.
*/
#ifdef HAVE_LIBPROXY_WITH_NON_THREAD_SAFE_GNOME_MODULE
g_setenv ("PX_CONFIG_ORDER", "envvar", TRUE);
if (http_proxy)
g_setenv ("http_proxy", http_proxy, TRUE);
We have never had libproxy 0.2 in MeeGo, although now we're using PacRunner it
may advertise itself as 0.1.
--- Comment #15 from pohly <patrick.ohly(a)intel.com> 2010-11-24 03:53:45 PST ---
(In reply to comment #0)
> And even when those are *correct*, it's broken -- it seems to connect to port
> *zero* of the host which GConf tells it is serving the proxy PAC script.
That answers my previous question about "cannot connect to proxy host". It
seems that pac+http leads to "let's try port 0". Setting port 80 in the
autoconfig_url gets me beyond that, but then it fails with:
[INFO] SoupTransport Failure: https://m.google.com/syncml via libsoup:
Connection terminated unexpectedly
I have not done any network dumps to investigate that further.
--- Comment #16 from dwmw2 <dwmw2(a)infradead.org> 2010-11-24 04:03:53 PST ---
https://bugzilla.gnome.org/show_bug.cgi?id=603285
Fixed in libsoup commit 25bfd5cbcfb93b94efc7c0f6f0d4bbfa51244e42
Although ideally we should just drop libproxy completely and talk D-Bus
directly to pacrunner.
--- Comment #17 from dwmw2 <dwmw2(a)infradead.org> 2010-11-24 04:21:36 PST ---
Thanks for the diagnosis. A fixed package should now be available in the
devel:enterprise repository at
http://download.meego.com/live/devel:/enterprise/MeeGo_1.1_Netbook/
--- Comment #18 from dwmw2 <dwmw2(a)infradead.org> 2010-11-24 04:27:58 PST ---
Yan, this probably wants to get into the 1.0 build for Fab28 too.
--- Comment #19 from dwmw2intel <dwmw2(a)linux.intel.com> 2010-12-03 10:00:29 PST ---
I've pushed the fix into devel:enterprise:1.0 for Fab 28 too.
--- Comment #20 from daihan <han.dai(a)intel.com> 2010-12-14 17:55:46 PST ---
submitted the patch in devel:enterprise/libsoup to
MeeGo:1.1:Core:Update:Testing
request id 10924
--- Comment #21 from dwmw2intel <dwmw2(a)linux.intel.com> 2010-12-15 07:47:51 PST ---
Submitted to Trunk too, but it was pointlessly rejected. Apparently we need a
*separate* bug filed against Trunk, and the changelog there must reference
*that* bug, so the Trunk and 1.1 packages would be gratuitously different
despite having exactly the same code.
Clever.
Really, this is not the way to build a community and encourage people to
contribute.
--- Comment #22 from daihan <han.dai(a)intel.com> 2010-12-15 18:32:16 PST ---
+++ This bug was initially created as a clone of Bug #10015 +++
--
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.
10 years, 9 months
[MeeGo Projects - Bug 12267] New: syncevo-phone-config.py doesn't create workable config for Nokia 5130c-2 or Nokia 6303i classic
by bugzilla＠meego.com
http://bugs.meego.com/show_bug.cgi?id=12267
Summary: syncevo-phone-config.py doesn't create workable config
for Nokia 5130c-2 or Nokia 6303i classic
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: mpppppp.123(a)gmail.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
latest python script used
1:1.1.1-2 (syncevolution-evolution)
ubuntu 10.10
mppppppp@EasyNote-TK81:~$ hcitool scan
Scanning ...
6C:9B:02:E4:21:C4 Nokia 6303i classic
00:1E:B2:3C:DB:7E 42SL9500-ZB
20:D6:07:FC:17:90 Nokia 5130c-2
mppppppp@EasyNote-TK81:~$ python test_syncevo-phone-config.py -b
20:D6:07:FC:17:90 --advanced --create-config=nokia5130c-2
Running test with test data inside /tmp/syncevo-phone-configSGCsWJ/data and
test results inside /tmp/syncevo-phone-configSGCsWJ/cache
Starting test for 1188 configurations...
Start 1/1188 test
...
...
..
We have conducted basic test by sending and receiving
data to the phone. You can help the SyncEvolution project
and other users by submitting the following configuration
template at http://syncevolution.org/wiki/phone-compatibility-template
--------------------> snip <--------------------
=== template.ini ===
fingerprint = <Model> <Manufacturer>
=== config.ini ===
peerIsClient = 1
consumerReady = 1
=== sources/calendar+todo/config.ini ===
evolutionsource = calendar,todo
type = virtual:text/calendar
uri = Calendar
=== sources/addressbook/config.ini ===
type = addressbook:text/x-vcard
sync = two-way
uri = Contact
=== sources/calendar/config.ini ===
type = calendar:text/calendar
sync = none
=== sources/todo/config.ini ===
type = todo:text/calendar
sync = none
=== sources/memo/config.ini ===
type = memo:text/plain
sync = two-way
uri = Memo
--------------------> snip <--------------------
Created configuration: nokia5130c-2
You may start syncing with: syncevolution nokia5130c-2
mpppppp@EasyNote-TK81:~$ syncevolution nokia5130c-2
[INFO] Server sending SAN
Local data changes to be applied remotely during synchronization:
*** addressbook ***
Comparison was impossible.
[INFO] addressbook: started
*** calendar ***
Comparison was impossible.
[INFO] calendar: started
[INFO] adding "do me"
[ERROR] calendar: extracting event
*** memo ***
Comparison was impossible.
[INFO] memo: started
[ERROR] OBEX Request 3 got a failed response Bad Request
[ERROR] ObexTransprotAgent: Underlying transport error
[INFO] calendar: inactive
[ERROR] aborted on behalf of user (local, status 20017)
[INFO] memo: inactive
[ERROR] aborted on behalf of user (local, status 20017)
[INFO] addressbook: inactive
[ERROR] aborted on behalf of user (local, status 20017)
Synchronization failed, see
/home/mpppppp/.cache/syncevolution/nokia5130c_+2-2011-01-12-00-14/syncevolution-log.html
for details.
--
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.
10 years, 9 months