Shell crashes and returns to the login screen

[Sergey]

from https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875435

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue May 12 14:52:03 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company TU104BM [GeForce RTX 2080 Mobile] [103c:8603]
InstallationDate: Installed on 2020-04-24 (17 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: HP OMEN by HP Laptop 17-cb0xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=c8a52116-acb9-4b90-b5b4-8f3641a10385 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/2019
dmi.bios.vendor: AMI
dmi.bios.version: F.22
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8603
dmi.board.vendor: HP
dmi.board.version: 45.41
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.41:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP OMEN
dmi.product.name: OMEN by HP Laptop 17-cb0xxx
dmi.product.sku: 5VX37AV
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

[Daniel van Vugt (vanvugt)]

Thanks for the bug reports. I don't yet fully understand what kind of problem you are trying to report, but I can see a couple of problems in the attached files:

 (1) The Nvidia driver is not properly installed and not functioning. Please uninstall the Nvidia driver and then reinstall it using the 'Additional Drivers' app. Do not install the the driver manually.

 (2) The connection to your 4K display seems faulty and constantly being redetected. That might be a cable problem or it might be a software problem caused by (1).

Please reinstall the Nvidia driver as described above, and let me know if those are not the issues you are trying to describe.

[Daniel van Vugt (vanvugt)]

Also your Intel CPU has a built-in GPU that the kernel can't seem to find. It's likely that's the only GPU wired to the laptop screen, so please look in your BIOS and make sure the integrated GPU is turned on.

[Sergey (s-n)]

1) In order to get rid of possible artifacts, I reinstalled ubuntu by re-deleting the completely old one. I also reset all BIOS settings to default, although there is no integrated GPU in it
This time nvidia-graphics-drivers-440 installed itself automatically. However, after 20 minutes of work, I was again re-logged.
Now I have 5.4.0-29-generic

2) The problem with the 4k monitor is that the ubunta does not know how to start it. Windows does this without problems in ubuntu, it remains black when turned on and writes NO SIGNAL, the only way to start it is to get it and insert the HDMI cable back

[Daniel van Vugt (vanvugt)]

Thanks.

(1) Solved. I can see the Nvidia driver is now loaded.

(2) Please run:

    xrandr --verbose > xrandr.txt
    lspci -k > lspcik.txt

    and attach the resulting text files.

(3) Please also attach the files from /usr/share/X11/xorg.conf.d/

[Sergey (s-n)]

Should I send you more journalctl reports when this situation happens?

[Daniel van Vugt (vanvugt)]

No please don't send any more journalctl reports.

What I can see now is that you have a 4K monitor connected via HDMI that's scaled to 8K:

HDMI-0 connected 7680x4320+3840+0 (0x1c0) normal (normal left inverted right x axis y axis) 698mm x 393mm
  ...
  3840x2160 (0x1c0) 594.000MHz +HSync +VSync *current +preferred
        h: width 3840 start 4016 end 4104 total 4400 skew 0 clock 135.00KHz
        v: height 2160 start 2163 end 2168 total 2250 clock 60.00Hz

I think that can only happen with the fractional scaling option so please turn that off:

  Settings > Screen Display > Fractional Scaling = OFF

Then restart. If the problem is still not solved after that then I ask for you to please describe it again in different words. Maybe in Russian.

[Sergey (s-n)]

I turned off scaling, but it didn’t help. Relogin happened in 20 minutes.
Now I’ll try to work without a monitor at all, but previously this didn’t help either. Relogin happened regardless of whether there is a monitor or not

[Sergey (s-n)]

Я в тех тасках которые уже закрывали как дубликаты приводил ссылки на снятые видео
Проблема в том что когда я работаю совершенно с разными приложениями, вдруг система подвисает на короткий миг а потом показывает сного экран логина. Если залогинится то все открытые приложения уже не работают - закрыты, но все сервисы продолжают работать (например докер)
Проблема как я заметил не зависит от типа драйвера или подключения монитора. Я возможно ошибаюсь, но мне кажется тут что то с сессиями gdm3. Однако чисто визуально готов подтвердить что при отключенном втором мониторе проблема случается реже.

Добавлю что сегодня, после того как отключил второй монитор - проблему не наблюдал.

[Sergey (s-n)]

Yesterday without monitors it worked stably, but today they relogin several times again

[Daniel van Vugt (vanvugt)]

Oh... "relogin" as in your session freezes, vanishes, and you are returned to the login screen. That means something has crashed so to help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Sergey (s-n)]

Today, such a crash happened to me 3 times, but I was not asked to send an error and I do not see the error file for today's date.

bf78f23a-990b-11ea-a491-fa163e6cac46
This id from the last crash that is in this directory from the _usr_sbin_cupsd.0.uploaded file

But it seems to me that these crashes do not fall into this directory

[Sergey (s-n)]

This is a list of all the caches, should you send any specific ones?

