RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem: This problem occurs if you log in to KDE desktop by root user, start Konsole terminal emulator, and use nmtui.

Version-Release number of selected component (if applicable): NetworkManager-tui-1.8.0-11.el7_4.x86_64

How reproducible: Always

Steps to Reproduce:
1) Log in to KDE desktop by root user 
2) start Konsole terminal emulator
3) Run nmtui as follows :

  i) Press Enter on "Edit a connection"  
 ii) Press Enter on "<Edit...>"
iii) Click "Allow once" 2 or 3 times on KDE Wallet dialog
 iv) It will take about 1 minutes to transit to "Edit connection" screen.

Actual results: screen transition is slow


Expected results: screen transition shouldn't take significant time

Additional Info : 

1) It does NOT occur if logging in to KDE desktop by normal user and become
root user by "su -" and run nmtui. (In this case, KDE Wallet dialog is not displayed.)

2) It does NOT occur if using GNOME desktop instead of KDE.

3) Disabling KDE Wallet does not work.
(KDE Wallet can be disabled by System Settings -> Account Details -> KDE Wallet
-> Uncheck "Enable the KDE Wallet subsystem" -> Click "Apply")

When running KDE, plasma-nm registers itself as a NM secret agent.

When the connection is opened for edit by nmtui, NetworkManager requests the connection's secret to the registered secret agents. It seems that on RHEL plasma-nm doesn't respond at GetSecret() requests from NM and makes them time out, causing the delay in nmtui.

For this reason I'm reassigning this bug to plasma-nm for investigation.

https://github.com/NetworkManager/NetworkManager/pull/327

we have no way to verify this but the reporter said, it's far better now as ipv4 and proxy are not asking for secrets anymore.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2302