It takes forever to login
1
I'm using Debian testing with Gnome. For some reason it takes around a three minutes to login, after I have typed in the password and pressed enter. What could the reason be? I would love to provide more details, but I have no idea about where to even start.
On demand:
$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 klutt-desktop.klutt klutt-desktop
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
On demand 2:
$ systemd-analyze blame | head -n3
1min 25.769s ssh.service
6.764s NetworkManager-wait-online.service
612ms udisks2.service
Seems to be ssh. Checking journaltcl
$ sudo journalctl | grep ssh
Dec 17 10:09:53 klutt-desktop systemd[828]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Dec 17 10:10:03 klutt-desktop systemd[1126]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Dec 17 10:11:22 klutt-desktop systemd[1]: ssh.service: Start-pre operation timed out. Terminating.
Dec 17 10:11:22 klutt-desktop systemd[1]: ssh.service: Failed with result 'timeout'.
Dec 17 10:11:22 klutt-desktop systemd[1]: ssh.service: Service RestartSec=100ms expired, scheduling restart.
Dec 17 10:11:22 klutt-desktop systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1.
Dec 17 10:12:48 klutt-desktop sshd[1151]: Server listening on 0.0.0.0 port 22.
Dec 17 10:12:48 klutt-desktop sshd[1151]: Server listening on :: port 22.
Dec 17 10:12:50 klutt-desktop gnome-keyring-ssh.desktop[1232]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
A piece from journalctl from a later reboot, after I ran systemctl disable ssh.service:
Dec 17 11:12:37 klutt-desktop systemd[1]: Startup finished in 3.587s (kernel) + 13.916s (userspace) = 17.504s.
Dec 17 11:12:56 klutt-desktop systemd-timesyncd[696]: Synchronized to time server 79.136.86.176:123 (2.debian.pool.
Dec 17 11:12:57 klutt-desktop dbus-daemon[740]: [system] Failed to activate service 'org.bluez': timed out (service
Dec 17 11:12:57 klutt-desktop pulseaudio[874]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freed
Dec 17 11:13:33 klutt-desktop geoclue[923]: Service not used for 60 seconds. Shutting down..
Dec 17 11:13:34 klutt-desktop realmd[1043]: quitting realmd service after timeout
Dec 17 11:13:34 klutt-desktop realmd[1043]: stopping service
Dec 17 11:15:17 klutt-desktop kernel: random: crng init done
geoclue and realmd seems to be candidates.
linux debian gnome gnome3 startup
asked Dec 17 at 7:57
Broman
159111
|
show 6 more comments
1
I'm using Debian testing with Gnome. For some reason it takes around a three minutes to login, after I have typed in the password and pressed enter. What could the reason be? I would love to provide more details, but I have no idea about where to even start.
On demand:
$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 klutt-desktop.klutt klutt-desktop
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
On demand 2:
$ systemd-analyze blame | head -n3
1min 25.769s ssh.service
6.764s NetworkManager-wait-online.service
612ms udisks2.service
Seems to be ssh. Checking journaltcl
$ sudo journalctl | grep ssh
Dec 17 10:09:53 klutt-desktop systemd[828]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Dec 17 10:10:03 klutt-desktop systemd[1126]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Dec 17 10:11:22 klutt-desktop systemd[1]: ssh.service: Start-pre operation timed out. Terminating.
Dec 17 10:11:22 klutt-desktop systemd[1]: ssh.service: Failed with result 'timeout'.
Dec 17 10:11:22 klutt-desktop systemd[1]: ssh.service: Service RestartSec=100ms expired, scheduling restart.
Dec 17 10:11:22 klutt-desktop systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1.
Dec 17 10:12:48 klutt-desktop sshd[1151]: Server listening on 0.0.0.0 port 22.
Dec 17 10:12:48 klutt-desktop sshd[1151]: Server listening on :: port 22.
Dec 17 10:12:50 klutt-desktop gnome-keyring-ssh.desktop[1232]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
A piece from journalctl from a later reboot, after I ran systemctl disable ssh.service:
Dec 17 11:12:37 klutt-desktop systemd[1]: Startup finished in 3.587s (kernel) + 13.916s (userspace) = 17.504s.
Dec 17 11:12:56 klutt-desktop systemd-timesyncd[696]: Synchronized to time server 79.136.86.176:123 (2.debian.pool.
Dec 17 11:12:57 klutt-desktop dbus-daemon[740]: [system] Failed to activate service 'org.bluez': timed out (service
Dec 17 11:12:57 klutt-desktop pulseaudio[874]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freed
Dec 17 11:13:33 klutt-desktop geoclue[923]: Service not used for 60 seconds. Shutting down..
Dec 17 11:13:34 klutt-desktop realmd[1043]: quitting realmd service after timeout
Dec 17 11:13:34 klutt-desktop realmd[1043]: stopping service
Dec 17 11:15:17 klutt-desktop kernel: random: crng init done
geoclue and realmd seems to be candidates.
linux debian gnome gnome3 startup
asked Dec 17 at 7:57
Broman
159111
1
"Around a minute"? 30 seconds is the default timeout for a failed DNS lookup. Perhaps you're missing an127.0.0.1and::1stanza in/etc/hostsor similar...
– Shadur
Dec 17 at 9:15
1
@jimmij Here is the output. I did not know what to look for: pastebin.com/NKxvpLqx
– Broman
Dec 17 at 9:15
1
@GAD3R No failed services.
– Broman
Dec 17 at 9:16
1
I'm seeing a couple things timing out near line 1816, and the timestamp moves from 10:09 to 10:12 pretty quickly around that point.
– Shadur
Dec 17 at 9:29
2
Check the output ofsystemd-analyze blame.
– jimmij
Dec 17 at 9:56
|
show 6 more comments
1
1
1
1
I'm using Debian testing with Gnome. For some reason it takes around a three minutes to login, after I have typed in the password and pressed enter. What could the reason be? I would love to provide more details, but I have no idea about where to even start.
On demand:
$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 klutt-desktop.klutt klutt-desktop
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
On demand 2:
$ systemd-analyze blame | head -n3
1min 25.769s ssh.service
6.764s NetworkManager-wait-online.service
612ms udisks2.service
Seems to be ssh. Checking journaltcl
$ sudo journalctl | grep ssh
Dec 17 10:09:53 klutt-desktop systemd[828]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Dec 17 10:10:03 klutt-desktop systemd[1126]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Dec 17 10:11:22 klutt-desktop systemd[1]: ssh.service: Start-pre operation timed out. Terminating.
Dec 17 10:11:22 klutt-desktop systemd[1]: ssh.service: Failed with result 'timeout'.
Dec 17 10:11:22 klutt-desktop systemd[1]: ssh.service: Service RestartSec=100ms expired, scheduling restart.
Dec 17 10:11:22 klutt-desktop systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1.
Dec 17 10:12:48 klutt-desktop sshd[1151]: Server listening on 0.0.0.0 port 22.
Dec 17 10:12:48 klutt-desktop sshd[1151]: Server listening on :: port 22.
Dec 17 10:12:50 klutt-desktop gnome-keyring-ssh.desktop[1232]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
A piece from journalctl from a later reboot, after I ran systemctl disable ssh.service:
Dec 17 11:12:37 klutt-desktop systemd[1]: Startup finished in 3.587s (kernel) + 13.916s (userspace) = 17.504s.
Dec 17 11:12:56 klutt-desktop systemd-timesyncd[696]: Synchronized to time server 79.136.86.176:123 (2.debian.pool.
Dec 17 11:12:57 klutt-desktop dbus-daemon[740]: [system] Failed to activate service 'org.bluez': timed out (service
Dec 17 11:12:57 klutt-desktop pulseaudio[874]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freed
Dec 17 11:13:33 klutt-desktop geoclue[923]: Service not used for 60 seconds. Shutting down..
Dec 17 11:13:34 klutt-desktop realmd[1043]: quitting realmd service after timeout
Dec 17 11:13:34 klutt-desktop realmd[1043]: stopping service
Dec 17 11:15:17 klutt-desktop kernel: random: crng init done
geoclue and realmd seems to be candidates.
linux debian gnome gnome3 startup
asked Dec 17 at 7:57
Broman
159111
I'm using Debian testing with Gnome. For some reason it takes around a three minutes to login, after I have typed in the password and pressed enter. What could the reason be? I would love to provide more details, but I have no idea about where to even start.
On demand:
$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 klutt-desktop.klutt klutt-desktop
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
On demand 2:
$ systemd-analyze blame | head -n3
1min 25.769s ssh.service
6.764s NetworkManager-wait-online.service
612ms udisks2.service
Seems to be ssh. Checking journaltcl
$ sudo journalctl | grep ssh
Dec 17 10:09:53 klutt-desktop systemd[828]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Dec 17 10:10:03 klutt-desktop systemd[1126]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Dec 17 10:11:22 klutt-desktop systemd[1]: ssh.service: Start-pre operation timed out. Terminating.
Dec 17 10:11:22 klutt-desktop systemd[1]: ssh.service: Failed with result 'timeout'.
Dec 17 10:11:22 klutt-desktop systemd[1]: ssh.service: Service RestartSec=100ms expired, scheduling restart.
Dec 17 10:11:22 klutt-desktop systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1.
Dec 17 10:12:48 klutt-desktop sshd[1151]: Server listening on 0.0.0.0 port 22.
Dec 17 10:12:48 klutt-desktop sshd[1151]: Server listening on :: port 22.
Dec 17 10:12:50 klutt-desktop gnome-keyring-ssh.desktop[1232]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
A piece from journalctl from a later reboot, after I ran systemctl disable ssh.service:
Dec 17 11:12:37 klutt-desktop systemd[1]: Startup finished in 3.587s (kernel) + 13.916s (userspace) = 17.504s.
Dec 17 11:12:56 klutt-desktop systemd-timesyncd[696]: Synchronized to time server 79.136.86.176:123 (2.debian.pool.
Dec 17 11:12:57 klutt-desktop dbus-daemon[740]: [system] Failed to activate service 'org.bluez': timed out (service
Dec 17 11:12:57 klutt-desktop pulseaudio[874]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freed
Dec 17 11:13:33 klutt-desktop geoclue[923]: Service not used for 60 seconds. Shutting down..
Dec 17 11:13:34 klutt-desktop realmd[1043]: quitting realmd service after timeout
Dec 17 11:13:34 klutt-desktop realmd[1043]: stopping service
Dec 17 11:15:17 klutt-desktop kernel: random: crng init done
geoclue and realmd seems to be candidates.
linux debian gnome gnome3 startup
linux debian gnome gnome3 startup
asked Dec 17 at 7:57
Broman
159111
asked Dec 17 at 7:57
Broman
159111
edited Dec 17 at 10:26
asked Dec 17 at 7:57
Broman
159111
asked Dec 17 at 7:57
Broman
159111
asked Dec 17 at 7:57
Broman
159111
159111
1
"Around a minute"? 30 seconds is the default timeout for a failed DNS lookup. Perhaps you're missing an127.0.0.1and::1stanza in/etc/hostsor similar...
– Shadur
Dec 17 at 9:15
1
@jimmij Here is the output. I did not know what to look for: pastebin.com/NKxvpLqx
– Broman
Dec 17 at 9:15
1
@GAD3R No failed services.
– Broman
Dec 17 at 9:16
1
I'm seeing a couple things timing out near line 1816, and the timestamp moves from 10:09 to 10:12 pretty quickly around that point.
– Shadur
Dec 17 at 9:29
2
Check the output ofsystemd-analyze blame.
– jimmij
Dec 17 at 9:56
|
show 6 more comments
1
"Around a minute"? 30 seconds is the default timeout for a failed DNS lookup. Perhaps you're missing an127.0.0.1and::1stanza in/etc/hostsor similar...
– Shadur
Dec 17 at 9:15
1
@jimmij Here is the output. I did not know what to look for: pastebin.com/NKxvpLqx
– Broman
Dec 17 at 9:15
1
@GAD3R No failed services.
– Broman
Dec 17 at 9:16
1
I'm seeing a couple things timing out near line 1816, and the timestamp moves from 10:09 to 10:12 pretty quickly around that point.
– Shadur
Dec 17 at 9:29
2
Check the output ofsystemd-analyze blame.
– jimmij
Dec 17 at 9:56
1
1
"Around a minute"? 30 seconds is the default timeout for a failed DNS lookup. Perhaps you're missing an
127.0.0.1 and ::1 stanza in /etc/hosts or similar...– Shadur
Dec 17 at 9:15
"Around a minute"? 30 seconds is the default timeout for a failed DNS lookup. Perhaps you're missing an
127.0.0.1 and ::1 stanza in /etc/hosts or similar...– Shadur
Dec 17 at 9:15
1
1
@jimmij Here is the output. I did not know what to look for: pastebin.com/NKxvpLqx
– Broman
Dec 17 at 9:15
@jimmij Here is the output. I did not know what to look for: pastebin.com/NKxvpLqx
– Broman
Dec 17 at 9:15
1
1
@GAD3R No failed services.
– Broman
Dec 17 at 9:16
@GAD3R No failed services.
– Broman
Dec 17 at 9:16
1
1
I'm seeing a couple things timing out near line 1816, and the timestamp moves from 10:09 to 10:12 pretty quickly around that point.
– Shadur
Dec 17 at 9:29
I'm seeing a couple things timing out near line 1816, and the timestamp moves from 10:09 to 10:12 pretty quickly around that point.
– Shadur
Dec 17 at 9:29
2
2
Check the output of
systemd-analyze blame .– jimmij
Dec 17 at 9:56
Check the output of
systemd-analyze blame .– jimmij
Dec 17 at 9:56
|
show 6 more comments
active
oldest
votes
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489422%2fit-takes-forever-to-login%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
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.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489422%2fit-takes-forever-to-login%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
1
"Around a minute"? 30 seconds is the default timeout for a failed DNS lookup. Perhaps you're missing an
127.0.0.1and::1stanza in/etc/hostsor similar...– Shadur
Dec 17 at 9:15
1
@jimmij Here is the output. I did not know what to look for: pastebin.com/NKxvpLqx
– Broman
Dec 17 at 9:15
1
@GAD3R No failed services.
– Broman
Dec 17 at 9:16
1
I'm seeing a couple things timing out near line 1816, and the timestamp moves from 10:09 to 10:12 pretty quickly around that point.
– Shadur
Dec 17 at 9:29
2
Check the output of
systemd-analyze blame.– jimmij
Dec 17 at 9:56