Re: DNF Upgrade from F38 to F39 Issues

[Tim via users]

Jeffrey Walton wrote:
>> * SecureBoot should be turned off if using tainted kernel drivers. Or,
>> you can cutover to driver signing. I usually turn off SecureBoot
>> because I don't like messing around with driver signing. In my case,
>> it usually is due to VirtualBox, not NVIDIA.

Stephen Morris:
> As my system is a tri-boot between Windows 11, Fedora 39 and Ubuntu 
> 22.04, and Windows doesn't seem to work properly with UEFI disabled, 
> I've gone down the path of signing the nvidia drivers under Fedora and 
> Ubuntu, using separate passwords as I found using the same password 
> causes thing to not work properly.
> 

UEFI is a hardware interface (simplifying that description quite a lot)
between the PC's hardware, firmware, and the OS before it boots, and
the control screens it gives you for you to configure things.  It's an
update on the similiar, but more primitive, thing done with the old
BIOS.

Secure boot is a *separate* thing (though probably only exists on
systems with UEFI).  It's to do with only booting up from signed
binaries (to verify that only authentic things can run, blocking any
fake things that have snuck in).

A problem with Secure Boot is that there are real and genuine things
you may want to use that are not signed (such as some graphics card
drivers).  One solution to that is to sign them yourself, with a
signature that you let things know that *you* trust.

("Signed" in these contexts is to do with cryptographic keys.)

Though again, it could be that Windows won't boot without secure boot
options set, not UEFI being disabled (not that I've seen a motherboard
where you could disable UEFI and go back to BIOS).  That and the TPM
hardware that's touted as being more fantastic than it really is.

As a home user you may feel that this security is kinda pointless, as
no-one else is going to touch your PC and sneak things in.  And
anything nasty that does get in is going to get in by your own
behaviour doing unwise things, for which you're going to ignore and
disable any warnings not to do it.  To that degree, that's true.  And
the same can be said about AntiVirus, SELinux, file permissions and
ownership.  But where such security features can help, is when you
start to do something unwise without realising it, it blocks you, and
you properly investigate the reasons.

-- 
 
uname -rsvp
Linux 3.10.0-1160.102.1.el7.x86_64 #1 SMP Tue Oct 17 15:42:21 UTC 2023 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: DNF Upgrade from F38 to F39 Issues

[Stephen Morris]

On 18/11/23 14:28, Jeffrey Walton wrote:

On Fri, Nov 17, 2023 at 10:08 PM Stephen Morris
 wrote:

Hi,
  I used dnf system-upgrade to upgrade from F38 to F39. After the
upgrade when I booted into gdm to login and start KDE, the machine hung
on KDE startup into X11.
  Thinking it might be an nvidia UEFI enrolment issue with the F39
nvidia drivers, I reset the machine and booted back into gdm.
  I then used ctrl+alt+F2 to start a terminal interface. In that
terminal I went through the UEFI enrolment process but that said the
drivers were already enrolled.
  I issued dmesg to see if there were any nvidia failure messages, of
which there none, but I did notice there were initialisation and what
looked like failure messages from Nouveau, but I don't understand why
there would be an Nouveau messages at all when Nouveau is blacklisted in
the kernel parameters in grub.
  I then uninstalled all the nvidia drivers that were present. I then
used ctrl+alt+delete to reboot from the terminal. That process hung for
1.5 minutes waiting for a job stop (I don't remember what it was waiting
on), and, when the 1.5 minute timer finished it then hung waiting for
XWayland to shut down. Why was it waiting for XWayland to shut down when
I don't use Wayland, I only use X11?
  On reboot, I started up KDE under Nouveau, which doesn't work
properly with my BENQ 4K monitor, it can't determine what the monitor
is, so doesn't run in the right resolutions, although it does honour the
display scaling specified when using the nvidia drivers (which do
recognise the monitor and set things up properly).
  I reinstalled the nvidia drivers and a subsequent reboot then
booted into KDE with any issues (which is where I'm sending this email
from). Why did this freezing of the nvidia drivers happen, is it because
the F39 nvidia drivers don't work properly with an update and have to be
installed from scratch to work properly?
  Also, after reinstalling the nvidia drivers, at the gdm login
