Mdthbs

Is the Starlink array really visible from Earth?

Why are C64 games inconsistent with which joystick port they use?

Why colon to denote that a value belongs to a type?

Which is the common name of Mind Flayers?

Image processing: Removal of two spots in fundus images

Construct a word ladder

Why does the 6502 have the BIT instruction?

Compactness of finite sets

Where have Brexit voters gone?

Is the Indo-European language family made up?

Adding spaces to string based on list

Popcorn is the only acceptable snack to consume while watching a movie

Text at the right of icon

My employer faked my resume to acquire projects

Is neural networks training done one-by-one?

Can I install both XCode & Android Studio on MacBook Air with only 8 GB of Ram

How should I introduce map drawing to my players?

A steel cutting sword?

How to respond to an upset student?

Is "cool" appropriate or offensive to use in IMs?

What is the largest (size) solid object ever dropped from an airplane to impact the ground in freefall?

Does Nitrogen inside commercial airliner wheels prevent blowouts on touchdown?

Why doesn't the Earth accelerate towards the Moon?

Why is this Simple Puzzle impossible to solve?

keyboard-setup.service is slow at boot. Do I need it?

Slow keyboard response in some DistrosPS/2 Keyboard & Mouse not working AFTER bootsystemd slow boot - systemd-tmpfiles-setupMedia key problems with Microsoft keyboardMy keyboard generates spurious eventsChange order of startup services with systemdKeyboard LEDs versus Laptop LEDskeyboard remap has killed keyboardSlow boot time due to firmware delayUSB keyboard sometimes does not work on boot

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

2

1

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

share|improve this question

edited Dec 29 '17 at 17:10

GKFX

asked Dec 29 '17 at 13:51

GKFXGKFX

120112

bumped to the homepage by Community♦ 1 hour ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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-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
  

  
  
  
  

add a comment | 

2

1

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

share|improve this question

edited Dec 29 '17 at 17:10

GKFX

asked Dec 29 '17 at 13:51

GKFXGKFX

120112

bumped to the homepage by Community♦ 1 hour ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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-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
  

  
  
  
  

add a comment | 

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

share|improve this question

edited Dec 29 '17 at 17:10

GKFX

asked Dec 29 '17 at 13:51

GKFXGKFX

120112

 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

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

share|improve this question

edited Dec 29 '17 at 17:10

GKFX

asked Dec 29 '17 at 13:51

GKFXGKFX

120112

share|improve this question

edited Dec 29 '17 at 17:10

GKFX

asked Dec 29 '17 at 13:51

GKFXGKFX

120112

asked Dec 29 '17 at 13:51

GKFXGKFX

120112

asked Dec 29 '17 at 13:51

GKFXGKFX

120112

1 Answer
1

active

oldest

votes

0

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

share|improve this answer

edited Dec 15 '18 at 17:56

G-Man

14.5k94174

answered Dec 15 '18 at 17:45

AndyBabaAndyBaba

101

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hi AndyBaba! Thanks for the advice, but it was made clear in the comments on the question why this wouldn't work.
  
  – GKFX
  Dec 15 '18 at 20:28
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  Dec 16 '18 at 10:32
  
  
  

  
  
  
  

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',
autoActivateHeartbeat: false,
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
});


}
});

draft saved

draft discarded

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

Name

Email

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

Name

Email

Required, but never shown

0

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

share|improve this answer

edited Dec 15 '18 at 17:56

G-Man

14.5k94174

answered Dec 15 '18 at 17:45

AndyBabaAndyBaba

101

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hi AndyBaba! Thanks for the advice, but it was made clear in the comments on the question why this wouldn't work.
  
  – GKFX
  Dec 15 '18 at 20:28
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  Dec 16 '18 at 10:32
  
  
  

  
  
  
  

add a comment | 

0

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

share|improve this answer

edited Dec 15 '18 at 17:56

G-Man

14.5k94174

answered Dec 15 '18 at 17:45

AndyBabaAndyBaba

101

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hi AndyBaba! Thanks for the advice, but it was made clear in the comments on the question why this wouldn't work.
  
  – GKFX
  Dec 15 '18 at 20:28
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  Dec 16 '18 at 10:32
  
  
  

  
  
  
  

add a comment | 

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

share|improve this answer

edited Dec 15 '18 at 17:56

G-Man

14.5k94174

answered Dec 15 '18 at 17:45

AndyBabaAndyBaba

101

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"

[Service]

TimeoutStartSec=10

share|improve this answer

edited Dec 15 '18 at 17:56

G-Man

14.5k94174

answered Dec 15 '18 at 17:45

AndyBabaAndyBaba

101

edited Dec 15 '18 at 17:56

G-Man

14.5k94174

edited Dec 15 '18 at 17:56

G-Man

14.5k94174

answered Dec 15 '18 at 17:45

AndyBabaAndyBaba

101

answered Dec 15 '18 at 17:45

AndyBabaAndyBaba

101