no sound on internal speakers or headphones, then open the gnome_alsamixer, there are three head phone choices, the ones on the left is muted, leave it muted (or not) and turn up the volume on that one, and then the internal speakers will play sound

Bug #1722066 reported by paint-it-black
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Eee PC Seashell series.

There is no sound after installing Ubuntu Gnome 17.04. The volume control shows the sound turned all the way up. The internal test found under settings->sound runs but no sound plays. Etc.

Installed a mixer and all looked correct, but still no sound.

work around:

Installed the gnome_alsamixer package. Three headphone settings show (strange). Turn up the volume on the far left of the headphones, and then sound plays on the internal speakers. This is true, although the 'mute' box under the far left headphones volume control remains checked. Checking or unchecking that mute box does nothing.

Wish I could attach two screen shots for the mixer, a before and after, but the report seems to only allow one, so I attached the 'after' one with working sound ..

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: shihju 1477 F.... pulseaudio
CurrentDesktop: GNOME
Date: Sun Oct 8 19:21:34 2017
InstallationDate: Installed on 2017-08-17 (51 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/30/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1401
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1015PE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd08/30/2011:svnASUSTeKComputerINC.:pn1015PX:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1015PX
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
paint-it-black (paint-it-black) wrote :
Revision history for this message
dino99 (9d9) wrote :
Changed in alsa-driver (Ubuntu):
status: New → Invalid
Revision history for this message
paint-it-black (paint-it-black) wrote : Re: [Bug 1722066] Re: no sound on internal speakers or headphones, then open the gnome_alsamixer, there are three head phone choices, the ones on the left is muted, leave it muted (or not) and turn up the volume on that one, and then the internal speakers will play sound
Download full text (3.2 KiB)

Yes updated to 17.10, the same bug is in 17.10.

On Mon, Jan 15, 2018 at 5:13 PM, dino99 <email address hidden> wrote:

> That version is now dead
> http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-
> has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
>
> ** Changed in: alsa-driver (Ubuntu)
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1722066
>
> Title:
> no sound on internal speakers or headphones, then open the
> gnome_alsamixer, there are three head phone choices, the ones on the
> left is muted, leave it muted (or not) and turn up the volume on that
> one, and then the internal speakers will play sound
>
> Status in alsa-driver package in Ubuntu:
> Invalid
>
> Bug description:
> Eee PC Seashell series.
>
> There is no sound after installing Ubuntu Gnome 17.04. The volume
> control shows the sound turned all the way up. The internal test
> found under settings->sound runs but no sound plays. Etc.
>
> Installed a mixer and all looked correct, but still no sound.
>
> work around:
>
> Installed the gnome_alsamixer package. Three headphone settings show
> (strange). Turn up the volume on the far left of the headphones, and
> then sound plays on the internal speakers. This is true, although the
> 'mute' box under the far left headphones volume control remains
> checked. Checking or unchecking that mute box does nothing.
>
> Wish I could attach two screen shots for the mixer, a before and
> after, but the report seems to only allow one, so I attached the
> 'after' one with working sound ..
>
> ProblemType: Bug
> DistroRelease: Ubuntu 17.04
> Package: alsa-base 1.0.25+dfsg-0ubuntu5
> ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
> Uname: Linux 4.10.0-35-generic x86_64
> NonfreeKernelModules: wl
> ApportVersion: 2.20.4-0ubuntu4.5
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: shihju 1477 F.... pulseaudio
> CurrentDesktop: GNOME
> Date: Sun Oct 8 19:21:34 2017
> InstallationDate: Installed on 2017-08-17 (51 days ago)
> InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64
> (20170412)
> PackageArchitecture: all
> SourcePackage: alsa-driver
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 08/30/2011
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 1401
> dmi.board.asset.tag: To Be Filled By O.E.M.
> dmi.board.name: 1015PE
> dmi.board.vendor: ASUSTeK Computer INC.
> dmi.board.version: x.xx
> dmi.chassis.asset.tag: 0x00000000
> dmi.chassis.type: 10
> dmi.chassis.vendor: ASUSTeK Computer INC.
> dmi.chassis.version: x.x
> dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd08/30/2011:
> svnASUSTeKComputerINC.:pn1015PX:pvrx.x:rvnASUSTeKComputerINC.:
> rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
> dmi.product.name: 1015PX
> dmi.product.version: x.x
> dmi.sys.vendor: ASUSTeK Computer INC.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.ne...

Read more...

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.