screen the display manager selection options only showed "Gnome", "Gnome
Classic" and "Plasma/X11", where are the options for all of those to
swap them between Wayland and X11 if I want to, that were present in F38
before the upgrade to F39?

A couple of thoughts in no particular order. I don't know how you
should move forward with your issues.

* The KDE spin uses Wayland, not X11.

* The KDE spin uses SDDM, not GDM.
I originally installed F36 from a live DVD which installs a Gnome spin 
with gdm. I then installed KDE by doing a dnf group install of Plasma 
which still leaves GDM as the default Display Manager. I then upgraded 
to F38 via dnf system-upgrade and then to F39 via dnf system-upgrade, 
all of which leave gdm as the display manager. I can then boot into 
Gnome (which I do infrequently) and KDE both in X11 by selecting the 
appropriate menu option in a GDM, as indicated by Patrick in a 
subsequent thread.

* SecureBoot should be turned off if using tainted kernel drivers. Or,
you can cutover to driver signing. I usually turn off SecureBoot
because I don't like messing around with driver signing. In my case,
it usually is due to VirtualBox, not NVIDIA.
As my system is a tri-boot between Windows 11, Fedora 39 and Ubuntu 
22.04, and Windows doesn't seem to work properly with UEFI disabled, 
I've gone down the path of signing the nvidia drivers under Fedora and 
Ubuntu, using separate passwords as I found using the same password 
causes thing to not work properly.


regards,
Steve



Jeff
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue




OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: recommended practice for python 3.11 on F39

[Ranjan Maitra via users]

My thanks again for this!


On Sat Nov18'23 08:26:10AM, George N. White III wrote:
> From: "George N. White III" 
> Date: Sat, 18 Nov 2023 08:26:10 -0400
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: recommended practice for python 3.11 on F39
>
> On Fri, Nov 17, 2023 at 10:29 PM Ranjan Maitra via users <
> users@lists.fedoraproject.org> wrote:
>
> > So, it turns out that there is no tensorflow for Python 3.12, which is
> > what is shipped out with F39.
> >
> > I tried to downgrade my python using
> >
> > sudo dnf downgrade python --releasever=38
> >
> > that downgrades a huge bunch of things, including important components
> > like rpm.
> >
>
> Many system tools use python -- as you have discovered, downgrading it will
> cause problems.
>
> >
> > However, dnf install/update pretty much anything gives a segmentation
> > fault after that.
> >
> > $ sudo dnf update --exclude=python\*
> > Last metadata expiration check: 2:37:29 ago on Fri 17 Nov 2023 05:50:32 PM
> > CST.
> > Segmentation fault
> >
> > Staying within the dnf system, is there a better way to keep the older
> > version of python around?
> >
>
> You broke dnf.  Fix it and you can install the F39 python3.11 package.
> There are ways
> (environments, tweaks to the hashbang line in python scripts).  With F38 I
> used 3rd party
>  python tools that needed python-3.10.   I haven't had time to see what is
> provided with
> F39, but you can look for conda or mamba packages.

I was not aware that it was possibe to install python3.11 using dnf in F39, so 
thanks for this. Wow, amazing! The old tensorflow installation just works out 
of the box. Did not expect that.

Thanks for this!

>
> Anaconda Python is a widely used platform independent system that supports
> use of multiple
> python versions via environments.
>

Thanks also for all the other information, it is very helpful and I will keep 
it with me for later use.

Best wishes,
Ranjan
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: DNF Upgrade from F38 to F39 Issues

[Stephen Morris]

On 18/11/23 20:05, John Pilkington wrote:

On 18/11/2023 05:11, Samuel Sieb wrote:

On 11/17/23 19:08, Stephen Morris wrote:
 I reinstalled the nvidia drivers and a subsequent reboot then 
booted into KDE with any issues (which is where I'm sending this 
email from). Why did this freezing of the nvidia drivers happen, is 
it because the F39 nvidia drivers don't work properly with an update 
and have to be installed from scratch to work properly?


