Tomboy.exe crashed with SIGSEGV in __kernel_vsyscall()

Bug #287241 reported by Sam Devol
26
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tomboy
Invalid
Critical
tomboy (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: tomboy

Since upgrading to 8.10 beta, I haven't been able to get tomboy to run. When starting from a shell, it crashes.

Description: Ubuntu 8.10
Release: 8.10

tomboy:
  Installed: 0.12.0-0ubuntu1
  Candidate: 0.12.0-0ubuntu1
  Version table:
 *** 0.12.0-0ubuntu1 0
        500 http://us.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/tomboy/Tomboy.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: wl nvidia
Package: tomboy 0.12.0-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: mono /usr/lib/tomboy/Tomboy.exe
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/User Name/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: tomboy
StacktraceTop:
 __kernel_vsyscall ()
 write () from /lib/tls/i686/cmov/libc.so.6
 _IO_file_write () from /lib/tls/i686/cmov/libc.so.6
 _IO_file_xsputn () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
Title: Tomboy.exe crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin cdrom dialout fuse gdm lpadmin plugdev pulse pulse-access pulse-rt sambashare saned scanner

Tags: apport-crash
Revision history for this message
Sam Devol (support-samdevol) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:__kernel_vsyscall ()
write () from /lib/tls/i686/cmov/libc.so.6
_IO_new_file_write () from /lib/tls/i686/cmov/libc.so.6
_IO_new_file_xsputn () from /lib/tls/i686/cmov/libc.so.6
buffered_vfprintf () from /lib/tls/i686/cmov/libc.so.6

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in tomboy:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

is this still an issue after latest updates? may you run tomboy from the command line as : tomboy --debug &> tomboy.txt and later on attach that file to the report? thanks in advance.

Changed in tomboy:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Sam Devol (support-samdevol) wrote :

Still an issue.

I ran tomboy --debug &> tomboy.txt and tomboy.txt quickly filled up (after a few minutes it was over 20MB). Only the first 15 lines contained unique information; The last line here was repeated throughout the whole file.
---------------begin tomboy.txt-------------------------
** Running Mono with --debug **
[DEBUG]: NoteManager created with note path "/home/sam/.tomboy".
[INFO]: Initializing Mono.Addins
Stack overflow in unmanaged: IP: 0x81138dc, fault addr: 0xbf3cdffc
Stack overflow: IP: 0xb80c2422, fault addr: 0xbf3c5ffc
At Unmanaged
Stacktrace:

  at (wrapper managed-to-native) System.IO.MonoIO.Read (intptr,byte[],int,int,System.IO.MonoIOError&) <0x00004>
  at (wrapper managed-to-native) System.IO.MonoIO.Read (intptr,byte[],int,int,System.IO.MonoIOError&) <0xffffffff>
  at System.IO.FileStream.ReadData (intptr,byte[],int,int) <0x00028>
  at System.IO.FileStream.RefillBuffer () <0x00022>
  at System.IO.FileStream.ReadByte () <0x0007a>
  at Mono.Addins.Serialization.BinaryXmlReader.ReadNext () <0x0001f>
  at Mono.Addins.Serialization.BinaryXmlReader.Skip () <0x00049>
  at Mono.Addins.Serialization.BinaryXmlReader.Skip () <0x00055>
  at Mono.Addins.Serialization.BinaryXmlReader.Skip () <0x00055>
  at Mono.Addins.Serialization.BinaryXmlReader.Skip () <0x00055>
  at Mono.Addins.Serialization.BinaryXmlReader.Skip () <0x00055>
---------------last line repeated ad infinitum--------------------------------

Hope this helps.

Revision history for this message
Sam Devol (support-samdevol) wrote :

Following a hint from another bug report:

I removed the .tomboy/addin-db-001 and tomboy seems to be behaving now.

Revision history for this message
Greg Grossmeier (greg.grossmeier) wrote :

This bug is known upstream: http://bugzilla.gnome.org/show_bug.cgi?id=556177

Did you happen to backup your ~/.tomboy/addin-db-001 before you removed it? If you did, please zip it up and attach it here.

Thanks!

Changed in tomboy:
status: Incomplete → Triaged
Revision history for this message
Sam Devol (support-samdevol) wrote :

Apologies Greg, but I did not keep a copy.

Revision history for this message
Greg Grossmeier (greg.grossmeier) wrote :

The upstream reporter did keep theirs, so not all is lost. It just would have been an additional set of information. If you want, you can watch the status of the bug upstream to see if there is anything else you can add.

Thanks again!

Changed in tomboy:
status: Unknown → New
Changed in tomboy:
status: New → Incomplete
Revision history for this message
tangerine (2wtangerine) wrote :

I had a similar problem with Tomboy. First Tomboy couldn't load as an applet, so I launched it with Alt+F2. Next, it ceased working at all, producing this output:

[DEBUG]: NoteManager created with note path "/home/#####/.tomboy".
[INFO]: Initializing Mono.Addins
Stack overflow in unmanaged: IP: 0x506c20, fault addr: 0x7fffeed8eff0
Stack overflow: IP: 0x506c20, fault addr: 0x7fffeed86ff0
At Unmanaged
Stacktrace:

  at (wrapper managed-to-native) System.IO.MonoIO.Read (intptr,byte[],int,int,System.IO.MonoIOError&) <0x00054>
  at (wrapper managed-to-native) System.IO.MonoIO.Read (intptr,byte[],int,int,System.IO.MonoIOError&) <0xffffffff>
  at System.IO.FileStream.ReadData (intptr,byte[],int,int) <0x0004f>
  at System.IO.FileStream.RefillBuffer () <0x00037>
  at System.IO.FileStream.ReadByte () <0x000e7>
  at Mono.Addins.Serialization.BinaryXmlReader.ReadNext () <0x00034>
  at Mono.Addins.Serialization.BinaryXmlReader.Skip () <0x00057>
  at Mono.Addins.Serialization.BinaryXmlReader.Skip () <0x00067>
  at Mono.Addins.Serialization.BinaryXmlReader.Skip () <0x00067>
  at Mono.Addins.Serialization.BinaryXmlReader.Skip () <0x00067>
  at Mono.Addins.Serialization.BinaryXmlReader.Skip () <0x00067>
  (last line repeated forever)

Here's my zipped addin-db-001 folder (hope it doesn't reveal any personal data).
As I removed the addin-db-001 folder, Tomboy fully recovered, and even all of my notes are there. Yet, it is not found in the applets menu, so can not be added to the Gnome panel (maybe that's because I reinstalled Tomboy a couple of times and then installed it from source in attempt to get it working).

Revision history for this message
tangerine (2wtangerine) wrote :

Forgot to mention I'm using fresh install of Ubuntu Jaunty on Intel x64 dual-core processor. One thing I can think of as triggering this bug is synchronization with notes which I saved on my previous installation of Ubuntu (Hardy). However, this did work, problems started later.

Changed in tomboy:
status: Incomplete → Confirmed
Revision history for this message
Sandy Armstrong (sanfordarmstrong) wrote :

I should mention that this bug was fixed for most users in Tomboy 0.14.2.

Changed in tomboy:
importance: Unknown → Critical
status: Confirmed → Unknown
Changed in tomboy:
status: Unknown → Invalid
Revision history for this message
Alemann Massho (armistice-con-deactivatedaccount) wrote :

bug is resolved in gnome bugzilla

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.