Fedora People

Fedora Women’s Day (FWD) 2019

Posted by Solanch96 on November 12, 2019 03:19 PM

El FWD (Fedora Women's Day) es un evento realizado anualmente, que se compromete a fomentar la diversidad y la inclusión en la comunidad de Fedora

<script> __ATA.cmd.push(function() { __ATA.initDynamicSlot({ id: 'atatags-26942-5dcb18c243f03', location: 120, formFactor: '001', label: { text: 'Anuncios', }, creative: { reportAd: { text: 'Informar de este anuncio', }, privacySettings: { text: 'Privacy settings', } } }); }); </script>

Fedora status updates: October 2019

Posted by Fedora Community Blog on November 12, 2019 06:36 AM
Fedora community elections

Welcome to the monthly set of updates on key areas within Fedora. This update includes Fedora Council representatives, Fedora Editions, and Fedora Objectives. The content here is based on the weekly updates submitted to the Fedora Council, published to the project dashboard.

Minimization objective

The Minimization objective submitted an updated proposal to the Fedora Council. Objective lead Adam Šamalík developed a logic model to help define the future work of the Minimization objective.


The Fedora Silverblue team was not able to get the necessary changes into Fedora 31 to support having Flatpak pre-installed. They are looking at the possibility of re-spinning the Silverblue ISO to incorporate the changes. But they did update the Fedora 31 Flatpak runtime. The team updated the Flatpak’ed GNOME applications to GNOME 3.34 and built them against the Fedora 31 runtime.

The team is planning for Fedora 32. See the Kanban board for more information.

Workstation WG

The Workstation WG is looking at how to increase membership and participation in the working group. Discussion is ongoing in issue #106. But the WG has started a subgroup investigating the possibility of encrypting user home directories by default. Meeting agendas and notes are available on the GNOME etherpad. Discussion is also occurring on the desktop mailing list.

Of course, Fedora 31 released at the end of the month. Fedora 31 Workstation included better support for non-English users, improved H.264 support, and many other enhancements. The working group hopes to support Wayland by default on Nvidia GPUs in Fedora 32.

The post Fedora status updates: October 2019 appeared first on Fedora Community Blog.

Upgrade Fedora 30 to Fedora 31

Posted by Robbi Nespu on November 12, 2019 05:42 AM
<script src="https://gist.github.com/30fac19b83d93eca068f1295ef33cc0f.js"> </script>

How to override bug details in Kiwi TCMS

Posted by Kiwi TCMS on November 11, 2019 09:11 AM

Starting with version 7.0 Kiwi TCMS pages displaying URLs to bugs also contain an info icon which shows additional information as tooltip. These are designed to provide more contextual information about the bug. By default the tooltip shows the OpenGraph metadata for that URL. This article will explain how to override this in 2 different ways.

bug details shown

Option #1: using the caching layer

Additional bug information is cached on the application layer. The cache key is the bug URL! By default Kiwi TCMS uses local-memory caching which isn't accessible for external processes but can be reconfigured very easily. This example changes the CACHES setting to use a directory on the file system like so

    'default': {
        'BACKEND': 'django.core.cache.backends.filebased.FileBasedCache',
        'LOCATION': '/tmp/kiwi-cache',
        'TIMEOUT': 3600,

Then you need to poll your 3rd party bug tracker (and/or other systems) and update the cache for each URL

from django.core.cache import cache
from tcms.core.contrib.linkreference.models import LinkReference

for reference in LinkReference.objects.filter(is_defect=True):
    # possibly filter objects coming only from your own bug tracker
    # in case there are multiple trackers in use

    # custom methods to grab more information. Must return strings
    title = fetch_title_from_bug_tracker(reference.url)
    description = fetch_description_from_bug_tracker(reference.url)

    # store the information in Kiwi TCMS cache
    cache.set(reference, {'title': title, 'description': description})

Then execute the Python script above regularly. For example use the following as your cron script

export VIRTUAL_ENV=/venv
export PATH=/venv/bin:${PATH}
cat /path/to/cache_updater.py | /Kiwi/manage.py shell

bug details from customized cache


  • Kiwi TCMS expires cache entries after an hour. Either change the TIMEOUT setting shown above or run your script more frequently
  • How to modify default Kiwi TCMS settings is documented here
  • The Python + Bash scripts above don't need to be on the same system where Kiwi TCMS is hosted. However they need the same Python 3 virtualenv and cache settings as Kiwi TCMS does
  • Information about Django's cache framework and available backends can be found here
  • memcached is a supported cache backend option, see here
  • django-elasticache is a backend for Amazon ElastiCache which provides several configuration examples
  • Both django-redis and django-redis-cache are good libraries which support Redis
  • Any 3rd party libraries must be pip3 install-ed into your own docker image

Option #2: extend bug tracker integration

Let's say you are already running a customized Docker image of Kiwi TCMS. Then you may opt-in to extend the existing bug tracker integration code which provides the information shown in the tooltip. In this example I've extended the KiwiTCMS bug tracker implementation but you can even provide your own from scratch

class ExtendedBugTracker(KiwiTCMS):
    def details(self, url):
        result = super().details(url)

        result['title'] = 'EXTENDED: ' + result['title']
        result['description'] += '<h1>IMPORTANT</h1>'

        return result

Then import the new ExtendedBugTracker class inside tcms/issuetracker/types.py like so

index 9ad90ac..2c76621 100644
--- a/tcms/issuetracker/types.py
+++ b/tcms/issuetracker/types.py
@@ -17,6 +17,9 @@ from django.conf import settings

 from tcms.issuetracker.base import IssueTrackerType
 from tcms.issuetracker.kiwitcms import KiwiTCMS  # noqa
+from tcms.issuetracker.kiwitcms import ExtendedBugTracker

and change the bug tracker type, via https://tcms.example.com/admin/testcases/bugsystem/, to ExtendedBugTracker.

bug details extended internally


  • ExtendedBugTracker may live anywhere on the filesystem but Python must be able to import it
  • It is best to bundle all of your customizations into a Python package and pip3 install it into your customized docker image
  • ExtendedBugTracker must be imported into tcms/issuetracker/types.py in order for the admin interface and other functions to find it. You may also place the import at the bottom of tcms/issuetracker/types.py
  • API documentation for bug tracker integration can be found here
  • Rebuilding the docker image is outside the scope of this article. Have a look at this Dockerfile for inspiration

Happy testing!

Understanding “disk space math”

Posted by Fedora Magazine on November 11, 2019 07:44 AM

Everything in a PC, laptop, or server is represented as binary digits (a.k.a. bits, where each bit can only be 1 or 0). There are no characters like we use for writing or numbers as we write them anywhere in a computer’s memory or secondary storage such as disk drives. For general purposes, the unit of measure for groups of binary bits is the byte — eight bits. Bytes are an agreed-upon measure that helped standardize computer memory, storage, and how computers handled data.

There are various terms in use to specify the capacity of a disk drive (either magnetic or electronic). The same measures are applied to a computers random access memory (RAM) and other memory devices that inhabit your computer. So now let’s see how the numbers are made up.

Suffixes are used with the number that specifies the capacity of the device. The suffixes designate a multiplier that is to be applied to the number that preceded the suffix. Commonly used suffixes are:

  • Kilo = 103 = 1,000 (one thousand)
  • Mega = 106 = 1,000,000 (one million)
  • Giga = 109 = 1000,000,000 (one billion)
  • Tera = 1012 = 1,000,000,000,000 (one trillion)

As an example 500 GB (gigabytes) is 500,000,000,000 bytes.

The units that memory and storage are specified in  advertisements, on boxes in the store, and so on are in the decimal system as shown above. However since computers only use binary bits, the actual capacity of these devices is different than the advertised capacity.

You saw that the decimal numbers above were shown with their equivalent powers of ten. In the binary system numbers can be represented as powers of two. The table below shows how bits are used to represent powers of two in an 8 bit Byte. At the bottom of the table there is an example of how the decimal number 109 can be represented as a binary number that can be held in a single byte of 8 bits (01101101).

Eight bit binary number


Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2

Bit 1

Bit 0

Power of 2









Decimal Value









Example Number









The example bit values comprise the binary number 01101101. To get the equivalent decimal value just add the decimal values from the table where the bit is set to 1. That is 64 + 32 + 8 + 4 + 1 = 109.

By the time you get out to 230 you have decimal 1,073,741,824 with just 31 bits (don’t forget the 20) You’ve got a large enough number to start specifying memory and storage sizes.

Now comes what you have been waiting for. The table below lists common designations as they are used for labeling decimal and binary values.



KB (Kilobyte)

1KB = 1,000 bytes

KiB (Kibibyte)

1KiB = 1,024 bytes

MB (Megabyte)

1MB = 1,000,000 bytes

MiB (Mebibyte)

1MiB = 1,048,576 bytes

GB (Gigabyte)

1GB = 1,000,000,000 bytes

GiB (Gibibyte)

1 GiB (Gibibyte) = 1,073,741,824 bytes

TB (Terabyte)

1TB = 1,000,000,000,000

TiB (Tebibyte)

1TiB = 1,099,511,627,776 bytes

Note that all of the quantities of bytes in the table above are expressed as decimal numbers. They are not shown as binary numbers because those numbers would be more than 30 characters long.

Most users and programmers need not be concerned with the small differences between the binary and decimal storage size numbers. If you’re developing software or hardware that deals with data at the binary level you may need the binary numbers.

As for what this means to your PC: Your PC will make use of the full capacity of your storage and memory devices. If you want to see the capacity of your disk drives, thumb drives, etc, the Disks utility in Fedora will show you the actual capacity of the storage device in number of bytes as a decimal number.

There are also command line tools that can provide you with more flexibility in seeing how your storage bytes are being used. Two such command line tools are du (for files and directories) and df (for file systems). You can read about these by typing man du or man df at the command line in a terminal window.

Photo by Franck V. on Unsplash.

Episode 169 - What happens when leadership doesn't care about security?

Posted by Open Source Security Podcast on November 11, 2019 01:19 AM

Josh and Kurt talk about government security incidents. The security concerns at the government level often have real life and death consequences. What happens when the leadership knowingly disregards security policy?

<iframe allowfullscreen="" height="90" mozallowfullscreen="" msallowfullscreen="" oallowfullscreen="" scrolling="no" src="https://html5-player.libsyn.com/embed/episode/id/11981144/height/90/theme/custom/thumbnail/yes/direction/backward/render-playlist/no/custom-color/6e6a6a/" style="border: none;" webkitallowfullscreen="" width="100%"></iframe>

Show Notes

    Fedora 31 : another FASM tutorial with Linux.

    Posted by mythcat on November 10, 2019 04:35 PM
    Today I wrote another tutorial about FASM and assembly language on my website.
    Because I used the Fedora distro I add my tutorial here.
    If you want to learn assembly programming for Windows O.S. or Linux with the Intel C.P.U. then you need the FASM tool and this manual.
    Today I will show you how to create a file using my Fedora 31 Linux distro and FASM tool.
    The name of this file will be new_file.txt.
    The assembly program will use INT 0x08 to create the file.
    entry _start

    filename db "new_file.txt", 0

    ; create a new file
    mov rax, 8
    mov rbx, filename
    mov rcx, 0011
    int 0x80

    ; use descriptor
    push rax

    ; close the new file
    mov rax, 6
    pop rbx
    int 0x80

    call exit

    mov rax, 1
    mov rbx, 0
    int 0x80
    The program also set the file permissions in the rcx register.
    Let's see some octal permissions:
        mov rcx, 000

    ----------. 1 mythcat mythcat 0 Nov 10 17:40 new_file.txt
    mov rcx, 0001

    ---------x. 1 mythcat mythcat 0 Nov 10 17:41 new_file.txt
    mov rcx, 0011

    ------x--x. 1 mythcat mythcat 0 Nov 10 17:43 new_file.txt

    Fedora 31 : Use bash script to see all the permissions.

    Posted by mythcat on November 10, 2019 04:34 PM
    This tutorial will show you how to generate all the permissions using one file named file_test.
    [mythcat@desk ~]$ mkdir my_bash_scripts
    [mythcat@desk ~]$ cd my_bash_scripts/
    [mythcat@desk my_bash_scripts]$ vim all_permissions.sh
    [mythcat@desk my_bash_scripts]$ vim all_permissions.sh
    [mythcat@desk my_bash_scripts]$ chmod +x all_permissions.sh
    [mythcat@desk my_bash_scripts]$ ls
    Let's see the bash script file named all_permissions.sh:
    #loops through a chmod sequence

    touch file_test
    while [ "$foo" -ne 7778 ];do
    echo $foo >> out
    chmod $foo file_test
    ls -gG >> out
    egrep -v '(all_permissions.sh)|(total)|(out)' out > results
    echo "use command cat results to see permissions for file_test."

    exit 0
    You can run the script:
    [mythcat@desk my_bash_scripts]$ ./all_permissions.sh 
    Try 'chmod --help' for more information.
    chmod: invalid mode: ‘7768’
    Try 'chmod --help' for more information.
    chmod: invalid mode: ‘7769’
    Try 'chmod --help' for more information.
    use command cat results to see permissions for file_test.
    [mythcat@desk my_bash_scripts]$ ls
    all_permissions.sh file_test out results
    The out file show all permissions for files:
    [mythcat@desk my_bash_scripts]$ cat out
    total 2052
    -rwxrwxr-x. 1 331 Nov 10 18:22 all_permissions.sh
    -rwsrwsr-T. 1 0 Nov 10 18:23 file_test
    -rw-rw-r--. 1 1153701 Nov 10 18:23 r
    total 2052
    -rwxrwxr-x. 1 331 Nov 10 18:22 all_permissions.sh
    -rwsrwsr-t. 1 0 Nov 10 18:23 file_test
    -rw-rw-r--. 1 1153853 Nov 10 18:23 r
    total 2052
    -rwxrwxr-x. 1 331 Nov 10 18:22 all_permissions.sh
    -rwsrwsrwT. 1 0 Nov 10 18:23 file_test
    -rw-rw-r--. 1 1154005 Nov 10 18:23 r
    total 2052
    -rwxrwxr-x. 1 331 Nov 10 18:22 all_permissions.sh
    -rwsrwsrwt. 1 0 Nov 10 18:23 file_test
    -rw-rw-r--. 1 1154157 Nov 10 18:23 r
    The results file show the permissions:
    [mythcat@desk my_bash_scripts]$ cat results 
    -rwsrwSrwT. 1 0 Nov 10 18:30 file_test
    -rwsrwSrwt. 1 0 Nov 10 18:30 file_test
    -rwsrwSrwt. 1 0 Nov 10 18:30 file_test
    -rwsrwSrwt. 1 0 Nov 10 18:30 file_test
    -rwsrws--T. 1 0 Nov 10 18:30 file_test
    -rwsrws--t. 1 0 Nov 10 18:30 file_test
    -rwsrws-wT. 1 0 Nov 10 18:30 file_test
    -rwsrws-wt. 1 0 Nov 10 18:30 file_test
    -rwsrwsr-T. 1 0 Nov 10 18:30 file_test
    -rwsrwsr-t. 1 0 Nov 10 18:30 file_test
    -rwsrwsrwT. 1 0 Nov 10 18:30 file_test
    -rwsrwsrwt. 1 0 Nov 10 18:30 file_test

    Fedora 31 : The new Fedora 31 Linux distro.

    Posted by mythcat on November 09, 2019 12:10 AM
    I tested today the new Fedora 31.
    This new Fedora comes with many features.
    One is the Toolbox tool that offers a familiar RPM-based environment for developing and debugging software that runs fully unprivileged using Podman.
    Fedora 31 significantly improves the speed of update installation, as packages are now compressed with zstd instead of xz.
    This commands let you to upgrading Fedora 30 to Fedora 31.
    [root@desk mythcat]# dnf upgrade --refresh
    [root@desk mythcat]# dnf install dnf-plugin-system-upgrade
    [root@desk mythcat]# dnf remove xorg-x11-drv-nvidia-340xx-libs-1:340.107-4.fc30.x86_64
    [root@desk mythcat]# dnf system-upgrade download --releasever=31
    [root@desk mythcat]# dnf system-upgrade reboot
    You can see I remove the xorg driver because system-upgrade don't let me to update.

    FPgM report: 2019-45

    Posted by Fedora Community Blog on November 08, 2019 09:26 PM
    Fedora Program Manager weekly report on Fedora Project development and progress

    Here’s your report of what has happened in Fedora Program Management this week. Fedora 29 will reach end of life on 26 November. Elections nominations are open through 13 November.



    Open TestConBeijing, CN30–31 Mar 2020closes 10 Nov
    CentOS DojoBrussels, BE31 Jan 2020closes 18 Nov
    FOSDEM Distro DevroomBrussels, BE2 Feb 2020closes 1 Dec
    Indy Cloud ConfIndianapolis, IN, US26–27 Mar 2020closes 21 Dec

    Help wanted

    Upcoming meetings


    Fedora 31


    • 13 November — Elections nomination deadline
    • 26 November — Fedora 29 EOL

    Fedora 32


    Submitted to FESCo
    Rejected by FESCo

    CPE update

    Community Application Handover & Retirement Updates

    • Elections — Blocking issue was fixed (https://pagure.io/fedora-infrastructure/issue/8253)
    • Fedocal — jlanda hitting permission error in communishift https://pagure.io/fedora-infrastructure/issue/8274
    • Nuancier — Benson Muite is now working on OIDC authentication. We are emailing him to check the progress and if he needs any help
    • fpaste — Updated fpaste CLI appears to have landed in EPEL. Writing a commblog about it. Sunset date: 1 December 2019.
    • Badges — GDPR query under investigation

    The post FPgM report: 2019-45 appeared first on Fedora Community Blog.

    oqubeslogging, a PoC for centralized logging in Qubes OS

    Posted by Kushal Das on November 08, 2019 11:38 AM

    oqubeslogging is a proof of concept project for Qubes OS. This includes a qrexec service, which allows one AppVM (we will call it logging VM for the rest of the blog post) to have all the logs from different select VMs. This enables central logging among QubesOS land.

    The second part is a Python logging handler, which if configured correctly, will allow to pass the logging lines to the logging VM

    import logging
    from oqubeslogging import OQubesLog
    def main():
        handler = OQubesLog("workvm", "loggingvm")
        logging.basicConfig(level=logging.DEBUG, handlers=[handler])
        logger = logging.getLogger("example")
        logger.info("kushal says it works")
    if __name__ == "__main__":

    Third, is another example code, which if run as root user in any VM, will collect all logs from journald and pass them to the logging VM.

    Why is this useful?

    The same reason we use central logging in every place. This will enable us to check only one VM to find the correct log. QubesOS is designed for single user in mind, and instead many random AppVM, we will be able to read and parse logs in that one special logging VM.

    Verified emoji on Mastodon

    Posted by Kushal Das on November 08, 2019 10:43 AM

    Yesterday, just for fun, I added an emoji (as a local emoji) to our mastodon instance, kind of look like a verification icon. Only to show the power of federation and Free Software to the new users of Mastodon. Many other users started using the same. But, most newbies to Mastodon got confused with the same

    my profile screenshot

    my profile edit screenshot

    If you see the above screenshot, I just added :verified: after my name in my profile, and that shows the icon. That is not any formal verification. The https://msdtn.social instance also has a similar emoji, but the big https://mastodon.social does not have the same.

    Then how to verify someone on Mastodon?

    The best way is via their website or blog. If you click to edit your profile, you will find the option to add a few profile metadata, in those sites, you can verify that you own or have edit access of those sites.

    my profile link verify

    Thus, my blog comes with a green tick on my profile image. Here is to the link verification documentation from the website.

    Feel free to follow me on Mastodon.

    Managing software and services with Cockpit

    Posted by Fedora Magazine on November 08, 2019 08:00 AM

    The Cockpit series continues to focus on some of the tools users and administrators can use to perform everyday tasks within the web user-interface. So far we’ve covered introducing the user-interface, storage and network management, and user accounts. Hence, this article will highlight how Cockpit handles software and services.

    The menu options for Applications and Software Updates are available through Cockpit’s PackageKit feature. To install it from the command-line, run:

     sudo dnf install cockpit-packagekit

    For Fedora Silverblue, Fedora CoreOS, and other ostree-based operating systems, install the cockpit-ostree package and reboot the system:

    sudo rpm-ostree install cockpit-ostree; sudo systemctl reboot

    Software updates

    On the main screen, Cockpit notifies the user whether the system is updated, or if any updates are available. Click the Updates Available link on the main screen, or Software Updates in the menu options, to open the updates page.

    RPM-based updates

    The top of the screen displays general information such as the number of updates and the number of security-only updates. It also shows when the system was last checked for updates, and a button to perform the check. Likewise, this button is equivalent to the command sudo dnf check-update.

    Below is the Available Updates section, which lists the packages requiring updates. Furthermore, each package displays the name, version, and best of all, the severity of the update. Clicking a package in the list provides additional information such as the CVE, the Bugzilla ID, and a brief description of the update. For details about the CVE and related bugs, click their respective links.

    Also, one of the best features about Software Updates is the option to only install security updates. Distinguishing which updates to perform makes it simple for those who may not need, or want, the latest and greatest software installed. Of course, one can always use Red Hat Enterprise Linux or CentOS for machines requiring long-term support.

    The example below demonstrates how Cockpit applies RPM-based updates.

    <figure class="wp-block-image">Running system updates with RPM-based operating systems in Cockpit.</figure>

    OSTree-based updates

    The popular article What is Silverblue states:

    OSTree is used by rpm-ostree, a hybrid package/image based system… It atomically replicates a base OS and allows the user to “layer” the traditional RPM on top of the base OS if needed.

    Because of this setup, Cockpit uses a snapshot-like layout for these operating systems. As seen in the demo below, the top of the screen displays the repository (fedora), the base OS image, and a button to Check for Updates.

    Clicking the repository name (fedora in the demo below) opens the Change Repository screen. From here one can Add New Repository, or click the pencil icon to edit an existing repository. Editing provides the option to delete the repository, or Add Another Key. To add a new repository, enter the name and URL. Also, select whether or not to Use trusted GPG key.

    There are three categories that provide details of its respective image: Tree, Packages, and Signature. Tree displays basic information such as the operating system, version of the image, how long ago it was released, and the origin of the image. Packages displays a list of installed packages within that image. Signature verifies the integrity of the image such as the author, date, RSA key ID, and status.

    The current, or running, image displays a green check-mark beside it. If something happens, or an update causes an issue, click the Roll Back and Reboot button. This restores the system to a previous image.

    <figure class="wp-block-image">Running system updates with OSTree-based operating systems in Cockpit.</figure>


    The Applications screen displays a list of add-ons available for Cockpit. This makes it easy to find and install the plugins required by the user. At the time of this article, some of the options include the 389 Directory Service, Fleet Commander, and Subscription Manager. The demo below shows a complete list of available Cockpit add-ons.

    Also, each item displays the name, a brief description, and a button to install, or remove, the add-on. Furthermore, clicking the item displays more information (if available). To refresh the list, click the icon at the top-right corner.

    <figure class="wp-block-image">Managing Cockpit application add-ons and features</figure>

    Subscription Management

    Subscription managers allow admins to attach subscriptions to the machine. Even more, subscriptions give admins control over user access to content and packages. One example of this is the famous Red Hat subscription model. This feature works in relation to the subscription-manager command

    The Subscriptions add-on can be installed via Cockpit’s Applications menu option. It can also be installed from the command-line with:

    sudo dnf install cockpit-subscriptions

    To begin, click Subscriptions in the main menu. If the machine is currently unregistered, it opens the Register System screen. Next, select the URL. You can choose Default, which uses Red Hat’s subscription server, or enter a Custom URL. Enter the Login, Password, Activation Key, and Organization ID. Finally, to complete the process, click the Register button.

    The main page for Subscriptions show if the machine is registered, the System Purpose, and a list of installed products.

    <figure class="wp-block-image">Managing subscriptions in Cockpit</figure>


    To start, click the Services menu option. Because Cockpit uses systemd, we get the options to view System Services, Targets, Sockets, Timers, and Paths. Cockpit also provides an intuitive interface to help users search and find the service they want to configure. Services can also be filtered by it’s state: All, Enabled, Disabled, or Static. Below this is the list of services. Each row displays the service name, description, state, and automatic startup behavior.

    For example, let’s take bluetooth.service. Typing bluetooth in the search bar automatically displays the service. Now, select the service to view the details of that service. The page displays the status and path of the service file. It also displays information in the service file such as the requirements and conflicts. Finally, at the bottom of the page, are the logs pertaining to that service.

    Also, users can quickly start and stop the service by toggling the switch beside the service name. The three-dots to the right of that switch expands those options to Enable, Disable, Mask/Unmask the service

    To learn more about systemd, check out the series in the Fedora Magazine starting with What is an init system?

    <figure class="wp-block-image">Managing services in Cockpit</figure>

    In the next article we’ll explore the security features available in Cockpit.

    Deleting Trunks in OpenStack before Deleting Ports

    Posted by Adam Young on November 07, 2019 07:27 PM

    Cloud is easy. It is networking that is hard.

    Red Hat supports installing OpenShift on OpenStack. As a Cloud SA, I need to be able to demonstrate this, and make it work for customers. As I was playing around with it, I found I could not tear down clusters due to a dependency issue with ports.

    When building and tearing down network structures with Ansible, I had learned the hard way that there were dependencies. Routers came down before subnets, and so one. But the latest round had me scratching my head. I could not get ports to delete, and the error message was not a help.

    I was able to figure out that the ports linked to security groups. In fact, I could unset almost all of the dependencies using the port set command line. For example:

    openstack port set openshift-q5nqj-master-port-1  --no-security-group --no-allowed-address --no-tag --no-fixed-ip

    However, I still could not delete the ports. I did notice that there was a trunk_+details section at the bottom of the port show output:

    trunk_details         | {'trunk_id': 'dd1609af-4a90-4a9e-9ea4-5f89c63fb9ce', 'sub_ports': []} 

    But there is no way to “unset” that. It turns out I had it backwards. You need to delete the port first. A message from Kristi Nikolla:

    the port is set as the parent for a “trunk” so you need to delete the trunk firs

    Kristi In IRC
    <pre lang="bash">curl -H "x-auth-token: $TOKEN" https://kaizen.massopen.cloud:13696/v2.0/trunks/</pre>

    It turns out that you can do this with the CLI…at least I could.

    $ openstack network trunk show 01a19e41-49c6-467c-a726-404ffedccfbb
    admin_state_up UP
    created_at 2019-11-04T02:58:08Z
    id 01a19e41-49c6-467c-a726-404ffedccfbb
    name openshift-zq7wj-master-trunk-1
    port_id 6f4d1ecc-934b-4d29-9fdd-077ffd48b7d8
    project_id b9f1401936314975974153d78b78b933
    revision_number 3
    status DOWN
    tags [‘openshiftClusterID=openshift-zq7wj’]
    tenant_id b9f1401936314975974153d78b78b933
    updated_at 2019-11-04T03:09:49Z

    Here is the script I used to delete them. Notice that the status was DOWN for all of the ports I wanted gone.

    for PORT in $( openstack port list | awk '/DOWN/ {print $2}' ); do TRUNK_ID=$( openstack port show $PORT -f json | jq  -r '.trunk_details | .trunk_id ') ; echo port  $PORT has trunk $TRUNK_ID;  openstack network trunk delete $TRUNK_ID ; done

    Kristi had used the curl command because he did not have the network trunk option in his CLI. Turns out he needed to install python-neutronclient first.

    Bodhi 5.0.0 released

    Posted by Bodhi on November 07, 2019 03:30 PM

    This is a major release with many backwards incompatible changes.

    Backwards incompatible changes

    • Celery is introduced to handle the long-running tasks (#2851).
    • Fedmenu was removed from the UI (#2194).
    • Remove deprecated search_packages path (#3411).
    • Remove critpath_karma from the UI (#2194).
    • Remove unused and incorrect server.bugs.Bugzilla.get_url() function.
    • Print errors to stderr in command line tools.

    Dependency changes

    • Celery is a new required dependency (#2851).

    Server upgrade instructions

    This release contains database migrations. To apply them, run:

    $ sudo -u apache /usr/bin/alembic -c /etc/bodhi/alembic.ini upgrade head


    • Update fedora-bootstrap to latest 1.5.0.
    • Add ctype to the ComposeComplete (#3297).
    • Add knowledge of branch freezes to the Release model (#1038, #1563).
    • API: Create/edit updates from Koji tags (#3009).
    • Add javascript confirmation for unpushing updates.
    • Use versioned dir name for static files.
    • Improve the performance of validate_build_uniqueness.
    • Add option to create/edit updates side tags to CLI (#2325).
    • Overhaul the new update form.
    • Mark updates not composed by bodhi as pushed when stable.
    • Allow multiple status params for update list views (#3429).
    • Send a message when an update is ready to be tested (#3428).
    • Create additional side tags on multi build tag (#3473).
    • Create comment when CI tests starts, but don't send an email (#3403).
    • Add support for creating sidetag updates to webui.
    • Create a Dashboard for logged in users.
    • Clean up Javascript, CSS and fonts.
    • Add a new config item, automatic_updates_blacklist, which is a list of
      users to not process auto updates from.
    • Document what the update states mean for rawhide.
    • Add a filtering/searching interface to the updates query view.
    • Add the list of packages in the update description to rss feed.
    • Transform markdown code to html for better readability of the rss feed.
    • Add frozen release state to bodhi releases list.
    • Add API call to retrigger update tests.
    • Tidy up the UI.
    • Add --user and --password to all actions of the bodhi CLI supporting
      --openid-api (for example: waive and trigger) (#3550).
    • Update ChartJS package and redesign Release page (#3671).
    • Automatically created updates (e.g. Fedora Rawhide single package updates)
      now include a changelog entry in the update notes. (#3192).
    • Move multi build update that failed to merge in rawhide to pending.

    Bug fixes

    • Handle connection problems when talking to Wiki (#3361).
    • Make Bodhi able to clear models.Release._all_releases cache (#2177).
    • Query Greenwave in batches to avoid timeouts.
    • Template, js and style fixes.
    • Allow to configure a release without an override tag (#3447).
    • Determine a release for sidetag updates (#3480).
    • Change update status to testing if every build is signed (#3475).
    • Delete additional tags once an side tag update was pushed to stable (#3476).
    • Turn off autokarma and autotime for automatic updates (#3424).
    • Make display_name optional in template (#3470).
    • Sign new builds to <sidetag>-pending-signing (#3485).
    • Allow only 1 update per side tag (#3484).
    • Disable comments on updates when update is pushed and stable (#2050).
    • Unify rawhide simple build update with multi build update (#3513).
    • Prevent crash when compose contains update without builds (#3471).
    • Added build.update.pushed = True for the signed consumer so that it can be
      unpushed. (#3625).

    Development improvements

    • Rename bteststyle to blint.
    • Update developer documentation.
    • Run mypy directly in Vagrant (#3335).
    • More type annotations.
    • Add WaiverDB and Greenwave to development environment (#3011).
    • Provide authentication in the integration testing environment.
    • Make it easier to develop using VS Code.
    • Add option to vagrant provisioning to use stg infra.
    • Introduction of Towncrier to
      manage the release notes (#3562).

    Other changes

    • List items in RSS feed starting from the most recent (#3621).


    The following developers contributed to Bodhi 5.0.0:

    • Anatoli Babenia
    • Aurélien Bompard
    • Randy Barlow
    • Clement Verna
    • David Fan
    • dimitraz
    • Lukas Holecek
    • Mattia Verga
    • Michal Konečný
    • Nils Philippsen
    • Ondrej Nosek
    • Pierre-Yves Chibon
    • Rick Elrod
    • Ryan Lerch
    • Robert Scheck
    • Rob Shelly
    • Sam Robbins
    • Stephen Coady
    • siddharthvipul
    • subhamkrai
    • Sebastian Wojciechowski

    PHP version 7.2.25RC1 and 7.3.12RC1

    Posted by Remi Collet on November 07, 2019 03:19 PM

    Release Candidate versions are available in testing repository for Fedora and Enterprise Linux (RHEL / CentOS) to allow more people to test them. They are available as Software Collections, for a parallel installation, perfect solution for such tests, and also as base packages.

    RPM of PHP version 7.3.12RC1 are available as SCL in remi-test repository and as base packages in the remi-test repository for Fedora 30-31 or remi-php73-test repository for Fedora 29 and Enterprise Linux.

    RPM of PHP version 7.2.25RC1 are available as SCL in remi-test repository and as base packages in the remi-test repository for Fedora 29 or remi-php72-test repository for Enterprise Linux.


    emblem-notice-24.pngPHP version 7.1 is now in security mode only, so no more RC will be released.

    emblem-notice-24.pngInstallation : read the Repository configuration and choose your version.

    Parallel installation of version 7.3 as Software Collection:

    yum --enablerepo=remi-test install php73

    Parallel installation of version 7.2 as Software Collection:

    yum --enablerepo=remi-test install php72

    Update of system version 7.3:

    yum --enablerepo=remi-php73,remi-php73-test update php\*

    or, the modular way (Fedora and RHEL 8):

    dnf module reset php
    dnf module enable php:remi-7.3
    dnf --enablerepo=remi-modular-test update php\*

    Update of system version 7.2:

    yum --enablerepo=remi-php72,remi-php72-test update php\*

    or, the modular way (Fedora and RHEL 8):

    dnf module reset php
    dnf module enable php:remi-7.2
    dnf --enablerepo=remi-modular-test update php\*

    Notice: version 7.4.0RC5 in Fedora rawhide and version 7.3.12RC1 in updates-testing for Fedora 31, for QA.

    emblem-notice-24.pngEL-8 packages are built using RHEL-8.0

    emblem-notice-24.pngEL-7 packages are built using RHEL-7.0

    emblem-notice-24.pngPackages of 7.4.0RC5 are also available

    emblem-notice-24.pngRC version is usually the same as the final version (no change accepted after RC, exception for security fix).

    Software Collections (php72, php73)

    Base packages (php)

    Tuning your bash or zsh shell on Fedora Workstation and Silverblue

    Posted by Fedora Magazine on November 07, 2019 02:45 PM

    This article shows you how to set up some powerful tools in your command line interpreter (CLI) shell on Fedora. If you use bash (the default) or zsh, Fedora lets you easily setup these tools.


    Some installed packages are required. On Workstation, run the following command:

    sudo dnf install git wget curl ruby ruby-devel zsh util-linux-user redhat-rpm-config gcc gcc-c++ make

    On Silverblue run:

    sudo rpm-ostree install git wget curl ruby ruby-devel zsh util-linux-user redhat-rpm-config gcc gcc-c++ make

    Note: On Silverblue you need to restart before proceeding.


    You can give your terminal a new look by installing new fonts. Why not fonts that display characters and icons together?


    Open a new terminal and type the following commands:

    git clone --depth=1 https://github.com/ryanoasis/nerd-fonts ~/.nerd-fonts
    cd .nerd-fonts 
    sudo ./install.sh


    On Workstation, install using the following command:

    sudo dnf install fontawesome-fonts

    On Silverblue, type:

    sudo rpm-ostree install fontawesome-fonts


    Powerline is a statusline plugin for vim, and provides statuslines and prompts for several other applications, including bash, zsh, tmus, i3, Awesome, IPython and Qtile. You can find more information about powerline on the official documentation site.


    To install powerline utility on Fedora Workstation, open a new terminal and run:

    sudo dnf install powerline vim-powerline tmux-powerline powerline-fonts

    On Silverblue, the command changes to:

    sudo rpm-ostree install powerline vim-powerline tmux-powerline powerline-fonts

    Note: On Silverblue, before proceeding you need restart.

    Activating powerline

    To make the powerline active by default, place the code below at the end of your ~/.bashrc file

    if [ -f `which powerline-daemon` ]; then
      powerline-daemon -q
      . /usr/share/powerline/bash/powerline.sh

    Finally, close the terminal and open a new one. It will look like this:

    <figure class="wp-block-image is-resized"></figure>


    Oh-My-Zsh is a framework for managing your Zsh configuration. It comes bundled with helpful functions, plugins, and themes. To learn how set Zsh as your default shell this article.


    Type this in the terminal:

    sh -c "$(curl -fsSL https://raw.github.com/robbyrussell/oh-my-zsh/master/tools/install.sh)"

    Alternatively, you can type this:

    sh -c "$(wget https://raw.github.com/robbyrussell/oh-my-zsh/master/tools/install.sh -O -)"

    At the end, you see the terminal like this:

    <figure class="wp-block-image"></figure>

    Congratulations, Oh-my-zsh is installed.


    Once installed, you can select your theme. I prefer to use the Powerlevel10k. One advantage is that it is 100 times faster than powerlevel9k theme. To install run this line:

    git clone https://github.com/romkatv/powerlevel10k.git ~/.oh-my-zsh/themes/powerlevel10k

    And set ZSH_THEME in your ~/.zshrc file


    Close the terminal. When you open the terminal again, the Powerlevel10k configuration wizard will ask you a few questions to configure your prompt properly.

    <figure class="wp-block-image"></figure>

    After finish Powerline10k configuration wizard, your prompt will look like this:

    <figure class="wp-block-image"></figure>

    If you don’t like it. You can run the powerline10k wizard any time with the command p10k configure.

    Enable plug-ins

    Plug-ins are stored in .oh-my-zsh/plugins folder. You can visit this site for more information. To activate a plug-in, you need edit your ~/.zshrc file. Install plug-ins means that you are going create a series of aliases or shortcuts that execute a specific function.

    For example, to enable the firewalld and git plugins, first edit ~/.zshrc:

    plugins=(firewalld git)

    Note: use a blank space to separate the plug-ins names list.

    Then reload the configuration

    source ~/.zshrc 

    To see the created aliases, use the command:

    alias | grep firewall
    <figure class="wp-block-image"></figure>

    Additional configuration

    I suggest the install syntax-highlighting and syntax-autosuggestions plug-ins.

    git clone https://github.com/zsh-users/zsh-syntax-highlighting.git ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-syntax-highlighting
    git clone https://github.com/zsh-users/zsh-autosuggestions ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-autosuggestions

    Add them to your plug-ins list in your file ~/.zshrc

    plugins=( [plugins...] zsh-syntax-highlighting zsh-autosuggestions)

    Reload the configuration

    source ~/.zshrc 

    See the results:

    <figure class="wp-block-image"></figure>

    Colored folders and icons

    Colorls is a Ruby gem that beautifies the terminal’s ls command, with colors and font-awesome icons. You can visit the official site for more information.

    Because it’s a ruby gem, just follow this simple step:

    sudo gem install colorls

    To keep up to date, just do:

    sudo gem update colorls

    To prevent type colorls everytime you can make aliases in your ~/.bashrc or ~/.zshrc.

    alias ll='colorls -lA --sd --gs --group-directories-first'
    alias ls='colorls --group-directories-first'

    Also, you can enable tab completion for colorls flags, just entering following line at end of your shell configuration:

    source $(dirname $(gem which colorls))/tab_complete.sh

    Reload it and see what it happens:

    <figure class="wp-block-image"></figure> <figure class="wp-block-image"></figure>

    Accommodating Flock in the release schedule

    Posted by Fedora Community Blog on November 07, 2019 07:21 AM
    Calendar showing days of Flock - Tue Aug 29, Wed Aug 30, Thu Aug 31, Fri Sep 1

    Jiří Konečný posted a request on the devel list a few weeks ago—he wanted to require a successful compose before the release is branched from Rawhide. As often happens, it’s not as simple as it seems on the surface, and the discussion eventually came around to not branching right after Flock.

    This, too, isn’t as simple as it might seem. Changing one milestone in the schedule has impacts on the remaining milestones. We can make changes, of course, but we want to make sure we’re aware of the potential side effects. After discussing this with Mohan Boddu of the release engineering team, I have a few possible alternatives.


    Before I present the alternatives, I want to cover a few of the considerations that went into this. The first is that Flock itself is not a predictable part of the schedule. Although it’s generally in early August, it bounces around a bit. This means it’s hard to predict ahead of time what the impact will be on the schedule.

    Schedule alternatives

    Option 0: Do nothing

    Option 0 is the baseline. It keeps the schedule the way it is. If the release engineers are jetlagged after Flock, they still have work to do. It’s worth noting here that in alternate years, the release engineering team won’t be traveling as far, so option 0 may be fine half the time.

    Option 1: Delay branching

    Option 1 delays the branching by a week, while keeping all other milestones in place. This shortens the time between branching and Bodhi activation/Beta freeze from two weeks to one. This is the simplest change from a schedule standpoint, but it only gives maintainers a week to test things in branched before the freeze kicks in.

    Option 2: Delay branching, shorten beta freeze

    Option 2 also delays branching by a week, but keeps the branch-to-Bodhi-activation window at two weeks. Thus the Beta freeze is shortened from three weeks to two. This gives maintainers the two week window to finish changes in branched, but shortens the amount of time available for testing. Mohan attributes the improved on-time delivery in the last few releases to the longer Beta freeze. Shortening this may result in unplanned changes to the schedule.

    Option 3: Delay branching, delay beta release

    Option 3 continues the pattern of delaying the branching by a week. Instead of shortening the Beta freeze, it pushes the freeze back a week, too. This shortens the time from Beta to Final by a week—from five weeks to four. It also means that the time from the Beta release to the beginning of Final freeze is two weeks if we release on the preferred target, one week if we release on Beta target #1. If the Beta release slips beyond target date #1, we immediately go into Final freeze or we delay the Final release.

    Option 4: Delay everything

    Option 4 adds a week to everything from the branch point and beyond. I include it here for completeness, although I strongly oppose it. The first reason I oppose it is marketing-related. With this option, the Final target date #1 milestone may end up in November. While it is still a week after the preferred target date, moving from October to November has a perceived difference. The second reason is that it pushes the elections further into December, so additional slips could mean the voting period ends up colliding with the end-of-year holidays.

    Options 0-4 summarized

    Here’s what the Fedora 31 schedule would look like under the various options.

    MilestoneOption 0Option 1 Option 2Option 3Option 4
    Flock08–11 Aug08–11 Aug08–11 Aug08–11 Aug08–11 Aug
    Change completion deadline (testable)13 Aug20 Aug20 Aug20 Aug20 Aug
    Branch13 Aug20 Aug20 Aug20 Aug20 Aug
    Bodhi activation27 Aug27 Aug3 Sep3 Sep3 Sep
    Change 100% code complete deadline27 Aug27 Aug3 Sep3 Sep3 Sep
    Beta Freeze starts27 Aug27 Aug3 Sep3 Sep3 Sep
    Beta preferred target date17 Sep17 Sep17 Sep24 Sep24 Sep
    Final freeze starts8 Oct8 Oct8 Oct8 Oct15 Oct
    Final preferred target22 Oct22 Oct22 Oct22 Oct29 Oct
    Final target #129 Oct29 Oct29 Oct29 Oct5 Nov

    Non-schedule alternatives

    Move Flock

    Okay, this is a schedule alternative, but not a Schedule™ alternative. One option would be to say the week before the branch is off-limits for Flock. Of course, this could mean holding Flock later in the schedule where it might negatively impact feature finalization or testing instead of branching and composing. It might also make it more difficult to find a venue at an appropriate price. But it is a choice.

    Make composes better

    I know the release engineering team is working on this independently of whatever schedule changes we may make. In an ideal world, composes would always work. As Kevin Fenzi noted, Rawhide gating should help catch many of the issues.

    Freeze right after branching

    Several people suggested a variation of doing a brief freeze after branching until a successful compose completes. This could be one day or several, depending, but the freeze would end as soon as the compose is available.

    My recommendation

    I’m inclined to go with option 0, plus a brief freeze after branch. The Flock dates are variable and so it’s difficult to pre-plan around them. With Rawhide gating and a freeze in place, we should be less likely to see a repeat of this. In addition, while this is a regular problem, both Jiŕi and Kevin said this was an abnormally-long version of it. I’m hesitant to make a structural change in the schedule to accommodate an anomaly that will be mitigated by other means.

    Editor’s note: comments are disabled on this post. Please use the devel list thread for discussion.

    The post Accommodating Flock in the release schedule appeared first on Fedora Community Blog.

    HP Envy x360 15 2500u - One year later

    Posted by Luya Tshimbalanga on November 07, 2019 03:38 AM
    A year passed since owning HP Envy x360 15 2500u now running mainly on Fedora Design Suite now on its 31 release. The Design Suite is based on Fedora Workstation running on Gnome Wayland by default.

    The touchscreen works as intended and feel more responsive. Tweaking Firefox 70.0 However, due to a bug related to the GTK toolkit, using a stylus can cause crash on some applications. The fix is available and will be a matter of the time of an update . Sometimes, the touchscreen failed to work due to an issue related to ACPI only HP can address. The current workaround is to reboot the laptop.

    The LED Mute button works as intended with the help of a veteran SuSE developer. The quality of audio is adequate with seemly minimal loss  for a laptop once over-amplification is applied via Tweak application.

    At the time of writing, the majority of Ryzen APU powered laptop has yet to get the gyroscope function needed to auto-rotate the screen and other features like disabling keyboard on tablet mode.  AMD is working on a driver currently under review and the time of availability is to be announced soon.

     The facial recognition is sketchy with only a tool named howdy, a  Windows Hello™ style facial authentication for Linux,  configurable via text editor or terminal. At this time, no automated process to detect camera is available yet. The system is functional and need more work to get properly integrated.

    As a laptop, the HP Envy x360 is excellent  choice for open source developers and users. For artists, graphic designers, the tablet mode is incomplete with the missing orientation sensor driver. Once that kink get ironed out, future blog will come.

    All systems go

    Posted by Fedora Infrastructure Status on November 06, 2019 11:41 PM
    New status good: Everything seems to be working. for services: Ipsilon, Badges, Blockerbugs, Package Updates Manager, Fedora Infrastructure Cloud, COPR Build System, Documentation website, Fedora elections, Account System, Fedora Messaging Bus, Fedora Calendar, Fedora pastebin service, The Koji Buildsystem, Koschei Continuous Integration, Kerberos, Mailing Lists, Mirror List, Mirror Manager, Fedora Packages App, Pagure, Fedora People, Package Database, Package maintainers git repositories, Fedora Container Registry, ABRT Server, Tagger, Fedora websites, Fedora Wiki, Zodbot IRC bot

    Final F30-20191106 updated isos Released

    Posted by Ben Williams on November 06, 2019 11:08 PM

    The Fedora Respins SIG is pleased to announce the final  release of Updated iso for F30. F30-20191106 Live ISOs, carrying the 5.3.8-200 kernel.

    This set of updated isos will save considerable amounts  of updates after install.  ((for new installs.)(New installs of Workstation have 1.2 GB of updates)).

    A huge thank you goes out to irc nicks dowdle,  Southern-Gentleman for testing these iso.

    We would also like to thank Fedora- QA  for running the following Tests on our ISOs.:



    As always our isos can be found at  http://tinyurl.com/Live-respins .  

    F31-20191105 updated iso released

    Posted by Ben Williams on November 06, 2019 11:03 PM

    The Fedora Respins SIG is pleased to announce the latest release of Updated F31-20191105 Live ISOs, carrying the 5.3.8-300 kernel.

    This set of updated isos will save considerable amounts  of updates after install.  ((for new installs.)(New installs of Workstation have 500MB of updates)).

    A huge thank you goes out to irc nicks dowdle,  Southern-Gentleman for testing these iso.

    We would also like to thank Fedora- QA  for running the following Tests on our ISOs.:



    As always our isos can be found at  http://tinyurl.com/Live-respins .  

    There are scheduled downtimes in progress

    Posted by Fedora Infrastructure Status on November 06, 2019 09:02 PM
    New status scheduled: Fedora is performing scheduled maintenance across its fleet. for services: Ipsilon, Badges, Blockerbugs, Package Updates Manager, Fedora Infrastructure Cloud, COPR Build System, Documentation website, Fedora elections, Account System, Fedora Messaging Bus, Fedora Calendar, Fedora pastebin service, The Koji Buildsystem, Koschei Continuous Integration, Kerberos, Mailing Lists, Mirror List, Mirror Manager, Fedora Packages App, Pagure, Fedora People, Package Database, Package maintainers git repositories, Fedora Container Registry, ABRT Server, Tagger, Fedora websites, Fedora Wiki, Zodbot IRC bot

    Fedora 30 : GIMP 2.10.14 with flatpak.

    Posted by mythcat on November 06, 2019 08:07 PM
    Flatpak is a software utility for software deployment and package management for Linux. It is advertised as offering a sandbox environment in which users can run application software in isolation from the rest of the system. see Wikipedia .
    Flatpak builds available in i386, x86-64, ARM and AArch64.
    [root@desk mythcat]# dnf install flatpak.x86_64 
    Last metadata expiration check: 0:27:27 ago on Fri 01 Nov 2019 11:27:47 PM EET.
    Dependencies resolved.

    The install and run of last GIMP software is easy, see commands:
    [mythcat@desk ~]$ flatpak install https://flathub.org/repo/appstream/org.gimp.GIMP.flatpakref

    Note that the directories


    are not in the search path set by the XDG_DATA_DIRS environment variable, so applications installed by
    Flatpak may not appear on your desktop until the session is restarted.

    Required runtime for org.gimp.GIMP/x86_64/stable (runtime/org.gnome.Platform/x86_64/3.32) found in remote
    Do you want to install it? [Y/n]: Y

    org.gimp.GIMP permissions:
    ipc network x11 file access [1]
    dbus access [2] tags [3]

    [1] /tmp, host, xdg-config/GIMP, xdg-config/gtk-3.0
    [2] org.freedesktop.FileManager1, org.gtk.vfs, org.gtk.vfs.*
    [3] stable
    ID Arch Branch Remote Download
    ID Arch Branch Remote Download
    1. [✓] org.gnome.Platform x86_64 3.32 flathub 360.0 MB / 374.0 MB
    2. [✓] org.gnome.Platform.Locale x86_64 3.32 flathub 17.4 kB / 320.0 MB
    3. [✓] org.freedesktop.Platform.VAAPI.Intel x86_64 18.08 flathub 1.8 MB / 1.8 MB
    4. [✓] org.freedesktop.Platform.html5-codecs x86_64 18.08 flathub 3.2 MB / 3.3 MB
    5. [✓] org.gimp.GIMP x86_64 stable flathub 106.5 MB / 108.9 MB

    Installation complete.
    [mythcat@desk ~]$ flatpak update

    Note that the directories


    are not in the search path set by the XDG_DATA_DIRS environment variable, so
    applications installed by Flatpak may not appear on your desktop until the session is restarted.

    Looking for updates…
    Nothing to do.
    [mythcat@desk ~]$ flatpak run org.gimp.GIMP//stable

    Note that the directories


    are not in the search path set by the XDG_DATA_DIRS environment variable, so
    applications installed by Flatpak may not appear on your desktop until the session is restarted.

    GIMP-Error: Skipping '/home/mythcat/.var/app/org.gimp.GIMP/config/GIMP/2.10/pluginrc
    wrong GIMP protocol version.

    Upgrading syslog-ng PE from version 6 to 7

    Posted by Peter Czanik on November 06, 2019 12:35 PM

    Learn the major steps necessary to upgrade your system from syslog-ng Premium Edition version 6 to 7. As you will see, it is no more difficult than any other major software version upgrade, and after the upgrade you can start using all the new and useful features that are available in version 7.

    Version 7 of syslog-ng Premium Edition (PE) brought quite a lot of changes compared version 6. The main reason for this was that syslog-ng PE source code was synchronized with syslog-ng Open Source Edition (OSE), and initially many of the PE specific features were unavailable in version 7. It also meant, that direct upgrade between version 6 and 7 was not possible.

    There are many new features in syslog-ng PE version 7 and most of the old features are available again. Due to this people started to upgrade their old installations and easy upgrade between the two versions became an important topic. Obviously, as with any major software upgrades, there are some limitations, but you do not need start an installation from scratch if you want to migrate from syslog-ng PE version 6 to 7.

    Making upgrades easy needed two major changes in syslog-ng PE 7. One is providing backwards compatibility to the old way of configuring features together with warning messages related to changes. The other is handling the persists file – a file containing internal syslog-ng data, like the position until syslog-ng read a source – from the old syslog-ng version properly. Starting with syslog-ng PE 7.0.17 both are handled properly.

    Before you begin

    Before you start downloading anything from the One Identity website, make sure that you read the release notes. There are two major group of changes which might affect your migration process:

    • There is a change in the supported platforms. Unlike PE 6, which also supports Windows and a number of UNIX variants, PE 7 only supports 64-bit Linux at the moment. FIPS-compliant packages are not available. Note that PE 7 has a component that allows you to fetch Windows event logs without installing an agent. For details, see the Windows Event Collector Administration Guide at https://support.oneidentity.com/technical-documents/syslog-ng-premium-edition/windows-event-collector-administration-guide/

    • Not all of the PE 6 features are available in PE 7 (for example SQL source is missing). Some features are available but not all of their original options are available (for example read-old-records() is missing from the file source). For a detailed list, see the Release Notes (http://support.oneidentity.com/technical-documents/syslog-ng-premium-edition/release-notes/release-notes/differences-in-features-between-syslog-ng-pe-6-lts-and-7)

    Once you are aware of the changes and know that your features and your platform are supported, go ahead and download the latest version of syslog-ng PE 7. At the time of writing it is version 7.0.17 (for a smooth upgrade experience, I recommend using the latest available version). Make sure that you also download your license file, otherwise you cannot use the server features of syslog-ng PE.


    If you are really adventurous you can go ahead and upgrade syslog-ng PE 7 without reading the release notes. But in this case be prepared for an extended down time :)

    For the rest of us it is recommended to do some testing, before installing syslog-ng PE 7 in production. This way you can minimize down time on your production server, as configuration testing and editing is done in a test environment.

    1. Install syslog-ng PE 7 on a test machine.

    2. Copy the syslog-ng configuration from your PE 6 machine and overwrite the syslog-ng PE 7 configuration with it.

    3. Edit the first line of configuration and change the version string to 7.0.
      Now you are ready to check your configuration for problems.

    4. Run your freshly installed syslog-ng application with the -s option, which verifies if the configuration is syntactically correct, prints any problems and exits. You can use information from the release notes and the syntax check to edit your configuration.

    Once there are no more warning messages (or you do not expect real problems from the warning message) the next step is testing syslog-ng with logs to check that syslog-ng works as expected. Start syslog-ng and send some logs at it. You can use the logger utility to send individual test messages or the loggen utility bundled with syslog-ng to send a large amount of synthetic messages at syslog-ng for benchmarking. You can also do some close to real-world testing by configuring one of your clients to send logs also to the test server.

    Note, that if you integrate syslog-ng with any other software, like a SIEM or Elasticsearch, then you should also double check that output formatting works as expected.


    Now that your configuration does not give any more warnings and even the test messages arrive as expected and in the right format, it’s time to do the actual upgrade.

    1. First of all – as a general precaution – create a backup of your old syslog-ng directory (/opt/syslog-ng).

    2. Also make sure that the configuration prepared during testing is copied to the production machine.

    3. You can now delete syslog-ng PE 6.

    4. Once syslog-ng PE 6 is removed, install PE 7. The new version of syslog-ng is started automatically at the end of installation.

    5. Copy the fully tested configuration in place and restart syslog-ng to make the configuration live.Check your logs if syslog-ng started correctly. By now everything should work as expected.

    As you can see, upgrading from syslog-ng PE 6 to PE 7 is not difficult any more. Download syslog-ng PE 7 now: https://www.syslog-ng.com/products/log-management-software/

    Running a script on bootup via Ignition

    Posted by Dusty Mabe on November 06, 2019 12:00 AM
    Introduction With Fedora CoreOS Ignition is being used to configure nodes on first boot. While Ignition json configs are not intended to be a tool that users typically interact with (we are building tooling like fcct for that) I’ll show you an example of how to deliver a script to a Fedora CoreOS (or RHEL CoreOS) host so that it will be run on first boot. Write the script Let’s say we have a small script we want to run that updates the issuegen from console-login-helper-messages to output the node’s public IPv4 address on the serial console during bootup.

    All systems go

    Posted by Fedora Infrastructure Status on November 05, 2019 10:16 PM
    New status good: Everything seems to be working. for services: Package Updates Manager, The Koji Buildsystem, Koschei Continuous Integration, Package maintainers git repositories, ABRT Server

    There are scheduled downtimes in progress

    Posted by Fedora Infrastructure Status on November 05, 2019 09:01 PM
    New status scheduled: Down for scheduled outage for services: Koschei Continuous Integration, Package maintainers git repositories, The Koji Buildsystem, Package Updates Manager, ABRT Server

    NeuroFedora Computational Neuroscience ISO image is now available

    Posted by The NeuroFedora Blog on November 05, 2019 10:12 AM

    We have been busy working on our first deliverable so this post is a little overdue. Since we now have quite a bit of software for computational neuroscience available to use in NeuroFedora, the obvious next step was to try and make this even more easily available to users.

    A Fedora 31 based Comp Neuro ISO image is now ready, you can get it here. For more information on what this contains, and how it is created, read on.

    Fedora Community deliverables

    The Fedora community generates a bunch of deliverables for users. The main ones, of course, are the primary editions: the workstation, the server edition, CoreOS, Silverblue, IoT. They can all be obtained from the community website at https://getfedora.org.

    All of these are ready to use and have gone through a thorough development cycle that includes a stringent Quality Assurance (QA) cycle. These are "live", so they can either either be used directly off the ISO image without having to install them, or they can be used to install a Fedora based system. Them being "live" makes them a great tool for temporary work---grab an ISO, start up a virtual machine, use Fedora to do your work, destroy the virtual machine when done.

    While these are the main deliverables, the Fedora community also generates other media for our diverse user base. These are classified as Spins and Labs. While the Workstation is based on the GNOME desktop environment, Spins provide Fedora users other desktop environment based images: KDE, LXQT, XFCE, Mate, Cinnamon, Sugar on a stick (SAOS). Labs are similar, but instead of focussing on the desktop environment, they include customised sets of software required for particular purposes: Astronomy, Design, Python, Security, Robotics.

    The Fedora Community Change Process

    We therefore, submitted a community change proposal to permit us to generate another Fedora Lab image, one for computational neuroscience. You can read the proposal here. The Changes process allows community members to propose new changes to aid the community. Depending on their scope, they can either be "System wide" or "Self Contained" changes. The community discussed our proposal, and the Fedora Engineering Steering Committee (FESCO) has approved it as a change for the Fedora 32 release.

    So, from Fedora 32 onwards, a Comp Neuro Lab image will be generated by the Fedora Release Engineering Team as an official Fedora community deliverable, and it will feature on the Fedora Labs website.

    Fedora 31 Comp Neuro Image

    Fedora 32, however, is still in the works. Fedora 31 was only released recently. Therefore, in the meantime, as a Beta test, the NeuroFedora team is generating an ISO based on Fedora 31 ourselves. You can get it here.

    This is based on the Fedora Workstation, which is an excellent GNOME based operating system for users. To the Fedora Workstation, we added a variety of simulators and analysis tools that are used in computational neuroscience, such as: auryn, bionetgen, calcium-calculator, COPASI, qalculate, getdp, genesis-simulator, gnuplot, moose, nest, neuron, neurord, octave, paraview, python3, brian2, ipython, nest, neuron, libNeuroML, neo, nineml, PyLEMS, and smoldyn.

    It also includes the complete Python Science stack: matplotlib, jupyter notebook, numpy, pandas, pillow, scikit-image, scikit-learn, scipy, statsmodels, and sympy.

    If you use these tools, please give it a go and see what you think. You can contact us using one of our communication channels (also linked in the top bar of this site). If you use a tool that is not included in NeuroFedora yet, you can also suggest it for inclusion using this form.

    NeuroFedora is volunteer driven initiative and contributions in any form always welcome. You can get in touch with us here. We are happy to help you learn the skills needed to contribute to the project. In fact, that is one of the major goals of the initiative---to spread technical knowledge that is necessary to develop software for Neuroscience.

    Xwayland randr resolution change emulation now available in Fedora 31

    Posted by Hans de Goede on November 05, 2019 08:41 AM
    As mentioned in an earlier blogpost, I have been working on fixing many games showing a small image centered on a black background when they are run fullscreen under Wayland. In that blogpost I was moslty looking at how to solve this for native Wayland games. But for various reasons almost all games still use X11, so instead I've ended up focussing on fixing this for games using Xwayland.

    Xwayland now has support for emulating resolution changes requested by an app through the randr or vidmode extensions. If a client makes a resolution change requests this is remembered and if the client then creates a window located at the monitor's origin and sized to exactly that resolution, then Xwayland will ask the compositor to scale it to fill the entire monitor.

    For apps which use _NET_WM_FULLLSCREEN (e.g. SDL2, SFML or OGRE based apps) to go fullscreen some help from the compositor is necessary. This is currently implemented in mutter. If you are a developer of another compositor and have questions about this, please drop me an email.

    I failed to get this all upstream in time for Fedora 31 final. But now it is all upstream, so 've backported the changes and created an update with the changes. This update is currently in updates-testing, to install this update run the following command:

    sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2019-103a594d07

    Linux Day 2019 @ Bari: A Retrospective

    Posted by Fedora Community Blog on November 05, 2019 06:30 AM
    Linux Day Gadgets

    Linux Day was held in Bari on Saturday, October 26 2019. First of all, I am excited to say that it was a successful event!


    Participants were beyond expectations and found this event a fantastic opportunity to learn, advance, and share their knowledge on Linux systems and trending themes, like Artificial Intelligence, Cybersecurity, and Digital Forensics. People were mostly technical high school students, university students of engineering and computer science, and university professors.

    Important people, from university to local industries, came to speak and gave interesting insights on said disciplines, stimulating discussions that protracted from morning to evening!


    How about Fedora? Well, Fedora was ever present during the event. We placed gadgets on the registration desk, dedicated a special lunch menu entry, tried to install it everywhere we could put our hands on people PCs. We also used Fedora to win a Cybersecurity challenge! You may ask: how did we do so many things? Don’t worry, let’s see them with some quick photos 🙂

    Linux Day Front Desk Linux Day Gadgets Audience at Linux Day Talks The Menu of the Day People at Linux Day Install Party CTF winners

    Linux and beyond

    This Linux Day was a great impulse for our local community here in Bari and I congratulate with UNPLUG community and URL Rete Libera association for an astonishing organization and work! People got inspired under the name of open source and new, insightful technologies. It was the first ever to earn such popularity.

    I hope my talk gave to all this people a path to embrace open source communities by seeing them as they really are: a group of extraordinary people with selflessness and other great values. It was a human-side stimulus to join Fedora, I believe that such an experiment was successful: people thanked me for such original talk that shared a part of Linux communities that is often overlooked: people, human beings, how to give credit to their work and how to share new work.

    This was a perfect day for Linux and I really hope that next year will be like so. Bari has a great potential to become a cultural pole of open source technology and I really hope that we, fedorians, recognize it that way.

    See you next year! 🙂

    The post Linux Day 2019 @ Bari: A Retrospective appeared first on Fedora Community Blog.

    Fedora 30 : How to remove packages without dependency.

    Posted by mythcat on November 04, 2019 06:36 PM
    In this tutorial, I will show you how to remove packages without dependency.
    I have this software named freecad.x86_64 and I want to remove it.
    If I use the dnf tool then I got this output:
    [root@desk mythcat]# dnf remove freecad.x86_64 
    Dependencies resolved.
    Package Arch Version Repo Size
    freecad x86_64 1:0.18.3-5.fc30.1 @updates 141 M
    Removing unused dependencies:
    Coin3 x86_64 3.1.3-24.fc30 @fedora 11 M
    OCE-foundation x86_64 0.18.3-4.fc30 @fedora 11 M
    OCE-modeling x86_64 0.18.3-4.fc30 @fedora 58 M
    OCE-ocaf x86_64 0.18.3-4.fc30 @fedora 11 M
    OCE-visualization x86_64 0.18.3-4.fc30 @fedora 6.7 M
    SoQt x86_64 1.5.0-26.fc30 @fedora 1.0 M
    assimp x86_64 3.3.1-19.fc30 @fedora 9.7 M
    boost-python3 x86_64 1.69.0-8.fc30 @updates 473 k
    dotconf x86_64 1.3-20.fc30 @fedora 61 k
    espeak-ng x86_64 1.49.2-6.fc30 @fedora 6.6 M
    The package is from Nightly FreeCAD, you can enable it if you want to install later:
    [root@desk mythcat]# sudo dnf copr enable @freecad/nightly
    To solve this issue you need to change this file:
    [root@desk mythcat]# vim /etc/dnf/dnf.conf
    From clean_requirements_on_remove=True to clean_requirements_on_remove=False.
    The next commands will fix and remove the package:
    [root@desk mythcat]# dnf clean all
    86 files removed
    [root@desk mythcat]# dnf remove freecad.x86_64
    Dependencies resolved.
    Package Architecture Version Repository Size
    freecad x86_64 1:0.18.3-5.fc30.1 @updates 141 M
    Removing dependent packages:
    freecad-data noarch 1:0.18.3-5.fc30.1 @updates 194 M

    Transaction Summary
    Remove 2 Packages

    Freed space: 335 M
    Is this ok [y/N]:

    Cloning a MAC address to bypass a captive portal

    Posted by Fedora Magazine on November 04, 2019 08:00 AM

    If you ever attach to a WiFi system outside your home or office, you often see a portal page. This page may ask you to accept terms of service or some other agreement to get access. But what happens when you can’t connect through this kind of portal? This article shows you how to use NetworkManager on Fedora to deal with some failure cases so you can still access the internet.

    How captive portals work

    Captive portals are web pages offered when a new device is connected to a network. When the user first accesses the Internet, the portal captures all web page requests and redirects them to a single portal page.

    The page then asks the user to take some action, typically agreeing to a usage policy. Once the user agrees, they may authenticate to a RADIUS or other type of authentication system. In simple terms, the captive portal registers and authorizes a device based on the device’s MAC address and end user acceptance of terms. (The MAC address is a hardware-based value attached to any network interface, like a WiFi chip or card.)

    Sometimes a device doesn’t load the captive portal to authenticate and authorize the device to use the location’s WiFi access. Examples of this situation include mobile devices and gaming consoles (Switch, Playstation, etc.). They usually won’t launch a captive portal page when connecting to the Internet. You may see this situation when connecting to hotel or public WiFi access points.

    You can use NetworkManager on Fedora to resolve these issues, though. Fedora will let you temporarily clone the connecting device’s MAC address and authenticate to the captive portal on the device’s behalf. You’ll need the MAC address of the device you want to connect. Typically this is printed somewhere on the device and labeled. It’s a six-byte hexadecimal value, so it might look like 4A:1A:4C:B0:38:1F. You can also usually find it through the device’s built-in menus.

    Cloning with NetworkManager

    First, open nm-connection-editor, or open the WiFI settings via the Settings applet. You can then use NetworkManager to clone as follows:

    • For Ethernet – Select the connected Ethernet connection. Then select the Ethernet tab. Note or copy the current MAC address. Enter the MAC address of the console or other device in the Cloned MAC address field.
    • For WiFi – Select the WiFi profile name. Then select the WiFi tab. Note or copy the current MAC address. Enter the MAC address of the console or other device in the Cloned MAC address field.

    Bringing up the desired device

    Once the Fedora system connects with the Ethernet or WiFi profile, the cloned MAC address is used to request an IP address, and the captive portal loads. Enter the credentials needed and/or select the user agreement. The MAC address will then get authorized.

    Now, disconnect the WiFi or Ethernet profile, and change the Fedora system’s MAC address back to its original value. Then boot up the console or other device. The device should now be able to access the Internet, because its network interface has been authorized via your Fedora system.

    This isn’t all that NetworkManager can do, though. For instance, check out this article on randomizing your system’s hardware address for better privacy.

    <figure class="wp-block-embed-wordpress wp-block-embed is-type-wp-embed is-provider-fedora-magazine">
    Randomize your MAC address using NetworkManager
    <iframe class="wp-embedded-content" data-secret="V7gFe0GI0s" frameborder="0" height="338" marginheight="0" marginwidth="0" sandbox="allow-scripts" scrolling="no" security="restricted" src="https://fedoramagazine.org/randomize-mac-address-nm/embed/#?secret=V7gFe0GI0s" style="position: absolute; clip: rect(1px, 1px, 1px, 1px);" title="“Randomize your MAC address using NetworkManager” — Fedora Magazine" width="600"></iframe>

    Episode 168 - The draconian draconians of DRM

    Posted by Open Source Security Podcast on November 04, 2019 12:00 AM

    Josh and Kurt talk about the social norms of security. We also discuss security coprocessors and the reasons behind adding them to hardware. Is DRM a draconian security measure or do we need it to secure the future? We also touch on the story of NordVPN getting hacked. The real story isn't they got hacked, the story is they responded like clowns. The actual problem was one of leadership, there are certain leadership skills you can't be taught, you can only learn.

    <iframe allowfullscreen="" height="90" mozallowfullscreen="" msallowfullscreen="" oallowfullscreen="" scrolling="no" src="https://html5-player.libsyn.com/embed/episode/id/11891765/height/90/theme/custom/thumbnail/yes/direction/backward/render-playlist/no/custom-color/6e6a6a/" style="border: none;" webkitallowfullscreen="" width="100%"></iframe>

    Show Notes

      Déployer votre application php avec Deployer

      Posted by Guillaume Kulakowski on November 03, 2019 08:21 PM

      Cela va maintenant faire un peu plus d’1 an que ce blog est motorisé par WordPress et non plus par Dotclear. Pour rappel, lors de cette migration vers WordPress, afin d’avoir quelque chose d’un minimum industrialisé, de propre mais surtout qui me satisfasse, j’ai fait plusieurs choix techniques : Utiliser Timber pour gérer mon thème. […]

      Cet article Déployer votre application php avec Deployer est apparu en premier sur Guillaume Kulakowski's blog.

      Fedora 30 : Introduction to Qt Designer.

      Posted by mythcat on November 03, 2019 06:15 PM
      Qt Designer is the Qt tool for designing and building graphical user interfaces (GUIs) with Qt Widgets... see the Qt Designer manual webpage.
      [root@desk mythcat]# dnf install qt5-designer.x86_64

      Let's start this tool with this command:
      [mythcat@desk ~]$ designer-qt5 
      Follow this video tutorial from my youtube channel:
      <iframe allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="allowfullscreen" frameborder="0" height="315" src="https://www.youtube.com/embed/itAaBxK1eMk" width="560"></iframe>
      You can preview your work with Ctrl+R keys.
      After you finish with the project then save the file with this name: mytest.ui.
      The next command to create your working python file named mytest.py.
      Use this command with the -x option creates the main section to the my.py file that will allow us to test quickly whether the GUI looks as we intended.
      [mythcat@desk ~]$ pyuic5 -x  mytest.ui -o mytest.py
      Now you can run it to see the output:
      [mythcat@desk ~]$ python3  mytest.py

      Fedora 30 : About Simple Screen Recorder tool.

      Posted by mythcat on November 03, 2019 11:43 AM
      The Simple Screen Recorder tool can be easily installed on Fedora 30 and provide a GUI interface for recording screen with audio input. Use the dnf tool to install it:
      [root@desk mythcat]# dnf install simplescreenrecorder.x86_64

      I used the LXDE Desktop Environment, see the command to identify the running desktop environment:
      [mythcat@desk ~]$ echo $XDG_CURRENT_DESKTOP
      The tool can be found on Fedora main menu: Sound & Video, see the screenshot:

      The tool start with this windows screen, you need to press the Continue button:

      The next steps comes with configuration area for your video recorder.
      I set and save my new Input profile to record an screen area.
      You can use a rectangle, change the size from left to right or select the window to define the area for record video.
      I change the Audio input to use my microphone.

      The next step let you to set the file , video and audio settings for output. I let all with default settings.
      The last step let you to see informations , preview and set the hotkeys.
      I can use keyboard to start and stop recorder.

      FPgM report: 2019-44

      Posted by Fedora Community Blog on November 02, 2019 02:57 AM
      Fedora Program Manager weekly report on Fedora Project development and progress

      Here’s your report of what has happened in Fedora Program Management this week. Fedora 31 was released on Tuesday. Fedora 29 will reach end of life on 26 November.

      I have weekly office hours in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else.



      DevConf.CZBrno, CZ24–26 Jan 2020closes 6 Nov
      Open TestConBeijing, CN30–31 Mar 2020closes 10 Nov
      CentOS DojoBrussels, BE31 Jan 2020closes 18 Nov
      FOSDEM Distro DevroomBrussels, BE2 Feb 2020closes 1 Dec
      Indy Cloud ConfIndianapolis, IN, US26–27 Mar 2020closes 21 Dec

      Help wanted

      Upcoming meetings


      Fedora 31


      • 13 November — Elections nomination deadline
      • 26 November — Fedora 29 EOL

      Fedora 32


      Submitted to FESCo
      Approved by FESCo

      CPE update

      Community Application Handover & Retirement Updates

      • Elections: Blocking issue was fixed
      • Fedocal: jlanda started to work on communishift port
      • Nuancier: Benson Muite is now working on OIDC authentication – Thank you Benson!
      • Fed-msg: fedmsg-logger equivalent for fedora-messaging

      Other Project updates

      • Rawhide Gating:
        • A call to arms email has been sent asking for testers for multi build
        • Single build workflow is working again and is aligned with multi-build workflows also
        • Update for the multi-build workflow needs to be created with autotime on, otherwise the update will not get pushed
        • Overview page of the remaining blockers and dependencies organized at: https://hackmd.io/Gbuu9JOPR–Y2yNCBEYI5A?view
        • Ci.centos.org is still not using fedora-messaging
        • Ci-resultsdb-listener with fedora-messaging and support for the new messages format is not deployed in production yet
      • repoSpanner
        • Developed another experimental patch that got us an ~83x speed up.
        • Got 122% performance patch merged.
        • Worked with smooge to get a repoSpanner cluster deployed on realistic cross-datacenter hardware.
        • repoSpanner is still extremely slow when all three DCs are used. Est. 58 minutes to push Bodhi into it, even with the 83x speedup patch. The team is investigating a solution.

      The post FPgM report: 2019-44 appeared first on Fedora Community Blog.

      Toolbox — A fall 2019 update

      Posted by Debarshi Ray on November 01, 2019 07:53 PM


      Things have been moving fast in Toolbox land, and it’s time to talk about what we have been doing lately.

      New home

      Toolbox is now part of the containers organization on GitHub. We felt that the project had outgrown the prototype stage — going by the activity on the GitHub project it’s safe to say that there are at least a few thousand users who rely on it to get their work done; and we are increasingly working towards expanding the scope of the project to go beyond just setting up a development environment.

      Housing the project in my personal GitHub namespace meant that I couldn’t share admin access with other contributors, and this was a problem we had to address as more and more people keep joining the project. Over the past year, we have developed a really good working relationship with the Podman team and other members of the containers organization, without whom Toolbox wouldn’t exist, so moving in under the same umbrella felt like a natural next step towards growing the project.

      Migration to cgroups v2

      Fedora 31 ships with cgroups v2 by default. The major blocker for cgroups v2 adoption so far was the lack of support in the various container and virtualization tools, including the Podman stack. Since Toolbox containers are just OCI containers managed with Podman, we saw some action too.

      After updating the host operating system to Fedora 31, Toolbox will try to migrate your existing containers to work with cgroups v2. Sadly, this is a somewhat complicated move, and in theory it’s possible that the migration might break some containers depending on how they were configured. So far, as per our testing, it seems that containers created by Toolbox do get smoothly migrated, so hopefully you won’t notice.

      However, if things go wrong, barring a delicate surgery on the container requiring some pretty arcane knowledge, your only option might be to do a factory reset of your local Podman installation. As factory resets go, you will lose all your existing OCI containers and images on your local system. This is a sad outcome for those unfortunate enough to encounter it. However, if you do find yourself in this quagmire then take a look at the toolbox reset command.

      Note that you need to have podman-1.6.2 and toolbox-0.0.16 for the above to work.

      Also, this is one of those changes where it bears repeating that online RPM package updates are fragile. They are officially unsupported on Fedora Workstation, and variants like CoreOS and Silverblue make it even harder. A cgroups v2 migration is only expected to work on a freshly booted system.


      The last six months have seen a whole boatload of new features and improvements. Here are some highlights.

      On Fedora Silverblue and Workstation, GNOME Terminal keeps track of the current Toolbox container, and just like it preserves the current working directory when opening a new terminal, it’s also able to preserve the Toolbox environment. This is quite convenient when hacking on a Silverblue system, because it removes the extra step of entering a toolbox after opening a new tab or window.

      The integration with the host operating system has been deepened. Toolbox containers can now access virtual machines managed by the host’s system libvirt instance, and the host’s ulimits are preserved. The entirety of /dev is made available inside the toolbox as a step towards supporting the proprietary Nvidia driver to enable CUDA for AI/ML frameworks like TensorFlow.

      The container’s /run/host now has big chunks of the host’s file hierarchy. This is handy for one-off use-cases which require access to parts of the host that aren’t covered by Toolbox by default.

      Last but not the least, Kerberos now works inside Toolbox containers. This will make it easier to contribute to Fedora itself from inside a toolbox.

      Fedora Design Suite 31 available

      Posted by Luya Tshimbalanga on November 01, 2019 05:37 AM
      As announced on Fedora Magazine, Design Suite 31 is now available for users like graphic artists and photographers among them.
      Notable update is the availability of Blender 2.80 featuring a revamped user interface. Other applications are mostly improved stability.

      Users with touch screen devices will notice an improved performance from the Fedora Workstation from which Design Suite is based. Due to a bug related to desktop environment (Gnome Shell running on Wayland), using a stylus can cause applications to crash so the workaround is to run on Gnome on Xorg until the fix lands on a future update.

      Full details published on the wiki section.

      Native GTK Dialogs in LibreOffice

      Posted by Caolán McNamara on October 31, 2019 08:01 PM

      LibreOffice Native GTK Dialog Status

      The LibreOffice UI was traditionally implemented with its own VCL toolkit which via theming emulated the host desktop toolkit.

      Then we migrated the file format the dialogs were described in to the GtkBuilder file format. But still implemented with VCL widgetry, though with additional GTK-alike layout widgets.

      Then migrated the translation format to gettext .mo files, which added plural form translation support we had lacked.

      Then incrementally migrated the code driving the dialogs to a new API with two implementations, one for VCL widgetry and one for GTK.

      Over the last few major releases the GTK version of LibreOffice has increasingly had true GTK dialogs and less VCL dialogs and in master, as of this week, there are now no direct uses of the VCL dialog APIs.

      There are still some non-dialog utility windows and other elements to port over, but dialogs are complete.

      LibreOffice has a lot of UI. There are 1029 XML UI definition files in master. 480 definitions of a GtkDialog and 75 additional GtkMessageDialog definitions. The remainder of the files typically describe a single page of a Notebook, Assistant or Sidebar, often appearing in multiple dialogs.

      Here are some gifs of a small set of the dialogs from master under Fedora 31, taken under Wayland with peek, showing some of the stock animations of the default GTK 3.24 Adwaita theme

      The Writer Character dialog

      Notebook, Color Selector MenuButton, and ToggleButton animations

      The Calc Page dialog

      SpinButtons and legacy Preview widgets hosted in a native dialog

      The Writer Paragraph dialog

      "Double Decker" Notebook and Scale widgets

      The Writer AutoCorrect dialog

      Smooth scrolling of huge Emoji autocorrect list

      Chart 3D View dialog

      Amusingly Over-engineered custom lighting direction widget

      The Options dialog

      TreeView, Overlay ScrollBar, fade in animation of CheckButtons

      Join us in #redhat-cpe on Freenode

      Posted by Randy Barlow on October 31, 2019 07:59 PM

      tl;dr; join us in #redhat-cpe on Freenode!

      Many moons ago, Red Hat merged the CentOS infrastructure team with the Fedora Infrastructure team, into a team known as "Community Platform Engineering" (CPE). Most of the individuals on the combined team have mostly continued to focus on the project they were …

      New hope for Packages app

      Posted by Miroslav Suchý on October 31, 2019 01:45 PM

      Jun Aruga and I worked on a rewrite of Fedora Packages


      While this application is useful, it is written in Python 2. To quote current maintainer Clement Verna:

      “… the big problem is the technology stack it is built on TurboGears2 and making heavy use of Moksha (https://moksha.readthedocs.io/en/latest/), while TG2 is still active upstream, this is not the case with Moksha and some of the TG2 dependencies the application has. The effort to move away from these two frameworks is quite high, and I don’t think we currently have the cycles for it…”

      We offered help and rewritten the application in Python 3, Flask, and PatternFly. We were able to rewrite around 40 percent of the code/templates. The current code is temporary at


      and we plan to do massive merge once the new app provides the same functionality as the original one.

      Jun did the great work of setting up CI, so we are immediately informed when something is broken.

      We plan to continue on this task (with slower pace) and to switch production application to new code before python2 becomes unsupported in Fedora.

      Disabling kinetic scrolling in Firefox

      Posted by Kamil Páral on October 31, 2019 11:33 AM

      In Firefox 70, there is a new feature called kinetic scrolling [1]. If you scroll the web page using trackpad (or possibly touchscreen), the scroll event will not stop immediately after releasing your fingers, but it will gradually slow down, as if a rotating wheel slowly stops. After using it for a short while, I started to hate it really quickly. The problem is that the slowdown-and-stop occurs very slowly and if you just want to scroll the webpage to continue reading, you need to wait several seconds until the page fully stops moving. That’s really annoying. Fortunately, this cool new feature can be disabled. Just open about:config page in a new tab, search for apz.gtk.kinetic_scroll.enabled and set it to false. Tada! No more kinetic scrolling.

      [1] I found these related Mozilla tickets: #1213601, #1564238

      Firefox tips for Fedora 31

      Posted by Fedora Magazine on October 31, 2019 08:08 AM

      Fedora 31 Workstation comes with a Firefox backend moved from X11 to Wayland by default. That’s just another step in the ongoing effort of moving to Wayland. This affects GNOME on Wayland only. This article helps you understand some changes and extra steps you may wish to take depending on your preferences.

      There is a firefox-wayland package available to activate the Wayland backend on KDE and Sway desktop environments.

      The Wayland architecture is completely different than X11. The team merged various aspects of Firefox internals to the new protocol where possible. However, some X11 features are missing completely. For such cases you can install and run firefox-x11 package as a fallback.

      If you want to run the Flash plugin, you must install the firefox-x11 package, since Flash requires X11 and GTK 2. Wayland also has a slightly different drag and drop behavior and strict popup window hierarchy.

      Generally, if you think Firefox is not behaving like you want, try the firefox-x11 package. In this case, ideally you should report the misbehavior in Bugzilla.

      The Wayland architecture comes with many benefits, and overcomes many limitations of X11. For instance, it can deliver smoother rendering and better HiDPI and screen scale support. You can also enable EGL hardware acceleration on Intel and AMD graphics cards. This decreases your power consumption and also gives you partially accelerated video playback. To enable it, navigate to about:config, and search for layers.acceleration.force-enabled. Set this option to true and restart Firefox.

      Brave users may wish to try the Firefox next-generation renderer, called WebRender, written in Rust. To do that, search for gfx.webrender.enabled and gfx.webrender.all in about:config. Set them to true, then cross your fingers and restart Firefox.

      But don’t worry — even if Firefox crashes at start after these experiments, you can launch it in safe mode to reset these options. Start Firefox from a terminal using the following command:

      $ firefox -safe-mode

      Fedora 31 has just rolled out

      Posted by Luca Ciavatta on October 31, 2019 08:05 AM

      Many under the armor improvements and a lot of changes, new features, and new graphical experiences: here we are, the new Fedora 31 release. Obviously, the big GUI step forward for Fedora Workstation is the latest GNOME 3.34 update, which brings some visual changes, different functions, and real performance improvements. Fedora 31 also drops the 32-bit support, so now you[...]

      The post Fedora 31 has just rolled out appeared first on CIALU.NET.

      Fedora-related FOSDEM activities

      Posted by Fedora Community Blog on October 31, 2019 07:00 AM

      FOSDEM is a free-to-attend event held every year in Brussels, Belgium. It is a community-run event for developers to meet and work together. In 2020 it will be held on 1–2 February—the weekend following DevConf.CZ. The main track proposals are closed, but there are a few Fedora-related or -adjacent activities if you’re interested.

      Distributions Developer Room

      The Distributions Developer Room will be held on Sunday, 2 February. This devroom focuses on the issues specific to creating distributions, including technology and process. Talks on how distributions can cooperate are also welcome. For details, see the announcement post. You can submit your proposals through 1 December 2019 in the FOSDEM CfP tool.

      CentOS Dojo

      The CentOS project will be holding their annual CentOS Dojo on the day before FOSDEM—Friday, 31 January. Details of the event may be found on the CentOS Wiki. While the event is CentOS-centric, there’s lots of overlap among the RHEL/Fedora/CentOS family of Linux distributions, and we encourage you to consider submitting your presentation proposals for anything you’re working on which may have some relevance to this larger ecosystem. Proposals close 18 November.

      Fedora Booth

      We’re coordinating a Fedora booth at FOSDEM. If you’re interested in participating, please sign up on the wiki page. If you have an accepted presentation, please let us know so we can help you promote it.

      The post Fedora-related FOSDEM activities appeared first on Fedora Community Blog.

      podman-compose: Review Request

      Posted by Gwyn Ciesla on October 31, 2019 12:28 AM

      Want to use docker-compose.yaml files with podman on Fedora?

      Review podman-compose! I’ll even review one of yours, no extra charge!


      Something to think about during Jazz Improvisation

      Posted by Adam Young on October 30, 2019 07:59 PM

      Jazz improvisation performance. You’ve been preparing. You have mastered your instrument with long tones, scales, and exercises. You have worked on general knowledge of music theory, chords, and the relationship between them. Now what?

      You need to know the song. Get the song in your head. Memorize the melody. Learn the chords on Piano, even if that is not your instrument. Learn the words to the tune if there are some. Play long passages over each chord on your instrument, to get the various sounds of it in your ears. Come up with phrases that work over subsets of the chord changes, like the ii-V-I sections etc. Play along with iReal Pro or some other automated rhythm section.

      By the time you get on the stand to improvise, you should not be thinking about the song. You should be getting ready to tell a story. There are a couple mental techniques you can use to develop your solo. You can build up from a musical phrase, or you can mentally tell yourself a story and play the words that you hear.

      When you build up from a musical phrase, you are going to take an idea, state it and then modify it through out the solo. You want to give the audience a hook to identify. It can start with a fragment of the melody line, or a phrase in your head. Something rhythmic. Something melodic. Repeat it, as close as you can, over the changes. Even if you play the exact same notes, it will have a different effect over different chords. More likely, you will want to adjust that phrase as the chords change. Add on to it. Drop notes from it.

      Sonny Rollins’s solo on “Tenor Madness” is a great example of building up a fragment this.

      One technique to use, but not over use, is to quote from a well known other song. A friend of mine opened a solo by playing the first phrase from “Sanford and Son.” Quoting a phrase like this is a shortcut to connecting with the audience. It can also be fun to throw a quote in to the middle of the solo, but make sure it makes sense in the context of the solo.

      You can think words in your head, and play those words. Improvise a story in your head, about Meeting Miss Jones or Something that Happened ‘Round Midnight or who you met On the A Train. You may want to pretend to be a character when you do this. Humphrey Bogart as Sam Spade in the Maltese Falcon, turning up his collar and walking away into the San Francisco rain. You are doing a performance, and the more you are in to it, and get lost in it, the more your audience will link in to your world.

      If you are still learning a song, you might want to use the lyrics to keep you in place, and play over them. You don’t replay the head, just use the words as a running commentary, and play “around” them as you solo.

      If you are trying to play over “Donna Lee” you might find it easier to learn and track the lyrics to “Back home in Indiana” and keep those running through your head as you solo.

      Build to a climax, conclude, and hand over the mike to the next player.

      Fedora 31

      Posted by Paul Mellors [MooDoo] on October 30, 2019 10:37 AM
      Well it seems like Fedora 31 has been released, I'm feeling the need for an upgrade.

      I think i'll just download the ISO from here - https://getfedora.org/ but I know I can upgrade from the command line, so if you don't know how to do it, try this [please note i've not tried it so if it hoses your system, erm sorry], it also might cause issues if you have any third party repos enabled on your system, but give it a try any way.

      Upgrade your software

      sudo dnf upgrade --refresh
      Install the dnf plugin

      sudo dnf install dnf-plugin-system-upgrade
      Start the upgrade

      sudo dnf system-upgrade download --releasever=31
      Start the upgrade and reboot

      sudo dnf system-upgrade reboot
      Go and make a cuppa....

      Enjoy Fedora 31