Bug 2191745 - Downgrading mesa-dri-drivers breaks Wayland/X
Summary: Downgrading mesa-dri-drivers breaks Wayland/X
Keywords:
Status: CLOSED DUPLICATE of bug 2187726
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 38
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-28 23:55 UTC by Felix Kaechele
Modified: 2023-05-03 10:36 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-03 10:36:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Felix Kaechele 2023-04-28 23:55:09 UTC
Downgrading mesa-dri-drivers leads to a situation where the GNOME Wayland Session no longer starts. The error message suggest it is due to a version mismatch of the mesa build and the drivers.
This is due to the fact that downgrading mesa-dri-drivers only downgrades mesa-filesystem with it but none of the other mesa libraries. All mesa packages that require version matching should depend on appropriately strict NEVRs of their actual dependencies.

Reproducible: Always

Steps to Reproduce:
1. dnf downgrade mesa-dri-drivers
2. Reboot
3. GNOME Session fails to start, failsafe Xorg server starts ("Oh no! Something has gone wrong")
Actual Results:  
Wayland fails to launch due to driver and mesa version mismatch.

Expected Results:  
dnf downgrade mesa-dri-drivers will downgrade all dependent packages with it and the system will remain in a functional state.

Log:
Apr 28 19:36:21 x1.home.kaechele.ca gnome-shell[1782]: Running GNOME Shell (using mutter 44.1) as a Wayland display server
Apr 28 19:36:22 x1.home.kaechele.ca org.gnome.Shell.desktop[1782]: DRI driver not from this Mesa build ('23.0.1' vs '23.0.3')
Apr 28 19:36:22 x1.home.kaechele.ca org.gnome.Shell.desktop[1782]: failed to bind extensions
Apr 28 19:36:22 x1.home.kaechele.ca org.gnome.Shell.desktop[1782]: DRI driver not from this Mesa build ('23.0.1' vs '23.0.3')
Apr 28 19:36:22 x1.home.kaechele.ca org.gnome.Shell.desktop[1782]: failed to bind extensions
Apr 28 19:36:22 x1.home.kaechele.ca org.gnome.Shell.desktop[1782]: DRI driver not from this Mesa build ('23.0.1' vs '23.0.3')
Apr 28 19:36:22 x1.home.kaechele.ca org.gnome.Shell.desktop[1782]: failed to bind extensions
Apr 28 19:36:22 x1.home.kaechele.ca org.gnome.Shell.desktop[1782]: DRI driver not from this Mesa build ('23.0.1' vs '23.0.3')
Apr 28 19:36:22 x1.home.kaechele.ca org.gnome.Shell.desktop[1782]: failed to bind extensions
Apr 28 19:36:22 x1.home.kaechele.ca gnome-shell[1782]: Failed to open gpu '/dev/dri/card1': Failed to initialize render device for /dev/dri/card1: Failed to create gbm device: Illegal seek, EGLDevice currently o>
Apr 28 19:36:22 x1.home.kaechele.ca org.gnome.Shell.desktop[1782]: Failed to setup: No GPUs found
Apr 28 19:36:22 x1.home.kaechele.ca gnome-session[1757]: gnome-session-binary[1757]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Apr 28 19:36:22 x1.home.kaechele.ca gnome-session-binary[1757]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Apr 28 19:36:22 x1.home.kaechele.ca gnome-session-binary[1757]: Unrecoverable failure in required component org.gnome.Shell.desktop

Fixing this bug may also aid in fixing issues with mesa drivers from third party repositories not properly conflicting with newer mesa libraries.

Comment 1 Kamil Páral 2023-05-03 10:36:20 UTC
This is fixed in mesa 23.0.3. Uninstall rpmfusion drivers, fully update, and wait for rpmfusion to catch up. A longer description is here:
https://bugzilla.rpmfusion.org/show_bug.cgi?id=6664#c4
and here:
https://discussion.fedoraproject.org/t/gnome-login-screen-might-not-start-when-mesa-va-drivers-freeworld-from-rpmfusion-are-installed/81856

Comment 2 Kamil Páral 2023-05-03 10:36:58 UTC
Closing as a duplicate of bug 2187726.

*** This bug has been marked as a duplicate of bug 2187726 ***


Note You need to log in before you can comment on or make changes to this bug.