Category: Fedora

Fedora 39 - GNOME 45 - missing "Suspend when lid is closed" in Tweak Tools

Published on Author admin

By default in GNOME 45 option "Suspend when lid is closed" no more exists. Follow below steps to prevent Fedora 39 Workstation from suspend when laptop lid is closed. as normal user: create ~/.config/autostart/ignore-lid-switch-tweak.desktop file with following content [Desktop Entry] Type=Application Name=ignore-lid-switch-tweak Exec=/usr/libexec/gnome-tweak-tool-lid-inhibitor as root: create /usr/libexec/gnome-tweak-tool-lid-inhibitor file with following content: #!/usr/bin/python3 # SPDX-License-Identifier: GPL-3.0+… Continue reading Fedora 39 - GNOME 45 - missing "Suspend when lid is closed" in Tweak Tools →

Fedora - unlock LUKS full disk encrypted system using USB stick

Published on Author admin

Follow below steps to enable unlocking LUKS full disk encrypted system using key file stored on USB stick Format USB key with FAT32 filesystem. Generate random keyfile: dd if=/dev/urandom of=/path/to/usbdisk/keyfile bs=4096 count=1 Add key to luks volume: cryptsetup luksAddKey /dev/sda6 /path/to/usbdisk/keyfile Check USB partition disk UUID: lsblk /dev/sdb1 -o NAME,UUID XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX - UUID of LUKS… Continue reading Fedora - unlock LUKS full disk encrypted system using USB stick →

Fedora 36 - fix for issue with new kernel installation

Published on Author admin

Sympthons: On UEFI Fedora 36 machines with long upgrade history (for instance starting from F25) you can encounter problem that after "dnf update kernel-core" new kernels are not being installed. Reason: When directory /boot/efi// is present, system is trying to install new kernel images into /boot/efi// instead of /boot/, which issues with /boot/efi/ overflow. Resoloution:… Continue reading Fedora 36 - fix for issue with new kernel installation →

Docker 20.10 fails to start on CentOS 8 and Fedora 33

Published on Author admin

After upgrading Docker to version 20.10 on CentOS 8 and Fedora 33 we can see that it fails to start docker.service. In docker.service logs and firewalld.service logs we can see following message: ERROR: ZONE_CONFLICT: 'docker0' already bound to a zone Solution for this issue: sudo firewall-cmd --zone=trusted --remove-interface=docker0 sudo firewall-cmd --zone=trusted --remove-interface=docker0 --permanent