As I requested in the github, Nico has added it
I’m not convinced this is correct - what are you basing this on, or what doesn’t work?
1 Like
╭─soumyaxgaruda@soumyas in ~ took 24s
╰─λ sudo nautilus
[sudo] password for soumyaxgaruda:
GSConnect: No translation file found for domain
<IntrospectionModule 'Nautilus' from '/usr/lib/girepository-1.0/Nautilus-3.0.typelib'>
Insync Nautilus Plugin
<class 'insync-nautilus-plugin.InsyncExtension'>
[Errno 2] No translation file found for domain: 'nautilus-pdf-tools'
[init insync plugin] <insync-nautilus-plugin.InsyncExtension object at 0x7f0606100ec0 (uninitialized at 0x(nil))>
Initializing nautilus-image-converter extension
(org.gnome.Nautilus:398267): dconf-WARNING **: 11:38:42.883: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=affbebbec2504fab88ffb995609bb000 --binary-syntax --close-stderr”: Child process exited with code 1
(org.gnome.Nautilus:398267): dconf-WARNING **: 11:38:42.883: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=affbebbec2504fab88ffb995609bb000 --binary-syntax --close-stderr”: Child process exited with code 1
Traceback (most recent call last):
File "/usr/share/nautilus-python/extensions/nautilus-gsconnect.py", line 81, in _init_async
proxy = proxy.new_for_bus_finish(res)
gi.repository.GLib.GError: g-spawn-exit-error-quark: Error spawning command line “dbus-launch --autolaunch=affbebbec2504fab88ffb995609bb000 --binary-syntax --close-stderr”: Child process exited with code 1 (1)
** (org.gnome.Nautilus:398267): WARNING **: 11:38:42.982: Unable to get contents of the bookmarks file: Error opening file /root/.gtk-bookmarks: No such file or directory
** (org.gnome.Nautilus:398267): CRITICAL **: 11:38:43.021: update_dbus_opened_locations: assertion 'dbus_object_path' failed
(org.gnome.Nautilus:398267): dconf-WARNING **: 11:38:43.021: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=affbebbec2504fab88ffb995609bb000 --binary-syntax --close-stderr”: Child process exited with code 1
(org.gnome.Nautilus:398267): dconf-WARNING **: 11:38:44.930: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=affbebbec2504fab88ffb995609bb000 --binary-syntax --close-stderr”: Child process exited with code 1
(org.gnome.Nautilus:398267): dconf-WARNING **: 11:38:44.930: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=affbebbec2504fab88ffb995609bb000 --binary-syntax --close-stderr”: Child process exited with code 1
(org.gnome.Nautilus:398267): dconf-WARNING **: 11:38:47.252: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=affbebbec2504fab88ffb995609bb000 --binary-syntax --close-stderr”: Child process exited with code 1
(org.gnome.Nautilus:398267): dconf-WARNING **: 11:38:47.253: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=affbebbec2504fab88ffb995609bb000 --binary-syntax --close-stderr”: Child process exited with code 1
(org.gnome.Nautilus:398267): dconf-WARNING **: 11:38:47.747: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=affbebbec2504fab88ffb995609bb000 --binary-syntax --close-stderr”: Child process exited with code 1
(org.gnome.Nautilus:398267): dconf-WARNING **: 11:38:47.747: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=affbebbec2504fab88ffb995609bb000 --binary-syntax --close-stderr”: Child process exited with code 1
(org.gnome.Nautilus:398267): dconf-WARNING **: 11:38:48.033: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=affbebbec2504fab88ffb995609bb000 --binary-syntax --close-stderr”: Child process exited with code 1
(org.gnome.Nautilus:398267): dconf-WARNING **: 11:38:48.033: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=affbebbec2504fab88ffb995609bb000 --binary-syntax --close-stderr”: Child process exited with code 1
Please read
Why are you running a GUI application directly with sudo? This will likely be why dbus-launch doesn’t work, as the session variables will be wrong.
This sort of situation is called an XY Problem - you have an initial problem X and you think Y might be a solution, but Y doesn’t work so you try to fix Y.
4 Likes
It works perfectly in wayland. When I use dconf editor same thing happens. And dconf editor is necessary to run from sudo to customize gdm.
Interesting... let me test sudo -u gdm dbus-launch as per https://wiki.archlinux.org/title/GDM#dconf_configuration
Edit: seems to work fine under Xorg - I changed the icon and cursor theme and enabled Night Light. 
The command dbus-launch is not necessary in wayland. But in xorg it needs. Every single time it is necessary to run apps as root user like gedit, dcof-editor etc. And if there is option to reduce stress on remembering comnands, why shall we not use it?
This is what pkexec is for?
2 Likes