F37 - dnf update error
by Robert Moskowitz
On a F37 system I have not updated in maybe a month or more, I get the
error:
Running transaction test
The downloaded packages were saved in cache until the next successful
transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transaction test error:
file /usr/lib64/libheif/libheif-libde265.so conflicts between
attempted installs of libheif-hevc-1.15.1-2.fc37.1.x86_64 and
libheif-freeworld-1.15.1-4.fc37.x86_64
file /usr/lib64/libheif/libheif-x265.so conflicts between attempted
installs of libheif-hevc-1.15.1-2.fc37.1.x86_64 and
libheif-freeworld-1.15.1-4.fc37.x86_64
How do I get around this?
Maybe first update without freeworld?
thanks
1 year, 1 month
0 network conection??
by ToddAndMargo
# nmcli conn show --active
NAME UUID TYPE DEVICE
Wired connection 2 3d30b55f-3675-3e71-88fd-a9796720a9f3 ethernet eno2
virbr0 5ed314a7-f7d5-4719-9f8a-e144718b6288 bridge virbr
0
What is with the "0" all by itself at the end?
1 year, 1 month
Certbot error
by Patrick O'Callaghan
I'm trying to set up a simple web server for personal use, using
Apache, and want to enable HTTPS access. This involves getting an SSL
certificate and I'll be using LetsEncrypt (www.letsencrypt.org).
The recommended way to do this is with Certbot, but I can't get past
this error:
# certbot --apache -d bree.org.uk
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for bree.org.uk
Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
Note that the httpd server is online and reachable from outside my
local net, i.e. this doesn't appear to be a firewall issue.
I've reported the problem upstream and followed a number of
suggestions, but nothing seems to make any difference:
https://community.letsencrypt.org/t/certbot-fails-with-cant-find-virtual-...
Any thoughts on this would be welcome, but please review the above link
before replying.
poc
1 year, 1 month
Re: Broken by the grub startup after have move whole the system from
one SSHDD more small to a SSD more big by a software acronis
by Chris Adams
I'm not sure exactly where your system is stopping, but I just went
through an issue moving a system yesterday, so maybe this will help.
If your system is booting in UEFI mode (running "efibootmgr" shows boot
entires), there's an extra file that needs to be updated that I don't
think is clearly documented anywhere, nor is there a command to updated
it. That is /boot/efi/EFI/fedora/grub.cfg. It searches for the /boot
partition by UUID.
To find the correct UUID, I believe this will work:
- boot a Live image from USB
- select Troubleshooting at the boot menu and choose Rescue
- at the prompt, choose to mount the system
- in the shell, run: chroot /mnt/sysimage
- find the correct UUID with: lsblk -o UUID,MOUNTPOINT | grep ' /boot$'
- edit /boot/efi/EFI/fedora/grub.cfg and put that UUID on the "search" line
I'm not sure that this is clearly documented anywhere, and I don't think
there's any command to update that file easily (unlike regenerating the
main grub.cfg with "grub2-mkconfig -o /etc/grub2.cfg").
--
Chris Adams <linux(a)cmadams.net>
1 year, 1 month
Re: Broken by the grub startup after have move whole the system
from one SSHDD more small to a SSD more big by a software acronis
by stan
On Fri, 21 Apr 2023 13:59:38 +0000
Dorian ROSSE <dorianbrice(a)hotmail.fr> wrote:
First, the translation is much better. I was going to suggest one of
https://deepl.com/translator
or
https://translate.google.com
but it reads like you found a better one.
I think there was a failure in our communication. The commands you ran
below need to be done after the installed system is mounted. Otherwise,
they only give information about the live system that you are
booted into. I will tell you how to do that below, after some
interspersed comments.
> i paste below the inside from /etc/fstab :
>
> vartmp /var/tmp tmpfs defaults 0 0
This is from the live system.
>
> i attach in attachment /usr/sbin/blkid because the file is
> misunderstood by the pen USB,
>
> now i paste below the happening of your advice df :
>
> [liveuser@localhost-live ~]$ df
> Sys. de fichiers blocs de 1K Utilisé Disponible Uti% Monté sur
> devtmpfs 4096 0 4096 0% /dev
> tmpfs 8117308 3356 8113952 1% /dev/shm
> tmpfs 3246924 9824 3237100 1% /run
> /dev/sdb1 7664800 2038132 5626668 27%
> /run/initramfs/live /dev/mapper/live-rw 7712908 6192208
> 1504316 81% / tmpfs 8117312 16 8117296
> 1% /tmp vartmp 8117308 0 8117308 0%
> /var/tmp tmpfs 1623460 132 1623328 1%
> /run/user/1000
The above seems to be from the live system. What I need is the
result from the installed system. It is a positive thing that it
shows your installed system, so the information we are looking for will
be available once you mount this partition.
/dev/sdb1 7664800 2038132 5626668 27%
If the above is all you have installed, there is no need to run df
again. If you do run it on the installed system, you should only get
the above line, I think. It might show the EFI partition, since that
is separate, and a different filesystem, usually fat32.
> below you will read the happening of your list from
> /boot/loader/entries :
>
> [liveuser@localhost-live ~]$ sudo ls -n /boot/loader/entries
> total 8
> -rw-r--r--. 1 0 0 442 13 avril 17:49
> f6fe47dfbe174a2b98acdafe136e1959-0-rescue.conf -rw-r--r--. 1 0 0 362
> 13 avril 17:47
> f6fe47dfbe174a2b98acdafe136e1959-6.2.9-300.fc38.x86_64.conf
Again, this is from the live system, so does not help with
troubleshooting. The installed system will look similar.
>
> so the list in boot below :
>
> [liveuser@localhost-live ~]$ sudo ls -n /boot
> total 53880
> -rw-r--r--. 1 0 0 255900 29 mars 20:00 config-6.2.9-300.fc38.x86_64
> drwx------. 4 0 0 4096 13 avril 17:47 efi
> drwx------. 3 0 0 4096 21 avril 09:33 grub2
> -rw-------. 1 0 0 32251854 13 avril 17:52
> initramfs-6.2.9-300.fc38.x86_64.img drwxr-xr-x. 3 0 0 4096 13
> avril 17:46 loader lrwxrwxrwx. 1 0 0 45 13 avril 17:47
> symvers-6.2.9-300.fc38.x86_64.gz ->
> /lib/modules/6.2.9-300.fc38.x86_64/symvers.gz -rw-------. 1 0 0
> 8429627 29 mars 20:00 System.map-6.2.9-300.fc38.x86_64 -rwxr-xr-x. 1
> 0 0 14215976 29 mars 20:00 vmlinuz-6.2.9-300.fc38.x86_64
Again, this is from the live system, so does not help with
troubleshooting. The installed system will look similar.
> /etc/default/grub is unfound by the pen USB :
>
> [liveuser@localhost-live ~]$ sudo cat /etc/default/grub
> cat: /etc/default/grub: Aucun fichier ou dossier de ce type
> [liveuser@localhost-live ~]$ less /etc/default/grub
> /etc/default/grub: Aucun fichier ou dossier de ce type
Again, this is from the live system, so does not help with
troubleshooting. The live USB doesn't use grub, it seems.
It should look something like:
$ cat /etc/default/grub
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=false
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true
And the blkid output was binary and didn't look like it was valid when
I examined it. I presume that it was like that because it was also
from the live system. Output from blkid should look like this:
/dev/sda4: LABEL="root1" UUID="fb6b3e13-20d8-445f-b25a-c8a05a4c842f" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="6d8baf7c-14e7-4496-926a-8882715415ba"
with a line for every partition on the installed system. Probably only
one on your system, but maybe one for the EFI partition.
Here are some better instructions. When the live system is running do
an
ls /mnt
Is there a directory called sysimage in the output?
Yes, next step.
No, create a directory under mnt.
mkdir /mnt/sysimage
Mount the installed system on the new directory.
mount /dev/sdb1 /mnt/sysimage
If there is an error from this command, there is no point in going
further. Stop, and send the error you got. You can try looking in
man mount to see if you can fix the error yourself.
If the command finished successfully, you can do an
ls /mnt/sysimage
This should give you a listing of your installed system root partition,
/dev/sdb1 7664800 2038132 5626668 27%
$ ls /
afs bin boot dev etc home lib lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var
If it does, then next step. Doesn't, no point in continuing. Post the
output of the command here.
Make the installed system the root system, so you will be in it as if
it was running, sort of. You will be able to edit and examine all the
files.
chroot /mnt/sysimage
Run all the commands you ran above in the installed system. They will
give the data we need to troubleshoot your system.
The command less is handy for looking at files, read only.
cat prints the contents of a file.
I use vim as an editor, but you probably want to use a simpler editor.
Fedora provides one called nano.
You use
exit
to leave the chroot environment.
Waiting for your data so we can get you running with your installed
system.
1 year, 1 month
Using python3-pycryptodomex
by Robert Moskowitz
I am NOT experienced with python, so reading lots of examples.
I have installed python3-pycryptodomex on my old F35 system (will mess
up my F37 system later).
Preparing : 1/1
Installing :
python3-pycryptodomex-3.15.0-1.fc35.x86_64 1/1
Running scriptlet:
python3-pycryptodomex-3.15.0-1.fc35.x86_64 1/1
Verifying :
python3-pycryptodomex-3.15.0-1.fc35.x86_64 1/1
Installed:
python3-pycryptodomex-3.15.0-1.fc35.x86_64
I go into python and try importing salsa per:
https://pycryptodome.readthedocs.io/en/v3.15.0/src/cipher/cipher.html
>>> from Crypto.Cipher import Salsa20
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'Crypto'
I then tried the self test from:
https://pycryptodome.readthedocs.io/en/v3.15.0/src/installation.html
python -m Cryptodome.SelfTest
/usr/bin/python: No module named Cryptodome.SelfTest
Obviously I am missing something very fundamental here in getting the
crypto module available to python...
Help?
thanks
1 year, 1 month
not an active connection ???
by ToddAndMargo
Hi All,
What am I missing here?????
# netstat -rn | grep eno2
0.0.0.0 192.168.250.1 0.0.0.0 UG 0 0 0
eno2
192.168.250.0 0.0.0.0 255.255.255.0 U 0 0 0
eno2
# /usr/bin/nmcli c down eno2
Error: 'eno2' is not an active connection.
Error: no active connection provided.
Yours in confusion,
-T
1 year, 1 month