Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2046147 - Xorg crashes with NVIDIA closed source driver in Present code
Summary: Xorg crashes with NVIDIA closed source driver in Present code
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Olivier Fourdan
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2047986 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-26 10:16 UTC by Olivier Fourdan
Modified: 2022-02-13 01:06 UTC (History)
12 users (show)

Fixed In Version: xorg-x11-server-1.20.14-3.fc35 xorg-x11-server-1.20.14-3.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-01 01:12:06 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
freedesktop.org Gitlab xorg xserver merge_requests 857 0 None opened [Backport to 1.20] present: Check for NULL to prevent crash 2022-01-26 10:17:03 UTC

Description Olivier Fourdan 2022-01-26 10:16:37 UTC 
Description of problem:

Xorg will crash with (recent) NVIDIA closed-source driver in Present code as reported upstream in https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275

Version-Release number of selected component (if applicable):

xorg-x11-server-1.20.14-1

How reproducible:

Always using a compositor using Present

Steps to Reproduce:
1. Install NVIDIA driver series 495 or later
2. Install xfce
3. Configure xfwm4 to use Present for vsync

   xfwm4 -r -b xpresent

Actual results:

Xorg crashes in Present code

Expected results:

No crash.

Additional info:
Comment 1 Fedora Update System 2022-01-28 11:51:13 UTC 
FEDORA-2022-a2017f20aa has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a2017f20aa
Comment 2 Fedora Update System 2022-01-28 12:23:19 UTC 
FEDORA-2022-399e4025dd has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-399e4025dd
Comment 3 Fedora Update System 2022-01-29 15:41:38 UTC 
FEDORA-2022-399e4025dd has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-399e4025dd`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-399e4025dd

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Olivier Fourdan 2022-01-31 07:49:22 UTC 
*** Bug 2047986 has been marked as a duplicate of this bug. ***
Comment 5 Fedora Update System 2022-02-01 01:12:06 UTC 
FEDORA-2022-a2017f20aa has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 6 Fedora Update System 2022-02-13 01:06:08 UTC 
FEDORA-2022-399e4025dd has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.