After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 540496 - Tomboy enters infinite loop of errors on start
Tomboy enters infinite loop of errors on start
Status: RESOLVED NOTGNOME
Product: tomboy
Classification: Applications
Component: General
0.10.x
Other Linux
: Normal normal
: ---
Assigned To: Tomboy Maintainers
Tomboy Maintainers
: 556177 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-06-27 14:34 UTC by Pedro Villavicencio
Modified: 2009-10-04 00:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Pedro Villavicencio 2008-06-27 14:34:59 UTC
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/tomboy/+bug/243387

"This is what I get when I try to start tomboy:

[DEBUG]: NoteManager created with note path "/home/drink/.tomboy".
[INFO]: Initializing Mono.Addins
Stack overflow in unmanaged: IP: 0xb7fbc402, fault addr: 0xbf69effc
Stack overflow: IP: 0x81080b6, fault addr: 0xbf696ff8
At Unmanaged
Stacktrace:

  at (wrapper managed-to-native) System.IO.MonoIO.Read (intptr,byte[],int,int,System.IO.MonoIOError&) <0x00004>
  at (wrapper managed-to-native) System.IO.MonoIO.Read (intptr,byte[],int,int,System.IO.MonoIOError&) <0xffffffff>
  at System.IO.FileStream.ReadData (intptr,byte[],int,int) <0x00028>
  at System.IO.FileStream.RefillBuffer () <0x00022>
  at System.IO.FileStream.ReadByte () <0x0007a>
  at Mono.Addins.Serialization.BinaryXmlReader.ReadNext () <0x0001f>
  at Mono.Addins.Serialization.BinaryXmlReader.Skip () <0x00049>
  at Mono.Addins.Serialization.BinaryXmlReader.Skip () <0x00055>
  at Mono.Addins.Serialization.BinaryXmlReader.Skip () <0x00055>

Repeat ad infinitum. On ^C there is a segmentation fault.

Ubuntu 8.04.1
tomboy 0.10.2-0ubuntu1"

"if I delete my .tomboy/addins-db-001 the problem goes away.
attached is my bad .tomboy "

http://launchpadlibrarian.net/15637187/badtomboy.tgz

thanks,
Comment 1 Sandy Armstrong 2008-06-27 14:47:18 UTC
Thanks for providing the bad .tomboy.  Clearly the addin db got corrupted somehow.  Will look into it.
Comment 2 ildella 2009-05-01 15:23:05 UTC
it also happened to me a few days ago on ubuntu 9.04 and tomboy 0.14. 
removin .tomboy/addins-db-00* make it back to work. 
Comment 3 Sandy Armstrong 2009-05-01 15:57:45 UTC
(In reply to comment #2)
> it also happened to me a few days ago on ubuntu 9.04 and tomboy 0.14. 
> removin .tomboy/addins-db-00* make it back to work. 

Hmm, this means it's still a problem with Mono.Addins 0.4.  :-/  ildella, are you sure it was the same error message?
Comment 4 Emre Ayca 2009-06-06 15:16:56 UTC
I can confirm the same infinite loop error happened with ubuntu 9.04.

Removing the .tomboy/addins-db-01 worked for me as well.
Comment 5 Paul Cutler 2009-06-13 14:31:38 UTC
I can confirm this bug, using Tomboy 0.14.1 on Foresight.  I upgraded to the nightly build of Tomboy in the GNOME DevKit.  Removing .tomboy/addins-db-01 fixed it as well.
Comment 6 Sandy Armstrong 2009-08-23 00:29:37 UTC
I've looked into this, and I don't think there's anything we can do from the Tomboy side.  Thanks a lot for providing the bad .tomboy for testing.  Closing the bug.
Comment 7 Runar Ingebrigtsen 2009-09-10 07:54:35 UTC
I don't see how you can state there's nothing you can do. Obviously this is a problem with the way Tomboy handles addons, since deleting the addin configuration and database solves this issue. Then you even get to keep your notes.

Here's what I do when this happens:
$ rm -rf .tomboy/addin*

I would recommend replacing the addin configuration with a different system, to avoid this issue.
Comment 8 Sandy Armstrong 2009-09-10 13:32:33 UTC
(In reply to comment #7)
> I don't see how you can state there's nothing you can do. Obviously this is a
> problem with the way Tomboy handles addons, since deleting the addin
> configuration and database solves this issue. Then you even get to keep your
> notes.

What I'm saying is that I don't think there's anything we can do in Tomboy code.  The bug needs to be fixed in Mono.Addins code.

> Here's what I do when this happens:
> $ rm -rf .tomboy/addin*

Since 0.15.6, this is stored in ~/.config/tomboy/addin*, btw.  Notes are in ~/.local/share/tomboy/.  See http://live.gnome.org/Tomboy/Directories

> I would recommend replacing the addin configuration with a different system, to
> avoid this issue.

That's not going to happen.  I do not have the time to maintain a custom add-in system; that's why we switched to Mono.Addins.  Instead, the correct thing to do is to fix the bug in Mono.Addins itself, so that other apps the use it can benefit from the fix (Banshee, F-Spot, GNOME Do...).

If the Mono.Addins guys tell me that I'm doing something wrong in Tomboy, then of course I'll reopen this bug.
Comment 9 Sandy Armstrong 2009-09-10 13:37:30 UTC
Oh, one last thing...I believe this is "fixed" for most users since Tomboy 0.14.2.  See this item from the release notes:

* Improve startup time by only rebuilding add-in registry when passing --debug.

After releasing, we realized that this change also seemed to get rid of the bug reported here.  Of course, running with --debug could potentially cause it to reoccur.

Have you tried Tomboy 0.14.2 or later?
Comment 10 Sandy Armstrong 2009-09-10 13:43:07 UTC
And by the way, here's the Mono.Addins bug:

https://bugzilla.novell.com/show_bug.cgi?id=513612
Comment 11 Sandy Armstrong 2009-09-10 13:48:05 UTC
*** Bug 556177 has been marked as a duplicate of this bug. ***