Cinnamon: Unable to run nemo (ver 3.8.6) as root

spsf64 · 2018-09-13 22:51:49

I have a fully updated system running cinnamon + latest nemo 3.8.6

If I try to "open as root" from gui nothing happens, from terminal I get these errors either with sudo or pkexec:

>> sudo nemo
[sudo] password for me: 

(nemo:4553): GLib-GIO-CRITICAL **: 18:42:27.489: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(nemo:4553): GLib-GIO-CRITICAL **: 18:42:27.489: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Segmentation fault


me on Thu Sep 13 at 06:42 PM in ~ 
>> pkexec nemo

(nemo:4572): GLib-GIO-CRITICAL **: 18:42:41.190: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(nemo:4572): GLib-GIO-CRITICAL **: 18:42:41.190: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Segmentation fault (core dumped)

.

Any suggestions?
TIA

edit: Temporary fix: downgrade gtk3 down to 3.22.30-1 (https://bbs.archlinux.org/viewtopic.php … 2#p1807532)

Last edited by spsf64 (2018-09-18 11:16:54)

jasonwryan · 2018-09-13 23:03:07

Don't run it as root. Don't use sudo to try and run as root.
https://wiki.archlinux.org/index.php/Ru … ns_as_root

Moving to NC...

spsf64 · 2018-09-13 23:17:15

@jasonryan, there is an option to run as root from the gui, and it works fine with the stable repos, I posted in testing forum because it does not work anymore...
Is this intentional?
I was collecting the coredump:

me on Thu Sep 13 at 07:06 PM in ~ 
>> coredumpctl info 2120
           PID: 2120 (nemo)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 11 (SEGV)
     Timestamp: Thu 2018-09-13 19:00:27 EDT (6min ago)
  Command Line: /usr/bin/nemo
    Executable: /usr/bin/nemo
 Control Group: /user.slice/user-1001.slice/user@1001.service/gnome-terminal-server.service
          Unit: user@1001.service
     User Unit: gnome-terminal-server.service
         Slice: user-1001.slice
     Owner UID: 1001 (me)
       Boot ID: 6
    Machine ID: b
      Hostname: me-pc
       Storage: /var/lib/systemd/coredump/core.nemo.0.622b7163daf14cc490f29a1d76dc6341.2120.1536879627000000.lz4 (inaccessible)
       Message: Process 2120 (nemo) of user 0 dumped core.
                
                Stack trace of thread 2120:
                #0  0x00007f119c2b7635 __strlen_avx2 (libc.so.6)
                #1  0x00007f119d084b04 g_strdup (libglib-2.0.so.0)
                #2  0x00007f119dcad7e2 n/a (libgtk-3.so.0)
                #3  0x00007f119ddf2c02 n/a (libgtk-3.so.0)
                #4  0x00007f119db2cd76 n/a (libgtk-3.so.0)
                #5  0x0000559c5c5342d3 n/a (nemo)
                #6  0x00007f119d1953d5 g_closure_invoke (libgobject-2.0.so.0)
                #7  0x00007f119d182348 n/a (libgobject-2.0.so.0)
                #8  0x00007f119d18601e g_signal_emit_valist (libgobject-2.0.so.0)
                #9  0x00007f119d186a80 g_signal_emit (libgobject-2.0.so.0)
                #10 0x00007f119d253a3f g_application_register (libgio-2.0.so.0)
                #11 0x0000559c5c5b3614 n/a (nemo)
                #12 0x00007f119d25474b g_application_run (libgio-2.0.so.0)
                #13 0x0000559c5c52c142 n/a (nemo)
                #14 0x00007f119c17c223 __libc_start_main (libc.so.6)
                #15 0x0000559c5c52c18e n/a (nemo)
                
                Stack trace of thread 2130:
                #0  0x00007f119c248bb1 __poll (libc.so.6)
                #1  0x00007f119d0afee0 n/a (libglib-2.0.so.0)
                #2  0x00007f119d0affce g_main_context_iteration (libglib-2.0.so.0)
                #3  0x00007f119d0b0022 n/a (libglib-2.0.so.0)
                #4  0x00007f119d0793eb n/a (libglib-2.0.so.0)
                #5  0x00007f119c323a9d start_thread (libpthread.so.0)
                #6  0x00007f119c253a43 __clone (libc.so.6)


me on Thu Sep 13 at 07:06 PM in ~ 
>> 
.

Last edited by spsf64 (2018-10-05 16:03:30)

jasonwryan · 2018-09-13 23:20:32

I was unaware that there was such an option. I'll move it back. Can you add the version to the title?

spsf64 · 2018-09-13 23:22:24

jasonwryan wrote:

I was unaware that there was such an option. I'll move it back. Can you add the version to the title?

Thank you!
edit: title edited

Last edited by spsf64 (2018-09-13 23:24:56)

eschwartz · 2018-09-14 03:55:08

If you downgrade gtk3 down to 3.22.30-1 in extra, then this works...

spsf64 · 2018-09-14 12:13:23

Eschwartz wrote:

If you downgrade gtk3 down to 3.22.30-1 in extra, then this works...

I will try and report back, thanks!

edit: works fine with gtk3 3.22.30 as you suggested!
Do you know if this a problem with gtk or nemo/cinnamon?

Last edited by spsf64 (2018-09-14 12:36:29)

eschwartz · 2018-09-14 16:29:00

I've uploaded debug-enabled builds of gtk3, glib2, and nemo to https://wiki.archlinux.org/index.php/Un … #eschwartz

Dump of core: https://pkgbuild.com/~eschwartz/nemo-sudo.core

                Stack trace of thread 24100:
                #0  0x00007f9ca8753b5a n/a (libc.so.6)
                #1  0x00007f9ca95e4b04 g_strdup (libglib-2.0.so.0)
                #2  0x00007f9caa20d7e2 get_portal_path (libgtk-3.so.0)
                #3  0x00007f9caa352c12 gtk_application_impl_dbus_startup (libgtk-3.so.0)
                #4  0x00007f9caa08cd76 gtk_application_startup (libgtk-3.so.0)
                #5  0x000055c9228d22d3 nemo_application_startup (nemo)
                #6  0x00007f9ca96f53d5 g_closure_invoke (libgobject-2.0.so.0)
                #7  0x00007f9ca96e2348 signal_emit_unlocked_R (libgobject-2.0.so.0)
                #8  0x00007f9ca96e601e g_signal_emit_valist (libgobject-2.0.so.0)
                #9  0x00007f9ca96e6a80 g_signal_emit (libgobject-2.0.so.0)
                #10 0x00007f9ca97b3a3f g_application_register (libgio-2.0.so.0)
                #11 0x000055c922951614 nemo_main_application_local_command_line (nemo)
                #12 0x00007f9ca97b474b g_application_run (libgio-2.0.so.0)
                #13 0x000055c9228ca142 main (nemo)
                #14 0x00007f9ca86de223 __libc_start_main (libc.so.6)
                #15 0x000055c9228ca18e _start (nemo)
                
                Stack trace of thread 24101:
                #0  0x00007f9ca87aac41 __poll (libc.so.6)
                #1  0x00007f9ca960fee0 g_main_context_poll (libglib-2.0.so.0)
                #2  0x00007f9ca960ffce g_main_context_iteration (libglib-2.0.so.0)
                #3  0x00007f9ca9610022 glib_worker_main (libglib-2.0.so.0)
                #4  0x00007f9ca95d93eb g_thread_proxy (libglib-2.0.so.0)
                #5  0x00007f9ca8885a9d n/a (libpthread.so.0)
                #6  0x00007f9ca87b5753 __clone (libc.so.6)

Last edited by eschwartz (2018-09-16 06:16:34)

loqs · 2018-09-14 19:38:14

Perhaps https://gitlab.gnome.org/GNOME/gtk/comm … ee6092c011 ?
Edit:
Oops arch already has that fix in the latest testing PKGBUILD

Last edited by loqs (2018-09-14 19:56:31)

spsf64 · 2018-09-15 10:21:51

@loqs, I tried the latest gtk3 from testing, does not work, same problem...

@Eschwartz, sorry, don't know what to do with these debug files... Can you guide me on this? Do you have the same problem with cinnamon/nemo? TIA

eschwartz · 2018-09-16 06:15:38

Those debug files are useful for using something like gdb to debug the cause of the error, or to reproduce the crash using debug builds of dependent libraries in order to get better coredumps.

They're a means to an end, not the end itself. Someone still needs to debug this.

...

Probably caused by https://gitlab.gnome.org/GNOME/gtk/blob … ate.c#L305 which does pointer arithmetic on something the docs say is permitted to return null. Probably a gtk bug, but nemo must be triggering it in some way the person who implemented this did not see.

Last edited by eschwartz (2018-09-16 06:23:12)

spsf64 · 2018-09-17 20:49:39

@Eschwartz, thank you for the explanation!

@jasonwryan, as the latest gtk3 has been moved to extra repo and the problem persists, can you move this topic to "Pacman & Package Upgrade Issues"?

V1del · 2018-09-18 07:08:45

Well the pacman upgrade worked correctly, moving to Apps & DEs

spsf64 · 2018-09-18 10:44:55

V1del wrote:

Well the pacman upgrade worked correctly, moving to Apps & DEs

Thanks!

spsf64 · 2018-09-20 21:00:08

Still trying to find a solution, I posted an issue at github for nemo developers (https://github.com/linuxmint/nemo/issues/1949) and it was quickly closed.
I think the developer suggests "it is not a problem with nemo"?? He says it works fine with latest GTK 3.24.1
The only solution suggested is to run "sudo dbus-launch --exit-with-session nemo" which does work, but only from terminal.
The context menu from GUI "Open as Root" still inoperative...
So, we have to wait for a new gtk3 release and check? Or this a problem with arch gtk3 packaging?

bullseye · 2018-09-22 19:30:35

dbus 1.12.10.2 may be doing this. Downgrading to dbus 1.12.10.1 brings back right click open as root and no errors in terminal.

sc44 · 2018-09-23 14:39:45

Thanks @bullseye.
The problem is this "--without-x" in the PKGBUILD. When you coment this out and compile dbus 1.12.10.2 new, than it goes.

bullseye · 2018-09-24 00:41:20

That works! Thanks @sc44

spsf64 · 2018-09-26 10:02:42

Wow, it works!
Thanks @sc44 and @bullseye, do you guys think it is a bug or a feature of dbus arch package?
Should this be reported as a bug?

@Eschwartz, any comments or suggestions?

V1del · 2018-09-26 11:00:02

No, this is intended behaviour. It has accidentally been reenabled with 1.12.10-1, and consequently disabled again. I'm also not entirely up to speed on the rationale on why it's disabled in the Arch package, however it is a potential security issue to silently start up root owned dbus sessions that other things you didn't intend to have access to could've access to. In general running entire GUI programs as root is considered unsafe and many better and controlled solutions have been/are being developed. I'm not sure if nemo has this ability as well, but if it uses gvfs it should technically be able to elevate only the actual file operations you intend to do using the admin://$fileurl protocol.

However the weird thing here is that a GTK up or downgrade has an effect on this.

Last edited by V1del (2018-09-26 11:06:50)

eschwartz · 2018-09-26 17:33:25

spsf64 wrote:

Wow, it works!
Thanks @sc44 and @bullseye, do you guys think it is a bug or a feature of dbus arch package?
Should this be reported as a bug?
@Eschwartz, any comments or suggestions?

It's definitely not a dbus bug. It may be a gtk3 or a nemo bug, as I mentioned before:

Eschwartz wrote:

Probably caused by https://gitlab.gnome.org/GNOME/gtk/blob … ate.c#L305 which does pointer arithmetic on something the docs say is permitted to return null. Probably a gtk bug, but nemo must be triggering it in some way the person who implemented this did not see.

Also regarding

V1del wrote:

In general running entire GUI programs as root is considered unsafe and many better and controlled solutions have been/are being developed. I'm not sure if nemo has this ability as well, but if it uses gvfs it should technically be able to elevate only the actual file operations you intend to do using the admin://$fileurl protocol.

Indeed it should and indeed it can. In fact, I don't really use nemo for root, since I use the CLI for that for the most part, but if/when I do, I use admin:// and that works great.

But, nemo offers the feature to run as root, so of course it's interesting and something to fix, if it fails to do as intended, in a non-segfaulty manner.

spsf64 · 2018-09-27 02:06:35

@V1del, @Eschartz and all posters, thanks for all explanations, but this thread escalated way beyond my technical knowledge...
If you think this must be closed, just do it or let me know.
I am just an arch / cinnamon enthusiast wanting all the features working!

Last edited by spsf64 (2018-09-27 02:51:47)

7314776 · 2018-09-27 20:19:36

As far as I understand, Nemo runs in full GUI (no terminal), as well as "Open as root" (by gksu) invoked by Nemo. Latest dbus doesn't "trust" full-GUI apps as they can steal root privileges for inappropriate purposes. Similar behavior is observed in Fedora (X11, don't know about Wayland) when local variables are changed. There are some rude modes of fixing that as "xhost +SI:localuser:root" and "xhost +SI:localuser:lightdm" in Cinnamon. So dbus, as a self defence, firewalls full-GUI apps not allowing them to elevate privileges. Probably, that is why "--without-x" works for making dbus, and gtk3 and/or nemo packages are not involved... Either we have to wait for dbus development, or make it using modified PKGBUILD - no answer here. The best way for me as I see it - using CLI when root is needed.
If this assumption is wrong, confusing or misleading, please, correct for others not to take it into consideration.

Arch Linux

#1 2018-09-13 22:51:49

Cinnamon: Unable to run nemo (ver 3.8.6) as root

#2 2018-09-13 23:03:07

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#3 2018-09-13 23:17:15

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#4 2018-09-13 23:20:32

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#5 2018-09-13 23:22:24

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#6 2018-09-14 03:55:08

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#7 2018-09-14 12:13:23

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#8 2018-09-14 16:29:00

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#9 2018-09-14 19:38:14

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#10 2018-09-15 10:21:51

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#11 2018-09-16 06:15:38

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#12 2018-09-17 20:49:39

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#13 2018-09-18 07:08:45

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#14 2018-09-18 10:44:55

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#15 2018-09-20 21:00:08

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#16 2018-09-22 19:30:35

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#17 2018-09-23 14:39:45

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#18 2018-09-24 00:41:20

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#19 2018-09-26 10:02:42

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#20 2018-09-26 11:00:02

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#21 2018-09-26 17:33:25

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#22 2018-09-27 02:06:35

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

#23 2018-09-27 20:19:36

Re: Cinnamon: Unable to run nemo (ver 3.8.6) as root

Board footer