friends-dispatcher crashed with SIGSEGV

Bug #1237116 reported by James Tait
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
friends (Ubuntu)
New
Undecided
Unassigned

Bug Description

First run after installation, my timeline updated with my own posts, the main Friends window dimmed, and the dispatcher service crashed.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: friends-dispatcher 0.2.0+13.10.20130926-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Tue Oct 8 23:37:32 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/friends-dispatcher
InstallationDate: Installed on 2013-09-11 (26 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130910)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/friends-dispatcher -o
SegvAnalysis:
 Segfault happened at: 0x7fa30b797320: cmp %rdi,0x18(%rdx)
 PC (0x7fa30b797320) ok
 source "%rdi" ok
 destination "0x18(%rdx)" (0x0000001a) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: friends
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libdee-1.0.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libdee-1.0.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libdee-1.0.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libdee-1.0.so.4
Title: friends-dispatcher crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
James Tait (jamestait) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1233724, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.