keyboard-setup.service is slow at boot. Do I need it?
up vote
2
down vote
favorite
My PC is running Debian Buster, and it's boot time seems to be slowed down by keyboard-setup.service. I understand that this is involved in setting up the keyboard for use at the console. The output of systemd-analyze blame is as below. I've checked it a number of times and it's always been similar.
5.549s keyboard-setup.service
5.063s dev-sda2.device
4.140s udisks2.service
3.565s accounts-daemon.service
3.487s console-kit-log-system-start.service
This makes me wonder why I need to spend 5.5 seconds setting up my keyboard every time I boot. Is keyboard-setup supposed to be this slow?
If yes, then why? What's it doing? And is it safe to just disable it?
If no, then what's going wrong and how should I go about fixing it?
Edit: systemd-analyse critical-chain
graphical.target @17.385s
└─gdm.service @15.588s +1.797s
└─rc-local.service @15.476s +110ms
└─network.target @15.475s
└─networking.service @14.971s +502ms
└─apparmor.service @8.262s +3.147s
└─local-fs.target @8.256s
└─boot-efi.mount @8.000s +255ms
└─local-fs-pre.target @7.971s
└─keyboard-setup.service @2.421s +5.549s
└─systemd-journald.socket @2.420s
└─system.slice @2.417s
└─-.slice @2.186s
systemd keyboard
asked Dec 29 '17 at 13:51
GKFX
120112
add a comment |
up vote
2
down vote
favorite
My PC is running Debian Buster, and it's boot time seems to be slowed down by keyboard-setup.service. I understand that this is involved in setting up the keyboard for use at the console. The output of systemd-analyze blame is as below. I've checked it a number of times and it's always been similar.
5.549s keyboard-setup.service
5.063s dev-sda2.device
4.140s udisks2.service
3.565s accounts-daemon.service
3.487s console-kit-log-system-start.service
This makes me wonder why I need to spend 5.5 seconds setting up my keyboard every time I boot. Is keyboard-setup supposed to be this slow?
If yes, then why? What's it doing? And is it safe to just disable it?
If no, then what's going wrong and how should I go about fixing it?
Edit: systemd-analyse critical-chain
graphical.target @17.385s
└─gdm.service @15.588s +1.797s
└─rc-local.service @15.476s +110ms
└─network.target @15.475s
└─networking.service @14.971s +502ms
└─apparmor.service @8.262s +3.147s
└─local-fs.target @8.256s
└─boot-efi.mount @8.000s +255ms
└─local-fs-pre.target @7.971s
└─keyboard-setup.service @2.421s +5.549s
└─systemd-journald.socket @2.420s
└─system.slice @2.417s
└─-.slice @2.186s
systemd keyboard
asked Dec 29 '17 at 13:51
GKFX
120112
The service is taking a long time to timeout. Try to: edit /lib/systemd/system/keyboard-setup.service, and adding the line: TimeoutStartSec=10sec after the last line of [Service] bit.
– vfbsilva
Dec 29 '17 at 14:07
1
You would have a better question for editing the output ofsystemd-analyze critical-chaininto it.
– JdeBP
Dec 29 '17 at 14:25
@vfbsilva Unlike askubuntu.com/q/919428/309061, the service is taking 5 seconds to start, not 20. AddingTimeoutStartSec=10secdoesn't have any effect.
– GKFX
Dec 29 '17 at 17:17
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
My PC is running Debian Buster, and it's boot time seems to be slowed down by keyboard-setup.service. I understand that this is involved in setting up the keyboard for use at the console. The output of systemd-analyze blame is as below. I've checked it a number of times and it's always been similar.
5.549s keyboard-setup.service
5.063s dev-sda2.device
4.140s udisks2.service
3.565s accounts-daemon.service
3.487s console-kit-log-system-start.service
This makes me wonder why I need to spend 5.5 seconds setting up my keyboard every time I boot. Is keyboard-setup supposed to be this slow?
If yes, then why? What's it doing? And is it safe to just disable it?
If no, then what's going wrong and how should I go about fixing it?
Edit: systemd-analyse critical-chain
graphical.target @17.385s
└─gdm.service @15.588s +1.797s
└─rc-local.service @15.476s +110ms
└─network.target @15.475s
└─networking.service @14.971s +502ms
└─apparmor.service @8.262s +3.147s
└─local-fs.target @8.256s
└─boot-efi.mount @8.000s +255ms
└─local-fs-pre.target @7.971s
└─keyboard-setup.service @2.421s +5.549s
└─systemd-journald.socket @2.420s
└─system.slice @2.417s
└─-.slice @2.186s
systemd keyboard
asked Dec 29 '17 at 13:51
GKFX
120112
My PC is running Debian Buster, and it's boot time seems to be slowed down by keyboard-setup.service. I understand that this is involved in setting up the keyboard for use at the console. The output of systemd-analyze blame is as below. I've checked it a number of times and it's always been similar.
5.549s keyboard-setup.service
5.063s dev-sda2.device
4.140s udisks2.service
3.565s accounts-daemon.service
3.487s console-kit-log-system-start.service
This makes me wonder why I need to spend 5.5 seconds setting up my keyboard every time I boot. Is keyboard-setup supposed to be this slow?
If yes, then why? What's it doing? And is it safe to just disable it?
If no, then what's going wrong and how should I go about fixing it?
Edit: systemd-analyse critical-chain
graphical.target @17.385s
└─gdm.service @15.588s +1.797s
└─rc-local.service @15.476s +110ms
└─network.target @15.475s
└─networking.service @14.971s +502ms
└─apparmor.service @8.262s +3.147s
└─local-fs.target @8.256s
└─boot-efi.mount @8.000s +255ms
└─local-fs-pre.target @7.971s
└─keyboard-setup.service @2.421s +5.549s
└─systemd-journald.socket @2.420s
└─system.slice @2.417s
└─-.slice @2.186s
systemd keyboard
systemd keyboard
asked Dec 29 '17 at 13:51
GKFX
120112
asked Dec 29 '17 at 13:51
GKFX
120112
edited Dec 29 '17 at 17:10
asked Dec 29 '17 at 13:51
GKFX
120112
asked Dec 29 '17 at 13:51
GKFX
120112
asked Dec 29 '17 at 13:51
GKFX
120112
120112
The service is taking a long time to timeout. Try to: edit /lib/systemd/system/keyboard-setup.service, and adding the line: TimeoutStartSec=10sec after the last line of [Service] bit.
– vfbsilva
Dec 29 '17 at 14:07
1
You would have a better question for editing the output ofsystemd-analyze critical-chaininto it.
– JdeBP
Dec 29 '17 at 14:25
@vfbsilva Unlike askubuntu.com/q/919428/309061, the service is taking 5 seconds to start, not 20. AddingTimeoutStartSec=10secdoesn't have any effect.
– GKFX
Dec 29 '17 at 17:17
add a comment |
The service is taking a long time to timeout. Try to: edit /lib/systemd/system/keyboard-setup.service, and adding the line: TimeoutStartSec=10sec after the last line of [Service] bit.
– vfbsilva
Dec 29 '17 at 14:07
1
You would have a better question for editing the output ofsystemd-analyze critical-chaininto it.
– JdeBP
Dec 29 '17 at 14:25
@vfbsilva Unlike askubuntu.com/q/919428/309061, the service is taking 5 seconds to start, not 20. AddingTimeoutStartSec=10secdoesn't have any effect.
– GKFX
Dec 29 '17 at 17:17
The service is taking a long time to timeout. Try to: edit /lib/systemd/system/keyboard-setup.service, and adding the line: TimeoutStartSec=10sec after the last line of [Service] bit.
– vfbsilva
Dec 29 '17 at 14:07
The service is taking a long time to timeout. Try to: edit /lib/systemd/system/keyboard-setup.service, and adding the line: TimeoutStartSec=10sec after the last line of [Service] bit.
– vfbsilva
Dec 29 '17 at 14:07
1
1
You would have a better question for editing the output of
systemd-analyze critical-chain into it.– JdeBP
Dec 29 '17 at 14:25
You would have a better question for editing the output of
systemd-analyze critical-chain into it.– JdeBP
Dec 29 '17 at 14:25
@vfbsilva Unlike askubuntu.com/q/919428/309061, the service is taking 5 seconds to start, not 20. Adding
TimeoutStartSec=10sec doesn't have any effect.– GKFX
Dec 29 '17 at 17:17
@vfbsilva Unlike askubuntu.com/q/919428/309061, the service is taking 5 seconds to start, not 20. Adding
TimeoutStartSec=10sec doesn't have any effect.– GKFX
Dec 29 '17 at 17:17
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
The best suggestion is to put a timeout limitation for the service to control the time it consumes at start up.
You may do this with two methods:
SERVICETOFIX="keyboard-setup.service"
sudo mkdir -p "/etc/systemd/system/$SERVICETOFIX.d"
sudo echo -e "[Service]nTimeoutStartSec=10" | tee "/etc/systemd/system/$SERVICETOFIX.d/reduce-timeout.conf"
Method 2: I personally prefer this method:
First run sudo systemctl edit keyboard-setup.service, and then in the editor add the below and then save and exit the editor.
[Service]
TimeoutStartSec=10
edited yesterday
G-Man
12.8k93164
answered yesterday
AndyBaba
101
New contributor
AndyBaba is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Hi AndyBaba! Thanks for the advice, but it was made clear in the comments on the question why this wouldn't work.
– GKFX
yesterday
Hi GKFX:) I guess in that regard you are right, however this is still a helpful tip to use for similar cases caused by other services. I do apologize if my answer if its not helpful though.
– AndyBaba
19 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f413656%2fkeyboard-setup-service-is-slow-at-boot-do-i-need-it%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The best suggestion is to put a timeout limitation for the service to control the time it consumes at start up.
You may do this with two methods:
SERVICETOFIX="keyboard-setup.service"
sudo mkdir -p "/etc/systemd/system/$SERVICETOFIX.d"
sudo echo -e "[Service]nTimeoutStartSec=10" | tee "/etc/systemd/system/$SERVICETOFIX.d/reduce-timeout.conf"
Method 2: I personally prefer this method:
First run sudo systemctl edit keyboard-setup.service, and then in the editor add the below and then save and exit the editor.
[Service]
TimeoutStartSec=10
edited yesterday
G-Man
12.8k93164
answered yesterday
AndyBaba
101
New contributor
AndyBaba is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Hi AndyBaba! Thanks for the advice, but it was made clear in the comments on the question why this wouldn't work.
– GKFX
yesterday
Hi GKFX:) I guess in that regard you are right, however this is still a helpful tip to use for similar cases caused by other services. I do apologize if my answer if its not helpful though.
– AndyBaba
19 hours ago
add a comment |
up vote
0
down vote
The best suggestion is to put a timeout limitation for the service to control the time it consumes at start up.
You may do this with two methods:
SERVICETOFIX="keyboard-setup.service"
sudo mkdir -p "/etc/systemd/system/$SERVICETOFIX.d"
sudo echo -e "[Service]nTimeoutStartSec=10" | tee "/etc/systemd/system/$SERVICETOFIX.d/reduce-timeout.conf"
Method 2: I personally prefer this method:
First run sudo systemctl edit keyboard-setup.service, and then in the editor add the below and then save and exit the editor.
[Service]
TimeoutStartSec=10
edited yesterday
G-Man
12.8k93164
answered yesterday
AndyBaba
101
New contributor
AndyBaba is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Hi AndyBaba! Thanks for the advice, but it was made clear in the comments on the question why this wouldn't work.
– GKFX
yesterday
Hi GKFX:) I guess in that regard you are right, however this is still a helpful tip to use for similar cases caused by other services. I do apologize if my answer if its not helpful though.
– AndyBaba
19 hours ago
add a comment |
up vote
0
down vote
up vote
0
down vote
The best suggestion is to put a timeout limitation for the service to control the time it consumes at start up.
You may do this with two methods:
SERVICETOFIX="keyboard-setup.service"
sudo mkdir -p "/etc/systemd/system/$SERVICETOFIX.d"
sudo echo -e "[Service]nTimeoutStartSec=10" | tee "/etc/systemd/system/$SERVICETOFIX.d/reduce-timeout.conf"
Method 2: I personally prefer this method:
First run sudo systemctl edit keyboard-setup.service, and then in the editor add the below and then save and exit the editor.
[Service]
TimeoutStartSec=10
edited yesterday
G-Man
12.8k93164
answered yesterday
AndyBaba
101
New contributor
AndyBaba is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
The best suggestion is to put a timeout limitation for the service to control the time it consumes at start up.
You may do this with two methods:
SERVICETOFIX="keyboard-setup.service"
sudo mkdir -p "/etc/systemd/system/$SERVICETOFIX.d"
sudo echo -e "[Service]nTimeoutStartSec=10" | tee "/etc/systemd/system/$SERVICETOFIX.d/reduce-timeout.conf"
Method 2: I personally prefer this method:
First run sudo systemctl edit keyboard-setup.service, and then in the editor add the below and then save and exit the editor.
[Service]
TimeoutStartSec=10
edited yesterday
G-Man
12.8k93164
answered yesterday
AndyBaba
101
New contributor
AndyBaba is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited yesterday
G-Man
12.8k93164
edited yesterday
G-Man
12.8k93164
edited yesterday
G-Man
12.8k93164
12.8k93164
answered yesterday
AndyBaba
101
New contributor
AndyBaba is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered yesterday
AndyBaba
101
answered yesterday
AndyBaba
101
101
New contributor
AndyBaba is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
AndyBaba is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
AndyBaba is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Hi AndyBaba! Thanks for the advice, but it was made clear in the comments on the question why this wouldn't work.
– GKFX
yesterday
Hi GKFX:) I guess in that regard you are right, however this is still a helpful tip to use for similar cases caused by other services. I do apologize if my answer if its not helpful though.
– AndyBaba
19 hours ago
add a comment |
Hi AndyBaba! Thanks for the advice, but it was made clear in the comments on the question why this wouldn't work.
– GKFX
yesterday
Hi GKFX:) I guess in that regard you are right, however this is still a helpful tip to use for similar cases caused by other services. I do apologize if my answer if its not helpful though.
– AndyBaba
19 hours ago
Hi AndyBaba! Thanks for the advice, but it was made clear in the comments on the question why this wouldn't work.
– GKFX
yesterday
Hi AndyBaba! Thanks for the advice, but it was made clear in the comments on the question why this wouldn't work.
– GKFX
yesterday
Hi GKFX:) I guess in that regard you are right, however this is still a helpful tip to use for similar cases caused by other services. I do apologize if my answer if its not helpful though.
– AndyBaba
19 hours ago
Hi GKFX:) I guess in that regard you are right, however this is still a helpful tip to use for similar cases caused by other services. I do apologize if my answer if its not helpful though.
– AndyBaba
19 hours ago
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f413656%2fkeyboard-setup-service-is-slow-at-boot-do-i-need-it%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
The service is taking a long time to timeout. Try to: edit /lib/systemd/system/keyboard-setup.service, and adding the line: TimeoutStartSec=10sec after the last line of [Service] bit.
– vfbsilva
Dec 29 '17 at 14:07
1
You would have a better question for editing the output of
systemd-analyze critical-chaininto it.– JdeBP
Dec 29 '17 at 14:25
@vfbsilva Unlike askubuntu.com/q/919428/309061, the service is taking 5 seconds to start, not 20. Adding
TimeoutStartSec=10secdoesn't have any effect.– GKFX
Dec 29 '17 at 17:17