I think there was another thread about this.  The akmods didn't run 
properly during the update process.



https://bugzilla.redhat.com/show_bug.cgi?id=2011120
Thanks Samuel and John. I wasn't expecting this as I have both the 
kmod-nvidia and akmod-nvidia packages installed so that I can use the 
akmod packages as a backup if the binary packages haven't been updated 
for new kernels when installed, so I was expected the kmod-nvidia driver 
to just work.
As of the boot I've just done now the issue with the missing selections 
in GDM has rectified itself.


regards,
Steve


--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue




OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: upgrade f38->f39 via discover?

[Michael D. Setzer II via users]

On 18 Nov 2023 at 17:11, Neal Becker wrote:

From:   Neal Becker 
Date sent:  Sat, 18 Nov 2023 17:11:15 -0500
Subject:upgrade f38->f39 via discover?
To: Community support for Fedora users 
Send reply to:  Community support for Fedora users 


> 
> I've always upgraded manually using dnf system-upgrade. I have a laptop 
> running F38 belonging to my wife. She got a notification, I presume from 
> "discover", saying F39 upgrade is available. I've never tried an upgrade this 
> way. Just wondering if anyone has tried this upgrade route and what was 
> their experience?

I've used it for a long time with only once having an issue when 
doing a 2 level upgrade, but now do the upgrades each version.
Only things, is to make sure to do the full update before running 
upgrade. It prompts you for that at beginning.
Another little thing. If one is using winehq package, one will 
eventually need to modify the /etc/yum.repos.d/winehq.repo to 
match the new version. Otherwise it will stay with the version 
listed in repo file. 

But is always best to do a backup of things just in case.
Does take a while to run, so make sure you have good power or 
good ups. Downloading part is not a problem, since it can be 
redone, but once you do reboot to actually do the upgrade that will 
not handle a shutdown or loose of power.



++
 Michael D. Setzer II - Computer Science Instructor (Retired) 
 mailto:mi...@guam.net
 mailto:msetze...@gmail.com
 Guam - Where America's Day Begins
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
++


--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

upgrade f38->f39 via discover?

[Neal Becker]

I've always upgraded manually using dnf system-upgrade. I have a laptop
running F38 belonging to my wife.  She got a notification, I presume from
"discover", saying F39 upgrade is available.  I've never tried an upgrade
this way.  Just wondering if anyone has tried this upgrade route and what
was their experience?
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Why Fedora/RHEL/CentOS Stream is not boot from other Linux district?

[Jonathan Billings]

On Nov 16, 2023, at 03:02, Jeffrey Walton  wrote:
> 
> On Wed, Nov 15, 2023 at 11:33 AM fedoraUser 2023  
> wrote:
>> 
>> Fedora/CentOS/RHEL boot only from this grub. When install Fedora and CentOS, 
>> CentOS no boot from Fedora boot loader, Fedora no boot From CentOS boot 
>> loader. Why?
> 
> Have you updated GRUB recently?
> 
> As I understand things, GRUB is not updated automatically. Once
> installed, it has to be updated manually. In fact, it is an option
> upgrade step at
> .

Nope, you don’t need to touch the grub configuration once installed on a Fedora 
system unless you have changed the settings in /etc/sysconfig/grub or you’ve 
updated to a new Fedora release (and that’s done automatically, I believe). 

New kernels drop a file in /boot/loader/entries/ as part of the post-install 
script, and those files are read by grub during boot. 

Now there have been people who post to this list that have managed to mess up 
their system to the point where they have to manually run grub2-mkconfig after 
each kernel update, but that’s not the default behavior of Fedora. 

> And there's the forbidden signature database that blacklists buggy
> versions of GRUB...
> .


This is something you’d get as a firmware update, either through fwupd, a 
windows update (dual-boot) or by manually updating the BIOS/firmware though 
some out-of-bound method. DBX updates change the firmware and not grub2. 


-- 
Jonathan Billings
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [SOLVED] LibreOffice Base to MariaDB?

[Greg Woods]

