[SOLVED]:vino-server fails in MX-32-bit due to missing gconf schema key: "draw-background=true" ;

[nickleke]

[SOLVED] [ thanks to "timkb4cq" ] : MX 21.1 32-bit installed on DELL desktop 2-cores @ 3.8GHz. ; RAM: 3GB ; Installed the MX-provided vino-server. Connection from remote to server is established and properly authenticated - but only for a split second ; At the server side the message pop-up occurs for the user (..with intent) to click "accept" connection. ( we use "prompt-enabled set to ON " ). However the pop-up message stays on-screen for 1 second. If the user hurriedly clicks onto "accept", then, connection is established & remote-access works perfectly. When the pop-up message window occurs, and more than 1 second elapses the pop-up disappears, and there after, connection fails and lost. When connection is lost, on the server terminal window where we launch vino, an error message occurs: Glib-Gio-error Schema org.gnome.desktop.background does not contain the key: "draw-background" ; It is strange of course that in one instant it works, and in another, it fail. Same error occurs when we turn-off the "prompt-enabled" switch.
I verified the schema via "gsettings list-recursively etc..." and I confirm that the key "draw-background" is not in the list. I also verified on another Linux 32-bit computer which has a good vino-server operation, and in fact the schema on this other installation did contain the key. So it looks like in MX 21.1 the vino-server is not "IN_STEP" with the org.gnome.desktop parameters. I would need some assistance from the MX-experts, to confirm the missing key in 21.1, and whether it might be available in either earlier or later releases of MX-32-bit. ?

Code: Select all

System:
  Kernel: 5.10.0-13-686-pae i686 bits: 32 compiler: gcc v: 10.2.1
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-13-686-pae
  root=UUID=<filter> ro vga=791 quiet
  video=1024x768 splash init=/lib/systemd/systemd init=/lib/systemd/systemd
  Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7
  dm: LightDM 1.26.0 Distro: MX-21.1_386 Wildflower April 9  2022
  base: Debian GNU/Linux 11 (bullseye)
Machine:
  Type: Desktop System: Dell product: Dimension 4600i v: N/A serial: <filter>
  Chassis: type: 6 serial: <filter>
  Mobo: Dell model: 0F4491 serial: <filter> BIOS: Dell v: A12 date: 08/26/2004
