← Back to team overview

desktop-packages team mailing list archive

[Bug 1358256] Re: No input devices in sound settings


[Expired for unity-control-center (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: unity-control-center (Ubuntu)
       Status: Incomplete => Expired

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.

  No input devices in sound settings

Status in unity-control-center package in Ubuntu:

Bug description:
  (Ubuntu 14.04, updated from 12.04) pavucontrol functions correctly, allowing adjustments to microphone settings. Microphone functions properly, tested in Audacity and Skype.
  Nevertheless, no input devices appear in the unity-control-center. Output devices do appear correctly.

  Sound is
  00:06.1 Audio device: NVIDIA Corporation MCP55 High Definition Audio (rev a2)
  	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7250
  	Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 21
  	Memory at f9ef0000 (32-bit, non-prefetchable) [size=16K]
  	Capabilities: [44] Power Management version 2
  	Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
  	Capabilities: [6c] HyperTransport: MSI Mapping Enable- Fixed+
  	Kernel driver in use: snd_hda_intel

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic
  Uname: Linux 3.13.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 18 13:13:33 2014
  InstallationDate: Installed on 2012-11-08 (647 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to trusty on 2014-08-11 (6 days ago)
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup             30.0-0ubuntu4
   gnome-control-center 1:3.6.3-0ubuntu56.1

To manage notifications about this bug go to: