[arch-general] Last networkmanager in testing busts everything in gnome ?
Hello everybody. Yesterday, my computer installed from testing last networkmanager version, 0.7.998-1. It worked OK until I shut down my computer. This morning, I cannot get any single program to be launched in gnome, even xterm using alt+f2 dialog box. After I downgraded to version 0.7.2-1, all was again working. I opened a bug : http://bugs.archlinux.org/task/17743 Did anybody see the same problem or is it my computer ? -- Frederic Bezies - fredbezies@gmail.com Weblog : http://frederic.bezies.free.fr/blog/
Frederic Bezies wrote:
Hello everybody.
Yesterday, my computer installed from testing last networkmanager version, 0.7.998-1. It worked OK until I shut down my computer.
This morning, I cannot get any single program to be launched in gnome, even xterm using alt+f2 dialog box.
After I downgraded to version 0.7.2-1, all was again working. I opened a bug : http://bugs.archlinux.org/task/17743
Did anybody see the same problem or is it my computer ?
I noticed the same thing today when I upgraded... Downgrading seems the current solution. Allan
On 01/08/2010 09:01 AM, Allan McRae wrote:
Frederic Bezies wrote:
Hello everybody.
Yesterday, my computer installed from testing last networkmanager version, 0.7.998-1. It worked OK until I shut down my computer.
This morning, I cannot get any single program to be launched in gnome, even xterm using alt+f2 dialog box.
After I downgraded to version 0.7.2-1, all was again working. I opened a bug : http://bugs.archlinux.org/task/17743
Did anybody see the same problem or is it my computer ?
I noticed the same thing today when I upgraded... Downgrading seems the current solution.
Allan
aynone noticed that the hostname and /etc/hosts has been changed? its the first thing that comes in your eyes.(hostname) -- Ionut
Ionut Biru wrote:
On 01/08/2010 09:01 AM, Allan McRae wrote:
Frederic Bezies wrote:
Hello everybody.
Yesterday, my computer installed from testing last networkmanager version, 0.7.998-1. It worked OK until I shut down my computer.
This morning, I cannot get any single program to be launched in gnome, even xterm using alt+f2 dialog box.
After I downgraded to version 0.7.2-1, all was again working. I opened a bug : http://bugs.archlinux.org/task/17743
Did anybody see the same problem or is it my computer ?
I noticed the same thing today when I upgraded... Downgrading seems the current solution.
Allan
aynone noticed that the hostname and /etc/hosts has been changed? its the first thing that comes in your eyes.(hostname)
Yep, my /etc/hosts file was definitely changed: # # /etc/hosts: static lookup table for host names # 127.0.0.1 localhost.localdomain localhost #<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 arch 127.0.0.1 localhost.localdomain localhost That additional line at the start is definitely not mine... Allan
On Fri, 2010-01-08 at 18:54 +1000, Allan McRae wrote:
Ionut Biru wrote:
On 01/08/2010 09:01 AM, Allan McRae wrote:
Frederic Bezies wrote:
Hello everybody.
Yesterday, my computer installed from testing last networkmanager version, 0.7.998-1. It worked OK until I shut down my computer.
This morning, I cannot get any single program to be launched in gnome, even xterm using alt+f2 dialog box.
After I downgraded to version 0.7.2-1, all was again working. I opened a bug : http://bugs.archlinux.org/task/17743
Did anybody see the same problem or is it my computer ?
I noticed the same thing today when I upgraded... Downgrading seems the current solution.
Allan
aynone noticed that the hostname and /etc/hosts has been changed? its the first thing that comes in your eyes.(hostname)
Yep, my /etc/hosts file was definitely changed:
# # /etc/hosts: static lookup table for host names # 127.0.0.1 localhost.localdomain localhost
#<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 arch 127.0.0.1 localhost.localdomain localhost
That additional line at the start is definitely not mine...
Allan
Looks to this noob as if some wrong assumptions are being made in using sed on /etc/hosts
On Friday 08 January 2010 03:54:23 Allan McRae wrote:
Ionut Biru wrote:
On 01/08/2010 09:01 AM, Allan McRae wrote:
Frederic Bezies wrote:
Hello everybody.
Yesterday, my computer installed from testing last networkmanager version, 0.7.998-1. It worked OK until I shut down my computer.
This morning, I cannot get any single program to be launched in gnome, even xterm using alt+f2 dialog box.
After I downgraded to version 0.7.2-1, all was again working. I opened a bug : http://bugs.archlinux.org/task/17743
Did anybody see the same problem or is it my computer ?
I noticed the same thing today when I upgraded... Downgrading seems the current solution.
Allan
aynone noticed that the hostname and /etc/hosts has been changed? its the first thing that comes in your eyes.(hostname)
Yep, my /etc/hosts file was definitely changed:
# # /etc/hosts: static lookup table for host names # 127.0.0.1 localhost.localdomain localhost
#<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 arch 127.0.0.1 localhost.localdomain localhost
That additional line at the start is definitely not mine...
Allan
FYI I was having trouble with networking several years ago and had a /etc/host like yours. I posted to usenet and the network gurus there promptly busted me for that layout. They told me to do this instead: #<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 localhost.localdomain localhost 127.0.0.2 arch.<yourdomain> arch They claim that the above conforms to the RFC's and reusing the 127.0.0.1 address can confuse some apps. I have been using the above and it has always worked, no busted apps.
On Wed, Jan 20, 2010 at 12:53 PM, Baho Utot <baho-utot@columbus.rr.com> wrote:
FYI I was having trouble with networking several years ago and had a /etc/host like yours. I posted to usenet and the network gurus there promptly busted me for that layout.
They told me to do this instead:
#<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 localhost.localdomain localhost 127.0.0.2 arch.<yourdomain> arch
They claim that the above conforms to the RFC's and reusing the 127.0.0.1 address can confuse some apps.
I have been using the above and it has always worked, no busted apps.
I think this comes close to what Debian does, I've kept my /etc/hosts file since I ran Debian and it looks like this: #<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 localhost 127.0.1.1 bryma.fq.dn bryma There's an explanation for it here http://www.debian.org/doc/manuals/reference/ch-gateway.en.html#s-net-dns /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe
On Friday 08 January 2010 10:23:20 Magnus Therning wrote:
On Wed, Jan 20, 2010 at 12:53 PM, Baho Utot <baho-utot@columbus.rr.com> wrote:
FYI I was having trouble with networking several years ago and had a /etc/host like yours. I posted to usenet and the network gurus there promptly busted me for that layout.
They told me to do this instead:
#<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 localhost.localdomain localhost 127.0.0.2 arch.<yourdomain> arch
They claim that the above conforms to the RFC's and reusing the 127.0.0.1 address can confuse some apps.
I have been using the above and it has always worked, no busted apps.
I think this comes close to what Debian does, I've kept my /etc/hosts file since I ran Debian and it looks like this:
#<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 localhost 127.0.1.1 bryma.fq.dn bryma
There's an explanation for it here http://www.debian.org/doc/manuals/reference/ch-gateway.en.html#s-net-dns ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Not Found The requested URL /doc/manuals/reference/ch-gateway.en.html was not found on this server. Apache Server at www.debian.org Port 80
On Wed, Jan 20, 2010 at 10:31 PM, Baho Utot <baho-utot@columbus.rr.com> wrote:
On Friday 08 January 2010 10:23:20 Magnus Therning wrote: [..]
There's an explanation for it here http://www.debian.org/doc/manuals/reference/ch-gateway.en.html#s-net-dns ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Not Found The requested URL /doc/manuals/reference/ch-gateway.en.html was not found on this server. Apache Server at www.debian.org Port 80
Indeed, today that link doesn't work :( I found it here[1], and the explanation is copied: Some software (e.g., GNOME) expects the system hostname to be resolvable to an IP address with a canonical fully qualified domain name. This is really improper because system hostnames and domain names are two very different things; but there you have it. In order to support that software, it is necessary to ensure that the system hostname can be resolved. Most often this is done by putting a line in /etc/hosts containing some IP address and the system hostname. If your system has a permanent IP address then use that; otherwise use the address 127.0.1.1. /M [1]: http://www.linuxquestions.org/questions/linux-networking-3/what-does-127.0.1... -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe
On Wed, Jan 20, 2010 at 07:53:10AM -0500, Baho Utot wrote:
On Friday 08 January 2010 03:54:23 Allan McRae wrote:
Ionut Biru wrote: Yep, my /etc/hosts file was definitely changed:
# # /etc/hosts: static lookup table for host names # 127.0.0.1 localhost.localdomain localhost
#<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 arch 127.0.0.1 localhost.localdomain localhost
I was having trouble with networking several years ago and had a /etc/host like yours. I posted to usenet and the network gurus there promptly busted me for that layout.
They told me to do this instead:
#<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 localhost.localdomain localhost 127.0.0.2 arch.<yourdomain> arch
They claim that the above conforms to the RFC's and reusing the 127.0.0.1 address can confuse some apps.
I have been using the above and it has always worked, no busted apps.
This also seems to work for me, at least the extra aliases at the end of the line are respected: #<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 localhost.localdomain localhost arch -- Jim Pryor profjim@jimpryor.net
Jim Pryor wrote:
On Wed, Jan 20, 2010 at 07:53:10AM -0500, Baho Utot wrote:
On Friday 08 January 2010 03:54:23 Allan McRae wrote:
Ionut Biru wrote: Yep, my /etc/hosts file was definitely changed:
# # /etc/hosts: static lookup table for host names # 127.0.0.1 localhost.localdomain localhost
#<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 arch 127.0.0.1 localhost.localdomain localhost
I was having trouble with networking several years ago and had a /etc/host like yours. I posted to usenet and the network gurus there promptly busted me for that layout.
They told me to do this instead:
#<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 localhost.localdomain localhost 127.0.0.2 arch.<yourdomain> arch
They claim that the above conforms to the RFC's and reusing the 127.0.0.1 address can confuse some apps.
I have been using the above and it has always worked, no busted apps.
This also seems to work for me, at least the extra aliases at the end of the line are respected:
#<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 localhost.localdomain localhost arch
Yes taht is a good way also but I like to keep all the aliases on there own line, that way I can assign a domain to the host.
participants (7)
-
Allan McRae
-
Baho Utot
-
Frederic Bezies
-
Ionut Biru
-
Jim Pryor
-
Magnus Therning
-
Ng Oon-Ee