After installing the "unixODBC" and "mariadb-connector-odbc" packages, I
finally found this:

https://mariadb.com/kb/en/creating-a-data-source-with-mariadb-connectorodbc/

After following the directions there for setting up a data source and
running the "odbcinst" commands from that document, I got it to work.

--Greg


On Fri, Nov 17, 2023 at 8:22 PM Greg Woods  wrote:

> I remember setting this up quite some time ago, but now I have a new
> machine running F38. I can find some documentation for the old very tedious
> procedure to get this to work; it still does work on an older machine where
> I had done this. But I notice now that Fedora might already have some of
> the required packages, such as mariadb-connector-odbc-3.1.19-1.fc38.x86_64
> and unixODBC-2.3.11-2.fc38.x86_64 . Would these packages work? Has anyone
> here already gotten LibreOfficeBase to talk to a MariaDB database on Fedora
> 38? If so can you point me to a place that describes the process for
> getting it working?
>
> Thanks in advance,
> --Greg
>
>
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: DNF Upgrade from F38 to F39 Issues

[Jeffrey Walton]

On Sat, Nov 18, 2023 at 7:16 AM Patrick O'Callaghan
 wrote:
>
> On Fri, 2023-11-17 at 22:28 -0500, Jeffrey Walton wrote:
> > A couple of thoughts in no particular order. I don't know how you
> > should move forward with your issues.
> >
> > * The KDE spin uses Wayland, not X11.
> >
>
> I use KDE with X11. You just have to select it on the login screen.
> AFAIK KDE 6 will default to Wayland in an upcoming release, without
> support for X11, but that isn't currently the case.

Oh, that's good news. I might have to poke around and try it.

I really miss "disable touchpad when mouse plugged in." libinput and
X11 provide it, Wayland does not.

Jeff
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Strange daily reboot - SOLVED

