It's extrange but when I start tomboy in debug mode work fine, but when I
kill it, it's pull over the CPU to maximum.
I attach the log file.
2010/5/4 Sandy Armstrong <email address hidden>
> Try starting Tomboy with --debug, but redirect output to a file. So,
> from a terminal, run `tomboy --debug &> out.txt` .
>
> Then, when Tomboy starts hanging, from another terminal run `kill -s
> QUIT $(pidof tomboy)` . That will trigger Tomboy to dump even more
> output (but it won't actually kill Tomboy). Attach the out.txt file
> you've created to this bug and we'll see if we can get some info out of
> it.
>
> --
> tomboy just stop to work anymore
> https://bugs.launchpad.net/bugs/574931
> You received this bug notification because you are a direct subscriber
> of the bug.
>
Sandy,
It's extrange but when I start tomboy in debug mode work fine, but when I
kill it, it's pull over the CPU to maximum.
I attach the log file.
2010/5/4 Sandy Armstrong <email address hidden>
> Try starting Tomboy with --debug, but redirect output to a file. So, /bugs.launchpad .net/bugs/ 574931
> from a terminal, run `tomboy --debug &> out.txt` .
>
> Then, when Tomboy starts hanging, from another terminal run `kill -s
> QUIT $(pidof tomboy)` . That will trigger Tomboy to dump even more
> output (but it won't actually kill Tomboy). Attach the out.txt file
> you've created to this bug and we'll see if we can get some info out of
> it.
>
> --
> tomboy just stop to work anymore
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>