Fedora 41 : remove package lead to unexpected results.

Today I saw the mutter package from Fedora distro come with a new update.

I don't use this package, ... is a mess in my oppinion.

But I found this output when I tried to remove

root@localhost:/home/mythcat# dnf5 remove mutter 
Package                          Arch   Version                 Reposit      Size
Removing:
 mutter                          x86_64 47.1-3.fc41             updates  12.5 MiB
Removing dependent packages:
 gdm                             x86_64 1:47.0-8.fc41           updates   5.3 MiB
 gnome-shell                     x86_64 47.1-1.fc41             updates  13.8 MiB
Removing unused dependencies:
 accountsservice                 x86_64 23.13.9-5.fc41          fedora  379.5 KiB
 accountsservice-libs            x86_64 23.13.9-5.fc41          fedora  212.3 KiB
 bluez-obexd                     x86_64 5.79-1.fc41             updates 345.1 KiB
 bolt                            x86_64 0.9.8-3.fc41            fedora  503.3 KiB
 boost-thread                    x86_64 1.83.0-8.fc41           fedora  136.8 KiB
 color-filesystem                noarch 1-34.fc41               fedora  151.0   B
 colord                          x86_64 1.4.7-5.fc41            fedora    1.7 MiB
 colord-gtk4                     x86_64 0.3.1-2.fc41            fedora   35.6 KiB
 composefs-libs                  x86_64 1.0.6-1.fc41            fedora  166.3 KiB
 cups-pk-helper                  x86_64 0.2.7-8.fc41            fedora  379.0 KiB
 dbus-daemon                     x86_64 1:1.14.10-4.fc41        fedora  553.2 KiB
 evolution-data-server           x86_64 3.54.1-1.fc41           updates   8.8 MiB
 evolution-data-server-langpacks noarch 3.54.1-1.fc41           updates   8.8 MiB
 flatpak-libs                    x86_64 1.15.10-1.fc41          fedora    1.0 MiB
 ...
 
Is this ok [y/N]: N
 ... 

If I used this command the gdm and gnome-shell is gone:

root@localhost:/home/mythcat# dnf5 remove --noautoremove mutter 
Package                        Arch   Version                   Repository        Size
Removing:
 mutter                        x86_64 47.1-3.fc41               updates       12.5 MiB
Removing dependent packages:
 gdm                           x86_64 1:47.0-8.fc41             updates        5.3 MiB
 gnome-session-wayland-session x86_64 47.0.1-1.fc41             fedora        15.9 KiB
 gnome-shell                   x86_64 47.1-1.fc41               updates       13.8 MiB

Transaction Summary:
 Removing:           4 packages
 
Is this ok [y/N]: N
...

I tried with the --noautoremove, and --exclude args and not result:

root@localhost:/home/mythcat# dnf5 remove --noautoremove --exclude=gnome-shell,gdm mutter
Failed to resolve the transaction:
Problem: installed package gnome-shell-47.1-1.fc41.x86_64 requires libmutter-15.so.0()(64bit), but none of the providers can be installed
  - installed package gnome-shell-47.1-1.fc41.x86_64 requires libmutter-clutter-15.so.0()(64bit), but none of the providers can be installed
  - installed package gnome-shell-47.1-1.fc41.x86_64 requires libmutter-cogl-15.so.0()(64bit), but none of the providers can be installed
  - installed package gnome-shell-47.1-1.fc41.x86_64 requires libmutter-mtk-15.so.0()(64bit), but none of the providers can be installed
  - installed package gnome-shell-47.1-1.fc41.x86_64 requires mutter(x86-64) >= 47.0, but none of the providers can be installed
  - conflicting requests
  - problem with installed package

The solution is old rpm tool:

root@localhost:/home/mythcat# rpm -e --nodeps mutter 
root@localhost:/home/mythcat# dnf5 remove mutter
No packages to remove for argument: mutter

Nothing to do.

Fedora 42 : ... testing Advanced Intrusion Detection Environment (AIDE).

Advanced Intrusion Detection Environment (AIDE) is a utility that creates a database of files on the system, and then uses that database to ensure file integrity and detect system intrusions.. See more on the official fedora documentation webpage.

