Nemo error: unresponsive while running with sudo (-or elevated privileges)

Support Software & Applications
1

Hello dear friends.
Manjaro Cinnamon is my main system.
Nemo behaves weird or unresponsive witj elevated priviliges or with sudo.
This is the error message I receive.
Any suggestions?
Thanks in advance.

[oz@oz-vpcsa ~]$ sudo nemo
[sudo] password for oz:

(nemo:9968): GLib-GIO-CRITICAL **: 13:48:45.961: g_dbus_interface_skeleton_export: assertion ‘G_IS_DBUS_CONNECTION (connection)’ failed
Initializing nemo-dropbox

(nemo:9968): dconf-WARNING **: 13:48:46.071: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=f66f43bd155e4e299f56414293eefd5c --binary-syntax --close-stderr”: Child process exited with code 1
ERROR SET META:15 Setting attribute metadata::nemo-icon-view-auto-layout not supported

2

Hi @cevad,

While I don’t really know what the problem could be, I have to point out that it could be because you’re trying to run a GUI application as root, which is not recommended. So my question is, why do you do it?

I see some mention of dropboox:

So it could be related to that. In some way.

Also, it could be that when running it with sudo, it is looking for something that it can’t find. Not sure.

1 Like
3

@Mirdarthos It’s fine to run Nemo as root for file and folder operations inside of the root folder. I the Plasma desktop and I always install Nemo just for this purpose. I for one am not editing something in Konsole that I can edit in Kate or Visual Code Studio. @cevad is that everything you get when you attempt to run Nemo as root?

1 Like
4

Well, then I might be in the minority, but I don’t think so. But to each his own, I guess.

Peace, brotha!

2 Likes
5

@Mirdarthos @Locutus thank you for your help.

During daily operations I don’t use neo from terminal. I just run it as root from dektop (cinnammon environment).
I experienced some weird behaviour lately when İ do this. To be able to see the problem in detail, I tried terminal.
Most basic problem is: I can’t edit preferences in Nemo while elevated privileges.
And disabling all extensions/plugins (-including nemo-dropbox) didn’t make any difference.

6

Well, then I’m out of ideas. Sorry.

7

To be more clear.
Nemo works normal while I am user. The problem occurs when I am root.

8

Thanks for your time.

1 Like
9

@Locutus Nemo starts, allows me to execute basic file operations but not letting me to change any option in preferences.

10

as Mirdarthos said do not use sudo instead use:

pkexec nemo
2 Likes
11

@manyaro01 thank you for your suggestion.
Unfortunately I got the same exact error again.

[oz@oz-vpcsa ~]$ pkexec nemo

(nemo:20074): GLib-GIO-CRITICAL **: 15:27:00.935: g_dbus_interface_skeleton_export: assertion ‘G_IS_DBUS_CONNECTION (connection)’ failed
Initializing nemo-dropbox

(nemo:20074): dconf-WARNING **: 15:27:01.045: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=f66f43bd155e4e299f56414293eefd5c --binary-syntax --close-stderr”: Child process exited with code 1
ERROR SET META:15 Setting attribute metadata::nemo-icon-view-auto-layout not supported

12

If you look at /usr/share/polkit-1/actions/org.nemo.root.policy you will see that you already can as user to open Nemo as “Root” from the context menu of Nemo.

You can ignore those.

pkexec nemo
should open the authentication dialog and then see this notification in Nemo after you entered your password

image
image782×272 15.1 KB

1 Like
13

@anon89812132 thanks a lot.
How can I solve the problem; (can’t edit preferences during elevated privileges)?
This problem is not valid for my other 4 manjaro laptops. Only 1 computer suffers.
All the best.

14

My guess, wrong permissions on your home directory on that particular install.

1 Like