ubiquity-dm: starting ubiquity-dm: plymouth ubiquity-dm: start X ['X', '-br', '-ac', '-noreset', '-nolisten', 'tcp', '-background', 'none', 'vt1', ':0'] X.Org X Server 1.20.7 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-173-generic x86_64 Ubuntu Current Operating System: Linux ubuntu 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 Kernel command line: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash --- Build Date: 08 February 2020 11:21:37AM xorg-server 2:1.20.7-2ubuntu2 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.38.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 15 18:02:23 2020 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (II) modeset(0): Initializing kms color map for depth 24, 8 bpc. The XKEYBOARD keymap compiler (xkbcomp) reports: > Internal error: Could not resolve keysym XF86MonBrightnessCycle > Internal error: Could not resolve keysym XF86RotationLockToggle > Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server ubiquity-dm: set vars ubiquity-dm: pam_open_session ubiquity-dm: dm-scripts ubiquity-dm: dconf-service ubiquity-dm: start frontend gtk_ui dbus-update-activation-environment: setting XDG_CURRENT_DESKTOP=ubuntu:GNOME dbus-update-activation-environment: setting DISPLAY=:0 No such schema “org.gnome.metacity” ubiquity-dm: start greeter (gnome-shell:1934): Clutter-CRITICAL **: 18:02:26.414: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed (gnome-shell:1934): Clutter-CRITICAL **: 18:02:26.414: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed dbus-daemon[1939]: Activating service name='org.a11y.atspi.Registry' requested by ':1.1' (uid=0 pid=1945 comm="/usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --" label="unconfined") dbus-daemon[1939]: Successfully activated service 'org.a11y.atspi.Registry' SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry ibus-m17n-Message: 18:02:27.539: skipped m17n:ko:romaja since its rank is lower than 0 ibus-m17n-Message: 18:02:27.539: skipped m17n:ko:han2 since its rank is lower than 0 ibus-m17n-Message: 18:02:27.539: skipped m17n:lo:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.540: skipped m17n:my:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.542: skipped m17n:ru:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.543: skipped m17n:sk:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.543: skipped m17n:sr:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.545: skipped m17n:ug:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.545: skipped m17n:uk:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.545: skipped m17n:uz:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.546: skipped m17n:zh:py since its rank is lower than 0 ibus-m17n-Message: 18:02:27.546: skipped m17n:ar:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.547: skipped m17n:be:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.548: skipped m17n:cmc:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.548: skipped m17n:cs:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.548: skipped m17n:el:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.549: skipped m17n:he:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.549: skipped m17n:hr:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.550: skipped m17n:hy:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.550: skipped m17n:ka:kbd since its rank is lower than 0 ibus-m17n-Message: 18:02:27.550: skipped m17n:kk:kbd since its rank is lower than 0 The XKEYBOARD keymap compiler (xkbcomp) reports: > Internal error: Could not resolve keysym XF86MonBrightnessCycle > Internal error: Could not resolve keysym XF86RotationLockToggle > Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server Gjs-Message: 18:02:28.390: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 24]: reference to undefined property "MetaWindowX11" The XKEYBOARD keymap compiler (xkbcomp) reports: > Internal error: Could not resolve keysym XF86MonBrightnessCycle > Internal error: Could not resolve keysym XF86RotationLockToggle > Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: > Internal error: Could not resolve keysym XF86MonBrightnessCycle > Internal error: Could not resolve keysym XF86RotationLockToggle > Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: > Internal error: Could not resolve keysym XF86MonBrightnessCycle > Internal error: Could not resolve keysym XF86RotationLockToggle > Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: > Internal error: Could not resolve keysym XF86MonBrightnessCycle > Internal error: Could not resolve keysym XF86RotationLockToggle > Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: > Internal error: Could not resolve keysym XF86MonBrightnessCycle > Internal error: Could not resolve keysym XF86RotationLockToggle > Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: > Internal error: Could not resolve keysym XF86MonBrightnessCycle > Internal error: Could not resolve keysym XF86RotationLockToggle > Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: > Internal error: Could not resolve keysym XF86MonBrightnessCycle > Internal error: Could not resolve keysym XF86RotationLockToggle > Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: > Internal error: Could not resolve keysym XF86MonBrightnessCycle > Internal error: Could not resolve keysym XF86RotationLockToggle > Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: > Internal error: Could not resolve keysym XF86MonBrightnessCycle > Internal error: Could not resolve keysym XF86RotationLockToggle > Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server (gnome-shell:1934): Clutter-CRITICAL **: 18:02:29.662: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed (gnome-shell:1934): Clutter-CRITICAL **: 18:02:29.662: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed (gnome-shell:1934): mutter-CRITICAL **: 18:02:29.667: meta_input_settings_get_tablet_wacom_device: assertion 'info != NULL' failed (gnome-shell:1934): mutter-CRITICAL **: 18:02:29.668: meta_input_settings_get_tablet_wacom_device: assertion 'info != NULL' failed (gnome-shell:1934): Bluetooth-WARNING **: 18:02:29.762: Error setting property 'Powered' on interface org.bluez.Adapter1: GDBus.Error:org.bluez.Error.Blocked: Blocked through rfkill (g-io-error-quark, 36) (gnome-shell:1934): Gjs-WARNING **: 18:02:29.762: JS ERROR: TypeError: this._slider.block_signal_handler is not a function _changeSlider@resource:///org/gnome/shell/ui/status/brightness.js:60:9 _sync@resource:///org/gnome/shell/ui/status/brightness.js:69:13 _init/this._proxy<@resource:///org/gnome/shell/ui/status/brightness.js:30:47 _makeProxyWrapper/ Internal error: Could not resolve keysym XF86MonBrightnessCycle > Internal error: Could not resolve keysym XF86RotationLockToggle > Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: > Internal error: Could not resolve keysym XF86MonBrightnessCycle > Internal error: Could not resolve keysym XF86RotationLockToggle > Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server