Comments

29 Comments

TWIMC, updated mesa-freeworld packages for f41 are now built and available in rpmfusion's koji; they with the next push will land in the repos, too. Sorry, took a moment to get the new llvm into the builders.

Side note: some changes in mesa 24.2.3 upstream had lead other problems earlier, so we had to change the approach somewhat (thx kwizart!). Would be good if people could check if the package actually works (e.g. that it actually helps and uses the video de/encoders in the GPU)

User Icon thl commented & provided feedback on mesa-24.2.2-1.fc41 3 months ago

@jexposit funny timing coincidence. Thx for handing this to everyone involved!

User Icon thl commented & provided feedback on mesa-24.2.2-1.fc41 3 months ago

Hey @jexposit, is it intentional that some mesa-packages (like dri-drivers or va-drivers) have a dependency[1] on the filesystem subpackage, while others (like vulkan-drivers or libOpenCL) do not? That can lead to partial updates of Fedora's Mesa packages when there is a conflict[2]; and I wonder if that can cause trouble.

[1] Requires: %{name}-filesystem%{?_isa} = %{?epoch:%{epoch}:}%{version}-%{release} [2] for example for users of the 3rd party package mesa-va-drivers-freeworld, which might be newer or older in the repos sometimes for a few days.

This update has been unpushed.

This update has been unpushed.

Here's the bug report: https://bugzilla.redhat.com/show_bug.cgi?id=2235254

Same problem here. Some mails in Thunderbird look different, too

this afaics breaks mesa-va-drivers-freeworld from RPM Fusion:

Cannot find target for triple amdgcn-- Unable to find target for this triple (no targets are registered)

A rebuild will likely fix this, but the timing of the update due to the freeze for Fedora 38 makes things complicated, as this package now has to be updated in parallel to not break things for users – and that is impossible to ensure with dnf without at least temporarily causing broken deps for some users. Hence allow me to ask:

is this really a worth updating in Fedora 38? Couldn't this have been done earlier? Or not at all?

Or is a freeze exception planed for this update? That would make things a lot easier.

User Icon thl commented & provided feedback on mesa-20.3.3-3.fc33 3 years ago
karma

Thx for fixing the pidgin issue!

BZ#1912159 pidgin crashes with mesa-vulkan-drivers-20.3.2-1.fc33.x65_64
karma

Thx for taking care of this. Did a quick test, worked fine with podman-2.0.5, including sudo; and yes, the warning is still there, as you mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1873430

BZ#1867829 sudo(8) inside toolbox containers asks for a password with Podman 2.0.5
User Icon thl commented & provided feedback on podman-2.0.5-1.fc32 4 years ago
karma

TWIMC, seems this update broke toolbox partly for me, as a sudo there suddenly started asking for an password; downgrading to 2.0.4 fixed this for me.

https://bugzilla.redhat.com/show_bug.cgi?id=1873430

karma

Sorry, I should have looked more closely, it's not toolbox or this update at fault, looks like it was a podman update from 2.0.4 to 2.0.5 that broke things

karma

Toolbox worked fine for me yesterday, but today after installing this update it suddenly asks for a password when running commands with sudo (there is also a warning "/usr/bin/id: cannot find name for group ID 1000" that is new iirc). Downgrading to 0.0.93 did not help :-/

Suddenly seeing High CPU load, too. Downgrading doesn't help, so I maybe it is something external. Opening the "options" in Libreoffice helps. Others see it too: https://www.spinics.net/linux/fedora/fedora-users/msg480321.html

BZ#1413306 Pointer speed on some Dell laptops (XPS 13, Precision 5510...) too slow with recent libinput (inc. 1.6)