Created attachment 1864999 [details] Log including gvfs crash Description of problem: Attempting to access a Nextcloud folder for an account configured via gnome-initial-setup results in "Remote peer disconnected" and a "gvfs quit unexpectedly" abrt message. Version-Release number of selected component (if applicable): nautilus-42~beta-2.fc36.x86_64 gvfs-1.49.90-1.fc36.x86_64 How reproducible: Every time. Steps to Reproduce: 1. Configure Nextcloud account via gnome-initial-setup 2. Open Nautilus 3. Click Nextcloud folder in side bar Actual results: "Remote peer disconnected" and "gvfs quit unexpectedly" abrt message. Expected results: Nextcloud folder to load. Additional info: abrt only sees an empty core dump. I have attached a log, crash happens around line 2331.
Reported upstream: https://gitlab.gnome.org/GNOME/gvfs/-/issues/608
Still occurs with Workstation beta 1.4 compose[0]. Mounting with davfs2 works fine. [0] - https://kojipkgs.fedoraproject.org/compose/36/Fedora-36-20220322.0/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-36_Beta-1.4.iso
Possible duplicate of bug 2066717.
This has a different backtrace, so I am not sure, but it is likely.
FEDORA-2022-ea5633132d has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ea5633132d
FEDORA-2022-ea5633132d 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-ea5633132d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ea5633132d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I can confirm the issue described here is fixed. Unfortunately now I run into a different (Nextcloud) issue[0][1]. [0] - https://gitlab.gnome.org/GNOME/gvfs/-/issues/617 [1] - https://github.com/nextcloud/server/issues/32061
This is going to be fixed by https://bodhi.fedoraproject.org/updates/FEDORA-2022-56ac7db53a.
(In reply to Ondrej Holy from comment #8) > This is going to be fixed by > https://bodhi.fedoraproject.org/updates/FEDORA-2022-56ac7db53a. I can confirm that with that update installed, everything works how I would expect.
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.
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.