Crash on selection of UbuntuOne synchronisation preference

After the crash, the error should have been recorded in ~/.config/tomboy/tomboy.log .

If you don't see it there, simply run Tomboy from the command line (make sure it's not already running first), then reproduce the crash, and attach the output to this bug.

This is an Ubuntu-specific bug and is probably simply a missing package or some such.

Output of tomboy crash scenario added as requested

Yeah, you're missing some package that provides syncdaemon-1.0. The Canonical guys will need to update the requirements of the .deb.

No. That's not the right fix. You need to fix syncdaemon to provide the depends through shlibs. Perhaps your dllmap or shlibs file is wrong there.

p.s. I see Tomboy is again diverging from Debian.

Iain, libsyncdaemon is DllImport'ed in the Ubuntu One patch, that's why the explicit Depends.

About diverging, I talked with the Tomboy developers about having this patch upstream, but it only works on Ubuntu, because it needs ubuntu-sso-client, so that's why it's only in the Ubuntu package, if not, it would not be also on the Debian package, but in Tomboy upstream code, as the rest of the fixes/improvements we had to do for Tomboy<->U1 syncing. If Debian has ubuntu-sso-client, then it can be merged to Debian, but if not, it makes no sense to add a patch to the Debian package that won't work.

I know *why* its done, but it's not the right solution. You probably need to supply a DLLmap in the patch, or if that's alright then you need to fix syncdaemon to provide correct shlibs. In any case, adding a lib dependency like this is a big red flag.

(and I'm sorry for seeming abrupt before: I meant the new upstream release mainly)

This bug was fixed in the package tomboy - 1.3.2-1ubuntu3

---------------
tomboy (1.3.2-1ubuntu3) maverick; urgency=low

  * debian/control:
    - Add dependency on libsyncdaemon-1.0-1 for the Ubuntu One sync plugin
      (LP: #620640)
 -- Rodrigo Moya <email address hidden> Thu, 02 Sep 2010 15:57:24 +0200

It *should* be possible to split the new U1 prefs pane out into a separate add-in that depends on the websync add-in. Then it could be installed as a separate add-in package.

This might help with your divergence issues, Iain?

Hi,

On Fri, Sep 03, 2010 at 01:13:27PM -0000, Sandy Armstrong wrote:
>It *should* be possible to split the new U1 prefs pane out into a
>separate add-in that depends on the websync add-in. Then it could be
>installed as a separate add-in package.
>
>This might help with your divergence issues, Iain?

Yes, in fact when I first saw this I was surprised that it wasn't a
separate package indeed. It seems like it would be better than being a
huge patch, and more maintainable.

I was mainly complaining that Ubuntu updated to 1.3.2 without sending
this update to Debian. Ideally the updates would be done there first
and then merged back to Ubuntu

btw Sandy, have you discussed taking the appindicator patch upstream?
It should be doable with an optional dep/enable flag, I hope. :)

btw2, I'm going to reopen this bug since the fix is bad and should be
done correctly.

Iain

I wonder why this mail got lost

Hi,

On Fri, Sep 03, 2010 at 01:13:27PM -0000, Sandy Armstrong wrote:
> It *should* be possible to split the new U1 prefs pane out into a
> separate add-in that depends on the websync add-in. Then it could be
> installed as a separate add-in package.
>
> This might help with your divergence issues, Iain?

Yes, in fact when I first saw this I was surprised that it wasn't a
separate package indeed. It seems like it would be better than being a
huge patch, and more maintainable.

I was mainly complaining that Ubuntu updated to 1.3.2 without sending
this update to Debian. Ideally the updates would be done there first
and then merged back to Ubuntu

btw Sandy, have you discussed taking the appindicator patch upstream?
It should be doable with an optional dep/enable flag, I hope. :)

btw2, I'm going to reopen this bug since the fix is bad and should be
done correctly.

Iain

On Fri, Sep 3, 2010 at 12:36 PM, Iain Lane <email address hidden> wrote:
> btw Sandy, have you discussed taking the appindicator patch upstream?
> It should be doable with an optional dep/enable flag, I hope. :)

I keep meaning to review it and take it upstream, and really will one
of these days. Apologies for the burden on packagers who wish to ship
appindicator support.

Am I the only one who is experiencing this bug under lucid?

Since Ubuntu One synchronization is already enabled, Tomboy crashes immediately after the start. Thus, I cannot even see my notes anymore (only through the Ubuntu One web interface).

Is there a work-around for this problem?

Cheers,
Tobias

On Sun, Sep 5, 2010 at 1:49 AM, Tobias Kuhn <email address hidden> wrote:
> Am I the only one who is experiencing this bug under lucid?

I was under the impression Rodrigo has only included this patch in Maverick

> Since Ubuntu One synchronization is already enabled, Tomboy crashes
> immediately after the start. Thus, I cannot even see my notes anymore
> (only through the Ubuntu One web interface).

Please share the output you get when starting Tomboy from the command
line. This is probably a different bug.

My output of tomboy (using lucid) is attached. Same bug or a different one?

@Tobias: different bug and one that surprises me that we don't handle. Please report upstream.

The note file mentioned in the error is probably corrupt for some reason. Take a look at it, and if you can't salvage the contents, delete it so Tomboy won't try to load it when it starts.

The note file was corrupt. I deleted it and now Tomboy works again. I don't know how this happend. The problem appeared after a system update. Anyway, it's not related to this bug. Thanks for your help!