upowerd crashed with SIGSEGV in node_list_remove()

Bug #870593 reported by Alan Pope 🍺🐧🐱 🦄
312
This bug affects 62 people
Affects Status Importance Assigned to Milestone
Upower
Won't Fix
Critical
upower (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Plugged in iPhone 4 running iOS 5 beta 6 and get this crash, and the crash outlined in bug 870592 which may be a dupe of bug 730385.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: upower 0.9.13-1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Sat Oct 8 10:47:31 2011
ExecutablePath: /usr/lib/upower/upowerd
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f591113ed3a <node_list_remove+10>: mov 0x10(%rdi),%ecx
 PC (0x7f591113ed3a) ok
 source "0x10(%rdi)" (0x1a74000000cab810) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: upower
StacktraceTop:
 node_list_remove () from /usr/lib/libplist.so.1
 node_detach () from /usr/lib/libplist.so.1
 ?? () from /usr/lib/libplist.so.1
 ?? ()
 ?? ()
Title: upowerd crashed with SIGSEGV in node_list_remove()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Alan Pope 🍺🐧🐱 🦄 (popey) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 node_list_remove (list=0x1a74000000cab800, node=0x7f5911852840) at /build/buildd/libplist-1.6/libcnary/node_list.c:122
 node_detach (parent=0x7f5911ec97f0, child=<optimized out>) at /build/buildd/libplist-1.6/libcnary/node.c:99
 plist_free_node (node=0x7f5911852840) at /build/buildd/libplist-1.6/src/plist.c:73
 up_device_idevice_coldplug (device=0x22b3190) at up-device-idevice.c:117
 up_device_coldplug (device=0x22b3190, daemon=<optimized out>, native=0x22c4450) at up-device.c:548

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
tags: removed: need-amd64-retrace
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
visibility: private → public
Revision history for this message
In , Pedro Villavicencio (pedro) wrote :
Download full text (10.3 KiB)

this report has been filed here:

https://bugs.launchpad.net/ubuntu/+source/upower/+bug/870593

there's no specific steps on how to reproduce the crash, most of users are commenting that the crash appears just after login. Btw is this more like a libplist issue? Thanks!.

".
Thread 3 (Thread 0x7f590e702700 (LWP 1489)):
#0 0x00007f5911ecc0dd in read () at ../sysdeps/unix/syscall-template.S:82
No locals.
#1 0x00007f591159ea83 in read (__nbytes=128, __buf=0x7f590e701d30, __fd=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/unistd.h:45
No locals.
#2 unix_signal_helper_thread (data=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:4567
        i = <optimized out>
        bytes_read = 140020529529296
        b = '\000' <repeats 16 times>"\377, \377\377\377", '\000' <repeats 28 times>"\320, \200!", '\000' <repeats 21 times>, "\003\000\000\000\000\000\000\000\000\320\353\021Y\177\000\000\264\377\277\022Y\177\000\000\005", '\000' <repeats 23 times>"\220, &\332\020Y\177\000"
        sigterm_received = 0
        sigint_received = 0
        sighup_received = 0
#3 0x00007f59115c82b6 in g_thread_create_proxy (data=0x2290ea0) at /build/buildd/glib2.0-2.30.0/./glib/gthread.c:1962
        thread = 0x2290ea0
        __PRETTY_FUNCTION__ = "g_thread_create_proxy"
#4 0x00007f5911ec4efc in start_thread (arg=0x7f590e702700) at pthread_create.c:304
        __res = <optimized out>
        pd = 0x7f590e702700
        now = <optimized out>
        unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 6404682131891087322, 140734146252624, 140020471048640, 0, 3, -6462634030028757030, -6462626227677239334}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
        not_first_call = 0
        robust = <optimized out>
        pagesize_m1 = <optimized out>
        sp = <optimized out>
        freesize = <optimized out>
        __PRETTY_FUNCTION__ = "start_thread"
#5 0x00007f5910e7a89d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
No locals.
#6 0x0000000000000000 in ?? ()
No symbol table info available.
.
Thread 2 (Thread 0x7f590df01700 (LWP 1490)):
#0 0x00007f5910e6e773 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
        resultvar = <optimized out>
        oldtype = 0
        result = <optimized out>
#1 0x00007f59115a2f68 in g_main_context_poll (n_fds=3, fds=0x7f5908001100, timeout=-1, context=0x22a2aa0, priority=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3402
        poll_func = 0x7f59115b14c0 <g_poll>
#2 g_main_context_iterate (context=0x22a2aa0, block=<optimized out>, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3084
        max_priority = 2147483647
        timeout = -1
        some_ready = <optimized out>
        nfds = 3
        allocated_nfds = <optimized out>
        fds = 0x7f5908001100
#3 0x00007f59115a3792 in g_main_loop_run (loop=0x22a2a50) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3297
        __PRETTY_FUNCTION__ = "g_main_loop_run"
#4 0x00007f5910b15516 in gdbus_shared_thread_func (user_data=0x22a2a70) at /build/buildd/gli...

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: https://bugs.freedesktop.org/show_bug.cgi?id=43242 ; Btw this seems to be a libplist issue but not sure so contacting upstream, they have a better understanding of the software. Thanks all.

Changed in upower (Ubuntu):
status: Confirmed → Triaged
Changed in upower:
importance: Unknown → Critical
status: Unknown → Confirmed
Revision history for this message
Vladimir Scherbaev (zemik) wrote :

Affect me on 12.04

tags: added: precise
Revision history for this message
In , Bugzilla-x (bugzilla-x) wrote :

It's either a bug in libimobiledevice, or our use of it. I cannot reproduce the problem locally, and the last bug dates back from 2012. As nothing changed on the UPower side, it's likely a problem lower down the stack.

Changed in upower:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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