Bug 1231763

Summary: [abrt] upower: g_try_malloc(): upowerd killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Christian Kirbach <c.kirbach>
Component: upowerAssignee: Richard Hughes <rhughes>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: bnocera, bochecha, c.kirbach, duminsky.nick, jean-baptiste, moshe, m.voropaiev, rhughes, samuel_lee_1991, titaniumkeys
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a27aa4f274bae70a88041953dd3d5f030618f497
Whiteboard: abrt_hash:c8ecaa17ae3ad040c9aed8a82ffc638e1e925b17
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 14:50:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
systemd journal none

Description Christian Kirbach 2015-06-15 11:30:37 UTC
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

Comment 1 Christian Kirbach 2015-06-15 11:30:40 UTC
Created attachment 1038900 [details]
File: backtrace

Comment 2 Christian Kirbach 2015-06-15 11:30:41 UTC
Created attachment 1038901 [details]
File: cgroup

Comment 3 Christian Kirbach 2015-06-15 11:30:42 UTC
Created attachment 1038902 [details]
File: core_backtrace

Comment 4 Christian Kirbach 2015-06-15 11:30:43 UTC
Created attachment 1038903 [details]
File: dso_list

Comment 5 Christian Kirbach 2015-06-15 11:30:44 UTC
Created attachment 1038904 [details]
File: environ

Comment 6 Christian Kirbach 2015-06-15 11:30:45 UTC
Created attachment 1038905 [details]
File: limits

Comment 7 Christian Kirbach 2015-06-15 11:30:47 UTC
Created attachment 1038906 [details]
File: maps

Comment 8 Christian Kirbach 2015-06-15 11:30:48 UTC
Created attachment 1038907 [details]
File: mountinfo

Comment 9 Christian Kirbach 2015-06-15 11:30:49 UTC
Created attachment 1038908 [details]
File: namespaces

Comment 10 Christian Kirbach 2015-06-15 11:30:50 UTC
Created attachment 1038909 [details]
File: open_fds

Comment 11 Christian Kirbach 2015-06-15 11:30:51 UTC
Created attachment 1038910 [details]
File: proc_pid_status

Comment 12 Christian Kirbach 2015-06-15 11:30:52 UTC
Created attachment 1038911 [details]
File: var_log_messages

Comment 13 Christian Kirbach 2015-06-15 11:34:05 UTC
Created attachment 1038913 [details]
systemd journal

Comment 14 Bastien Nocera 2015-06-26 09:45:20 UTC
*** Bug 1231768 has been marked as a duplicate of this bug. ***

Comment 15 Bastien Nocera 2015-06-26 09:45:30 UTC
*** Bug 1231770 has been marked as a duplicate of this bug. ***

Comment 16 Bastien Nocera 2015-06-26 09:56:56 UTC
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?

Comment 17 Christian Kirbach 2015-06-29 07:06:14 UTC
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.

Comment 18 Fedora End Of Life 2016-07-19 14:50:40 UTC
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.