Recently I ran "dnf upgrade" on a Fedora 41 VM running in VMWare Fusion (on Mac). After restarting, the virtual console went black after gdm started. Gdm was running, because I was able to type my password and start a console session, even though the screen stayed black the entire time. (I logged in to the VM with ssh and confirmed that a console login session had started.) The systemd journal shows gnome-shell errors: gnome-shell[1285]: Failed to query buffer age, got error 3003 gnome-shell[1285]: Failed to lock front buffer on /dev/dri/card0: gbm_surface_lock_front_buffer failed Someone else observed this exact problem (in a VirtualBox VM rather than VMWare) and reported a gnome-shell bug, which was switched to a mutter bug since the messages come from libmutter: https://gitlab.gnome.org/GNOME/mutter/-/issues/3851 The comments on the bug noted that the 3003 error is EGL_BAD_ALLOC, and that implies a problem in the driver. I tried downgrading mesa: sudo dnf downgrade --allowerasing --allow-downgrade mesa-dri-drivers That downgraded mesa from version 24.3.2 to 24.2.4, and Wayland started working again. (Note that X still works fine on the VM with mesa 24.3.2, so that's a workaround for the console issue -- you have to edit /etc/gdm/custom.conf and disable Wayland.) I had some free time, so I ran some bisection on mesa versions. I found that the problem started in mesa version 24.3.1. If I have time later, I'll try bisecting the git commits in mesa between 24.3.0 and 24.3.1. Reproducible: Always Steps to Reproduce: 1. Upgrade a VM to mesa 24.3.2 by running "dnf upgrade" on Fedora 41. 2. Reboot the VM. 3. Wait for Plymouth to finish and for gdm to start. Actual Results: Screen goes black. Expected Results: The screen displays a standard gdm login prompt. I'm guessing that you can duplicate this problem on any system that uses the vmwgfx mesa driver.
Could it be a duplicated of https://bugzilla.redhat.com/show_bug.cgi?id=2333711 ? Do you see a similar error?
Yes, my bug does look to me like a duplicate of that bug. I did a search in Bugzilla but didn't find the other bug -- too bad! I'm a little puzzled that the commit that you mentioned appears in mesa 24.3.0, but 24.3.0 worked for me. I suppose I could have screwed up my test; I'll re-check.
If I remember correctly, I didn't release mesa 24.3.0 in Fedora 41, only Rawhide. So maybe you remember 24.2.8 working. Anyway, if you don't mind, I'm going to close this issue as duplicated of https://bugzilla.redhat.com/show_bug.cgi?id=2333711 to keep the conversation in a single place. *** This bug has been marked as a duplicate of bug 2333711 ***
As a workaround, in the (VirtualBox) VM settings -> display, enabling 3D acceleration might fix the issue. Not sure about what happens on Mac, but it is worth trying.
FEDORA-2025-055e8d116f (mesa-24.3.4-2.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-055e8d116f
Hi! I've pushed a new update including a fix for your issue. You can test it following the instructions available here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-055e8d116f
FEDORA-2025-055e8d116f has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-055e8d116f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-055e8d116f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I just got a chance to test the fix. It worked -- thanks!
FEDORA-2025-a24369766c (mesa-24.3.4-3.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.