Bug 2065053 - NetworkManager-vpnc UI disables "Add" button regardless of input validity
Summary: NetworkManager-vpnc UI disables "Add" button regardless of input validity
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager-vpnc
Version: 36
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2022-03-17 08:53 UTC by Jacob Emcken
Modified: 2023-05-25 17:40 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2023-05-25 17:40:33 UTC
Type: Bug

Attachments (Terms of Use)
Demo how to reproduce the bug (394.80 KB, video/webm)
2022-03-17 08:53 UTC, Jacob Emcken
no flags Details

Description Jacob Emcken 2022-03-17 08:53:37 UTC
Created attachment 1866344 [details]
Demo how to reproduce the bug

Description of problem:
Unable to add a vpnc connection.

Version-Release number of selected component (if applicable):
NetworkManager-vpnc.x86_64          1:1.2.8-1.fc36             @updates-testing                  
NetworkManager-vpnc-gnome.x86_64    1:1.2.8-1.fc36             @updates-testing                  
vpnc.x86_64                         0.5.3-43.svn550.fc36       @fedora                           
vpnc-script.noarch                  20201205-4.gitcdbd5b.fc36  @fedora 

How reproducible:
Every time

Steps to Reproduce:
1. Open Networks Settings
2. Add VPN (plus button)
3. Choose Cisco Compatible VPN (vpnc)
4. Fill out "Gateway"
5. Fill out "User name"
6. Write a single letter in "Group name" (or paste a whole string)
7. See the "Add" button become active
8a. Change a single character in "Group name"...
8b. or open "Advanced..." modal and close it again.

Actual results:
The "Add" button becomes inactive and never becomes active again.

Expected results:
The "Add" button stays active until the form fields are "invalid"

Additional info:
Workaround is to fill "Group name" last.

Comment 1 Felix Schwarz 2022-07-17 11:09:31 UTC
I think this problem is recorded in the following upstream issue: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/982

possible duplicate: bug 2064779

Comment 2 Ben Cotton 2023-04-25 16:55:47 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ludek Smid 2023-05-25 17:40:33 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.