Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#61057 - [nvidia]X.org server CRASH with nvidia driver
Attached to Project:
Arch Linux
Opened by Jamp (jamp) - Thursday, 13 December 2018, 10:18 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 15 December 2019, 16:40 GMT
Opened by Jamp (jamp) - Thursday, 13 December 2018, 10:18 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 15 December 2019, 16:40 GMT
|
DetailsDescription:
As already reported in the issue #60634 there is a problem in the NVidia driver (415.22 for example), at least on my Asus NV750JV with a NVIDIA 840M card. If I try to load this page with Firefox (63 or 64, don't know for previous versions) https://www.ktm.com/en/travel/790-adventure-r/ the server crashes. This is probably due to the driver. The same does not happen on a Toshiba with a NVidia 710M that uses the 390.xx driver. Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: Go to https://www.ktm.com/en/travel/790-adventure-r/ and scroll to the bottom. The Xorg crashes. |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Sunday, 15 December 2019, 16:40 GMT
Reason for closing: Works for me
Additional comments about closing: Can't reproduce and also it's very unlikely that we can fix this at a packaging level. If the issue remains, please contact NVIDIA directly.
Sunday, 15 December 2019, 16:40 GMT
Reason for closing: Works for me
Additional comments about closing: Can't reproduce and also it's very unlikely that we can fix this at a packaging level. If the issue remains, please contact NVIDIA directly.

Is this still an issue?