Description of problem: This crash happens when I connect to server A, then server B, and then again server A (all over RDP). Can be reproduced 100%. Version-Release number of selected component: gnome-connections-42.1-1.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 3 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-842ea91f-6bea-47f1-b0ed-cb141f177f4e.scope cmdline: gnome-connections crash_function: frdp_session_configure_event executable: /usr/bin/gnome-connections journald_cursor: s=8b6ba1c691284e9fb128272f86372632;i=21cf6;b=112eeb9ed1ed40fe99a28889be550ca5;m=a97bc203;t=5dbfbcd40b940;x=5e0acbd61559fe90 kernel: 5.17.1-300.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 frdp_session_configure_event #1 _gtk_marshal_BOOLEAN__BOXED at gtk/gtkmarshalers.c:84 #3 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3743 #6 gtk_widget_event_internal.part.0.lto_priv.0 at ../gtk/gtkwidget.c:7812 #7 gtk_drawing_area_send_configure at ../gtk/gtkdrawingarea.c:264 #8 gtk_drawing_area_realize at ../gtk/gtkdrawingarea.c:224 #9 _g_closure_invoke_va at ../gobject/gclosure.c:893 #12 gtk_widget_realize at ../gtk/gtkwidget.c:5523 #13 gtk_widget_set_parent at ../gtk/gtkwidget.c:9663 #14 gtk_bin_add at ../gtk/gtkbin.c:135
Created attachment 1871060 [details] File: backtrace
Created attachment 1871061 [details] File: core_backtrace
Created attachment 1871062 [details] File: cpuinfo
Created attachment 1871063 [details] File: dso_list
Created attachment 1871064 [details] File: environ
Created attachment 1871065 [details] File: exploitable
Created attachment 1871066 [details] File: limits
Created attachment 1871067 [details] File: maps
Created attachment 1871068 [details] File: mountinfo
Created attachment 1871069 [details] File: open_fds
Created attachment 1871070 [details] File: proc_pid_status
Steps to Reproduce: 1. start gnome-connections 2. connect to a remote desktop A (localhost is sufficient) using RDP. (An RDP server can be easily started in GNOME Settings -> Sharing). 3. stop the connection using the quit button in top right 4. connect to a remote desktop B using RDP. (This can be a different server, or it can be the same URL as for server A, but you have to add it as a new *separate entry* using the + button). 5. stop the connection using the quit button in top right 6. connect again to remote desktop A using its existing entry in gnome-connections (i.e. don't use the + button) 7. crash
Proposing for a blocker consideration. Is connecting to server A -> B -> A a basic functionality of a remote desktop viewer? https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Default_application_functionality
This should be fixed by commit https://gitlab.gnome.org/GNOME/gtk-frdp/-/commit/8567157f51aaaf928d6048d28aecf3a404672357
Sorry, that's actually https://gitlab.gnome.org/GNOME/gtk-frdp/-/commit/7259754ae1be9680d99b9f9578611269bf4a5372
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 #16) > FEDORA-2022-4f7e9dc2fb has been submitted as an update to Fedora 36. > https://bodhi.fedoraproject.org/updates/FEDORA-2022-4f7e9dc2fb This is now fixed, thanks.
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.
Discussed in ticket: https://pagure.io/fedora-qa/blocker-review/issue/724 The decision to classify this bug as an AcceptedBlocker was made: "This violates the Default application functionality release criterion as it significantly hampers user experience with an application (GNOME Connections) that is part of the default application set for Fedora Workstation deliverable."
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.
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.