parole crashed with SIGSEGV in SmcInteractDone()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| parole (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
artful beta1+ updates .. was just playing tracks randomly when it died. note: a chroot'd linux was also be updated at the same time.
no messages for plugins needed seen
a gstreamer backend failure message was presented on screen .. did a reboot prior to restarting parole
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: parole 0.9.2-1
ProcVersionSign
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Sep 13 13:13:11 2017
ExecutablePath: /usr/bin/parole
InstallationDate: Installed on 2017-03-24 (173 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
ProcCmdline: parole
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_CA.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7ff671c0fc18 <SmcInteractDon
PC (0x7ff671c0fc18) ok
source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: parole
StacktraceTop:
SmcInteractDone () from /usr/lib/
?? () from /usr/lib/
_SmcProcessMessage () from /usr/lib/
IceProcessMessages () from /usr/lib/
?? () from /usr/lib/
Title: parole crashed with SIGSEGV in SmcInteractDone()
UpgradeStatus: Upgraded to artful on 2017-09-13 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| Derk Willem te Bokkel (dtebokkel) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
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 #1228627, 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.