tomboy just stop to work anymore

Bug #574931 reported by Anibal on 2010-05-04
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tomboy (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: tomboy

I was working with tomboy and just hang. I stop the process and when I try to started again, just pull the CPU to the top, 100%. I rebooted a few times and problem continues. I saw in the log, but theres nothing there. I really don't know what happened with this program.

Best regards,

Aníbal.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: tomboy 1.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue May 4 01:17:07 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcEnviron:
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
SourcePackage: tomboy

Anibal (elkan9) wrote :

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.

  • out.txt Edit (10.5 KiB, text/plain; charset=UTF-8; name="out.txt")

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,
> 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.
>

Unfortunately the log is not useful if the kill command isn't run when Tomboy is hanging.

One thing that running with --debug does is that it rebuilds the add-in database, which occasionally fixes problems. So you may want to wait and see if the problem returns.

Anibal (elkan9) wrote :

Yes, I prefer wait if the problem returns. I've work with another issue and
later I try to reproduce the hang. Another thing, the hang occurs when
unsetup some "topos" (spanish) in one note, and I was working with 4 or 5
notes at the same time. But I thing the problem occurs with the database,
like you said.

2010/5/4 Sandy Armstrong <email address hidden>

> Unfortunately the log is not useful if the kill command isn't run when
> Tomboy is hanging.
>
> One thing that running with --debug does is that it rebuilds the add-in
> database, which occasionally fixes problems. So you may want to wait
> and see if the problem returns.
>
> --
> 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.
>

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in tomboy (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers