Computers – Don's House of Fine Patisseries

December 1, 2024December 1, 2024

Desktop Linux: Unveiled Chapter 7: Desktop applications

Previous chapter: Desktop Linux: Unveiled Chapter 6: Upgrading the Operating System

Using your computer of course requires some software beyond the base operating system; fortunately, most desktop linux distributions not only have repositories of freely installable software, often more common software as decided by the distro’s maintainers are pre-installed on the system at the same time as system installation.

This post is concentrating on the popular office suite LibreOffice which includes a drawing program, a word processor, a spreadsheet application, and a database application. While this post will show a few functions of each part, it is in no way intended to be a tutorial, but rather a cursory demonstration of each, leaving the exploration of each to you, the reader.

In this post I occasionally refer to operating systems beyond Linux. Also, contrary to my usual habit of not editorializing in this series, I offer the following: Many Linux software suites are largely, although importantly, not completely compatible with other known equivalents on other systems. They will often be able to open and edit files created by them; however, the compatibility and drop-in replacement value of each piece of software for the other (regardless of in which order) is often variable, sometimes quite substantially.

Note that occasionally, some screenshots were taken at different times for the sake of completeness, but presented in the order seen here, for the sake of the narrative.

Pinning Apps to the Dock:

Start from the Activities (hot corner in the upper left hand corner (the horizontal bar; either just quickly move the mouse there, or if necessary, click on the the horizontal bar):

I searched for “Lib” which brought up three of LibreOffice’s apps: Writer, Calc, and Impress, and I right clicked each one …

Searching for installed LibreOffice components

… each of which I pinned to the dock at the bottom, one at a time:

Templates:

Note: In this post, the use of existing document templates found on the internet will be generously relied upon in order to demonstrate in a cursory fashion some of the resources available to desktop users — both of free software packages and other systems as well — as well as to simplify the mounting and development of the narrative using said existing documents. The site www.freedesktop.org, by happenstance, is frequently used, as is the templates section of www.libreoffice.org. Of note, especially on the former site, there are a number of templates which are in languages other than English, and some which have been on the site for several years, using older formats. Hopefully, the language barriers as the cases may be will not be too difficult to surmount given online translation services, while the older file formats are normally seamlessly supported by current software suites, with the ability to save in modern formats.

Users are of course free to create documents from scratch as they would on any system.

Going back to the activities screen, choose the Firefox icon (orange and blue, on the left at the bottom):

In the address bar, enter the address of a search engine, such as www.duckduckgo.com:

Search for templates. In this case, I specifically asked for templates appropriate for LibreOffice, which brought me to www.opendesktop.org:

In the search bar, I searched for LibreOffice, which gave me the following options:

… and chose for ODF Text Templates (for word processessing):

Browsing through the templates, I chose a CV template, for “Tux the Penguin — Brand Ambassador and Mascot”:

… which I downloaded:

On the activities screen, I opened up the Files application:

Drawing:

… and this is where I learned that the downloaded CV template was not what it seemed. 🙂

Much like other popular desktops, Fedora Linux has several fully functional and fully featured drawing software. One such piece is LibreOffice Draw, which functions similarly to Microsoft Visio, allowing for some basic-to-not-so basic graphical manipulations, editing, basic draughting, and inserting texts.

From the Files program just opened, I navigated to the Downloads directory, where the CV was located after downloading, and despite having believed that the CV I had downloaded was a text document, the file format in fact proved to be a drawing format:

I double-clicked on the CV file, which, since LibreOffice Draw isn’t always a part of a Fedora base installation, launched the software store, and having found LibreOffice Draw in the Fedora repositories, offered to install it, which I accepted:

CV file double-clicked, launching the software store in order to install required software

Once LibreOffice Draw had been installed, I asked that it be launched:

After closing the offer to see the “What’s New” notes, I went to the File dropdown menu to open the file:

… and navigated over to the Downloads directory, where the CV was located.

I clicked on the CV file to open it:

In Draw — depending on the nature of the input file — various existing texts can be modified, as well as many basic-to-not-so-basic graphical manipulations. In the case of this file, the file was designed such that the text could be modified:

To manipulate images, the picture of Tux (the penguin) was double-clicked to select it, the right mouse button was clicked, and the “Rotate or Flip” option was selected:

… and I chose to flip the picture of Tux upside-down:

Some modestly — or more complex — drawings, including multimedia documents such as the CV shown above, can be created and / or modified, which I leave to the reader to explore.

Word Processor:

Much like other popular desktops, Fedora Linux has several fully functional and fully featured word processing software suites. One of the more popular such pieces is LibreOffice Writer.

I returned to the opendesktop.org website, and chose a business card template to open in a word processor — LibreOffice Writer.

I navigated to find a business card template:

opendesktop.org template for business cards

… and downloaded the file:

Similar to how the CV above was opened, the business card template was opened, without having to go through the installation of LibreOffice Writer:

Business card template opened in LibreOffice Writer

The text of the first card was changed to a “Desktop Linux: Revealed” theme:

Name and contact details on first card changed

The modifications were also saved:

Returning to the opendesktop.org templates, I chose the “Organica Business Forms” to download:

The page for the Organica Business Forms was opened:

… and the file downloaded:

Template downloaded and directory opened

The business forms were compressed in the .tar format, analogous to .zip files:

Directory with downloaded file, which was double clicked

The archive was double-clicked, revealing a directory contained within:

.tar file double clicked, opening up the archive

The directory was double-clicked, revealing several templates: Business cards (different from above), a fax cover sheet, four different kinds and sizes of labels, an invoice, and a letter:

Going back to Writer, the letter file was double-clicked, which again opened the file in LibreOffice Writer:

A space was added between two paragraphs:

The “Table” drop down menu was opened:

… and the “Insert Table” option was chosen:

… which opened up a window to determine some settings for the table to be inserted:

Window opened to set table characteristics

A table with five columns and five rows was selected:

The table was selected, and the right mouse button was clicked, revealing a contextual menu:

The option “Table Properties” was selected, bringing up a window:

The button for all lines under “Line Arrangement” was chosen in the Borders tab, in order to insert borders around all the cells of the table:

The “Ok” button was pressed, returning me to the document, showing now all the cells of the table with borders:

Text was added to a cell in the upper left hand corner (“Linux Desktop”):

A number of other cells were filled in:

The “File” drop down menu was opened:

… and the file was saved:

As with the previous section, I leave it to the reader to further explore LibreOffice Writer to see the various options in the various menus, and the various kinds of text documents that can be created.

Spreadsheets:

Much like other popular desktops, Fedora Linux has several fully functional and fully featured spreadsheet software. One of the most popular such pieces is LibreOffice Calc.

After saving the business cards, I returned to the freedesktop.org website, browsing the spreadsheet templates:

opendesktop.org page sorting for spreadsheets

I chose the Amortization Schedule:

opendesktop.org page with amortization schedule

The amortization Schedule was downloaded:

Similarly to previous files, the Amortization Schedule was opened (file double clicked in the file download directory).

Amortization schedule opened in LibreOffice Calc

Several of the balance figures was selected, revealing how the value us calculated in the formula bar:

Amortization schedule, cell calculation revealed

I chose to modify the table, by adding a value of 1000 in the “Extra Principle Payment”, to change the values of “New Balance” …

… and then I changed the value to 500 to see how it affected the values of “New Balance”.

Again I leave it to the reader to further explore mounting spreadsheets of their own using their own data.

Slide Shows / Presentations

At the opendesktop.org collection of templates, I chose a slide show template to download:

opendesktop.org page sorting for a presentation template

I chose a template to download …

… and downloaded it:

Again through the files directory, I double-clicked on the downloaded file:

File in download directory double clicked

… which opened up the file in LibreOffice Impress:

Presentation opened in LibreOffice Impress

I began editing the title line — in the process, using the wrong branding for this series!

The text colour, white, didn’t have enough contrast for my taste, so I selected the text …

… and went into the options area on the right to by clicking on the letter “A” with a red underline, to change the font colour:

Text colour changed through menu icons on the right

The font colour was changed to a greenish-blue colour:

Other text was changed and added:

I changed to the second page, and similarly started to change the text:

Text can be changed as per your needs, as well as pages added through copy / paste or other wizards available.

The drop-down file menu was chosen, so that I could save the file:

Once the file was saved, I opened up the drop-down file menu again, and chose “Export As” so that I could export the file as a PDF. (Editorial note: As mentioned earlier, while there is a good amount of compatibility between LibreOffice and other office suites, it can be disappointingly incomplete, which I have particularly seen and experienced with — but not only — slide shows. For more of a discussion of such from the perspective of the usefulness of PDFs, please see my post on the subject.)

The file drop-down menu was clicked again, and the option “Export As” was clicked:

File menu opened to export the file as a PDF

Exporting to PDFs can be rather easy and direct, or, as I am going to show a little bit here, allows for a large amount of choices …

… including protecting PDFs with passwords for opening:

Tab with options for password setting for opening PDFs

Passwords were set for both opening as well as for “permission” which means to allow editing of the PDF (see my post on the subject), and the slide show was exported as a PDF:

… and the OK button was clicked:

As usual, I leave to the reader to explore further. Also, within LibreOffice itself it has a wizard to help the user create a number of presentations with various backgrounds and layouts.

Database:

LibreOffice also includes a database module, called “Base”, which is similar to Microsoft Access; it is essentially a front end manager — a gui interface — for the actual database software behind it that it leverages.

Before I show a properly mounted database, I will show some screenshots about how to start.

Starting from the home screen, the activities corner (hot corner) in the upper left was clicked:

On the Activies screen, “libreoffice base” was typed into the search bar, and the option to install LibreOffice Base, which is not always installed in a base install, was offered:

Activities screen accessed, and “libreoffice base” searched for; the option to install Base was offered

The option was double-clicked, which brought up the “software store” with the choice of LibreOffice Base …

Software store opened to allow for installation of Base

I double-clicked on the option, bringing up the information page on the package and the offer to install it:

I clicked the “Install” button:

Once LibreOffice Base was installed, an “Open” button presented itself:

The “Open” button was clicked, lauching LibreOffice:

A wizard came up to select a database:

Wizard opened to allow choice to launch Base

The presented option was accepted, and the “Next>” button was clicked, bringing up a “Save and proceed” window:

The “Finish” button was clicked, opening a Save window:

Finish button clicked, allowing for the creation of a database

Once that was done, the following screen came up, in order to start creating a database:

Note that from this point on, I am showing some very basic things, and I will soon recommend a tutorial, which will better show how to use the software than I could ever present.

I clicked on the “Table” icon, which brought up a Table Wizard:

I chose the “Personal” category, on the premise — in the context of this post, anyway which presumes that many readers may be seeking to use linux at home and not just at the office, and that a database might not as easily appear to be a personal piece of software.

I pulled down the suggested list of topics:

… and chose “Recipes” for what I presume are obvious reasons — we all eat, and presumably many people have a personal collection of varying sizes (here’s my collection of recipes, incidentally NOT in a database format, at https://www.malak.ca/food).

Some field names were suggested:

I clicked on “Name”:

… which moved it over to the column on the right:

I also chose other sample tables:

… at which point, I clicked on the “Finish” button, leading to the following screen:

Finish button clicked, leading to a data entry page

I started entering data:

I chose to save my changes:

At this point, I am going to direct you to a far better tutorial than I could ever present, even in the most cursory of fashions:

As of the writing of this post, a rather complete tutorial on using Base can be found at thefrugalcomputerguy.com/seriespg.php?ser=15/ (no doubt amongst countless other similarly excellent resources):

TheFrugalComputerGuy.com LibreOffice Base tutorial page

Although I think it best to leave the tutorial to TheFrugalComputerGuy, I will show a small database in action:

Starting again at the desktop screen:

The activities screen was accessed through the upper left hand hot corner with the mouse:

The Firefox icon (orange, on the left on the dock at the bottom) was clicked:

I went to my favourite search engine, duckduckgo.com:

Search engine opened (in this case www.duckduckgo.com)

… and I searched for “libreoffice base templates”:

I chose the “Templates & Extensions” link, the second link above, at the LibreOffice.org site itself:

I clicked on the green “plus” sign to the right of “Boost your creativity with templates”:

… which led to the following page:

On the left, there are a number of filters under “Add tag filters:”, and clicked on “Base”, bringing up the following page:

I chose the “MyRecipes” template for LibreOffice Base:

I scrolled down to quickly assess the files, finding them eminently interesting for the task at hand:

The download button was clicked, and the file downloaded:

The files program was opened, and the newly downloaded file was highlighted:

The .zip file was double-clicked, creating a directory of the files (ok I accidentally created the directory three times!)

One of the directories was double-clicked and opened:

The “ReadMe.txt” file was double-clicked and opened:

The .odt file was opened as well:

Instructions and general description file checked

The “MyRecipes1.jpg” file was double-clicked, opening a screenshot:

Screenshot of database operating consulted

The FoodPix directory was opened, showing pictures of the recipes in the database:

From the database’s main directory, the database was opened:

After looking about, the “UpdateRecipes” option was selected:

Which opened up one of the recipes:

The database author chose to have an active Pantry list with checkable items, no doubt based at least partly on their recipes; by having it dynamic, when asked to create purchasing lists, the database can exclude pantry items already on hand:

Said shopping lists can be generated from the “1MainMenuSwitchboard” option:

Main menu switchboard created by the author to navigate through their recipes and other functions they programmed

Given that the “switchboard” is based on macros, the Tools pull down menu was opened::

… and the “Options” option was clicked:

“Options” option clicked, opening an options window

The Security option was chosen:

… and the “Macro Security” button was clicked. The security level was set to low, as per the author’s suggestion:

Back to the Switchboard:

The “Mark Recipe List” button was clicked, and I decided to mark three of the recipes:

In trying to close the window, a window asked if I wanted to save my changes, to which I clicked “yes”.

The “Grocery List for Marked Recipes” button was clicked:

Grocery list option chosen from main menu

… producing a grocery list based on the recipes, which was automatically opened in LibreOffice Writer:

Grocery list created for the selected recipes

The next chapter will look at graphics.

October 18, 2024October 18, 2024

Desktop Linux: Unveiled Chapter 6: Upgrading the Operating System

Previous Chapter: Desktop Linux: Unveiled Chapter 5: Gnome Extensions, and Basic File Management

Note: Although it has been a while between posts and I had planned on another subject for what would have been this post, given the time lapse I decided to take advantage of a new version of Fedora that had been released to show how to easily upgrade the OS version, in this case, from version 39 to version 40. Note that many different versions of linux (Ubuntu, Mint, Debian, etc.) have similar functions and upgrade paths; since I began using the automatic upgrade tool in Fedora in about 2018, I have had good experiences.

Firstly, the “Activities” screen happened to open when I logged into the system, and I chose the software icon in the dock on the bottom (the white “shopping bag” with the red, black, and blue symbols):

Which brought up the following screen, telling me that there were general updates, and that a new version of Fedora was available:

The system updates were first chosen and downloaded:

Once the updates were downloaded, the system was ready to be rebooted for installation:

The “Restart & Install” button was chosen to confirm the reboot:

Restart and install updates dialog box opened

The system rebooted:

… and updates were installed:

Once the updates were installed, the system rebooted:

System rebooted after installation of updates

… leading to the login screen:

… where I entered my password:

Once logged in, I clicked on the software icon again in the dock, and chose to download the upgrades for Fedora 40:

Software store opened again, and upgrade packages downloaded (2%)

Once the upgrade packages were downloaded, the “Restart & Upgrade” button was pressed:

All packages downloaded, and Restart and Upgrade button pressed

… which required authentication, so my password was entered:

Authentication required for the major changes

The system asked again if I wanted to restart and Install the upgrade:

Confirmation requested to restart and upgrade the system

The “Restart & Install Upgrade” button was pressed:

Once the upgrade was complete, the computer rebooted:

The login screen came up again:

And again I provided my password:

Once logged in, new artwork for the new version came up, as well as a notification that the system had been upgraded to the new version (in this case, Fedora v.40):

Just to finish off some checks, the menu at the power button was opened, in order to open the settings screen, accessible from the little gear second from the left on top:

The settings were opened:

I noticed that the name of my computer was curiously changed back to “Fedora” in the upgrade:

System renamed after curious change by upgrade

Then I chose the “System Details”, showing that the system had indeed been updated to version 40:

Confirmation that the system had been upgraded to Fedora 40

Next chapter: Using common pieces of desktop software

October 8, 2024January 5, 2025

AI Generated Podcast About my Yoghurt Muffins Post

Note: I suggest that you read my recent post about making yoghurt muffins first for context before reading this post.

This past weekend, my brother decided to play around with the Google NotebookLM podcast generator, using my recent post about making yoghurt muffins as the podcast topic source material.

Here are the results: “Podcast 1“, the first one I listened to and chuckled at throughout (see below), and “Podcast 2“, which is longer than the first, and a slightly different approach (again, see below).

As a reference, according to Wikipedia (here’s my archive), NotebookLM is a tool by Google that has an “audio summary” feature has the “ability to condense complex documents into engaging podcasts”. As referenced in the article, some of the generated podcasts have indeed been making the rounds on at least the media local to me; the samples played on the radio had the “voices” of two artificial “hosts”, one male and one female, and appeared to greatly impress the real radio host. The real human host on the radio then proceeded to create their own samples with the tool using local news items as source material, resulting in stunningly … seemingly accurate (or at least faithful to the source material) content and banter between the two artificial “hosts”. The voices — and banter — of the artificial “hosts” that were created sounded so real that the “hosts” did not sound obviously artificial in almost any, let alone many, of the usual ways that usually betray the artificiality or synthetic nature of the voices. “They” seemed to bypass the Uncanny Valley (here’s my archive) as well, if only because they weren’t associated with artificially-created “speaking” faces or other cues that might suggest that “they” were artificial.

To wit: My brother came up with two podcasts: Podcast1, and Podcast2, based on the blog page about the yoghurt muffins: The first podcast was roughly what I would have expected, based on the samples I’d heard on the radio, in the form of “entertaining” banter from the artificial “hosts” about the overall post and subject, while the second podcast followed a play-by-play style review of the post and its pictures.

Especially while listening to the first, I was often incredulously guffawing at how “seriously” they seemed to be taking the subject, to the point of “their” calling me a perfectionist; despite, uhm, seriously having approached mounting the post with its pictures and processing the photos for presentation, as well as of course maintaining my recipe archive, and again of course being fairly serious on a hobby level about my cooking, for the overall cooking project I have always had a certain laid back, “enjoying the fun” pleasure to mounting the posts. Which, I must admit, intentionally include a lot of photos detailing usually every last step and even micro-step. I would estimate that the “hosts” got it better in the second podcast by calling me meticulous.

The end result of the two podcasts is so good that except for the knowledge that it’s totally AI generated, I would actually believe that the podcast was hosted by real people and put together by real people providing real feedback. As such, I have a few responses to some of the “comments” that the “hosts” made:

Shorter Podcast: (audio here)

I am flattered in a giggly kind of way that the “hosts” underlined the dirty oven window, which I myself had somewhat sheepishly admitted was the case in the original post;
The “hosts” seem to enthusiastically say it’s like a scientific document with no room for error; I would challenge anyone to compare the blog post against the recipe and say that the two are identical. 🙂
For the record: I did not lick the spoon. 🙂
The “hosts” spoke of how much care I took by freezing them … well, I will go into the “easy” column and say both that baking a half batch or a double batch is roughly as easy as a standard batch, and, that I often try to make recipes that are good for the freezer!
And finally … the “hosts”, in a tongue-in-cheek fashion, pretty much suggested that I make a blog post on making the morning coffee, ~~which I may just do sometimes in the future~~ which I actually have done. 🙂

Longer Podcast: (audio here)

The “hosts” asked what does “easy” mean in my claim that the muffins are easy to make, such as is it the number of ingredients, the technique, or the cleanup? “They” initially conclude “Let’s find out!” “They” then go on to point out the use of the paper liners, and the reuse of the measuring cup used to measure out the yoghurt to then measure out the oil without cleaning it in between, as examples of the “easy” part.
The “hosts” seem to insinuate at a couple of points that the amounts of sugar and oil used are “generous”, while of course continuing to state that the muffins’ crumb would no doubt be rather moist as a result; yet, when discussing the presence of the yoghurt, the “hosts” wondered whether the yoghurt muffins were just an alternative to the bran muffins I make for my mom, but ultimately seemed to decide that it was obviously a “health angle”. I perceived this as a lack of continuity in the “creation” of the podcast. And to be clear, having adopted this recipe was simply meant to be an alternative to the bran muffins I give to my mom, which is clearly stated at the beginning of the post; further, I am not trying to “match” the sweetness of bran muffins.
The “hosts” say that the kind of yoghurt I use is not identified, ie. firm yoghurt, stirred yoghurt, or greek yoghurt, etc.; “they” are correct that the tub does not say so, at least in the view in the picture. However, “they” do read into it by saying that this lack of information is part of the “easy” claim by letting people trying the recipe to use what they have on hand. Also, “they” did not pick up on the strawberry on the tub as an example of how the “relatively plain” was intentionally a loose interpretation.
The “hosts” say that the kind of oil I used was not identified; again, the photo of the jug plainly says “vegetable oil”, which should tell all bakers that it’s generic vegetable-based cooking oil.

Is this a fun tool? Sure. My brother and I have bandied about ideas — purely in the hypothetical — about using the tool to create large numbers of podcasts that could then be syndicated to AM radio stations for the overnight slot during which a lot of content is often recycled or of what we consider to be of dubious interest.

February 26, 2024March 18, 2024

Desktop Linux: Unveiled Chapter 3: Preparing to Install Linux

Desktop Linux: Unveiled is a series of posts that show how to start using Linux.

Previous Chapter: Desktop Linux: Unveiled Chapter 2: Common Linux Distributions

In this post, acquiring a computer on which to install Linux, as well as downloading and writing a Linux distribution on a USB stick, will be shown. Fedora Desktop Edition will be used as an example, although at this point, setting up the installation USB stick can be done with any other distribution — which is most of the common ones — that allows for such an installation.

(Note for future reference, graphical installation with other distributions will be similar, but each may have some nuances and differences between them.)

Hardware — the computer on which Linux is to be installed

First, I recommend that as a newcomer, whichever linux you decide to install, that you decide to do the installation on a separate computer, such as an old computer, on its own. By doing this, you will not reduce space on the hard drive / SSD on which your current OS is installed, especially in taking account the space for data you may to transfer over to the Linux system, nor will you have to deal with the intricacies and occasional perils of dual booting or data loss on your current computer setup, nor will you have deal with the myriad and occasionally confusing issues that may surround virtualisation. Finally, by having a separate computer to “play” with, you will be able to start over again in the event that something goes wrong, or if you decide that you’d like to try a different Linux distribution.

The current (2024) webserver for www.malak.ca

The above photo is taken from a page from a recent (February 2024) presentation the author made about their web server, which hosts https://www.malak.ca (the website hosting this blog), using an old computer with a BIOS creation date of 2008.

Acquiring a computer:

“Old” computers are not unusually difficult to acquire; you may already possess one in storage.

Use an old computer you may be wishing to replace, or already be in the process of replacing, or even a several years-disused computer of which you may not yet have disposed;
Buy, or barter for, a used computer from family or friends;
Buy a used computer from a local computer repair person, who may have a storefront and may sell refurbished computers;
Speak with your employer; depending on their policies, they may be willing to sell you older equipment of which they would like to divest themself(ves);
Check reputable online markets;
Buy a new dedicated computer (only recommended once you become convinced of the cost/benefit regime).

Check the “minimum requirements” page of the distribution you choose; my current bare minimum specs are a Core 2 Duo 64bit processor, 4GB memory, 40GB hard drive (the current, as of late 2023, Fedora Workstation recommendation), and a spare USB 2.0 port (such as after other common USB peripherals you may be using, like a mouse and keyboard), in order to use the installation USB stick (which will be shown lower down in this post). (As desired or required, don’t forget to get a used screen.)

For the purposes of introduction to, and the exploration of, Linux, the old mechanical hard drive with such an old computer is likely adequate; however, SSD cards and extra memory will dramatically increase performance of older equipment. Further, as of posting, SSD cards in the 250GB range are typically very affordable to either add on later, or purchase for immediate use including installation of the system, while memory cards appropriate to the motherboard are usually readily available and inexpensively as per the above list regarding sourcing an old computer.

Downloading and creating a USB installation stick:

A USB stick is required for this step; Fedora’s installation image as of version 39 in late 2023 is approximately 2GB; hence a 4GB USB stick would be recommended going forward.

I am recommending the use of Fedora Media Writer to create the installation media, which can be run on Windows or Mac (as well as Linux, of course!) Should you choose another distribution, you can use a downloaded image from another distribution’s download page (see Desktop Linux: Unveiled Chapter 2: Common Linux Distributions for a few suggestions of other distributions; see below regarding choosing other Fedora desktops, or creating installation media of another distribution).

(Note that the following screenshots may have been created out of order, however are presented in the order required for the narrative.)

To get the Fedora Media Writer, visit https://getfedora.org (I start off using screenshots from Windows):

Click on the circle indicating the latest release (in the shot above, 39), which will bring you to the following screen.

On this screen, click on “Download Now”; don’t worry, you aren’t committing yet.

On the following page, click on the green download button for Fedora Media Writer, either for Windows or for Mac:

A licence agreement window will pop up. This is for the Gnu Public Licence version 2, the licence under which the Fedora Media Writer is licensed. Click on “I agree”.

The next screen will ask where to install Fedora Media Writer on your computer, and it will suggest a location to install it on your hard drive. Click “Install”:

Once Fedora Media Writer is installed, click on “Next”:

… and click on “Finish”:

Launch Fedora Media Writer:

You may be asked to allow the app to make changes to your device. Click “Yes”.

At this point, you can either choose to have the Fedora Media Writer download Fedora automatically, or, you can download a distribution of your choice, and ask Fedora Media Writer to use that distribution instead (the “Select .iso file” option):

Going with the “Download automatically” option above, which by default chooses a Fedora distribution, on the next page (below), choose “Official Editions”:

Should you wish to try another desktop instead of the standard Gnome Desktop in Fedora Workstation Edition, you can choose the “Spins” option above, which will list the following drop-down menu:

Under the choice taken, the next screen is the “Write Options” for the USB stick, which at this point should be inserted in a USB port. Choose the latest version of Fedora (in this case, 39), the hardware architecture, and the USB stick to which you wish to write the installation media:

Click “Write” in the above screen, and Fedora Media Writer will begin writing to the USB stick:

The screen will automatically change to indicate that the written data is being checked:

Once finished, you can click on “Finish”.

Should you wish to try out Fedora without installing it on your computer first, you can follow the instructions on the screen to restart the computer and try a live, temporary version of Fedora. This will not affect your hard drive in the least, unless you choose to install … which I am not recommending, since I am recommending that you install on a completely separate computer (see beginning section).

Next Chapter

Chapter 4 will show the installation of Fedora Workstation.

February 14, 2024February 26, 2024

Desktop Linux: Unveiled Chapter 2: Common Linux Distributions

Desktop Linux: Unveiled is a series of posts that show how to start using Linux.

Previous chapter: Desktop Linux: Unveiled Chapter 1: What is Linux?

In this post, a few of the more well known linux distributions and desktop environments will be showcased.

Note: Clicking on the various desktops will show larger versions.

Fedora

Fedora Linux is a general-purpose linux distribution focusing on free software (ie. not containing any proprietary software) and on being on the leading edge of free software development. It can be used by all desktop users. While having many tools that developers find useful, it is can also be used as a general purpose computer desktop.

Fedora provides a variety of desktop environments; the Gnome desktop environment is the default desktop environment, although other desktop environments are available in Fedora’s various spins, which cater to varying visual aesthetics, technical requirements, and useability.

Fedora Linux can be downloaded from https://getfedora.org (note: do not add “www”, it will lead to an error page)

Debian

Debian GNU/Linux is a general purpose Linux distribution aiming to be available on a large variety of computer architectures, built on free software, and is known for its stability. The large number of software packages available under Debian and its stability are often highlighted as some of its strengths. Debian is used for a wide variety of purposes including desktops and servers, and is equally capable in both functions. Debian is often used as a base for other Linux Distributions.

Debian can be downloaded from https://www.debian.org/distrib/

Ubuntu

Ubuntu is a popular Linux distribution based on Debian. It releases “Long Term Support versions every two years which typically are supported for at least five years, as well as intermediary releases usually every nine months. Ubuntu is often found not to be too difficult to learn to use.

Ubuntu can be downloaded from https://ubuntu.com/desktop (note: adding “www” optional)

Linux Mint

Linux Mint is based on Ubuntu, and is known for its desktop named “Cinnamon”, which was originally based on the Gnome Desktop, but was branched off into its own desktop environment which focuses on a more traditional computer desktop appearance and functionality.

Linux Mint can be downloaded from https://www.linuxmint.com/download_all.php

openSUSE

openSUSE is the community version of SUSE Linux, a business and server oriented version of Linux. openSUSE is known for its use of the KDE desktop, but also uses the Gnome desktop.

openSUSE Tumbleweed is a version which updates continuously and does not require reinstallation after a certain period of time; however, it may prove more challenging to newer users, who might find openSUSE Leap more stable.

openSUSE Tumbleweed using the KDE Desktop

openSUSE Tumbleweed and openSUSE Leap can be downloaded from https://www.opensuse.org

Other Linux Distributions

More Linux distributions, with reviews and description, can be found at https://www.distrowatch.com

Next Chapter

Desktop Linux: Unveiled Chapter 3 will show some steps to prepare to install Linux.

February 11, 2024February 14, 2024

Desktop Linux: Unveiled Chapter 1: What is Linux?

Desktop Linux: Unveiled is a series of posts that show how to start using Linux.

In this post, Linux will be briefly explained and briefly compared to other common desktop computer operating systems.

First, what is an operating system?

An operating system (OS) is the software that makes a computer run, like Microsoft Windows, or MacOS. It is typically able to provide a way for users to operate the computer, and translate the instructions so the computer can run them. It also coordinates all the computer’s resources such as its CPU (central processing unit), memory, hard drive, and other components of the computer, as well as coordinate the user’s programs and data.

What is Linux?

Most people understand “Linux” to be a complete operating system like Windows or MacOS. However, strictly speaking, “Linux” is in fact just a part of the operating system, the central part called the kernel. Common usage has had “Linux” to informally refer to the whole operating system.

“Distributions”, (usually) complete and integrated collections of software built around the Linux kernel, can be legally built and distributed by anyone with the abilities and inclination because of the way the Linux kernel and the other software usually used with it are licensed, although most people choose to use an established distribution.

Distributions vs. Operating Systems

Linux distributions usually contain full linux-based operating systems, as well as extra software often not traditionally included in operating systems, such as office suites, media players, graphic design software, educational software, games, various apps, as well as other software such as server software. Although not all of the software is installed at the same time, they are typically all easily available in central locations called “repositories”, similar to app stores on MacOS and Windows; much is available free of charge, too!

Free Software vs. Proprietary Software

A lot of software available under Linux — and a growing amount under Windows and MacOS as well — is called Free Software, or sometimes Open Source Software. As a contrast, a substantial amount of Windows and MacOS software is called Proprietary Software.

Many people hear the expression “Free Software” and assume that it means that it is free of monetary charge. Some may even question its quality on the basis of such a lack of price.

Although free software is often (though not always) given away free of charge, and most common free software is of very high quality, the expression “Free Software” in fact refers to “freedom”, specifically various freedoms granted to the users of the software. These freedoms include the freedom to run the software for whatever purpose you wish, the freedom to study how the program works as well as make any changes that you wish, the freedom to share the software with others, and the freedom to share software you’ve modified with others.

Some of these freedoms require that the source code, or “recipes” that people can read and understand, be available to anyone and everyone.

The various licences used to allow this often tend to foster cooperation between various parties, often allowing groups who might sometimes be competitors to also cooperate with each other, creating common software that each group can then package together to present according to their own vision. Within this cooperation, software sometimes is developed quickly, and often many programming bugs are found and corrected quickly.

Some common free software licences are the GPL and the LGPL, which specifically give the recipient of the software the above freedoms, and require the sharing of the source code to the software, and any changes you may have made to it, when distributing the software. Other common free software licences are the BSD licence, the MIT licence, and the Apache licence, which have very few requirements but which permit users to use, modify, and distribute the software, while retaining copyright and some disclaimers notices.

In contrast, proprietary software is usually controlled by very restrictive licenses that keep the source code hidden, doesn’t allow users to distribute the software to whomever they please, doesn’t allow users to modify it or fix bugs even if they are able to were they to have access to the source code, and may even dictate how the software may or may not be used.

Next Chapter

Chapter 2 will list some popular Linux distributions that people use on their computers.

December 11, 2023December 12, 2023

Updating a (very small) fleet of computers to Fedora 39

I have been using Fedora Linux since 2008. I would update by re-installation my computers regularly to new versions after end-of-life. Complete, manual re-installs ended in 2018 or 2019 when I started using Fedora’s command line upgrade feature after having observed it in action. Throughout it all, I have sometimes experienced technology change adventures along the way.

I have five active computers, all which were ready to update to Fedora 39 in November, 2023: Three were running on Fedora 37, and two were running Fedora 38. Normally, I try to keep to the same version of Fedora on my fleet of computers — although I will format with the current version of Fedora mid-stream when I format a new or a new to me computer, or a new hard drive or ssd, and try to use a version (that of the majority of computers) until end-of-life, usually roughly 12 to 13 months. I settled on odd numbered versions several years ago, on Fedora 15, by happenstance, and a desire not to be reformatting different computers every six months depending on when their end of life fell.

As such, I proceeded to upgrade my computers.

Since the recommended method of update for Fedora is by the command line DNF upgrade command (here’s my archive), or to use the graphical method in the “Software” “App Store”, I proceeded to upgrade my machines on the command line.

(Note: Some of the screenshots and photos used in this post were created during the various upgrades, while some were re-created ex post facto for the sake of mounting this narrative.)

Webserver: Fedora 37, Workstation Edition, Legacy BIOS (Dell Vostro 420 Series)

First, I updated my home web server using the above-cited DNF upgrade commands (as root; see further down in this post) :

dnf upgrade --refresh
dnf system-upgrade download --releasever=39
dnf system-upgrade reboot

Note that the upgrade plugin was already present on the server, hence my having omitted the step of installing the plugin. Important note, minor in my head although critical to my experience, is that my webserver uses the Workstation Edition, not the Server edition.

All went smoothly, with one small quirk: After the upgrade and later that evening while at a restaurant, I wanted to check my website for something, and it was down. I thought little of it beyond the frustration in the moment. When I got home, I let my brother know in the hopes he might help … but in the process, I saw that the machine’s light in the power button was amber, and I had an idea that there was a software power management issue. I pressed the button, and the machine popped to life; I then went into the power management part of the settings in the gnome settings, and found the “automatic suspend” setting had been turned on to “when idle”.

This was odd. This was an established system I originally installed back in April, 2021, when I upgraded the machine’s mechanical hard drive to an SSD. To be clear, powersaving on idle was *not* a previous setting (ie. the server was always to be on to be a 24/7 webserver, the machine’s only active function, besides its passive function as a backup server), and it appears to have been a change in default settings somewhere around Fedora 38; it appears to be a power saving policy (here’s my archive).

VPN Server: Fedora 38, Server Edition, Legacy BIOS (HP Compaq dc7700 Small Form Factor)

My next upgrade was also fairly simple and straightforward. It was on a machine I found in a building slated for demolition in about 2016, and is a P4-3.4GHz single core machine, which I had been using as a world community grid node for years, but which had been inactive for months, after there having been little work for it for months when WCG moved from IBM to the University of Toronto. (I also suspect that the UofT may have decided to shift most of its tasks to GPUs, which I don’t think the machine possesses, and in any case I did not properly research let alone confirm this, beyond the apparent lack of work units being sent to it.)

A problem I’d been having for years with this machine was that it would not reboot without manual intervention, apparently due to a time error; this suggested a dead bios battery. I tolerated this for years, but this summer I finally installed a new battery in the machine, resolving the issue.

I reformatted the machine with Fedora 38 Server Edition given its age and lack of memory, and I renamed the machine, having some misgivings about its former name. I offered its use to my brother, who uses it as a VPN server for the household here, particularly to simplify assisting our mother in her computer use. I generally leave the machine alone: VPNs are a nebulous thing I don’t understand very much at all; I understand SSH filesystem tunnelling, and the parts between that and VPNs are too nebulous for me to understand.

But to wit: Up to this point I was neglecting the machine, letting my brother deal with it, but as a result the machine would often go unupdated for weeks at a time. In mentioning that I’d embarked upon the process of upgrading my computers all to Fedora 39, I mentioned that I liked to keep my fleet of computers all aligned on the same version of Fedora; I mentioned that at that time, due to new installs, I had two out of five computers on Fedora 38, while the rest were still on Fedora 37. With the comment that I wanted to keep my fleet on the same version, my brother encouraged me to maintain responsibilities for updates and yes indeed to upgrade this machine in particular, to keep it in line with the rest of my computers.

As mentioned, the upgrade went smoothly and with one exception was rather unremarkable: The suspend on idle mentioned earlier was not invoked, which I learned while researching the issue above is a feature not invoked in the Fedora Server Edition (here’s my archive).

Dell XPS 13 Laptop: Fedora 37, Workstation Edition, UEFI

Next, I updated my Dell XPS 13 (note: 2021). Again, this was an easy process with the dnf upgrade command.

One of the items to do in a couple of lists to do after installing Fedora 39, “17 Things to Do After Installing Fedora 39” (here’s my archive) and “Things to do after installing Fedora 39 Workstation” (here’s my archive) was to do firmware updates, using the following commands:

sudo fwupdmgr refresh –force
sudo fwupdmgr get-updates
sudo fwupdmgr update

Which, of course, I did. (There were indeed some firmware updates to be installed.)

Here’s what the process looks like on my XPS13 (Screenshots and photos taken after the fact, on a subsequent series of firmware updates):

Firmware updates a few weeks after upgrade

At this point, I was invigorated by being able to perform firmware updates on my XPS 13 laptop (which admittedly had not been the first time I had done so under linux, but no matter.)

However, a couple of weeks later, I noticed that an extension wasn’t working: My XP13 has a touchscreen display, and Gnome has an onscreen keyboard that pops up contextually when text is to be entered, occupying a major amount of screen space; I had been using the “disable-touch-osk” extension by sulincix, which stopped working with the upgrade to Fedora 39.

On screen keyboard disabling extension not working

This leads to a gripe I have for the Gnome developers: Stop breaking extensions with each new version of Gnome, or provide *some* kind of stable API or environment or whatever is needed so that the extension developers don’t decide to abandon their extensions because Gnome keeps on shifting so much that they have to work excessively hard every six months just to maintain their extension.

This led to the next two computers I have, which are a 2015 Acer laptop, and a 2014 Dell Inspiron desktop.

Acer Laptop: Fedora 37, Workstation Edition, UEFI — but using Legacy BIOS

I have been having problems using UEFI in my Acer laptop since I received it new in 2015; the Fedora live media would boot up, and I could install Fedora under UEFI; however, it would never boot up afterwards. My only solution seemed to be to use legacy bios. Nonetheless, hope springs eternal, this was the time to try again to install under UEFI.

I should note at this point, as mentioned above, that my home server (2008) and my VPN server (2007) are both rather old computers and pre-date UEFI and use legacy BIOS, while my XPS 13, Acer laptop, and Dell Inspiron desktop, are all UEFI machines. I make these distinctions because of conversations I had in which on the one hand, it was suggested that I perform a baremetal reformat of the Acer laptop in order to sidestep a problem I had been experiencing when I’d allowed the battery to drain completely, forcing a reset to defaults in the BIOS and hence to UEFI boot, making my setup with legacy-BIOS unbootable; on the other hand, I concluded “It’s 2023; it’s absurd not to be using UEFI on UEFI machines.” (Of course, the use of older, legacy machines predating UEFI are a different issue altogether, and for them, said point is moot.)

In addition to this comment about using UEFI, and the potential to have any UEFI firmware upgrades as discussed above, I decided that my Acer laptop needed to receive a baremetal format, given the accumulation of a lot of software on the system that I didn’t use (many though hardly all installed because of a presentation I gave in 2021); I decided that instead of package hunting and manually uninstalling them all — including dependencies that decide not to uninstall — it seemed more efficient and effective to do a clean install.

Fast forward to this round of upgrades, I upgraded the installation using a downloaded Fedora 39 image, and I went through various upgrades and setups, such as Gnome extensions, and some software installations. Suddenly I remembered that I had not changed the boot sequence from legacy bios to UEFI, so … I started over.

Several installation attempts later, including trying Fedora 36 (with an intention of upgrading through to version 39) based on some advice playing around with the various BIOS settings trying to get just “the right” settings, none worked, and I finally resigned to reinstalling yet again under, and continuing to use, legacy BIOS. Sigh.

Setting the Boot sequence to Legacy BIOS

Before setting up in legacy mode, I had a flash of inspiration: Since I was nonetheless able to boot the live media under UEFI (which I knew wouldn’t otherwise be used afterwards), I attempted a firmware update as per the above. To my mild disappointment, there weren’t any firmware updates for my Acer Laptop:

I continued with the installation under Legacy BIOS mode, and set up the desktop with the various Gnome Extensions, installing software not in the base installation, and customizing settings and the like.

I once again faced a few pet peeves I have about how Fedora is set up (incidentally through Anaconda, but by itself not Anaconda issues, best I can tell):

A long time ago, for Fedora 21 at the latest, Fedora stopped listing my home city of Montreal in Anaconda. Sigh. (I think I choose New York, which is in the same time zone.)

Fedora uses sudo by default, which I don’t like: I go by the notion of “Don’t be afraid of root; respect it, but don’t be afraid of it” — when you have to do root-y stuff, log into root, do what you have to do as root, and then sign out of root. (Yes, I am aware of the advantages of sudo, even beyond its convenience and short term elevations of privileges, such as logging of *who* elevated their privileges to do *what*; I just wasn’t taught that way, and on a single user system, I don’t see much value to it; hey maybe that’s just me.) As such, with each new install I perform, I have to, ironically using sudo under my default user account, assign a password to the root account, and then, remove my default account from the wheel group.

First, a password was set for the root user:

Then, after logging into the root account, I edited the /etc/group file (here’s my archive) …

… by removing my user account from the wheel group (highlighted):

The next thing that irked me was that in Fedora Workstation Edition, it seems that Anaconda no longer has an option (read, without the qualifier “it seems”) to set the hostname during the installation. While I understand that it is a trivial enough thing to set as per the following, under the default régime of the default primary user having sudo privileges … it seems to me that this is the kind of thing that should still be in the system installation part. (As in, I wonder how many new users have “fedora” as their machine name for a significant amount of time if not forever, being unaware that it is (only) a default placeholder name, unaware that it can be changed, and unaware of how to change it.)

Fortunately, this is easily set in the Settings / About menu, *if* you don’t remove your default user from the wheel group, or at least haven’t yet, and therefore still have sudo privileges:

Note that in the above screenshot, the option appears shaded out because since I had already removed the primary user from the wheel group, effectively disabling sudo, my (default user) account did not possess the requisite permissions to edit the hostname.

Changing the hostname on the command line is also not particularly difficult, using the command “hostnamectl set-hostname new-name”

… or, editing the /etc/hostname file, by entering the command “nano /etc/hostname” as the at the command line and as the root user:

Then, once in the /etc/hostname file, enter the host name you want (in the case of my Acer laptop, “reliant”, as in the USS Reliant from Star Trek: The Wrath of Khan movie.)

(More on changing the hostname can be found at the Fedora documentation page (here’s my archive) and techadmin.net (here’s my archive), among many other sites)

And on this install, I noticed that the extension Vertical Overview by Ralthuis, which among other things, allowed for the dock on the Activities page to remain vertical and on the left edge of the screen, instead of on the bottom of the screen, was broken, something I hadn’t noticed when upgrading my XPS13. Note: Check lower down in the section for my desktop.

Dock moved to the bottom of the activities screen due to a broken extension (note screenshot recreated after the fact)

On this point, I installed a number of Gnome extensions that I like, unfortunately not the one mentioned above, as well as adding apps to the dock, and other optimizations I commonly perform.

After these items, I installed Gnome Evolution, modified the installation’s setup such as pinning apps to the dock, and checked the power management issue listed above. During the install process, I was able to specify that third party repositories could be enabled; after install, I installed the free and non-free repositories from rpmfusion, as well as Rémi’s RPM repository. I transferred my data from the backup I had created earlier onto my laptop. (See next section on my Desktop).

Finally, I had to activate the flathub repository (here’s my archive) in order to be able to install software that I use that is distributed as flatpaks, such as Signal (a secure texting app):

… and then Signal was installed from the Software App:

Minor note: I don’t recall having to enable the flatpak.org repositories before, although I may be wrong.

This leads to my final computer to upgrade, my desktop:

Dell Inspiron: Fedora 38, Workstation Edition; installed Legacy BIOS, Machine UEFI

When I purchased the computer new in 2014, Fedora 21 installed easily under UEFI.

In the summer of 2023, I upgraded the mechanical drive to an SSD, and I had installed Fedora 38 the SSD; the Dell Inspiron had difficulty recognizing Fedora 38 media, so I took an old pre-UEFI computer, inserted the SSD, and installed Fedora on the SSD. I don’t recall if I knew to change to legacy BIOS once I transferred the SSD to the Dell, or after an error or two, I realized the error, and made the change in the setup. The installation worked, although I was slightly irked.

Come time to upgrade to Fedora 39, I performed the command line DNF upgrade covered earlier, dealing with some of the consequences like the power management and idling issue above. Additionnaly, I noticed something else that irked me regarding the power button (changing it from “Suspend” to “Power Off”:

“Power Button Behavior” setting changed from “Suspend” to “Power Off”. Call me old school …

However, in the intervening time I had experienced the UEFI crisis above, so I first performed a backup of my data to my backup folders on my web server, mildly surprised by how much I was behind in my manual backups.

Unfortunately from this point on, my desktop proved to be the most challenging to upgrade properly.

Having downloaded a copy of the install media for Fedora 39 and burned it onto a usb stick, as well as still having the Fedora 38 Server Edition DVD (which I had forgotten was the F38 Server Edition, instead erroneously assuming that I had gone to the trouble of burning the F39 Workstation Edition onto the DVD), and I tried to install Fedora 39 from both media. I tried several settings in the setup menu, to no avail: The motherboard categorically refused to recognize either, simply displaying an error message vaguely communicating a sense that it didn’t like the media. In looking through the internet for pages on the subject, including the Dell website, I was mildly piqued that solutions commonly referenced burning the usb stick using particular software under Windows (to which strictly speaking I have access, but not on the computer in question), and often just assuming that there would be a Windows partition on the computer. Putting aside knee-jerk reactions, I assumed that this would not address the issue since the solutions appeared to assume a conflict with Windows which could not exist on my machine, or that the Fedora media-writing tools were inherently unable to operate correctly.

I gave up for the moment, changed the boot settings back to Legacy BIOS, and used the untouched Legacy BIOS install for roughly a week while dealing with other upgrades and life in general.

After roughly up to a week, I remembered something I’d read a week or two earlier that said that the UEFI shim for Fedora versions 37 and 38 (and I presume, given my experience, Fedora 39 as well), was not working for some motherboards “due to a difficult certification process for this component“, (here’s my archive) and that a workaround was to install Fedora 36, whose shim was known to work, then proceed through the command line upgrades to Fedora 39.

Fedora 36 was downloaded and burned on a usb stick, and the settings in the boot menu were changed back to UEFI. Fedora 36 was installed — successfully! …

… and the updates were performed, after which the command for the version upgrade was performed, to bring it to Fedora 38. However, the system would not reboot on its own; a quick fsck command corrected some “dirty code”, which it corrected, and I changed some boot settings about booting and automatic on at certain dates. Once this was done, the upgrade to Fedora 38 continued:

DNF upgrade command working; yes, my screen is dusty!

I again performed a dnf upgrade to Fedora 39, and had to repeat the fsck command in order for the system to properly reboot.

To correct this rebooting issue, an empty file named “fsck” was created in my home directory.

Backups were restored, and work similar to what I’d performed on my Acer laptop were performed regarding sudo, root, renaming of the box, evolution, extensions, pinning apps to the dock, and the like were performed.

After yet another week or so, I noticed that my backups had not fully been transferred, and began transferring the balance. In the process, my computer indicated that it did not have enough space on the hard drive; I suspected that during the previous install that I had not correctly removed the previous install, so I reformatted yet again.

So I repeated the installation and upgrade process, this time ensuring that all space on the drive was reclaimed, and repeated the above processes, both specific to the computer as well as other things generally required as part of the upgrade.

During the initial setup, I discovered an extension that brings back the vertical view: V-Shell (vertical workspaces) by GdH, and it seems to do what I want, although on the desktop there is a setting that brings up the (vertical) dock, workspaces, and app search space over the workspace; comparison with another setup allowed me to find the setting I wanted.

And, to repeat myself: Gnome, do you hear me? Stop breaking extensions!

Now — so far — the computer seems to be working, but as this whole process over a month has shown, I should give it at least a week to find out if there are any other issues.

Final Thoughts

I don’t read the upcoming changes for new versions, nor do I research in advance problems that people have been having. I discover the problems, changes, and challenges along the way, and as such for me Fedora reveals itself as per my usage and discoveries — no doubt leaving a lot hidden to me — not only over its roughly 13 month lifespan, but also over the first few weeks of using it, and, interestingly, over the installation process itself, especially when it’s over several machines of different eras and manufacturers and technologies.

As this round of upgrades in particular has shown, as well as years of using Fedora Linux, using Fedora Linux is an exercise in bleeding edge.

Now, barring unforeseen changes, additions, and the like, I’m looking forward to roughly a year of Fedora 39 goodness!

May 28, 2023August 13, 2023

New malak.ca internet connection

www.malak.ca is hosted by myself on an old desktop computer in my bedroom, using my home internet connection. The general specs are:

Dell Vostro 420 Series (64bits) — BIOS date of October 24, 2008
Intel(R) Core(TM) 2 Quad CPU @ 2.66GHz (with hyperthreading), with a clock speed of 333MHz; L1d cache 128KiB (4 instances); L1i cache 128KiB (4 instances); L2 cache 6MiB
8GB (4 x 2GB) memory, clock speed 800MHz
HD: 240GB SSD (OS and blog)
External USB hard drive: 1TB (static website data and other stuff)

Currently, it is running Fedora Linux version 37 Workstation Edition. Using the Server Edition for such a small, home-grown vanity project seemed unnecessary given a comfort level with the Workstation Edition and, since at its core, the two editions are subsets of the same OS. Ultimately, missing packages from one edition compared to the other are a “dnf install” command away. (As for a longer-term distro, I have always been a Red Hat user, so Debian or an Ubuntu LTS release aren’t interesting to me, while the new community respins of RHEL have neither captured my imagination, nor do they hold sufficient appeal anymore on a technical level.) Hence, I started from the Edition with which I and my brother (the technical heavy-lifter) are familiar, which allows for the (admittedly rare) use of a GUI as needed.

The filesystems are with ext4 on the boot partition of the SSD, as well as on the external USB hard drive; I use ext4 because I’m used to it, but can’t truly say I know, or can recommend, one filesystem from or over the next. UPDATE: I checked the filesystems and … the boot partition is ext4, and the SSD’s data portion seems to have defaulted to BTRFS; there you go, proof I don’t know much about the differences between various filesystems and their comparative advantages and disadvantages. 🙂

I have been hosting my personal website at home since at least December 2017 on a few used computers (I think the current computer is at least the fourth since transferring my website from a friend-of-my-brother’s web hosting service):

December 2017: IBM ThinkCentre, circa 2003 era and running CentOS 7.X (retired due to a suspected thermal event)
Sometime after 2017 and until April 2020: A Core 2-duo circa possibly 2010 era, running various current Fedora versions up to version 31 (repurposed due to power issues)
April 2020: IBM ThinkCentre, circa possibly 2006 or 2007 era, running Fedora 31 to Fedora 37 (retired due to unknown problems causing constant reboot cycles, which were not fully investigated)
The current 2008 era computer installed in February 2023: Dell Core 2 Duo, 2008, (described above) using the same SSD and therefore instance of Fedora 37 from the previous IBM ThinkCentre

But to wit, since hosting www.malak.ca myself, it has always been on my home internet service, a DSL line with a (now-)paltry 6.05MBit-ish down and, what, 0.67MBit-ish up capacity, which for reasons beyond the scope of this post had not been upgraded for (best I can remember) over 20 years.

Time marching on and the increase of devices in the household meant that while still minimally usable and just functional, the internet connection regularly became inadequate for daily use, and barely usable for things like weekly simultaneous videoconferences (and with slightly-more-than-tacit rules of “no other internet usage during said weekly dual videoconferences” and the like.) The slow internet access, especially the slow uplink, affected a blogging project started in late 2020 showing pictures of the preparation of my recipes from my collection by limiting photo sizes not only as a good idea for reasons of netiquette, page layout and formatting, but as an outright necessity given the limited upload capacity (thank you WordPress for lazy-loading!)

Well, last week we finally upgraded the internet package to cable with 120MBit down and 20MBit up. Interestingly, we had had a cable modem for a few years in the late 1990’s until it became quite unusable and made a switch to DSL; as a side note, a box, some equipment inside it, and some cable wiring from that period were still attached to the outside of the house, not having been removed at the time, and were still compatible and usable when we got the install last week.

As such, www.malak.ca now has decent upload speeds!

February 26, 2023February 26, 2023

malak.ca hardware upgrade

This is a quick note (mostly to myself) to say that the computer hosting www.malak.ca — the website hosting this blog — has been switched out and replaced.

Last night, I was able to access the site normally and remotely while out to dinner at the home of some friends. This morning, in trying to ssh into the machine to do a routine manual software update, the connection kept timing out and disconnecting. Some quick diagnostics along the lines of “is the machine plugged in?” and a few reboots to watch was what happening — about as much as it would allow me to do, in fact — revealed that for reasons unknown, it was rebooting, going through a grub page, booting up, showing the Fedora logo, and, after the logo disappeared but before the login prompt appeared, a bios message came on the screen indicating a signal loss, and a reboot would begin again.

I tried a few past kernels in the grub menu, including the rescue kernel, and checking the bios, to no avail. Bringing up the text display of what was going on during the bootup was hard to access since I was scratching my head wondering “What’s the keystroke to do that again?”; same for getting the console. No matter, other things needed attending to in the moment, and I moved on.

Fortunately, my brother-in-the-know was coming within the hour, and I sent him some messages about it. He offered to bring an old junk-computer-which-wasn’t-quite-junk-yet I had given to him a while back and which he wasn’t using, at least not yet. After describing the problem to him and offering my rough diagnosis — either there was a corruption somewhere in the software, causing the reboots, or, during the reboots software commands invoke a (presumably faulty due to old age) physical hardware system or circuit, which caused a problem leading to the reboots — both of which, particularly the latter, he thought may have had merit.

My brother brought the old machine. Before installing anything, he first checked the OS SSD from the server (which also contains this blog’s database) in a USB caddy, then he checked the external data drive holding the rest of the static website and my backups, again by USB. Data on both units were in good condition. We finally went straight to replacing the machine by transferring the SSD and external drive to the new old machine, and here I am typing up this memo to myself.

The machine’s specs?

Dell Vostro 420 series; 8.0 GiB; Intel Core2 Quad Q9400 x 4; Mesa Intel G45/G43 (ELK) video card, with lots of USB ports, a networking card, and other things many people including myself take for granted.

And since the 240.1 GB SSD is the drive from the previous machine, it is still running the same instance of Fedora and the LAMP stack with WordPress, suffice it to say that I’m up to Fedora Linux 37 (Workstation Edition) 64-bit on it, and running up to date LAMP and WordPress software.

In fact, as I am finishing up this post, the machine is being updated!

April 5, 2022April 7, 2022

Overview of Open Source / Free Software for PDF files

This post is a translation of and (somewhat of an) adaptation, as well as slight update, of a presentation I gave in November, 2021, at a meeting of my local Linux Meetup. This adaptation includes some extra limited mockups of demonstrations performed live during the presentation.

The presentation was put together using Fedora Workstation (a general purpose version of Linux, in this case specializing in being a desktop workstation), highlighting some software either installed by default, or available in the Fedora Linux and rpmfusion software repositories (“App Stores”). It is therefore not intended to be a complete exposé on all available open source / free software options for PDF, even under Fedora Linux, let alone GNU / Linux in general, or other systems.

It should be noted that the presentation’s original target audience was a French-speaking group of Linux enthusiasts, Linux professionals, and other IT enthusiasts and professionals familiar with Linux. Most of the listed software would typically be available in standard or easily accessible Linux software repositories (“App Stores”). Beyond the world of GNU / Linux, free software is generally available for use on other systems, and, barring instances of a specific given package offered with paid warranty support, are usually also free of charge to download, install, and use.

In the case of the software highlighted in this post, all are either free-of-charge, or represent the free-of-charge version.

The Value of a PDF File

Context / Situation:

Take the case of the exchange of a document between two computers — such as between one running Linux, and another running Windows (or vice-versa) — and each computer is endowed with a different office suite, such as LibreOffice (cross-platform) on one, and Microsoft Office (Windows / Mac) on the other. (Of course, other possibilities exist, such as Calligra Suite (cross-platform), Pages / Numbers / Keynote / etc. (Mac), Corel Wordperfect, Google Docs, etc.)

LibreOffice, and in days gone by, OpenOffice.org, have long been touted as being “compatible” with MS Office; this purported compatibility, however, is disappointingly nowhere near as good as I and many others would like to believe.

As such, each user will open the shared document, which will be displayed according to each suite’s interpretation of the file, and may find that the actual displayed content on their screen could be different — sometimes substantially so — from the intended original display of the document. Text lines may be cut off; fonts may not be available on one or more of the systems, causing font substitution; font sizes may be changed, or text size may be different while substituting a different font due to the lack of the specified font; certain symbols may not be available on some systems; table effects may not work, or objects inserted into tables may not function or be displayed as expected, such as the insertion of a spreadsheet.

Unfortunately, I would estimate that said disappointing lack of “complete and perfect” “drop-in replacement” compatibility is a very common experience in comparing many well-known pieces of proprietary software and their open-source counterparts — not just LibreOffice and MS Office. Personally, as a Linux user, I have experienced this lack of complete compatibility a number of times since beginning to use OpenOffice.org in 2005 and Linux in 2006. Since then, I have also seen the incompatibility in action on a number of occasions during varying presentations under completely unrelated circumstances in which the presentation files were produced in one suite, and attempts made to show them in another were met with varying degrees of disappointment, sometimes leading to complete failure.

Example PDF

The PDF at this link is a somewhat varied although basic document created for this presentation (you will need a PDF viewer); images of the PDF are shown below. It was developed in order to use throughout the presentation as an example PDF to demonstrate the various given points at hand. It should be noted that the PDF was written in French because the presentation’s original target audience was French-speaking.

The following four images are jpeg images of the pages of the PDF document linked to above, and which I created in LibreOffice Presentation. It should be noted that, for the sake of argument, the pages could have been created in another format, such as a word processor, a spreadsheet program, or a drawing program, for instance.

Page 1 — Song lyrics to be displayed for a Karaoke Night

Page 1, the lyrics to a French song, such as one might want to display during a karaoke event among friends

Page 2 — Expenses list for a Luncheon

Page 2, a fictitious list of expenses for a luncheon

Page 3 — TV Listings

Page 3, a fictitious TV listing for an evening, with some Linux in-jokes and some in-jokes specific to the original audience

Page 4 — Flea Market Poster

Page 4, a fictitious flyer for a local flea market

The above document — represented here in jpeg format directly produced from a PDF of the document — was originally prepared in LibreOffice Presentation, and therefore correctly represented the original document.

However, the following four images are jpeg images of the pages of the PDF document I created in Microsoft PowerPoint (you will need a PDF viewer) into which I imported the original LibreOffice Presentation, in order to demonstrate the relative lack of compatibility between, at least in this case, LibreOffice Presentation and Microsoft Powerpoint.

Page 1 — Song lyrics to be displayed for a Karaoke Night

Changes: Text fonts and font sizes, causing text to be cut off the page

Page 1, note the changes in fonts and font sizes

Page 2 — Expenses list for a Luncheon

Changes: Text fonts, and improper translation of symbols

Page 2, note the changes in fonts, font sizes, and improper translation of symbols

Page 3 — TV Listings

Changes: text fonts, font sizes, and lack of background colours in the various cells

Page 3, note the changes in fonts, font sizes, and lack of background colours in the various cells

Page 4 — Flea Market Poster

Changes: Text fonts, font sizes, corrupted translation of spreadsheet table in the centre of the flyer

Page 4, note the changes in fonts, font sizes, and the completely corrupted translation of the spreadsheet table in the centre of the flyer

The value of a PDF:

PDF files are generally well supported across multiple platforms and software, generally regardless of platform, and will usually be displayed in a virtually identical fashion on all systems; in the case of discrepancies, they are usually inconsequential.

However:

There exists a certain perception that, short of having Adobe Acrobat Pro (a commercial, closed source piece software), PDF files are difficult to edit and modify, allowing for a certain view that PDF files are more secure. This is a case of “security by obscurity”, since editing and modification may be performed by many pieces of software, besides but of course including Adobe Acrobat Pro.

PDF files may also benefit from a perception of being less susceptible to viruses and malware, such as through macros. Suspicious files, regardless of format, should always be checked when there is reasonable doubt, particularly under certain environments.

Warning:

Be careful when using some PDF software downloaded from random websites on the internet, or websites which advertise PDF modification: The may add watermarks to the resulting file — this may be undesirable, and embarrassing, particularly if the software, website, or their output aren’t vetted prior to distributing the resulting file.

PDF Software which adds a watermark to edited watermarks when using an unregistered version

Further, websites providing PDF editing services may have very reasonable terms of service for editing your document, limiting their responsibilities toward you. By submitting a document to an external website, it may may not be able to protect personal privacy, nor be able to guarantee to not divulge commercial or industrial secrets or confidential personal information contained in the submitted document: They may become the victim of a hacking, or become the target of legal proceedings, not to mention potential dubious or unscrupulous intentions operators might have to begin with. Or, they may simply be unwilling to formally engage in such responsibilities in the absence of a paid service contract.

Sample from a website listing their conditions of use

This article’s objectives therefore are:

Firstly, presenting the utility of PDF as a useful format for distributing documents to a wide audience, without having to concern oneself with what software individual audience members may or may not have access to, if at all, and regardless of reason(s);
Secondly, presenting safe, free software and open-source software options for using and editing of PDF files;
Thirdly, beyond the general promotion of free and open-source software and PDF editing, this article is not about promoting nor deriding particular OSes or software packages, or strictly speaking their strengths or weaknesses.

As such, if a particular system or software package suits your needs and / or purposes, you should use it.

However, if a given preferred solution is costly software, perhaps your organization (or your family) may find it to be financially worthwhile to only purchase a minimum number of licences and only install it on a minimum number of designated computers, instead of needlessly on every computer in your organization (or family).

A simple cost / benefit analysis would be worthwhile: You should consider whether you wish to pay $5, $10, $15, or more, on a recurring basis (perhaps monthly), per computer on which such software would be installed. The costs, be they one-time costs or recurring, should be considered against how often the software may be used, perhaps in some cases only once or twice monthly — perhaps overall, let alone for each individual instance, depending on your organization’s size, needs, and other considerations. Further, it should be considered what operations are typically executed, especially if they simple operations such as joining multiple PDFs, or extracting a page or two, which can be easily performed by many, using any of a multitude of software packages you can get without cost, as opposed to perhaps more technical tasks which may justify costly specialized software.

Creating PDFs from an established document

To begin with, most software which create documents will have an option in the File menu or elsewhere to Print, or Print to Document, or an Export function, which will offer PDF as a format:

PDF (creation) Options in the “Export as PDF” option in LibreOffice

At the risk of skipping ahead to the PDF splitting section below, note that it is a common option to be able to selectively output some, instead of all, pages to the resulting PDF, thereby avoiding the question of having to later split the PDF to get only the desired page(s).

Overview of PDF Software

Perhaps (or perhaps not) to the surprise of many, there are many software packages and suites which will:

Display PDF files
Combine, divide, and export PDF files, as well as reorder pages within a PDF;
Edit PDF files, such as the overall files and the file metadata, as well as the PDF file content
Import and display PDF files according to particular strengths (The Gimp, Inkscape, e-readers)

Displaying PDF files:

Here are some examples of software which will display PDF files directly:

Evince Document Viewer (Gnome Project)
Okular (KDE Project)
Firefox and Chromium (Web Browsers)
PDFSam (limited free version; there is also a commercial version with more capabilities); a version for Debian derived Linux systems is available on their website

Here is a very short list of software which will open and display PDF files and allow editing, each according to their strengths, but whose primary function is not PDF display:

LibreOffice (Office Suite)
Calligra (Office Suite)
The Gimp (Image Manipulation)
Inkscape (Vector Graphics Editor)

Evince Document Viewer

Chromium (web browser)

Okular

Software to Combine PDF files

A relatively common activity is to combine multiple PDF files into one file — such as, separately scanned pieces of paper, or PDF files produced separately, perhaps by different people.

Here are some examples of software which will combine PDF files:

PDF Mix Tool
PDF Arranger
PDF Mod
PDF Jumbler
PDFedit
PDFTricks
PDFSam
LibreOffice
Calligra Suite
The Gimp

Combining PDF files in PDFArranger

Software to Divide PDF Files / Extract Pages

Another relatively common activity is to divide a PDF File, or extract one or more pages from a PDF file.

Note that if you are the creator of the document, as shown earlier, the software you used to create the document likely allows for you to selectively export individual or multiple pages to PDF in addition to exporting the entire document.

Here are some examples of software which will divide PDF files / extract pages:

PDF Mix Tool
PDF Mod
PDF Jumbler
PDFedit
PDFTricks
PDFSam
LibreOffice — allows to print and / or export one or more pages
Calligra Suite — allows to print and / or export one or more pages
The Gimp — allows to print and / or export one or more pages

Splitting a PDF File with PDFMod

Removing pages from a PDF file using PDFMod

PDF Editing

Here are some examples of software which will edit PDF files to varying degrees:

LibreOffice permits the possibility of creating a hybrid PDF and .odt / .ods file (word processor or spreadsheet files), which will allow for the PDF to be more easily edited by any suite that is able to edit .odt and .ods files; create a document with LibreOffice, and in creating a PDF, choose Export — General — PDF Hybrid (incorporating .odt / .ods file)

Other software to edit existing PDF files:

LibreOffice Draw
The Gimp
Scribus
PDFedit (old, but good)
jPDF Tweak (old, but good)
PDF Mix Tool (Basic functions)
https://itsfoss.com/pdf-editors-linux/
https://alternativeto.net/software/pdf24-creator/?platform=linux
PDFFill (pdffill.com) (Windows)

In my personal experience, PDF editing — and ease of doing so — can vary wildly according to what one wishes to do, as well as wildly according to the nature of the source PDF. I have had excellent experiences editing a PDF created from a CAD software drawing (presumably created using commercial CAD software such as AutoCAD), and whose individual elements could be manipulated in LibreOffice Draw. I have also used LibreOffice Draw to insert text zones, arrows, and scanned signatures into PDFs. Conversely, documents composed primarily of scanned images — including text and forms — may require more image manipulation skills to edit, modify, and manipulate individual and specific elements of the document, depending on your objectives.

What you can do will also be dictated by which software package you choose and its strengths and weaknesses.

For instance, it should be noted that the phrase “Editing a PDF” can be a nebulous thing which can mean many and different things to many and different people. For instance, actually editing document text directly in the PDF may be what one understands and expects, while the strengths of a given piece of software may lay elsewhere.

LibreOffice has some PDF import functions, as well as imperfect document layout functions. Depending on the source PDF document, it can be quite effective at editing text directly.

Note from the closed-source world: I once had an excellent experience with a moderately-difficult-to-edit PDF using Microsoft Word, which included being able to edit the text — and presumably save in MS Word’s native file format.

Importing and editing a PDF in LibreOffice Draw (note the imperfect import):

In the case of my example PDF, LibreOffice Draw allows for some direct editing of the text (Notice the word “MODIFIÉ” with a brick-red text colour replacing some of the text):

Importing and editing a PDF in Scribus, a desktop publishing programme:

The Gimp can insert text zones into a PDF, and which text zones themselves may be edited within The Gimp; however, its strengths lie in dealing with a PDF as an image, and editing image characteristics, while editing the text as one might in a word processor might be more challenging.

Importing a PDF file into The Gimp, image manipulation software:

Adding a text zone to a PDF in The Gimp:

Note the insertion of a text zone under the first line, saying “TEST document”

Exporting Text, Cut & Paste, and .odt File Creating

Depending on the source PDF and its nature, “cut & paste” may work (as opposed to not working at all), and may even “work well”, although this may be wildly variable according to the source PDF document. However, even in the best case, this method will normally only copy the actual text, and some of the images, from your PDF document; it may not usually be particularly useful in actually replicating the PDF document formatting.

As for other document and content formats, such as drawings, pictures, and text rendered into images, other sections of this post should be consulted (ie. using LibreOffice Draw or The Gimp for drawings; optical character reading (OCR), including OCRFeeder, etc.)

In addition to the mention of LibreOffice above, OCRFeeder is software that acts as a front end to optical character recognition software, and is able to import PDF files, and then export in HTML, plain text, OpenDocument (.odt) format, and of course PDF. Again depending on the source file, results may be variable, although the results are usable.

OCRFeeder in action and ready to export a page of the example PDF to ODT format

… and here is an image of the exported .odt file (word processor file) of the page viewed and created in OCRFeeder, then opened in my word processor (LibreOffice):

Ironically, as this case shows, the changes (or lack of adequate recognition and / or translation of the original layout) can be as great or even more as can occur by simply sharing documents between not-fully-compatible-though-similar software suites. However, though far from perfect, it is arguably usable, depending, of course, on how much effort you are willing to devote to replicating the original document layout — and then making your desired changes, and finally creating a new PDF document.

Exporting to other file formats:

As has been (indirectly) demonstrated several times throughout this post, PDF files can be imported into software that isn’t specifically dedicated to PDFs, and then allow for the resulting imported file to be exported into other formats. For example, The Gimp was used to create most of the working images for this post: In the case where PDF files were to be displayed, the PDF files were imported into The Gimp, and then exported in jpeg or png formats. This type of conversion — from PDF to another given format — can often be done by other pieces of software (to varying degrees) according to their strengths or weaknesses.

Photo Editing with PDFs

The Gimp is fully functional image processing software, very similar to — but, unfortunately, not fully compatible with nor a perfect drop-in replacement of — Photoshop. Using The Gimp, you can import a PDF and edit the image(s) directly, or extract photos and other images through a variety of means, such as selecting the area of the photo, copying the selected area, and creating a new document from the clipboard.

Here is a The Gimp having imported a PDF of a photo of myself on a cruise:

PDF of a photo of the author imported into The Gimp

During the live presentation, I gave the hypothetical example — for the sake of levity — of a barber who particularly likes sideburns, and seeing mine in a PDF, decided to clip out one of my sideburns from the photo …

Selecting a region of the photo and creating a new document therefrom

… and then notice on how I was starting to go grey at the time :

The beginnings of some greying in my sideburns

It is taken as an understood that use of The Gimp to manipulate the photo can be continued at this point — such as how my sideburns might look after a colouring, or to compare side-by-side against other people’s sideburns — and then the result exported as a PDF.

PDFTricks allows for resizing of images in PDFs, principally compressing and reducing the file size to the order of “large”, “medium”, “small”, and “extra-small”, as well as image exporting to .jpg / .png / .txt formats, and file merging and splitting.

During the presentation, the PDF document above composed of the photo of myself on a trip was run through the software’s “extreme compression” option. The following is a clip from a screenshot from a file manager, showing the size difference between the the original file, and the newly created compressed file:

File size difference before and after processing file with PDFTricks

LibreOffice Draw allows for some image manipulation.

LibreOffice Draw being used to manipulate an embedded image

In this particular situation, the night sky drawing in the karaoke page of the example PDF I created was selected, and the various options directly available were shown. However, as mentioned earlier, I have imported PDF documents of building plans and modified them to include notes showing were works were performed, or to add signatures to documents.

PDF Forms

PDF Form Creation

LibreOffice Writer and Calligra Suite are fully-featured for the creation of forms. Unfortunately, I am not particularly adept at creating forms.

Filling PDF Forms

Evince — if the PDF form was designed to be interactively filled
Okular — if the PDF form was designed to be interactively filled
The Gimp — allows for text areas to be inserted, as well as photos, drawings, and the like
LibreOffice Draw — allows for text areas to be inserted, as well as photos, drawings, and the like

Here is an example form found at https://www.aloaha.com/sample-fillable-pdf-forms/ — a sample tax form which I began filling out for Mickey and Minnie Mouse, using Evince:

Fillable form being filled with the names of Mickey and Minnie Mouse

Final Choices:

Viewing / displaying PDF files : User’s choice (usually a system’s default PDF viewer is adequate, or a web browser)
Combining and splitting PDF files : PDFMixTool
Editing PDF files : User’s choice (depends on objectives and source file; The Gimp and LibreOffice Draw are good contenders)
Adjusting PDF file size : PDFTricks
Form creation : User’s choice
Form filling : User’s choice (usually a system’s default PDF viewer is adequate, or a web browser)
Exporting PDF to other formats : OCRFeeder (for .odt); LibreOffice Draw (Photos and images); The Gimp (photos and images)

Note on Linux availability of the above software:

Here are some screen shots from my system’s installed repositories (Fedora Stable; Fedora Updates; rpmfusion.org — free and non-free)

PDF software easily accessible from my computer’s software repositories (“App Stores”):

Gnome Software list of available PDF software from various software repositories on Fedora Linux

As this list suggests, there is lot of software available which have varying PDF abilities, ranging from being dedicated PDF software of various kinds, to other pieces of software with other principal functions but with PDF functions ranging to simple importing from and exporting to the format, to being useful within the limits of the software’s main functions to manipulate PDF files in some way(s).

Summary:

This presentation’s goals are to highlight:

how PDF files are well supported most of the time on most systems, while the various pieces of software, between two versions, typically a well-known closed source project and an open-source counterpart, for document production, are not as compatible with each other as we may want;
free software while avoiding the security risks inherent to using unknown and potentially dangerous websites, as well as software which is easily available for routine tasks as well as to reduce costs;
the possibility of editing PDF files with various pieces of free software which are easily available in most Linux distributions’ repositories — as well as often easily available for other platforms — albeit occasionally with variable success.

Questions taken during the presentation:

A question asked midway through the presentation expressed a certain surprise that The Gimp can be used to edit PDFs. As mentioned earlier, The Gimp is able to import PDF files, and perform various functions on the file according to its strengths (image manipulation).

A participant asked at the end during a question period about a recommendation for software to affix signatures to documents. I replied that I was not aware of any open source official signing software with digital traceability, simply because that I had not done any research on that subject; however, an image of a scanned signature can usually be inserted in a document using The Gimp or LibreOffice Draw, or as a document is being created in a word processor.

A final comment recommended the use of LibreOffice Draw, based on the commentor’s frequent use of it to perform a number of the functions listed here, to which I’d commented that I had asked my employer’s IT department to install LibreOffice on my work-issued Windows-based laptop computer in order to be able to perform some drawing-modification functions as part of my employment.

Enjoy sharing and editing PDF files!

UPDATE 20220407:

Signing PDFs can be performed with jPDF Tweak.

JPDF Tweak can also encrypt and add passwords to a PDF.