Ubuntu
upower package

upowerd crashed with SIGSEGV in __stpcpy_chk()

Bug #1062398 reported by Reiner Jung on 2012-10-05

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	upower (Ubuntu)	New	Medium	Unassigned

Bug Description

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:

Tags:

Revision history for this message

Reiner Jung (prefec2) wrote on 2012-10-05:

#1

Dependencies.txt Edit (3.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (808 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (9.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (743 bytes, text/plain; charset="utf-8")
Registers.txt Edit (490 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (925 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (2.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-05: Possible regression detected

#2

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.

tags:

added: regression-retracer

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-05:

#3

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

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-05: Stacktrace.txt

#4

Stacktrace.txt Edit (3.9 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-05: StacktraceSource.txt

#5

StacktraceSource.txt Edit (4.2 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-05: ThreadStacktrace.txt

#6

ThreadStacktrace.txt Edit (8.2 KiB, text/plain)

Changed in upower (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Robert Ancell (robert-ancell) on 2014-03-18

information type:

Private → Public

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.