Bug 1297887

Summary: [abrt] upower: xmlInitParserCtxt__internal_alias(): upowerd killed by SIGABRT
Product: [Fedora] Fedora Reporter: Yves Bourdic <titaniumkeys>
Component: upowerAssignee: Richard Hughes <rhughes>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: rhughes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a533d1c2e8f6568c9683f5b0fa16dfd33937d928
Whiteboard: abrt_hash:7c33c55727145ef8009cf9a91e96b3dc63b0b417;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:39:25 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

Description Yves Bourdic 2016-01-12 17:18:49 UTC
Version-Release number of selected component:
upower-0.99.3-1.fc22

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/libexec/upowerd
crash_function: xmlInitParserCtxt__internal_alias
executable:     /usr/libexec/upowerd
global_pid:     1234
kernel:         4.2.8-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #6 xmlInitParserCtxt__internal_alias at parserInternals.c:1637
 #7 xmlNewParserCtxt__internal_alias at parserInternals.c:1857
 #8 xmlCreateMemoryParserCtxt__internal_alias at parser.c:14573
 #9 xmlSAXParseMemoryWithData__internal_alias at parser.c:14627
 #10 xmlSAXParseMemory__internal_alias at parser.c:14673
 #11 xmlParseMemory__internal_alias at parser.c:14687
 #12 plist_from_xml at xplist.c:560
 #13 receive_packet at libusbmuxd.c:209
 #14 usbmuxd_get_result at libusbmuxd.c:306
 #15 usbmuxd_get_device_list at libusbmuxd.c:852

Potential duplicate: bug 1276506

Comment 1 Yves Bourdic 2016-01-12 17:18:53 UTC
Created attachment 1114044 [details]
File: backtrace

Comment 2 Yves Bourdic 2016-01-12 17:18:54 UTC
Created attachment 1114045 [details]
File: cgroup

Comment 3 Yves Bourdic 2016-01-12 17:18:55 UTC
Created attachment 1114046 [details]
File: core_backtrace

Comment 4 Yves Bourdic 2016-01-12 17:18:57 UTC
Created attachment 1114047 [details]
File: dso_list

Comment 5 Yves Bourdic 2016-01-12 17:18:58 UTC
Created attachment 1114048 [details]
File: environ

Comment 6 Yves Bourdic 2016-01-12 17:18:59 UTC
Created attachment 1114049 [details]
File: limits

Comment 7 Yves Bourdic 2016-01-12 17:19:01 UTC
Created attachment 1114050 [details]
File: maps

Comment 8 Yves Bourdic 2016-01-12 17:19:02 UTC
Created attachment 1114051 [details]
File: mountinfo

Comment 9 Yves Bourdic 2016-01-12 17:19:04 UTC
Created attachment 1114052 [details]
File: namespaces

Comment 10 Yves Bourdic 2016-01-12 17:19:05 UTC
Created attachment 1114053 [details]
File: open_fds

Comment 11 Yves Bourdic 2016-01-12 17:19:06 UTC
Created attachment 1114054 [details]
File: proc_pid_status

Comment 12 Yves Bourdic 2016-01-12 17:19:08 UTC
Created attachment 1114055 [details]
File: var_log_messages

Comment 13 Fedora End Of Life 2016-07-19 18:39:25 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.