Description of problem: I just tested adding a Google account in GNOME Online Accounts in Fedora 38, and the Google Drive shortcut doesn't appear in Nautilus after the account is added to GOA. That's because `gvfs-goa` package is not installed by default. Once I install it and reboot, I can use Nautilus to browse my Google Drive. It seems that either gnome-online-accounts should require/recommend gvfs-goa, or the Workstation package group should specify gvfs-goa, so that Google account integration works out of the box. //Edit: It seems I was wrong, gvfs-goa is installed by default. See comment 7. Version-Release number of selected component (if applicable): Fedora-Workstation-Live-x86_64-38-20230301.n.0.iso gnome-control-center-44~beta-2.fc38.x86_64 nautilus-44~beta-1.fc38.x86_64 How reproducible: always
Proposing as a Beta freeze exception. This is something users might want to select in the initial setup, but it won't work for them properly.
gnome-online-accounts should depend on gvfs-goa. I think we generally expect Google Drive to work out of the box.
(In reply to Neal Gompa from comment #2) > gnome-online-accounts should depend on gvfs-goa. I think we generally expect > Google Drive to work out of the box. This feature was removed in GNOME 44 because it depends on libgdata, which was removed because it wasn't ported to libsoup 2. But we don't necessarily have to remove it from Fedora. At least gvfs doesn't seem to be crashing due to soup symbol mixing.
(In reply to Neal Gompa from comment #2) > gnome-online-accounts should depend on gvfs-goa. I think we generally expect > Google Drive to work out of the box. I'll get this change out.
FEDORA-2023-3a43fdafdd has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-3a43fdafdd
FEDORA-2023-3a43fdafdd has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-3a43fdafdd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Well this is embarrassing. I just reinstalled my F38 VM and found out that gvfs-goa *is* installed by default. It's present on the Workstation Live. I also tested a network installation, and it's also installed by default (even before the GOA update hit repos). It's because gvfs-goa is listed as part of the gnome-desktop comps group. I have no idea how I ended up with that package missing, I certainly didn't uninstall it and I believed my VM was fairly fresh installation. Now it's gone, I can't figure it out anymore :-/ Anyway, sorry for confusion. It might still make sense to keep the requires at GOA, or we can drop it again, because the described problem is likely not happening by default. Either way, we don't need to rush to make it happen before Beta. > You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-3a43fdafdd I tested it and it works fine.
> But we don't necessarily have to remove it from Fedora. At least gvfs doesn't seem to be crashing due to soup symbol mixing. Yup, it doesn't crash as the different libsoup versions are linked with different binaries...
Does anyone know if gvfs-goa makes sense in a flatpak container? Right now we only have the gvfs-client subpackage included in the flatpak runtime.
(In reply to Kalev Lember from comment #9) > Does anyone know if gvfs-goa makes sense in a flatpak container? Right now > we only have the gvfs-client subpackage included in the flatpak runtime. No, this is not needed in flatpak runtime.
OK, in that case we should change the 'Requires: gvfs-goa' in gnome-online-accounts to either: Recommends: gvfs-goa or %if !0%{?flatpak} Requires: gvfs-goa %endif Otherwise it will get pulled in to flatpak containers.
FEDORA-2023-b08d7088ec has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-b08d7088ec
Thanks, Gwyn!
FEDORA-2023-b08d7088ec has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-b08d7088ec See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Discussed during the 2023-03-06 blocker review meeting: [0] The decision to classify this bug as a "RejectedFreezeException (Beta)" was made as new information indicates there's no compelling reason to grant an exception here. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-03-06/f38-blocker-review.2023-03-06-17.00.txt
FEDORA-2023-b08d7088ec has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.