You are not logged in.
when starting, "sudo nautilus" shows following messages on terminal
(nautilus:2128): Gtk-WARNING **: Theme parsing error: <broken file>:1:0: Failed to import: The resource at '/org/gnome/libgd/tagged-entry/default.css' does not exist
(nautilus:2128): dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=9d384f75f43841548d04cf9ca806aff8 --binary-syntax --close-stderr': Child process exited with code 1
(nautilus:2128): dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=9d384f75f43841548d04cf9ca806aff8 --binary-syntax --close-stderr': Child process exited with code 1
(nautilus:2128): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed
(nautilus:2128): dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=9d384f75f43841548d04cf9ca806aff8 --binary-syntax --close-stderr': Child process exited with code 1
when I press Ctrl+H it shows as following. The nautilus just blinks and doesn't show hidden file. the checkbox "Show Hidden Files" doesn't get checked.
(nautilus:2128): dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=9d384f75f43841548d04cf9ca806aff8 --binary-syntax --close-stderr': Child process exited with code 1
(nautilus:2128): dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=9d384f75f43841548d04cf9ca806aff8 --binary-syntax --close-stderr': Child process exited with code 1
I have no idea where these error messages come from. I'm temporarily using pcmanfm but I want to fix this problem eventually. Could someone give some help for me?
Last edited by freaxtux (2016-09-17 13:39:10)
Offline
I have a similar issue launching gksu gnome-terminal, the tip was to look at pam .pacnew, unfortunately, that did not help me (still lost inside pacnew complexities) and i must have missed what i needed to change, hope you have better luck!
Offline
Dbus has been compiled without X11 invocation, so you now have to explicitly start it with
gksu dbus-launch --exit-with-session nautilus
(or use gksudo which retains your user and environment and hence the running DBUS session)
EDIT: Added --exit-with-session to not leave a lingering dbus daemon
Last edited by V1del (2016-09-21 12:00:51)
Offline
Dbus has been compiled without X11 invocation, so you now have to explicitly start it with
gksu dbus-launch nautilus
(or use gksudo which retains your user and environment and hence the running DBUS session)
That works! thank you very much
Last edited by freaxtux (2016-09-17 13:40:15)
Offline
Dbus has been compiled without X11 invocation, so you now have to explicitly start it with
gksu dbus-launch --exit-with-session nautilus
(or use gksudo which retains your user and environment and hence the running DBUS session)
EDIT: Added --exit-with-session to not leave a lingering dbus daemon
How to use it with pkexec?
pkexec dbus-launch nautilus
Unable to init server: Could not connect: Connection refused
(nautilus:26687): Gtk-WARNING **: cannot open display:
pkexec used by this extension.
Offline