NOTE : The documentation and translations on the official page are in progress due to ongoing development and resource management ...

I used the DNF tool to install:

[mythcat@fedora ~]$ sudo dnf install aide
... aide      x86_64      0.18.6-5.fc41        rawhide      

Make sure the AIDE database file exists and is accessible:

[mythcat@fedora ~]$ sudo ls -l /var/lib/aide/aide.db.gz

Ensure that the user running AIDE has the necessary permissions:

[mythcat@fedora ~]$ sudo ls -l /var/lib/aide/

Check the AIDE configuration file:

[mythcat@fedora ~]$ sudo cat /etc/aide.conf | grep DBDIR

Check if the AIDE service file exists:

[mythcat@fedora ~]$ sudo ls /usr/lib/systemd/system/ | grep aide

If the service exists then check the status:

[mythcat@fedora ~]$ sudo systemctl status aide
Unit aide.service could not be found.

If the service not exist then take some time to run first time ...

[mythcat@fedora ~]$ sudo /sbin/aide --init
...
End timestamp: 2024-10-26 14:10:00 +0300 (run time: 98m 41s)

You can check each time you want ...

[mythcat@fedora ~]$ sudo /sbin/aide --check

If you want and your Fedora linux need to use this tool, then you can use it like service:

sudo nano /usr/lib/systemd/system/aide.service

Fill with the basic service source code like any unit service :

[Unit]
   Description=Advanced Intrusion Detection Environment
   After=network.target

   [Service]
   Type=simple
   ExecStart=/sbin/aide --init
   ExecStop=/sbin/aide --check
   Restart=on-failure

   [Install]
   WantedBy=multi-user.target

This is a simple tutorial about how to start with AIDE tool ...

Fedora 42 : The cvxpy python module ... part 001.

We are building a CVXPY community on Discord. Join the conversation! CVXPY is an open source Python-embedded modeling language for convex optimization problems. It lets you express your problem in a natural way that follows the math, rather than in the restrictive standard form required by solvers.

Today I install the cvxpy python module ...

You can see on the official website - www.cvxpy.org .

NOTE: I don't understand why the blogger don't have a a code tag , I used a div - pre - code into txt file to wrote my posts ...

[mythcat@fedora ~]$ nano tutoriale.txt 

Let's see ...

[mythcat@fedora home]# dnf5 upgrade
[mythcat@fedora home]# dnf5 install openblas-devel
[mythcat@fedora home]# dnf5 install blas-devel
...
$ ldconfig -p | grep openblas
$ ldconfig -p | grep blas
...
[mythcat@fedora home]$ pip install cvxpy
...
Successfully built cvxpy ecos scs qdldl
Installing collected packages: scipy, scs, qdldl, ecos, clarabel, osqp, cvxpy
Successfully installed clarabel-0.9.0 cvxpy-1.5.2 ecos-2.0.14 osqp-0.6.7.post3 qdldl-0.1.7.post4 scipy-1.14.1 scs-3.2.7

Fedora 42 : First test with red language - part 001.

Red is a next-generation programming language strongly inspired by Rebol, but with a broader field of usage thanks to its native-code compiler, from system programming to high-level scripting and cross-platform reactive GUI, while providing modern support for concurrency, all in a zero-install, zero-config, single ~1MB file!

I download and change to be executable:

[mythcat@fedora ~]$ cd red-lang/
[mythcat@fedora red-lang]$ ls
red-03oct24-920dd0452  red-toolchain-03oct24-920dd0452  red-view-03oct24-920dd0452
[mythcat@fedora red-lang]$ ls -l
total 4444
-rw-r--r--. 1 mythcat mythcat 1347348 Oct  4 23:56 red-03oct24-920dd0452
-rw-r--r--. 1 mythcat mythcat 1611781 Oct  4 23:55 red-toolchain-03oct24-920dd0452
-rw-r--r--. 1 mythcat mythcat 1589092 Oct  4 23:55 red-view-03oct24-920dd0452
[mythcat@fedora red-lang]$ chmod 760 red*
[mythcat@fedora red-lang]$ ls -l
total 4444
-rwxrw----. 1 mythcat mythcat 1347348 Oct  4 23:56 red-03oct24-920dd0452
-rwxrw----. 1 mythcat mythcat 1611781 Oct  4 23:55 red-toolchain-03oct24-920dd0452
-rwxrw----. 1 mythcat mythcat 1589092 Oct  4 23:55 red-view-03oct24-920dd0452

