Re: Unable to do F40 Live Workstation install on machine with very old graphics

2024-04-26 Thread Felix Miata
Andre Robatino composed on 2024-04-27 03:56 (UTC): > I have 2 desktops, each running Fedora, the one in question is a backup that > I normally just log into with ssh and do updates, and would only use normally > if the main machine dies. I'll probably be buying a new machine in a year or > two

Re: Unable to do F40 Live Workstation install on machine with very old graphics

2024-04-26 Thread Andre Robatino
I have 2 desktops, each running Fedora, the one in question is a backup that I normally just log into with ssh and do updates, and would only use normally if the main machine dies. I'll probably be buying a new machine in a year or two and this one will go into storage, all of its hardware is

Re: Unable to do F40 Live Workstation install on machine with very old graphics

2024-04-26 Thread Felix Miata
Andre Robatino composed on 2024-04-27 02:49 (UTC): > I have an old machine from 2008 with very old integrated graphics (GeForce > 6150SE nForce 430). Up to and including F39, I was able to do a Live > Workstation install simply by using the nomodeset boot option. With F40 that > no longer

Unable to do F40 Live Workstation install on machine with very old graphics

2024-04-26 Thread Andre Robatino
I have an old machine from 2008 with very old integrated graphics (GeForce 6150SE nForce 430). Up to and including F39, I was able to do a Live Workstation install simply by using the nomodeset boot option. With F40 that no longer works - it fails to come up in graphical. I ended up doing a

Re: Upgrade to Fedora 40 errors on freerdp

2024-04-26 Thread Samuel Sieb
On 4/26/24 5:54 PM, Ranbir wrote: On Fri, 2024-04-26 at 16:30 -0400, Jeffrey Walton wrote: I seem to recall a similar problem about 6 months ago. Do you have updates-testing repo enabled? I do not. But, I do have enabled: Also see

Re: Upgrade to Fedora 40 errors on freerdp

2024-04-26 Thread Ranbir
On Fri, 2024-04-26 at 16:30 -0400, Jeffrey Walton wrote: > I seem to recall a similar problem about 6 months ago. Do you have > updates-testing repo enabled? I do not. But, I do have enabled: - rpmfusion-free - rpmfusion-free-updates - rpmfusion-nonfree - rpmfusion-nonfree-updates -

Re: Upgrade to Fedora 40 errors on freerdp

2024-04-26 Thread Ranbir
On Fri, 2024-04-26 at 12:50 -0700, Samuel Sieb wrote: > > That is odd.  I just checked my system that I upgraded yesterday and > I > do have freerdp installed.  Did you do an update before trying the > version upgrade?  And are you using `system-upgrade` to do it? Yes to both questions. --

Re: Upgrade to Fedora 40 errors on freerdp

2024-04-26 Thread Samuel Sieb
On 4/26/24 1:30 PM, Jeffrey Walton wrote: On Fri, Apr 26, 2024 at 11:45 AM Ranbir > wrote: I'm trying to upgrade to Fedora 40, but I'm running into an odd error: Error:  Problem: package freerdp-2:2.11.2-1.fc39.x86_64 from @System requires

Re: Upgrade to Fedora 40 errors on freerdp

2024-04-26 Thread Jeffrey Walton
On Fri, Apr 26, 2024 at 11:45 AM Ranbir wrote: > I'm trying to upgrade to Fedora 40, but I'm running into an odd error: > > Error: > Problem: package freerdp-2:2.11.2-1.fc39.x86_64 from @System requires > libwinpr(x86-64) = 2:2.11.2-1.fc39, but none of the providers can be > installed > -

Re: Upgrade to Fedora 40 errors on freerdp

2024-04-26 Thread Samuel Sieb
On 4/26/24 8:45 AM, Ranbir wrote: I'm trying to upgrade to Fedora 40, but I'm running into an odd error: Error: Problem: package freerdp-2:2.11.2-1.fc39.x86_64 from @System requires libwinpr(x86-64) = 2:2.11.2-1.fc39, but none of the providers can be installed -

[389-users] Re: [Freeipa-users] Fedora 40: new warning in ipa-healthckeck

2024-04-26 Thread Rob Crittenden
Cross-posting this on the 389-users list. rob Jochen Kellner via FreeIPA-users wrote: > > Hi, > > I've upgraded my freeipa server to Fedora 40 (the system was installed > several releases ago). After the upgrade I get the following new warning > from ipa-healthcheck: > > { > "source":

Re: Fedora 40 is available

2024-04-26 Thread Patrick O'Callaghan
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

Upgrade to Fedora 40 errors on freerdp

2024-04-26 Thread Ranbir
I'm trying to upgrade to Fedora 40, but I'm running into an odd error: Error: Problem: package freerdp-2:2.11.2-1.fc39.x86_64 from @System requires libwinpr(x86-64) = 2:2.11.2-1.fc39, but none of the providers can be installed - libwinpr-2:2.11.2-1.fc39.x86_64 from @System does not belong to

Re: The best way to still use Fedora + Xorg + Gnome ... even after version 40

2024-04-26 Thread Michael Hennebry
On Fri, 26 Apr 2024, Tim via users wrote: Tim: (re xeyes) My guess would be that something monitoring mouse movements when those mouse movements could be related to another app is considered insecure. Well, *I* would consider it insecure if any app could see what I was doing with the mouse at

Re: Fedora 40 is available

2024-04-26 Thread Michael Hennebry
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

Re: The best way to still use Fedora + Xorg + Gnome ... even after version 40

2024-04-26 Thread Dario Lesca
Il giorno gio, 25/04/2024 alle 00.10 -0400, Jeffrey Walton ha scritto: > So it looks like your fears may be unfounded at the moment. Yes, my fear is postponed to Fedora 41 (after version 40), for now. I have try on a F40 VM with Gnome + Xorg my preferred, and for me useful, app & extensions and

Re: Fedora 40 is available

2024-04-26 Thread Patrick O'Callaghan
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