Tomboy.exe crashed with SIGSEGV

[Dmitriy Geels]

Binary package hint: tomboy

It crashed after system boot, when gnome-panel loaded it's applets.

ProblemType: Crash
Architecture: i386
Date: Thu Jan 3 21:04:53 2008
Disassembly: 0xb5dd70c0:
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/tomboy/Tomboy.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: nvidia
Package: tomboy 0.8.1-0ubuntu1
PackageArchitecture: i386
ProcCmdline: mono /usr/lib/tomboy/Tomboy.exe --panel-applet --oaf-activate-iid=OAFIID:TomboyApplet_Factory --oaf-ior-fd=25
ProcCwd: /
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: tomboy
Stacktrace: #0 0xb5dd70c0 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: Tomboy.exe crashed with SIGSEGV
Uname: Linux dmig-desktop 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

[Winael (vinzjobard)]

I 'd closed Tomboy from de systray and it crashed

[Jens Askengren (jens-askengren)]

The problem occurs in somewhere in libgobject-2.0 (I have no usable stacktrace). It's triggered by the libc exit() function.

The crash only happens when you close Tomboy using the systray icon, not when you quit using the menu.

What packages should i get ddebs for? mono? libgobject?

[Engcheng (engcheng-sg)]

I was punching in a few lines without error until the following occurs:

i typed "/etc/systems" and it turned into a blue hyperlink. When I clicked on the link, CPU utilization shot up to 50 odd percent. After about 2minutes, the application close, and a bug report was generated.

Hope this helps

[Pedro Villavicencio (pedro)]

that's known then, and a dup of bug 199496