Bug 1745762

Summary: [abrt] android-tools: fatal_errno(): adb killed by SIGABRT
Product: [Fedora] Fedora Reporter: Christian Kujau <redhat>
Component: android-toolsAssignee: Ivan Afonichev <ivan.afonichev>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: admiller, ivan.afonichev, jeroen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a0b6ee8b35a67d3caccad0c39852fa768e72cb26
Whiteboard: abrt_hash:de3ec4015827d7010896a9b2d6486a4f57acb293;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-01 04:10:30 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: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Christian Kujau 2019-08-26 20:46:02 UTC 
Version-Release number of selected component:
android-tools-20180828gitc7815d675-3.fc30

Additional info:
reporter:       libreport-2.10.1
backtrace_rating: 4
cmdline:        adb -L tcp:5037 fork-server server --reply-fd 4
crash_function: fatal_errno
executable:     /usr/bin/adb
journald_cursor: s=6ce954209fc445b9a398f87bc47a6f8b;i=16b0;b=2b2c42904c194f2081ce10260e4c1e29;m=85fa9283;t=590e6bc0e602d;x=da7c83cb8df7cd90
kernel:         5.2.8-200.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (1 frames)
 #2 fatal_errno at core/adb/adb.cpp:103

Potential duplicate: bug 1664322
Comment 1 Christian Kujau 2019-08-26 20:46:04 UTC 
Created attachment 1608314 [details]
File: backtrace
Comment 2 Christian Kujau 2019-08-26 20:46:04 UTC 
Created attachment 1608315 [details]
File: cgroup
Comment 3 Christian Kujau 2019-08-26 20:46:05 UTC 
Created attachment 1608316 [details]
File: core_backtrace
Comment 4 Christian Kujau 2019-08-26 20:46:06 UTC 
Created attachment 1608317 [details]
File: cpuinfo
Comment 5 Christian Kujau 2019-08-26 20:46:07 UTC 
Created attachment 1608318 [details]
File: dso_list
Comment 6 Christian Kujau 2019-08-26 20:46:08 UTC 
Created attachment 1608319 [details]
File: environ
Comment 7 Christian Kujau 2019-08-26 20:46:09 UTC 
Created attachment 1608320 [details]
File: limits
Comment 8 Christian Kujau 2019-08-26 20:46:10 UTC 
Created attachment 1608321 [details]
File: maps
Comment 9 Christian Kujau 2019-08-26 20:46:11 UTC 
Created attachment 1608322 [details]
File: mountinfo
Comment 10 Christian Kujau 2019-08-26 20:46:11 UTC 
Created attachment 1608323 [details]
File: open_fds
Comment 11 Christian Kujau 2019-08-26 20:46:12 UTC 
Created attachment 1608324 [details]
File: proc_pid_status
Comment 12 Ben Cotton 2020-04-30 21:15:59 UTC 
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 '30'.

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 30 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.
Comment 13 Christian Kujau 2020-05-01 04:10:30 UTC 
I can't reproduce this (anymore), closing.