maemo.org - Talk - HOWTO: Syncevolution with N900

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - HOWTO: Syncevolution with N900 (https://talk.maemo.org/showthread.php?t=40278)

Re: HOWTO: Syncevolution with N900

Thank you for your reply.

Quote:

Originally Posted by mason (Post 544337)

this looks strange, are you sure you don't have a space issue?

My file system disk space usage looks as follows:

Code:

Nokia-N900-51-1:~/.cache/syncevolution$ df

Filesystem           1k-blocks      Used Available Use% Mounted on

rootfs                  233344    171608     57456  75% /

ubi0:rootfs             233344    171608     57456  75% /

tmpfs                     1024        68       956   7% /tmp

tmpfs                      256        80       176  31% /var/run

none                     10240        80     10160   1% /dev

tmpfs                    65536         4     65532   0% /dev/shm

/dev/mmcblk0p2         2064208    789048   1170304  40% /home

/opt/pymaemo/usr/lib/python2.5

                       2064208    789048   1170304  40% /usr/lib/python2.5

/opt/pymaemo/usr/share/pyshared

                       2064208    789048   1170304  40% /usr/share/pyshared

/opt/pymaemo/usr/lib/pyshared

                       2064208    789048   1170304  40% /usr/lib/pyshared

/opt/pymaemo/usr/share/python-support

                       2064208    789048   1170304  40% /usr/share/python-support

/opt/pymaemo/usr/lib/python-support

                       2064208    789048   1170304  40% /usr/lib/python-support

/dev/mmcblk0p1        28312128    736832  27575296   3% /home/user/MyDocs

/dev/mmcblk1p1          248960    105056    143904  42% /media/mmc1

Syncevolution uses 667MB of memory of cache! I wonder if this is the intended behaviour of syncevolution?

Code:

Nokia-N900-51-1:~/.cache/syncevolution$ du -hs

666.6M        .

Re: HOWTO: Syncevolution with N900

Joschum: Check this out, maybe?

Re: HOWTO: Syncevolution with N900

i'm not getting the new syncevolution gui to work. while the command line version works as before, the gui always says that the synchronization is already in progress (and therefore doesn't do anything).

any idea why this could be? any lock file or something of that kind?

Re: HOWTO: Syncevolution with N900

strange indeed, my cache folder is just around 200-300kb.

what takes up all the space?

Re: HOWTO: Syncevolution with N900

the cache seems to keep the last 10 syncs. on mine each is about 5mb. I assume the size of each will depend on the volume of data synced

Re: HOWTO: Syncevolution with N900

As I said here, it makes a backup of all contacts, each in its own file. And it makes two backups each time, one before sync, one after. The files are small, but if you've got many contacts, it will be a lot of ffiles.

Re: HOWTO: Syncevolution with N900

I'm trying to get my N900 syncing with Funambol and the Zimbra Connector.

I can sync my contacts successfully, but my calendar fails to sync events. Actually, it reports a successful sync, but syncs zero items.

Code:

[2010-02-25 10:03:05,768] [funambol.zimbra.internal.CalendarUtils] [WARN] [9EAC8076CFA1963D8A45CEFA49901A82] [my-n900] [myuser] [event] Cann't moving calendar event

[2010-02-25 10:03:05,785] [funambol.zimbra.internal.CalendarUtils] [WARN] [9EAC8076CFA1963D8A45CEFA49901A82] [my-n900] [myuser] [event] Cann't moving calendar event

[2010-02-25 10:03:05,828] [funambol.zimbra.internal.CalendarUtils] [WARN] [9EAC8076CFA1963D8A45CEFA49901A82] [my-n900] [myuser] [event] Cann't moving calendar event

[2010-02-25 10:03:05,847] [funambol.zimbra.internal.CalendarUtils] [WARN] [9EAC8076CFA1963D8A45CEFA49901A82] [my-n900] [myuser] [event] Cann't moving calendar event

[2010-02-25 10:03:06,415] [funambol.transport.http] [INFO] [9EAC8076CFA1963D8A45CEFA49901A82] [my-n900] [myuser] [] Request processed.

[2010-02-25 10:03:07,741] [funambol.transport.http] [INFO] [9EAC8076CFA1963D8A45CEFA49901A82] [my-n900] [myuser] [] Handling incoming request

[2010-02-25 10:03:07,741] [funambol.transport.http] [INFO] [9EAC8076CFA1963D8A45CEFA49901A82] [my-n900] [myuser] [] Request URL: https://mail.example.com:8443/funambol/ds

[2010-02-25 10:03:07,741] [funambol.transport.http] [INFO] [9EAC8076CFA1963D8A45CEFA49901A82] [my-n900] [myuser] [] Requested sessionId: 9EAC8076CFA1963D8A45CEFA49901A82

[2010-02-25 10:03:08,313] [funambol.handler] [INFO] [9EAC8076CFA1963D8A45CEFA49901A82] [my-n900] [myuser] [] Handling mapping ...

[2010-02-25 10:03:08,314] [funambol.handler] [INFO] [9EAC8076CFA1963D8A45CEFA49901A82] [my-n900] [myuser] [] Performing mapping ...

[2010-02-25 10:03:08,314] [funambol.zimbra] [INFO] [9EAC8076CFA1963D8A45CEFA49901A82] [my-n900] [myuser] [event] Status:'UNSUPPORTED MEDIA TYPE' for a 'Add' for this items: 

[2010-02-25 10:03:08,314] [funambol.zimbra] [INFO] [9EAC8076CFA1963D8A45CEFA49901A82] [my-n900] [myuser] [event] Status:'UNSUPPORTED MEDIA TYPE' for a 'Add' for this items: 

[2010-02-25 10:03:08,314] [funambol.zimbra] [INFO] [9EAC8076CFA1963D8A45CEFA49901A82] [my-n900] [myuser] [event] Status:'UNSUPPORTED MEDIA TYPE' for a 'Add' for this items:

Any ideas?

Re: HOWTO: Syncevolution with N900

Quote:

Originally Posted by Palleman (Post 533330)

Also, running Syncevolution with my settings creates backups before and after each sync, containing one vcard file for each contact. Doing that with a large contact list will eat up your space after a bunch of syncs...

1.0 beta 2 shares the file content between different backups. For large items, that means you will need roughly the space for one full dump, not 20x that much as it is now.

Not sure why "df" gave you misleading information, though.

Re: HOWTO: Syncevolution with N900

Quote:

Originally Posted by p.ohly (Post 549939)

I think df gave me the correct info. I don't think I used up the available disk space, I think I used up the available number of files. I've run into that problem on FreeBSD a couple of times (the maxfiles kernel setting), so maybe it's the same kind of limit in Linux?

Re: HOWTO: Syncevolution with N900

Quote:

Originally Posted by benny1967 (Post 544600)

Yes it's a lock file, you can delete it in ~/.config/syncevolution/<your server>/.sync_lock

However, I get a bug with all extra IM properties in vcard as X-MSN/JABBER... They are removed in funambol and then when I synchronise from somewhere else I don't get those informations. Worst, If I modify a contact with one of this field, I will get a new contact in Funambol since It does not care of extra vcard field. Have someone the same issue ?