Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #265753
| From | Rodolfo Medina <rodolfo.medina@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Temporary failure in name resolution |
| Date | 2024-01-10 20:30 +0100 |
| Message-ID | <HUMqZ-2bLR-1@gated-at.bofh.it> (permalink) |
| References | <HULlg-2b8e-1@gated-at.bofh.it> <HULuV-2bbJ-11@gated-at.bofh.it> <HULEC-2bf6-13@gated-at.bofh.it> <HULOh-2biw-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Greg Wooledge <greg@wooledge.org> writes: > On Wed, Jan 10, 2024 at 06:34:53PM +0000, Rodolfo Medina wrote: >> <tomas@tuxteam.de> writes: >> > Where/how does this error message "appear"? >> >> As an output of the `startx' command. > > It would be lovely to see the *entire* error message, in case some part > of it identifies the program that produced the error. Many messages do. /etc/resolv.conf is there again (the system created it) but the error message does not seem to occur any more. Even if it occurred again, I have no way to fetch it, cause it appears (it used to) at login. > Failing that, let's go out on a limb and guess that it's *your own* > hostname that can't be resolved. > > What is the output of the "hostname" command? It's: `thinkpad'. > What is the output of "grep -F $(hostname) /etc/hosts"? It's: 127.0.1.1 caterina-thinkpad.home caterina-thinkpad > What is the output of "grep hosts /etc/nsswitch.conf"? It's: hosts: files mdns4_minimal [NOTFOUND=return] dns --------- Rodolfo
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Temporary failure in name resolution Rodolfo Medina <rodolfo.medina@gmail.com> - 2024-01-10 19:20 +0100
Re: Temporary failure in name resolution <tomas@tuxteam.de> - 2024-01-10 19:30 +0100
Re: Temporary failure in name resolution Rodolfo Medina <rodolfo.medina@gmail.com> - 2024-01-10 19:40 +0100
Re: Temporary failure in name resolution Greg Wooledge <greg@wooledge.org> - 2024-01-10 19:50 +0100
Re: Temporary failure in name resolution Rodolfo Medina <rodolfo.medina@gmail.com> - 2024-01-10 20:30 +0100
Re: Temporary failure in name resolution Marco Moock <mm@dorfdsl.de> - 2024-01-10 20:30 +0100
Re: Temporary failure in name resolution Greg Wooledge <greg@wooledge.org> - 2024-01-10 21:30 +0100
Re: Temporary failure in name resolution Max Nikulin <manikulin@gmail.com> - 2024-01-11 04:20 +0100
Re: Temporary failure in name resolution Greg Wooledge <greg@wooledge.org> - 2024-01-11 04:30 +0100
Re: Temporary failure in name resolution Max Nikulin <manikulin@gmail.com> - 2024-01-12 04:10 +0100
Re: Temporary failure in name resolution David Wright <deblis@lionunicorn.co.uk> - 2024-01-11 06:00 +0100
Re: Temporary failure in name resolution Curt <curty@free.fr> - 2024-01-11 17:40 +0100
Re: Temporary failure in name resolution Marco Moock <mm@dorfdsl.de> - 2024-01-11 18:10 +0100
Re: Temporary failure in name resolution debian-user@howorth.org.uk - 2024-01-12 12:30 +0100
Re: Temporary failure in name resolution Byung-Hee HWANG <soyeomul@doraji.xyz> - 2024-01-12 14:10 +0100
Re: Temporary failure in name resolution Curt <curty@free.fr> - 2024-01-12 17:10 +0100
Re: Temporary failure in name resolution Jeffrey Walton <noloader@gmail.com> - 2024-01-12 17:30 +0100
Re: Temporary failure in name resolution Jeffrey Walton <noloader@gmail.com> - 2024-01-12 18:40 +0100
Re: Temporary failure in name resolution debian-user@howorth.org.uk - 2024-01-12 18:40 +0100
Re: Temporary failure in name resolution John Hasler <john@sugarbit.com> - 2024-01-12 20:50 +0100
Re: Temporary failure in name resolution debian-user@howorth.org.uk - 2024-01-12 19:20 +0100
Re: Temporary failure in name resolution <tomas@tuxteam.de> - 2024-01-11 06:30 +0100
csiph-web