GNOME Bugzilla – Bug 681542
Tomboy.exe will not continue running
Last modified: 2016-08-31 19:36:25 UTC
Created attachment 220813 [details] Cmd line, Task Mgr, Program List I've got Tomboy running on 2 XP systems and 1 Win7 system but this Win7Prof32Bit has me stumped. I cannot get it to function at all. I start the program the Icon appears but when I mouse to it it disappears. I've attached a screenshot which I hope is view able. If you can teach me a better way to capture a dual screen as .tif or jpg I'm willing to learn. Back to the problem, I've copied the command line running, task manager etc. Thanks in advance for your assistance.
I've seen this problem before. If I build you a new build that may fix this, would you be willing to try?
Certainly! Any help would be appreciated. Thank you.
(In reply to comment #1) > I've seen this problem before. > If I build you a new build that may fix this, would you be willing to try? Certainly! Any help would be appreciated. Thank you.
Bill, Sorry about the delay. Here you can download a custom build I made. There's no install, just extract the ZIP and run Tomboy.exe from the Debug folder. http://dl.dropbox.com/u/11996020/tomboy-debug-1.11.6.zip md5sum:ae946aef1bbe3d719e7f3acad5cc21ce If you have problems, please post the tomboy.log.
Thank you!!! Works under the following condition: I downloaded zip, to a flash drive, and extracted to the same flash drive and then ran tomboy.exe from this flash drive. What next? Obviously I don't want to be limited to the flash drive. Should I copy the extract, over to my hard drive etc etc?? Thank you in advance for all your assistance on this matter.
Bill, Here's a build that you can use. https://dl.dropbox.com/u/11996020/Tomboy-dev-1.11.7.msi It should upgrade your existing Tomboy build. If this works for you, then the changes will get merged with the main Tomboy code line.
My apologies for the delay as I went on vacation & tried to forget about tech for a few days. I've been running your build no for a few days and I'm happy to report that your build fixed the problem I was having. Thank you for your assistance. Bill (In reply to comment #6) > Bill, > Here's a build that you can use. > https://dl.dropbox.com/u/11996020/Tomboy-dev-1.11.7.msi > > It should upgrade your existing Tomboy build. > If this works for you, then the changes will get merged with the main Tomboy > code line.
Thanks Bill!
Created attachment 223452 [details] [review] Hopefully adding the try / catch block will fix an exception when the Addin Manager cannot read the Addin description. The patch has been testing and is running, but could someone review it?
Adding discussion from #tomboy > (2012-09-04 10:46:41) adborden_: jared_: If the exception is thrown, do the > add-ins get initialized properly? because we wouldn't want tomboy to run if > the add > (2012-09-04 10:46:49) adborden_: *if the add-ins aren't completely loaded > (2012-09-04 10:46:58) adborden_: Notebooks and Sync are implemented as addins > (2012-09-04 12:07:28) jared_: adborden_ well it has to do if a bad add-in > exists or outdated. > (2012-09-04 12:07:45) jared_: It stops the whole process. Stopping Tomboy > from loading completely doesn't seem like a good thing. > (2012-09-04 12:07:53) jared_: Other add-ins will load, just the bad add-in > doesn't. > (2012-09-04 12:08:22) jared_: I see your point, but I think Tomboy should > still load unless (1) the add-in is "critical" or (2) we put a warning > message that some failed to load. > (2012-09-04 14:13:05) adborden_: jared_: the other question i have is that if > the add-in doesn't load, what happens to make it load in the future? does it > need to be recompiled? does a registry need to be rebuilt or something? what > causes the add-ins to fail to load > (2012-09-04 20:05:37) jared_: adborden_ yah, no clue at this point. Would like to dig into this a bit deeper.
Bill, Would you mind running Tomboy with --debug now that Tomboy is running. I would like to see the tomboy.log after you start in debug and see if I can determine why this is happening. Actually, get a copy of tomboy.log as you normally start it and then a copy with --debug. Thanks. (In reply to comment #7) > My apologies for the delay as I went on vacation & tried to forget about tech > for a few days. I've been running your build no for a few days and I'm happy > to report that your build fixed the problem I was having. Thank you for your > assistance. Bill > > (In reply to comment #6) > > Bill, > > Here's a build that you can use. > > https://dl.dropbox.com/u/11996020/Tomboy-dev-1.11.7.msi > > > > It should upgrade your existing Tomboy build. > > If this works for you, then the changes will get merged with the main Tomboy > > code line.
Jared, I spoke to soon. My initial problem is fixed but I neglected to fully test/verify the SYNC. I just thought I was syncing. I can't adjust the sync folder to my dropbox account. It's greyed out inside of Tomboy. Can you be of any further assistance? Thanks, Bill
Could you post a screen-shot of this?
Created attachment 223581 [details] Greyed Out Sync Options Per your request.
Unless I'm missing something simple here, this is working expected. Once the sync option has been set you cannot change it unless you select "clear". Then you will be able to set a new sync option, like Ubuntu Web or such.
Created attachment 223583 [details] Ran from CMD Line
CLEAR, Well me Ostrich certainly had it's head buried. Thanks for all your help.
committed #87df3294211282b2866685a116f88be6e572873d I wasn't expecting the fix to make it into master, but it has. This needs a few more changes though. We need a patch so that the user knows there is a problem with the add-in.
Hello. I just saw the commit in tomboy to workaround this problem. I would actually recommend a different approach: just bundle/require the version 0.6.2 of Mono.Addins, where this bug was fixed: https://github.com/mono/mono-addins/commit/2bf0f4b5c56c56473e0a055f0f987309f3dd366a
Completely valid call. I had forgotten you had mentioned this. I will see how to undo the commit I made.
change reverted We still need to check on the version requirements for Mono Addins.
*** Bug 664047 has been marked as a duplicate of this bug. ***
I think since 2012 Mono Addins greater than 0.6.2 (which fixes the original problem) has become default in any imaginable distribution, so I think we can safely close this one as resolved. Any objections, Jared, Aaron?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!