maemo.org - Talk - [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar

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

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

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar

Mine often does too - for me I think it may be when it cannot connect properly as it always seems to work on wifi.

John

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar

Quote:

Originally Posted by fw190 (Post 656750)

The app always crushes for me when I try to sync with google.

Yeah mine crashes when I try to sync too. Haven't had a successful sync yet. Looking forward to getting it working though.

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar

I think it happens when the connection is too slow/weak.

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar

There's for sure a bug when there's no internet connection at all. Now for the case of slow connections I wouldn't know...it's a use-case not really easy to test out....

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar

Quote:

Originally Posted by DaSilva (Post 656871)

I think it happens when the connection is too slow/weak.

I try to sync on 3.5G so I don't think it is slow...

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar

Quote:

Originally Posted by kirano (Post 586789)

Code:

Traceback (most recent call last):

  File "/usr/bin/erminig", line 146, sync_all_profiles(widget=<gtk.ToolButton object at 0x41c67da0 (GtkToolButton at 0x4a41b8)>, data=<hildon.StackableWindow object at 0x41c67b20 (HildonStackableWindow at 0x429060)>)

        id = i[0]

        do_profile_sync(id, data)

  variables: {'data': ('local', <hildon.StackableWindow object at 0x41c67b20 (HildonStackableWindow at 0x429060)>), 'id': ('local', 1), 'do_profile_sync': ('global', <function do_profile_sync at 0x41c6bcf0>)}

  File "/usr/bin/erminig", line 118, do_profile_sync(id=1, data=<hildon.StackableWindow object at 0x41c67b20 (HildonStackableWindow at 0x429060)>)

            profile['remoteSource'], \

            profile['lastUpdate'], progress)

  variables: {'profile': ('local', {'lastUpdate': 0, 'direction': 0, 'lastLocalUpdate': 0, 'remoteSourceTitle': None, 'remoteAccountId': 1, 'enabled': 1, 'localSource': u'1', 'remoteSource': u'0', 'localSourceTitle': u'N900', 'id': 1}), 'progress': ('local', <gtk.ProgressBar object at 0x41cb0238 (GtkProgressBar at 0x4b5b30)>)}

  File "/usr/share/erminig/erminig_core.py", line 370, syncFromGoogle(pid=1, localSource=u'1', remoteSource=u'0', lastSync=0, progress=<gtk.ProgressBar object at 0x41cb0238 (GtkProgressBar at 0x4b5b30)>)

      getNewEventsFromGoogle(pid, int(localSource), remoteSource, lastSync, \

          progress)

  variables: {'progress': ('local', <gtk.ProgressBar object at 0x41cb0238 (GtkProgressBar at 0x4b5b30)>)}

  File "/usr/share/erminig/erminig_core.py", line 150, getNewEventsFromGoogle(pid=1, localSource=1, remoteSource=u'0', lastSync=0, progress=<gtk.ProgressBar object at 0x41cb0238 (GtkProgressBar at 0x4b5b30)>)

      feed_size = len(feed.entry)

      if feed_size == 0:

  variables: {'feed': ('local', None), 'feed_size': (None, None), 'len': ('builtin', <built-in function len>)}

AttributeError: 'NoneType' object has no attribute 'entry'

I get this error, I'm using 0.2.1, latest in extras. I get this crash report when I try tu update. I've never gotten it to work.

I'm using the N900 database and my googe account.

I get this error with my wifi connection, gpodder, and other software works just fine with the same connection.

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar

This is a known bug, which I had hoped to have removed in 0.2.1, but apparently I missed a few spots where it could occur. This is also one of the most frequent error reported, unfortunately.

I'm fairly certain that I will be able to release a new version of Erminig by Sunday evening (thanks to the awful weather :) ....), with fixes for this bug and a few other enhancements (recurring events? :))

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar

Quote:

Originally Posted by lorelei (Post 658276)

Hmmm, I think I'll start waiting for that release instead of the hopeless PR1.2 :)

And as a comment - have you ever considered implementing an auto-connect/disconnect feature? This most probably will greatly reduce the "not-connected" related bugs, and most importantly will save our batteries a lot! :D

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar

Quote:

Originally Posted by lorelei (Post 560654)

The very first release of Erminig-NG with its GUI is now on its way in the extras-devel repository. It should be available in a few moments. (force a refresh of the packages list in the application manager if it doesn't show up)

I have installed erminig 0.2.1 from extras-devel, and I assume that is the current version. I expected to find erminig-ng, but that is apparently no longer the name of this software, right?

I have the same problem as kirano in post #280.

I have submitted this problem in bugzilla as bug #10176.

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar

Quote:

Originally Posted by pmd (Post 658403)

I have installed erminig 0.2.1 from extras-devel, and I assume that is the current version. I expected to find erminig-ng, but that is apparently no longer the name of this software, right?

Here's the situation:

Erminig -> for Diablo
Erminig-NG -> for Freemantle/Maemo 5, but known as Erminig in the application manager. This is also the only version still supported, as Erminig (the original) will be replaced by Erminig-NG in the future.

I'm aware that it's really misleading...all my apologies...

Quote:

Originally Posted by pmd (Post 658403)

I have submitted this problem in bugzilla as bug #10176.

Excellent, thank you!

Edit: bug fixed in upcoming version 0.2.9.