upowerd crashed with SIGSEGV in __stpcpy_chk()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upower (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The issue happened while the computer was on power but I left it on for about 24 hours alone, and when back found the error report and lead me to this page.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: upower 0.9.17-1build1
ProcVersionSign
Uname: Linux 3.5.0-7-generic x86_64
NonfreeKernelMo
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Sat Aug 11 17:11:15 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: /usr/lib/
ProcEnviron:
SegvAnalysis:
Segfault happened at: 0x7fbd35aa5b50 <__stpcpy_chk+80>: mov (%rsi),%rax
PC (0x7fbd35aa5b50) ok
source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: upower
StacktraceTop:
__stpcpy_chk () from /lib/x86_
?? () from /usr/lib/
userpref_
lockdownd_
?? ()
Title: upowerd crashed with SIGSEGV in __stpcpy_chk()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
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 #1034005, 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.