XRDP Gnome issues on 18.04

XRDP login crashes when I am trying to fix this colord infamous bug with the below setting. In file org.freedesktop.color.policy I edit <action id="org.freedesktop.color-manager.create-device"> like this
<defaults>
  <allow_any>yes</allow_any>
  <allow_inactive>yes</allow_inactive>
  <allow_active>yes</allow_active>
 </defaults>

When I return <allow_any> setting to auth_admin I get colord password prompt again but at least no fatal error and login kick-out.
Here is what in logs:
May  4 00:43:56 zimus systemd[839]: Started Evolution calendar service.
May  4 00:43:57 zimus gnome-shell[912]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.impl.portal.PermissionStore was not provided by any .service files
May  4 00:43:57 zimus dbus-daemon[859]: [session uid=1000 pid=859] Activating service name='ca.desrt.dconf' requested by ':1.70' (uid=1000 pid=1169 comm="/usr/lib/evolution/evolution-calendar-factory-subp" label="unconfined")
May  4 00:43:57 zimus dbus-daemon[859]: [session uid=1000 pid=859] Successfully activated service 'ca.desrt.dconf'
May  4 00:43:57 zimus dbus-daemon[859]: [session uid=1000 pid=859] Activating via systemd: service name='org.gnome.evolution.dataserver.AddressBook9' unit='evolution-addressbook-factory.service' requested by ':1.70' (uid=1000 pid=1169 comm="/usr/lib/evolution/evolution-calendar-factory-subp" label="unconfined")
May  4 00:43:57 zimus systemd[839]: Starting Evolution address book service...
May  4 00:43:57 zimus kerneloops-appl[1141]: Failed to load module "canberra-gtk-module"
May  4 00:43:57 zimus dbus-daemon[859]: [session uid=1000 pid=859] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook9'
May  4 00:43:57 zimus systemd[839]: Started Evolution address book service.
May  4 00:43:58 zimus gsd-color[1077]: failed to get edid: unable to get EDID for output
May  4 00:43:58 zimus colord[1129]: failed to get seat for session c1 [pid 1077]: No data available
May  4 00:43:59 zimus gsd-color[1077]: unable to get EDID for xrandr-rdp0: unable to get EDID for output
May  4 00:43:59 zimus kernel: [   57.913920] do_trap: 20 callbacks suppressed
May  4 00:43:59 zimus kernel: [   57.913922] traps: gsd-color[1077] trap divide error ip:55b8a93f194a sp:7ffc6561ccf0 error:0 in gsd-color[55b8a93e8000+12000]
May  4 00:43:59 zimus gnome-session[856]: gnome-session-binary[856]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' killed by signal 8
May  4 00:43:59 zimus gnome-session-binary[856]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' killed by signal 8
May  4 00:44:00 zimus gsd-color[1219]: failed to get edid: unable to get EDID for output
May  4 00:44:00 zimus colord[1129]: failed to get seat for session c1 [pid 1219]: No data available
May  4 00:44:00 zimus gsd-color[1219]: unable to get EDID for xrandr-rdp0: unable to get EDID for output
May  4 00:44:00 zimus kernel: [   59.272298] traps: gsd-color[1219] trap divide error ip:55cd2150094a sp:7fff2d2d55b0 error:0 in gsd-color[55cd214f7000+12000]
May  4 00:44:00 zimus gnome-shell[912]: Could not get current seat: No data available
May  4 00:44:00 zimus gnome-session[856]: gnome-session-binary[856]: WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' respawning too quickly
May  4 00:44:00 zimus gnome-session-binary[856]: WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' respawning too quickly
May  4 00:44:00 zimus gnome-session-binary[856]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
May  4 00:44:00 zimus gnome-session[856]: gnome-session-binary[856]: CRITICAL: We failed, but the fail whale is dead. Sorry....
May  4 00:44:00 zimus gnome-session-binary[856]: CRITICAL: We failed, but the fail whale is dead. Sorry....
May  4 00:44:00 zimus xrdp-sesman[838]: (838)(140268754420800)[CORE ] window manager (pid 851) did exit, cleaning up session
May  4 00:44:00 zimus xrdp-sesman[838]: (838)(140268754420800)[INFO ] calling auth_stop_session and auth_end from pid 838
May  4 00:44:00 zimus xrdp-sesman[838]: (838)(140268754420800)[DEBUG] cleanup_sockets:
May  4 00:44:00 zimus xrdp-sesman[838]: (838)(140268754420800)[DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdp_chansrv_audio_out_socket_10
May  4 00:44:00 zimus xrdp-sesman[838]: (838)(140268754420800)[DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdp_chansrv_audio_in_socket_10
May  4 00:44:00 zimus xrdp-sesman[838]: (838)(140268754420800)[DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdpapi_10
May  4 00:44:00 zimus xrdp-sesman[617]: (617)(140268754420800)[INFO ] ++ terminated session:  username xoob, display :10.0, session_pid 838, ip <IP_ADDRESS>:4237 - socket: 12
May  4 00:44:00 zimus xrdp[836]: (836)(140685308189952)[DEBUG] Closed socket 26 (AF_UNIX)
May  4 00:44:01 zimus gnome-shell[912]: gnome-shell: Fatal IO error 0 (Success) on X server :10.0.
May  4 00:44:01 zimus gsd-power[1036]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
May  4 00:44:01 zimus gsd-xsettings[1056]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
May  4 00:44:01 zimus gsd-wacom[1061]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
May  4 00:44:01 zimus gsd-clipboard[1075]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
May  4 00:44:01 zimus gsd-keyboard[1083]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
May  4 00:44:01 zimus gsd-media-keys[1086]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
May  4 00:44:01 zimus kerneloops-applet.desktop[1141]: kerneloops-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
May  4 00:44:01 zimus xrdp[836]: (836)(140685308189952)[DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:7777)
May  4 00:44:01 zimus xrdp[836]: (836)(140685308189952)[DEBUG] xrdp_mm_module_cleanup
May  4 00:44:01 zimus xrdp[836]: (836)(140685308189952)[DEBUG] Closed socket 25 (AF_UNIX)
May  4 00:44:01 zimus pulseaudio[1240]: [pulseaudio] client-conf-x11.c: xcb_connection_has_error() returned true
May  4 00:44:01 zimus pulseaudio[1245]: [pulseaudio] pid.c: Stale PID file, overwriting.
May  4 00:44:03 zimus gnome-software[1144]: plugin appstream took 6.0 seconds to do setup
May  4 00:44:03 zimus gnome-software[1144]: enabled plugins: packagekit-upgrade, packagekit-local, packagekit, packagekit-url-to-app, ubuntuone, desktop-categories, packagekit-offline, shell-extensions, packagekit-refresh, fwupd, os-release, packagekit-refine-repos, packagekit-proxy, systemd-updates, appstream, hardcoded-featured, hardcoded-popular, modalias, rewrite-resource, steam, desktop-menu-path, ubuntu-reviews, packagekit-refine, hardcoded-blacklist, generic-updates, packagekit-history, provenance, snap, icons, provenance-license, key-colors, key-colors-metadata
May  4 00:44:03 zimus gnome-software[1144]: disabled plugins: dpkg, repos, dummy, odrs, epiphany

How to fix it?

I wanna add that this crash occurs not only when I explicitly allow action in policy but also when I leave default auth_admin policy and simply enter password manually. Result is the same - fatal error and crash.
Here are key log lines:

May  6 11:46:55 zimus kernel: [  116.602287] traps: gsd-color[1071] trap divide error ip:55e3474a894a sp:7ffe943c05b0 error:0 in gsd-color[55e34749f000+12000]
May  6 11:46:56 zimus gnome-session[857]: gnome-session-binary[857]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' killed by signal 8
May  6 11:46:56 zimus gnome-session-binary[857]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' killed by signal 8
May  6 11:46:56 zimus gsd-color[1266]: failed to get edid: unable to get EDID for output
May  6 11:46:57 zimus PackageKit: search-file transaction /284_eeeceace from uid 1000 finished with success after 2458ms
May  6 11:46:58 zimus PackageKit: search-file transaction /285_deacbcca from uid 1000 finished with success after 673ms
May  6 11:46:58 zimus PackageKit: search-file transaction /286_ddddaaac from uid 1000 finished with success after 632ms
May  6 11:46:59 zimus PackageKit: search-file transaction /287_adbbdacc from uid 1000 finished with success after 631ms
May  6 11:46:59 zimus PackageKit: search-file transaction /288_baabcbea from uid 1000 finished with success after 647ms
May  6 11:47:00 zimus PackageKit: search-file transaction /289_addccebd from uid 1000 finished with success after 644ms
May  6 11:47:01 zimus colord[1135]: failed to get seat for session c1 [pid 1266]: No data available
May  6 11:47:01 zimus gsd-color[1266]: unable to get EDID for xrandr-rdp0: unable to get EDID for output
May  6 11:47:01 zimus kernel: [  122.249719] traps: gsd-color[1266] trap divide error ip:55cbb120994a sp:7ffc0b145e60 error:0 in gsd-color[55cbb1200000+12000]
May  6 11:47:01 zimus gnome-session[857]: gnome-session-binary[857]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' killed by signal 8
May  6 11:47:01 zimus gnome-session-binary[857]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' killed by signal 8
May  6 11:47:01 zimus gnome-session[857]: gnome-session-binary[857]: WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' respawning too quickly
May  6 11:47:01 zimus gnome-session[857]: gnome-session-binary[857]: CRITICAL: We failed, but the fail whale is dead. Sorry....
May  6 11:47:01 zimus gnome-session-binary[857]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
May  6 11:47:01 zimus gnome-session-binary[857]: WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' respawning too quickly
May  6 11:47:01 zimus gnome-session-binary[857]: CRITICAL: We failed, but the fail whale is dead. Sorry....
May  6 11:47:01 zimus xrdp-sesman[839]: (839)(140650868393024)[CORE ] window manager (pid 852) did exit, cleaning up session
May  6 11:47:01 zimus xrdp-sesman[839]: (839)(140650868393024)[INFO ] calling auth_stop_session and auth_end from pid 839
May  6 11:47:01 zimus xrdp-sesman[839]: (839)(140650868393024)[DEBUG] cleanup_sockets:
May  6 11:47:01 zimus xrdp[837]: (837)(139809021074688)[DEBUG] Closed socket 26 (AF_UNIX)
May  6 11:47:01 zimus xrdp-sesman[839]: (839)(140650868393024)[DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdp_chansrv_audio_out_socket_10
May  6 11:47:01 zimus xrdp-sesman[839]: (839)(140650868393024)[DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdp_chansrv_audio_in_socket_10
May  6 11:47:01 zimus xrdp-sesman[839]: (839)(140650868393024)[DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdpapi_10
May  6 11:47:01 zimus gsd-power[1030]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
May  6 11:47:01 zimus xrdp-sesman[619]: (619)(140650868393024)[INFO ] ++ terminated session:  username xoob, display :10.0, session_pid 839, ip <IP_ADDRESS>:6760 - socket: 12
May  6 11:47:01 zimus gsd-xsettings[1050]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
May  6 11:47:01 zimus gsd-wacom[1058]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
May  6 11:47:01 zimus gsd-clipboard[1070]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
May  6 11:47:01 zimus gsd-keyboard[1078]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
May  6 11:47:01 zimus gsd-media-keys[1079]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
May  6 11:47:01 zimus kerneloops-applet.desktop[1137]: kerneloops-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
May  6 11:47:01 zimus PackageKit: search-file transaction /290_ebadbabe from uid 1000 finished with success after 1241ms
May  6 11:47:01 zimus xrdp[837]: (837)(139809021074688)[DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:7777)
May  6 11:47:01 zimus xrdp[837]: (837)(139809021074688)[DEBUG] xrdp_mm_module_cleanup
May  6 11:47:01 zimus xrdp[837]: (837)(139809021074688)[DEBUG] Closed socket 25 (AF_UNIX)
May  6 11:47:01 zimus gnome-shell[909]: gnome-shell: Fatal IO error 0 (Success) on X server :10.0.

Anybody faced this?

Fixed gnome-keyring errors and got such DBus errors:
xrdp[624]: (624)(140711347752192)[DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:7777)
xrdp[843]: (843)(140711347752192)[DEBUG] Closed socket 11 (AF_INET <IP_ADDRESS>:7777)
xrdp[843]: (843)(140711347752192)[INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
xrdp[843]: (843)(140711347752192)[INFO ] Using default X.509 key file: /etc/xrdp/key.pem
xrdp[843]: (843)(140711347752192)[DEBUG] TLSv1.2 enabled
xrdp[843]: (843)(140711347752192)[DEBUG] TLSv1.1 enabled
xrdp[843]: (843)(140711347752192)[DEBUG] TLSv1 enabled
xrdp[843]: (843)(140711347752192)[DEBUG] Security layer: requested 11, selected 1
xrdp[843]: (843)(140711347752192)[DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:7777)
xrdp[624]: (624)(140711347752192)[INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 7137
xrdp[624]: (624)(140711347752192)[DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:7777)
xrdp[844]: (844)(140711347752192)[DEBUG] Closed socket 11 (AF_INET <IP_ADDRESS>:7777)
xrdp[844]: (844)(140711347752192)[INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
xrdp[844]: (844)(140711347752192)[INFO ] Using default X.509 key file: /etc/xrdp/key.pem
xrdp[844]: (844)(140711347752192)[DEBUG] TLSv1.2 enabled
xrdp[844]: (844)(140711347752192)[DEBUG] TLSv1.1 enabled
xrdp[844]: (844)(140711347752192)[DEBUG] TLSv1 enabled
xrdp[844]: (844)(140711347752192)[DEBUG] Security layer: requested 11, selected 1
xrdp[844]: (844)(140711347752192)[INFO ] connected client computer name: ISIDA
xrdp[844]: (844)(140711347752192)[INFO ] TLS connection established from <IP_ADDRESS> port 7137: TLSv1.2 with cipher AES256-GCM-SHA384
xrdp[844]: (844)(140711347752192)[DEBUG] xrdp_0000034c_wm_login_mode_event_00000001
xrdp[844]: (844)(140711347752192)[INFO ] Loading keymap file /etc/xrdp/km-00000409.ini
xrdp[844]: (844)(140711347752192)[WARN ] local keymap file for 0x00000409 found and doesn't match built in keymap, using local keymap file
xrdp[844]: (844)(140711347752192)[DEBUG] xrdp_wm_log_msg: connecting to sesman ip <IP_ADDRESS> port 3350
xrdp-sesman[621]: (621)(140561311482944)[INFO ] A connection received from <IP_ADDRESS> port 51182
xrdp[844]: (844)(140711347752192)[INFO ] xrdp_wm_log_msg: sesman connect ok
xrdp[844]: (844)(140711347752192)[DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
xrdp[844]: (844)(140711347752192)[DEBUG] return value from xrdp_mm_connect 0
xrdp-sesman[621]: (621)(140561311482944)[INFO ] ++ created session (access granted): username xoob, ip <IP_ADDRESS>:7137 - socket: 12
xrdp-sesman[621]: (621)(140561311482944)[INFO ] starting Xorg session...
xrdp-sesman[621]: (621)(140561311482944)[DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5910)
xrdp-sesman[621]: (621)(140561311482944)[DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6010)
xrdp-sesman[621]: (621)(140561311482944)[DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6210)
xrdp[844]: (844)(140711347752192)[INFO ] xrdp_wm_log_msg: login successful for display 10
xrdp-sesman[621]: (621)(140561311482944)[DEBUG] Closed socket 8 (AF_INET <IP_ADDRESS>:3350)
xrdp-sesman[846]: (846)(140561311482944)[INFO ] calling auth_start_session from pid 846
xrdp[844]: (844)(140711347752192)[DEBUG] xrdp_wm_log_msg: started connecting
systemd[1]: Created slice User Slice of xoob.
systemd[1]: Starting User Manager for UID 1000...
systemd[1]: Started Session c1 of user xoob.
systemd[847]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
xrdp-sesman[846]: (846)(140561311482944)[DEBUG] Closed socket 7 (AF_INET <IP_ADDRESS>:3350)
systemd[847]: Listening on GnuPG cryptographic agent and passphrase cache.
xrdp-sesman[846]: (846)(140561311482944)[DEBUG] Closed socket 8 (AF_INET <IP_ADDRESS>:3350)
systemd[847]: Reached target Paths.
systemd[847]: Reached target Timers.
systemd[847]: Listening on GnuPG network certificate management daemon.
systemd[847]: Starting D-Bus User Message Bus Socket.
systemd[847]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
systemd[847]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
systemd[847]: Listening on D-Bus User Message Bus Socket.
systemd[847]: Reached target Sockets.
systemd[847]: Reached target Basic System.
systemd[1]: Started User Manager for UID 1000.
systemd[847]: Reached target Default.
systemd[847]: Startup finished in 123ms.
xrdp-sesman[860]: (860)(140561311482944)[INFO ] Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log
xrdp-sesman[846]: (846)(140561311482944)[CORE ] waiting for window manager (pid 859) to exit
xrdp[844]: (844)(140711347752192)[INFO ] lib_mod_log_peer: xrdp_pid=844 connected to X11rdp_pid=860 X11rdp_uid=1000 X11rdp_gid=1000 client_ip=<IP_ADDRESS> client_port=7137
xrdp[844]: (844)(140711347752192)[DEBUG] xrdp_wm_log_msg: connected ok
dbus-daemon[867]: [session uid=1000 pid=867] AppArmor D-Bus mediation is enabled
systemd[847]: Started D-Bus User Message Bus.
dbus-daemon[867]: [session uid=1000 pid=867] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.4' (uid=1000 pid=883 comm="/usr/lib/gnome-session/gnome-session-check-acceler" label="unconfined")
systemd[847]: Starting Accessibility services bus...
dbus-daemon[867]: [session uid=1000 pid=867] Successfully activated service 'org.a11y.Bus'
systemd[847]: Started Accessibility services bus.
at-spi-bus-launcher[884]: dbus-daemon[889]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=883 comm="/usr/lib/gnome-session/gnome-session-check-acceler" label="unconfined")
at-spi-bus-launcher[884]: dbus-daemon[889]: Successfully activated service 'org.a11y.atspi.Registry'
at-spi-bus-launcher[884]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
dbus-daemon[867]: [session uid=1000 pid=867] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.7' (uid=1000 pid=883 comm="/usr/lib/gnome-session/gnome-session-check-acceler" label="unconfined")
systemd[847]: Starting Virtual filesystem service...
dbus-daemon[867]: [session uid=1000 pid=867] Successfully activated service 'org.gtk.vfs.Daemon'
xrdp[844]: (844)(140711347752192)[DEBUG] xrdp_mm_connect_chansrv: chansrv connect successful
systemd[847]: Started Virtual filesystem service.
xrdp[844]: (844)(140711347752192)[DEBUG] Closed socket 24 (AF_INET <IP_ADDRESS>:51182)
xrdp[844]: (844)(140711347752192)[INFO ] The following channel is allowed: rdpdr (0)
xrdp[844]: (844)(140711347752192)[INFO ] The following channel is allowed: rdpsnd (1)
xrdp[844]: (844)(140711347752192)[INFO ] The following channel is allowed: cliprdr (2)
xrdp[844]: (844)(140711347752192)[INFO ] The following channel is allowed: drdynvc (3)
xrdp[844]: (844)(140711347752192)[DEBUG] The allow channel list now initialized for this session
gnome-session[877]: gnome-session-binary[877]: WARNING: Could not parse desktop file xscreensaver.desktop or it references a not found TryExec binary
gnome-session-binary[877]: WARNING: Could not parse desktop file xscreensaver.desktop or it references a not found TryExec binary
gnome-keyring-pkcs11.desktop[916]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
gnome-keyring-ssh.desktop[918]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
gnome-keyring-secrets.desktop[917]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
dbus-daemon[568]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.26' (uid=1000 pid=922 comm="/usr/bin/gnome-shell " label="unconfined")
systemd[1]: Starting Daemon for power management...
dbus-daemon[568]: [system] Successfully activated service 'org.freedesktop.UPower'
systemd[1]: Started Daemon for power management.
dbus-daemon[568]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=1000 pid=935 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined")
systemd[1]: Starting RealtimeKit Scheduling Policy Service...
dbus-daemon[568]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
systemd[1]: Started RealtimeKit Scheduling Policy Service.
rtkit-daemon[936]: Successfully called chroot.
rtkit-daemon[936]: Successfully dropped privileges.
rtkit-daemon[936]: Successfully limited resources.
rtkit-daemon[936]: Running.
rtkit-daemon[936]: Watchdog thread running.
rtkit-daemon[936]: Canary thread running.
gnome-shell[922]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 340]: reference to undefined property "MetaStage"
gnome-shell[922]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 220]: reference to undefined property "MetaWindowGroup"
gnome-shell[922]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property "MetaDBusDisplayConfigSkeleton"
dbus-daemon[867]: [session uid=1000 pid=867] Activating service name='org.freedesktop.portal.IBus' requested by ':1.23' (uid=1000 pid=946 comm="ibus-daemon --xim --panel disable " label="unconfined")
dbus-daemon[867]: [session uid=1000 pid=867] Successfully activated service 'org.freedesktop.portal.IBus'
dbus-daemon[867]: [session uid=1000 pid=867] Activating service name='org.gnome.Shell.CalendarServer' requested by ':1.21' (uid=1000 pid=922 comm="/usr/bin/gnome-shell " label="unconfined")
dbus-daemon[867]: [session uid=1000 pid=867] Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service' requested by ':1.27' (uid=1000 pid=965 comm="/usr/lib/gnome-shell/gnome-shell-calendar-server " label="unconfined")
systemd[847]: Starting Evolution source registry...
dbus-daemon[867]: [session uid=1000 pid=867] Activating service name='org.gnome.OnlineAccounts' requested by ':1.28' (uid=1000 pid=969 comm="/usr/lib/evolution/evolution-source-registry " label="unconfined")
dbus-daemon[867]: [session uid=1000 pid=867] Successfully activated service 'org.gnome.evolution.dataserver.Sources5'
systemd[847]: Started Evolution source registry.
dbus-daemon[867]: [session uid=1000 pid=867] Successfully activated service 'org.gnome.Shell.CalendarServer'
goa-daemon[975]: goa-daemon version 3.28.0 starting
dbus-daemon[867]: [session uid=1000 pid=867] Activating service name='org.gnome.Identity' requested by ':1.29' (uid=1000 pid=975 comm="/usr/lib/gnome-online-accounts/goa-daemon " label="unconfined")
dbus-daemon[867]: [session uid=1000 pid=867] Successfully activated service 'org.gnome.OnlineAccounts'
dbus-daemon[867]: [session uid=1000 pid=867] Successfully activated service 'org.gnome.Identity'
gnome-shell[922]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property "CallyActor"
dbus-daemon[568]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' requested by ':1.26' (uid=1000 pid=922 comm="/usr/bin/gnome-shell " label="unconfined")
systemd[1]: Reached target User and Group Name Lookups.
systemd[1]: Starting Accounts Service...
accounts-daemon[994]: started daemon version 0.6.45
dbus-daemon[568]: [system] Successfully activated service 'org.freedesktop.Accounts'
systemd[1]: Started Accounts Service.
dbus-daemon[568]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.26' (uid=1000 pid=922 comm="/usr/bin/gnome-shell " label="unconfined")
systemd[1]: Starting Location Lookup Service...
dbus-daemon[568]: [system] Successfully activated service 'org.freedesktop.GeoClue2'
systemd[1]: Started Location Lookup Service.
dbus-daemon[867]: [session uid=1000 pid=867] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.21' (uid=1000 pid=922 comm="/usr/bin/gnome-shell " label="unconfined")
systemd[847]: Starting Virtual filesystem service - disk device monitor...
dbus-daemon[568]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' requested by ':1.46' (uid=1000 pid=1007 comm="/usr/lib/gvfs/gvfs-udisks2-volume-monitor " label="unconfined")
systemd[1]: Starting Disk Manager...
udisksd[1010]: udisks daemon version 2.7.6 starting
udisksd[1010]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
kernel: [  207.905086] Lockdown: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7
udisksd[1010]: Failed to load the 'mdraid' libblockdev plugin
dbus-daemon[568]: [system] Successfully activated service 'org.freedesktop.UDisks2'
systemd[1]: Started Disk Manager.
udisksd[1010]: Acquired the name org.freedesktop.UDisks2 on the system message bus
dbus-daemon[867]: [session uid=1000 pid=867] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
systemd[847]: Started Virtual filesystem service - disk device monitor.
dbus-daemon[867]: [session uid=1000 pid=867] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.21' (uid=1000 pid=922 comm="/usr/bin/gnome-shell " label="unconfined")
systemd[847]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
dbus-daemon[867]: [session uid=1000 pid=867] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
systemd[847]: Started Virtual filesystem service - Media Transfer Protocol monitor.
dbus-daemon[867]: [session uid=1000 pid=867] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.21' (uid=1000 pid=922 comm="/usr/bin/gnome-shell " label="unconfined")
systemd[847]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
dbus-daemon[867]: [session uid=1000 pid=867] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
systemd[847]: Started Virtual filesystem service - GNOME Online Accounts monitor.
dbus-daemon[867]: [session uid=1000 pid=867] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.21' (uid=1000 pid=922 comm="/usr/bin/gnome-shell " label="unconfined")
systemd[847]: Starting Virtual filesystem service - Apple File Conduit monitor...
gvfs-afc-volume-monitor[1033]: Volume monitor alive
dbus-daemon[867]: [session uid=1000 pid=867] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
systemd[847]: Started Virtual filesystem service - Apple File Conduit monitor.
dbus-daemon[867]: [session uid=1000 pid=867] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.21' (uid=1000 pid=922 comm="/usr/bin/gnome-shell " label="unconfined")
systemd[847]: Starting Virtual filesystem service - digital camera monitor...
dbus-daemon[867]: [session uid=1000 pid=867] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
systemd[847]: Started Virtual filesystem service - digital camera monitor.
gnome-shell[922]: Failed to add search provider /usr/share/gnome-shell/search-providers/nautilus-search-provider.ini: TypeError: appInfo is null
dbus-daemon[568]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.26' (uid=1000 pid=922 comm="/usr/bin/gnome-shell " label="unconfined")
systemd[1]: Starting PackageKit Daemon...
PackageKit: daemon start
dbus-daemon[568]: [system] Successfully activated service 'org.freedesktop.PackageKit'
systemd[1]: Started PackageKit Daemon.
spice-vdagent[1079]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
gnome-shell[922]: JS WARNING: [resource:///org/gnome/shell/ui/workspaceThumbnail.js 903]: reference to undefined property "_switchWorkspaceNotifyId"
gnome-session[877]: gnome-session-binary[877]: WARNING: App 'spice-vdagent.desktop' exited with code 1
gsd-rfkill[1055]: Error setting up rfkill: Could not open RFKILL control device, please verify your installation
dbus-daemon[568]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.49' (uid=1000 pid=1055 comm="/usr/lib/gnome-settings-daemon/gsd-rfkill " label="unconfined")
systemd[1]: Starting Hostname Service...
gnome-session-binary[877]: WARNING: App 'spice-vdagent.desktop' exited with code 1
dbus-daemon[568]: [system] Successfully activated service 'org.freedesktop.hostname1'
systemd[1]: Started Hostname Service.
gsd-rfkill[1055]: Could not open RFKILL control device, please verify your installation
dbus-daemon[867]: [session uid=1000 pid=867] Activating via systemd: service name='org.gnome.evolution.dataserver.Calendar7' unit='evolution-calendar-factory.service' requested by ':1.27' (uid=1000 pid=965 comm="/usr/lib/gnome-shell/gnome-shell-calendar-server " label="unconfined")
systemd[847]: Starting Evolution calendar service...
dbus-daemon[568]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.56' (uid=1000 pid=1088 comm="/usr/lib/gnome-settings-daemon/gsd-color " label="unconfined")
systemd[1]: Starting Manage, Install and Generate Color Profiles...
dbus-daemon[568]: [system] Successfully activated service 'org.freedesktop.ColorManager'
systemd[1]: Started Manage, Install and Generate Color Profiles.
dbus-daemon[568]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.59' (uid=1000 pid=1093 comm="/usr/lib/gnome-settings-daemon/gsd-keyboard " label="unconfined")
systemd[1]: Starting Locale Service...
dbus-daemon[568]: [system] Successfully activated service 'org.freedesktop.locale1'
systemd[1]: Started Locale Service.
gsd-media-keys[1099]: Unable to inhibit keypresses: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Permission denied
gsd-sharing[1059]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-user-share-webdav.service not loaded.
gsd-sharing[1059]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
gsd-sharing[1059]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.
gsd-sharing[1059]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service not loaded.
gnome-session-binary[877]: Entering running state
dbus-daemon[867]: [session uid=1000 pid=867] Successfully activated service 'org.gnome.evolution.dataserver.Calendar7'
systemd[847]: Started Evolution calendar service.
dbus-daemon[867]: [session uid=1000 pid=867] Activating service name='ca.desrt.dconf' requested by ':1.56' (uid=1000 pid=1176 comm="/usr/lib/evolution/evolution-calendar-factory-subp" label="unconfined")
dbus-daemon[867]: [session uid=1000 pid=867] Activating via systemd: service name='org.gnome.evolution.dataserver.AddressBook9' unit='evolution-addressbook-factory.service' requested by ':1.56' (uid=1000 pid=1176 comm="/usr/lib/evolution/evolution-calendar-factory-subp" label="unconfined")
systemd[847]: Starting Evolution address book service...
dbus-daemon[867]: [session uid=1000 pid=867] Successfully activated service 'ca.desrt.dconf'
dbus-daemon[867]: [session uid=1000 pid=867] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook9'
systemd[847]: Started Evolution address book service.
gnome-shell[922]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.impl.portal.PermissionStore was not provided by any .service files
kerneloops-appl[1152]: Failed to load module "canberra-gtk-module"
gsd-color[1088]: failed to get edid: unable to get EDID for output
colord[1140]: failed to get seat for session c1 [pid 1088]: No data available
gnome-shell[922]: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
gsd-color[1088]: unable to get EDID for xrandr-rdp0: unable to get EDID for output
kernel: [  213.817502] do_trap: 20 callbacks suppressed
kernel: [  213.817504] traps: gsd-color[1088] trap divide error ip:5592b1f5c94a sp:7fffbcc03a90 error:0 in gsd-color[5592b1f53000+12000]
gnome-shell[922]: Could not get current seat: No data available
gnome-shell[922]: GNOME Shell started at Mon May 21 2018 12:06:54 GMT+0300 (EEST)
gnome-session[877]: gnome-session-binary[877]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' killed by signal 8
gnome-session-binary[877]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' killed by signal 8
gsd-color[1240]: failed to get edid: unable to get EDID for output
colord[1140]: failed to get seat for session c1 [pid 1240]: No data available
gsd-color[1240]: unable to get EDID for xrandr-rdp0: unable to get EDID for output
kernel: [  220.142162] traps: gsd-color[1240] trap divide error ip:55c79912d94a sp:7ffcbd6a6020 error:0 in gsd-color[55c799124000+12000]
gnome-session[877]: gnome-session-binary[877]: WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' respawning too quickly
gnome-session-binary[877]: WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' respawning too quickly
gnome-session-binary[877]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
gnome-session[877]: gnome-session-binary[877]: CRITICAL: We failed, but the fail whale is dead. Sorry....
gnome-session-binary[877]: CRITICAL: We failed, but the fail whale is dead. Sorry....
xrdp-sesman[846]: (846)(140561311482944)[CORE ] window manager (pid 859) did exit, cleaning up session
xrdp-sesman[846]: (846)(140561311482944)[INFO ] calling auth_stop_session and auth_end from pid 846
xrdp-sesman[846]: (846)(140561311482944)[DEBUG] cleanup_sockets:
xrdp-sesman[846]: (846)(140561311482944)[DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdp_chansrv_audio_out_socket_10
xrdp-sesman[846]: (846)(140561311482944)[DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdp_chansrv_audio_in_socket_10
xrdp-sesman[846]: (846)(140561311482944)[DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdpapi_10
xrdp-sesman[621]: (621)(140561311482944)[INFO ] ++ terminated session:  username xoob, display :10.0, session_pid 846, ip <IP_ADDRESS>:7137 - socket: 12
xrdp[844]: (844)(140711347752192)[DEBUG] Closed socket 26 (AF_UNIX)
at-spi-bus-launcher[884]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":10.0"
at-spi-bus-launcher[884]:       after 23 requests (23 known processed) with 0 events remaining.
kernel: [  221.144168] gnome-shell[922]: segfault at 10 ip 00007fd88cb3712f sp 00007fff690fcac0 error 4 in libmutter-2.so.0.0.0[7fd88ca73000+156000]
gsd-power[1051]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
gsd-xsettings[1069]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
gsd-wacom[1075]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
gsd-clipboard[1084]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
gsd-media-keys[1099]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
gsd-keyboard[1093]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
kerneloops-applet.desktop[1152]: kerneloops-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
conky.desktop[1150]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":10.0"
conky.desktop[1150]:       after 578 requests (578 known processed) with 0 events remaining.
xrdp[844]: (844)(140711347752192)[DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:7777)
xrdp[844]: (844)(140711347752192)[DEBUG] xrdp_mm_module_cleanup
xrdp[844]: (844)(140711347752192)[DEBUG] Closed socket 25 (AF_UNIX)

Can anybody suggest something?

I know this is a while ago, but one thing that springs to mind looking at your problems above is to check your version of xorgxrdp is at least 0.2.6. It's possible you're seeing neutrinolabs/xorgxrdp#111 as the fix improved improving the gamma ramp compatibility with other X servers.

@matt335672 , how to check the version? dpkg -l shows xorgxrdp version 0.9.5-2

Hey, I've just solved the "color managed device" prompt error with this solution, just copy/paste the commands to the terminal. The problem with this is that the sidebar doesn't appear and the application layouts have a different theme (???) than the original.
Ubuntu 18.04 here, btw

@dangpzanco you paste into console exactly this?
polkit.addRule(function(action, subject) { if ((action.id == "org.freedesktop.color-manager.create-device" || action.id == "org.freedesktop.color-manager.create-profile" || action.id == "org.freedesktop.color-manager.delete-device" || action.id == "org.freedesktop.color-manager.delete-profile" || action.id == "org.freedesktop.color-manager.modify-device" || action.id == "org.freedesktop.color-manager.modify-profile") && subject.isInGroup("{xoob}")) { return polkit.Result.YES; }});
It throws syntax error on semicolon.
When I added this rule into /etc/polkit-1/localauthority.conf.d/02-allow-colord.conf it solves the problem of color device, but it completely brokes all other functions. I cannot neither connect to VPN nor shutdown the machine. Which makes this solution fatal.
Jun  1 07:02:34 zimus systemd[1]: Started Authorization Manager.
Jun  1 07:02:35 zimus org.gnome.Shell.desktop[921]: PolicyKit daemon reconnected to bus.
Jun  1 07:02:35 zimus org.gnome.Shell.desktop[921]: Attempting to re-register as an authentication agent.
Jun  1 07:02:35 zimus org.gnome.Shell.desktop[921]: We are now a registered authentication agent.
Jun  1 07:02:53 zimus kernel: [  184.982026] polkitd[1319]: segfault at 8 ip 00007f809a16cfa6 sp 00007ffc53625690 error 4 in libpolkit-backend-1.so.0.0.0[7f809a15d000+18000]
Jun  1 07:02:53 zimus systemd[1]: polkit.service: Main process exited, code=dumped, status=11/SEGV
Jun  1 07:02:53 zimus org.gnome.Shell.desktop[921]: PolicyKit daemon disconnected from the bus.
Jun  1 07:02:53 zimus org.gnome.Shell.desktop[921]: We are no longer a registered authentication agent.
Jun  1 07:02:53 zimus systemd[1]: polkit.service: Failed with result 'core-dump'.
Jun  1 07:02:53 zimus dbus-daemon[569]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.10' (uid=0 pid=576 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Jun  1 07:02:53 zimus gnome-session-binary[881]: WARNING: Shutdown failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Jun  1 07:02:53 zimus gnome-session-binary[881]: Entering running state
Jun  1 07:02:53 zimus gnome-session[881]: gnome-session-binary[881]: WARNING: Shutdown failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Jun  1 07:02:53 zimus systemd[1]: Starting Authorization Manager...
Jun  1 07:02:53 zimus polkitd[1329]: started daemon version 0.105 using authority implementation `local' version `0.105'
Jun  1 07:02:53 zimus dbus-daemon[569]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jun  1 07:02:53 zimus systemd[1]: Started Authorization Manager.
Jun  1 07:02:53 zimus gnome-shell[921]: Ignored exception from dbus method: Gio.IOErrorEnum: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code19: Operation was cancelled
Jun  1 07:02:53 zimus org.gnome.Shell.desktop[921]: PolicyKit daemon reconnected to bus.
Jun  1 07:02:53 zimus org.gnome.Shell.desktop[921]: Attempting to re-register as an authentication agent.
Jun  1 07:02:53 zimus org.gnome.Shell.desktop[921]: We are now a registered authentication agent.

Oh, sorry, I messed up when I said to copy/paste to the terminal, I meant to add the rule...
And it probably breaks the same things on my setup too, since I didn't thoroughly check the solution, sorry if it wasn't useful for you.
I'll probably set up VNC on my machine and not have to deal with this mess...

@suncatcher - I've just had a look at the Ubuntu packages in 18.04. Details for xorgxrdp are here and details for xrdp are here. At the moment the version is 0.9.5-2.
What seems to have been done for Ubuntu is that xrdp and xorgxrdp (which are separate github projects) have been combined into a single xrdp package under the xrdp version number. This is different from CentOS/EPEL, where xrdp and xorgxrdp are separate RPMs.
In the Ubuntu package 0.9.5-2 there's a file xrdp_0.9.5.orig-xorgxrdp.tar.gz. If you look in there it contains a single directory xorgxrdp-0.2.5.
So I think the packaged Ubuntu xrdp will need updating before it will work with GNOME.
You could try rebuilding the package yourself, incorporating the latest xorgxrdp, or use the VNC backend until an update is produced for the package by the Ubuntu developers. I think they are your only two options at this point.
The problem fixed in the 0.2.6 version of xorgxrdp is not the "color managed device" prompt error discussed above - it's a fix to the xrandr handler to provide more realistic gamma ramps.
Hope this is useful information.

Ok, thanks for the info.
Rebuilt from scratch and now it works! Hats off!


added json-pairs example

@dmpetrov @volkfox QQ - are we merging / fixing this?

@volkfox @dmpetrov ping


Needs to make it clear that the Service Principal created has a password that expires

This page does not document that the Service Principal that is created has a password that expires in 1 year, and will need to be reset every year (or longer). This is critical for the cluster to be able to pull images, for example, when the HPA needs new pods created. The password expiring will causes services to fail. The expiration needs to be called out clearly, with a link to instructions on how to reset it.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0b775c99-7231-2bfa-1af2-c40852c591aa
Version Independent ID: 499f8091-28e4-b6c5-4dd1-b5fac9632769
Content: Authenticate with an Azure container registry using a Kubernetes pull secret - Azure Container Registry
Content Source: articles/container-registry/container-registry-auth-kubernetes.md
Service: container-registry
GitHub Login: @karolz-ms
Microsoft Alias: karolz

@pdonovan Thanks for your feedback! We will investigate and update as appropriate.

Hello @karolz-ms , could you please review this and add your comments.

I understand @pdonovan point, but I am not sure if this documentation article is the best place to emphasize that Service Principal passwords do expire, and how to deal with that.
@dlepow has an article https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-registry/container-registry-auth-service-principal.md about using Service Principal authentication with ACR that might be a better place for such information. Or maybe there is another, even better way to address this feedback--Dan?

I agree that container-registry-auth-service-principal could be better place to make that point. Adding @tejaswikolli-web who is the current writer for ACR to evaluate the update. Thanks

I have made changes to the https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-registry/container-registry-auth-service-principal.md, It is under review, will be published very soon.

https://docs.microsoft.com/en-us/azure/container-registry/container-registry-auth-service-principal

#please-close


VMI CRD validation with OpenAPI v3 schema

What this PR does
Move many VMI validation from the validating webhook, to the CRD, using OpenAPI v3 schema
See here for more info.
Continue the CRD validation started at #11156
Before this PR:
Many simple validation are done in the webhook logic
After this PR:
These validations are now done by the api-server, according to the CRD.
Many field are now validated by the CRD:

firmware.Serial
spec.domain.devices.inputs
spec.Domain.IOThreadsPolicy
disk name duplication
volume name duplication
sound device
interface
CPU feature policy

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

Removed many vmi validation to the CRD, using OpenAPI v3 schema

/test pull-kubevirt-e2e-arm64

/retest

@orelmisan - Not sure we need to retest K8s mechanisms

@orelmisan - Not sure we need to retest K8s mechanisms

I'm not talking about the K8s mechanism.
For example, lets assume that some field is validated using a regex.
How or where do we validate the correctness of the regex against several test cases?

You have a point regarding regex. In this specific PR, I just copied the regex from the code, as is

/lgtm

/uncc

Last commit adds unit test to make sure the CRD validation is working.


resampling: Don't subscribe twice to the same source

When receiving a subcription, we need to check if we are already handling a subscription with the same request parameters to avoid pushing the data twice to the same channel.
Fixes #115.

I will try to add a test to make sure we don´t regress.

I can approve as soon as the black issues are fixed.  There will be tests from the logicalmeter anyway.

Updated to fix black issues and add a test. Enabling auto-merge.

After thinking about this a bit more, wondering how things could go after/if we add historical data, maybe I should have kept a set of requests instead of channels, as for historical data we might want to put more data in the same channel. But OTOH doing this will complicate a lot the use of the resampler, as whatever happens we should keep the pace of the resampling period. So better to address it when the problem comes and we have more clarity on how to solve it, o maybe we don't even use the same resampler for historical data than for live data.


ControlledOnInt return should use LittleEndian argument

Describe the bug
The return of ControlledOnInt is an operation that takes a tuple (Qubit[], 'T). I think it should return an operation that takes a tuple of (LittleEndian, 'T) so that there is a clear interpretation of the integer that the register is supposed to represent.
To Reproduce
Not really any steps, just an inconsistent design.
Expected behavior
As noted above, to be able to control on an integer there has to be way to interpret a register as an integer. This can be encoded in the type signature by having the operation take a type LittleEndian.

Thanks @crazy4pi314 for filing this issue! It looks like it is covered by https://github.com/microsoft/QuantumLibraries/issues/337, so we will close this for now.

Reopening this issue and assigning our new Status-ChildIssue label so we can track it as part of the #337 proposal.


Linux .deb installer package not working on Ubuntu

Describe the bug
I fired up a fresh Ubuntu 18.04.3 server, downloaded the installer .deb file, and tried to install it, but clicking "Install" does nothing.
To Reproduce
Fire up a new Ubuntu VM
Follow instructions here to set up gnome packages and VNC server: sudo apt-get install gnome-core vnc4server
.vnc/xstartup contains:
#!/bin/sh

# Uncomment the following two lines for normal desktop:
# unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
x-window-manager &

metacity &
gnome-settings-daemon &
gnome-panel &

Desktop (please complete the following information):
Ubuntu 18.04.3
Gnome 3.28.2
Metacity
Additional context
I was able to install the app using gdebi by following the instructions at https://www.ubuntupit.com/cant-install-deb-files-ubuntu-heres-possible-ways-install-deb-packages/.

To upgrade to the latest package I did the following:
> sudo apt-get remove smapp
> sudo gdebi <new package.deb>
> rm -rf ~/post ~/.config/Spacemesh

How do we resolve this?

I upgraded the app today, and I installed the package with this command, which worked fine:

sudo dpkg -i ~/Downloads/spacemesh_app_0.0.3_amd64.deb

So maybe to close this we just need to add to the guide how to install using dpkg?

I think that's fine for now. I tried on several VMs and was not able to get
the app to install by double-clicking the pkg file on any of them. I'm not
a Linux expert, I have no idea why this isn't working. Happy to dig deeper
on it if you think it's valuable, but all of our Linux users should be
comfortable running things on the command line and I can't imagine any of
them will struggle to run dpkg. I'll update the docs if we're in agreement
on this.
On Mon, 9 Mar 2020 at 14:55, Aviv Eyal<EMAIL_ADDRESS>wrote:

So maybe to close this we just need to add to the guide how to install
using dpkg?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/spacemeshos/smapp/issues/390?email_source=notifications&email_token=AAZJWNEQI3DTRZ2YEZ73SDLRGU3QZA5CNFSM4KYDLBE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOIT2AA#issuecomment-596720896,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZJWNEOCB3XOIW4ILZZAMTRGU3QZANCNFSM4KYDLBEQ
.

Added here: https://github.com/spacemeshos/testnet-guide/commit/a9faa5ecc471eaee55d64a08b39e0d782fc2b261#diff-ac890c1ed8e54fcb56710db1a649959f


Create input translating tools

The Atom editor has a [https://github.com/AtomLinter/linter-clang](built in tool for validating c code with clant) as you type. It takes the error output and displays it inline in the editor. Atom is consuming the compiler output.

We want to create a consumer that inhales the same information into a STAT data structure.

[x] Identify which program Atom uses by default to lint c code
[ ] Make a simple c program with a few errors and generate the same linting output
[ ] Write a new tool stat-from-clang (or whatever that producer is called) it will read clang input and produce stat output

Of course, when we're done we should be able to
clang a.cpp > tmp
cat tmp | stat-from-clang | stat-to-clang | cmp tmp

And they will be the same.

Note: here is the code that the Atom clang linter uses to inhale clang messages:
https://github.com/AtomLinter/linter-clang/blob/master/lib/main.js
That code also includes details about how to run the compiler. We don't care about that, we just want the compiler output and this is captured by the regex they use:
    const regex = "(?<file>.+):(?<line>\\d+):(?<col>\\d+):(\{(?<lineStart>\\d+):(?<colStart>\\d+)\-(?<lineEnd>\\d+):(?<colEnd>\\d+)}.*:)? (?<type>[\\w \\-]+): (?<message>.*)";

This idea is stupid, #17 is better.


Fixes for version 0.16.0

Description of changes: Fixes the Braket-PennyLane plugin to support the upcoming PennyLane version 0.16.0.
Currently, our test suite is showing this plugin failing for compatibility with the development version of PennyLane. The failure is due to a new addition to PennyLane of a Projector observable that projects onto one of the computational basis states.
This PR provides a fix in preparation for the 0.16.0 release of PL next week. This is a simple fix which converts the Projector into a matrix and uses the Hermitian observable in Braket. This conversion risks being inefficient, since the constructed matrix is quite large - the ideal scenario would be for projectors to be supported on the Braket backend.
Testing done:
Added a supporting unit test.

Looks fine to me. @speller26 do you want to take a look?


driverJourney and passengerJourney vocabulary & difference Journey vs Trip

I find the names driverJourney and passengerJourney somewhat confusing, and I would like your input before proposing a PR.
Especially, when we look at a DriverJourney object (or more specifically its DriverTrip component), we see attributes like departureToPickupWalkingDistance, which is especially confusing as at first we expect informations about a driver and not a walker given the name.
I suggest searching for better names. The best I could come up with is:

DriverJourney -> JourneyAsPassenger
PassengerJourney -> JourneyWithPassenger

EDIT: I also wonder why \driver_regular_trips endpoint is not called \driver_regular_journeys. (Especially as *Journey = *Trip + JourneySchedule, I would expect *RegularJourney = *Trip + Schedules).
Is there a rationale behind the change in vocabulary? Maybe because regular trips are more likely to be round trips than single journeys? or is it common business vocabulary?
2nd EDIT: By writing the spec, I realize that considering that a regular trip can be composed of individual Journeys is pretty useful, so I think I've got it.

DriverJourney means a journey being done by a driver, which a passenger can send a request to, right? That's at least my current understanding of it. See, for example, https://github.com/fabmob/standard-covoiturage/pull/2/files#r832597019
I'm not sure changing it to JourneyAsPassenger disambiguates it. It now makes me think of a journey I'm doing as a passenger, i.e., to me it feels like we are changing the meaning of the term.
I don't remember, though, why we need to qualify the journey. Since a journey will always have a driver and at least one passenger, could we maybe just use the term journey instead?


nginx service commands not working any more if auto_ssl:init()

We have an openresty <IP_ADDRESS> on Ubuntu 12.04 LTS and/or Ubuntu 14.04, and we're having issues with the service start/stop commands since we started using lua-resty-auto-ssl.
I have been able to narrow it down to a single line in the configuration file.
Once the line auto_ssl:init() in nginx.conf is commented out of nginx.conf, everything works. (i.e. all normal nginx/openresty functionality)
Once the line auto_ssl:init() is active, nginx can be started once using service nginx start or start nginx, but when a stop is attempted (service nginx stop or stop nginx)
nginx does stop, but the stop command never returns, and from that moment on, the start and stop commands do not work any more, until a reboot. No nginx processes are left running.
nginx can still be started by issuing the nginx command, and stopped using nginx -s stop...
openresty is self-compiled, lua-resty-auto-ssl 0.10.5 is installed using luarocks.
Do you have some pointers on this?

If nginx -s stop is still working, then I'm wondering if this issue is related to the script you're using to start and stop nginx as a service (although it's still odd that this init() is making a difference). So what type of service script are you using? Do you have an init.d script, or are you using upstart, or something else? Could you share the contents of that script?
And are there any errors being logged to your nginx error log file on either startup or shutdown?
Since it seems like the service script is getting hung up on shutdown, one other potential thing to debug is to see if any child processes are being left around. If you're using something like upstart, I'm wondering if the sockproc process might be left running, which might be confusing the shutdown script if it's paying attention to process groups. One way to potentially debug this is to use pstree to see what processes are running as a child to nginx. So after starting nginx, you could try running pstree -a -p and find the nginx processes in this output. Then after attempting to stop nginx, try running that same command again and see if there's still any processes hanging around under nginx's parent process.

We're using upstart. Yes, it definitely has to do with the startup script, but it definitely has to do with auto_ssl:init() as well... those two are just not playing nicely together.
Here is /etc/init/nginx.conf
description "nginx - small, powerful, scalable web/proxy server"

start on filesystem and static-network-up
stop on runlevel [016]

expect fork
respawn

pre-start script
        [ -x /usr/sbin/nginx ] || { stop; exit 0; }
        /usr/sbin/nginx -q -t -g 'daemon on; master_process on;' || { stop; exit 0; }
end script

exec /usr/sbin/nginx -g 'daemon on; master_process on;'

pre-stop exec /usr/sbin/nginx -s quit

No errors in any logs. Yes, after some web searching I'm totally suspecting sockproc as well, but I don't even see it running.
 1578 ?        Ss     0:00 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;
 1579 ?        S      0:00  \_ nginx: worker process
 1580 ?        S      0:00  \_ nginx: worker process
 1581 ?        S      0:00  \_ nginx: worker process
 1582 ?        S      0:00  \_ nginx: worker process
 1583 ?        S      0:00  \_ nginx: cache manager process

Problem is: nothing seems to be stuck. After stopping they're all gone...

Update: somehow removing expect fork solves this issue.

@discoursehosting: Sorry for the belated followup, but thank you very much for the sleuthing! Very interesting. I'm not super-familiar with upstart, but it definitely seems like us starting sockproc inside nginx is somehow interfering with how Upstart tracks forked processes. I'm glad you were able to find the workaround with removing expect fork, but I'll have to play around with Upstart at some point to see if there's a cleaner way we could be handling this.


⚠ Bofrost.at has degraded performance

In a5fe4d3, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1373 ms

Resolved: Bofrost.at performance has improved in c8d5b88 after 7 minutes.


Explicit countdown: resource URL is short-lived

Strategies:

a) Display nothing. Keep widgets active. But after 10mn, the [Open in new tab] and [Download] buttons may malfunction, because the download URL has expired.

b) After 4mn, display a warning "URL is short-lived, please save your document"

c) Do (b) + after another 4mn, remove [Open in new tab] and [Download] buttons, and display "Resource URL has expired."

d) Do (c) + also remove preview.

e) Do (c) or (d), but taking into account the real expiration time, not guessing from the dispatch time which may be misleading.

Currently, we have (a). We can do better.

Like #142, different component


Project: Dark Mode Option In a Web Page

Description :
A simple web page with a dark mode toggle that will have two option : light mode and dark mode.
Features :

User can have light mode turned on as well as dark mode

Tentative Deadline :  1 days (Provide tentative deadline as per your analyses. Make sure it falls under 1st Oct to 31st Oct)
Some Rules to follow :

Add a README.md file for your project.
Name of Project
Demo of Project in .gif how your project is look
Description of project
Requirements or Setup instructions
Name of Author(s)
Look at Demo here.

@Harshil-Jani @Rameshchandrapola @soumik2012  Can you assign me this for the next project that I want to do for the hacktoberfest ?

it seems good and interesting to me can I work on this 🤔

@BajraYeJoon Go Ahead ! :tada:
Happy Hacktoberfest :rocket:

@Harshil-Jani  Please review the PR.😃

Hello! I would like to contribute to the issue. Would you assign the issue to me?