Bug 1626778

Summary: [abrt] NetworkManager: rl_callback_read_char(): nmcli killed by SIGABRT
Product: [Fedora] Fedora Reporter: Marcin Szydelski <marcin>
Component: NetworkManagerAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: alexl, bgalvani, dcbw, fadnix, fgiudici, john.j5live, lkundrak, mclasen, rhughes, rstrode, sandmann
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/335bf1593c2d7999b6a3a2cbf8915bd21d5489ca
Whiteboard: abrt_hash:073320d72f3b2f51697ac28c633a40cc5636bc4e;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 22:45:51 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 Marcin Szydelski 2018-09-08 14:34:04 UTC 
Description of problem:
crashing when I try to connect to a new wireless network (not saved before).

Version-Release number of selected component:
1:NetworkManager-1.10.10-1.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        nmcli connection edit TP-Link_A1AC
crash_function: rl_callback_read_char
executable:     /usr/bin/nmcli
journald_cursor: s=867f4c688d8c4915b38d5228252e2563;i=fff5c;b=bce1d17248684d66b69edca35d975bf8;m=be07be0;t=5755c29cd4bed;x=1574a2e580470a55
kernel:         4.17.19-200.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0
Comment 1 Marcin Szydelski 2018-09-08 14:34:14 UTC 
Created attachment 1481784 [details]
File: backtrace
Comment 2 Marcin Szydelski 2018-09-08 14:34:16 UTC 
Created attachment 1481785 [details]
File: cgroup
Comment 3 Marcin Szydelski 2018-09-08 14:34:20 UTC 
Created attachment 1481786 [details]
File: core_backtrace
Comment 4 Marcin Szydelski 2018-09-08 14:34:22 UTC 
Created attachment 1481787 [details]
File: cpuinfo
Comment 5 Marcin Szydelski 2018-09-08 14:34:25 UTC 
Created attachment 1481788 [details]
File: dso_list
Comment 6 Marcin Szydelski 2018-09-08 14:34:27 UTC 
Created attachment 1481789 [details]
File: environ
Comment 7 Marcin Szydelski 2018-09-08 14:34:29 UTC 
Created attachment 1481790 [details]
File: limits
Comment 8 Marcin Szydelski 2018-09-08 14:34:33 UTC 
Created attachment 1481791 [details]
File: maps
Comment 9 Marcin Szydelski 2018-09-08 14:34:37 UTC 
Created attachment 1481792 [details]
File: mountinfo
Comment 10 Marcin Szydelski 2018-09-08 14:34:41 UTC 
Created attachment 1481793 [details]
File: open_fds
Comment 11 Marcin Szydelski 2018-09-08 14:34:43 UTC 
Created attachment 1481794 [details]
File: proc_pid_status
Comment 12 Fahad Alduraibi 2018-10-02 08:37:43 UTC 
*** Bug 1635151 has been marked as a duplicate of this bug. ***
Comment 13 Marcin Szydelski 2018-10-05 21:29:54 UTC 
Today I found that to connect to a new network I have to manually create a keys-<netname> file with WPA_PSK=<passwd>.
That workaround solves an issue with crashing.
Comment 14 Ben Cotton 2019-05-02 20:44:20 UTC 
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 15 Ben Cotton 2019-05-28 22:45:51 UTC 
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.