upowerd crashed with SIGSEGV in __stpcpy_chk()

[Reiner Jung]

This is most likely the same as in #1034005. Hwoever, it happened after installing 12.10. So it looks like the problem remains.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: upower 0.9.17-1build1
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
Uname: Linux 3.2.0-31-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
Date: Fri Oct 5 14:39:06 2012
ExecutablePath: /usr/lib/upower/upowerd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0xb73e502e <__stpcpy_chk+30>: movzbl (%edx),%esi
 PC (0xb73e502e) ok
 source "(%edx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: upower
StacktraceTop:
 __stpcpy_chk () from /lib/i386-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: Upgraded to quantal on 2012-03-09 (210 days ago)
UserGroups:

[Apport retracing service (apport)]

This crash has the same stack trace characteristics as bug #1034005. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

[Apport retracing service (apport)]

StacktraceTop:
 __stpcpy_chk (dest=dest@entry=0xb74b0320 "", src=0x0, destlen=<optimized out>, destlen@entry=512) at stpcpy_chk.c:40
 strcpy (__src=<optimized out>, __dest=0xb74b0320 "") at /usr/include/i386-linux-gnu/bits/string3.h:105
 userpref_get_config_dir () at userpref.c:128
 userpref_get_config_dir () at userpref.c:105
 userpref_get_host_id (host_id=host_id@entry=0xbfe7d588) at userpref.c:406