I still have a computer with OMV 2014.2. There, hostname also changes but drakconf does not stop working! So, is it a problem to have hostname changes or the problem is in those applications that do not accept these changes?
Hello Adelson,
here’s the way to solve the problem (at least my problem was solved) with the CCM thanks to Jcl.Vanier
1°)choose a hostname2°)type hostnamectl set-hostname new_name (instead of new_name, type the hostname you chose)3°) restart your computer
Now everything should work. I hope it helped you and solved your problem.Cheers !
CD
I boot the computer and logged in,
$ hostname
localhost
Drakconf working fine.
then I disconnected and reconnected the wifi, yes, hostname changed,
$ hostname
localhost.localdomain
Drakconf stopped working.
Then I logged off and in,
$ hostname
localhost.localdomain
and drakconf is working fine again!
Hence, drakconf works whatever hostname is, it stops when hostname is changed in a particular session (??). It must be said that this seems to be a drakconf problem since many other applications do not fail in the same situation and, in particular, the authentication window for drakconf is open without any problem! How could it be related to Xorg?
As far as I could see, this has the same effect as
$ hostname new_name
doesn’t it?
It seems strange that old OMV 2014 did not show this problem! It makes me to think that something else could be done to avoid new users to face this problem …
I will try your suggestion and post here the result. This test may be useful for understanding the problem.
the command hostnamectl altered the file /etc/hostname only.
So, Luca, the file /etc/hosts has the ip address you mention (127.0.0.1)? Why should I not change the hostname to localhost simply? And I still wonder what made OMX LX 3.0 users have this problem after all since OMV 2014 users had not.
I have no more problems since I’ve followed JCLXavier suggestion and Luca’s tips. However, for a new user, it seems that the problem is still pending since everything can happen again. The default hostname is localhost and networkmanager will change it if it is so.
So, what can I say, my personal problem is solved but … May I let to the forum administration the decision on marking the topic solved or pending?
Or is it the reverse? Why does your hardware have so many problems with OpenMandriva 3.02. Not very many people had a problem with this.
Edit: How many times does it need to be said. Developers can’t fix things they don’t know about. How do developers know users have a certain specific problem?
Right! These problems were discussed in the forum, not at a bug in bugzilla. I did not want to seem upset with these problems. I prefer to face them than to use other proprietary OS. Back to the virtuous cicle where people report bugs and help development of the distro, I guess I should report at bugzilla things like:
1 - SDDM, by default, starts with “NUM LOCK on” which yields messages of wrong passwords in laptops if users define passwords that uses shared keys … this was reported in the forum and still happens with the new 3.02.
2 - Passwords of new users are not correctly set with OMCC (It is in the Errata, I guess). To set passwords one should use kusers, but kusers has to be installed…this was also reported in the forum and still happens with 3.02.
3 - Those who have hybrid graphical support (Nvidia + other) may have problems if proprietary nvidia drivers are installed (in the ERRATA, isn’t it?). Here, the problem was solved with XFdrake which creates a xorg.conf file. It happened with OMV LX 3.0 and is still a problem with 3.02.
Can we consider this topic solved, or still pending?