Bug 1266666

Created attachment 1077366 [details]
File: backtrace

Created attachment 1077367 [details]
File: cgroup

Created attachment 1077368 [details]
File: core_backtrace

Created attachment 1077369 [details]
File: dso_list

Created attachment 1077370 [details]
File: environ

Created attachment 1077371 [details]
File: limits

Created attachment 1077372 [details]
File: maps

Created attachment 1077373 [details]
File: mountinfo

Created attachment 1077374 [details]
File: namespaces

Created attachment 1077375 [details]
File: open_fds

Created attachment 1077376 [details]
File: proc_pid_status

Created attachment 1077377 [details]
File: var_log_messages

Another user experienced a similar problem:

I plugged in my iPhone 4 into the PC USB port

reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/libexec/upowerd
crash_function: start_poll_cb
executable:     /usr/libexec/upowerd
global_pid:     4435
kernel:         4.2.6-301.fc23.x86_64
package:        upower-0.99.3-2.fc23
reason:         upowerd killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Another user experienced a similar problem:

No idea what happened. Things in Fedora 23 just crash out of the blue all the time. The same hardware worked fine under Fedora 20.

reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/libexec/upowerd
crash_function: start_poll_cb
executable:     /usr/libexec/upowerd
global_pid:     1444
kernel:         4.3.3-301.fc23.x86_64
package:        upower-0.99.3-2.fc23
reason:         upowerd killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

I had the same problem.  I think it happened when I plugged an iPhone 4 in via USB cable.  upowerd repeatedly crashes, gets restarted, crashes again, ad infinitum.

The backtrace shows start_poll_cb() in upowerd calling lockdownd_client_new_with_handshake() in /usr/lib64/libimobiledevice.so.6.0.0.

I also see the following in /var/log/messages:

upowerd[26954]: *** Error in `/usr/libexec/upowerd': double free or corruption (fasttop): 0x0000561f9d9f62d0 ***

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.