X server segfault when starting youtube videos

[clepsdyrae]

This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%).

Stack trace in Xorg.0.log.old is always the same:

[ 1890.850] (EE)
[ 1890.850] (EE) Backtrace:
[ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9]
[ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520]
[ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9]
[ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85]
[ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183]
[ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183]
[ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d]
[ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c]
[ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c41ffff21]
[ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e]
[ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60]
[ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8]
[ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257]
[ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524]
[ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90]
[ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40]
[ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5]
[ 1890.855] (EE)
[ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000
[ 1890.855] (EE)
Fatal server error:
[ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0000.01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.141.03 Thu Jun 30 18:45:31 UTC 2022
 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Sat Nov 5 10:27:18 2022
DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000]
 NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281]
InstallationDate: Installed on 2020-04-27 (921 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=30826023-39fe-4d5c-8720-a3a2d86c4839 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=8M mtrr_chunk_size=32M quiet splash nomodeset vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to jammy on 2022-05-14 (174 days ago)
dmi.bios.date: 03/18/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87X-UD3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd03/18/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnZ87X-UD3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87X-UD3H-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Z87X-UD3H
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. 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.

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.

[clepsdyrae (myopenid)]

Crash just happened again (this time watching a video on reddit, not youtube.)

There are three resulting files in /var/crash:

2022-11-17 09:43:59 _usr_bin_kwin_x11.1000.crash
2022-11-17 09:43:54 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash
2022-11-17 09:43:53 _usr_lib_xorg_Xorg.0.crash

...I did "ubuntu-bug filename" for each one of them, and that seemed to work fine, but there was no ID reported to me of the newly-created bug, so I can't report that per the instructions above. How do I discover this in order to report it?

I could also post those files somewhere, if it's not a big security risk.

ubuntu-bug was run roughly at 2022-11-17 17:45:00 UTC, if that helps.

I checked the whoopsie link and there were no relevant crashes there that I could find.

[clepsdyrae (myopenid)]

I just noticed /var/crash/_usr_bin_kwin_x11.1000.uploaded -- is that the ID? That file contains:

c59a5430-676f-11ed-a93a-fa163e55efd0

Also, just had another crash -- this time I have compiled everything in /var/crash and uploaded to this link: https://drive.google.com/file/d/1TAKFU9t72iwJT33j8nfgt3fhaYTPHplP/view?usp=sharing

(...let me know if there are substantial security concerns with that. I perused those files and it didn't look too bad.)

[Daniel van Vugt (vanvugt)]

c59a5430-676f-11ed-a93a-fa163e55efd0 is a crash in KWin:

https://errors.ubuntu.com/bucket/?id=/usr/bin/kwin_x11%3A11%3AKWin%3A%3AWorkspace%3A%3AworkspaceEvent%3AQAbstractEventDispatcher%3A%3AfilterNativeEvent%3AQXcbConnection%3A%3AhandleXcbEvent%3AQXcbConnection%3A%3AprocessXcbEvents%3AQXcbUnixEventDispatcher%3A%3AprocessEvents

Judging by the timestamps in comment #3 however that should be ignored (from our perspective) because Xorg crashed first.

[Daniel van Vugt (vanvugt)]

The nvidia-470 driver sounds old and NVIDIA themselves seem to recommend driver 515 instead for your GPU.

Please open the Additional Drivers app and try installing a newer NVIDIA driver.

[clepsdyrae (myopenid)]

Oops, didn't realize I was behind on the driver, sorry. I'm on 515 now. I'll report back soon(ish) with results. Thanks.

[clepsdyrae (myopenid)]

Crash just happened again (with nvidia 515 drivers).

Here's the Xorg crash; let me know if you want any of the others:

https://drive.google.com/file/d/19qiKkTHZH5iuxUpmMTmxjn5fTZpg-RVc/view?usp=share_link

I tried ubuntu-bug, but it generated a 0-length .upload file so I have no ID.

[Daniel van Vugt (vanvugt)]

Please upload crash files using ubuntu-bug, or try apport-cli if that fails.

[clepsdyrae (myopenid)]

I have tried both ubuntu-bug and apport-cli; they both just return without generating an ID number (that I'm aware of), and /var/crash/_usr_lib_xorg_Xorg.0.upload is zero-length:

---------------

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

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (5.8 MB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): s
# ls -lah /var/crash/_usr_lib_xorg_Xorg.0.upload
-rw-r--r-- 1 root whoopsie 0 Dec 8 11:52 /var/crash/_usr_lib_xorg_Xorg.0.upload
#

------------------

Is there something wrong with my approach there?

[Daniel van Vugt (vanvugt)]

Try looking for /var/crash/*.uploaded and check the contents of those files.

Also try step 2 from comment #2.

[clepsdyrae (myopenid)]

Thanks -- the .upload file is zero-length (see previous comment for how I determined that.) There are no *.uploaded files present.

The GUI version of the crash reporter also came up and I submitted all of those.

The errors.ubuntu.com page for the whoopsie ID has none of the recent crashes shown (last one November 17th).

[Daniel van Vugt (vanvugt)]

Alright we can give up on the automated crash reports for now.

Next would be to improve the quality of the stack trace that Xorg writes to its log. You can do that by installing the debug symbols packages. Assuming your system is fully up to date:

  sudo apt update
  sudo apt full-upgrade

then next install the "dbgsym" files from:

https://launchpad.net/ubuntu/+source/xorg-server/2:21.1.3-2ubuntu2.4/+build/24877323

[Daniel van Vugt (vanvugt)]

Oh actually not being fully up to date might make your crash reports get rejected. Please do:

  sudo apt update
  sudo apt full-upgrade

and reboot.

[clepsdyrae (myopenid)]

Thanks, will do -- should I install all five dbgsym .ddeb files that I see there?

[Daniel van Vugt (vanvugt)]

I think you probably only need https://launchpad.net/ubuntu/+source/xorg-server/2:21.1.3-2ubuntu2.4/+build/24877323/+files/xserver-xorg-core-dbgsym_21.1.3-2ubuntu2.4_amd64.ddeb assuming that's the version of xserver-xorg-core already installed.

[clepsdyrae (myopenid)]

Thanks -- after updating and reboot I now have ".uploaded" files.

_usr_lib_xorg_Xorg.0.uploaded: c0b761f4-7781-11ed-b5f8-fa163ef35206

I have installed that .ddeb and will report when/if another crash happens (it is indeed the same version).

[Daniel van Vugt (vanvugt)]

Thanks. That crash is now being tracked in bug 1999213.

[clepsdyrae (myopenid)]

Thank you -- let me know if there's anything else I can do to help.

Would crash reports from me be useful at this point or should I uninstall those debug symbols?

[Daniel van Vugt (vanvugt)]

Keep reporting crashes in case your system is experiencing multiple different ones.

And it doesn't affect the system whether you leave the debug symbols installed or not. Though keeping them installed should help the stack traces in your logs to make more sense.

[clepsdyrae (myopenid)]

Ok, I'll report any further crashes (here, I assume). Thanks for your attention to it!

[clepsdyrae (myopenid)]

Got a crash this morning. Debug symbols are installed. Stack trace looks the same as before:

724f4d3a-8792-11ed-aab2-fa163e55efd0

[clepsdyrae (myopenid)]

Another crash: c4ba5026-8a1d-11ed-aac8-fa163e55efd0

[clepsdyrae (myopenid)]

Another crash: f7aa5c24-8c5c-11ed-9ccf-fa163e993415

[Daniel van Vugt (vanvugt)]

Yes the above three crashes are all bug 1999213.

[clepsdyrae (myopenid)]

Thank you -- I'll keep reporting them here unless otherwise directed.

[clepsdyrae (myopenid)]

(Oh by the way -- does the stack trace suggest any kind of workaround worth trying? Since it can result in loss of work I'd love to prevent it if possible.)

[Daniel van Vugt (vanvugt)]

It looks like the crash reports went silent in Ubuntu 22.10 so maybe you should try that.

[Daniel van Vugt (vanvugt)]

Confirmed (by upstream) fixed in Xorg 21.1.4 (Ubuntu 22.10)

[clepsdyrae (myopenid)]

Thanks -- great to know. Do you know if the fix will be brought into 22.04 ?

And thanks for the help on it.

[clepsdyrae (myopenid)]

Another crash: e2cad21a-91d2-11ed-9d18-fa163e993415

(I'm probably going to upgrade to 22.10 today so presumably I won't have any more.)

[Daniel van Vugt (vanvugt)]

Yes that's still bug 1999213.