friends-dispatcher crashed with SIGSEGV

Bug #1233724 reported by Vague Entertainment
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
dee
Confirmed
Undecided
Michal Hruby
friends (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I was doing system testing, going from X to Mir and back again, this error (having nothing to do with my testing) may have been caused by that.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: friends-dispatcher 0.2.0+13.10.20130926-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Tue Oct 1 10:25:28 2013
ExecutablePath: /usr/bin/friends-dispatcher
InstallationDate: Installed on 2013-08-22 (39 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130822)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/friends-dispatcher -o
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f921698c320: cmp %rdi,0x18(%rdx)
 PC (0x7f921698c320) ok
 source "%rdi" ok
 destination "0x18(%rdx)" (0x0000004f) 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
Vague Entertainment (bflanagin) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 node_get_pos (node=0x7f92080ace10) at /build/buildd/glib2.0-2.38.0/./glib/gsequence.c:1677
 dee_sequence_model_peek_value (self=0x106c660, iter=0x7f92080ace10, column=<optimized out>) at dee-sequence-model.c:589
 dee_sequence_model_get_value (self=0x106c660, iter=0x7f92080ace10, column=17) at dee-sequence-model.c:607
 dee_serializable_model_get_row (self=0x11c10f0, iter=0x7f92080ace10, out_row_members=0x1291900) at dee-serializable-model.c:1014
 on_self_row_added (self=0x11c10f0, iter=0x7f92080ace10) at dee-shared-model.c:1594

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 friends (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in dee:
assignee: nobody → Michal Hruby (mhr3)
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in friends (Ubuntu):
status: New → Confirmed
Changed in friends (Ubuntu):
status: Confirmed → Invalid
Changed in dee:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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