Ubuntu
upower package

upowerd crashed with SIGABRT in __libc_message()

Bug #1005418 reported by Ozgur Kucuktekin
38
This bug affects 8 people
Affects Status Importance Assigned to Milestone
upower (Fedora)
Won't Fix
Undecided
upower (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

upower crash

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: upower 0.9.15-3git1
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16
Uname: Linux 3.2.0-24-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Sun May 27 19:01:39 2012
ExecutablePath: /usr/lib/upower/upowerd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

Signal: 6
SourcePackage: upower
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 lockdownd_gen_pair_cert () from /usr/lib/libimobiledevice.so.2
Title: upowerd crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Ozgur Kucuktekin (ozgurktekin) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __libc_message (do_abort=2, fmt=0xb74ba3bc "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 malloc_printerr (action=<optimized out>, str=<optimized out>, ptr=0x8c4f7b0) at malloc.c:5007
 lockdownd_gen_pair_cert (public_key=..., odevice_cert=0xbfe2d270, ohost_cert=0xbfe2d278, oroot_cert=0xbfe2d280) at lockdown.c:1241
 generate_pair_record_plist (pair_record_plist=<synthetic pointer>, public_key=..., host_id=<optimized out>) at lockdown.c:795
 lockdownd_do_pair (client=0x8c53960, pair_record=0x0, verb=0xb752015c "ValidatePair") at lockdown.c:871

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in upower (Ubuntu):
importance: Undecided → Medium
summary: - upowerd crashed with SIGABRT in raise()
+ upowerd crashed with SIGABRT in __libc_message()
tags: removed: need-i386-retrace
Robert Ancell (robert-ancell)
information type: 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
In , Christian (christian-redhat-bugs) wrote :

Description of problem:
Plugging in an iPhone 5S via USB triggers this crash reliably, and the crash keeps repeating infinitely.

The issue started about 2 weeks ago. Before that I had no problems with it on Fedora 22.
I am running an up-to-date system.

I never told the phone to trust the computer and open its services to the computer.
GNOME never shows the message that a phone was connected.

Version-Release number of selected component:
upower-0.99.3-1.fc22

Additional info:
reporter: libreport-2.5.1
backtrace_rating: 4
cmdline: /usr/libexec/upowerd
crash_function: g_try_malloc
executable: /usr/libexec/upowerd
global_pid: 4263
kernel: 4.0.4-303.fc22.x86_64
runlevel: N 5
type: CCpp
uid: 0

Truncated backtrace:
Thread no. 1 (8 frames)
 #3 g_try_malloc at gmem.c:244
 #4 get_contents_regfile at gfileutils.c:784
 #5 get_contents_posix at gfileutils.c:886
 #6 g_file_get_contents at gfileutils.c:987
 #7 sysfs_get_bool at sysfs-utils.c:127
 #8 up_device_supply_refresh_battery at up-device-supply.c:523
 #9 up_device_supply_refresh at up-device-supply.c:1128
 #10 up_device_supply_poll_unknown_battery at up-device-supply.c:912

Revision history for this message
In , Christian (christian-redhat-bugs) wrote :

Created attachment 1038900
File: backtrace

Revision history for this message
In , Christian (christian-redhat-bugs) wrote :

Created attachment 1038901
File: cgroup

Revision history for this message
In , Christian (christian-redhat-bugs) wrote :

Created attachment 1038902
File: core_backtrace

Revision history for this message
In , Christian (christian-redhat-bugs) wrote :

Created attachment 1038903
File: dso_list

Revision history for this message
In , Christian (christian-redhat-bugs) wrote :

Created attachment 1038904
File: environ

Revision history for this message
In , Christian (christian-redhat-bugs) wrote :

Created attachment 1038905
File: limits

Revision history for this message
In , Christian (christian-redhat-bugs) wrote :

Created attachment 1038906
File: maps

Revision history for this message
In , Christian (christian-redhat-bugs) wrote :

Created attachment 1038907
File: mountinfo

Revision history for this message
In , Christian (christian-redhat-bugs) wrote :

Created attachment 1038908
File: namespaces

Revision history for this message
In , Christian (christian-redhat-bugs) wrote :

Created attachment 1038909
File: open_fds

Revision history for this message
In , Christian (christian-redhat-bugs) wrote :

Created attachment 1038910
File: proc_pid_status

Revision history for this message
In , Christian (christian-redhat-bugs) wrote :

Created attachment 1038911
File: var_log_messages

Revision history for this message
In , Christian (christian-redhat-bugs) wrote :

Created attachment 1038913
systemd journal

Revision history for this message
In , Bastien (bastien-redhat-bugs) wrote :

*** Bug 1231768 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Bastien (bastien-redhat-bugs) wrote :

*** Bug 1231770 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Bastien (bastien-redhat-bugs) wrote :

Looks like a memory corruption problem, hard to detect without being able to reproduce the problem.

Christian, do those problems usually happen when you plug in an iPad or iPhone into your computer?

Revision history for this message
In , Christian (christian-redhat-bugs) wrote :

Hello Bastien,

yes, Plugging in an iPhone 5S via USB cable triggers this crash reliably for me, and the crash keeps repeating infinitely while the phone is connected. Just plugging in is sufficient, no other action like choosing "trust this device" on the phone is neccessary.

Revision history for this message
kolya (mar-kolya) wrote :

More detailed backtrace:

(gdb) bt
#0 0x00007f988bfda267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#1 0x00007f988bfdbeca in __GI_abort () at abort.c:89
#2 0x00007f988c01dbf3 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7f988c136168 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
#3 0x00007f988c025c09 in malloc_printerr (ptr=<optimized out>, str=0x7f988c1322ba "free(): invalid pointer", action=1) at malloc.c:4965
#4 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3834
#5 0x00007f988c02983c in __GI___libc_free (mem=<optimized out>) at malloc.c:2950
#6 0x000055c127b25f75 in start_poll_cb (idevice=0x55c128e48510) at up-device-idevice.c:114
#7 0x00007f988c7e2913 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8 0x00007f988c7e1eaa in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x00007f988c7e2250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007f988c7e2572 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x000055c127b1b5de in main (argc=1, argv=0x7ffea90738c8) at up-main.c:280

This seems to have been fixed upstream quite long time ago: https://cgit.freedesktop.org/upower/commit/?id=c9b2e177267b623850b3deedb1242de7d2e413ee

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Bug Watch Updater (bug-watch-updater)
Changed in upower (Fedora):
importance: Unknown → Undecided
status: Unknown → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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