I upgraded to Ubuntu 22.04

As the needlessly ambiguous title declares, last night I upgraded my primary work laptop from Ubuntu 20.04 to 22.04 using Ubuntu's upgrade feature (do-release-upgrade). Note that I didn't do this blindly - I did install it quickly on a Virtual Machine to ensure that nothing was obviously wrong, but verification of this was quick and the upgrade process swiftly followed.

Completely unexpectedly, this went (mostly) incredibly well! I replaced all of the flagged applications with the new versions during this process and, after a post-installation reboot, I am extremely impressed at how snazzy the new system looks!

We've got an updated boot logo and a removal of purple from the default loading / login screen; we've got hover indications for almost every clickable option; we've got more vanilla theming customisation than ever.
And we've still got GNOME as our default DE. These victories are true and real and cause for celebration.

However, issues arose almost instantly - some trivial (like having to re-enable passwordless sudo), some very much not so.

For starters, because of the new version of GNOME and all the changes made, none of my extensions work anymore! In fact, gnome-tweaks doesn't even appear to have a section for extensions any longer, which I find most displeasing. My little system monitor graphs in the top-most toolbar will be sorely missed.

Equally egregiously, though admittedly only to me, GNOME have decided to conform to the contemporary (read: MacOS and Windows) horizontal workspace layout. While this means I can use three fingers to change my workspace during the few occassions that I'm not plugged into my spectacularly loud keyboard and LED-dressed mouse, as a feature that is essential to how I work both professionally and personally, it means that all of my instincts are wrong with regards to workspace switching. My poor VDU hasn't had this much abuse directed at it since my efforts to get a Rails app running on GCP App Engine.

However, the most pressing, most horrifying change is the new version of OpenSSH on Ubuntu 22.04. Somewhere down the line, they silently decided that they would discontinue default permission of RSA public keys. What this translated to, when trying to access a remote production Rails console, was the knowledge that my ability to connect to any server we have> had just... gone: 

Permission denied (publickey)
Panic, as you might well imagine, ensued.

Luckily for me, certain members our Systems Engineering team are masters of the noble art of Google-Fu and, after a needlessly deep dive, we found the decision made by the OpenSSH team mentioned above. Despite the disgust and pitchfork-retrieving anger this stimulated, it did at least allow us to find the source of the problem.

So, for the benefit of anybody who has this same issue, whereby your SSH connections are inexplicably failing with a Permission denied error after upgrading to or installing Ubuntu 22.04, just add the following line to the very top of your SSH config (~/.ssh/config): 

PubkeyAcceptedKeyTypes +ssh-rsa

Comments

Post a Comment

Popular posts from this blog

New Rails Apps with Docker Compose

Image
Following on from the Docker & docker-compose guides, it is possible to use docker-compose to build a Rails application that uses a PostgreSQL database without even installing Ruby on your local machine by instead using containers ! This becomes a very useful option to have if you work from many different workstations and don't want to ensure they are all equipped with the correct Ruby and Rails dependencies, or if you wish to use a version of Ruby / Rails not supported by your operating system (for example, Ubuntu 20.04 only allows provides up to Ruby 2.7 in its apt cache). In fact, Rails 7 added native support for Docker, such that it generates almost all of the default files we need for us! This comes with its problems and, I won't lie, updating this post to work with Rails 7 (it was previously written for Rails 6) has been a colossal pain and features a bit of hackery. However it is ultimately a good thing, and having
Read more

[ToDoList] Basic Pages

Image
Well that was fun. However all we’ve really done is spooked someone called Bob, without actually creating anything remotely resembling a web application. Let’s rectify this and create some pages one would normally find on a website; a Home page and an About page. Home & Away About Helpful Links [Insert Beatles Reference]     Because we already learned a bit about MVC, we know that we will need a controller and at least one view to display these pages (we won’t need to worry about models until we’re handling real data). As before, we’ll need to add a route configuration so Rails knows where to go, too. Rails provides a fair bit of magic to streamline this process in the form of generators . However, because we’re learning, we’re going to do this manually for now and learn what this magic entails, so we can appreciate it more later. We already created a PagesController in the last sec
Read more

[ToDoList] Docker Compose

Image
We learned in the previous section how Docker is a fantastic tool with which to build and deploy applications, however has some inconveniences with developing these apps such as having to rebuild the image every time there is a code change as well as any development database entries being wiped. This section will offer some relief against these two issues by using Docker Compose to build our application and make live code changes, as well as using a separate container to host our development database in PostgreSQL - this will encompass three main tasks: Back up and edit the Dockerfile we made in the previous section so our image can be built. Create our docker-compose.yml in the app's root directory to create our web & postgresql database containers. Back up and edit some our app's configuration (namely the database.yml & Gemfile ) to use the new postgresql container . After all this, we can set about
Read more