You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
(10) |
Apr
(30) |
May
(11) |
Jun
(8) |
Jul
(28) |
Aug
(113) |
Sep
(74) |
Oct
(43) |
Nov
(111) |
Dec
(31) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(70) |
Feb
(78) |
Mar
(110) |
Apr
(99) |
May
(106) |
Jun
(128) |
Jul
(65) |
Aug
(123) |
Sep
(80) |
Oct
(128) |
Nov
(80) |
Dec
(54) |
2007 |
Jan
(89) |
Feb
(83) |
Mar
(56) |
Apr
(56) |
May
(69) |
Jun
(29) |
Jul
(89) |
Aug
(44) |
Sep
(32) |
Oct
(114) |
Nov
(36) |
Dec
(46) |
2008 |
Jan
(88) |
Feb
(100) |
Mar
(63) |
Apr
(27) |
May
(39) |
Jun
(61) |
Jul
(35) |
Aug
(11) |
Sep
(9) |
Oct
(19) |
Nov
(28) |
Dec
(72) |
2009 |
Jan
(33) |
Feb
(4) |
Mar
(15) |
Apr
(24) |
May
(17) |
Jun
(17) |
Jul
(11) |
Aug
(30) |
Sep
(19) |
Oct
(8) |
Nov
(10) |
Dec
(5) |
2010 |
Jan
(5) |
Feb
(10) |
Mar
(12) |
Apr
(1) |
May
(8) |
Jun
(4) |
Jul
(9) |
Aug
(29) |
Sep
(6) |
Oct
(19) |
Nov
(4) |
Dec
(3) |
2011 |
Jan
(9) |
Feb
|
Mar
|
Apr
(7) |
May
(2) |
Jun
(9) |
Jul
(3) |
Aug
(2) |
Sep
|
Oct
|
Nov
(7) |
Dec
|
2012 |
Jan
(2) |
Feb
(5) |
Mar
(5) |
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(9) |
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(5) |
From: Norm D. <no...@dr...> - 2006-03-06 14:07:23
|
Given that SyncML won't work (right now) with the 6620, what are the chances of getting Obex to work on it? What do the error 80 and error 64 mean? Maybe there's a chance for it to work? Norm On Mon, 2006-03-06 at 02:27 +0100, Armin Bauer wrote: > the contacts database on your phone is named "addressbook", so you have > to use this as the database name: --sync vcard addressbook > > Best Regards, > Armin > > Norm Dressler wrote: > > Unfortunately neither Obex nor http works on my 6620. > > > > First Obex sync: It fails with error 80 or error 64. I've tried with > > wbxml, or without. When I do syncml-obex-client I get: > > Found 2 USB OBEX interfaces > > Interface 0: > > Manufacturer: Nokia > > Product: Nokia 6620 > > Interface description: SYNCML-SYNC > > Interface 1: > > Manufacturer: Nokia > > Product: Nokia 6620 > > Interface description: PC Suite Services > > Use '-u interface_number' to connect > > > > I've tried both 0 and 1 in the identifier and I've tried all versions of > > Syncml. Set with no username or password. > > > > With HTTP: The phone sits on Initializing forever. I've attached the > > syncml traces. This is the same as what I had previously. > > > > My kingdom for a good sync with linux --- > > > > Norm |
From: Armin B. <arm...@de...> - 2006-03-06 14:01:25
|
Anders Hermansen wrote: > Armin Bauer wrote: > >>adding bluetooth support to libsyncml is fairly trivial. The only thing >>that has to be done is to expose the configuration through the config if >>the obex transport and add the appropiate connection code (which can be >>copied from obexftp). After that, libsyncml can handle bluetooth. Adding >>support for irda would be the same procedure. > > > Attached is a patch which does this. I tested it with the > syncml-obex-client and my 6680. And it works :) > cool :) i will try your patch right away and then commit it to the repository. thanks! > I have not tried the syncml-plugin yet. But it probably needs some easy > configuration patching too. > > To find your bluetooth address run: > hcitool scan > > To find your bluetooth channel run: > sdptool browse <bt-addr> > > Look for SyncMLClient, on my 6680 it was channel 11. > > Instead of "-u <usb-id>" use "-b <bt-addr> <bt-channel>". > > Armin: I just reused some of the available config variables. Tell me if > you want me to change that so the names are more logic. i think it is ok to reuse. I think the developers will understand what they mean. > > Armin2: I still get hangups when doing a slow-sync. Can I send you some > more dumps for debugging? Sure! traces are always welcome. Armin |
From: Anders H. <an...@gi...> - 2006-03-06 13:54:22
|
Armin Bauer wrote: > adding bluetooth support to libsyncml is fairly trivial. The only thing > that has to be done is to expose the configuration through the config if > the obex transport and add the appropiate connection code (which can be > copied from obexftp). After that, libsyncml can handle bluetooth. Adding > support for irda would be the same procedure. Attached is a patch which does this. I tested it with the syncml-obex-client and my 6680. And it works :) I have not tried the syncml-plugin yet. But it probably needs some easy configuration patching too. To find your bluetooth address run: hcitool scan To find your bluetooth channel run: sdptool browse <bt-addr> Look for SyncMLClient, on my 6680 it was channel 11. Instead of "-u <usb-id>" use "-b <bt-addr> <bt-channel>". Armin: I just reused some of the available config variables. Tell me if you want me to change that so the names are more logic. Armin2: I still get hangups when doing a slow-sync. Can I send you some more dumps for debugging? Anders |
From: Luca <gol...@li...> - 2006-03-06 11:38:00
|
Here is the log! :D [1141644697.991048] >>>>>>> osync_env_initialize(0x804ed88, 0xbfa25be8) [1141644697.991137] >>>>>>> osync_env_load_plugins(0x804ed88, (null), 0xbfa25be8) [1141644697.991169] >>>>>>> osync_module_load_dir(0x804ed88, /usr/lib/opensync/plugins, 0xbfa25be8) [1141644697.991271] >>>>>>> osync_module_load(0x804ed88, /usr/lib/opensync/plugins/evo2_sync.so, 0xbfa25b48) [1141644698.152462] osync_plugin_new_info(0x804ed88): 0x80588d0 [1141644698.152527] <<<<<<< osync_module_load: 0x8058000 [1141644698.152578] >>>>>>> osync_module_load(0x804ed88, /usr/lib/opensync/plugins/irmc_sync.so, 0xbfa25b48) [1141644698.182491] osync_plugin_new_info(0x804ed88): 0x8059598 [1141644698.182535] <<<<<<< osync_module_load: 0x8059580 [1141644698.182585] >>>>>>> osync_module_load(0x804ed88, /usr/lib/opensync/plugins/gnokii_sync.so, 0xbfa25b48) [1141644698.301961] osync_plugin_new_info(0x804ed88): 0x8057f40 [1141644698.302006] <<<<<<< osync_module_load: 0x8057f28 [1141644698.302056] >>>>>>> osync_module_load(0x804ed88, /usr/lib/opensync/plugins/file_sync.so, 0xbfa25b48) [1141644698.376330] osync_plugin_new_info(0x804ed88): 0x805c0d8 [1141644698.376374] <<<<<<< osync_module_load: 0x805c0c0 [1141644698.376425] <<<<<<< osync_module_load_dir [1141644698.376450] <<<<<<< osync_env_load_plugins [1141644698.376478] >>>>>>> osync_env_load_formats(0x804ed88, (null), 0xbfa25be8) [1141644698.376503] >>>>>>> osync_module_load_dir(0x804ed88, /usr/lib/opensync/formats, 0xbfa25be8) [1141644698.376583] >>>>>>> osync_module_load(0x804ed88, /usr/lib/opensync/formats/data.so, 0xbfa25b48) [1141644698.376775] osync_env_format_set_compare_func(0x804ed88, plain, 0xb7e5a784) [1141644698.376805] <<<<<<< osync_module_load: 0x805c350 [1141644698.376849] >>>>>>> osync_module_load(0x804ed88, /usr/lib/opensync/formats/gnokii.so, 0xbfa25b48) [1141644698.411096] <--- ERROR --- osync_module_load: Unable to open module /usr/lib/opensync/formats/gnokii.so: /usr/lib/opensync/formats/gnokii.so: undefined symbol: osxml_get_node [1141644698.411133] [OSPLG] ERROR: Unable to load plugin /usr/lib/opensync/formats/gnokii.so: Unable to open module /usr/lib/opensync/formats/gnokii.so: /usr/lib/opensync/formats/gnokii.so: undefined symbol: osxml_get_node [1141644698.411182] >>>>>>> osync_module_load(0x804ed88, /usr/lib/opensync/formats/xml-kde.so, 0xbfa25b48) [1141644698.412115] <<<<<<< osync_module_load: 0x805c8f8 [1141644698.412163] >>>>>>> osync_module_load(0x804ed88, /usr/lib/opensync/formats/xml-vnote.so, 0xbfa25b48) [1141644698.412863] osync_env_format_set_compare_func(0x804ed88, xml-note, 0xb7226432) [1141644698.412899] <<<<<<< osync_module_load: 0x805d370 [1141644698.412944] >>>>>>> osync_module_load(0x804ed88, /usr/lib/opensync/formats/xml-evolution.so, 0xbfa25b48) [1141644698.415458] <<<<<<< osync_module_load: 0x805dce0 [1141644698.415515] >>>>>>> osync_module_load(0x804ed88, /usr/lib/opensync/formats/contact.so, 0xbfa25b48) [1141644698.415712] osync_env_format_set_compare_func(0x804ed88, vcard21, 0xb73bd9a4) [1141644698.415746] osync_env_format_set_compare_func(0x804ed88, vcard30, 0xb73bd9a4) [1141644698.415776] <<<<<<< osync_module_load: 0x805de08 [1141644698.415820] >>>>>>> osync_module_load(0x804ed88, /usr/lib/opensync/formats/file.so, 0xbfa25b48) [1141644698.416011] osync_env_format_set_compare_func(0x804ed88, file, 0xb73baca4) [1141644698.416041] <<<<<<< osync_module_load: 0x805e5c8 [1141644698.416086] >>>>>>> osync_module_load(0x804ed88, /usr/lib/opensync/formats/xml-vcard.so, 0xbfa25b48) [1141644698.416775] osync_env_format_set_compare_func(0x804ed88, xml-contact, 0xb71574b5) [1141644698.416808] <<<<<<< osync_module_load: 0x805dec0 [1141644698.416852] >>>>>>> osync_module_load(0x804ed88, /usr/lib/opensync/formats/todo.so, 0xbfa25b48) [1141644698.417035] osync_env_format_set_compare_func(0x804ed88, vtodo10, 0xb72188c4) [1141644698.417379] osync_env_format_set_compare_func(0x804ed88, vtodo20, 0xb72188c4) [1141644698.417407] <<<<<<< osync_module_load: 0x805f0f0 [1141644698.417455] >>>>>>> osync_module_load(0x804ed88, /usr/lib/opensync/formats/event.so, 0xbfa25b48) [1141644698.417644] osync_env_format_set_compare_func(0x804ed88, vevent10, 0xb71518c4) [1141644698.417677] osync_env_format_set_compare_func(0x804ed88, vevent20, 0xb71518c4) [1141644698.417705] <<<<<<< osync_module_load: 0x805afc8 [1141644698.417748] >>>>>>> osync_module_load(0x804ed88, /usr/lib/opensync/formats/note.so, 0xbfa25b48) [1141644698.417928] osync_env_format_set_compare_func(0x804ed88, vnote11, 0xb714f90c) [1141644698.417955] <<<<<<< osync_module_load: 0x805fd60 [1141644698.417998] >>>>>>> osync_module_load(0x804ed88, /usr/lib/opensync/formats/xml-vcal.so, 0xbfa25b48) [1141644698.418700] osync_env_format_set_compare_func(0x804ed88, xml-event, 0xb7146198) [1141644698.418740] osync_env_format_set_compare_func(0x804ed88, xml-todo, 0xb714622f) [1141644698.418772] <<<<<<< osync_module_load: 0x8060210 [1141644698.418816] <<<<<<< osync_module_load_dir [1141644698.418841] <<<<<<< osync_env_load_formats [1141644698.419768] [OSUSR] DEBUG: Detected User: UID: 1000 GID: 100 Home: /home/ashura OSyncDir: /home/ashura/.opensync [1141644698.419844] >>>>>>> osync_group_load(0x804ed88, /home/ashura/.opensync/group1, 0xbfa25b6c) [1141644698.419874] [OSGRP] DEBUG: Trying to load group from directory /home/ashura/.opensync/group1 [1141644698.419908] >>>>>>> osync_conv_env_new(0x804ed88) [1141644698.419969] New converter from vnote11 to xml-note [1141644698.419994] New converter from xml-note to vnote11 [1141644698.420018] New converter from file to plain [1141644698.420042] New converter from plain to file [1141644698.420066] New converter from vcard21 to xml-contact [1141644698.420090] New converter from xml-contact to vcard21 [1141644698.420115] New converter from vcard30 to xml-contact [1141644698.420142] New converter from xml-contact to vcard30 [1141644698.420167] New converter from vevent10 to xml-event [1141644698.420192] New converter from xml-event to vevent10 [1141644698.420217] New converter from vevent20 to xml-event [1141644698.420241] New converter from xml-event to vevent20 [1141644698.420266] New converter from vtodo10 to xml-todo [1141644698.420290] New converter from xml-todo to vtodo10 [1141644698.420314] New converter from vtodo20 to xml-todo [1141644698.420338] New converter from xml-todo to vtodo20 [1141644698.420389] <<<<<<< osync_conv_env_new: 0x8060a98 [1141644698.420777] >>>>>>> osync_member_load(0x8060b50, /home/ashura/.opensync/group1/1, 0xbfa25b6c) [1141644698.420911] <<<<<<< osync_member_load: Loaded member: 0x8062c78 [1141644698.420952] <<<<<<< osync_group_load [1141644698.420986] <<<<<<< osync_env_initialize [1141644698.421032] [OSMEM] DEBUG: Instancing plugin gnokii-sync for member 0 [1141644698.421864] >>>>>>> osync_env_finalize(0x804ed88, 0xbfa25be8) [1141644698.421903] osync_plugin_free(0x80588d0) [1141644698.421927] osync_plugin_free(0x8059598) [1141644698.421951] osync_plugin_free(0x8057f40) [1141644698.421975] osync_plugin_free(0x805c0d8) [1141644698.422004] osync_module_unload(0x804ed88, 0x8058000) [1141644698.422028] osync_module_unload(0x804ed88, 0x8059580) [1141644698.422052] osync_module_unload(0x804ed88, 0x8057f28) [1141644698.422075] osync_module_unload(0x804ed88, 0x805c0c0) [1141644698.422098] osync_module_unload(0x804ed88, 0x805c350) [1141644698.422122] osync_module_unload(0x804ed88, 0x805c8f8) [1141644698.422145] osync_module_unload(0x804ed88, 0x805d370) [1141644698.422169] osync_module_unload(0x804ed88, 0x805dce0) [1141644698.422192] osync_module_unload(0x804ed88, 0x805de08) [1141644698.422216] osync_module_unload(0x804ed88, 0x805e5c8) [1141644698.422239] osync_module_unload(0x804ed88, 0x805dec0) [1141644698.422262] osync_module_unload(0x804ed88, 0x805f0f0) [1141644698.422285] osync_module_unload(0x804ed88, 0x805afc8) [1141644698.422308] osync_module_unload(0x804ed88, 0x805fd60) [1141644698.422331] osync_module_unload(0x804ed88, 0x8060210) [1141644698.422358] <<<<<<< osync_env_finalize |
From: Daniel G. <dg...@su...> - 2006-03-06 07:56:59
|
On Sun, 2006-03-05 at 14:00 +0100, Luca wrote: > > Which version of gnokii do you have? You can get this with: pkg-config > > --modversion gnokii > > ashura@anoth ~ $ pkg-config --modversion gnokii > 0.6.11 > > > export OSYNC_TRACE=/tmp/osync-gnokii-trace/ msynctool --addmember > > evognokii gnokii-sync > > it does nothing :( > I tried to export another path, but nothing worked too... Oh - you have to create this folder before running msynctool. mkdir /tmp/gnokii-sync/ OSYNC_TRACE=/tmp/gnokii-sync/ msynctool --addmember evognokii gnokii-sync (maybe you are using another shell?) > > If you wish, i have msn...we can communicate with that... or via jabber, > icq and so on. Try to contact me in #opensync on irc.freenode.net |
From: Daniel G. <dg...@su...> - 2006-03-06 07:50:48
|
On Sun, 2006-03-05 at 14:00 +0100, Luca wrote: > > it does nothing :( > I tried to export another path, but nothing worked too... > > If you wish, i have msn...we can communicate with that... or via > jabber, > icq and so on. |
From: Norm D. <no...@dr...> - 2006-03-06 01:47:35
|
Thanks Armin, I matched the database names on the phone and in the config file and now I'm getting a segmentation fault -- [norm@lapzilla syncml]$ msynctool --sync sml --wait Synchronizing group "sml" The previous synchronization was unclean. Slow-syncing I/O error : Attempt to load network entity http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd received contact dsession received event dsession Member 2 of type file-sync just connected Member 1 of type syncml-http-server just connected All clients connected or error Member 2 of type file-sync just sent all changes I/O error : Attempt to load network entity http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd Member 1 of type syncml-http-server had an error while getting changes: No node at all Segmentation fault My config file looks like this: <config><username></username><password></password><url></url><port>8080</port><usestringtable>1</usestringtable><onlyreplace>0</onlyreplace><recvLimit>0</recvLimit><contact_db>addressbook</contact_db><calendar_db>calendar</calendar_db><note_db>notes</note_db></config> Attached are the logs if they help. The error is a bit non-descript.. Norm On Mon, 2006-03-06 at 02:27 +0100, Armin Bauer wrote: > the contacts database on your phone is named "addressbook", so you have > to use this as the database name: --sync vcard addressbook > > Best Regards, > Armin > > Norm Dressler wrote: > > Unfortunately neither Obex nor http works on my 6620. > > > > First Obex sync: It fails with error 80 or error 64. I've tried with > > wbxml, or without. When I do syncml-obex-client I get: > > Found 2 USB OBEX interfaces > > Interface 0: > > Manufacturer: Nokia > > Product: Nokia 6620 > > Interface description: SYNCML-SYNC > > Interface 1: > > Manufacturer: Nokia > > Product: Nokia 6620 > > Interface description: PC Suite Services > > Use '-u interface_number' to connect > > > > I've tried both 0 and 1 in the identifier and I've tried all versions of > > Syncml. Set with no username or password. > > > > With HTTP: The phone sits on Initializing forever. I've attached the > > syncml traces. This is the same as what I had previously. > > > > My kingdom for a good sync with linux --- > > > > Norm |
From: Armin B. <arm...@de...> - 2006-03-06 01:37:45
|
Stef Epardaud wrote: > Hello, > > I just noticed the front page of the opensync.org website advises > everyone to test the SyncML plugin. After fighting a bit with makefiles > in libsyncml in order to not get any HTTP support, I managed to compile > everything. I am really very exited about this release and thank all of > you very much for it, I can't wait to have sync support for my phone! > > But in the end I'm stuck: it looks as if only obex over USB or HTTP is > supported, but I need bluetooth in order to test. I've tried opening an > rfcomm connection to the SyncML Client channel on my phone and bind it > to /dev/rfcomm0, then attempting to use the BLUETOOTH transport of > libsyncml by giving it the path to the device, but that did not work. > It looks as if making the syncml plugin support the bluetooth libsyncml > transport is easy enough, but there doesn't seem to be the proper > support for bluetooth in libsyncml yet, or am I wrong ? > Do you have any release plan for bluetooth support so that I can test > this great plugin ? > Thanks. Hi Stef, adding bluetooth support to libsyncml is fairly trivial. The only thing that has to be done is to expose the configuration through the config if the obex transport and add the appropiate connection code (which can be copied from obexftp). After that, libsyncml can handle bluetooth. Adding support for irda would be the same procedure. Ill see if i get around to adding this the next days. I will drop a mail to the mailing list once it is finished. Armin |
From: Armin B. <arm...@de...> - 2006-03-06 01:27:30
|
the contacts database on your phone is named "addressbook", so you have to use this as the database name: --sync vcard addressbook Best Regards, Armin Norm Dressler wrote: > Unfortunately neither Obex nor http works on my 6620. > > First Obex sync: It fails with error 80 or error 64. I've tried with > wbxml, or without. When I do syncml-obex-client I get: > Found 2 USB OBEX interfaces > Interface 0: > Manufacturer: Nokia > Product: Nokia 6620 > Interface description: SYNCML-SYNC > Interface 1: > Manufacturer: Nokia > Product: Nokia 6620 > Interface description: PC Suite Services > Use '-u interface_number' to connect > > I've tried both 0 and 1 in the identifier and I've tried all versions of > Syncml. Set with no username or password. > > With HTTP: The phone sits on Initializing forever. I've attached the > syncml traces. This is the same as what I had previously. > > My kingdom for a good sync with linux --- > > Norm |
From: Armin B. <arm...@de...> - 2006-03-06 01:24:42
|
sorry! did not write this to the list yet: You dont need to patch libsoup anymore. All patches are now upstream. So if you check out from cvs it will be just fine. Sorry again for the confusion! Armin Conrad Wolf wrote: > Hi all! > > I'm new to this list and I've been trying to follow the guide to install > the SyncML-plugin. Installing > > libopensync-0.18, > multisync-0.90.18, > libopensync-plugin-file-0.18 > and libopensync-plugin-evolution2-0.18 > > worked well. Next I checked out libsyncml and libsoup as mentioned in > the guide, but when it came to patching libsoup, I couldn't find out how > to actually do it. I entered the libsoup directory and tried to apply > the patch from libsyncml like this: > > libsoup # patch -p1 <.../libsyncml/misc/libsoup-async-dns.patch > > The output I became showed that the patching failed for several 'hunks': > > patching file ChangeLog > Hunk #1 FAILED at 1. > 1 out of 1 hunk FAILED -- saving rejects to file ChangeLog.rej > patching file libsoup/soup-address.c > Hunk #2 succeeded at 397 with fuzz 2. > Hunk #3 FAILED at 409. > 1 out of 3 hunks FAILED -- saving rejects to file > libsoup/soup-address.c.rej > patching file libsoup/soup-address.h > Hunk #1 succeeded at 81 with fuzz 2 (offset 4 lines). > patching file libsoup/soup-dns.c > Hunk #2 FAILED at 506. > Hunk #3 succeeded at 555 with fuzz 1 (offset 4 lines). > Hunk #4 FAILED at 563. > Hunk #5 succeeded at 574 (offset 5 lines). > Hunk #6 FAILED at 584. > 3 out of 6 hunks FAILED -- saving rejects to file libsoup/soup-dns.c.rej > patching file libsoup/soup-dns.h > Hunk #1 succeeded at 39 with fuzz 2 (offset 1 line). > patching file libsoup/soup-socket.c > Hunk #1 FAILED at 569. > 1 out of 1 hunk FAILED -- saving rejects to file > libsoup/soup-socket.c.rej > patching file tests/dns.c > > When I thereafter try to compile libsoup, compilation fails with the > following output: > > soup-address.c:401: error: conflicting types for > `soup_address_resolve_async' > soup-address.h:80: error: previous declaration of > `soup_address_resolve_async' > soup-address.c: In function `soup_address_resolve_async': > soup-address.c:402: error: too few arguments to function > `soup_address_resolve_async_full' > soup-address.c: At top level: > soup-address.c:419: error: conflicting types for > `soup_address_resolve_async_full' > soup-address.h:85: error: previous declaration of > `soup_address_resolve_async_full' > soup-address.c: In function `soup_address_resolve_async_full': > soup-address.c:430: error: too few arguments to function > `soup_dns_lookup_resolve_async' > make[2]: *** [soup-address.lo] Fehler 1 > make[2]: Leaving directory `/usr/local/src/svn/libsoup/libsoup' > make[1]: *** [install] Fehler 2 > make[1]: Leaving directory `/usr/local/src/svn/libsoup/libsoup' > make: *** [install-recursive] Fehler 1 > > Did I do the patching wrong? Any help would be appreciated. > > Conrad. > > |
From: Armin B. <arm...@de...> - 2006-03-06 01:23:16
|
Michael Kolmodin wrote: > Valgrind reveals an illegal call to free() in xml-vcard.c. The ticket > system does accept my attempt to create a ticket, hangs. It did hang since i have to use a mail relay to send the mails to sourceforge mailinglists. But this relay server was down due to a power loss which lasted longer than the ups :) > > Enclosing patch Thanks! committed. Armin > > -------------------------------------------------------------------------- > Michael Kolmodin Kungsg 24, 1 tr > Phone: +46 920 269413 S-972 31 Lulea > Mobile +46 70 551 6507 Sweden > > > ------------------------------------------------------------------------ > > --- ./opensync-org/formats/vformats-xml/xml-vcard.c 2006-03-05 12:51:05.000000000 +0100 > +++ ./opensync/formats/vformats-xml/xml-vcard.c 2006-03-05 12:46:33.000000000 +0100 > @@ -419,7 +419,7 @@ > * This is necessary because some fields (N and ADR, for example) need > * a specific order of the values > */ > - tmp = ""; > + tmp = g_strdup( "" ); > } > > if (needs_charset((unsigned char*)tmp)) |
From: Stef E. <st...@ep...> - 2006-03-05 19:53:19
|
Hello, I just noticed the front page of the opensync.org website advises everyone to test the SyncML plugin. After fighting a bit with makefiles in libsyncml in order to not get any HTTP support, I managed to compile everything. I am really very exited about this release and thank all of you very much for it, I can't wait to have sync support for my phone! But in the end I'm stuck: it looks as if only obex over USB or HTTP is supported, but I need bluetooth in order to test. I've tried opening an rfcomm connection to the SyncML Client channel on my phone and bind it to /dev/rfcomm0, then attempting to use the BLUETOOTH transport of libsyncml by giving it the path to the device, but that did not work. It looks as if making the syncml plugin support the bluetooth libsyncml transport is easy enough, but there doesn't seem to be the proper support for bluetooth in libsyncml yet, or am I wrong ? Do you have any release plan for bluetooth support so that I can test this great plugin ? Thanks. --=20 St=C3=A9phane Epardaud |
From: Conrad W. <con...@we...> - 2006-03-05 14:38:39
|
Hi all! I'm new to this list and I've been trying to follow the guide to install the SyncML-plugin. Installing libopensync-0.18, multisync-0.90.18, libopensync-plugin-file-0.18 and libopensync-plugin-evolution2-0.18 worked well. Next I checked out libsyncml and libsoup as mentioned in the guide, but when it came to patching libsoup, I couldn't find out how to actually do it. I entered the libsoup directory and tried to apply the patch from libsyncml like this: libsoup # patch -p1 <.../libsyncml/misc/libsoup-async-dns.patch The output I became showed that the patching failed for several 'hunks': patching file ChangeLog Hunk #1 FAILED at 1. 1 out of 1 hunk FAILED -- saving rejects to file ChangeLog.rej patching file libsoup/soup-address.c Hunk #2 succeeded at 397 with fuzz 2. Hunk #3 FAILED at 409. 1 out of 3 hunks FAILED -- saving rejects to file libsoup/soup-address.c.rej patching file libsoup/soup-address.h Hunk #1 succeeded at 81 with fuzz 2 (offset 4 lines). patching file libsoup/soup-dns.c Hunk #2 FAILED at 506. Hunk #3 succeeded at 555 with fuzz 1 (offset 4 lines). Hunk #4 FAILED at 563. Hunk #5 succeeded at 574 (offset 5 lines). Hunk #6 FAILED at 584. 3 out of 6 hunks FAILED -- saving rejects to file libsoup/soup-dns.c.rej patching file libsoup/soup-dns.h Hunk #1 succeeded at 39 with fuzz 2 (offset 1 line). patching file libsoup/soup-socket.c Hunk #1 FAILED at 569. 1 out of 1 hunk FAILED -- saving rejects to file libsoup/soup-socket.c.rej patching file tests/dns.c When I thereafter try to compile libsoup, compilation fails with the following output: soup-address.c:401: error: conflicting types for `soup_address_resolve_async' soup-address.h:80: error: previous declaration of `soup_address_resolve_async' soup-address.c: In function `soup_address_resolve_async': soup-address.c:402: error: too few arguments to function `soup_address_resolve_async_full' soup-address.c: At top level: soup-address.c:419: error: conflicting types for `soup_address_resolve_async_full' soup-address.h:85: error: previous declaration of `soup_address_resolve_async_full' soup-address.c: In function `soup_address_resolve_async_full': soup-address.c:430: error: too few arguments to function `soup_dns_lookup_resolve_async' make[2]: *** [soup-address.lo] Fehler 1 make[2]: Leaving directory `/usr/local/src/svn/libsoup/libsoup' make[1]: *** [install] Fehler 2 make[1]: Leaving directory `/usr/local/src/svn/libsoup/libsoup' make: *** [install-recursive] Fehler 1 Did I do the patching wrong? Any help would be appreciated. Conrad. -- Conrad Wolf <con...@we...> |
From: Luca <gol...@li...> - 2006-03-05 13:01:07
|
> Which version of gnokii do you have? You can get this with: pkg-config > --modversion gnokii ashura@anoth ~ $ pkg-config --modversion gnokii 0.6.11 > export OSYNC_TRACE=/tmp/osync-gnokii-trace/ msynctool --addmember > evognokii gnokii-sync it does nothing :( I tried to export another path, but nothing worked too... If you wish, i have msn...we can communicate with that... or via jabber, icq and so on. My full equipment is at your disposition! See ya :) Msn is rot13. MSN: wbuanfure82vg (at) ubgznvy (dot) pbz |
From: Michael K. <Mi...@ko...> - 2006-03-05 12:16:11
|
Valgrind reveals an illegal call to free() in xml-vcard.c. The ticket system does accept my attempt to create a ticket, hangs. Enclosing patch -------------------------------------------------------------------------- Michael Kolmodin Kungsg 24, 1 tr Phone: +46 920 269413 S-972 31 Lulea Mobile +46 70 551 6507 Sweden |
From: Norm D. <no...@dr...> - 2006-03-04 22:44:23
|
Unfortunately neither Obex nor http works on my 6620. First Obex sync: It fails with error 80 or error 64. I've tried with wbxml, or without. When I do syncml-obex-client I get: Found 2 USB OBEX interfaces Interface 0: Manufacturer: Nokia Product: Nokia 6620 Interface description: SYNCML-SYNC Interface 1: Manufacturer: Nokia Product: Nokia 6620 Interface description: PC Suite Services Use '-u interface_number' to connect I've tried both 0 and 1 in the identifier and I've tried all versions of Syncml. Set with no username or password. With HTTP: The phone sits on Initializing forever. I've attached the syncml traces. This is the same as what I had previously. My kingdom for a good sync with linux --- Norm |
From: Daniel G. <dg...@su...> - 2006-03-04 14:35:14
|
On Sat, 2006-03-04 at 15:07 +0100, Luca wrote: > Hello. > Thank you for this plugin, it is exactly what I have been looking for! Thank you! for testing :) > I checked out, configured, installed it but... > > ashura@anoth .opensync $ msynctool --addmember evognokii gnokii-sync > Unable to instance plugin with name gnokii-sync: Could not find format > "gnokii-event" Which version of gnokii do you have? You can get this with: pkg-config --modversion gnokii Can you set the OSYNC_TRACE variable to get more information. Run: export OSYNC_TRACE=/tmp/osync-gnokii-trace/ msynctool --addmember evognokii gnokii-sync The logs can be found then in /tmp/osync-gnokii-trace/ |
From: mailinglists <mai...@in...> - 2006-03-04 14:25:18
|
Hi Armin! Nice to hear of this big progress. Thanks for your efforts. I just tried to install it, but it seems libsoup has been updated yesterday and the patch does not apply cleanly any more. /tobi Am Freitag, den 03.03.2006, 13:56 +0100 schrieb Armin Bauer: > Hi, > > i worked a lot on the syncml plugin and it is now ready to be tested. I > updated the syncml guide at http://www.opensync.org/wiki/syncml-guide to > show how the libraries and the syncml plugin can be installed. > > if you already checked out libsyncml from the repository you can use the > switch command to switch it to the trunk: svn switch > http://svn.opensync.org/libsyncml/trunk . > > I tested the synchronization against the file-sync plugin and evolution > 2.4. There are still some bugs i have to fix though. > > The syncml plugin supports syncml version 1.0, 1.1 and 1.2 and the > transport http and obex. The syncml guide also has a section with known > configurations which you can use. If the plugin works for your device, > please let me know so that i can add the device to the list. > > Best Regards, > Armin Bauer ++++++++++++ WERBUNG +++++++++++++++ http://www.inetsolutions.de Webhosting / Homepagebaukasten / CMS Webpacks ab 0,21 EUR ++++++++++++ WERBUNG +++++++++++++++ http://www.inetladen.de Handys / Zubehör / Multimedia Über 10000 Artikel |
From: Luca <gol...@li...> - 2006-03-04 14:08:12
|
On Mon, 27 Feb 2006 17:19:03 +0100, Daniel Gollub wrote: > Hi list! > > I have written a OpenSync plugin for Nokia cellphones based on gnokii. At > the moment it only can sync the calendar (object type: event). Support of > contacts, todo list and notes will follow soon. There are some (known) > problems with gnokii itself with writing specific details of calendar > entries. This is known and will be fixed hopefully soon. Please read the > "Known Problems/Bug" Section of the README file for more details. > > It would be great to get some feedback of your experience with > gnokii-sync. And which devices/connection types (bluetooth, IR, cable, > ...) works with gnokii-sync and which doesn't. For testing it is > recommended to use the latest version of gnokii[1]. At least version > 0.6.11 of gnokii. > > But keep in mind that the plugin is quiet experimental and you should make > a _whole_BACKUP_ of your CALENDAR, CONTACTS and TODO list! > > Feel free to ask if you have questions or problems :) You can found me > (and many others) in the IRC of #opensync on irc.freenode.org > > BTW: the plugin can be found in the subversion repository of OpenSync: snv > co http://svn.opensync.org/plugins/gnokii-sync > Hello. Thank you for this plugin, it is exactly what I have been looking for! I checked out, configured, installed it but... ashura@anoth .opensync $ msynctool --addmember evognokii gnokii-sync Unable to instance plugin with name gnokii-sync: Could not find format "gnokii-event" This is the error i get. I managed to sync evolution with file-sync, so i think this has nothing to do with my lameness :) ... anyway, we are still humans! Thanks Again. See Ya |
From: <bu...@gm...> - 2006-03-03 20:12:19
|
Dnia 03-03-2006, pią o godzinie 14:49 -0500, Norm Dressler napisał(a): > More info -- > > It looks like the problem might be linked to the version of libsoup > being found. I had similar issues compiling other programs with some non-packaged libraries involved (although configured with proper prefixes). Look for all instances of libsoup (like all .pc files, all links to libraries) - maybe there is something left from older versions? That is why - if I am not sure - I always compile external/patched libraries to some local (meaning /home) prefixes and use PKG_CONFIG_PATH or other variables. When I want to try a new version, I just delete the whole folder. I hope this helps, otherwise I have no ideas (just to make sure I compiled today's svn libsyncml and had no problems). Just an example: $ pkg-config --modversion libsoup-2.2 $ 2.2.6.1 $ PKG_CONFIG_PATH=/home/burlap/sync/alternative/lib/pkgconfig pkg-config --modversion libsoup-2.2 $ 2.2.90 Cheers, Rafał |
From: Norm D. <no...@dr...> - 2006-03-03 19:49:48
|
More info -- It looks like the problem might be linked to the version of libsoup being found. pkg-config --modversion libsoup-2.2 gives a version of 2.2.7 but the configure.ac script looks for 2.2.90 which results in no libsoup and the error below. Oddly, there was a previously installed libsoup package used by my OS (Arch Linux) but when I built libsoup from source, I gave a prefix=/usr and it was overwritten with the compiled/patched version, which I assume is version 2.2.90? PKG_CHECK_MODULES(LIBSOUP, libsoup-2.2 >= 2.2.90, HAVE_LIBSOUP=yes, HAVE_LIBSOUP=no) if test "x${HAVE_LIBSOUP}" = "xyes"; then Regardless, for whatever reason its not catching the new libsoup -- if I change the configure.ac, and do an autoreconf -sfi, I get past the first error only to get a new one. Any suggestions around my problem? Thx Norm On Fri, 2006-03-03 at 13:07 -0500, Norm Dressler wrote: > Yes, just like the web-page indicated. Although there are 2 patches in > libsyncml/misc, the web site posted by Armin says to only patch with > misc/libsoup-async-dns.patch, which I did. > > Norm > > On Fri, 2006-03-03 at 19:02 +0100, Rafał Próchniak wrote: > > Dnia 03-03-2006, pią o godzinie 12:57 -0500, Norm Dressler napisał(a): > > > All software is the latest freshly grabbed from svn or cvs. > > > > Did you patch libspoup? > > (Patch should be located in libsyncml/misc) > > > > It is necessary also for the latest cvs version of libsoup. > > > > Cheers, > > Rafał > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > > that extends applications into web and mobile media. Attend the live webcast > > and join the prime developer group breaking into this new coding territory! > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > > _______________________________________________ > > Opensync-users mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/opensync-users > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Opensync-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensync-users |
From: Norm D. <no...@dr...> - 2006-03-03 18:07:04
|
Yes, just like the web-page indicated. Although there are 2 patches in libsyncml/misc, the web site posted by Armin says to only patch with misc/libsoup-async-dns.patch, which I did. Norm On Fri, 2006-03-03 at 19:02 +0100, Rafał Próchniak wrote: > Dnia 03-03-2006, pią o godzinie 12:57 -0500, Norm Dressler napisał(a): > > All software is the latest freshly grabbed from svn or cvs. > > Did you patch libspoup? > (Patch should be located in libsyncml/misc) > > It is necessary also for the latest cvs version of libsoup. > > Cheers, > Rafał > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Opensync-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensync-users |
From: <bu...@gm...> - 2006-03-03 18:02:29
|
Dnia 03-03-2006, pią o godzinie 12:57 -0500, Norm Dressler napisał(a): > All software is the latest freshly grabbed from svn or cvs. Did you patch libspoup? (Patch should be located in libsyncml/misc) It is necessary also for the latest cvs version of libsoup. Cheers, Rafał |
From: Norm D. <no...@dr...> - 2006-03-03 17:57:31
|
All software is the latest freshly grabbed from svn or cvs. if /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I../.. -Wall -Werror -g -O2 -MT libhttp_client_la-http_client.lo -MD -MP -MF ".deps/libhttp_client_la-http_client.Tpo" -c -o libhttp_client_la-http_client.lo `test -f 'http_client.c' || echo './'`http_client.c; \ then mv -f ".deps/libhttp_client_la-http_client.Tpo" ".deps/libhttp_client_la-http_client.Plo"; else rm -f ".deps/libhttp_client_la-http_client.Tpo"; exit 1; fi gcc -DHAVE_CONFIG_H -I. -I. -I../.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I../.. -Wall -Werror -g -O2 -MT libhttp_client_la-http_client.lo -MD -MP -MF .deps/libhttp_client_la-http_client.Tpo -c http_client.c -fPIC -DPIC -o .libs/libhttp_client_la-http_client.o In file included from http_client.c:27: http_client_internals.h:24:40: error: libsoup/soup-session-async.h: No such file or directory http_client_internals.h:25:30: error: libsoup/soup-uri.h: No such file or directory In file included from http_client.c:27: http_client_internals.h:28: error: syntax error before 'SoupSession' On Fri, 2006-03-03 at 18:41 +0100, Daniel Gollub wrote: > On Fri, 2006-03-03 at 11:57 -0500, Norm Dressler wrote: > > I'm having problems compiling libsyncml. > > http_client_internals.h:24:40: error: libsoup/soup-session-async.h: No > > such file or directory > > http_client_internals.h:25:30: error: libsoup/soup-uri.h: No such file > > or direct ory > can you paste last 3 lines (the line with gcc and parameters are very > helpful :)) > > Did you installed the latest CVS snapshot (2.2.90) of libsoup? > Did you set PKG_CONFIG_PATH (before configure!) to your libsoup-cvs > build? > > To get the version and the include path of libsoup try: > pkg-config --modversion libsoup-2.2 > pkg-config --cflags libsoup-2.2 > > best regards, > Daniel > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Opensync-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensync-users |
From: Daniel G. <dg...@su...> - 2006-03-03 17:37:56
|
On Fri, 2006-03-03 at 11:57 -0500, Norm Dressler wrote: > I'm having problems compiling libsyncml. > http_client_internals.h:24:40: error: libsoup/soup-session-async.h: No > such file or directory > http_client_internals.h:25:30: error: libsoup/soup-uri.h: No such file > or direct ory can you paste last 3 lines (the line with gcc and parameters are very helpful :)) Did you installed the latest CVS snapshot (2.2.90) of libsoup? Did you set PKG_CONFIG_PATH (before configure!) to your libsoup-cvs build? To get the version and the include path of libsoup try: pkg-config --modversion libsoup-2.2 pkg-config --cflags libsoup-2.2 best regards, Daniel |