Security Vulnerabilities fixed in Firefox 150.0.2: https://www.mozilla.org/en-US/security/advisories/mfsa2026-40/

Both "Stable by Karma" and "Stable by Time" are disabled; is this intentional?

Firefox 150 fixes multiple security vulnerabilities, and it's been released almost a week ago; how come it's still not in stable?

Apologies for the bump, but is there any ETA for Mutter 49.3?

It should have a fix for https://gitlab.gnome.org/GNOME/mutter/-/issues/4489

LGTM!

LGTM.

I get this when running the new version in the terminal:

gtk_root_set_focus: assertion 'GTK_IS_ROOT (self)' failed

Is it harmless?

LGTM.

@frantisekz I see. And, as expected, the backported PR made Oblivion look normal again. All in all, LGTM.

Thank you for your hard work, guys.

>>> Running post-transaction scriptlet: wine-dxvk-d3d10-0:2.5.2-1.fc41.i686
>>> Finished post-transaction scriptlet: wine-dxvk-d3d10-0:2.5.2-1.fc41.i686
>>> Scriptlet output:
>>> failed to read link /usr/lib/wine/i386-windows/d3d10core.dll: No such file or directory
>>> 
>>> Running post-transaction scriptlet: wine-dxvk-d3d10-0:2.5.2-1.fc41.x86_64
>>> Finished post-transaction scriptlet: wine-dxvk-d3d10-0:2.5.2-1.fc41.x86_64
>>> Scriptlet output:
>>> failed to read link /usr/lib64/wine/x86_64-windows/d3d10core.dll: No such file or directory
>>>

Also, DXVK v2.5.2 turns The Elder Scrolls IV: Oblivion into an acid-trip horrow show (might be fixed by https://github.com/doitsujin/dxvk/pull/4533). I would suggest waiting until the next release, and just updating Wine without wine-dxvk for now.

wine-dxvk hasn't been updated, right? I still get the same scriptlet errors.

That is to say, the Wine scriptlets seem to have been fixed, whereas the wine-dxvk ones still error out.

>>> Running post-transaction scriptlet: wine-dxvk-d3d10-0:2.5.1-1.fc41.i686
>>> Finished post-transaction scriptlet: wine-dxvk-d3d10-0:2.5.1-1.fc41.i686
>>> Scriptlet output:
>>> failed to read link /usr/lib/wine/i386-windows/d3d10core.dll: No such file or directory
>>> 
>>> Running post-transaction scriptlet: wine-dxvk-d3d10-0:2.5.1-1.fc41.x86_64
>>> Finished post-transaction scriptlet: wine-dxvk-d3d10-0:2.5.1-1.fc41.x86_64
>>> Scriptlet output:
>>> failed to read link /usr/lib64/wine/x86_64-windows/d3d10core.dll: No such file or directory
>>> 

Getting there... )

@frantisekz I see, thanks for the links.

After updating a clean install of wine-9.15-1 to 0.2rc1, the errors seem to persist:

>>> Running post-transaction scriptlet: wine-core-0:10.0-0.2rc1.fc41.x86_64
>>> Finished post-transaction scriptlet: wine-core-0:10.0-0.2rc1.fc41.x86_64
>>> Scriptlet output:
>>> failed to link /usr/lib64/wine/x86_64-windows/d3d8.dll -> /etc/alternatives/wine-d3d8(x86-64): /usr/lib64/wine/x86_64-windows/d3d8.dll exists and it is not a symlink
>>> 
>>> Running post-transaction scriptlet: wine-core-0:10.0-0.2rc1.fc41.i686
>>> Finished post-transaction scriptlet: wine-core-0:10.0-0.2rc1.fc41.i686
>>> Scriptlet output:
>>> failed to link /usr/lib/wine/i386-windows/d3d8.dll -> /etc/alternatives/wine-d3d8(x86-32): /usr/lib/wine/i386-windows/d3d8.dll exists and it is not a symlink
>>> 
>>> Running post-transaction scriptlet: wine-dxvk-d3d10-0:2.5.1-1.fc41.i686
>>> Finished post-transaction scriptlet: wine-dxvk-d3d10-0:2.5.1-1.fc41.i686
>>> Scriptlet output:
>>> failed to read link /usr/lib/wine/i386-windows/d3d10core.dll: No such file or directory
>>> 
>>> Running post-transaction scriptlet: wine-dxvk-d3d10-0:2.5.1-1.fc41.x86_64
>>> Finished post-transaction scriptlet: wine-dxvk-d3d10-0:2.5.1-1.fc41.x86_64
>>> Scriptlet output:
>>> failed to read link /usr/lib64/wine/x86_64-windows/d3d10core.dll: No such file or directory
>>> 

Also, I just realized that dnf5 truncates whatever doesn't fit on a single line, so above is the full output.

After a bit of testing, which involved three Windows games (with MangoHud and Gamescope), I can tell that this RC appears to be working as well as wine-9.15-1. That said, I noticed that wine-dxvk is engaged even for DX9 games now, even though that was disabled at some point due to a wine bug (which remains open). Is this intentional?

I got the following output upon updating:

>>> Running post-transaction scriptlet: wine-core-0:10.0-0.1rc1.fc41.x86_64
>>> Finished post-transaction scriptlet: wine-core-0:10.0-0.1rc1.fc41.x86_64
>>> Scriptlet output:
>>> failed to link /usr/lib64/wine/x86_64-windows/d3d8.dll -> /etc/alternatives/wine-d3d8(x86-64): /usr/lib64/
>>> 
>>> Running post-transaction scriptlet: wine-core-0:10.0-0.1rc1.fc41.i686
>>> Finished post-transaction scriptlet: wine-core-0:10.0-0.1rc1.fc41.i686
>>> Scriptlet output:
>>> failed to link /usr/lib/wine/i386-windows/d3d8.dll -> /etc/alternatives/wine-d3d8(x86-32): /usr/lib/wine/i
>>> 
>>> Running post-transaction scriptlet: wine-dxvk-d3d10-0:2.5.1-1.fc41.i686
>>> Finished post-transaction scriptlet: wine-dxvk-d3d10-0:2.5.1-1.fc41.i686
>>> Scriptlet output:
>>> failed to read link /usr/lib/wine/i386-windows/d3d10core.dll: No such file or directory
>>> 
>>> Running post-transaction scriptlet: wine-dxvk-d3d10-0:2.5.1-1.fc41.x86_64
>>> Finished post-transaction scriptlet: wine-dxvk-d3d10-0:2.5.1-1.fc41.x86_64
>>> Scriptlet output:
>>> failed to read link /usr/lib64/wine/x86_64-windows/d3d10core.dll: No such file or directory

Now, on to test some Windows games...

Any plans to update the F40 package to v58 proper?

@chrisawi Ninja'd.

</off-topic>