CPU:
  Info: Single Core model: Intel Pentium 4 bits: 32 type: MT
  arch: Netburst Prescott family: F (15) model-id: 3 stepping: 4 microcode: 17
  cache: L2: 1024 KiB
  flags: pae sse sse2 sse3 bogomips: 13565
  Speed: 3391 MHz min/max: N/A Core speeds (MHz): 1: 3391 2: 3391
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds
  status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1
  mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD RV535 [Radeon X1650 PRO] vendor: VISIONTEK driver: N/A
  alternate: radeon bus-ID: 01:00.0 chip-ID: 1002:71c1 class-ID: 0300
  Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.16.1 driver:
  loaded: vesa display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 800x600 s-dpi: 67 s-size: 303x231mm (11.9x9.1")
  s-diag: 381mm (15")
  Monitor-1: default res: 800x600
  OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.3.5
  compat-v: 3.1 direct render: Yes
Audio:
  Device-1: Intel 82801EB/ER AC97 Audio vendor: Dell driver: snd_intel8x0
  v: kernel bus-ID: 00:1f.5 chip-ID: 8086:24d5 class-ID: 0401
  Sound Server-1: ALSA v: k5.10.0-13-686-pae running: yes
  Sound Server-2: PulseAudio v: 14.2 running: yes
Network:
  Device-1: Intel 82562EZ 10/100 Ethernet vendor: Dell driver: e100 v: kernel
  port: cf40 bus-ID: 02:08.0 chip-ID: 8086:1050 class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 149.05 GiB used: 5.91 GiB (4.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD1600JS-60MHB1
  size: 149.05 GiB block-size: physical: 512 B logical: 512 B speed: <unknown>
  type: N/A serial: <filter> rev: 2E02 scheme: MBR
Partition:
  ID-1: / raw-size: 29.8 GiB size: 29.17 GiB (97.87%) used: 5.73 GiB (19.6%)
  fs: ext4 dev: /dev/sda2 maj-min: 8:2
  ID-2: /home raw-size: 114.09 GiB size: 111.74 GiB (97.94%)
  used: 184.4 MiB (0.2%) fs: ext4 dev: /dev/sda4 maj-min: 8:4
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 3.73 GiB used: 0 KiB (0.0%) priority: -2
  dev: /dev/sda3 maj-min: 8:3
Sensors:
  Message: No sensor data found. Is lm-sensors configured?
Repos:
  Packages: note: see --pkg apt: 1979 lib: 981 flatpak: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
  1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list
  1: deb http://deb.debian.org/debian bullseye main contrib non-free
  2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/mx.list
  1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
Info:
  Processes: 176 Uptime: 2h 37m wakeups: 0 Memory: 3.2 GiB
  used: 732.1 MiB (22.3%) Init: systemd v: 247 runlevel: 5 default: 5
  tool: systemctl Compilers: gcc: 10.2.1 alt: 10 Shell: bash
  default: Bash v: 5.1.4 running-in: quick-system-info-mx inxi: 3.3.06
Boot Mode: BIOS (legacy, CSM, MBR)

[Eadwine Rose]

Please post your Quick System Info, thanks

[dolphin_oracle]

I don't know how exactly, but you could use gsettings to add the missing key.

[timkb4cq]

MX uses debian as a base, and the vino package comes from the debian repositories. We don't build it.
There is a bug reported for the debian package that if draw-backround is set to false vino crashes. There has been no action on it.
The version in debian buster (MX-19's base) doesn't include that XML key either.
You didn't state what other Linux you used, but Vino is a Gnome program and the package from that distro may have the key in their schema file ( /usr/share/glib-2.0/schemas/org.gnome.Vino.gschema.xml )
I'm sure the missing key can be added to that file.

[nickleke]

Reply to dolphin_oracle:
Thanks a lot for the idea. Have you done such a tweak in past yourself ? According to the gsettings-man I did not see any functional command to allow us to add keys to existing gnome Schemas. Take a look . . .
https://developer-old.gnome.org/gio/sta ... -tool.html ;

[nickleke]

Reply to: timkb4cq ; Thanks for the info ; I wonder if MX-support in future 32-bit releases, it may include in the "background Schema" list, the key "draw-background=TRUE" ; . . . & instruct the user base not to tweak the background switch to OFF. Also, regarding the - - - Vino.gschema.xml file, this appears to construct the GUI dconf menu for vino settings and to support the vino-preferences command. The preceding XML makes no reference to the "draw-background" key. I suspect the calling for this old phased-out key is done by the vnc-server core software in the MX 21.1-32 bit DISTRO. It is possible also, that newer versions of vnc-server don't make a reference to this key any more. And also it is extremely likely that newer versions of Vino core software don't make use of this key either. So to resolve this for users of 32bit older systems, it becomes a question of the vnc-server version core software to be totally compatible with the DISTRO included vino server version. I just hope that this issue for 32 bit systems is resolved in new MX releases at the Installation level, or the MX-support team provides clearly documented work-arounds in their release notes.

[timkb4cq]

I do need to read more carefully

org.gnome.desktop.background does not contain the key: "draw-background"

That's not specific to Vino but to the Gnome desktop - which MX doesn't come with. Was your other 32bit Linux running Gnome? I suspect that's a setting the Gnome desktop adds in.

But while I was looking for the Vino source repository I came across this

Vino was the GNOME desktop sharing server. It is now archived and unmaintained - please use gnome-remote-desktop instead!

Just FYI

[timkb4cq]

After some research, here's how you can add the key. Copy /usr/share/glib2.0/schemas/org.gnome.desktop.background.gschema.xml somewhere safe just in case things go wrong when you edit it.
Now you will edit that file as root.
The end of that file looks like this:

Code: Select all

    <key name="show-desktop-icons" type="b">
      <default>false</default>
      <summary>Have file manager handle the desktop</summary>
      <description>
        If set to true, then file manager will draw the icons on the desktop.
      </description>
    </key>
  </schema>
</schemalist>

Add the key so it looks like this:

Code: Select all

    <key name="show-desktop-icons" type="b">
      <default>false</default>
      <summary>Have file manager handle the desktop</summary>
      <description>
        If set to true, then file manager will draw the icons on the desktop.
      </description>
    </key>
    <key name="draw-background" type="b">
      <default>true</default>
      <summary>Whether the background should be rendered</summary>
      <description>
        If set to true, the desktop background will be rendered.
      </description>
    </key>
  </schema>
</schemalist>

Save the file.
Open a terminal and cd /usr/share/glib-2.0/schemas
Then

Code: Select all

sudo glib-compile-schemas .

Yeah, they don't make it convenient, but it can be done - I just did it here.

[nickleke]

Reply to "timkb4cq": Thanks a lot for the tip: It worked !!. ( . . . I.E. adding a TEMPERED key in the "org.gnome.desktop,background.gschema.xml" : This thread which highlights a bug in MX-21.1-32Bit will now be marked =SOLVED= ;
One more little thing: I start the VINO manually, after PC boots: I enter command: "sudo /usr/lib/vino/vino-server &" thus remote-access works ; Can you offer me your opinion on how to start-up the VINO, automatically, when PC boots ?
Thanks a million for everything. Nick.

[timkb4cq]

Start -> Settings -> Session and Startup -> Application Autostart (tab) -> Add Is probably the easiest way to go about it.