Tomboy.exe crashed with SIGSEGV

Bug #1036183 reported by Ingo Gerth on 2012-08-13
30
This bug affects 2 people
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
Undecided
Unassigned
tomboy (Ubuntu)
Undecided
Unassigned

Bug Description

Happened out of the blue. Hope this is no dupe.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: tomboy 1.11.5-1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-9.9-generic 3.5.0
Uname: Linux 3.5.0-9-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Mon Aug 13 14:22:34 2012
ExecutablePath: /usr/lib/tomboy/Tomboy.exe
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120811.1)
InterpreterPath: /usr/bin/mono
ProcCmdline: mono /usr/lib/tomboy/Tomboy.exe --search
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fc28b286790: cmp 0x18(%rdx),%rbx
 PC (0x7fc28b286790) ok
 source "0x18(%rdx)" (0x1f35e2818) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: tomboy
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: Tomboy.exe crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Ingo Gerth (igerth) wrote :

StacktraceTop:
 ?? () from /tmp/tmpzoGmaz/lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /tmp/tmpzoGmaz/lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /tmp/tmpzoGmaz/lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /tmp/tmpzoGmaz/lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /tmp/tmpzoGmaz/lib/x86_64-linux-gnu/libdbus-1.so.3

Changed in tomboy (Ubuntu):
status: New → Invalid

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libdrm-intel1 version 2.4.37-0ubuntu2 required, but 2.4.38-0ubuntu1 is available
outdated debug symbol package for initscripts: package version 2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11.1
libdrm-radeon1 version 2.4.37-0ubuntu2 required, but 2.4.38-0ubuntu1 is available
libdrm-nouveau1a version 2.4.37-0ubuntu2 required, but 2.4.38-0ubuntu1 is available
libkms1 version 2.4.37-0ubuntu2 required, but 2.4.38-0ubuntu1 is available
libdrm2 version 2.4.37-0ubuntu2 required, but 2.4.38-0ubuntu1 is available
outdated debug symbol package for module-init-tools: package version 3.16-1ubuntu3 dbgsym version 3.16-1ubuntu2

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
information type: Private → Public
Changed in dbus (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