upowerd crashed with SIGSEGV in __stpcpy_chk()

[Mathias Burén]

I didn't suspend, resume or unplug anything (on AC power), this just popped up while I was working. I saw the other report about coming back from suspend but I didn't suspend, so thought I'd do a separate.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: upower 0.9.17-1build1
ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Tue Sep 11 23:32:34 2012
ExecutablePath: /usr/lib/upower/upowerd
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7fe4c7a3db50 <__stpcpy_chk+80>: mov (%rsi),%rax
 PC (0x7fe4c7a3db50) 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_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:

[Mathias Burén (mathias-buren)]

Actually it might have happened just as I was pluggin in an iPhone 4s phone. (shotwell and rhythmbox were launching)

[Launchpad Janitor (janitor)]

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

[Apport retracing service (apport)]

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.