Tomboy Notes (shuts down & doesn't sync)

Asked by Ron on 2011-12-26

Dear all,

For some reason, my Tomboy Notes quits within a couple of minutes of opening. I don't know how to fix this. Why does it shut down without me doing anything?

Another issue I have with it is that I can no longer sync my notes. As soon as I try to sync them, the entire Tomboy Notes software gets shut down. I don't know what is wrong with this otherwise excellent software.

Any tips would be greatly appreciated.

Ron

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu tomboy Edit question
Assignee:
No assignee Edit question
Last query:
2011-12-27
Last reply:
2011-12-27
Nathan Heafner (nathan1465-5) said : #1

please open terminal by pressing CTRL+ALT+T and run the following command

uname -a && free -m && lsb_release -a

please paste the results here. Then in terminal run tomboy and when it crashes you should receive some information from terminal. Please post that here also.

Ron (ronald17b95) said : #2

Here's the output for the command cited above:

Linux ranin-Satellite-C655 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
             total used free shared buffers cached
Mem: 3762 2590 1172 0 100 962
-/+ buffers/cache: 1527 2234
Swap: 9138 0 9138
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 11.10
Release: 11.10
Codename: oneiric

Ron (ronald17b95) said : #3

Here's the info provided in my terminal when I try to sync Tomboy Notes. Again it crashes or shuts down:

ranin@ranin-Satellite-C655:~$ tomboy notes
[INFO 09:33:34.997] Initializing Mono.Addins
Stacktrace:

Native stacktrace:

Segmentation fault
ranin@ranin-Satellite-C655:~$

Ron (ronald17b95) said : #4

And here's the output when Tomboy Notes crashes without any actions on my part:

ranin@ranin-Satellite-C655:~$ tomboy notes
[INFO 09:39:39.031] Initializing Mono.Addins
Stacktrace:

Native stacktrace:

Segmentation fault
ranin@ranin-Satellite-C655:~$

mycae (mycae) said : #5

A segfault indicates a problem in mono itself, or one of its plugins. You would have to install the debugging symbols and then use GDB to be able to provide a useful source for the crash.

More pragmatically:
I take it you have tried using gnote instead? It is supposed to be able to pull in tomboy databases, and its completely mono-independent, and thus should not be affected by this particular bug. I've not used either of these applications much myself, however.

Ron (ronald17b95) said : #6

Thanks for your message. I have not understood what I should do exactly. Although I understand your general point, I am not sure how I can install the debugging symbols and then use GDB!

mycae (mycae) said : #7

I wasn't really suggesting to do that... I was illustrating that it is probably in the "too hard basket", sorry -- I should have been more clear.

The backtrace might potentially be useful in giving a hint where things have gone wrong, but more probably would only be useful to the mono developers -- I can't recommend it.

For curiosity's sake (really, I cannot recommend this at all):
https://wiki.ubuntu.com/DebuggingProgramCrash

delance (olivier-delance) said : #8

Please convert question into a bug.

Can you help with this problem?

Provide an answer of your own, or ask Ron for more information if necessary.

To post a message you must log in.