Pitfalls of OSs
Ubuntu live server
IDK who thought that enabling auto suspend by default on a server is a good idea, but I hate it as it keep shutting down servers. Just ban server suspend all together:
sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target
Ubuntu messy audio
Ubuntu 20.04 defaults to pulseaudio
Ubuntu 22.04 defaults to pipewire
Pulseaudio is a piece of mess and does not support both audio in and out on bluetooth headset.
Pipewire has support on both in&out on bluetooth headset, but there are still some issues.
This end up with you wanting to switch between them at this stage.
Note that you do not wish to delete the original audio option when switching as it can break your system.
So switching involves installing another audio option and disabling the old option instead.
pulseaudio to pipewire
``` # For < Ubuntu 22.04 sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream sudo apt update sudo apt install pipewire libspa-0.2-bluetooth pipewire-audio-client-libraries systemctl --user daemon-reload systemctl --user stop pulseaudio.service pulseaudio.socket systemctl --user --now disable pulseaudio.service pulseaudio.socket systemctl --user mask pulseaudio systemctl --user unmask pipewire{,-pulse}.{socket,service} systemctl --user --now enable pipewire{,-pulse}.{socket,service} pipewire-media-session.service pactl info | grep PipeWire systemctl --user restart pipewire # When above command has nothing ```pipewire to pulseaudio
``` # For < Ubuntu 22.04 sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream sudo apt update sudo apt install pulseaudio systemctl --user stop pipewire{,-pulse}.{socket,service} pipewire-media-session.service systemctl --user --now disable pipewire{,-pulse}.{socket,service} pipewire-media-session.service systemctl --user mask pipewire{,-pulse}.{socket,service} systemctl --user unmask pulseaudio.service pulseaudio.socket systemctl --user --now enable pulseaudio.service pulseaudio.socket ```Ubuntu disk is full
Symptom: “…OOM…”
Symptom: “finished wait until snapd is fully seeded”
Symptom: Cannot boot into GUI
When ubuntu has used up 100% disk, it will fail to boot into GUI and you cannot use apt properly.
You can try to boot into safe mode and choose clean in recovery menu if there is still enough space for apt autoremove.
It is either ESC once just after bios entry point or shift before ubuntu logo to get into safe mode.
In worst case, even apt autoremove will fail to run when it cannot even squeeze out any space,
you can borrow swap to free some space just to allow apt autoremove to work.