parole crashed with SIGSEGV in 5mcInteractiDone() (19.10 xubuntu qa-test; shutdown didn't occur)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
parole (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
19.10 Xubuntu daily test
I was trying to shutdown system using whisker menu. it did nothing.
I assumed I'd made a mistake without mouse so tried again and got message
"Received error while trying to log out \n GDBus.Error.
Then apport appear and is reporting this `parole` crashed (i didn't close windows prior to attempt to shutdown.
note everything here is typed into d960 (system near it), not copy/pasted on d755 or test system where crash occurred (firefox won't load on that system anymore..)
ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: parole 1.0.2-0ubuntu1
ProcVersionSign
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu2
Architecture: amd64
CasperVersion: 1.407
CurrentDesktop: XFCE
Date: Tue Jun 4 06:09:03 2019
ExecutablePath: /usr/bin/parole
LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190604)
ProcCmdline: parole /media/
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fef99980348 <SmcInteractDon
PC (0x7fef99980348) 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 /lib/x86_
?? () from /lib/x86_
_SmcProcessMessage () from /lib/x86_
IceProcessMessages () from /lib/x86_
?? () from /lib/x86_
Title: parole crashed with SIGSEGV in SmcInteractDone()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:
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.