Here is an ugly 3 steps workaround:

-1) Edit the org.gnome.Vino schema to restore the missing "enabled"
parameter (copying from 16.04)

sudo nano /usr/share/glib-2.0/schemas/org.gnome.Vino.gschema.xml

Add this key:
    <key name='enabled' type='b'>
      <summary>Enable remote access to the desktop</summary>
      <description>
        If true, allows remote access to the desktop via the RFB
        protocol. Users on remote machines may then connect to the
        desktop using a VNC viewer.
      </description>
      <default>false</default>
    </key>

-2) Compile the schemas for Gnome:

sudo glib-compile-schemas /usr/share/glib-2.0/schemas


-3) Now the screen sharing panel in unity-control-center works... but this is 
not enough to get vino running! So you need to add in the programs at session 
start: Vino-server with the following command line:

/usr/lib/vino/vino-server


Now you can VNC your 18.04-Unity!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1741027

Title:
  [FFE] screen sharing panels abort using an unexistant vino gsettings
  key

Status in unity-control-center package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed
Status in vino package in Ubuntu:
  Invalid

Bug description:
  [FFE]

  This happens because Gnome removed that particular gsettings key. The
  removal did not happen with the ui removal but rather much later than
  that. That is why it doesn't work with the latest version of vino.

  As of now If users try to open the new sharing panel, unity-control-
  center will crash. This sort behavior is not desired on LTS release
  (18.04).


  
  ------------
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-control-center.  This problem was most recently seen with package version 
15.04.0+17.10.20171225-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/be6d095e2145d77c79a6e47e17c94dfe70bcaa0a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  Specifically, the error report

   "Settings schema 'org.gnome.Vino' does not contain a key named
  'enabled' "

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to