Screen randomly turns black minutes after successfully login with GDM

Bug #1785834 reported by Eduardo Medina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
Undecided
Unassigned

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

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1785834

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

tags: added: bionic
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
tags: added: black-screen
Revision history for this message
Eduardo Medina (no-more-hopes) wrote : Dependencies.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Eduardo Medina (no-more-hopes) wrote : ProcCpuinfoMinimal.txt

apport information

Changed in gnome-shell (Ubuntu):
status: Incomplete → New
Revision history for this message
Eduardo Medina (no-more-hopes) wrote :

Sorry, but I forgot one thing.

When the screen turns black, I can recover the graphical session switching between a virtual console and the console that is supporting the graphical session with alt+control+f5 and alt+control+f2 or alt+control+f1.

No issues with nomodeset so far.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Interesting. That sounds similar to bug 1786872.

Are you sure your bug title is correct?

  "Screen randomly turns black minutes after
   successfully login with GDM"

Have you really logged in with your username and password *before* the bug occurs? Or do you just mean the machine has booted when you say "login"?

tags: added: nvidia
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Eduardo Medina (no-more-hopes) wrote :

When the screen turns black I'm using the GNOME session as usual. I'm working with my common apps (Dropbox, LibreOffice, Visual Studio Code and/or Audacious... ) normally until the screen suddenly turns black without any previous warning.

After the screen turn black, I switch to a virtual console that works as usual, and after I come back to the console where the graphical session is loaded and everything is in the same place that before the black screen.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. Next, please reproduce the problem and then in the virtual console run:

  journalctl -b > journal.txt
  dmesg > dmesg.txt
  dpkg -l > dpkgl.txt

Now return to the graphical session and send us the files 'journal.txt', 'dmesg.txt' and 'dpkgl.txt'

Revision history for this message
Eduardo Medina (no-more-hopes) wrote :

OK. I will try to reproduce the error.

Revision history for this message
Eduardo Medina (no-more-hopes) wrote :

OK, I have the three files. I hope to give useful information.

The last time I had the bug, I saw that the graphical session switched automatically to the "alt+ctrl+F1" virtual console and after returned to "alt+ctrl+F2" virtual console.

Revision history for this message
Eduardo Medina (no-more-hopes) wrote :
Revision history for this message
Eduardo Medina (no-more-hopes) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.