-rw-r----- 1 sealse whoopsie 94409341 мая 17 17:31 _opt_google_chrome_chrome.1000.crash
-rw-rw-r-- 1 sealse whoopsie 0 мая 13 23:37 _opt_google_chrome_chrome.1000.upload
-rw------- 1 whoopsie whoopsie 37 мая 13 23:38 _opt_google_chrome_chrome.1000.uploaded
-rw-r----- 1 sealse whoopsie 10579493 мая 14 12:32 _usr_bin_gnome-control-center.1000.crash
-rw-r--r-- 1 sealse whoopsie 0 мая 14 12:32 _usr_bin_gnome-control-center.1000.upload
-rw------- 1 whoopsie whoopsie 37 мая 14 12:32 _usr_bin_gnome-control-center.1000.uploaded
-rw-r----- 1 sealse whoopsie 56266105 мая 14 00:10 _usr_bin_gnome-shell.1000.crash
-rw-rw-r-- 1 sealse whoopsie 0 мая 13 23:07 _usr_bin_gnome-shell.1000.upload
-rw------- 1 whoopsie whoopsie 37 мая 13 23:07 _usr_bin_gnome-shell.1000.uploaded
-rw-r----- 1 gdm whoopsie 23012679 мая 16 14:18 _usr_bin_gnome-shell.125.crash
-rw-r--r-- 1 gdm whoopsie 0 мая 16 14:18 _usr_bin_gnome-shell.125.upload
-rw------- 1 whoopsie whoopsie 37 мая 16 14:18 _usr_bin_gnome-shell.125.uploaded
-rw-r----- 1 sealse whoopsie 12441624 мая 15 20:47 _usr_bin_gnote.1000.crash
-rw-r--r-- 1 sealse whoopsie 0 мая 15 20:47 _usr_bin_gnote.1000.upload
-rw------- 1 whoopsie whoopsie 37 мая 15 20:47 _usr_bin_gnote.1000.uploaded
-rw-r----- 1 sealse whoopsie 227722 мая 13 22:05 _usr_bin_guake.1000.crash
-rw-rw-r-- 1 sealse whoopsie 0 мая 13 22:05 _usr_bin_guake.1000.upload
-rw------- 1 whoopsie whoopsie 37 мая 13 22:05 _usr_bin_guake.1000.uploaded
-rw-r----- 1 sealse whoopsie 627918 мая 13 23:13 _usr_bin_ibus-daemon.1000.crash
-rw-rw-r-- 1 sealse whoopsie 0 мая 13 23:13 _usr_bin_ibus-daemon.1000.upload
-rw------- 1 whoopsie whoopsie 37 мая 13 23:13 _usr_bin_ibus-daemon.1000.uploaded
-rw-r----- 1 sealse whoopsie 2417077 мая 14 12:37 _usr_bin_pulseaudio.1000.crash
-rw-r--r-- 1 sealse whoopsie 0 мая 14 12:37 _usr_bin_pulseaudio.1000.upload
-rw------- 1 whoopsie whoopsie 37 мая 14 12:37 _usr_bin_pulseaudio.1000.uploaded
-rw-r----- 1 sealse whoopsie 247322 мая 14 15:34 _usr_bin_software-properties-gtk.1000.crash
-rw-r--r-- 1 sealse whoopsie 0 мая 14 15:34 _usr_bin_software-properties-gtk.1000.upload
-rw------- 1 whoopsie whoopsie 37 мая 14 15:34 _usr_bin_software-properties-gtk.1000.uploaded
-rw-r----- 1 sealse whoopsie 3274882 мая 14 19:50 _usr_bin_synapse.1000.crash
-rw-r--r-- 1 sealse whoopsie 0 мая 14 00:09 _usr_bin_synapse.1000.upload
-rw------- 1 whoopsie whoopsie 37 мая 14 00:09 _usr_bin_synapse.1000.uploaded
-rw-r----- 1 sealse whoopsie 15701256 мая 13 21:48 _usr_bin_update-manager.1000.crash
-rw-rw-r-- 1 sealse whoopsie 0 мая 13 21:48 _usr_bin_update-manager.1000.upload
-rw------- 1 whoopsie whoopsie 37 мая 13 21:48 _usr_bin_update-manager.1000.uploaded
-rw-r----- 1 sealse whoopsie 1448392 мая 13 23:45 _usr_bin_vim.basic.1000.crash
-rw-rw-r-- 1 sealse whoopsie 0 мая 13 23:45 _usr_bin_vim.basic.1000.upload
-rw------- 1 whoopsie whoopsie 37 мая 1...

[Sergey (s-n)]

sudo cat /var/lib/whoopsie/whoopsie-id

e847d46fc81152758bc93994b29424d066b0da0af35faa2e46bf08feea7dcbebaa492cb2ce4934d752cba70dfac2573ef4025974be0ee563647520648404bf0d

[Sergey (s-n)]

After the next crash, the file for today appeared
I did sudo ubuntu-bug _usr_sbin_cupsd.0.crash
But I don’t see him here https://errors.ubuntu.com/user/e847d46fc81152758bc93994b29424d066b0da0af35faa2e46bf08feea7dcbebaa492cb2ce4934d752cba70dfac2573ef4025974be0ee563647520648404bf0d
I also don’t see the files for yesterday

[Daniel van Vugt (vanvugt)]

