Tomboy.exe crashed with SIGSEGV in dbus_message_unref()

Bug #1033353 reported by siucdude
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tomboy (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

just got this after todays updates

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: tomboy 1.11.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-7.7-generic 3.5.0
Uname: Linux 3.5.0-7-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
CheckboxSubmission: 436b39225e95524b1259e913c38499a0
CheckboxSystem: 3e53d3ea5811723345f19eff5070f9ab
Date: Sun Aug 5 11:23:28 2012
ExecutablePath: /usr/lib/tomboy/Tomboy.exe
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
InterpreterPath: /usr/bin/mono
ProcCmdline: mono /usr/lib/tomboy/Tomboy.exe
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f7369b9f71b <_IO_vfprintf_internal+155>: callq 0x7f7369bea790 <strchrnul>
 PC (0x7f7369b9f71b) ok
 source "0x7f7369bea790" (0x7f7369bea790) ok
 destination "(%rsp)" (0x7f7359c1af70) not located in a known VMA region (needed writable region)!
SegvReason: writing 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
 dbus_message_unref () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 gconf_engine_get_fuller () from /usr/lib/x86_64-linux-gnu/libgconf-2.so.4
 gconf_engine_get_entry () from /usr/lib/x86_64-linux-gnu/libgconf-2.so.4
Title: Tomboy.exe crashed with SIGSEGV in dbus_message_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
siucdude (siucdude) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /tmp/tmpxLBB47/lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /tmp/tmpxLBB47/lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_message_unref () from /tmp/tmpxLBB47/lib/x86_64-linux-gnu/libdbus-1.so.3
 gconf_engine_get_fuller (conf=<optimized out>, key=0x7f73380032c0 "/apps/tomboy/sync/tomboyweb/oauth_access_token_base_url", locale=0x153ff00 "en_US.UTF-8", use_schema_default=1, is_default_p=0x7f734506258c, is_writable_p=0x7f7345062588, schema_name_p=0x7f7345062580, err=0x7f7345062578) at gconf-dbus.c:1235
 gconf_engine_get_entry (conf=0x1c62c50, key=0x7f73380032c0 "/apps/tomboy/sync/tomboyweb/oauth_access_token_base_url", locale=0x153ff00 "en_US.UTF-8", use_schema_default=1, err=0x7f7345062608) at gconf-dbus.c:1296

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in tomboy (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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