This bug was fixed in the package gvfs - 1.44.1-1ubuntu1.1
---
gvfs (1.44.1-1ubuntu1.1) focal; urgency=medium
* debian/patches/fix-trashd-hang.patch: avoids deadlock in trashd that can
cause gtk file dialogs to hang system-wide (LP: #1927100)
-- David Buckmaster Tue, 21 Dec
Thank you for taking the time to do this!
--
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/1927100
Title:
Slow file dialogs, open and save
To manage notifications about this bug go
Confirming that
1. I noticed no regression in clean, fully-updated Ubuntu VMs over 48h
(periodic file browser operations and open-file dialogs in gtk apps, looped
`gio info trash:///` in terminal). Tested standard Ubuntu and Ubuntu MATE (per
the original report here).
2. I did NOT experience
Apologies for the delay, was just finally able to confirm yesterday that
the bug still exists on unpatched-gvfs (my container/transient fuse
mount workflow hadn't been active for a while, and that must've been a
critical part of reproducing the bug for me)
Moving onto -proposed shortly
--
You
I've had the fix for focal installed since yesterday and it seems to
have fixed the bug without any adverse effects
--
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/1927100
Title:
Slow
I've accepted this into -proposed on the basis that it'll make it
possible for you to verify, and it's easy to reject if it turns out you
can't verify it its easy to remove from proposed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Hello sam, or anyone else affected,
Accepted gvfs into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gvfs/1.44.1-1ubuntu1.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This sounds fine to me--sorry that it has ended up this way, but thanks
for offering this compromise.
Let me just first confirm that I can still reproduce it on my Mint
install--I've been running from my locally-patched gvfs since October,
so I should be sure it hasn't changed with any subsequent
Thank you for working with us to try and get a test plan for Ubuntu
together.
How about this:
1) I'll accept the package (1.44.1-1ubuntu1.1) into focal-proposed.
2) You test using your Ubuntu VM as best as you can to ensure that the package
hasn't regressed for Ubuntu users.
3) You verify the
I haven't seen the issue occur in an (idle) Ubuntu Mate VM after a week
or so. To be fair, I can't reproduce it in a clean Mint VM either.
There's a user in the Mint/Nemo issue tracker that was seeing the issue
using Ubuntu+Cinnamon, but they've since upgraded to 21.10 (with newer
gvfs) and are no
I created an (installed) VM of Ubuntu Mate, since that was the original
report.
My main affected workstation sees long uptimes, many transient podman
containers and fuse mounts, temporary files, etc. that are not easily
duplicated in a VM--I'm not sure if all/any of that contributes to the
Is there nobody using Ubuntu itself who will be able to help test at
all?
Is anyone willing to fire up an Ubuntu live image to help test it there?
If so, maybe it's worth seeing if the race reproduces in a live
environment on Ubuntu first?
--
You received this bug notification because you are a
I've seen the same issue reported in gnome trackers under
Nautilus+Fedora and Thunar+Arch, so I'm fairly sure it's not a Mint-
specific bug (though those are obviously not Ubuntu-based).
The original report here was for Ubuntu Mate...that's "direct" Ubuntu,
right? If there's anyone out there, I'd
> I guess the goal there would just be to say the issue occurred X times
in Y hours on 1.44.1-1ubuntu1, and zero times in Z hours on -proposed.
I think something like that would be fine, yes.
I'm not sure about using Mint for the test though. Are there any direct
users of Ubuntu who could test
I can tell you anecdotally that I went from pkill-ing gvfsd-trash hourly
or worse, to not once since I applied the patch locally in October. But
even after all that, I'm not really sure what behavior of mine was
triggering the lockup so frequently.
Is an anecdotal user-report like that enough?
The patch and upload look good. Thanks!
> To my knowledge, there is not a 100% reproducer for gvfs from
userspace as this is a probable lock-ordering issue in lower-level code.
https://gitlab.gnome.org/GNOME/glib/-/issues/1941 contains a reproducer
for the underlying glib issue.
I appreciate the
I've uploaded this now, thanks!
$ dput gvfs_1.44.1-1ubuntu1.1_source.changes
Trying to upload package to ubuntu
Checking signature on .changes
gpg: /tmp/pkgs/focal/gvfs_1.44.1-1ubuntu1.1_source.changes: Valid signature
from 1E918B66765B3E31
Checking signature on .dsc
gpg:
The bug description is now updated. Apologies for anything I missed!
--
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/1927100
Title:
Slow file dialogs, open and save
To manage
In the attached patch, I've edited debian/changelog to include the LP
bug # as requested. I also went ahead and added some
description/reference links to the patch itself--I ended up creating a
new debdiff to do this since I wasn't sure how to manually update line
numbers in a way that would be
I would have used a version number of 1.44.1-1ubuntu2~ppa1 as this is
greater than 1.44.1-1ubuntu1 and less than 1.44.1-1ubuntu2.
$ dpkg --compare-versions 1.44.1-1ubuntu2~ppa1 lt 1.44.1-1ubuntu2; echo $?
0
$ dpkg --compare-versions 1.44.1-1ubuntu2~ppa1 gt 1.44.1-1ubuntu1; echo $?
0
Sure, I'll try to take care of that soon.
I was also a little unclear on what to do about the version number--I
forced something non-standard (1.44.1-1ubuntu1-test) so that it would
locally supersede the current ubuntu version but not block updates.
Should the debdiff reflect what would be the
The debdiff here looks fine, although the debian/changelog should
reference this bug report using the syntax (LP: #1927100). Because this
fix is for a stable release of Ubuntu we need to follow the Stable
Release Update policy (https://wiki.ubuntu.com/StableReleaseUpdates).
Could you please add
Just a quick confirmation that with the patch applied, I've had no
gvfsd-trash deadlocks requiring a pkill in over a week. It was
previously hourly or worse.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
** Changed in: gvfs (Ubuntu)
Importance: Undecided => Low
** Also affects: gvfs (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: gvfs (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: gvfs (Ubuntu)
Status: Confirmed => Fix Released
--
You
The attachment "gvfs.debdiff" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you
I created a patch to 1.44.1-1ubuntu1 from the merge request on GNOME's
gvfs gitlab (https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96)
commit dc21a0948bcbe8a6d79d674bd1e4d63ded57d340
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gvfs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
Yes, please could the fix be included on Ubuntu 20.04 ?
--
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/1927100
Title:
Slow file dialogs, open and save
To manage notifications about
28 matches
Mail list logo