I check and install these supporting libraries:

sudo yum install glibc.i686
sudo yum install libcurl.i686
sudo yum install gtk3.i686

I start with the basic intro example from the official website.

Then I need to check the missing files with the DNF tool and install Fedora packages for each error on runtime with executable result

dnf provides \*/libgtk-3.so.0

The result is this:

Fedora 42 : testing programming for ARM - part 001.

Today I tested the creation of a program that works on ARM processors and tested with QEMU emulator in Fedora 42.

I install with dnf5 these fedora packages:

[root@fedora mythcat]# dnf5 clean all
[root@fedora mythcat]# dnf5 install qemu-system-arm
[root@fedora mythcat]# dnf5 install arm-none-eabi-gcc gcc-arm-linux-gnu gcc-c++-arm-linux-gnu
[root@fedora mythcat]# dnf5 install arm-none-eabi-newlib.noarch 
...
[root@fedora mythcat]# dnf5 install binutils-devel

I create a new folder into may pagure account to test this issue with QEMU:

[mythcat@fedora mythcat]$ mkdir ARMProjects
[mythcat@fedora mythcat]$ cd ARMProjects/
[mythcat@fedora ARMProjects]$ qemu-system-arm --version
QEMU emulator version 9.1.0 (qemu-9.1.0-2.fc42)

I create a default assembly file for ARM named hello.s:

[mythcat@fedora ARMProjects]$ cat hello.s 
.global _start

_start:
    mov r0, #1     
    mov r7, #4     
    str r0, [r7]
    bx lr

Let's see how this means:

global _start: This declares the _start label as global, making it
 accessible from outside the file.
_start:: This marks the beginning of the program.
mov r0, #1: Moves the immediate value 1 into register R0.
mov r7, #4: Moves the immediate value 4 into register R7. This represents the system call number for write().
str r0, [r7]: Stores the contents of R0 (which contains 1) into the memory address pointed to by R7.
bx lr: Branches to the address in Link Register (LR). In this case, it loops indefinitely because there's no return instruction.

The compile of the file:

[mythcat@fedora ARMProjects]$ arm-none-eabi-gcc -nostartfiles -lc hello.s -o hello.o
[mythcat@fedora ARMProjects]$ ls
hello.o  hello.s

Let's see the hello.o file:

[mythcat@fedora ARMProjects]$ nm hello.o
00008000 t $a
00009010 T __bss_end__
00009010 T _bss_end__
00009010 T __bss_start
00009010 T __bss_start__
00009010 T __data_start
00009010 T _edata
00009010 T __end__
00009010 T _end
00080000 B _stack
00008000 T _start
[mythcat@fedora ARMProjects]$ objdump -f hello.o

hello.o:     file format elf32-little
architecture: UNKNOWN!, flags 0x00000112:
EXEC_P, HAS_SYMS, D_PAGED
start address 0x00008000

Fedora 42 : ima: Error Communicating to TPM chip ... cannot be fixed.

TPM stands for Trusted Platform Module. It's a hardware security chip designed to provide cryptographic capabilities and perform platform authentication.

I found this error and I tried to fix on my laptop HP 6710b:

[mythcat@fedora ~]$ sudo dmesg | grep Error
[    1.274790] tpm tpm0: [Hardware Error]: Adjusting reported timeouts: A 750->750000us B 2000->2000000us C 750->750000us D 750->750000us
[    2.240276] ima: Error Communicating to TPM chip
[    2.243913] ima: Error Communicating to TPM chip
[    2.246923] ima: Error Communicating to TPM chip
[    2.249919] ima: Error Communicating to TPM chip
[    2.253088] ima: Error Communicating to TPM chip
[    2.255923] ima: Error Communicating to TPM chip
[    2.258921] ima: Error Communicating to TPM chip
[    2.261938] ima: Error Communicating to TPM chip
[    2.415255] RAS: Correctable Errors collector initia

I update and nistall with the dnf5 tool

