why debian set hostname to easy?

This creates a lot of problems.

Installed the latest debian lxqt bookworm 12 distribution.
Same problem again.

I must set kernel.hostname in sysctl.conf, then in bashrc to write
sudo sysctl --system -p.

However, even sometimes, the hostname goes back to "easy" for unknown reasons.
Sadly, it is populated in a lot of files. Especially in .Xauthority that creates the following problems:
"invalid magic number", "problems to open display :0".

So, I tried to report the bug in debian bug tracker using sysctl package.
But it is said unknown package.
How i can properly report this problem to debian devs?
What package i must use?





Sincerely,
Elias

ps. 5 years vegan

What does "to easy" mean? Is "easy" the content of /etc/hostname? Do you rather mean /etc/hostname is excessively easy to change?

Have you ever tried setting hostname with hostnamectl?

What are the contents of /etc/hostname?

Try altering the contents of /etc/hostname to be a single line with your desired new hostname. Then reboot.

I typically use the net install option and the default hostname is "debian" and I would expect the live versions to be the same.

Quoting myself: "why debian set hostname to easy?". `kernel.hostname=easy`.
Hostname has my NAME, not "easy" name. Nothing to do there.
I have found as i described a temporary solution.

It is a bug of debian. How i can report it this to debian bug report system?
What package to put as bug? sysctl? hostname or other?

You may expect your bug report to be designated invalid.

I have several debian virtual and physical machines of different versions and none of them have exhibited a similar problem. For me:

/proc/sys/kernel/hostname = /etc/hostname

Are you actually writing to /etc/sysctl.conf? The file is only writable by root.

Of course i am writing to sysctl.conf as root user.

2 different machines (no virtual ones), same problem! This is not random error.
(latest stable debian distribution).

I have 4 machines both physical and virtual running latest stable and none of them have your problem. Are they standalone and not part of a domain etc?

standalone on same router

Are you using a reservation from the router to assign an address to the computers?

FYI: none of my Debian machines exhibit this problem. I doubt it is the Debian install that is caused the symptoms, and if that is correct it is not something the Debian team can address in the software.

I find the cause of my problems.

please check your file, and tell me what do you see in your machines.
in file: /var/lib/dhcp/dhclient.enp3s0.leases

in the line `option host-name "easy.box";` before .box what it writes? your hostname or another?

It seems, that in latest debian distribution, somehow this line it cannot modified with any proper command like eg. hostname, or even sysctl exept aftermath but in every boot, its there.

The file "dhclient.enp3s0.leases" is created from what application/package?

The leases file is basically a log of valid dhcp leases from the DHCP server created by dhclient. Of the two debian 12 systems I just checked Network Manager is the DHCP client not dhclient.

The option host-name in the leases file indicates the router is sending the hostname to the client. This is why I asked if you have a address reservation in the router for this PC.

1 members found this post helpful.

what means an address reservation in the router for this PC? How i can check that? i go to 192.168.2.1 and i enter router. then? can you send some relevant screenshot?