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.9 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.15.0-118-generic x86_64 Ubuntu Current Operating System: Linux ubuntu 5.8.0-25-generic #26-Ubuntu SMP Thu Oct 15 10:30:38 UTC 2020 x86_64 Kernel command line: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- Build Date: 07 October 2020 05:46:52AM xorg-server 2:1.20.9-2ubuntu1 (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: Fri Nov 27 19:39:48 2020 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (II) modeset(0): Initializing kms color map for depth 24, 8 bpc. ubiquity-dm: set vars ubiquity-dm: pam_open_session ubiquity-dm: dm-scripts 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” (gsd-a11y-settings:2178): a11y-settings-plugin-WARNING **: 19:39:51.729: Unable to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ubiquity-dm: start greeter (gsd-xsettings:2187): xsettings-plugin-WARNING **: 19:39:52.844: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist (gsd-keyboard:2179): keyboard-plugin-WARNING **: 19:39:53.432: Unable to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files (gsd-power:2184): power-plugin-WARNING **: 19:39:53.678: Unable to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files (gsd-media-keys:2180): media-keys-plugin-WARNING **: 19:39:53.731: Unable to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files (gsd-xsettings:2187): xsettings-plugin-WARNING **: 19:39:54.193: Unable to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files (gsd-media-keys:2180): media-keys-plugin-WARNING **: 19:39:54.931: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell (gsd-media-keys:2180): media-keys-plugin-WARNING **: 19:39:55.942: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell (gnome-shell:2188): Gjs-WARNING **: 19:39:56.023: Some code accessed the property 'CredentialManager' on the module 'credentialManager'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. GNOME Shell-Message: 19:39:56.124: Skipping parental controls support as it’s disabled ibus-m17n-Message: 19:39:56.837: skipped m17n:ko:romaja since its rank is lower than 0 ibus-m17n-Message: 19:39:56.837: skipped m17n:ko:han2 since its rank is lower than 0 ibus-m17n-Message: 19:39:56.837: skipped m17n:lo:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.839: skipped m17n:my:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.841: skipped m17n:ru:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.842: skipped m17n:sk:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.842: skipped m17n:sr:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.845: skipped m17n:ug:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.845: skipped m17n:uk:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.845: skipped m17n:uz:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.846: skipped m17n:zh:py since its rank is lower than 0 ibus-m17n-Message: 19:39:56.847: skipped m17n:ar:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.848: skipped m17n:be:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.849: skipped m17n:cmc:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.849: skipped m17n:cs:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.849: skipped m17n:el:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.851: skipped m17n:he:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.851: skipped m17n:hr:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.852: skipped m17n:hy:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.852: skipped m17n:ka:kbd since its rank is lower than 0 ibus-m17n-Message: 19:39:56.852: skipped m17n:kk:kbd since its rank is lower than 0 (gsd-media-keys:2180): media-keys-plugin-WARNING **: 19:39:56.949: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell (gsd-media-keys:2180): media-keys-plugin-WARNING **: 19:39:57.956: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell GNOME Shell-Message: 19:39:58.806: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation (gsd-media-keys:2180): media-keys-plugin-WARNING **: 19:39:59.069: Failed to grab accelerator for keybinding settings:playback-random (gsd-media-keys:2180): media-keys-plugin-WARNING **: 19:39:59.069: Failed to grab accelerator for keybinding settings:rfkill (gsd-media-keys:2180): media-keys-plugin-WARNING **: 19:39:59.069: Failed to grab accelerator for keybinding settings:rotate-video-lock (gsd-media-keys:2180): media-keys-plugin-WARNING **: 19:39:59.069: Failed to grab accelerator for keybinding settings:playback-repeat (gsd-media-keys:2180): media-keys-plugin-WARNING **: 19:39:59.069: Failed to grab accelerator for keybinding settings:hibernate GNOME Shell-Message: 19:40:00.014: GNOME Shell started at Fri Nov 27 2020 19:39:57 GMT+0000 (UTC) GNOME Shell-Message: 19:40:00.016: Registering session with GDM GNOME Shell-Message: 19:40:00.040: Error registering session with GDM: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.DisplayManager was not provided by any .service files ubiquity-dm: greeter exited with code 0 No such schema “org.gnome.metacity” (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.179: JS ERROR: TypeError: actor.get_meta_window() is null _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1616:32 onStopped@resource:///org/gnome/shell/ui/windowManager.js:1586:39 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:82:22 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:165:64 (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.207: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.207: The offending signal was notify on NMDeviceEthernet 0x5581a078a200. == Stack trace for context 0x55819e3652d0 == (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.207: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.207: The offending signal was notify on NMDeviceWifi 0x5581a078c250. == Stack trace for context 0x55819e3652d0 == (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.207: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.207: The offending signal was notify on NMDeviceEthernet 0x5581a078a440. == Stack trace for context 0x55819e3652d0 == (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.207: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.207: The offending signal was notify on NMActiveConnection 0x55819f305180. == Stack trace for context 0x55819e3652d0 == (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.207: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.207: The offending signal was notify on NMActiveConnection 0x55819f305180. == Stack trace for context 0x55819e3652d0 == (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.207: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.207: The offending signal was state-changed on NMDeviceEthernet 0x5581a078a200. == Stack trace for context 0x55819e3652d0 == (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.207: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.207: The offending signal was state-changed on NMDeviceWifi 0x5581a078c250. == Stack trace for context 0x55819e3652d0 == (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.207: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell:2188): Gjs-CRITICAL **: 19:43:54.207: The offending signal was state-changed on NMDeviceEthernet 0x5581a078a440. == Stack trace for context 0x55819e3652d0 == (ibus-daemon:2412): GLib-WARNING **: 19:43:54.326: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). See the documentation of g_child_watch_source_new() for possible causes. (ibus-daemon:2412): GLib-WARNING **: 19:43:54.326: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). See the documentation of g_child_watch_source_new() for possible causes. (II) Server terminated successfully (0). Closing log file. ubiquity-dm: set_locale Generating locales (this might take a while)... en_US.UTF-8... done Generation complete. ubiquity-dm: Exiting with code 0