• # Pulseaudio et systemd

    Posté par . En réponse à la dépêche Slackware 14.2. Évalué à 10. Dernière modification le 04 juillet 2016 à 19:12.

    En complément de la dépêche, l'intégration de pulseaudio dans slack n'a pas été une décision facile.

    Premier message du changelog :

    Wed Jan 13 00:01:23 UTC 2016
    Hey folks, happy new year!
    After upgrading to BlueZ 5 recently, everything seemed to be working great,
    but then it was pointed out that Bluetooth audio was no longer working.
    The reason was that the newer BlueZ branch had dropped ALSA support and now
    required PulseAudio. So with some trepidation, we began investigating adding
    PulseAudio to Slackware. Going back to BlueZ 4 wasn't an option with various
    dependent projects either having dropped support for it, or considering doing
    so. After several iterations here refining the foundation packages and
    recompiling and tweaking other packages to use PulseAudio, it's working well
    and you'll likely not notice much of a change. But if you're using Bluetooth
    audio, or needing to direct audio through HDMI, you'll probably find it a lot
    easier to accomplish that.
    Best of all, we're finally a modern, relevant Linux distro! ;-)
    Thanks to Mario Preksavec, Heinz Wiesinger, and Robby Workman for a lot of
    help and testing. Bug reports, complaints, and threats can go to me.

    Et premier bug assez rapidement :

    Wed Jun 22 21:56:53 UTC 2016
    l/pulseaudio-9.0-x86_64-1.txz: Upgraded.
    This release fixes many bugs, including this one that was commonly reported
    during the Slackware 14.2 development cycle:
    "Automatic routing improvements:
    In 8.0, PulseAudio started to automatically switch to another profile when
    the device associated with the current profile is unplugged. That seemingly
    smart thing had some serious unintended consequences. One typical issue was
    that when unplugging headphones, PulseAudio might switch to S/PDIF output
    and not switch back to headphones when they are plugged in again. Another
    issue was that HDMI in many cases appears to get temporarily unplugged when
    the monitor goes to sleep mode, or even when switching the refresh rate of
    the monitor—PulseAudio 8.0 would move audio away from the HDMI monitor in
    these cases and not move the audio back to HDMI when the monitor becomes
    available again. These issues are now fixed."

    Notons également que pour éviter d'utiliser systemd, slack a du changer de udev vers eudev et de ConsoleKit vers ConsoleKit2.
    Pour la suite, il est envisagé de passer à elogind dans le but de bénéficier du support de wayland sous kde sans s'encombrer de systemd.

    Comme quoi, si une petite équipe y arrive, on peut se passer de systemD sans faire beaucoup d'effort.