GNOME Bugzilla – Bug 382190
NoteOfTheDay plugin creates one additional note each minute
Last modified: 2008-02-26 20:46:34 UTC
Hi, tomboy 0.5.1 on mono 1.2.1 creates one new note each minute if the NoteOfTheDay plugin is enabled. This easily results in many 100 useless notes and makes tomboy nearly unusable. Ubuntu Bug: https://launchpad.net/distros/ubuntu/+source/tomboy/+bug/74181 Bye
Does this happen only when using de_DE as the language or is it happening in en_US as well? I'm wondering if this is a similar problem to Bug #375072.
Seems to be caused by the locale... it seems tomboy is comparing the title of the note which contains the time for de_DE and if no note for the current "time" exists already a new one is created... i.e. one each minute for locales with time in the format, one each day for others. Wouldn't it be better to have some kind of created-timestamp in the notes or something instead of relying on translations?
Is there any progress on this?
I haven't spent the time to look into this yet. Has anyone else?
Created attachment 80085 [details] [review] Patch to fix the problem by looking at the date AND title I just committed this to SVN. Please test this out and let us know if it resolves the problem for you.
Works fine it seems... good work, thanks :)
Thanks for checking so quickly!
I don't get a new note on the next day after applying this patch :/
Did you leave Tomboy running or have you restarted Tomboy since?
I left it running
Hmm. I just tried to duplicate this on one of my machines running in a VM using latest SVN. I set the time to 23:58 and let the time roll over. After a minute or so, it had created a new note for the new day. I started Tomboy like this: LANG=de_DE tomboy I tried rollover both when editing the current NotD and when leaving the current NotD alone (so it'd delete the old NotD automatically). Double-check that you're using the latest SVN (I'm sure you are). Otherwise, we need to instrument the code in the NotD plugin to give us more clues as to what's happening specifically on your machine.
We've tried to reproduce this with the latest patch and have been unsuccessful. Everything appears to be working correctly. Please re-open it with additional details if hit the problem again in 0.5.4.
Hmm works fine now for some reason... so let's leave this closed ;)