gnome-shell looks like the relevant crash here. I can see it is crashing for you almost daily. Unfortunately none of those crashes are traceable, which is a common problem with the Nvidia driver :(

Please check that you don't have any nonstandard gnome-shell extensions installed, by running:

  gsettings list-recursively org.gnome.shell > settings.txt

and then attach the resulting text file here.

[Daniel van Vugt (vanvugt)]

Thanks. Please continue repeating the steps in comment #28 whenever the problem happens.

[Sergey (s-n)]

There are a lot of files, do you have to repeat any specific or new ones?
Yesterday, after a problem, I did "sudo ubuntu-bug * .crash" - is that right?

[Daniel van Vugt (vanvugt)]

I suggest you start by deleting all the crash files. Then you will only see the new crashes.

[Sergey (s-n)]

I sent _usr_lib_xorg_Xorg.0.crash

[Daniel van Vugt (vanvugt)]

Can you please share a link to where it was reported?

[Sergey (s-n)]

How do I get this link?
Isn't that what you need? (https://errors.ubuntu.com/user/e847d46fc81152758bc93994b29424d066b0da0af35faa2e46bf08feea7dcbebaa492cb2ce4934d752cba70dfac2573ef4025974be0ee563647520648404bf0d)

[Sergey (s-n)]

just repeated, tried to send again "sudo ubuntu-bug *_usr_lib_xorg_Xorg.0.crash"
Seems to have appeared here https://errors.ubuntu.com/user/e847d46fc81152758bc93994b29424d066b0da0af35faa2e46bf08feea7dcbebaa492cb2ce4934d752cba70dfac2573ef4025974be0ee563647520648404bf0d

[Sergey (s-n)]

sudo ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.0.crash

[Daniel van Vugt (vanvugt)]

Thanks. That most recent crash is Xorg crashing in:

?? ()
GetPointerEvents ()
QueuePointerEvents ()
?? () from /usr/lib/xorg/modules/input/libinput_drv.so
?? () from /usr/lib/xorg/modules/input/libinput_drv.so

[Daniel van Vugt (vanvugt)]

It might be related to bug 1733292 or bug 1868519.

[Sergey (s-n)]

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1885272

[Sergey (s-n)]

Hi Daniel!
Tell me how can I solve this problem
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1868519
More than half a year has already passed and I still absolutely cannot use
my laptop for Ubuntu
I could even write this letter only from the 5th time, the system
constantly overloaded the desktop

пн, 25 мая 2020 г. в 05:55, Daniel van Vugt <email address hidden>:

> It might be related to bug 1733292 or bug 1868519.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1878193
>
> Title:
> Shell crashes and returns to the login screen
>
> Status in xorg-server package in Ubuntu:
> Incomplete
>
> Bug description:
> from https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875435
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: xorg 1:7.7+19ubuntu14
> ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
> Uname: Linux 5.4.0-31-generic x86_64
> ApportVersion: 2.20.11-0ubuntu27
> Architecture: amd64
> BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
> CasperMD5CheckResult: skip
> CompositorRunning: None
> CurrentDesktop: ubuntu:GNOME
> Date: Tue May 12 14:52:03 2020
> DistUpgraded: Fresh install
> DistroCodename: focal
> DistroVariant: ubuntu
> GraphicsCard:
> NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev
> a1) (prog-if 00 [VGA controller])
> Subsystem: Hewlett-Packard Company TU104BM [GeForce RTX 2080 Mobile]
> [103c:8603]
> InstallationDate: Installed on 2020-04-24 (17 days ago)
> InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
> MachineType: HP OMEN by HP Laptop 17-cb0xxx
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic
> root=UUID=c8a52116-acb9-4b90-b5b4-8f3641a10385 ro quiet splash vt.handoff=7
> SourcePackage: xorg
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 12/09/2019
> dmi.bios.vendor: AMI
> dmi.bios.version: F.22
> dmi.board.asset.tag: Base Board Asset Tag
> dmi.board.name: 8603
> dmi.board.vendor: HP
> dmi.board.version: 45.41
> dmi.chassis.type: 10
> dmi.chassis.vendor: HP
> dmi.chassis.version: Chassis Version
> dmi.modalias:
> dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.41:cvnHP:ct10:cvrChassisVersion:
> dmi.product.family: 103C_5335KV HP OMEN
> dmi.product.name: OMEN by HP Laptop 17-cb0xxx
> dmi.product.sku: 5VX37AV
> dmi.sys.vendor: HP
> version.compiz: compiz N/A
> version.libdrm2: libdrm2 2.4.101-2
> version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
> version.libgl1-mesa-glx: libgl1-mesa-glx N/A
> version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
> version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
> version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
> version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20200226-1
> version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/...

[Daniel van Vugt (vanvugt)]

Since this bug looks similar to other crashes reported against the Nvidia driver I would try to avoid the Nvidia driver (and the whole Nvidia GPU) if you want more stability, for the moment.

Your i9-9880H has an Intel GPU built in. If you can disable Nvidia in the BIOS and enable Intel graphics then I think that might avoid these crashes.

Also this bug is still incomplete... we don't have a usable stack trace. So please continue following the steps in comment #28.

[Launchpad Janitor (janitor)]

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]