kwave crashed with SIGSEGV [NULL pointer dereference in libmirclient.so.9 after mir::dispatch::MultiplexingDispatchable::dispatch(unsigned int)]

Bug #1666874 reported by dinamic
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Expired
High
Unassigned
kwave (Ubuntu)
Invalid
Undecided
Unassigned
mir (Ubuntu)
Expired
High
Unassigned

Bug Description

ubuntu 17.04 Unity 8
kwave crashed with SIGSEGV

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: kwave 16.12.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
Uname: Linux 4.10.0-9-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity8
Date: Wed Feb 22 12:42:59 2017
ExecutablePath: /usr/bin/kwave
ExecutableTimestamp: 1484842756
InstallationDate: Installed on 2016-12-12 (71 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
ProcCmdline: kwave
ProcCwd: /home/pixel
Signal: 11
SourcePackage: kwave
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
 ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
 ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
 ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
Title: kwave crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
dinamic (dinamic6661) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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 kwave (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

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:

no debug symbol package found for libmad0

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 mir (Ubuntu):
status: New → Incomplete
summary: - kwave crashed with SIGSEGV
+ kwave crashed with SIGSEGV [NULL pointer dereference in
+ libmirclient.so.9 after
+ mir::dispatch::MultiplexingDispatchable::dispatch(unsigned int)]
Changed in mir:
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

All I can figure out from the ProcMaps and crash address is that the top of the stack is something in: mir::client::rpc::MirProtobufRpcChannel

Changed in mir:
importance: Undecided → High
Changed in mir (Ubuntu):
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Mir because there has been no activity for 60 days.]

Changed in mir:
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for mir (Ubuntu) because there has been no activity for 60 days.]

Changed in mir (Ubuntu):
status: Incomplete → Expired
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.