Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 2026622

Summary: gnome-shell Error connecting to Nautilus
Product: Red Hat Enterprise Linux 8 Reporter: Yaniv Ferszt <yferszt>
Component: gnome-shell-extensionsAssignee: Florian Müllner <fmuellner>
Status: CLOSED ERRATA QA Contact: Martin Krajnak <mkrajnak>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.5CC: dking, jadahl, jgrulich, oholy, tpelka, tpopela
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gnome-shell-extensions-3.32.1-25.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-10 13:42:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yaniv Ferszt 2021-11-25 10:59:44 UTC
Description of problem:
gnome-shell Error connecting to Nautilus found in the logs


Version-Release number of selected component (if applicable):
# rpm -qa| grep -i nautilus
nautilus-sendto-3.8.6-2.el8.x86_64
nautilus-extensions-3.28.1-15.el8.x86_64
nautilus-3.28.1-15.el8.x86_64
totem-nautilus-3.26.2-1.el8.x86_64
evince-nautilus-3.28.4-14.el8.x86_64
gnome-terminal-nautilus-3.28.3-3.el8.x86_64

# rpm -qa| grep -i gnome-shell
gnome-shell-extension-window-list-3.32.1-20.el8_5.1.noarch
gnome-shell-3.32.2-40.el8.x86_64
gnome-shell-extension-common-3.32.1-20.el8_5.1.noarch
gnome-shell-extension-launch-new-instance-3.32.1-20.el8_5.1.noarch
gnome-shell-extension-desktop-icons-3.32.1-20.el8_5.1.noarch
gnome-shell-extension-apps-menu-3.32.1-20.el8_5.1.noarch
gnome-shell-extension-horizontal-workspaces-3.32.1-20.el8_5.1.noarch
gnome-shell-extension-places-menu-3.32.1-20.el8_5.1.noarch


Steps to Reproduce:
1. Install RHEL 8.5 with GUI.
2. Login with a user
3. Observe /var/log/messages

Actual results:
The following is found in /var/log/messages
8<----------8<----------8<----------
Nov 23 17:56:34 hostname dbus-daemon[7943]: [session uid=903 pid=7943] Successfully activated service 'org.gnome.Nautilus'
Nov 23 17:56:34 hostname org.freedesktop.FileManager1[7943]: Failed to register: Unable to acquire bus name 'org.gnome.Nautilus'
Nov 23 17:56:34 hostname dbus-daemon[7943]: [session uid=903 pid=7943] Activated service 'org.freedesktop.FileManager1' failed: Process org.freedesktop.FileManager1 exited with status 1
Nov 23 17:56:34 hostname gnome-shell[8383]: Error connecting to Nautilus
8<----------8<----------8<----------


Expected results:
No error in /var/log/messages about "Error connecting to Nautilus"

Comment 4 Milan Crha 2021-11-26 06:28:18 UTC
I can confirm I see the warning when running the classic mode - except of the FileManager1 error, that I do not see). The GNOME mode doesn't show it, because it does not show desktop icons (which are/used-to-be provided by the Nautilus). Why that happens I've no idea, Nautilus is not a software I know anything about.

Comment 5 Ondrej Holy 2021-11-26 15:48:36 UTC
I see all those messages over journalctl on my RHEL 8 VM as well. After some digging, I finally see why it is happening. The desktop-icons extension activates the "org.gnome.Nautilus" and 
"org.freedesktop.FileManager1" services at the same time. The problem is that they are served by the same daemon in our case. So two daemons are started but only one can succeed when acquiring the bus names. I am not sure this can be handled better from the Nautilus resp. D-Bus side, but I would say that it should be possible to handle this better from the desktop-icons extension side...

This can be reproduced with two dbus-send calls at the same time:
$ dbus-send --session --print-reply --dest="org.gnome.Nautilus" /org/gnome/Nautilus org.gnome.Nautilus.FileOperations.EmptyTrash & \
dbus-send --session --print-reply --dest="org.freedesktop.FileManager1" /org/gnome/Nautilus org.gnome.Nautilus.FileOperations.EmptyTrash
[1] 12932
Error org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.FileManager1 exited with status 1
$ method return time=1637939989.676464 sender=:1.166 -> destination=:1.163 serial=35 reply_serial=2
[1]+  Done                    dbus-send --session --print-reply --dest="org.gnome.Nautilus" /org/gnome/Nautilus org.gnome.Nautilus.FileOperations.EmptyTrash

Before moving this to the gnome-shell-extensions component, I will try to find out, whether it could be handled better from the Nautilus resp. D-Bus side...

