Thanks. Your journal.txt is showing the nvidia driver thinks the display was disconnected a few minutes after boot. So normally I would say that's a bad monitor connection (check your cables) or a driver bug. However the first message here also suggests the blackout was triggered by the system suspending and resuming. So please check your screensaver and power management settings...
ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (II) systemd-logind: got resume for 13:68 ago 31 21:39:08 ubuntu-ryzen systemd-journald[416]: Suppressed 524 messages from session-3.scope ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-0: disconnected ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-0: Internal TMDS ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): Ancor Communications Inc VX229 (DFP-1): connected ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): Ancor Communications Inc VX229 (DFP-1): Internal TMDS ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): Ancor Communications Inc VX229 (DFP-1): 600.0 MHz maximum pixel clock ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-2: disconnected ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-3: disconnected ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-3: Internal TMDS ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select" Unfortunately this is not a gnome-shell bug and the nvidia driver version 396 is not supported yet because it's not released yet (https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-396). So we can keep discussing it here, but don't have a supported software component to blame right now. Hence the status is "Invalid". :( ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1785834 Title: Screen randomly turns black minutes after successfully login with GDM Status in gnome-shell package in Ubuntu: Invalid Bug description: Hi, Daniel van Vugt asked me to fill a new bug for the problem I have after he replied me in this old problem with GDM. https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705369 First, I will show the basic configuration of my desktop computer: -Motherboard: ROG STRIX X370-F GAMING. -CPU: Ryzen 7 1700. -GPU: GTX 1050 2GB from MSI. -Sound: Xonar DSX with ALC1220 of the motherboard deactivated. Well, the problem I have ocurrs randomly and I saw it in Ubuntu 17.10 and 18.04. In the prior version I get the typical “stopping user manager for uid” message, but in the most recent version I only see some information about storage I always see in the system boot, nothing apparently bad. I always use the official NVIDIA blob driver from the Proprietary GPU Drivers PPA, but the I also saw the bug in drivers provided by Ubuntu’s repositories. I used Linux Mint 19 for one month and I didn’t see the bug, so I think that origin is from Ubuntu’s stack. I suspect of two components and three possibilities: -GDM. -NVIDIA Prime. -Both combinanted. I’m trying a workaround setting nomodeset in the file “/etc/default/grub”. The line: ----- GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" ----- Is now: ----- GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" ----- After modify the file I executed the “sudo update-grub” command. Until now I didn’t see the bug again, but it’s too early to make sure. If I don’t see the bug again in two months I will declare the bug solved for me, but this is not the "out of the box" behavior you expect from a system like Ubuntu. Sorry if my English is hard to understand. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-07-26 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=es_ES.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1785834/+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
