When I lock the screen - After a while, Ubuntu "fires up" the fan for a couple of minutes, then completely shuts down

Asked by Vitalii Zdanovskyi on 2019-10-19

This doesn't happen every time, but about half the times, when I lock the screen (Win+L) or close the lid. My system may crash after a couple of minutes in standby mode. The fans are working at full speed for a minute or two and then the system completely shuts down. After this - I can turn the laptop on and It'll load normally (No open applications or processes are preserved, of course).
The issue only occurs when I lock the screen or close the lid on a laptop, otherwise - the system works fine.

My laptop: HP ProBook 450 G6;
My System: Ubuntu 18.04.3 LTS (Linux version 5.0.0-31-generic (buildd@lgw01-amd64-046) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #33~18.04.1-Ubuntu SMP Tue Oct 1 10:20:39 UTC 2019)

Also, I was monitoring the crash with the journactl-tool. It's tracked as *Reboot* in the system and before each crash - I see those lines in the journal:

жов 19 10:43:55 vtl-HP-ProBook-450-G6 gnome-shell[3195]: Object .Gjs_AppIndicatorIconActor__1 (0x565513113b10), has been already finalized. Impossible to set any property to it.
жов 19 10:43:55 vtl-HP-ProBook-450-G6 gnome-shell[3195]: Object .Gjs_AppIndicatorIconActor__1 (0x565512c25000), has been already finalized. Impossible to set any property to it.
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: == Stack trace for context 0x565511016340 ==
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #0 0x7ffc306a1e30 I resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7f256c6b5de0 @ 87)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #1 0x5655113a7510 i /<email address hidden>/indicatorStatusIcon.js:93 (0x7f25545bdef0 @ 58)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #2 0x7ffc306a2a10 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f256c6b5de0 @ 71)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #3 0x7ffc306a2ad0 b self-hosted:916 (0x7f256c6f12b8 @ 367)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #4 0x7ffc306a2bc0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f256c6d2230 @ 386)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #5 0x5655113a7488 i /<email address hidden>/appIndicator.js:190 (0x7f25545acbc0 @ 22)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #6 0x7ffc306a3810 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f256c6b5de0 @ 71)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #7 0x5655113a73e0 i /<email address hidden>/statusNotifierWatcher.js:219 (0x7f25545ac230 @
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #8 0x7ffc306a43f0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f256c6b5de0 @ 71)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #9 0x5655113a7368 i /<email address hidden>/extension.js:61 (0x7f255459f3c8 @ 37)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #10 0x5655113a72a8 i resource:///org/gnome/shell/ui/extensionSystem.js:83 (0x7f256c3592b8 @ 441)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #11 0x5655113a7228 i resource:///org/gnome/shell/ui/extensionSystem.js:354 (0x7f256c359d58 @ 13)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #12 0x7ffc306a50f0 b self-hosted:251 (0x7f256c6c4ab0 @ 223)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #13 0x5655113a71a8 i resource:///org/gnome/shell/ui/extensionSystem.js:353 (0x7f256c359cd0 @ 64)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #14 0x5655113a7128 i resource:///org/gnome/shell/ui/extensionSystem.js:371 (0x7f256c359de0 @ 87)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #15 0x7ffc306a65f0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f256c6d2230 @ 386)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #16 0x7ffc306a6d90 b resource:///org/gnome/shell/ui/sessionMode.js:205 (0x7f256c270120 @ 254)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #17 0x7ffc306a7a70 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f256c6b5de0 @ 71)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #18 0x5655113a6fe8 i resource:///org/gnome/shell/ui/sessionMode.js:167 (0x7f256c26ce68 @ 40)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #19 0x7ffc306a8650 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f256c6b5de0 @ 71)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 gnome-software[5158]: no app for changed <email address hidden>
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #20 0x5655113a6f40 i resource:///org/gnome/shell/ui/screenShield.js:1282 (0x7f256c252670 @ 188)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #21 0x7ffc306a9230 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f256c6b5de0 @ 71)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #22 0x5655113a6e90 i resource:///org/gnome/shell/ui/screenShield.js:1331 (0x7f256c2526f8 @ 391)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #23 0x7ffc306a9e10 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f256c6b5de0 @ 71)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #24 0x5655113a6e10 i resource:///org/gnome/shell/ui/screenShield.js:854 (0x7f256c2505e8 @ 25)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: == Stack trace for context 0x565511016340 ==
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #0 0x7ffc306a1e30 I resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7f256c6b5de0 @ 87)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #1 0x5655113a7510 i /<email address hidden>/indicatorStatusIcon.js:93 (0x7f25545bdef0 @ 58)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #2 0x7ffc306a2a10 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f256c6b5de0 @ 71)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #3 0x7ffc306a2ad0 b self-hosted:916 (0x7f256c6f12b8 @ 367)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #4 0x7ffc306a2bc0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f256c6d2230 @ 386)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #5 0x5655113a7488 i /<email address hidden>/appIndicator.js:190 (0x7f25545acbc0 @ 22)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #6 0x7ffc306a3810 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f256c6b5de0 @ 71)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #7 0x5655113a73e0 i /<email address hidden>/statusNotifierWatcher.js:219 (0x7f25545ac230 @
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #8 0x7ffc306a43f0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f256c6b5de0 @ 71)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #9 0x5655113a7368 i /<email address hidden>/extension.js:61 (0x7f255459f3c8 @ 37)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #10 0x5655113a72a8 i resource:///org/gnome/shell/ui/extensionSystem.js:83 (0x7f256c3592b8 @ 441)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #11 0x5655113a7228 i resource:///org/gnome/shell/ui/extensionSystem.js:354 (0x7f256c359d58 @ 13)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #12 0x7ffc306a50f0 b self-hosted:251 (0x7f256c6c4ab0 @ 223)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #13 0x5655113a71a8 i resource:///org/gnome/shell/ui/extensionSystem.js:353 (0x7f256c359cd0 @ 64)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #14 0x5655113a7128 i resource:///org/gnome/shell/ui/extensionSystem.js:371 (0x7f256c359de0 @ 87)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #15 0x7ffc306a65f0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f256c6d2230 @ 386)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #16 0x7ffc306a6d90 b resource:///org/gnome/shell/ui/sessionMode.js:205 (0x7f256c270120 @ 254)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #17 0x7ffc306a7a70 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f256c6b5de0 @ 71)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #18 0x5655113a6fe8 i resource:///org/gnome/shell/ui/sessionMode.js:167 (0x7f256c26ce68 @ 40)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #19 0x7ffc306a8650 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f256c6b5de0 @ 71)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #20 0x5655113a6f40 i resource:///org/gnome/shell/ui/screenShield.js:1282 (0x7f256c252670 @ 188)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #21 0x7ffc306a9230 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f256c6b5de0 @ 71)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #22 0x5655113a6e90 i resource:///org/gnome/shell/ui/screenShield.js:1331 (0x7f256c2526f8 @ 391)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #23 0x7ffc306a9e10 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f256c6b5de0 @ 71)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 org.gnome.Shell.desktop[3195]: #24 0x5655113a6e10 i resource:///org/gnome/shell/ui/screenShield.js:854 (0x7f256c2505e8 @ 25)
жов 19 10:43:55 vtl-HP-ProBook-450-G6 gnome-software[5158]: no app for changed <email address hidden>
-- Reboot --

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
actionparsnip
Solved:
2019-10-21
Last query:
2019-10-21
Last reply:
2019-10-19
Vitalii Zdanovskyi (vtl) said : #2

Got this error on dpkg -i
dpkg: dependency problems prevent configuration of linux-image-unsigned-5.4.0-050400rc1-lowlatency:
 linux-image-unsigned-5.4.0-050400rc1-lowlatency depends on linux-modules-5.4.0-050400rc1-lowlatency; however:
  Package linux-modules-5.4.0-050400rc1-lowlatency is not installed.

dpkg: error processing package linux-image-unsigned-5.4.0-050400rc1-lowlatency (--install):
 dependency problems - leaving unconfigured
Setting up linux-modules-5.4.0-050400rc1-generic (5.4.0-050400rc1.201909301433) ...
Setting up linux-image-unsigned-5.4.0-050400rc1-generic (5.4.0-050400rc1.201909301433) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.0.0-31-generic
I: /initrd.img.old is now a symlink to boot/initrd.img-5.0.0-31-generic
I: /vmlinuz is now a symlink to boot/vmlinuz-5.4.0-050400rc1-generic
I: /initrd.img is now a symlink to boot/initrd.img-5.4.0-050400rc1-generic
Processing triggers for linux-image-unsigned-5.4.0-050400rc1-generic (5.4.0-050400rc1.201909301433) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-050400rc1-generic
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-050400rc1-lowlatency
Found linux image: /boot/vmlinuz-5.4.0-050400rc1-generic
Found initrd image: /boot/initrd.img-5.4.0-050400rc1-generic
Found linux image: /boot/vmlinuz-5.0.0-31-generic
Found initrd image: /boot/initrd.img-5.0.0-31-generic
Found linux image: /boot/vmlinuz-5.0.0-29-generic
Found initrd image: /boot/initrd.img-5.0.0-29-generic
Adding boot menu entry for EFI firmware configuration
done
Errors were encountered while processing:
 linux-image-unsigned-5.4.0-050400rc1-lowlatency

Vitalii Zdanovskyi (vtl) said : #4

Nope It's intel.
I was able to update the kerner afterall (Installed all except linux-image-unsigned-5.4.0-050400rc1-lowlatency )

uname -a is now showing the latest version:
Linux vtl-HP-ProBook-450-G6 5.4.0-050400rc1-generic #201909301433 SMP Mon Sep 30 18:37:54 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Since the issue isn't recurrent and happens at random times - I'd have to monitor for a while to se if it's resolved.

Are you using the system for music creation?

Vitalii Zdanovskyi (vtl) said : #6

Nope. I'm using it for web development. Haven't even launched the native Ubuntu player, not to mention creating music)

Then why are you using the lowlatency kernel?

Vitalii Zdanovskyi (vtl) said : #8

Well, Just following the advice above (Seems to be helping me so far).
Not sure if my kernel was (or is) lowlatency. I haven't updated it manually before today.

Vitalii Zdanovskyi (vtl) said : #9

UPDATE: 2 days with the newer kernel - The issue seems to be fixed. Thanks for help.

Vitalii Zdanovskyi (vtl) said : #10

Thanks actionparsnip, that solved my question.