Comment 6 Ondrej Holy 2021-11-29 09:19:29 UTC
Just a note that the desktop-icons extension doesn't work with GNOME 40+, so can't be tested with recent Fedoras, but the dbus-send reproducer leads to similar errors in journal, though the dbus-send command doesn't fail itself, so maybe something has changed in D-Bus in the meantime:

lis 29 09:02:20 t480s systemd[1294]: Started dbus-:1.2-org.freedesktop.FileManager1.
lis 29 09:02:20 t480s systemd[1294]: Started dbus-:1.2-org.gnome.Nautilus.
lis 29 09:02:20 t480s nautilus[323592]: Failed to register: Unable to acquire bus name 'org.gnome.Nautilus'
lis 29 09:02:20 t480s systemd[1294]: dbus-:1.2-org.gnome.Nautilus: Main process exited, code=exited, status=1/FAILURE
lis 29 09:02:20 t480s systemd[1294]: dbus-:1.2-org.gnome.Nautilus: Failed with result 'exit-code'.

Comment 7 Ondrej Holy 2021-11-29 09:20:03 UTC
Does it cause any real issues, or is the main problem that there are some errors in the logs?

Comment 8 Ondrej Holy 2021-11-29 09:43:13 UTC
I don't see how this should be fixed from the Nautilus side, feel free to correct me, thus moving to gnome-shell-extensions. To fix these errors, I would say that the desktop-icons extension should use only one of those services and it should fallback to another one only if the first one doesn't provide all the needed interfaces...

Comment 9 Florian Müllner 2021-11-29 17:35:29 UTC
(In reply to Ondrej Holy from comment #8)
> To fix these errors, I would say that the desktop-icons extension should use only one of those
> services and it should fallback to another one only if the first one doesn't
> provide all the needed interfaces...

I don't think that's worth the effort. As far as I can see, the extension assumes that nautilus is available, and only uses the org.freedesktop.FileManager1 interface for (two) actions that don't have an equivalent in the nautilus interface.

That is, unless we explicitly support swapping out the file manager, I'll create all proxies for the org.gnome.Nautilus name and won't bother with fallbacks.

Comment 10 Ondrej Holy 2021-11-30 08:50:27 UTC
Hmm, yes, this should be pretty enough currently. The org.freedesktop.FileManager1 service is probably meant to open files in the default file manager, which doesn't work currently anyway: https://gitlab.gnome.org/GNOME/nautilus/-/issues/228.

Comment 12 Martin Krajnak 2021-12-01 12:48:57 UTC
gnome-shell-extension-screenshot-window-sizer-3.32.1-25.el8.noarch
gnome-shell-extension-native-window-placement-3.32.1-25.el8.noarch
gnome-shell-extension-auto-move-windows-3.32.1-25.el8.noarch
gnome-shell-extension-apps-menu-3.32.1-25.el8.noarch
gnome-shell-extension-workspace-indicator-3.32.1-25.el8.noarch
gnome-shell-extension-launch-new-instance-3.32.1-25.el8.noarch
gnome-shell-extension-user-theme-3.32.1-25.el8.noarch
gnome-shell-extension-dash-to-dock-3.32.1-25.el8.noarch
gnome-shell-extension-systemMonitor-3.32.1-25.el8.noarch
gnome-shell-extension-window-list-3.32.1-25.el8.noarch
gnome-shell-extension-no-hot-corner-3.32.1-25.el8.noarch
gnome-shell-extension-windowsNavigator-3.32.1-25.el8.noarch
gnome-shell-extension-places-menu-3.32.1-25.el8.noarch
gnome-shell-extension-drive-menu-3.32.1-25.el8.noarch
gnome-shell-extension-updates-dialog-3.32.1-25.el8.noarch
gnome-shell-extension-common-3.32.1-25.el8.noarch
gnome-shell-extension-dash-to-panel-3.32.1-25.el8.noarch
gnome-shell-extension-window-grouper-3.32.1-25.el8.noarch
gnome-shell-extension-desktop-icons-3.32.1-25.el8.noarch
gnome-shell-extension-top-icons-3.32.1-25.el8.noarch
gnome-shell-extension-gesture-inhibitor-3.32.1-25.el8.noarch
gnome-shell-extension-panel-favorites-3.32.1-25.el8.noarch
gnome-shell-extension-disable-screenshield-3.32.1-25.el8.noarch
gnome-shell-extension-heads-up-display-3.32.1-25.el8.noarch
gnome-shell-extension-horizontal-workspaces-3.32.1-25.el8.noarch

I can confirm that the message is gone after last update (I've tried the reproducer before I updated the packages), 
I tested both Wayland/Xorg and both classic and standard session, the error message is gone.

Comment 17 errata-xmlrpc 2022-05-10 13:42:04 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (gnome-shell-extensions bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:1807