# cryptsetup luksChangeKey /dev/vda5
/dev/vda5 with your actual LUKS device. The command will ask you for the existing passphrase to replace, and then for the new passphrase for the device.
Recently, I had to connect to a hidden WiFi network with an EAP-TLS authentication. When configured via the NetworkManager UI on Ubuntu, it would work. However, on Debian Unstable running Gnome 42 and on Arch, the same process didn’t work. The problem seems to be an empty configuration line for
domain-suffix-match that gets created. To solve it, you can remove the
$ nmcli connection modify CorpSSID 802-1x.domain-suffix-match ""
Alternatively, you can configure the WiFi network directly with
nmcli without setting the problematic property>:
nmcli connection add type wifi ifname wlp0s20f3 \ con-name CorpSSID \ 802-11-wireless.ssid CorpSSID \ 802-11-wireless-security.key-mgmt wpa-eap \ 802-1x.eap tls \ 802-1x.identity guyru \ 802-1x.client-cert /absolute/path/wifi-certs/signed-certificate.cer \ 802-1x.private-key /absolute/path/wifi-certs/private.key
It’s important to have absolute paths to both the client certificate and the private key.
When trying to mount SMB share using
gio you might encounter the following error:
$ gio mount smb://ptnas1.cellebrite.local
gio: smb://nas.corp.local/: Location is not mountable
This error might be due to a missing gvfs backend. The smb backend should be located in
/usr/share/gvfs/mounts/smb.mount. If it is missing, you should install the
gvfs-backends package and it should resolve the mounting issue.
If the mount was successful, but you can’t see it under
$XDG_SESSION_DESKTOP/gvfss/, you are probably missing the FUSE server that makes the mounted filesystem available to all applications and not only to GIO aware applications. You can install the FUSE server by installing the
gvfs-fuse package. The server will automatically run after reboot. If you want to start the server immediately, you can start it manually:
$ /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs
After the latest PipeWire upgrade on Debian, sound stopped working for. The bluetooth headset would not connect, and in the output options I had only one device labeled dummy output.
This was caused by a recent upgrade of the
pipewire-media-session package to version 0.4.1-3. Debian decided that media-session is deprecated in favor of WirePlumber. As part of the package installation, the
/usr/share/pipewire/media-session.d/with-pulseaudio file, signalling media-session it should handle audio, gets removed. As I didn’t have WirePlumber installed, nothing managed the audio configuration. The solution is to recreate the file and restart the relevant PipeWire servcies.
$ sudo touch /usr/share/pipewire/media-session.d/with-pulseaudio $ systemctl restart --user pipewire pipewire-media-session pipewire-pulse
Sometimes GPG stops recognizing my Yubikey. Usually restarting
pcscd resolves it:
systemctl restart pcscd