Как решить проблему с подключением второго дисплея?

Question

Николай Бараненко @drno-reg

см не кратко

Ubuntu

Как решить проблему с подключением второго дисплея?

Здравствуйте.

9 мая этого года перешел на Ubuntu 19.04.

До сегодняшней плановой перезагрузки не было ни одного существенного нарекания: ни одного зависания, ни креша ни что-либо еще.

НО сегодня менеджер обновлений предложил накатить обновления и потом попросил сделать перезагрузку.
Я сделал эту плановую перезагрузку.
После перезагрузки сразу порвался на первую же видимую проблему - перестал подключаться дополнительный дисплей.

В системном логе такие ошибки

work01 /usr/lib/gdm3/gdm-x-session[1835]: (II) modeset(0): Allocate new frame buffer 4480x1440 stride
May 23 12:36:21 work01 /usr/lib/gdm3/gdm-x-session[1835]: (EE) modeset(0): failed to set mode: Invalid argument
May 23 12:36:21 work01 /usr/lib/gdm3/gdm-x-session[1835]: (II) modeset(0): Allocate new frame buffer 1920x1080 stride
May 23 12:36:21 work01 /usr/lib/gdm3/gdm-x-session[1835]: (II) modeset(0): EDID vendor "AUO", prod id 8509
May 23 12:36:21 work01 /usr/lib/gdm3/gdm-x-session[1835]: (II) modeset(0): Printing DDC gathered Modelines:
May 23 12:36:21 work01 /usr/lib/gdm3/gdm-x-session[1835]: (II) modeset(0): Modeline "1920x1080"x0.0  149.80  1920 1968 2068 2228  1080 1083 1084 1120 +hsync -vsync (67.2 kHz eP)
May 23 12:36:21 work01 /usr/lib/gdm3/gdm-x-session[1835]: (II) modeset(0): Modeline "1920x1080"x0.0  119.84  1920 1968 2068 2228  1080 1083 1084 1120 +hsync -vsync (53.8 kHz e)
May 23 12:36:21 work01 /usr/lib/gdm3/gdm-x-session[1835]: (--) modeset(0): HDMI max TMDS frequency 300000KHz
May 23 12:36:21 work01 /usr/lib/gdm3/gdm-x-session[1835]: (II) modeset(0): EDID vendor "AUO", prod id 8509
May 23 12:36:21 work01 /usr/lib/gdm3/gdm-x-session[1835]: (II) modeset(0): Printing DDC gathered Modelines:
May 23 12:36:21 work01 /usr/lib/gdm3/gdm-x-session[1835]: (II) modeset(0): Modeline "1920x1080"x0.0  149.80  1920 1968 2068 2228  1080 1083 1084 1120 +hsync -vsync (67.2 kHz eP)
May 23 12:36:21 work01 /usr/lib/gdm3/gdm-x-session[1835]: (II) modeset(0): Modeline "1920x1080"x0.0  119.84  1920 1968 2068 2228  1080 1083 1084 1120 +hsync -vsync (53.8 kHz e)
May 23 12:36:21 work01 /usr/lib/gdm3/gdm-x-session[1835]: (--) modeset(0): HDMI max TMDS frequency 300000KHz
May 23 12:36:21 work01 org.gnome.Shell.desktop[1976]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
May 23 12:36:21 work01 org.gnome.Shell.desktop[1976]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
May 23 12:36:21 work01 org.gnome.Shell.desktop[1976]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
May 23 12:36:21 work01 org.gnome.Shell.desktop[1976]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
May 23 12:36:21 work01 org.gnome.Shell.desktop[1976]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
May 23 12:36:21 work01 org.gnome.Shell.desktop[1976]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
May 23 12:36:21 work01 org.gnome.Shell.desktop[1976]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
May 23 12:36:21 work01 org.gnome.Shell.desktop[1976]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
May 23 12:36:21 work01 org.gnome.Shell.desktop[1976]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).

May 23 12:38:06 work01 gnome-shell[1976]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. 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[1976]: Some code accessed the property 'ENABLED_EXTENSIONS_KEY' on the module 'extensionSystem'. 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.
May 23 12:51:29 work01 gnome-software[2418]: not GsPlugin error g-io-error-quark:24: Время ожидания истекло

Что можно сделать в этом случае?

p.s.
удалось накопать диагностики

в статусе служб

systemctl status gdm.service
systemctl status gdm3.service

присутствует такая ошибка

gdm-password][7432]: gkr-pam: unable to locate daemon control file

root@work01:~# systemctl status gdm3.service
● gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled)
   Active: active (running) since Thu 2019-05-23 13:03:58 MSK; 52s ago
  Process: 7192 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
  Process: 7205 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, status=0/SUCCESS)
 Main PID: 7206 (gdm3)
    Tasks: 3 (limit: 4915)
   Memory: 2.7M
   CGroup: /system.slice/gdm.service
           └─7206 /usr/sbin/gdm3

мая 23 13:03:58 work01 systemd[1]: Starting GNOME Display Manager...
мая 23 13:03:58 work01 systemd[1]: Started GNOME Display Manager.
мая 23 13:03:58 work01 gdm-launch-environment][7210]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
мая 23 13:04:09 work01 gdm-password][7432]: gkr-pam: unable to locate daemon control file
мая 23 13:04:09 work01 gdm-password][7432]: pam_unix(gdm-password:session): session opened for user drno by (uid=0)
мая 23 13:04:36 work01 gdm3[7206]: Child process -7240 was already dead.
root@work01:~# systemctl status gdm.service
● gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled)
   Active: active (running) since Thu 2019-05-23 13:03:58 MSK; 1min 6s ago
  Process: 7192 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
  Process: 7205 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, status=0/SUCCESS)
 Main PID: 7206 (gdm3)
    Tasks: 3 (limit: 4915)
   Memory: 2.7M
   CGroup: /system.slice/gdm.service
           └─7206 /usr/sbin/gdm3

мая 23 13:03:58 work01 systemd[1]: Starting GNOME Display Manager...
мая 23 13:03:58 work01 systemd[1]: Started GNOME Display Manager.
мая 23 13:03:58 work01 gdm-launch-environment][7210]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
мая 23 13:04:09 work01 gdm-password][7432]: gkr-pam: unable to locate daemon control file
мая 23 13:04:09 work01 gdm-password][7432]: pam_unix(gdm-password:session): session opened for user drno by (uid=0)
мая 23 13:04:36 work01 gdm3[7206]: Child process -7240 was already dead.