2016-07-06 18:11:07 |
Anthony |
bug |
|
|
added bug |
2016-07-06 18:11:07 |
Anthony |
attachment added |
|
version.log https://bugs.launchpad.net/bugs/1599599/+attachment/4696519/+files/version.log |
|
2016-07-06 18:14:42 |
Anthony |
attachment added |
|
lspci-vnvn.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599599/+attachment/4696534/+files/lspci-vnvn.log |
|
2016-07-06 18:30:13 |
Brad Figg |
linux (Ubuntu): status |
New |
Confirmed |
|
2016-07-06 18:38:21 |
Anthony |
description |
This is my first ever bug report, so bear with me if I make mistakes.
Description: Ubuntu 16.04 LTS
Release: 16.04
System bell (aka PC speaker beep) is not working upon installing Ubuntu 16.04 Xenial Xerus. The "beep" command has been installed and works, also "echo foo | wall" works.
But "echo -e '\a'" and "printf '\a'" make no sound, nor does pressing the rubout or other keys in terminal and Gedit like it usually does.
lsmod shows pcspkr is loaded
****Note****
The symptoms are exactly the same as in bug #486154
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/486154
Just for the record, rmmod and reloading the pcspkr module, unblacklisting it, trying in vain to turn up the volume, and all the other usual steps are no longer relevant at this point. We are way beyond that here. Something very, very elusive in this 16.04 distro is blocking the bell. I suspect something new in 16.04 runs after you login which nullifies the standard error beep. Pressing down at the end in Gedit and the terminal also used to make the beep, but something is telling it not to anymore. The PC speaker works of course, as the alternative beep command and "echo foo | wall" prove.
Interestingly, Ubuntu can and does produce the system beep in two other instances:
1) Edit the grub menu at /etc/default /grub and remove the # hash at GRUB_INIT_TUNE="480 440 1" and you will get a beep when grub loads.
2) Press Backspace without entering your password at login, and you will get the error beep.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-28-generic 4.4.0-28.47
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: dv430uuyn 1784 F.... pulseaudio
/dev/snd/controlC0: dv430uuyn 1784 F.... pulseaudio
CurrentDesktop: Unity
Date: Wed Jul 6 14:00:50 2016
HibernationDevice: RESUME=UUID=e8206eff-651f-4207-b0a8-9c5a06959711
InstallationDate: Installed on 2016-06-24 (12 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
enp2s0 no wireless extensions.
lo no wireless extensions.
MachineType: Dell Inc. Vostro 430
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=c3a8f971-548b-4666-b865-6bf917bef1c9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-28-generic N/A
linux-backports-modules-4.4.0-28-generic N/A
linux-firmware 1.157.2
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/13/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.0
dmi.board.name: 054KM3
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:svnDellInc.:pnVostro430:pvr00:rvnDellInc.:rn054KM3:rvrA01:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 430
dmi.product.version: 00
dmi.sys.vendor: Dell Inc. |
This is my first ever bug report, so bear with me if I make mistakes.
Description: Ubuntu 16.04 LTS
Release: 16.04
System bell (aka PC speaker beep) is not working upon installing Ubuntu 16.04 Xenial Xerus.
The "beep" command has been installed and works, also "echo foo | wall" works. But "echo -e '\a'" and "printf '\a'" make no sound, nor does pressing the rubout or other keys in terminal and Gedit like it usually does.
lsmod shows pcspkr is loaded
****Note****
The symptoms are exactly the same as in bug #486154
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/486154
Just for the record, rmmod and reloading the pcspkr module, unblacklisting it, trying in vain to turn up the volume, and all the other usual steps are no longer relevant at this point. We are way beyond that here. Something very, very elusive in this 16.04 distro is blocking the bell. I suspect something new in 16.04 runs after you login which nullifies the standard error beep. Pressing down at the end in Gedit and the terminal also used to make the beep, but something is telling it not to anymore. The PC speaker works of course, as the alternative beep command and "echo foo | wall" prove.
Interestingly, Ubuntu can and does produce the system beep in two other instances:
1) Edit the grub menu at /etc/default /grub and remove the # hash at GRUB_INIT_TUNE="480 440 1" and you will get a beep when grub loads.
2) Press Backspace without entering your password at login, and you will get the error beep.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-28-generic 4.4.0-28.47
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: dv430uuyn 1784 F.... pulseaudio
/dev/snd/controlC0: dv430uuyn 1784 F.... pulseaudio
CurrentDesktop: Unity
Date: Wed Jul 6 14:00:50 2016
HibernationDevice: RESUME=UUID=e8206eff-651f-4207-b0a8-9c5a06959711
InstallationDate: Installed on 2016-06-24 (12 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
enp2s0 no wireless extensions.
lo no wireless extensions.
MachineType: Dell Inc. Vostro 430
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=c3a8f971-548b-4666-b865-6bf917bef1c9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-28-generic N/A
linux-backports-modules-4.4.0-28-generic N/A
linux-firmware 1.157.2
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/13/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.0
dmi.board.name: 054KM3
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:svnDellInc.:pnVostro430:pvr00:rvnDellInc.:rn054KM3:rvrA01:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 430
dmi.product.version: 00
dmi.sys.vendor: Dell Inc. |
|
2016-07-06 18:39:26 |
Anthony |
description |
This is my first ever bug report, so bear with me if I make mistakes.
Description: Ubuntu 16.04 LTS
Release: 16.04
System bell (aka PC speaker beep) is not working upon installing Ubuntu 16.04 Xenial Xerus.
The "beep" command has been installed and works, also "echo foo | wall" works. But "echo -e '\a'" and "printf '\a'" make no sound, nor does pressing the rubout or other keys in terminal and Gedit like it usually does.
lsmod shows pcspkr is loaded
****Note****
The symptoms are exactly the same as in bug #486154
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/486154
Just for the record, rmmod and reloading the pcspkr module, unblacklisting it, trying in vain to turn up the volume, and all the other usual steps are no longer relevant at this point. We are way beyond that here. Something very, very elusive in this 16.04 distro is blocking the bell. I suspect something new in 16.04 runs after you login which nullifies the standard error beep. Pressing down at the end in Gedit and the terminal also used to make the beep, but something is telling it not to anymore. The PC speaker works of course, as the alternative beep command and "echo foo | wall" prove.
Interestingly, Ubuntu can and does produce the system beep in two other instances:
1) Edit the grub menu at /etc/default /grub and remove the # hash at GRUB_INIT_TUNE="480 440 1" and you will get a beep when grub loads.
2) Press Backspace without entering your password at login, and you will get the error beep.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-28-generic 4.4.0-28.47
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: dv430uuyn 1784 F.... pulseaudio
/dev/snd/controlC0: dv430uuyn 1784 F.... pulseaudio
CurrentDesktop: Unity
Date: Wed Jul 6 14:00:50 2016
HibernationDevice: RESUME=UUID=e8206eff-651f-4207-b0a8-9c5a06959711
InstallationDate: Installed on 2016-06-24 (12 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
enp2s0 no wireless extensions.
lo no wireless extensions.
MachineType: Dell Inc. Vostro 430
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=c3a8f971-548b-4666-b865-6bf917bef1c9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-28-generic N/A
linux-backports-modules-4.4.0-28-generic N/A
linux-firmware 1.157.2
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/13/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.0
dmi.board.name: 054KM3
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:svnDellInc.:pnVostro430:pvr00:rvnDellInc.:rn054KM3:rvrA01:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 430
dmi.product.version: 00
dmi.sys.vendor: Dell Inc. |
This is my first ever bug report, so bear with me if I make mistakes.
System bell (aka PC speaker beep) is not working upon installing Ubuntu 16.04 Xenial Xerus.
The "beep" command has been installed and works, also "echo foo | wall" works. But "echo -e '\a'" and "printf '\a'" make no sound, nor does pressing the rubout or other keys in terminal and Gedit like it usually does.
lsmod shows pcspkr is loaded
****Note****
The symptoms are exactly the same as in bug #486154
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/486154
Just for the record, rmmod and reloading the pcspkr module, unblacklisting it, trying in vain to turn up the volume, and all the other usual steps are no longer relevant at this point. We are way beyond that here. Something very, very elusive in this 16.04 distro is blocking the bell. I suspect something new in 16.04 runs after you login which nullifies the standard error beep. Pressing down at the end in Gedit and the terminal also used to make the beep, but something is telling it not to anymore. The PC speaker works of course, as the alternative beep command and "echo foo | wall" prove.
Interestingly, Ubuntu can and does produce the system beep in two other instances:
1) Edit the grub menu at /etc/default /grub and remove the # hash at GRUB_INIT_TUNE="480 440 1" and you will get a beep when grub loads.
2) Press Backspace without entering your password at login, and you will get the error beep.
Description: Ubuntu 16.04 LTS
Release: 16.04
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-28-generic 4.4.0-28.47
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: dv430uuyn 1784 F.... pulseaudio
/dev/snd/controlC0: dv430uuyn 1784 F.... pulseaudio
CurrentDesktop: Unity
Date: Wed Jul 6 14:00:50 2016
HibernationDevice: RESUME=UUID=e8206eff-651f-4207-b0a8-9c5a06959711
InstallationDate: Installed on 2016-06-24 (12 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
enp2s0 no wireless extensions.
lo no wireless extensions.
MachineType: Dell Inc. Vostro 430
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=c3a8f971-548b-4666-b865-6bf917bef1c9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-28-generic N/A
linux-backports-modules-4.4.0-28-generic N/A
linux-firmware 1.157.2
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/13/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.0
dmi.board.name: 054KM3
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:svnDellInc.:pnVostro430:pvr00:rvnDellInc.:rn054KM3:rvrA01:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 430
dmi.product.version: 00
dmi.sys.vendor: Dell Inc. |
|
2016-07-07 14:37:01 |
Joseph Salisbury |
linux (Ubuntu): importance |
Undecided |
Medium |
|
2016-07-07 14:37:08 |
Joseph Salisbury |
linux (Ubuntu): status |
Confirmed |
Incomplete |
|
2016-07-08 11:47:17 |
Anthony |
attachment added |
|
changelog https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599599/+attachment/4697388/+files/linux-image-extra-4.4.0-28-generic_changelog.txt |
|
2016-07-08 12:38:46 |
Anthony |
tags |
amd64 apport-bug xenial |
kernel-bug-exists-upstream |
|
2016-07-08 12:52:15 |
Anthony |
tags |
kernel-bug-exists-upstream |
amd64 apport-bug kernel-bug-exists-upstream xenial |
|
2016-07-08 13:11:00 |
Anthony |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
2016-07-20 23:33:49 |
Anthony |
attachment added |
|
updates_term_log.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599599/+attachment/4704306/+files/updates_term_log.txt |
|
2016-08-30 08:25:13 |
Anthony |
linux (Ubuntu): status |
Confirmed |
Fix Released |
|
2017-09-30 05:02:49 |
Anthony |
linux (Ubuntu): status |
Fix Released |
Confirmed |
|