Linux reports Samson Meteor USB mic as an output device

Bug #1762725 reported by Carlos Echenique
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: guru 2355 F.... pulseaudio
 /dev/snd/controlC1: guru 2355 F.... pulseaudio
 /dev/snd/controlC0: guru 2355 F.... pulseaudio
CurrentDesktop: Budgie:GNOME
Date: Tue Apr 10 08:54:30 2018
InstallationDate: Installed on 2018-04-07 (2 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/06/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.52
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350M MORTAR ARCTIC (MS-7A37)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 4
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A37
dmi.product.version: 2.0
dmi.sys.vendor: MSI
---
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: guru 2402 F.... pulseaudio
 /dev/snd/controlC1: guru 2402 F.... pulseaudio
 /dev/snd/controlC0: guru 2402 F.... pulseaudio
CurrentDesktop: Budgie:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-04-07 (3 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
IwConfig:
 enp30s0 no wireless extensions.

 lo no wireless extensions.
MachineType: MSI MS-7A37
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-13-generic N/A
 linux-backports-modules-4.15.0-13-generic N/A
 linux-firmware 1.173
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: bionic
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/06/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.52
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350M MORTAR ARCTIC (MS-7A37)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 4
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A37
dmi.product.version: 2.0
dmi.sys.vendor: MSI
---
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: guru 2402 F.... pulseaudio
 /dev/snd/controlC1: guru 2402 F.... pulseaudio
 /dev/snd/controlC0: guru 2402 F.... pulseaudio
CurrentDesktop: Budgie:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-04-07 (3 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
IwConfig:
 enp30s0 no wireless extensions.

 lo no wireless extensions.
MachineType: MSI MS-7A37
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-13-generic N/A
 linux-backports-modules-4.15.0-13-generic N/A
 linux-firmware 1.173
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: bionic
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/06/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.52
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350M MORTAR ARCTIC (MS-7A37)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 4
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A37
dmi.product.version: 2.0
dmi.sys.vendor: MSI

Revision history for this message
Carlos Echenique (etrigan63) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

PulseAudio is selecting the USB device for output because that's correct behaviour for USB speakers. And PulseAudio thinks the mic is a speaker because that's what ALSA seems to be telling it.

The real problem here is that the Linux kernel seems to be reporting the mic is an output device. Much like bug 1749207.

affects: pulseaudio (Ubuntu) → linux (Ubuntu)
summary: - Ubuntu Budgie selects USB mic as default audio output after every
- reboot.
+ Linux reports Samson Meteor USB mic as an output device
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1762725

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Carlos Echenique (etrigan63) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Carlos Echenique (etrigan63) wrote : CRDA.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : Lspci.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : Lsusb.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : ProcEnviron.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : ProcModules.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : PulseList.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : UdevDb.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : WifiSyslog.txt

apport information

description: updated
Revision history for this message
Carlos Echenique (etrigan63) wrote : AlsaInfo.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : CRDA.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : Lspci.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : Lsusb.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : ProcEnviron.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : ProcModules.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : PulseList.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : UdevDb.txt

apport information

Revision history for this message
Carlos Echenique (etrigan63) wrote : WifiSyslog.txt

apport information

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Oops, didn't see Daniel already triaged this.

no longer affects: pulseaudio (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please try daily kernel at [1]. I think this commit is to solve the issue. The fix is not in mainline yet.

commit 5a222e8494524d04cc8de63726644759e5b132f7
Author: Andrew Chant <email address hidden>
Date: Fri Mar 23 19:25:23 2018 -0700

    ALSA: usb-audio: UAC2 jack detection

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/

Revision history for this message
Carlos Echenique (etrigan63) wrote : Re: [Bug 1762725] Re: Linux reports Samson Meteor USB mic as an output device
Download full text (6.6 KiB)

I am not that brave. I will wait until it is mainlined.

Carlos EcheniquePhotographer
<email address hidden> (https://link.getmailspring<email address hidden>/0?redirect=mailto%3Acarlos%40echenique.com&recipient=MTc2MjcyNUBidWdzLmxhdW5jaHBhZC5uZXQ%3D)
305-219-2433 (tel:305-219-2433)
http://www.cephotographic.com (https://link.getmailspring<email address hidden>/1?redirect=http%3A%2F%2Fwww.cephotographic.com&recipient=MTc2MjcyNUBidWdzLmxhdW5jaHBhZC5uZXQ%3D)

On Apr 11 2018, at 1:47 am, Kai-Heng Feng <email address hidden> wrote:
>
> Please try daily kernel at [1]. I think this commit is to solve the
> issue. The fix is not in mainline yet.
>
> commit 5a222e8494524d04cc8de63726644759e5b132f7
> Author: Andrew Chant <email address hidden>
> Date: Fri Mar 23 19:25:23 2018 -0700
>
> ALSA: usb-audio: UAC2 jack detection
> [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1762725
>
> Title:
> Linux reports Samson Meteor USB mic as an output device
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> Whenever I reboot my system, pulseaudio selects my Samson Meteor USB
> mic as the default output device. I have to manually select the analog
> output every time. Also, the Default effect sound does not make any
> noise.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: pulseaudio 1:11.1-1ubuntu7
> ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
> Uname: Linux 4.15.0-13-generic x86_64
> ApportVersion: 2.20.9-0ubuntu4
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC2: guru 2355 F.... pulseaudio
> /dev/snd/controlC1: guru 2355 F.... pulseaudio
> /dev/snd/controlC0: guru 2355 F.... pulseaudio
> CurrentDesktop: Budgie:GNOME
> Date: Tue Apr 10 08:54:30 2018
> InstallationDate: Installed on 2018-04-07 (2 days ago)
> InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
> SourcePackage: pulseaudio
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 06/06/2017
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: A.52
> dmi.board.asset.tag: To be filled by O.E.M.
> dmi.board.name: B350M MORTAR ARCTIC (MS-7A37)
> dmi.board.vendor: MSI
> dmi.board.version: 2.0
> dmi.chassis.asset.tag: To be filled by O.E.M.
> dmi.chassis.type: 4
> dmi.chassis.vendor: MSI
> dmi.chassis.version: 2.0
> dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0:
> dmi.product.family: To be filled by O.E.M.
> dmi.product.name: MS-7A37
> dmi.product.version: 2.0
> dmi.sys.vendor: MSI
> ---
> ApportVersion: 2.20.9-0ubuntu4
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC2: guru 2402 F.... pulseaudio
> /dev/snd/controlC1: guru 2402 F.... pulseaudio
> /dev/snd/controlC0: guru 2402 F.... pulseaudio
> CurrentDesktop: Budgie:GNOME
> DistroRelease: Ubuntu 18.04
> InstallationD...

Read more...

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Carlos Echenique (etrigan63) wrote :

Any idea when that kernel will be pushed out to regular users? I am still experiencing this issue.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

If trying mainline kernel is not an option, wait for Cosmic (18.10).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.