My fellow penguins,

I have been pwned. What started off as weeks of smiling everytime I heard a 7-10s soundbyte of Karma Factory’s “Where Is My Mind” has now devolved into hearing dashes and dots (Morse Code) and my all-time favorite, a South Park S13: Dead Celebrities soundbyte of Ike’s Dad saying, “Ike, we are sick of you talking about ghosts!”

It’s getting old now.

I feel like these sounds should be grepable in some log somewhere, but I’m a neophyte to this. I’ve done a clean (secure wipe >> reinstall) already, the sounds returned not even a day later.

Distro is Debian Bookworm. So how do I find these soundbytes? And how do I overcome this persistence? UFW is blocking inbound connection attempts everyday, but the attacker already established a foothold.

Thank you in advance. LOLseas

  • CaptainBasculin@lemmy.bascul.in
    link
    fedilink
    arrow-up
    18
    ·
    edit-2
    2 days ago

    Run this command, it will record all audio activity until you stop it to the file sound-inputs.log.

    watch -n0.5 'pacmd list-sink-inputs | tee -a sound-inputs.log'

    When you hear the sound bites, take a look at it and see which process is triggering the sounds. Might help you discover its cause.

    Alternatively you can watch playback streams on pavucontrol. It lists all programs that run sounds, but is less detailed.

    • LOLseas@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      6
      ·
      2 days ago

      So the pulseaudio package wasn’t installed. Installed it, ran the command, and it reports, “No PulseAudio daemon running, or not running as session daemon.”

      I also lost sound. Checked into it, the Output switched from my HDMI to my USB Audio Interface. Switched it back to HDMI 5.1 and I’ve got audio back. If PulseAudio wasn’t in use, should we consider another one-liner?

      • CaptainBasculin@lemmy.bascul.in
        link
        fedilink
        arrow-up
        15
        ·
        2 days ago

        If the OS isn’t using PulseAudio by default, then it’s using PipeWire. I am not using it so cannot confirm how it’d work, but from what I understood from its documentation, replacing pacmd list-sink-inputs with pw-cli clients in the previously mentioned command should work.

        • LOLseas@sh.itjust.worksOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 day ago

          ‘pw-cli clients’ didn’t work. Maybe it’s deprecated? I can’t find mention of ‘clients’ in the pw-cli manpage.

              • CaptainBasculin@lemmy.bascul.in
                link
                fedilink
                arrow-up
                1
                ·
                edit-2
                22 hours ago

                from looking here, the thing that makes the most sense for me is pw-cli list-objects, could you try running pw-cli, then type list-objects and then play random sounds on an application? Could be anything, like a media player or web browser.

                When no command is given, pw-cli starts an interactive session with the default PipeWire instance pipewire-0.

                This would mean this should list any changes directly to the terminal, saving us from needing to log it externally

                It should report quite a lot of data considering it reports everything related to audio there, but it should let you know about any changes. If you can trace back from the sounds you made to the application you’ve run it from, it should work.

                • LOLseas@sh.itjust.worksOP
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  21 hours ago

                  Thanks, I ran the above watch command with ‘pw-cli list-objects’ and will report back upon the next occurence. It’s been quiet these past few hours. Thanks for helping a fellow penguin! Much appreciated, all of you.

                  • LOLseas@sh.itjust.worksOP
                    link
                    fedilink
                    English
                    arrow-up
                    1
                    ·
                    edit-2
                    21 hours ago

                    I couldn’t wait for the next soundbyte, so I checked the running sound-inputs.log and noticed a few entries for Chromium. I don’t use it, nor have I ever installed it on this system. Did a ‘which chromium-browser’ and got no hits. Yet it’s mentioned a few times in the log. Thoughts?

                    Edit: typo

    • LOLseas@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      4
      ·
      2 days ago

      God-tier comment here. Will run this right away. Thanks so much, will post findings. What a nice one-liner!