Running Ubuntu 22.04 LTS with Ubuntu Desktop on X11.
After setting dock (dash to dock extension) to auto-hide, it won't reappear if any app is full screen.
Turn off "require-pressure-to-show" in dconf settings for dock.
UPDATE: According to the Ubuntu bug history cited below, this problem was fixed with an update of ubuntu-drivers-common on September 10, 2024. After removing the workaround udev rule and verifying the package was updated on my system, I confirmed that the troublesome behavior didn't return for me. That said, at least one other person has advised that they're still experiencing it even with the workaround.
Got bit by Ubuntu Linux bug #2060268 on the latest kernel update for 22.04 LTS (6.8.0-40-generic).
As in the bug report (and many forum posts across the Internet) this appears to be due to a collision between the simpledrm kernel module and NVIDIA drivers. The symptom is a nonexistent display device being assigned as card0. The practical effect is to throw off any previous configuration of the display system (display 1 becoming display 2, display 2 becoming display 3). As a result, customization
The latest KVM on Ubuntu Desktop 22.04 supports both TPM2.0 and Secure Boot for Windows 11 guests. To use it you'll need to make sure the ovmf package is installed.
If using Virtual Machine Manager (VMM, or virt-manager) to install Windows 11 from a Microsoft iso, be sure to check "Customize configuration before install" before clicking on the "Finish" button. While VMM will automatically detect the operating system version and customize many things, including TPM, it will not choose the correct setting for Secure Boot.
When you get to the VM's configuration screen in VMM, you'll find that a TPM vNone device has already been added. Setting up Secure Boot properly will require manually selecting the correct firmware. To do that:
NOTE: Please don't ask for help here, it was a miracle that I got it to work at all. Seek answers in the usual places (yes, even Stackoverflow knows more than I do).
The question: How can I get 3d accelerated graphics for Linux guests in KVM without using PCI passthrough?
The short answer is: Use VirGL. The long answer is more complicated, because the VirGL project has had slow but steady progress towards actually working reliably, but the degree to which any given Linux distribution (or related driver project) is in sync has varied greatly over time. Even if it works right now, today, on your machine, it might not tomorrow. Note that even when it works, graphics performance is mediocre to downright painful.
Tested on Ubuntu Desktop 22.04.04 LTS with qemu-kvm, in an "Ubuntu on Xorg" session (not Wayland). Linux quests must have spice-vdagent installed (Ubuntu installs this by default). The hardware is a AMD 5600G d
System impacted is a AMD workstation with NVIDIA graphics, running Gnome desktop on X11. The operating system is Ubuntu Desktop 22.04.4 LTS.
The latest mutter update causes stutter and lagging in Gnome terminal sessions. Switching to xterm relieves the problem, but not a real solution.
The problem was finally identified as a bug in the code to Canonical's latest update for Gnome's mutter window manager and compositor (Bug #2059847). A preliminary workaround PPA from mutter maintainer Daniel Van Vugt (vanvugt) stopped working after a new official update that retained the original bug. In a 15 May 2024 comment to the bug report (#135), Daniel posted links to corrected packages that fix the issue:
You don't really need to enable jammy-proposed. Just download the 3 proposed packages:
Use ghostscript:
$ gs -sDEVICE=pdfwrite \
-dCompatibilityLevel=1.4 \
-dPDFSETTINGS=/ebook \
-dNOPAUSE \
-dBATCH \
NOTE: The N3060 CPU's 2 cores on this old Chromebook were just too sluggish for it to be usable during that overseas trip mentioned below. It now sits unused on my lab table, as I contemplate taking it on a journey to our local county recycling center. I leave this gist here mostly out of nostalgia.
My retail (not enterprise) Dell Chromebook 11 (an Inspiron model 3181, not the 3180 or 3189) went EOL shortly after I purchased it new from Best Buy. Since then it saw some hard use in the family kitchen as a recipe lookup device, but was finally retired when replaced by a (relatively) newer Android tablet (that also reached EOL shortly thereafter).
With an overseas trip looming, I decided to look into refurbishing the Chromebook for use as a privacy hardened travel laptop. Frankly, the thought of TSA and Customs manhandling my trusty portable workstation was too much to bear.
I mostly followed the detailed instructions in the Chrultrabook Docs,
IMPORTANT: Anyone trying to understand/manage printing on Debian-derived distributions, including Ubuntu, should read through CupsDriverlessPrinting. "CupsDriverLessPrinting". Debian Wiki, https://wiki.debian.org/CUPSDriverlessPrinting.
Following are some notes I've brought back from the gist graveyard. Notably, the recent publication of a vulnerability in the Apple-managed CUPS printing subsystem has renewed my misgivings about Zeroconf. I've now disabled it on all my Linux systems, although it will result in inconvenience to me.
Zeroconf, or Zero Configuration may be a dream for developers: but can be an absolute nightmare for sysadmins and users. Zeroconf aims to allow the system to configure itself automatically for all kinds of external devices, from music players to printers. For many of th
We just recently began to use restic as our main backup solution at home. I'm posting this mostly to document the configuration for myself. Anyone interested in using restic should thoroughly read the documentation before proceeding.
By default, backups are run with encryption and compression enabled. Although many people have all hosts in a multi-host network sharing a single repo, I chose to separate them out (to limit the impact of any future data corruption and simplify security configuration).