Solid Smoke

On Fedora (and other systems that use DNF for package management), we can set the directory used by DNF for cache data. Combined with keepcache setting, this can be used to collect all RPM packages downloaded by DNF. Then one can just copy these files to another computer without Internet access and use them to install/update packages on that machine. The configuration file for DNF used to be /etc/dnf/dnf.conf . I used to have the following two settings in my dnf.conf file: [main] cachedir = /my/cache/dir/path keepcache = True But after I installed Fedora 41, which has DNF5 , I found that setting cachedir was not having any effect. Usually, when you do a ' sudo dnf update ' command, you could see repository data getting created in the cache directory. But for some reason, this was not happening. Digging around DNF5 documentation , I finally figured out the reason. For superuser, the cache directory needs to be set by system_cachedir setting and not cachedir . So my /etc...

I have been struggling for the past two hours to get qDebug() messages from my Qt 5 application to show up on the 'Application output' pane in Qt Creator IDE on Linux. Finally I found a solution, thanks to a user on Qt IRC channel. To enable log messages in Qt, do the following: Edit ~/.config/QtProject/qtlogging.ini and make sure it has: [Rules] *.debug=true qt.*.debug=false With this, I was getting the messages when I run the application from a terminal. But Qt Creator was not showing the qDebug() messages. To have the messages displayed in Qt Creator, do the following: Qt creator > Tools > Options > Kits, select your kit, find Environment, click change and add: QT_ASSUME_STDERR_HAS_CONSOLE=1 This fixed the problem for me. I thought I should document the full process here as Google wasn't getting me good leads. My environment: Fedora 29 Linux x86-64 Qt 5.11.3 Qt Creator v4.7.2 References: https://bugzilla.redhat.com/show_bug.cgi?id=12272...

Fedora 16 was released almost a month back. This is the first Fedora release to have switched to the GRUB2 boot loader. I had some trouble installing Fedora 16 - the boot loader won't get installed on my MBR since there wasn't enough space to accommodate the boot image. The details of my struggles can probably be the subject of another post. Here, it must suffice to say that I had nuked my first partition, containing Windows 7, to make sufficient space (unallocated sectors) at the beginning of the HDD for grub2 boot image. After installing F16, I reinstalled Windows 7 on to the first partition on the HDD. Everything was fine, except, unsurprisingly, that it replaced grub2 boot loader with its own. Getting back grub2 to boot Fedora was a matter of doing this: Boot using Fedora 16 DVD Select 'Troubleshoot' and use the 'rescue mode' Let Anaconda autodetect existing Linux installations, and when prompted, select your F16 installation from among the multi...