Public bug reported: This is a new bugfix release from upstream
This component is covered by the GNOME MicroReleaseException https://wiki.ubuntu.com/StableReleaseUpdates/GNOME From https://gitlab.gnome.org/GNOME/gvfs/-/raw/1.54.4/NEWS: * udisks2: Increasing reference count when updating volume to fix crashes (Ondrej Holy) * onedrive: Add missing replace stream to fix crashes (Jan-Michael Brummer) * onedrive: Fix double free during cache rebuild to fix crashes (Jan-Michael Brummer) * onedrive: Set name of drive root (Jan-Michael Brummer) * onedrive: Handle multiple drives with same IDs (Jan-Michael Brummer) * onedrive: Guess mime type locally if not set by the server (Jan-Michael Brummer) * ftp: Change cwd to root before renaming to prevent failures (rong wang) * udisks2: Ignore autofs mounts to prevent duplicated entries (Ondrej Holy) * ftp: Use timegm instead of mktime to not shift dates by timezone (Ondrej Holy) * ftp: Preserve mtime when copying to local (Ondrej Holy) * build: Add deprecated_apis option to control installation of headers (Ondrej Holy) * dav: Disable query_info_on_read method to fix mtime preservation (Ondrej Holy) * network: Disable usage of smbbrowse backend by default (Ondrej Holy) * smbbrowse: Don't enforce NT1 to fix mounting in certain cases (Ondrej Holy) * onedrive: Fix various memory leaks (Jan-Michael Brummer) * build: Disable burn backend by default (Ondrej Holy) * network: Request content-type attribute to suppress critical errors (Ondrej Holy) * metadata: Check g_stat result to avoid using of uninitialized value (Ondrej Holy) * ftp: Fix data connection to IPv6 link-local address (Ben Wolsieffer) * Translation updates (GNOME Translation Project contributors) Test case --------- Follow the testplan described on https://wiki.ubuntu.com/Process/Merges/TestPlans/gvfs Where problems could occur -------------------------- The main regression potential is in the usage of Microsoft's One Drive, there is a section in the testplan describing how to test that feature. Note that the burn:// backend is now disabled, but that's not a regression but rather a bug fix because it was leading to mounting an empty disk to nautilus that does not support any burning extension in noble (since GNOME 43). ** Affects: gvfs (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: gvfs (Ubuntu Noble) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Tags: udeng-6919 ** Also affects: gvfs (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: gvfs (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: gvfs (Ubuntu Noble) Status: New => In Progress ** Changed in: gvfs (Ubuntu Noble) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Tags added: udeng-6919 ** Changed in: gvfs (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2109540 Title: [SRU] Update gvfs to 1.54.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2109540/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
