Volume buttons not working in 14.04
Multi tool use
up vote
12
down vote
favorite
When using the volume buttons (+, -, mute) there is no reaction, neither on laptop keyboard nor on USB keyboard. No popup, no volume change, and no sound indication.
Volume control with the mouse works fine.
The buttons are working and get recognized:
Checked with keyboard system settings tool: they get recognized by the tool both from the laptop directly as well as from my USB keyboard.
Who can help?
sound keyboard 14.04
add a comment |
up vote
12
down vote
favorite
When using the volume buttons (+, -, mute) there is no reaction, neither on laptop keyboard nor on USB keyboard. No popup, no volume change, and no sound indication.
Volume control with the mouse works fine.
The buttons are working and get recognized:
Checked with keyboard system settings tool: they get recognized by the tool both from the laptop directly as well as from my USB keyboard.
Who can help?
sound keyboard 14.04
I had to bookmark this question because this happens so much.
– Matt G
Jan 25 '17 at 17:58
add a comment |
up vote
12
down vote
favorite
up vote
12
down vote
favorite
When using the volume buttons (+, -, mute) there is no reaction, neither on laptop keyboard nor on USB keyboard. No popup, no volume change, and no sound indication.
Volume control with the mouse works fine.
The buttons are working and get recognized:
Checked with keyboard system settings tool: they get recognized by the tool both from the laptop directly as well as from my USB keyboard.
Who can help?
sound keyboard 14.04
When using the volume buttons (+, -, mute) there is no reaction, neither on laptop keyboard nor on USB keyboard. No popup, no volume change, and no sound indication.
Volume control with the mouse works fine.
The buttons are working and get recognized:
Checked with keyboard system settings tool: they get recognized by the tool both from the laptop directly as well as from my USB keyboard.
Who can help?
sound keyboard 14.04
sound keyboard 14.04
edited May 5 '14 at 13:09
jkt123
2,5741321
2,5741321
asked May 5 '14 at 12:51
ohoservices
63116
63116
I had to bookmark this question because this happens so much.
– Matt G
Jan 25 '17 at 17:58
add a comment |
I had to bookmark this question because this happens so much.
– Matt G
Jan 25 '17 at 17:58
I had to bookmark this question because this happens so much.
– Matt G
Jan 25 '17 at 17:58
I had to bookmark this question because this happens so much.
– Matt G
Jan 25 '17 at 17:58
add a comment |
4 Answers
4
active
oldest
votes
up vote
29
down vote
accepted
Looks like a known bug on Launchpad.
According to the thread, the current fix is to...
- Open terminal (Ctrl+Alt+T)
Type the following three commands to reset the volume/mute keys on your keyboard...
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-up
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-down
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-mute
It worked for me, hope it works for you too.
3
Mine stopped working right now and this solution didn't fix it
– matteo
Aug 5 '14 at 21:27
Doesn't work for me. Creating new user works (with original volume keys) And for the existing user ONLY different keys work. So strange.
– niry
May 7 '15 at 6:20
As for my previous comment, this is after upgrading to 15.04.
– niry
May 7 '15 at 6:33
add a comment |
up vote
7
down vote
If resetting the keyboard shortcuts didn't work (such as in my case) move or delete the .gconf directory:
cd && mv .gconf .gconf.old
Logout and log back in again.
3
Also take note that some apps may store settings in this directory, in which case they will be lost. Guake is one program that stores settings there.
– Blossoming_Flower
May 11 '15 at 14:40
add a comment |
up vote
2
down vote
Additionally, to fix the mute button, execute
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-mute
from a shell. Worked for me, hope it helps you too.
thank you worked perfect ... that was the last missing part.
– ohoservices
Jul 23 '14 at 22:37
add a comment |
up vote
1
down vote
I think I may have fixed this by reinstalling lightdm (Be careful to reinstall and not to remove it since that might cause issues with rebooting). None of the other solutions worked for me.
sudo apt install --reinstall lightdm
update:
This happened again and this time reinstalling lightdm didn't solve the problem. What worked instead was this:
1) I installed dconf-editor and reset the value /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ to default, keeping a copy of its value in a file.
2) After logging out and logging in again I reinserted the original value (i.e., my custom shortcuts). Now, everything seems to work again.
This problem keeps on occurring and this time again the previous solutions didn't work. Killing unity-settings-daemon solved the problem. It remains a mystery to me how to prevent this from re-occurring. Any pointers would be much appreciated. I should add that I run Ubuntu 16.10.
– bilbo
Feb 12 '17 at 6:15
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f461093%2fvolume-buttons-not-working-in-14-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
29
down vote
accepted
Looks like a known bug on Launchpad.
According to the thread, the current fix is to...
- Open terminal (Ctrl+Alt+T)
Type the following three commands to reset the volume/mute keys on your keyboard...
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-up
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-down
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-mute
It worked for me, hope it works for you too.
3
Mine stopped working right now and this solution didn't fix it
– matteo
Aug 5 '14 at 21:27
Doesn't work for me. Creating new user works (with original volume keys) And for the existing user ONLY different keys work. So strange.
– niry
May 7 '15 at 6:20
As for my previous comment, this is after upgrading to 15.04.
– niry
May 7 '15 at 6:33
add a comment |
up vote
29
down vote
accepted
Looks like a known bug on Launchpad.
According to the thread, the current fix is to...
- Open terminal (Ctrl+Alt+T)
Type the following three commands to reset the volume/mute keys on your keyboard...
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-up
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-down
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-mute
It worked for me, hope it works for you too.
3
Mine stopped working right now and this solution didn't fix it
– matteo
Aug 5 '14 at 21:27
Doesn't work for me. Creating new user works (with original volume keys) And for the existing user ONLY different keys work. So strange.
– niry
May 7 '15 at 6:20
As for my previous comment, this is after upgrading to 15.04.
– niry
May 7 '15 at 6:33
add a comment |
up vote
29
down vote
accepted
up vote
29
down vote
accepted
Looks like a known bug on Launchpad.
According to the thread, the current fix is to...
- Open terminal (Ctrl+Alt+T)
Type the following three commands to reset the volume/mute keys on your keyboard...
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-up
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-down
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-mute
It worked for me, hope it works for you too.
Looks like a known bug on Launchpad.
According to the thread, the current fix is to...
- Open terminal (Ctrl+Alt+T)
Type the following three commands to reset the volume/mute keys on your keyboard...
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-up
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-down
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-mute
It worked for me, hope it works for you too.
edited Aug 13 '14 at 15:33
answered May 17 '14 at 3:44
jakesantos
1,240910
1,240910
3
Mine stopped working right now and this solution didn't fix it
– matteo
Aug 5 '14 at 21:27
Doesn't work for me. Creating new user works (with original volume keys) And for the existing user ONLY different keys work. So strange.
– niry
May 7 '15 at 6:20
As for my previous comment, this is after upgrading to 15.04.
– niry
May 7 '15 at 6:33
add a comment |
3
Mine stopped working right now and this solution didn't fix it
– matteo
Aug 5 '14 at 21:27
Doesn't work for me. Creating new user works (with original volume keys) And for the existing user ONLY different keys work. So strange.
– niry
May 7 '15 at 6:20
As for my previous comment, this is after upgrading to 15.04.
– niry
May 7 '15 at 6:33
3
3
Mine stopped working right now and this solution didn't fix it
– matteo
Aug 5 '14 at 21:27
Mine stopped working right now and this solution didn't fix it
– matteo
Aug 5 '14 at 21:27
Doesn't work for me. Creating new user works (with original volume keys) And for the existing user ONLY different keys work. So strange.
– niry
May 7 '15 at 6:20
Doesn't work for me. Creating new user works (with original volume keys) And for the existing user ONLY different keys work. So strange.
– niry
May 7 '15 at 6:20
As for my previous comment, this is after upgrading to 15.04.
– niry
May 7 '15 at 6:33
As for my previous comment, this is after upgrading to 15.04.
– niry
May 7 '15 at 6:33
add a comment |
up vote
7
down vote
If resetting the keyboard shortcuts didn't work (such as in my case) move or delete the .gconf directory:
cd && mv .gconf .gconf.old
Logout and log back in again.
3
Also take note that some apps may store settings in this directory, in which case they will be lost. Guake is one program that stores settings there.
– Blossoming_Flower
May 11 '15 at 14:40
add a comment |
up vote
7
down vote
If resetting the keyboard shortcuts didn't work (such as in my case) move or delete the .gconf directory:
cd && mv .gconf .gconf.old
Logout and log back in again.
3
Also take note that some apps may store settings in this directory, in which case they will be lost. Guake is one program that stores settings there.
– Blossoming_Flower
May 11 '15 at 14:40
add a comment |
up vote
7
down vote
up vote
7
down vote
If resetting the keyboard shortcuts didn't work (such as in my case) move or delete the .gconf directory:
cd && mv .gconf .gconf.old
Logout and log back in again.
If resetting the keyboard shortcuts didn't work (such as in my case) move or delete the .gconf directory:
cd && mv .gconf .gconf.old
Logout and log back in again.
edited Dec 2 at 11:17
Community♦
1
1
answered May 7 '15 at 6:49
niry
442311
442311
3
Also take note that some apps may store settings in this directory, in which case they will be lost. Guake is one program that stores settings there.
– Blossoming_Flower
May 11 '15 at 14:40
add a comment |
3
Also take note that some apps may store settings in this directory, in which case they will be lost. Guake is one program that stores settings there.
– Blossoming_Flower
May 11 '15 at 14:40
3
3
Also take note that some apps may store settings in this directory, in which case they will be lost. Guake is one program that stores settings there.
– Blossoming_Flower
May 11 '15 at 14:40
Also take note that some apps may store settings in this directory, in which case they will be lost. Guake is one program that stores settings there.
– Blossoming_Flower
May 11 '15 at 14:40
add a comment |
up vote
2
down vote
Additionally, to fix the mute button, execute
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-mute
from a shell. Worked for me, hope it helps you too.
thank you worked perfect ... that was the last missing part.
– ohoservices
Jul 23 '14 at 22:37
add a comment |
up vote
2
down vote
Additionally, to fix the mute button, execute
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-mute
from a shell. Worked for me, hope it helps you too.
thank you worked perfect ... that was the last missing part.
– ohoservices
Jul 23 '14 at 22:37
add a comment |
up vote
2
down vote
up vote
2
down vote
Additionally, to fix the mute button, execute
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-mute
from a shell. Worked for me, hope it helps you too.
Additionally, to fix the mute button, execute
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-mute
from a shell. Worked for me, hope it helps you too.
answered Jul 22 '14 at 13:40
spqpad
314
314
thank you worked perfect ... that was the last missing part.
– ohoservices
Jul 23 '14 at 22:37
add a comment |
thank you worked perfect ... that was the last missing part.
– ohoservices
Jul 23 '14 at 22:37
thank you worked perfect ... that was the last missing part.
– ohoservices
Jul 23 '14 at 22:37
thank you worked perfect ... that was the last missing part.
– ohoservices
Jul 23 '14 at 22:37
add a comment |
up vote
1
down vote
I think I may have fixed this by reinstalling lightdm (Be careful to reinstall and not to remove it since that might cause issues with rebooting). None of the other solutions worked for me.
sudo apt install --reinstall lightdm
update:
This happened again and this time reinstalling lightdm didn't solve the problem. What worked instead was this:
1) I installed dconf-editor and reset the value /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ to default, keeping a copy of its value in a file.
2) After logging out and logging in again I reinserted the original value (i.e., my custom shortcuts). Now, everything seems to work again.
This problem keeps on occurring and this time again the previous solutions didn't work. Killing unity-settings-daemon solved the problem. It remains a mystery to me how to prevent this from re-occurring. Any pointers would be much appreciated. I should add that I run Ubuntu 16.10.
– bilbo
Feb 12 '17 at 6:15
add a comment |
up vote
1
down vote
I think I may have fixed this by reinstalling lightdm (Be careful to reinstall and not to remove it since that might cause issues with rebooting). None of the other solutions worked for me.
sudo apt install --reinstall lightdm
update:
This happened again and this time reinstalling lightdm didn't solve the problem. What worked instead was this:
1) I installed dconf-editor and reset the value /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ to default, keeping a copy of its value in a file.
2) After logging out and logging in again I reinserted the original value (i.e., my custom shortcuts). Now, everything seems to work again.
This problem keeps on occurring and this time again the previous solutions didn't work. Killing unity-settings-daemon solved the problem. It remains a mystery to me how to prevent this from re-occurring. Any pointers would be much appreciated. I should add that I run Ubuntu 16.10.
– bilbo
Feb 12 '17 at 6:15
add a comment |
up vote
1
down vote
up vote
1
down vote
I think I may have fixed this by reinstalling lightdm (Be careful to reinstall and not to remove it since that might cause issues with rebooting). None of the other solutions worked for me.
sudo apt install --reinstall lightdm
update:
This happened again and this time reinstalling lightdm didn't solve the problem. What worked instead was this:
1) I installed dconf-editor and reset the value /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ to default, keeping a copy of its value in a file.
2) After logging out and logging in again I reinserted the original value (i.e., my custom shortcuts). Now, everything seems to work again.
I think I may have fixed this by reinstalling lightdm (Be careful to reinstall and not to remove it since that might cause issues with rebooting). None of the other solutions worked for me.
sudo apt install --reinstall lightdm
update:
This happened again and this time reinstalling lightdm didn't solve the problem. What worked instead was this:
1) I installed dconf-editor and reset the value /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ to default, keeping a copy of its value in a file.
2) After logging out and logging in again I reinserted the original value (i.e., my custom shortcuts). Now, everything seems to work again.
edited Jan 30 '17 at 9:33
answered Jan 29 '17 at 5:26
bilbo
112
112
This problem keeps on occurring and this time again the previous solutions didn't work. Killing unity-settings-daemon solved the problem. It remains a mystery to me how to prevent this from re-occurring. Any pointers would be much appreciated. I should add that I run Ubuntu 16.10.
– bilbo
Feb 12 '17 at 6:15
add a comment |
This problem keeps on occurring and this time again the previous solutions didn't work. Killing unity-settings-daemon solved the problem. It remains a mystery to me how to prevent this from re-occurring. Any pointers would be much appreciated. I should add that I run Ubuntu 16.10.
– bilbo
Feb 12 '17 at 6:15
This problem keeps on occurring and this time again the previous solutions didn't work. Killing unity-settings-daemon solved the problem. It remains a mystery to me how to prevent this from re-occurring. Any pointers would be much appreciated. I should add that I run Ubuntu 16.10.
– bilbo
Feb 12 '17 at 6:15
This problem keeps on occurring and this time again the previous solutions didn't work. Killing unity-settings-daemon solved the problem. It remains a mystery to me how to prevent this from re-occurring. Any pointers would be much appreciated. I should add that I run Ubuntu 16.10.
– bilbo
Feb 12 '17 at 6:15
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f461093%2fvolume-buttons-not-working-in-14-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
iXyMiGa6BiIoHiEwoiI1JzdSLjScplNrKJs6hCVEDOCB2xTM c,EI A60ZESNE9V 1 B
I had to bookmark this question because this happens so much.
– Matt G
Jan 25 '17 at 17:58