[SOLVED] Screen remains black after wake up from standby

[hermann-san]

Hi,
since a couple of month I have a sporadic issue with resuming my PC from standby mode (not hibernation).
I do send my PC to sleep and the screen goes off. When I turn my PC back on, it does power on with the green LED and the fan is running, but the 2 connected screen remains black. I've tried disconnect/connect the HDMI cable, tried any key on the keyboard (incl. ctrl+alt+del) but nothing happens. Only reboot helps to get Mint starting. However, that also triggers fsck and may even corrupt files, so I don't want to keep it like that.
This doesn't happen every time but only sometimes. I've noticed that most of the times it is when I'm using my HMDI adapter / port replicator with my Laptop (see the below diagram for my hardware setup). So what I've found out is that when do put Mint into sleep, I have do wait about 10-15 sec (until both screens are actually is sleep). and only then turn on the Windows Laptop. Then again, when I switch back to Linux Mint, I do put the Windows 10 laptop into sleep, wait about 10-15 sec. until both screens are in sleep and only then wake up my Mint PC from sleep. This is a workaround that works most of the times, but not always. Similarly, sometimes I forget to apply the workaround and the Mint PC does still wake up properly anyways, but most of the times it doesn't, so that's why I always try to use the workaround. Also, this issue appeared without even having used the HDMI adapter, but it's rare.

I've only found the following 2 error messages in the log, but they don't seem to be relevant to me. I could provide a full log when Mint is crashing next time, but right now I don't have a full log, only the below 2 messages I took a note of a couple of weeks ago.

Code: Select all

Failed to start Refresh fwupd metadata and update motd
....
pulseaudio   GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)

Does someone has any idea what I could try to fix this? I suspect that something with the nvidia driver is wrong or with the kernel.
When I first installed Linux Mint 20, I didn't had that problem for several month, even with the adapter, but at some point this issue came up and I don't know what has happened right before (kernel update? nvidia update? ) I didn't update nvidia driver manually myself.
Thanks in advance for your hints and help.

Code: Select all

System:
  Kernel: 5.4.0-126-generic x86_64 bits: 64 compiler: gcc v: 9.4.0 
  Desktop: Cinnamon 4.6.7 wm: muffin 4.6.3 dm: LightDM 1.30.0 
  Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop System: MSI product: MS-7693 v: 3.0 serial: <filter> 
  Mobo: MSI model: 970A-G43 (MS-7693) v: 3.0 serial: <filter> 
  BIOS: American Megatrends v: 10.3 date: 03/28/2013 
Battery:
  Device-1: hidpp_battery_0 
  model: Logitech Marathon Mouse/Performance Plus M705 serial: <filter> 
  charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:
  Topology: 8-Core model: AMD FX-8320 bits: 64 type: MCP arch: Bulldozer 
  L2 cache: 2048 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 56006 
  Speed: 1400 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz): 
  1: 1399 2: 1399 3: 1397 4: 1395 5: 1399 6: 1399 7: 1399 8: 1390 
Graphics:
  Device-1: NVIDIA GK208 [GeForce GT 630 Rev. 2] vendor: ZOTAC 
  driver: nvidia v: 470.141.03 bus ID: 01:00.0 chip ID: 10de:1284 
  Display: x11 server: X.Org 1.20.13 driver: nvidia 
  unloaded: fbdev,modesetting,nouveau,vesa 
  resolution: 1920x1080~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: NVIDIA GeForce GT 630/PCIe/SSE2 
  v: 4.6.0 NVIDIA 470.141.03 direct render: Yes 
