I recently setup a GNOME development environment (after about seven years!). That meant starting from scratch since my old notes and scripts were completely useless.
My goal for this setup was once again to have the bare minimum jhbuild modules on top of a solid base system provided by my distro. The Linux desktop stack has changed a bit, specially around activation, dbus, and systemd, so I was a bit lost on how to do things properly.
Luckily around the time I was trying to figure this out, I ran into Florian Müllner’s excellent post on how to work on shell hacking on a Silverblue system.
After removing the container-related bits, I was able to get a reliable jhbuild session integrated into my system.
Here is how to run a development GNOME session, fully integrated into your system.Continue reading “A minimal jhbuild GNOME session in Debian”
GUADEC 2020 has moved online because of the pandemic, and that means that many of us will be streaming our voice and faces.
Seeing as I have a fancy B.A. on Communication Studies & Film, I thought I might share some guerilla film making tips for our new online reality.
Here are some tips on how to sound and look good online.Continue reading “Some (late) video and audio advice for GUADEC online”
The HDMI out works just fine out of the box, except that you’ll notice that unless you boot with the HDMI cable connected, you’ll experience some weird audio lag through HDMI. Even worse, after a few seconds, HDMI audio will simply stop working.
Audio drift, lag, and eventually no audio. To rub some salt into the wound, this does not happen under macOS. Classic.
Well, the good news is that you can get this fixed. Turns out this is because of Linux kernel bug #60769. I can’t comment on the details of how and why the
IOMMU feature breaks this particular combination of videocard/HDMI/audio, but I can tell you how to work-around this.
To fix, or at least work-around this, you have to edit your
/etc/default/grub and add
intel_iommu=on,igfx_off to your kernel boot options: