I upgraded my Ubuntu 20.04 (Focal Fossa) to 22.04.1 (jammy jellyfish), the current LTS release, last week. I simply followed the prompts from the Software Upgrader. The updates succeeded and the systems are completely useable, but there were a couple glitches.
I have a Lenovo ThinkPad X130e laptop. It came with Windows 10 Home Edition, which does not work nearly as well for me as the Profession Edition I have on other systems. It hangs frequently. I have also installed Ubuntu Linux on it, which does better.
These days Chromebooks are everywhere, so I have become curious about Google’s Chrome OS Flex, the installation of which can turn an ordinary old (but not too old) PC into a Chromebook. Continue reading
Recently there were a few times when I was using VS Code under Windows and the response time got worse and worse. A reboot would fix it temporarily, but the problem would come back. A look at task manager showed that the Shell Infrastructure Host, sihost.exe, was using a lot of CPU. I thought about killing the process, but the dire warnings about system instability deterred me the first time.
I spent the weekend of June 16-19 at Carleton College. The occasion was my 50 year class reunion, for which I was a member of the gift committee, which in turn was a part of the overall planning committee. Mia (my wife) and I had a room on the third floor of Watson Hall, “3rd Watson” was how we would have referred to it back in the day. I don’t know if the current students refer to campus locations like that. I lived on “6th Watson” my senior year.
What I wrote in Slackware Diary – 3 about keeping Slackware up to date is not correct:
slackpkg update gpg slackpkg update
Does not do the job. A closer look at told me that I had to also run
# slackpkg install-new # slackpkg upgrade-all # slackpkg clean-system
By default, Windows assumes that the local system clock is set to local time, and updates it accordingly. Ubuntu Linux assumes that the clock is running UTC (essentially Greenwich Mean Time) and will update it on that assumption. Since it knows your location (you specified it at installation, and hopefully updated it when you moved) it will display the correct local time just like windows.
The problem comes when you have a dual boot (Linux and Windows) system. When you reboot from one OS into the other the new OS will assume the system clock is behaving according its own rules, even though the other OS was following its rules. To fix this:
I noted in Slackware Diary that I had installed Free42 under Slackware. As I wrote in 2006 I fell in love with HP calculators and their RPN notation back in the 1970s, and still find the conventional algebraic notation rather awkward. I no longer carry a physical calulator, but I have Free42 installed on my phone and my tablet, and on my Windows systems. Now I also have it on Slackware. So I circled back to see if I could install in on Ubuntu.
Following up from last time:
gmcdavid@Tyrone:~$ flatpak uninstall com.visualstudio.code gmcdavid@Tyrone:~$ flatpak uninstall com.visualstudio.code-oss
I was prompted for the root password. I may come back to Flatpak on Slackware, but for now on to some other installations….
Continuing from Slackware Diary – 1
Fixed the prompt by copying .bashrc and .profile (renamed as .bash_profile) from my primary Ubuntu system. This works and I have nice color prompts in Slackware. Need to see if I have scripts from my previous Slackware days to add environment variables, aliases, etc. Life in Slackware means a lot of time on the command line.
The next task on my list was to install Flatpak so I could use apps from Flathub
From Hilbert Space to Dilbert Space, and beyond 