RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/4191efda59c550b2197a34b3d0590b6d4bbb0cfa/

This is not a regression, thus removing the keyword. It is an old bug, which I was trying to fix in 1.31 devel cycle. Some fixes are already part of 1.30.3, but obviously, they don't fix it fully, because this report is for 1.30.4 version. I don't see any upstream reports for Fedora 26 and newer, so tentatively the following patch should fix it fully:
https://git.gnome.org/browse/gvfs/commit/?id=d659151

However, the patch is rather a workaround than proper fix and would be really nice to find the real cause, why the error variable is not defined at that point. Are you able to reproduce it somehow?

We can backport the patch anyway, so setting devel_ack+, but not sure it isn't too late at this point...

Another bug report for this issue already exists, so closing...

*** This bug has been marked as a duplicate of bug 1465302 ***