Description of problem: When you have some saved connection entries in gnome-connections and want to remove them, in most cases they seem to get removed, but then re-appear when the application is restarted. That means the app gets cluttered with lots of IP addresses that you used in the past and you can't get rid of them, which makes the navigation pretty bad. Version-Release number of selected component (if applicable): gnome-connections-42.1-1.fc36.x86_64 How reproducible: always Steps to Reproduce: 1. start gnome-connections 2. create some new connection entries. They don't need to be real, connecting to an invalid IP/hostname will still create an entry. So e.g. try to connect over VNC to "foo", "bar" a "baz", that will fail to connect, but will create 3 entries for you. 3. remove foo, bar and baz entries 4. wait until the info bar "connection has been deleted" disappears (this is important) 5. close and reopen gnome-connections 6. see foo, bar and baz entries back Actual results: entries are not deleted, they return after app restart Expected results: entries are deleted Additional info: There are workarounds to force the app the actually delete the entries: 1. One workaround is to click the X button on the "connection has been deleted" info bar. That will delete the entry. If you're deleting multiple entries, you need to click the X button for each of them, i.e. you can't delete multiple entries and then click the X button only on the last notification bar. 2. A second workaround is to close the whole app before the "connection has been deleted" info bar disappears. That will also delete the entry. This makes deleting multiple entries quite impractical, though. An upstream report: https://gitlab.gnome.org/GNOME/connections/-/issues/84
Proposing for a blocker consideration. Do you deleting existing entries a basic functionality of a remote desktop viewer? https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Default_application_functionality
I just posted a fix for this upstream at https://gitlab.gnome.org/GNOME/connections/-/commit/f5f3baf8ee736f6b4c28fd1f4e229ef29381eab5
FEDORA-2022-4f7e9dc2fb has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-4f7e9dc2fb
(In reply to Fedora Update System from comment #3) > FEDORA-2022-4f7e9dc2fb has been submitted as an update to Fedora 36. > https://bodhi.fedoraproject.org/updates/FEDORA-2022-4f7e9dc2fb This bug is partially fixed now. Removing a single entry seems to work now in all cases. However, when removing multiple entries, it seems that only the last one gets removed, the others return back after app restart. The workaround seems to be wait after each deletion until the notification bar disappears, and only then remove the next entry.
FEDORA-2022-4f7e9dc2fb has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-4f7e9dc2fb` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-4f7e9dc2fb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-4f7e9dc2fb has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
Reopening because of comment 4.
Based on votes in https://pagure.io/fedora-qa/blocker-review/issue/721 , rejected as a blocker and accepted as a freeze exception (if another fix is available before the Final release).
FEDORA-2022-13ed0f323e has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-13ed0f323e
FEDORA-2022-13ed0f323e has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
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.
Is there an upstream issue tracking the "removing multiple entries" issue?
I'm not aware of it, but it's mentioned in https://gitlab.gnome.org/GNOME/connections/-/issues/84 , so it can be easily reopened for that purpose.
I don't think anyone will address this if you don't open an issue issue.
I don't have the right to reopen that issue, but you have, so I don't understand the point of this discussion. Opening a new issue is just needless busywork. But anyway, here we go: https://gitlab.gnome.org/GNOME/connections/-/issues/134
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.