• 0 Posts
  • 6 Comments
Joined 6 years ago
cake
Cake day: May 31st, 2020

help-circle


  • So, I’m actually able to reproduce that and then had to fix it myself. 😅

    The “Pro Audio” profile seems to be a PipeWire thing: https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/FAQ#what-is-the-pro-audio-profile

    I’m guessing, the recording device doesn’t like that profile and just crashes right away. And when it has crashed, it won’t show up in the list of available devices.

    Now, how is that profile remembered even when the device disconnects? Apparently, a component called “WirePlumber” is responsible for that.
    And it stores this information in: ~/.local/state/wireplumber/default-profile

    If you don’t mind losing your profile selection for other devices, you can just do:

    mv ~/.local/state/wireplumber/default-profile ~/.local/state/wireplumber/default-profile.old
    

    and then do a reboot.
    After the reboot, your recording device should be back.

    If you do mind losing the other profiles, then make a backup of that file and try to remove lines related to your recording device, and again do a reboot to test it.
    For me, it was a device which had both input and output, and I had to remove both lines before it recognized it as unconfigured.




  • Firefox and Python’s cryptography toolchain have a build dependency on Rust, which are two packages that virtually all Linux distributions have packaged. So, some version of the Rust compiler is going to be available on virtually all Linux distributions.

    There’s no real reason to have the Rust compiler installed on non-dev systems, as you don’t need it for running Rust programs (although I kind of assume you know this).
    But yeah, it seems to be possible to dynamically link the standard library into Rust programs, so Linux distros could try to share that between them, and then it would effectively be installed by default.