gedit admin:///home no longer work

[corrado venturini]

reproduce problem described in https://gitlab.freedesktop.org/polkit/polkit/-/issues/136
I see:
corrado@corrado-n2-hh-0402:~$ gedit admin:///home

(gedit:15891): GVFS-WARNING **: 18:05:08.157: The peer-to-peer connection failed: Could not connect: Permission denied. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges.

** (gedit:15891): WARNING **: 18:05:08.159: Hit unhandled case 36 (GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subject does not have uid set) in parse_error.

and:
corrado@corrado-n2-hh-0402:~$ ubuntu-bug nautilus
ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 227, in _run_hook
    symb['add_info'](report, ui)
  File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info
    apport.hookutils.attach_casper_md5check(report,
  File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 945, in attach_casper_md5check
    with open(location) as json_file:
PermissionError: [Errno 13] Permission denied: '/var/log/installer/casper-md5check.json'
corrado@corrado-n2-hh-0402:~$

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: nautilus 1:3.38.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu61
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 6 18:12:28 2021
GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1269, 611)'
InstallationDate: Installed on 2021-04-02 (4 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 evince 3.39.2-1
 file-roller 3.38.0-1
 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
 nautilus-share 0.7.3-2ubuntu3

[Sebastien Bacher (seb128)]

sounds like it's basically the same issue than bug #1922548 no?