Audio:
  Device-1: AMD SBx00 Azalia vendor: Micro-Star MSI driver: snd_hda_intel 
  v: kernel bus ID: 00:14.2 chip ID: 1002:4383 
  Device-2: NVIDIA GK208 HDMI/DP Audio vendor: ZOTAC driver: snd_hda_intel 
  v: kernel bus ID: 01:00.1 chip ID: 10de:0e0f 
  Device-3: Plantronics type: USB driver: plantronics,snd-usb-audio,usbhid 
  bus ID: 1-1.1.3:6 chip ID: 047f:c053 serial: <filter> 
  Sound Server: ALSA v: k5.4.0-126-generic 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Micro-Star MSI driver: r8169 v: kernel port: d000 bus ID: 05:00.0 
  chip ID: 10ec:8168 
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  Device-2: Microchip (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter 
  type: USB driver: smsc95xx bus ID: 1-1.1.1:4 chip ID: 0424:ec00 
  serial: <filter> 
  IF: enx00116ba09660 state: down mac: <filter> 
  IF-ID-1: br-8ed9e780f9b5 state: up speed: N/A duplex: N/A mac: <filter> 
  IF-ID-2: docker0 state: down mac: <filter> 
  IF-ID-3: veth4912be7 state: up speed: 10000 Mbps duplex: full 
  mac: <filter> 
Drives:
  Local Storage: total: 3.17 TiB used: 2.68 TiB (84.4%) 
  ID-1: /dev/sda vendor: Kingston model: SA400S37240G size: 223.57 GiB 
  speed: <unknown> serial: <filter> rev: 62B3 scheme: GPT 
  ID-2: /dev/sdb vendor: Samsung model: SSD 750 EVO 250GB size: 232.89 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT 
  ID-3: /dev/sdc vendor: Toshiba model: DT01ACA300 size: 2.73 TiB 
  speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: ABB0 scheme: GPT 
Partition:
  ID-1: / size: 54.70 GiB used: 38.68 GiB (70.7%) fs: ext4 dev: /dev/sdb1 
  ID-2: /home size: 158.54 GiB used: 122.32 GiB (77.2%) fs: ext4 
  dev: /dev/sdb2 
  ID-3: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb3 
Sensors:
  System Temperatures: cpu: 52.0 C mobo: 52.0 C gpu: nvidia temp: 56 C 
  Fan Speeds (RPM): cpu: 1259 fan-2: 0 fan-3: 0 gpu: nvidia fan: 21% 
  Voltages: 12v: N/A 5v: N/A 3.3v: 3.12 vbat: 3.30 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/alexlarsson-flatpak-focal.list 
  1: deb http://ppa.launchpad.net/alexlarsson/flatpak/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
  1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/element-io.list 
  1: deb [signed-by=/usr/share/keyrings/element-io-archive-keyring.gpg] https://packages.element.io/debian/ default main
  Active apt repos in: /etc/apt/sources.list.d/giuspen-ppa-focal.list 
  1: deb http://ppa.launchpad.net/giuspen/ppa/ubuntu focal main
  No active apt repos in: /etc/apt/sources.list.d/jami.list 
  Active apt repos in: /etc/apt/sources.list.d/josm.list 
  1: deb [signed-by=/usr/share/keyrings/josm-archive-keyring.gpg] https://josm.openstreetmap.de/apt alldist universe
  No active apt repos in: /etc/apt/sources.list.d/linuxuprising-shutter-focal.list 
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://ftp-stud.hs-esslingen.de/pub/Mirrors/packages.linuxmint.com ulyana main upstream import backport
  2: deb http://ftp.uni-stuttgart.de/ubuntu focal main restricted universe multiverse
  3: deb http://ftp.uni-stuttgart.de/ubuntu focal-updates main restricted universe multiverse
  4: deb http://ftp.uni-stuttgart.de/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/openshot_developers-ppa-focal.list 
  1: deb http://ppa.launchpad.net/openshot.developers/ppa/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.list 
  1: deb [arch="all", signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
  Active apt repos in: /etc/apt/sources.list.d/recoll-backports-recoll-1_15-on-focal.list 
  1: deb http://ppa.launchpad.net/recoll-backports/recoll-1.15-on/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/shutter-ppa-focal.list 
  1: deb http://ppa.launchpad.net/shutter/ppa/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list 
  1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main
  Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
  1: deb [signed-by=/usr/share/keyrings/teamviewer-keyring.gpg] https://linux.teamviewer.com/deb stable main
Info:
  Processes: 371 Uptime: 7h 35m Memory: 23.43 GiB used: 5.40 GiB (23.0%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.4.0 alt: 7/8/9 
  Shell: bash v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 

[hermann-san]

today it has happened again.
Here is a log of the important messages. It looks like there was a systemd coredumb element-desktop dumped core , Stack trace of thread ...
https://pastebin.grey.pw/?66b81dd095619 ... ErEPc2t2mN

[SMG]

today it has happened again.
Here is a log of the important messages.

From where did you get that information? It seems to be missing the top part which is the part saying what caused the core dump.

since a couple of month I have a sporadic issue with resuming my PC from standby mode (not hibernation).

The workaround mentioned in this post has worked for many people. If you need detailed instructions for editing the file then see this post and the subsequent ones in that topic.

[hermann-san]

From where did you get that information? It seems to be missing the top part which is the part saying what caused the core dump.

I've got it from the Linux Mint log UI. Not sure how it's called in English (see the attached screenshot)
I've tried to get the missing part with the MInt log UI, but it seems to be buggy on my PC. Sometimes it hangs for 10-15 sec. and when I select the filter "all" and the corresponting time filter, it doesn't shows me the entries for that particular time I'm looking for. When I search for keywords "dump" , I do get results for that time frame. Very strange. I don't know any other way to get that information. I know there is dmesg, but I don't know how to get the messages from starting yesterday with it. dmesg -T only give's me messages from the last 12 hours or so.

I will try out that workaround. Thanks.

[SMG]

I've got it from the Linux Mint log UI. Not sure how it's called in English (see the attached screenshot)

It is the Log app in English.

I thought maybe you got the information from the System Reports app. It has an option at the bottom of the left panel for CrashReports (highlighted below). On the upper right pane you can select a crash report (if there is more than one) and the bottom pane will have the details including the stack traces. However, right above the stack traces will be the information on which module crashed.

[hermann-san]

right above the stack traces will be the information on which module crashed.

Element Desktop appears to be the culprit: /opt/Element/element-desktop
https://termbin.com/y99a

[SMG]

Element Desktop appears to be the culprit: /opt/Element/element-desktop

I am not familiar with that app, so I do not know if that app crashing is a factor in the problem you describe in your initial post.

[hermann-san]

am not familiar with that app, so I do not know if that app crashing is a factor in the problem you describe in your initial post.

sure, I'll remove the app if the problem is not solved with the workaround.
Thanks a lot for your help, so far.

[hermann-san]

am not familiar with that app, so I do not know if that app crashing is a factor in the problem you describe in your initial post.

until now, that fix above, for my standby issue has worked perfectly well. Thanks

[SMG]

until now, that fix above, for my standby issue has worked perfectly well. Thanks

You're welcome.

[hermann-san]

yesterday I has a strange issue with the graphics driver. I switched to another driver and back to NVidia driver. That did fix the issue somehow, but it also overwrites the changes I've made to
/usr/bin/nvidia-sleep.sh - exit 0
So "exit 0" has to be re-added to the file because it was not there anymore after the driver change.

I hope that workaround (exit 0) will still work.... I will report if not.

[SMG]

So "exit 0" has to be re-added to the file because it was not there anymore after the driver change.

Others have also posted they had to add the line again. A new driver means at least some new files so it makes sense that might happen.