dee

friends-dispatcher crashed with SIGSEGV

Bug #1207899 reported by gepas
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
dee
New
Medium
Michal Hruby
friends (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Ubuntu Saucy Salamander (development branch)

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: friends-dispatcher 0.2.0+13.10.20130730-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Aug 2 23:02:22 2013
ExecutablePath: /usr/bin/friends-dispatcher
InstallationDate: Installed on 2013-07-26 (7 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130726)
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=it
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f8089f1d9fb: mov (%rax,%rdx,8),%rdi
 PC (0x7f8089f1d9fb) ok
 source "(%rax,%rdx,8)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: friends
StacktraceTop:
 ?? () 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
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
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
gepas (gennpas) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 flush_revision_queue (self=self@entry=0x10f8250) at dee-shared-model.c:385
 reset_model (self=0x10f8250) at dee-shared-model.c:1649
 on_invalidate (self=0x10f8250) at dee-shared-model.c:2193
 handle_dbus_method_call (connection=<optimized out>, sender=0x7f8085854c60 ":1.125", object_path=<optimized out>, interface_name=0x7f8085854c80 "com.canonical.Dee.Model", method_name=0x7f8085871f70 "Invalidate", parameters=<optimized out>, invocation=0x7f806c087f50, user_data=0x10f8250) at dee-shared-model.c:889
 call_in_idle_cb (user_data=<optimized out>) at /build/buildd/glib2.0-2.37.3/./gio/gdbusconnection.c:4868

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
Revision history for this message
Robert Bruce Park (robru) wrote :

Looks like a bug in libdee, hopefully there's enough information here for mhr3 to sort it out... ;-)

Changed in dee:
assignee: nobody → Michal Hruby (mhr3)
importance: Undecided → Medium
Revision history for this message
Michal Hruby (mhr3) wrote :

Doesn't seem to contain any public information, so marking as public.

Looks weird that we're trying to flush the revision queue during processing of invalidation, but it would be useful to see the console log that leads to the crash, as I think there'd be some extra criticals/warnings.

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
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.