It looks like Fedora 40 just dropped! Upgrade instructions at < https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/%3E.
RPMFushion folks should wait about a month before upgrading. There always seems to be a lot of video problems after a new release while RPMFusion is rebuilding their packages.
Jeff
Am 25.04.2024 um 04:48 schrieb Jeffrey Walton noloader@gmail.com:
It looks like Fedora 40 just dropped! Upgrade instructions at https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/.
RPMFushion folks should wait about a month before upgrading. There always seems to be a lot of video problems after a new release while RPMFusion is rebuilding their packages.
Jeff
Updated Quick Docs to release 40. So the text should show the correct release numbers soon.
-- Peter Boy https://fedoraproject.org/wiki/User:Pboy PBoy@fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast
On 25 Apr 2024, at 03:48, Jeffrey Walton noloader@gmail.com wrote:
There always seems to be a lot of video problems after a new release while RPMFusion is rebuilding their packages.
You mean Nvidia problems? Nothing reported on the fedora forum that is negative, beyond the traditional upgrade not setting up the drives in the upgrade that is easy to fix.
Lots of people have working nvidia in f40.
Barry
On Thu, Apr 25, 2024 at 4:10 AM Barry Scott barry@barrys-emacs.org wrote:
On 25 Apr 2024, at 03:48, Jeffrey Walton noloader@gmail.com wrote:
There always seems to be a lot of video problems after a new release while RPMFusion is rebuilding their packages.
You mean Nvidia problems? Nothing reported on the fedora forum that is negative, beyond the traditional upgrade not setting up the drives in the upgrade that is easy to fix.
Lots of people have working nvidia in f40.
I have not been able to get a working system on Virtual Box due to video problems. Here are the latest problem: https://ibb.co/SXm8YyF, < https://ibb.co/mG9sL8H%3E and https://ibb.co/VvCKkKx. The last image, VvCKkKx, is after an install and then a 'dnf upgrade'.
I am Ok with upgrading headless servers; but not workstations with desktop software at the moment. I can't risk losing some of my desktops machines which are used daily.
Jeff
On 4/25/24 11:09, Jeffrey Walton wrote:
On Thu, Apr 25, 2024 at 4:10 AM Barry Scott <barry@barrys-emacs.org mailto:barry@barrys-emacs.org> wrote:
On 25 Apr 2024, at 03:48, Jeffrey Walton <noloader@gmail.com <mailto:noloader@gmail.com>> wrote: There always seems to be a lot of video problems after a new release while RPMFusion is rebuilding their packages.You mean Nvidia problems? Nothing reported on the fedora forum that is negative, beyond the traditional upgrade not setting up the drives in the upgrade that is easy to fix. Lots of people have working nvidia in f40.I have not been able to get a working system on Virtual Box due to video problems. Here are the latest problem: <https://ibb.co/SXm8YyF https://ibb.co/SXm8YyF>, <https://ibb.co/mG9sL8H https://ibb.co/mG9sL8H> and <https://ibb.co/VvCKkKx https://ibb.co/VvCKkKx>. The last image, VvCKkKx, is after an install and then a 'dnf upgrade'.
virtualbox is not a Fedora issue.
I am Ok with upgrading headless servers; but not workstations with desktop software at the moment. I can't risk losing some of my desktops machines which are used daily.
All the Fedora provided desktop software that I've used so far works great in F40. And no issues with running it under qemu/kvm.
On Wed, 2024-04-24 at 22:48 -0400, Jeffrey Walton wrote:
It looks like Fedora 40 just dropped! Upgrade instructions at < https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/
.
It was on the Fedora Announce list yesterday. Surprised it didn't appear here as well as it usually does.
RPMFushion folks should wait about a month before upgrading. There always seems to be a lot of video problems after a new release while RPMFusion is rebuilding their packages.
I've updated to F40. Everything works as expected, (I don't have an Nvidia card at present so YMMV). I do have some comments on the new KDE/Plasma but I'll post on the Fedora KDE list after a bit more testing.
poc
On Thu, 2024-04-25 at 11:51 +0100, Patrick O'Callaghan wrote:
I've updated to F40. Everything works as expected, (I don't have an Nvidia card at present so YMMV). I do have some comments on the new KDE/Plasma but I'll post on the Fedora KDE list after a bit more testing.
Did that xv security issue get sorted out before the release?
On Thu, 2024-04-25 at 23:09 +0930, Tim via users wrote:
On Thu, 2024-04-25 at 11:51 +0100, Patrick O'Callaghan wrote:
I've updated to F40. Everything works as expected, (I don't have an Nvidia card at present so YMMV). I do have some comments on the new KDE/Plasma but I'll post on the Fedora KDE list after a bit more testing.
Did that xv security issue get sorted out before the release?
AFAIK that was fixed almost immediately after it was announced.
poc
On Thu, Apr 25, 2024 at 05:00:09PM GMT, Patrick O'Callaghan wrote:
On Thu, 2024-04-25 at 23:09 +0930, Tim via users wrote:
On Thu, 2024-04-25 at 11:51 +0100, Patrick O'Callaghan wrote:
I've updated to F40. Everything works as expected, (I don't have an Nvidia card at present so YMMV). I do have some comments on the new KDE/Plasma but I'll post on the Fedora KDE list after a bit more testing.
Did that xv security issue get sorted out before the release?
AFAIK that was fixed almost immediately after it was announced.
You mean xz? xv was a pretty cool (but not open source) image viewer back in the day. :)
as far as xz, for F40, the affected version was only in updates-testing for a short time, it never reached stable. The downgrade to the older version was pushed later in the day that the announcement came out about it.
kevin
Tim:
Did that xv security issue get sorted out before the release?
Patrick:
AFAIK that was fixed almost immediately after it was announced.
Kevin Fenzi:
You mean xz? xv was a pretty cool (but not open source) image viewer back in the day. :)
Yes, I did mean that. Oops...
as far as xz, for F40, the affected version was only in updates-testing for a short time, it never reached stable. The downgrade to the older version was pushed later in the day that the announcement came out about it.
Thanks. Also wondering how far back the breach went. I remember reading that the person had being playing the long game about doing this.
On Fri, 2024-04-26 at 08:22 +0930, Tim via users wrote:
as far as xz, for F40, the affected version was only in updates- testing for a short time, it never reached stable. The downgrade to the older version was pushed later in the day that the announcement came out about it.
Thanks. Also wondering how far back the breach went. I remember reading that the person had being playing the long game about doing this.
They spent a long time setting it up, but the actual breach wasn't introduced until very recently, and IIRC was caught before it made it to a stable release.
poc
On Fri, 26 Apr 2024, Patrick O'Callaghan wrote:
On Fri, 2024-04-26 at 08:22 +0930, Tim via users wrote:
as far as xz, for F40, the affected version was only in updates- testing
Thanks. Also wondering how far back the breach went. I remember reading that the person had being playing the long game about doing this.
They spent a long time setting it up, but the actual breach wasn't introduced until very recently, and IIRC was caught before it made it to a stable release.
How was it caught? If it's what I read about recently, 'twas a bit of a fluke.
On Fri, 2024-04-26 at 10:00 -0500, Michael Hennebry wrote:
On Fri, 26 Apr 2024, Patrick O'Callaghan wrote:
On Fri, 2024-04-26 at 08:22 +0930, Tim via users wrote:
as far as xz, for F40, the affected version was only in updates- testing
Thanks. Also wondering how far back the breach went. I remember reading that the person had being playing the long game about doing this.
They spent a long time setting it up, but the actual breach wasn't introduced until very recently, and IIRC was caught before it made it to a stable release.
How was it caught? If it's what I read about recently, 'twas a bit of a fluke.
Not quite a fluke, but certainly something to think about:
https://en.wikipedia.org/wiki/XZ_Utils_backdoor
poc
On 4/25/24 10:00 AM, Patrick O'Callaghan wrote:
On Thu, 2024-04-25 at 23:09 +0930, Tim via users wrote:
On Thu, 2024-04-25 at 11:51 +0100, Patrick O'Callaghan wrote:
I've updated to F40. Everything works as expected, (I don't have an Nvidia card at present so YMMV). I do have some comments on the new KDE/Plasma but I'll post on the Fedora KDE list after a bit more testing.
Did that xv security issue get sorted out before the release?
AFAIK that was fixed almost immediately after it was announced.
xv is maintained by a github group named "jasper-software". The current release is v5.0.0, less than 3 months ago. There was a significant enhancement almost a year ago to support "webp" images.
The web site for this xv is here: "https://github.com/jasper-software/xv".
It appears to be free and open-source, but I'm not certain. If it is, I wonder if it should still be in rpm-nonfree or somewhere else.
poc
Le jeu. 25 avr. 2024 à 20:35, home user mattisonw@comcast.net a écrit :
xv is maintained by a github group named "jasper-software". The current release is v5.0.0, less than 3 months ago. There was a significant enhancement almost a year ago to support "webp" images.
The web site for this xv is here: "https://github.com/jasper-software/xv".
It appears to be free and open-source, but I'm not certain. If it is, I wonder if it should still be in rpm-nonfree or somewhere else.
$ rpm -qi xv Name : xv Version : 4.1.1 Release : 1.fc38 Architecture: x86_64 Install Date: Wed 20 Sep 2023 11:30:02 PM CEST Group : Unspecified Size : 1444371 License : Shareware Signature : RSA/SHA256, Thu 08 Jun 2023 06:52:31 PM CEST, Key ID 6a2af96194843c65 Source RPM : xv-4.1.1-1.fc38.src.rpm Build Date : Thu 08 Jun 2023 12:31:55 PM CEST Build Host : buildvm-07.virt.rpmfusion.net Packager : RPM Fusion Vendor : RPM Fusion URL : https://github.com/jasper-software/xv [...]
On Wed, Apr 24, 2024 at 11:48 PM Jeffrey Walton noloader@gmail.com wrote:
It looks like Fedora 40 just dropped! Upgrade instructions at < https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/
.
RPMFushion folks should wait about a month before upgrading. There always seems to be a lot of video problems after a new release while RPMFusion is rebuilding their packages.
RPMFusion nvidia-470xx packages broke with recent F39 kernel updates.
On 4/24/24 22:48, Jeffrey Walton wrote:
It looks like Fedora 40 just dropped! Upgrade instructions at https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/.
RPMFushion folks should wait about a month before upgrading. There always seems to be a lot of video problems after a new release while RPMFusion is rebuilding their packages.
NVIDIA drivers came out with the release. Also for the 6.8 kernels on Fedora 39. Been quite a wait from 6.8.0 to 6.8.7 but now here.
-
Andras Simon -
Barry Scott -
George N. White III -
home user -
Jeffrey Walton -
Kevin Fenzi -
Michael Hennebry -
Patrick O'Callaghan -
Peter Boy -
Robert McBroom -
Samuel Sieb -
Tim