[root@fedora mythcat]# dnf5 upgrade 
...
[root@fedora mythcat]# dnf install tpm-tools
...

I reboot the Fedora and I try to test it:

[mythcat@fedora ~]$ ls /dev/tpm*
/dev/tpm0
[mythcat@fedora ~]$ lsmod | grep tpm
tpm_infineon           20480  0

To see all commands, use:

[mythcat@fedora ~]$ tpm_
tpm_changeownerauth  tpm_nvwrite          tpm_setclearable
tpm_clear            tpm_resetdalock      tpm_setenable
tpm_createek         tpm_restrictpubek    tpm_setoperatorauth
tpm_getpubek         tpm_restrictsrk      tpm_setownable
tpm_nvdefine         tpm_revokeek         tpm_setpresence
tpm_nvinfo           tpm_sealdata         tpm_takeownership
tpm_nvread           tpm_selftest         tpm_unsealdata
tpm_nvrelease        tpm_setactive        tpm_version

I install tcsd

[root@fedora mythcat]#  dnf install tcsd
...
[mythcat@fedora ~]$ sudo usermod -a -G tss $USER
[root@fedora mythcat]# systemctl daemon-reload
[root@fedora mythcat]# systemctl start tcsd
[root@fedora mythcat]#  systemctl status tcsd

I check the tpm version vith:

[mythcat@fedora ~]$ tpm_version
  TPM 1.2 Version Info:
  Chip Version:        1.2.1.2
  Spec Level:          2
  Errata Revision:     0
  TPM Vendor ID:       IFX
  TPM Version:         01010000
  Manufacturer Info:   49465800
[mythcat@fedora ~]$ sudo dnf5 search tpm2-tools
Updating and loading repositories:
Repositories loaded.
Matched fields: name (exact)
 tpm2-tools.x86_64: A bunch of TPM testing toolS build upon tpm2-tss
[mythcat@fedora ~]$ sudo dnf5 install tpm2-tools
...
Package "tpm2-tools-5.7-2.fc41.x86_64" is already installed.

The last error :

[mythcat@fedora ~]$ sudo tpm2_startup
ERROR:tcti:src/tss2-tcti/tcti-device.c:455:Tss2_Tcti_Device_Init() Failed to open specified TCTI device file /dev/tpmrm0: No such file or directory 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:149:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-device.so.0 
ERROR:tcti:src/tss2-tcti/tcti-device.c:455:Tss2_Tcti_Device_Init() Failed to open specified TCTI device file /dev/tpm0: Device or resource busy 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:149:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-device.so.0 
ERROR:tcti:src/tss2-tcti/tcti-device.c:455:Tss2_Tcti_Device_Init() Failed to open specified TCTI device file /dev/tcm0: No such file or directory 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:149:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-device.so.0 
WARNING:tcti:src/util-io/io.c:262:socket_connect() Failed to connect to host 127.0.0.1, port 2321: errno 111: Connection refused 
ERROR:tcti:src/tss2-tcti/tcti-swtpm.c:617:Tss2_Tcti_Swtpm_Init() Cannot connect to swtpm TPM socket 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:149:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-swtpm.so.0 
WARNING:tcti:src/util-io/io.c:262:socket_connect() Failed to connect to host 127.0.0.1, port 2321: errno 111: Connection refused 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:149:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-mssim.so.0 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:263:tctildr_get_default() No standard TCTI could be loaded 
ERROR:tcti:src/tss2-tcti/tctildr.c:477:tctildr_init_context_data() Failed to instantiate TCTI 
ERROR: Could not load tcti, got: "(null)"

Fedora 40 : Find version and GlibC flaw !

Because today I saw a video about the GlibC flaw that lets attackers get root on major distros, I will show an easy way to find the version of this lib with dnf and dnf5 tools:

[root@fedora var]# dnf in glibc
Last metadata expiration check: 0:04:06 ago on Wed 31 Jan 2024 10:25:13 PM EET.
Package glibc-2.38.9000-35.fc40.x86_64 is already installed.
Package glibc-2.38.9000-35.fc40.i686 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
[root@fedora var]# dnf5 in glibc
Updating and loading repositories:
Repositories loaded.
Package "glibc-2.38.9000-35.fc40.x86_64" is already installed.
Package "glibc-2.38.9000-35.fc40.i686" is already installed.

