!SmxNkRyYfaSczVlhFH:matrix.org

Silverblue

344 Members
Container-focused workflows for your desktop needs. Docs: https://docs.fedoraproject.org/en-US/fedora-silverblue User forums: https://discussion.fedoraproject.org/tag/silverblue Issue tracker: https://github.com/fedora-silverblue/issue-tracker/issues Dev forums: https://discussion.fedoraproject.org/tag/silverblue-team Site: https://fedoraproject.org/silverblue/42 Servers

Load older messages


SenderMessageTime
30 Nov 2023
@farribeiro:matrix.org@farribeiro:matrix.org
In reply to @sanecito:kde.org
Are there plans to release Mesa 23.3 for Fedora 39? There are a lot of enabling improvements, particularly around things like fake sparse support w/ the Intel drivers I'd like to have. Currently 39 is on Mesa 23.1 .9 and didn't do 23.2.x
just check if you have already entered bodhi
20:45:04
@farribeiro:matrix.org@farribeiro:matrix.org
In reply to @sanecito:kde.org
Are there plans to release Mesa 23.3 for Fedora 39? There are a lot of enabling improvements, particularly around things like fake sparse support w/ the Intel drivers I'd like to have. Currently 39 is on Mesa 23.1 .9 and didn't do 23.2.x
* just check if it has already entered bodhi
20:45:30
@sanecito:kde.orgsanecitoRedacted or Malformed Event20:48:45
@sanecito:kde.orgsanecitoThank you. bodhi sadly only lists it for Fedora 40 and ELN, so I'll need to jump to the rawhide tree then since 40 isn't available yet20:55:52
@sgallagh:fedora.imStephen Gallagher sanecito: Maybe see if the maintainer can backport it? It would also help fix https://bugzilla.redhat.com/show_bug.cgi?id=2247117 which is an F39 Common Bug 21:13:00
@nanonyme:matrix.orgnanonymeMaybe there's soem hard reason why Mesa has not been updated if it didn't even get 23.2.x21:13:05
@sanecito:kde.orgsanecitoIt did, I mispoke based on what GPU-Viewer told me21:13:34
@sgallagh:fedora.imStephen Gallagher nanonyme: I know for a fact that there were some issues related to llvm 17, but if it's building on F40, those must have been resolved. 21:13:35
@sanecito:kde.orgsanecitoGPU-View shows 23.1.9, glxinfo | grep -i mesa shows 23.2.121:14:34
@sanecito:kde.orgsanecito * 21:14:45
@nanonyme:matrix.orgnanonymeThe LLVM 17 Mesa issues I'm aware of is that clover didn't build. But I also read clover while it now builds has heavy regressions with LLVM 1721:15:59
@sanecito:kde.orgsanecitoimage.png
Download image.png
21:16:28
@sanecito:kde.orgsanecito(Just as a point of reference; doesn't matter as I have the answer I need: no 23.3 plans for 39, only 40 and Rawhide)21:17:10
@sgallagh:fedora.imStephen Gallagher sanecito: Update? https://bodhi.fedoraproject.org/updates/FEDORA-2023-86e10b6cae says 23.2.1 is available 21:17:27
@sgallagh:fedora.imStephen Gallagher * sanecito: Update? https://bodhi.fedoraproject.org/updates/FEDORA-2023-86e10b6cae says 23.2.1 is available for F39 21:17:56
@sanecito:kde.orgsanecitoYeah, it's a bug with GPU-Viewer; glxinfo | grep -i mesa shows 23.2.1. Something for me to file later21:18:33
@nanonyme:matrix.orgnanonymeYay, that GPUCache issue keeps on giving21:18:38
@sanecito:kde.orgsanecitoIt would be nice if GNOME System Info listed Mesa version alongside Kernel version so 3rd party software wasn't needed for basic system driver info, but that's neither here nor there21:22:42
@sanecito:kde.orgsanecito * 21:23:55
@sanecito:kde.orgsanecito * 21:29:06
@yukidream:matrix.orgyukidream
In reply to @sanecito:kde.org
sent an image.
did you use gpu viewer flathub package?
23:13:30
1 Dec 2023
@idkrn:envs.netidkrn
In reply to @Zlopez:matrix.org
idkrn: It's better to do this in toolbox on Silverblue
I was going to do it on a fedora VM but that seems better
03:15:02
@dngray:polarbear.armydngray (Ursus maritimus) changed their display name from dngray to dngray (Ursus maritimus).10:43:16
@miguelfito:matrix.orgMiguel Ángel Melón Pérez joined the room.16:53:31
@chile09:matrix.orgrolodondo34 joined the room.18:32:07
@llothar:matrix.orgLLothar joined the room.21:20:58
@jnglrobba:matrix.orgjunglerobba joined the room.21:25:43
@orowith2os:fedora.imRika (she/her)Has anybody noticed that podman likes to break on upgrades with Rawhide?21:55:08
@orowith2os:fedora.imRika (she/her)

for some reason I'm also getting this error now.

❯ podman container list
ERRO[0000] running `/usr/bin/newuidmap 6183 0 1000 1 1 100000 65536`: newuidmap: write to uid_map failed: Operation not permitted 
Error: cannot set up namespace using "/usr/bin/newuidmap": should have setuid or have filecaps setuid: exit status 1
21:55:38
@orowith2os:fedora.imRika (she/her) looks like a solution for non-ostree systems is to rpm --restore shadow-utils, but an rpm-ostree reset doesn't do anything. 22:15:29

There are no newer messages yet.


Back to Room ListRoom Version: 5