Ticket #359 (closed defect: worksforme)

Opened 16 months ago

Last modified 16 months ago

hexter GUI does not start (/etc/hostname problem)

Reported by: parkland99@… Owned by: free
Priority: normal Milestone: 2.0
Component: packages Version: 1.4.0
Severity: normal Keywords:
Cc:

Description

Fresh install

AMD64 2.0pre1 master 13jul upgraded to 2.0pre3

When configuring the network using the GUI tools, the etc/hostname does not include the domain.

This causes a problem with hexter; hexter needs a fully qualified domain name in order to display the GUI.

In my system, the host name is "64studio" and the domain name is "mshome"

/etc/hosts is set correctly

127.0.0.1 localhost
127.0.1.1 64studio.mshome

/etc/hostname is set as follows

64studio

Setting etc/hostname to 64studio.mshome and rebooting allows hexter to run as expected (with a GUI)

Change History

  Changed 16 months ago by parkland99@…

  • summary changed from hexter does not start (/etc/hostname problem) to hexter GUI does not start (/etc/hostname problem)

follow-up: ↓ 3   Changed 16 months ago by free@…

Which version of hexter is installed on your system? I've checked the bug with version 0.6.1-1~bpo.1 and I can't replicate it (as your one, my 64studio install as only the hostname in /etc/hostname, no domain name).

in reply to: ↑ 2   Changed 16 months ago by parkland99@…

Replying to free@64studio.com:

Which version of hexter is installed on your system?

Hi Free,

Yes I am also version 0.6.1-1~bpo.1

I've just retested. I confirm: With /etc/hostname set to 64studio, the GUI does not start, with hostname set to 64studio.mshome, the GUI starts normally.

If I $ ping 64studio, I get unknown host

If I $ ping 64studio.mshome, the localhost is found.

Also, adding "64studio" to the hosts file as a localhost allows the GUI to start.

On my system, hexter appears to be taking the hostname from /etc/hostname and trying to resolve the name. My system is a fresh-install using 2.0 pre master from 13th July.

Free, what happens when you ping your hostname (without the domain name)? Does it resolve to your local machine? (Mine does not resolve.)

follow-up: ↓ 5   Changed 16 months ago by free@…

On my system (which is also a fresh install of a recent master snapshot) the "64studio" host name was added automatically to /etc/hosts and a can ping it. It could be something wrong with the installer. Did you configure the network at installation time or after? With DCHP or manual settings?

in reply to: ↑ 4   Changed 16 months ago by parkland99@…

Replying to free@64studio.com:

It could be something wrong with the installer. Did you configure the network at installation time or after? With DCHP or manual settings?

Hi Free,

Network was configured manually after install. I don't run DHCP and use fixed IP addresses for my machines.

  Changed 16 months ago by daniel@…

  • status changed from new to closed
  • resolution set to worksforme

I can't reproduce this bug either, even using a static IP address. I can also ping 64studio out of the box:

64studio:/home/daniel# ping 64studio PING 64studio (127.0.1.1) 56(84) bytes of data. 64 bytes from 64studio (127.0.1.1): icmp_seq=1 ttl=64 time=0.038 ms

I can only conclude there is something strange about your network setup, Steve! Perhaps this is related to the trouble you were having with the Network Manager applet. I'll close this ticket for now, but we can re-open it if anyone reports the same problem.

  Changed 16 months ago by parkland99@…

Fair enough, I guess static IP's aren't normal setup for most users.

I'll manually add a localhost resolution to the /etc/hosts.

Note: See TracTickets for help on using tickets.