You can see in the name is add the version: 2.38.9000-35.fc40.x86_64.

This is the video about GlibC from Bits inside by René Rebe.

Fedora 39 : Fixing common upgrade issues.

The most common issue is that the Linux system hangs due to disk space and upgrades.

Here's what you need to do:

Ensure you have root access by editing the boot sequence from the boot menu with the word single and entering the root password.

... start the network in the maintenance environment with the command:

# systemctl restart NetworkManager

Check if you can update with the DNF5 tool or DNF , see this webpage:

# dnf5 upgrade --refresh

If the update tool tells you that you have no space available, then you can clean up with:

# journalctl --disk-usage
# journalctl --vacuum-size=16M

The size of 16M is a relative size related to how the resource is allocated!

Another possibility would be to reallocate the space.

NOTE: If you are using a virtual disk with .vdi extension on Windows OS, then I don't have a solution.

Although virtualbox has an interface that would allow resizing the virtual disk, it didn't work for me.

Fedora 39 : Issues in Fedora with PyGobject and sway-tests.

Today I wanted to test this repo named sway-tests.

I followed the steps there and received an error from gi.repository.

This error is related to another issue related to PyGobject.

In Fedora Linux distro, installing PyGobject is done with pip like this:

$ pip install PyGobject

In order to have no errors, the dnf or dnf5 tool should be used like this ...

I tested the functionality of this installation with a simple example:

import gi

gi.require_version("Gtk", "3.0")
from gi.repository import Gtk

win = Gtk.Window()
win.connect("destroy", Gtk.main_quit)
win.show_all()
Gtk.main()

It worked very well.

After solving this issue, I returned to the initial one and tested the sway-tests.

$ whereis sway
$ env/bin/pytest --sway=/usr/bin/sway
$ sudo env/bin/pytest --sway=/usr/bin/sway

I used the command both with and without sudo.

Both generated the same errors.

For the following command I had to install ... xorg-x11-server-Xephyr:

Xephyr is an X server which has been implemented as an ordinary X application. It runs in a window just like other X applications, but it is an X server ...

... the fixed centered black window specific to the xorg runtime appeared and somewhere on the side the terminal showed me a bunch of errors.

... obviously, I don't know how well sway-tests is implemented, now it's an archived repo, but I solved the use of PyGobject in python on the Fedora linux distribution.

Fedora 39 : How to start using cockpit tool in firefox.

Use lie any default installation like any Fedora Linux Distro package for cockpit tool with DNF or DNF5 tool.

$ sudo su
# dnf5 install cockpit
# systemctl enable --now cockpit.socket
# firewall-cmd --add-service=cockpit
# firewall-cmd --add-service=cockpit --permanent
# exit

The next step is to test if this runs well.

Get your ip address with netstat:

$ netstat nr

Because I used an virtual box for testing Fedora I get this ip 10.0.2.0

Use with firefox in the terminal:

$ firefox http://10.0.2.0:9090

The result will be the online cockpit tool.

Fedora 39 : DNF, DNF-3 and DNF5

Before installing DNF5 you should know that your installations with this tool in the fedora distribution may not work correctly

After implementation of dnf5 module install dnf and dnf5 cannot share the same location for storing state of modules, because dnf5 will store additional information about installed profiles (braking change). Modules enabled by DNF5 (dnf5 module enable <module>) will be not seen as enabled in DNF. Module profile installed by DNF5 will be not sees as installed in DNF. DNF will only see installed RPMs.

More details on this official webpage.

You can fix it with the dnf-3 tool if you accidentally modified or deleted the dnf tool.

A simple example is installing Deepin Desktop, which I could only install with DNF-3:

# dnf-3 install @deepin-desktop

The other dnf and dnf5 tools didn't work, I didn't wait to check if it's because of the repos. but it did not bring me the packets from the web and shows me transactions of 0 B.

Fedora 39 : DNF5 error update.

Sometimes errors may occur when installing Fedora packages using the dnf or dnf5 utility. One of the reasons may result from the coincidence of the package installation process. If you know how to build packages, how to develop the Fedora team, and how many repositories you have set up in your Linux distribution, then such an error can be easily fixed. Here is the error:

