public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220238] New: Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.
Date: Mon, 16 Jun 2025 08:45:21 +0000	[thread overview]
Message-ID: <bug-220238-208809@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=220238

            Bug ID: 220238
           Summary: Blue Yeti microphone doesn't consistently work after
                    unplugging and plugging back in or reboot.
           Product: Drivers
           Version: 2.5
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: fewspotty@protonmail.com
        Regression: No

Arch Linux

Bus 001 Device 018: ID 046d:0ab1 Logitech, Inc. Yeti Nano

When my Blue Yeti microphone is unplugged it won't work again until I reboot.
After I reboot, sometimes it works, sometimes it doesn't. Sometimes unplugging
and replugging fixes it after reboot, but if I unplug it while it's working it
won't work again no matter what until I reboot. Although it will still be
listed under lsusb, it won't work or be listed in pavucontrol. I have asked
others with Blue Yeti microphones, and they have confirmed this as an issue as
of right now.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2025-06-16  8:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  8:45 bugzilla-daemon [this message]
2025-06-17  5:32 ` [Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot bugzilla-daemon
2025-06-23  9:07 ` bugzilla-daemon
2025-06-23  9:29 ` bugzilla-daemon
2025-06-23  9:36 ` bugzilla-daemon
2025-06-23  9:42 ` bugzilla-daemon
2025-06-23 10:03 ` bugzilla-daemon
2025-06-23 10:40   ` Oliver Neukum
2025-06-23 10:40 ` bugzilla-daemon
2025-06-23 11:23 ` bugzilla-daemon
2025-06-23 11:24 ` bugzilla-daemon
2025-07-02  3:39 ` bugzilla-daemon
2025-07-21  8:39 ` bugzilla-daemon
2025-07-21 16:32 ` bugzilla-daemon
2025-07-26 23:17 ` bugzilla-daemon
2025-12-26 14:09 ` bugzilla-daemon
2025-12-26 14:09 ` bugzilla-daemon
2026-01-09 23:35 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-220238-208809@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox