Gtk nags when launching nemo from Gnome terminal (LM 19.3 Tricia)

[sour_captain]

[UPDATED], see below

This is a common use-case for me. It does not block me from using Nemo, but it is rather annoying and needlessly clutters the terminal. If it were only the one error message, I would ignore it, but every time I perform any kind of action in Nemo, the nag message repeats and fills the entire terminal. I'm sure I'm not the only one to run into this issue but I searched the web and forums for anything similar but couldn't find it.

Here's the message:

Code: Select all

% nemo .

(nemo:7661): Gtk-WARNING **: 10:28:37.363: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Nemo-Share-Message: 10:28:37.734: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
Please ask your system administrator to enable user sharing.

System info:

Code: Select all

% inxi -Fxxxrz
System:    Host: desktop6 Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 
           wm: muffin 4.4.4 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic 
Machine:   Type: Desktop Mobo: ASRock BIOS: American Megatrends
           date: 12/01/2020 
Battery:   Device-1: hidpp_battery_0 model: Wireless Mouse serial: charge: 55% 
           Device-2: hidpp_battery_1 model: Wireless Keyboard serial: charge: 55% 
CPU:       Topology: AMD Ryzen 64
           Speed: 2194 MHz min/max: 2200/3500 MHz boost: enabled Core speeds (MHz): 1: 2199 2: 2199 3: 2200 4: 2200 
           5: 2195 6: 2198 7: 2196 8: 2197
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] 
           vendor: ASUSTeK driver: amdgpu v: kernel bus ID: 0e:00.0
           Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa 
           resolution: 3840x2160~30Hz, 3840x2160~30Hz 
           OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.35.0 5.4.0-58-generic LLVM 10.0.0) 
           v: 4.6 Mesa 20.0.8 direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 580] vendor: ASUSTeK 
           Device-2: Advanced Micro Devices [AMD] vendor: ASRock driver: snd_hda_intel v: kernel
           Sound Server: ALSA
Partition: ID-1: / size: 208.56 GiB used: 99.04 GiB (47.5%) fs: ext4
           ID-2: swap-1 size: 18.62 GiB used: 200 KiB (0.0%) fs: swap
Sensors:   System Temperatures: cpu: 49.4 C mobo: N/A 
           Fan Speeds (RPM): N/A gpu: fan: 1102 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/inkscape_dev-stable-0_92-bionic.list 
           1: deb http://ppa.launchpad.net/inkscape.dev/stable-0.92/ubuntu bionic main
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb http://packages.linuxmint.com tricia main upstream import backport #id:linuxmint_main
           2: deb http://archive.ubuntu.com/ubuntu bionic main restricted universe multiverse
           3: deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse
           4: deb http://archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
           5: deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
           6: deb http://archive.canonical.com/ubuntu/ bionic partner
Info:      Processes: 602 Uptime: 20d 17h 36m Memory: used: 8.08 GiB Init: systemd v: 237 
           runlevel: 5 Compilers: gcc: 7.5.0 alt: 7 Shell: bash v: 4.4.20 running in: gnome-terminal inxi: 3.0.32 

Any hints / hacks / etc appreciated. Really, all I need is to make that error message stop appearing, I don't necessarily care about getting a root-cause or fixing anything. Thanks!

[spamegg]

Warnings are extremely common in a lot of programs. The devs do not perfectly adhere to the standards of the APIs/frameworks they use, and 99% of the time the warnings do not pose any functional issues. They can usually be safely ignored. Even the devs ignore them!

Code: Select all

Please ask your system administrator to enable user sharing.

Maybe look into this and enable user sharing, whatever that means?

[sour_captain]

Warnings are extremely common in a lot of programs. The devs do not perfectly adhere to the standards of the APIs/frameworks they use, and 99% of the time the warnings do not pose any functional issues. They can usually be safely ignored. Even the devs ignore them!

Code: Select all

Please ask your system administrator to enable user sharing.

Maybe look into this and enable user sharing, whatever that means?

Yeah, that's the part where I'm kind of needing help. I tried searching that too and got a bunch of nonsense about shared folders in the home directory. *sigh -- what the heck does launching Nemo have anything to do with Samba anyway? There are no Windows drives or network drives on my machine so the warning/error message makes no sense to me. As is usually the case...

[sour_captain]

OK, to get rid of the "net usershare info" Samba error, I just went ahead and created the directory it's complaining about because I can't see how it would hurt anything. That did clear up the error, however, the Gtk nag is still there and I also have a whole bunch of Python vomit whenever I change directories in Nemo:

Code: Select all

% nemo .

(nemo:21529): Gtk-WARNING **: 14:24:33.792: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Traceback (most recent call last):
  File "/usr/share/nemo-python/extensions/nemo-folder-color-switcher.py", line 547, in get_file_items
    supported_colors = self.theme.get_supported_colors(directories)
  File "/usr/share/nemo-python/extensions/nemo-folder-color-switcher.py", line 394, in get_supported_colors
    icon_path = self.find_folder_icon(color, directory)
  File "/usr/share/nemo-python/extensions/nemo-folder-color-switcher.py", line 373, in find_folder_icon
    relevant_ancestor = self.get_ancestor_defining_folder_svg(directory)
  File "/usr/share/nemo-python/extensions/nemo-folder-color-switcher.py", line 352, in get_ancestor_defining_folder_svg
    if self.has_icon_for_folder(directory):
  File "/usr/share/nemo-python/extensions/nemo-folder-color-switcher.py", line 328, in has_icon_for_folder
    return self.get_folder_icon_path(directory) is not None
  File "/usr/share/nemo-python/extensions/nemo-folder-color-switcher.py", line 319, in get_folder_icon_path
    self.discover_image_support(icon_size)
  File "/usr/share/nemo-python/extensions/nemo-folder-color-switcher.py", line 194, in discover_image_support
    path = os.path.join(self.base_path, self.supported_icon_sizes[icon_size][1], self.KNOWN_DIRECTORIES[key] + ext)
KeyError: 128

Great... now I get to go muck-diving in Python code... *sigh

[sour_captain]

A workaround just struck me which I will implement immediately. It works, so documenting here in case anyone else runs into this. Edit your .bashrc:

Code: Select all

nemox(){
    nemo $1 2> /dev/null
}

... or if you only ever open pwd:

Code: Select all

alias nemo='nemo 2> /dev/null'

Big-hammer solves the problem, ROFL...

[mikeflan]

What are you doing to launch Nemo?
I see this in one of your posts:
% nemo .
When I do that I get:

Code: Select all

$ % nemo .
-bash: fg: %: no such job

What I normally do to launch nemo is this:

Code: Select all

nemo '/home/mike/Documents' &

When I do that nemo launches without any errors and the terminal says this:

Code: Select all

$ nemo '/home/mike/Documents' &
[1] 21645
$

and it return to a prompt in the terminal, which is real nice.