[Patrick O'Callaghan]

On Tue, 2023-11-14 at 13:52 +, Patrick O'Callaghan wrote:
> My system (both F38 and now F39) reboots itself every morning at 8am,
> yet nothing in the cron configuration is telling it to do that and I
> don't see anything obvious in the journal to cause it.
> 
> How can I figure out what is triggering this? I know the description
> is
> vague, but there it is.

Just to close this off:

- The problem was being caused by a flaky smart plug
- Restoring factory settings to the plug fixed it
- I decided to follow some recommendations in the thread and use the
built-in motherboard RTC instead of the smart plug as a way to re-
activate the system at a set time. This is now working (touch wood).

My hibernation script now includes this snippet, if anyone's
interested:

set_wakeup() {  # See 
https://www.linux.com/training-tutorials/wake-linux-rtc-alarm-clock/
if [[ $(date +"%H") -lt 8 ]]; then
datestring=$(date '+%s' -d '08:00 today')
else
datestring=$(date '+%s' -d '08:00 tomorrow')
fi
echo "$datestring" > /sys/class/rtc/rtc0/wakealarm
}

Thanks again to all who chipped in.

poc
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: recommended practice for python 3.11 on F39

[George N. White III]

On Fri, Nov 17, 2023 at 10:29 PM Ranjan Maitra via users <
users@lists.fedoraproject.org> wrote:

> So, it turns out that there is no tensorflow for Python 3.12, which is
> what is shipped out with F39.
>
> I tried to downgrade my python using
>
> sudo dnf downgrade python --releasever=38
>
> that downgrades a huge bunch of things, including important components
> like rpm.
>

Many system tools use python -- as you have discovered, downgrading it will
cause problems.

>
> However, dnf install/update pretty much anything gives a segmentation
> fault after that.
>
> $ sudo dnf update --exclude=python\*
> Last metadata expiration check: 2:37:29 ago on Fri 17 Nov 2023 05:50:32 PM
> CST.
> Segmentation fault
>
> Staying within the dnf system, is there a better way to keep the older
> version of python around?
>

You broke dnf.  Fix it and you can install the F39 python3.11 package.
There are ways
(environments, tweaks to the hashbang line in python scripts).  With F38 I
used 3rd party
 python tools that needed python-3.10.   I haven't had time to see what is
provided with
F39, but you can look for conda or mamba packages.

Anaconda Python is a widely used platform independent system that supports
use of multiple
python versions via environments.



>
> Many thanks,
> Ranjan
> --
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>


-- 
George N. White III
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: DNF Upgrade from F38 to F39 Issues

[Patrick O'Callaghan]

On Fri, 2023-11-17 at 22:28 -0500, Jeffrey Walton wrote:
> A couple of thoughts in no particular order. I don't know how you
> should move forward with your issues.
> 
> * The KDE spin uses Wayland, not X11.
> 

I use KDE with X11. You just have to select it on the login screen.
AFAIK KDE 6 will default to Wayland in an upcoming release, without
support for X11, but that isn't currently the case.

poc
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: recommended practice for python 3.11 on F39

[Hiep Pham via users]

On 18/11/23 03:29, Ranjan Maitra via users wrote:
> So, it turns out that there is no tensorflow for Python 3.12, which is
> what is shipped out with F39.
>
> I tried to downgrade my python using
>
> sudo dnf downgrade python --releasever=38
>
> that downgrades a huge bunch of things, including important components
> like rpm.
>
> However, dnf install/update pretty much anything gives a segmentation
> fault after that.
>
> $ sudo dnf update --exclude=python\*
> Last metadata expiration check: 2:37:29 ago on Fri 17 Nov 2023 05:50:32 PM 
> CST.
> Segmentation fault
>
> Staying within the dnf system, is there a better way to keep the older
> version of python around?

You should try something like Pyenv [1] or miniconda [2] to manage 
different Python versions instead of messing around with the system 
packages.


[1]: https://github.com/pyenv/pyenv

[2]: https://docs.conda.io/projects/miniconda/en/latest/

-- 
Hiep

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: f39 emacs strange behavior?

[Tim via users]

On Fri, 2023-11-17 at 19:49 -0600, Ranjan Maitra via users wrote:
> I am more or less finding my way around nvim, but I have
> not yet figured out two things yet.
> 
> I loved the autoformatting feature of C, etc in emacs. Basically as I
> typed, things would get formatted. And I have not really been able to
> figure out if that is possible here (automagically, without pressing any
> key combination).
> 
> The other thing I will look at more carefully this weekend is to figure
> out a way to reliably highlight a area with my mouse left button and
> then paste it with my second mouse button (the wheel). Inside nvim, it
> is largely not reliable (with workarounds in many cases, but with key
> combinations) and I can not quite figure out why it is not. In the old
> days before DEs, the idea of highlight and paste (rather than use
> whatever key combination) is something I really got used to.

I use gvim (graphical vim), so this may or may not be applicable:

It can recognise various coding formats and highlight the sections in
colours, so there's potential for further automation.  I haven't tried
to find any auto-formatting, beyond its basic auto-indenting (which
just starts the next line at the same indent as the current line, no
fancy nesting).

A quick look through google suggests there's some add-on that can do
that.  Though I got the feeling it was a post-processing tool, rather
than an as-you-type thing.

I can cut and paste with the mouse, but if you're not in insert
(typing) mode, the results can take you by surprise.  Also, you need to
put the cursor where you want the paste to be inserted before you paste
the contents of the buffer.

-- 
 
uname -rsvp
Linux 3.10.0-1160.102.1.el7.x86_64 #1 SMP Tue Oct 17 15:42:21 UTC 2023 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: DNF Upgrade from F38 to F39 Issues

[John Pilkington]

On 18/11/2023 05:11, Samuel Sieb wrote:

On 11/17/23 19:08, Stephen Morris wrote:
 I reinstalled the nvidia drivers and a subsequent reboot then 
booted into KDE with any issues (which is where I'm sending this email 
from). Why did this freezing of the nvidia drivers happen, is it 
because the F39 nvidia drivers don't work properly with an update and 
have to be installed from scratch to work properly?


I think there was another thread about this.  The akmods didn't run 
properly during the update process.



https://bugzilla.redhat.com/show_bug.cgi?id=2011120
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue