v0.3.3

One behaviour change, and the documentation catching up with 0.3.2.

A bluetooth headset now takes the sound when it connects

Connect a headset and the audio moves to it. That used to happen on its own, and hyprsimple was the reason it stopped.

WirePlumber chooses the default output by priority, and a bluetooth sink already outranks the built-in one: priority.session 1010 against 1009 on the machine this was reported from. So on a fresh install a headset takes over by itself.

What stops it is an explicitly chosen output. WirePlumber's find-selected-default-node.lua does

if current_configured_node == name then
  priority = 30000 + priority

to whatever default.configured.audio.sink names, so the chosen output scores 31009 and no bluetooth device can outrank it. SUPER + F10 writes that key through pactl set-default-sink. Pressing the audio switch once therefore turned bluetooth auto-switching off permanently, on every machine, and nothing said so. It was reported as a headset that connects, appears as an output, and gets no sound (#152).

A user service watches for a bluetooth output appearing and switches to it. Only on appearance, so a device already connected is left where it is, and switching away from it by hand is not undone. Reconnecting counts as appearing again.

Turn it off with

systemctl --user disable --now hyprsimple-audio-autoswitch.service

SUPER + F10 still works exactly as before, and is still the way to choose an output by hand.

The wl-screenrec build failure has a real answer

0.3.2 said a missing x86_64-linux-gnu-gcc meant an incomplete base-devel or a partial upgrade, and told you to run a full pacman -Syu. That was wrong, and it would have left the machine exactly as broken.

A rustc that reaches for that name has it baked in at build time, so upgrading gcc changes nothing, and it breaks every cargo build on the machine rather than this one package. The FAQ now says how to tell that apart in one command and points cargo at a linker that exists.

Recording itself was never at risk. wf-recorder comes from the official repositories and 0.3.2 already falls back to it.

Documentation

• The README covers what 0.3.2 changed: the install that no longer stops to confirm, wifi asking for a password, and which screen recorder is required (#151).
• FAQ.md is one paragraph per line. Wrapping at a column put an unrelated reflow into the diff every time a sentence changed.

Upgrading

hyprsimple-update            # continue the channel you are on
hyprsimple-update --stable   # switch to this release

A migration delivers and enables the audio watcher on installs that already exist, because ~/.config is copied once and never overwritten. A unit already at that path is left alone.