Ubuntu
libimobiledevice package

upowerd crashed with SIGABRT in __assert_fail_base()

Bug #1332848 reported by Xiaoqi Zhao on 2014-06-21

52

This bug affects 10 people

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

Bug Description

error right after login

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: upower 0.9.23-2ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.3-0ubuntu2
Architecture: i386
Date: Wed Jun 18 18:21:27 2014
ExecutablePath: /usr/lib/upower/upowerd
InstallationDate: Installed on 2014-05-21 (31 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta i386 (20140326)
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

Signal: 6
SourcePackage: upower
StacktraceTop:
__assert_fail_base (fmt=0xb73bab94 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0xb740baa1 "data", file=file@entry=0xb740bac9 "plist.c", line=line@entry=194, function=function@entry=0xb740bdcb "plist_copy_node") at assert.c:92
__GI___assert_fail (assertion=0xb740baa1 "data", file=0xb740bac9 "plist.c", line=194, function=0xb740bdcb "plist_copy_node") at assert.c:101
?? () from /usr/lib/i386-linux-gnu/libplist.so.2
plist_copy () from /usr/lib/i386-linux-gnu/libplist.so.2
?? () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
Title: upowerd crashed with SIGABRT in __assert_fail_base()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Tags:

Revision history for this message

Xiaoqi Zhao (xiaoqi) wrote on 2014-06-21:

#1

Dependencies.txt Edit (4.1 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (536 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (12.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (762 bytes, text/plain; charset="utf-8")
Registers.txt Edit (457 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (3.2 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (5.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2014-06-21:

#2

StacktraceTop:
__assert_fail_base (fmt=0xb73bab94 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0xb740baa1 "data", file=file@entry=0xb740bac9 "plist.c", line=line@entry=194, function=function@entry=0xb740bdcb <__PRETTY_FUNCTION__.3675> "plist_copy_node") at assert.c:92
__GI___assert_fail (assertion=assertion@entry=0xb740baa1 "data", file=file@entry=0xb740bac9 "plist.c", line=line@entry=194, function=function@entry=0xb740bdcb <__PRETTY_FUNCTION__.3675> "plist_copy_node") at assert.c:101
plist_copy_node (node=node@entry=0x0, parent_node_ptr=parent_node_ptr@entry=0xbfd9422c) at plist.c:194
plist_copy (node=0x0) at plist.c:237
lockdownd_do_pair (client=0x0, pair_record=0x6, verb=0xb7425e95 "ValidatePair") at lockdown.c:959

Revision history for this message

Apport retracing service (apport) wrote on 2014-06-21: Stacktrace.txt

#3

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

Revision history for this message

Apport retracing service (apport) wrote on 2014-06-21: StacktraceSource.txt

#4

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

Revision history for this message

Apport retracing service (apport) wrote on 2014-06-21: ThreadStacktrace.txt

#5

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

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

Revision history for this message

Seth Arnold (seth-arnold) wrote on 2014-06-23: Bug is not a security issue

#6

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type:

Private Security → Public

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-06-26:

#7

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

Changed in upower (Ubuntu):
status:	New → Confirmed

Revision history for this message

Tim Lunn (darkxst) wrote on 2014-07-25:

#8

This crash appears to be happening when disconnecting an iphone (or other idevice). The stack trace show it trying to create a new pairing which fails (presumably since the idevice is now unplugged).

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-10-03:

#9

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

Changed in libimobiledevice (Ubuntu):
status:	New → Confirmed

Alberto Salvia Novella (es20490446e) on 2014-11-12

Changed in libimobiledevice (Ubuntu):
importance:	Undecided → Medium

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.