First, install the dnf5 and dnf5-plugins with this command:

sudo dnf install dnf5 dnf5-plugins

One good way to fix error is to have defined settings in : /etc/dnf/dnf.conf in order to have a good installation flow and how to link packages to the interconnected job.

See my example that fix this error:

Some packages may conflict in the repo and you can check with the dnf info fedora_repo_package command.

For example, you can use exclude=*.noarch in the [main] area.

Fedora 39 : Using a stick or hard disk created in Windows.

When attached to USB, Linux distribution cannot access it.

Install these packages with the DNF utility.

sudo dnf install ntfs-3g
sudo dnf install ntfsfix

Use these commands to create a folder where it will be mounted and test if it can be mounted and where it is viewed :

sudo mkdir /mnt/mydrive
sudo mount -t ntfs-3g /dev/sdb1 /mnt/mydrive
dmesg| grep usb 
sudo mount /dev/sdb /mnt/mydrive
df -h

Fix errors with this command

sudo umount /dev/sdb1
sudo ntfsfix /dev/sdb1

It resumes the operation of mounting it in the folder named /mnt/mydrive:

sudo mount -t ntfs-3g /dev/sdb1 /mnt/mydrive

This command will mount as a superuser but can be modified as a normal user.

Create a USB folder into your home folder as normal user.

You can use these commands to use your files like a normal user:

[mythcat@fedora ~]$ sudo mount -t ntfs-3g /dev/sdb1 ~/USB
[sudo] password for mythcat: 
...
[mythcat@fedora ~]$ sudo umount /dev/sdb1

Fedora 39 : The vifm file manager ...

My monitor broke a few days ago so i'm using an old laptop. Website posts will be less frequent.

You can use the vifm file manager in Fedora 39 easy.

Use the DNF command tool to install it.

[root@fedora mythcat]# dnf install vifm

See the result of this file manager:

Fedora 39 : Fedora 39 Cinnamon environment pre-release - upgrade.

Today I tested the new version of fedora 39 and it worked very well.

If you want to upgrade Fedora using the DNF system upgrade then you can find all information on the official webpage.

You can try a Fedora 39 Cinnamon environment pre-release from this website.

A very good feature comes with this new command remove-retired-packages.

This allow you to keep the all packages with update.

Fedora 37 : Lite editor.

lite is a lightweight text editor written mostly in Lua — it aims to provide something practical, pretty, small and fast, implemented as simply as possible; easy to modify and extend, or to use without doing either.

You can find this project on GitHub.

I install with DNF tool:

# dnf install lite-xl.x86_64
...
Installed:
  lite-xl-2.1.1-2.fc38.x86_64                                                   

Complete!

... and works very well:

Fedora 37 : Vala development in Fedora 37.

Yesterday I tested the Vala programming language on the Fedora 37 linux distribution. The basic idea was that most linux distribution environments use the GTK+ toolkit that Gnome developed. Development with GTK+ can be done with various programming languages: c, python, rust... The main reason why I tested the implementation of the Vala programming language was that Gnome developed it.

For the installation, I used the DNF utility with the following commands to install the packages necessary for the operation of the development in Vala

$sudo dnf groupinstall "Development Tools" "Development Libraries"
$ sudo dnf install vala

The first command installs the tools that are essential to perform tasks such as installing packages from source code.

The second command only installs the Vala package.

To test the written program we will need to use the Valac compiler and then run it as a simple executable in Linux.

$valac --pkg gtk+-3.0 test.vala 
$ ./test

(test:6198): GLib-GObject-CRITICAL **: 14:34:11.454: g_value_set_boxed: assertion 'G_VALUE_HOLDS_BOXED (value)' failed 

The error is about the implementation of Vala in Fedora, I don't have an answer of this but in other Linux distributions this is not show.

If you want to use WebKit2GTK+ Extensions then you need to compile it.

valac test.vala  --pkg gtk+-3.0 --pkg webkit2gtk-4.0

Is a more easy way to developm application but you need to know well how to deal with GTK and GObject structure.

Fedora 37 : Use radiotray-ng to simple radio player.

Radiotray-NG is a simple radio player for Ubuntu that runs from the system tray.

You can use this command to install the package.

