upowerd crashed with SIGSEGV in __stpcpy_chk()

Bug #1035670 reported by Nathan Williams
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
upower (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

just using the computer, no change in power state. upowerd crashed in the background.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: upower 0.9.17-1build1
ProcVersionSignature: Ubuntu 3.5.0-9.9-generic 3.5.0
Uname: Linux 3.5.0-9-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Fri Aug 10 21:09:04 2012
ExecutablePath: /usr/lib/upower/upowerd
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f5d42708c30 <__stpcpy_chk+304>: inc %edi
 PC (0x7f5d42708c30) ok
 source "%edi" ok
 SP (0x7fffa5357238) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: upower
StacktraceTop:
 __stpcpy_chk () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/libimobiledevice.so.3
 userpref_get_host_id () from /usr/lib/libimobiledevice.so.3
 lockdownd_client_new_with_handshake () from /usr/lib/libimobiledevice.so.3
 ?? ()
Title: upowerd crashed with SIGSEGV in __stpcpy_chk()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Nathan Williams (nathwill-deactivatedaccount-deactivatedaccount) wrote :
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in upower (Ubuntu):
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

tags: removed: need-amd64-retrace
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.