Ubuntu
tomboy package

Tomboy.exe crashed with SIGSEGV

Bug #216108 reported by Jesse Aldridge on 2008-04-12

This bug report is a duplicate of: Bug #199496: Tomboy.exe crashed with SIGSEGV in exit(). Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	tomboy (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: tomboy

I closed the program while several notes were open and the "program is not responding" dialog came up (rather quickly). I clicked "force quit".

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Apr 11 21:04:48 2008
Disassembly: 0xb5e93778:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/tomboy/Tomboy.exe
InterpreterPath: /usr/bin/mono
Package: tomboy 0.10.0-1
PackageArchitecture: i386
ProcCmdline: mono /usr/lib/tomboy/Tomboy.exe
ProcEnviron:
SHELL=/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games:/usr/mz/bin:/home/username/Desktop/haxe-1.18-linux:/home/username/my-libs/google_appengine
LANG=C
Signal: 11
SourcePackage: tomboy
Stacktrace: #0 0xb5e93778 in ?? ()
StacktraceTop: ?? ()
Title: Tomboy.exe crashed with SIGSEGV
Uname: Linux 2.6.24-15-386 i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Tags:

Revision history for this message

Jesse Aldridge (jessealdridge) wrote on 2008-04-12:

Dependencies.txt Edit (5.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (23.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (667 bytes, text/plain; charset="utf-8")
Registers.txt Edit (457 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (101 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2008-04-12: Symbolic stack trace

Stacktrace.txt (retraced) Edit (23 bytes, text/plain)

StacktraceTop:?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2008-04-12: Symbolic threaded stack trace

ThreadStacktrace.txt (retraced) Edit (101 bytes, text/plain)

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2008-04-14:

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.