dnf install radiotray-ng

After installation, you will see an icon on the tray area.

Use this to select the radio and this will play it.

The project can be found on GitHub.

.

Fedora 37 : Starting with the conda tool.

In this tutorial, I will show the first steps for working with conda tool on Fedora 37.

Conda is an open-source package management system and environment management system that runs on Windows, macOS, Linux, and z/OS. Conda quickly installs, runs, and updates packages and their dependencies. Conda easily creates, saves, loads, and switches between environments on your local computer. It was created for Python programs, but it can package and distribute software for any language., see the official webpage.

I used the DNF tool to install this tool.

[root@fedora mythcat]# dnf install conda

By default, Conda is configured to activate the base environment when I open a fresh terminal session and you can set it to false.

[mythcat@fedora ~]$ conda config --set auto_activate_base false

For the changes to be applied, run the source command with the .bashrc file as an argument.

[mythcat@fedora ~]$ source ~/.bashrc

After installation, the conda can be activated with the base environment.

[mythcat@fedora ~]$ conda activate
(base) [mythcat@fedora ~]$ conda deactivate
[mythcat@fedora ~]$

Let's start a new project environment named test001 with this command:

[mythcat@fedora ~]$ conda create -n test001 python=3.9
...
  zlib               pkgs/main/linux-64::zlib-1.2.12-h5eee18b_3
Proceed ([y]/n)? y
Downloading and Extracting Packages
libffi-3.3           | 50 KB     | ##################################### | 100%
...
setuptools-63.4.1    | 1.1 MB    | ##################################### | 100%
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
#
# To activate this environment, use
#
#     $ conda activate test001
#
# To deactivate an active environment, use
#
#     $ conda deactivate

The next step is to activate this with the next command and list installed packages in a conda environment.

[mythcat@fedora ~]$ conda activate test001
(test001) [mythcat@fedora ~]$ conda list

If you want to see all environments then use the next command:

(test001) [mythcat@fedora ~]$ conda env list
# conda environments:
#
test001               *  /home/mythcat/.conda/envs/test001
base                     /usr

The basic usage of conda is to install packages, you can see how to install the scipy package with the next command:

(test001) [mythcat@fedora ~]$ conda install scipy

Using the conda tool.

Also, you can update a package like the pip tool, see the next command:

(test001) [mythcat@fedora ~]$ conda update
CondaValueError: no package names supplied
# Example: conda update -n myenv scipy 

You can deactivate/deactivate the environment with these commands:

(test001) [mythcat@fedora ~]$ conda deactivate
[mythcat@fedora ~]$ conda activate test001
(test001) [mythcat@fedora ~]$ 

You can export the conda environment into YML file type:

(test001) [mythcat@fedora ~]$ conda env export > test001.yml
(test001) [mythcat@fedora ~]$ ls test001.yml
test001.yml 

With this file, you can create a new environment in another area, and see the next commands for deactivating and creating the new environment.

(test001) [mythcat@fedora ~]$ conda deactivate
[mythcat@fedora ~]$ ls
Desktop    Downloads     Music     Public     test001.yml
Documents  kernel-tests  Pictures  Templates  Videos
[mythcat@fedora ~]$ conda env create -f test001.yml
CondaValueError: prefix already exists: /home/mythcat/.conda/envs/test001

Because I try to create in the same place as the old environment I got this error.

You need to use the YML file in another place.

Another option is to clone one environment.

[mythcat@fedora ~]$ conda create --name test001_new_clone --clone test001
Source:      /home/mythcat/.conda/envs/test001
Destination: /home/mythcat/.conda/envs/test001_new_clone
Packages: 34
...

You can see all environments with this command:

[mythcat@fedora ~]$ conda info --env
# conda environments:
#
test001                  /home/mythcat/.conda/envs/test001
test001_new_clone        /home/mythcat/.conda/envs/test001_new_clone
base                  *  /usr

These commands shown are just the beginning of working with the conda utility. It has many more development options.

Fedora 37 : Kernel Test Days.

The main goal of a Kernel Test Day is to test a new kernel on many different machines as possible ...

To test the kernel and help the Fedora development team you need to run one tool from Fedora.

I used DNF to install the fedora python package.

