Nemo: GLib-GIO-ERROR - 'org.nemo.preferences' does not contain a key named 'context-menus-show-all-actions'

Created on 8 Nov 2019  路  5Comments  路  Source: linuxmint/nemo

 * Nemo version (nemo --version)
   4.2.2
 * Is issue with desktop or windowed nemo?
   Both
 * Distribution - (Mint 17.2, Arch, Fedora 25, etc...)
   Mint 17.2
 * Graphics hardware *and* driver used
   NVIDIA GTX 1060, 435.21
 * 32 or 64 bit
   64 bit
 ```

**Issue**

After login, there are no symbols (folders, files) displayed on the Desktop.
Clicking the nemo tray icon or trying to open nemo via the start menu does not show any window.
Trying to open nemo via terminal results in the following error:

$ nemo .

(nemo:14409): Gtk-WARNING **: 20:15:43.629: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client

(nemo:14409): GLib-GIO-ERROR **: 20:15:44.297: Settings schema 'org.nemo.preferences' does not contain a key named 'context-menus-show-all-actions'
Trace/Breakpoint ausgel枚st (Speicherabzug geschrieben)

The corresponding file, however, does exist:

$ ls -l /usr/share/glib-2.0/schemas/org.nemo.gschema.xml
-rw-r--r-- 1 root root 41481 Nov 7 06:47 /usr/share/glib-2.0/schemas/org.nemo.gschema.xml

**Additional information**

$ uname -a
Linux ${HOSTNAME} 5.3.9-050309-generic #201911061337 SMP Wed Nov 6 13:39:34 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux


$ inxi -Fxxxz
System: Host: ${HOSTNAME} Kernel: 5.3.9-050309-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: Cinnamon 4.3.0
wm: muffin 4.2.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic
Machine: Type: Desktop System: ASUS product: All Series v: N/A serial:
Mobo: ASUSTeK model: Z97-P v: Rev X.0x serial: UEFI: American Megatrends v: 2907 date: 03/11/2016
CPU: Topology: Quad Core model: Intel Core i7-4790 bits: 64 type: MT MCP arch: Haswell rev: 3 L2 cache: 8192 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 58756
Speed: 3468 MHz min/max: 800/4000 MHz Core speeds (MHz): 1: 3468 2: 3468 3: 3468 4: 3468 5: 3470 6: 3469 7: 3469
8: 3475
Graphics: Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: Gigabyte driver: nvidia v: 435.21 bus ID: 01:00.0
chip ID: 10de:1c03
Display: x11 server: X.Org 1.19.6 driver: nvidia resolution: 1920x1080~60Hz, 2560x1440~60Hz
OpenGL: renderer: GeForce GTX 1060 6GB/PCIe/SSE2 v: 4.6.0 NVIDIA 435.21 direct render: Yes
Audio: Device-1: Intel 9 Series Family HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 00:1b.0
chip ID: 8086:8ca0
Device-2: NVIDIA GP106 High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 01:00.1
chip ID: 10de:10f1
Device-3: Conexant Systems CX23880/1/2/3 PCI Video and Audio Decoder vendor: Hauppauge works driver: cx8800
v: 1.0.0 bus ID: 05:01.0 chip ID: 14f1:8800
Device-4: Conexant Systems CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] vendor: Hauppauge works
driver: cx88_audio bus ID: 05:01.1 chip ID: 14f1:8811
Device-5: Conexant Systems CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] vendor: Hauppauge works
driver: cx88-mpeg driver manager bus ID: 05:01.2 chip ID: 14f1:8802
Sound Server: ALSA v: k5.3.9-050309-generic
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel port: d000
bus ID: 03:00.0 chip ID: 10ec:8168
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac:
Drives: Local Storage: total: 4.78 TiB used: 1.94 TiB (40.6%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB speed: 31.6 Gb/s lanes: 4
serial: rev: 2B2QEXE7 scheme: GPT
ID-2: /dev/sda vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB speed: 6.0 Gb/s serial: rev: 2B6Q
scheme: GPT
ID-3: /dev/sdb vendor: Seagate model: ST2000LX001-1RG174 size: 1.82 TiB speed: 6.0 Gb/s rotation: 5400 rpm
serial: rev: SDM1 scheme: GPT
ID-4: /dev/sdc vendor: Seagate model: ST2000LX001-1RG174 size: 1.82 TiB speed: 6.0 Gb/s rotation: 5400 rpm
serial: rev: SDM1 scheme: GPT
Partition: ID-1: / size: 49.09 GiB used: 35.34 GiB (72.0%) fs: ext4 dev: /dev/sda6
ID-2: /home size: 1.01 TiB used: 893.14 GiB (86.2%) fs: ext4 dev: /dev/sdc3
ID-3: swap-1 size: 4.77 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda7
Sensors: System Temperatures: cpu: 32.0 C mobo: N/A gpu: nvidia temp: 30 C
Fan Speeds (RPM): cpu: 0 gpu: nvidia fan: 0%
Info: Processes: 285 Uptime: 1h 08m Memory: 31.31 GiB used: 4.42 GiB (14.1%) Init: systemd v: 237 runlevel: 5 Compilers:
gcc: 7.4.0 alt: 5/6/7/8 clang: 6.0.0-1ubuntu2 Shell: bash v: 4.4.20 running in: gnome-terminal inxi: 3.0.32
```

All 5 comments

That key is removed in the current master branch - this is from the nemo-fileroller extension - it had been checking that key to determine whether or not to show one of its menu entries.

The extension is fixed in git (https://github.com/linuxmint/nemo-extensions), if you want to re-build it. Otherwise, uninstalling nemo-fileroller would resolve this also.

@mtwebster From the info posted he is running nemo stable not master and the key was only removed two days ago from nemo-extensions master.
Linux Mint 19.2 shouldn't have this code yet.

https://github.com/linuxmint/nemo-extensions/commit/0c7bbe6e43b69ffa194f61516f26b9fa928c0491

@leigh123linux reinstalling nemo didn't fix it. I'm running the daily builds (https://launchpad.net/~linuxmint-daily-build-team/+archive/ubuntu/daily-builds) though.
@mtwebster removing nemo-fileroller solved the issue - with all the caveats coming with that of course.

I agree though that even with the daily build ppa breaking code shouldn't be published.

Just install the fixed nemo-fileroller package: https://github.com/linuxmint/nemo-extensions/releases/tag/master.mint19

The daily ppa is not considered stable, things may unavoidably break at times. What should probably happen is that the extensions be published in that ppa alongside everything else.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

mdogancay picture mdogancay  路  3Comments

omartrigui picture omartrigui  路  7Comments

WhyNotHugo picture WhyNotHugo  路  6Comments

ngabor7 picture ngabor7  路  6Comments

DominicMe picture DominicMe  路  4Comments