b2e5ad1670
Due to an issue, probably in bluez, the bluetooth service often fails to start on boot. Restarting the service later make bluez start correctly. While adding the service supervisor for just this issue isn't a great solution, in any case having a supervisor on such an important system service is good, and it fixes this issue also by restarting the bluetooth service after the first failure on boot. May 30 08:05:56 fairphone-fp4 daemon.info bluetoothd[1420]: Bluetooth daemon 5.66 May 30 08:05:56 fairphone-fp4 daemon.err bluetoothd[1420]: src/main.c:main() Unable to get on D-Bus Also while we're editing the list of subpackages make sure they're ordered alphabetically. [ci:skip-build]: already built successfully in CI |
||
---|---|---|
.. | ||
APKBUILD | ||
postmarketos-base-ui-elogind.post-install | ||
postmarketos-base-ui-elogind.pre-upgrade | ||
postmarketos-base-ui-openrc-settingsd.post-install | ||
postmarketos-base-ui-openrc-settingsd.post-upgrade | ||
postmarketos-base-ui.post-install | ||
postmarketos-base-ui.post-upgrade | ||
rootfs-etc-chrony-chrony.conf | ||
rootfs-etc-conf.d-bluetooth | ||
rootfs-etc-conf.d-openrc-settingsd | ||
rootfs-etc-conf.d-tinydm | ||
rootfs-etc-conf.d-wpa_supplicant | ||
rootfs-etc-elogind-logind.conf | ||
rootfs-etc-NetworkManager-conf.d-hostname-mode.conf | ||
rootfs-etc-NetworkManager-conf.d-tethering.conf | ||
rootfs-etc-NetworkManager-conf.d-use-dnsmasq.conf | ||
rootfs-etc-NetworkManager-dispatcher.d-85-tethering | ||
rootfs-etc-NetworkManager-dispatcher.d-99-dns-filter.sh | ||
rootfs-etc-pulse-default.pa.d-postmarketos.pa | ||
rootfs-etc-skel-.profile | ||
rootfs-etc-sleep-inhibitor.conf | ||
rootfs-etc-tinydm.d-env-wayland.d-50-firefox-wayland.sh | ||
rootfs-etc-tinydm.d-env-wayland.d-50-sdl-wayland.sh | ||
rootfs-etc-X11-Xwrapper.config | ||
rootfs-usr-lib-NetworkManager-system-connections-USB_Networking.nmconnection |