[root@fedora kernel-tests]# dnf install python3-fedora.noarch
...
Installed:
  python3-fedora-1.1.1-7.fc37.noarch                                            
  python3-kitchen-1.2.6-14.fc37.noarch                                          
  python3-lockfile-1:0.12.2-8.fc37.noarch                                       
  python3-munch-2.5.0-10.fc37.noarch                                            
  python3-openidc-client-0.6.0-17.20220119git0e2ed81.fc37.noarch                

Complete!

I install the Development Tools group for development issues.

[mythcat@fedora kernel-tests]$ sudo dnf -y groupinstall "Development Tools"

I clone the kernel-tests tool from the GitHub repository.

[mythcat@fedora ~]$ git clone https://pagure.io/kernel-tests.git
Cloning into 'kernel-tests'...

Into the folder kernel-tests set your user and password to send data to the Fedora development team.

[mythcat@fedora ~]$ cd kernel-tests/
[mythcat@fedora kernel-tests]$ cp config.example .config
[mythcat@fedora kernel-tests]$ vi .config

Set the SELinux settings, if this is enabled.

[mythcat@fedora kernel-tests]$ sudo semanage boolean -m --on selinuxuser_execheap

I run both tests, like in the documentation area.

See these results of my tests on HP Compaq 6710b laptop:

[mythcat@fedora kernel-tests]$ sudo ./runtests.sh
[sudo] password for mythcat:
Test suite called with default
./default/cachedrop                                              PASS    
./default/insert_leap_second                                     PASS    
./default/libhugetlbfs                                           SKIP    
./default/memfd                                                  PASS    
./default/modsign                                                PASS    
./default/mq-memory-corruption                                   PASS    
./default/paxtest                                                SKIP    
./default/posix_timers                                           PASS    
./default/selinux-dac-controls                                   PASS    
./default/stack-randomness                                       PASS    
./default/sysfs-perms                                            WARN    
./default/timer-overhead                                         PASS    

Test suite complete                                              WARN    

Your log file is being submitted...
Upload successful!
The following information is not submitted with your log;
it is for informational purposes only.
Vulnerability status:
/sys/devices/system/cpu/vulnerabilities/itlb_multihit:KVM: Mitigation: VMX unsupported
/sys/devices/system/cpu/vulnerabilities/l1tf:Mitigation: PTE Inversion
/sys/devices/system/cpu/vulnerabilities/mds:Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
/sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/mmio_stale_data:Not affected
/sys/devices/system/cpu/vulnerabilities/retbleed:Not affected
/sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: usercopy/swapgs barriers and __user pointer sanitization
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected
/sys/devices/system/cpu/vulnerabilities/srbds:Not affected
/sys/devices/system/cpu/vulnerabilities/tsx_async_abort:Not affected

[mythcat@fedora kernel-tests]$ sudo ./runtests.sh -t performance
Test suite called with performance
Using config in CONFIG.fedora
Sun Aug 21 05:19:23 PM EEST 2022
Latency measurements
Sun Aug 21 05:21:46 PM EEST 2022
Calculating file system latency
Sun Aug 21 05:21:48 PM EEST 2022
Local networking
Sun Aug 21 05:25:29 PM EEST 2022
Bandwidth measurements
Sun Aug 21 05:34:57 PM EEST 2022
Calculating context switch overhead
Sun Aug 21 05:35:20 PM EEST 2022
./performance/lmbench3                                           PASS    

Test suite complete                                              PASS    

Your log file is being submitted...
Upload successful!
The following information is not submitted with your log;
it is for informational purposes only.
Vulnerability status:
/sys/devices/system/cpu/vulnerabilities/itlb_multihit:KVM: Mitigation: VMX unsupported
/sys/devices/system/cpu/vulnerabilities/l1tf:Mitigation: PTE Inversion
/sys/devices/system/cpu/vulnerabilities/mds:Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
/sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/mmio_stale_data:Not affected
/sys/devices/system/cpu/vulnerabilities/retbleed:Not affected
/sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: usercopy/swapgs barriers and __user pointer sanitization
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected
/sys/devices/system/cpu/vulnerabilities/srbds:Not affected
/sys/devices/system/cpu/vulnerabilities/tsx_async_abort:Not affected