parole crashed with SIGSEGV in SmcInteractDone() when i pressed reboot in xfce
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
parole (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I pressed reboot to reboot my dell e7440 laptop because the audio died of the sound card (also happens in windows 8.1). Then i got this crash of parole (it was playing a full hd video recorded by my galaxy s3)
sb_release -rd
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
apt-cache policy parole
parole:
Installed: 0.6.0-1
Candidate: 0.6.0-1
Version table:
*** 0.6.0-1 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: parole 0.6.0-1
ProcVersionSign
Uname: Linux 3.13.0-19-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Mar 25 19:17:27 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/parole
InstallationDate: Installed on 2014-03-17 (8 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140225)
ProcCmdline: parole /media/
SegvAnalysis:
Segfault happened at: 0x7f9d3a3ebc4e <SmcInteractDon
PC (0x7f9d3a3ebc4e) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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.