When trying to open "Files", there is just a white field, and nothing else

There appears just a white field when opening “Files” app. It can be closed by clicking in the upper right corner. It has only appeared this way since a recent update. It was working normally prior to a recent update, but I can not say which update exactly as I due updates several times per day. Is it possible that others have this problem as well?

sudo dnf downgrade 'mesa*' --refresh [1]

Try to downgrade the mesa package.


  1. As a reference have a look here: https://discussion.fedoraproject.org/t/many-gnome-applications-cannot-display/155291/2` ↩︎

That seems to be the solution to the problem, as it is working again. What is “mesa” ? Is this just a temp. fix or will it remain working as usual after the next updates? is there an “official” fix for the problem, or was that the fix?
Thanks for your support / solution to this problem !

Your welcome.

It is a workaround. Keep an eye on it when updating. As long as you get the same version as it was while you updated, you should just not do it again.

Mesa is a 3D Graphic library >> https://mesa3d.org/ or Mesa (computer graphics) - Wikipedia

An official fix will be integrated in a further update. For the moment keep on the older version is the Workaround so that you can work.

2 Likes

Okay, thanks ! How can I know which / what version is the working one and which is the wrong one? I suspected it would be corrected in a new update, and thats why I was doing several updates per day, hoping it would be taken care of, but obviously it is taking a bit longer…

Thanks again

Updates go to the Updates Testing repo. You can check for an update to mesa, see if it solves your issue, and contribute your findings. Bodhi updates for the mesa package says an update is now (since 10 hours ago) available for testing.

Hi George, thanks for your input about the mesa testing… As I’m not that savvy about working with the installation of individual software programs in the konsole, I’ll just wait awhile and see what the results are before doing a normal dnf update. I don’t want to make my present situation worse by playing around with things I’m not familiar with. Hope you can appreciate that. Would rather just wait awhile until lt is approved as STABLE.

1 Like

Fair enough, but testing the pre-release a) helps reduce the delay getting approvals it successful, and b) if there is an issue it gets prompt attention while details are fresh in the mind of the developer.

Hi George, if you can give me the exact sudo commands, to install the “Test software”, I will try to run it… also how will I know what to look for as far as if it is working properly or not?
Thanks

I did a normal (command-line) update on this system and got the new mesa-25.0.7-1.fc42 version packages:

% dnf list --installed mesa-\*     
Installed packages
mesa-dri-drivers.x86_64    25.0.7-1.fc42 updates
mesa-filesystem.x86_64     25.0.7-1.fc42 updates
mesa-libEGL.x86_64         25.0.7-1.fc42 updates
mesa-libGL.x86_64          25.0.7-1.fc42 updates
mesa-libGLU.x86_64         9.0.3-6.fc42  fedora    <--- not part of the updates
mesa-libOSMesa.x86_64      25.0.7-1.fc42 updates
mesa-libgbm.x86_64         25.0.7-1.fc42 updates
mesa-va-drivers.x86_64     25.0.7-1.fc42 updates
mesa-vulkan-drivers.x86_64 25.0.7-1.fc42 updates

Quoting the Bodii page –

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn’t work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2025-df3c68a7ce 

Try opening “Files” and other Gnome applications.

Edit: updated the advisory identifier

Hi George, sorry to say, but after installing your advice, ( sudo dnf upgrade --refresh --advisory=FEDORA-2025-2c707bb4ba) the problem is back again… just a white screen again. I reinstalled the work-around again in the meantime. Maybe it is too early for the FIX to be available, in the updates. I will try again later today.
Thanks for your assistance and good will!

Did you check the installed versions after the dnf updgrade? You should be seeing the released upgrade soon.

Hi George, I just did a new dnf update, and it again went back to the problem software… “WHITE SCREEN”. So I will run the “work-around” one more time. So now after re-running the “work-around”, the normal screen appears. I don’t know when the fix will actually be available as a dnf update, that will actually correct the problem… maybe it is taking longer. Have you had this problem as well? and if so, did you get / see the fix as being available, to actually run as dnf ?

sudo dnf upgrade --refresh --advisory=FEDORA-2025-2c707bb4ba

reinstalls the broken mesa package.

this is the one you want to install.

sudo dnf upgrade --refresh  --advisory=FEDORA-2025-df3c68a7ce

This has been pushed to stable by now, so a dnf --refresh upgrade should download it too.

mesa-25.0.7-2

rpm -qa mesa\* |grep 25
mesa-filesystem-25.0.7-2.fc42.x86_64
mesa-libgbm-25.0.7-2.fc42.x86_64
mesa-dri-drivers-25.0.7-2.fc42.x86_64
mesa-libGL-25.0.7-2.fc42.x86_64
mesa-libEGL-25.0.7-2.fc42.x86_64
mesa-libEGL-devel-25.0.7-2.fc42.x86_64
mesa-libGL-devel-25.0.7-2.fc42.x86_64
mesa-libgbm-devel-25.0.7-2.fc42.x86_64
mesa-vulkan-drivers-25.0.7-2.fc42.x86_64
mesa-vdpau-drivers-25.0.7-2.fc42.x86_64
mesa-va-drivers-25.0.7-2.fc42.x86_64
mesa-libxatracker-25.0.7-2.fc42.x86_64
3 Likes

Hi Mark, thank you for the tip. I ran it as you suggested and things seem to be okay for now.

Thanks to all who have contributed to solving this problem ! This is the solution !

1 Like

HI All, sorry but I spoke too soon ! After going into the “Files” app, I realized that the “Pictures” file is not available. There comes a banner that says, Ooops, something went wrong ! Unable to find
“/home/…/Pictures”. Please check the spelling and try again. But the icon for Pictures is showing in the left hand column although with a “Triangle” and an ! in the triangle. All the other “Folders” open correctly with the relevant content. Just not the Pictures folder. I was able to add a folder labelled “Pictures”, but that has no influence over the original Folder. When opening my added folder, it just says “This folder is empty”, So I removed it.
Any ideas as to how to correct this new problem?
Greetings to all !

HI All, sorry but I spoke too soon ! After going into the “Files” app, I realized that the “Pictures” file is not available. There comes a banner that says, Ooops, something went wrong ! Unable to find
“/home/…/Pictures”. Please check the spelling and try again. But the icon for Pictures is showing in the left hand column although with a “Triangle” and an ! in the triangle. All the other “Folders” open correctly with the relevant content. Just not the Pictures folder. I was able to add a folder labelled “Pictures”, but that has no influence over the original Folder. When opening my added folder, it just says “This folder is empty”, So I removed it.
Any ideas as to how to correct this new problem?
Greetings to all !

I assume you’ve replaced your username with 3 dots. It’s confusing because two dots .. stand for parent directory in CLI like ‘cd ..’
or ‘ls -al’

You either deleted or moved the Pictures folder/directory to another location.
Check the Trash folder in “Files”
Maybe find $HOME -type d -iname pictures can find it

Move it back to $HOME/Pictures

Hi Mark, yes the dots were a replacement for my name. I didn’t realize that so many dots represent different things. It should have been … (5) dots. Any way, you were right, somehow it got into the trash / Waste Basket. I’ve since put in it into the Pictures folder again. I don’t know how it got moved out of the Pictures folder to begin with ?

Again, thanks for your support.

Best regards