I have never seen this bug but well

CC: (none) => mageia, olav, sander.lepik, tmb

If this happens then your login DM config is busted (or the DM itself is just buggy). The XAuthority should certainly not be keyed to your hostname.

Can you reproduce simply by logging in as you normally do, becoming root and then changing the hostname manually? If so, it's really not NetowrkManager's fault. Even drakxnet allows you to configure things such that the network conenction can set the hostname (NEED_HOSTNAME=yes IIRC).

But the real thing is how your x is authenticate, and it certainly shouldn't be based on hostname.

I had the same problem on Monday after a normal update. I'm using systemd and networkmanager and haven't change any config.
After the update (and a reboot because of glibc) i wasn't able to start any program in LXDE after connecting with networkmanager. I think an updated package changed /etc/hostname but i can't reproduce it any more.

(In reply to comment #2)
> If this happens then your login DM config is busted (or the DM itself is just
> buggy). The XAuthority should certainly not be keyed to your hostname.
> 
> Can you reproduce simply by logging in as you normally do, becoming root and
> then changing the hostname manually? If so, it's really not NetowrkManager's
> fault. Even drakxnet allows you to configure things such that the network
> conenction can set the hostname (NEED_HOSTNAME=yes IIRC).
> 
> But the real thing is how your x is authenticate, and it certainly shouldn't be
> based on hostname.

[kamil@localhost zap3]$ xclock 
[kamil@localhost zap3]$ hostname
localhost
[kamil@localhost zap3]$ xclock 
[kamil@localhost zap3]$ hostname test_a
hostname: you must be root to change the host name
[kamil@localhost zap3]$ sudo hostname test_a
[kamil@localhost zap3]$ xclock 
[kamil@localhost zap3]$ hostname 
test_a
[kamil@localhost zap3]$

Ping!

After fresh boot.iso installation this is still true.

Just to satisfy my thoughts here, can you install and use gdm as your DM and see if this is still a problem?

(In reply to comment #6)
> Just to satisfy my thoughts here, can you install and use gdm as your DM and
> see if this is still a problem?
With GDM + Gnome3: No, it's not.

So if things work in GDM+Gnome, I'd suggest that this is more of a problem with KDE and KDM then rather than NetworkManager per-se.

(In reply to comment #8)
> So if things work in GDM+Gnome, I'd suggest that this is more of a problem with
> KDE and KDM then rather than NetworkManager per-se.

I have not tested it with KDE and KDM, just Slim + Window Maker.

Oh sorry, I just assumed... slim is generally a bit messed up permissions wise and such like :s

I don't know if this is still the case, but some months back NM had the bad habit of setting the hostname to something set in an NM config file (I believe the default was localhost.localdomain).

The problem occurred when you had a wired connection that started via ifplugd and specified NEED_HOSTNAME=yes.  ifplugd would get and set the hostname from DHCP, and NM would later trample on this.  IIRC, it even issued a syslog message saying that it was doing it.

IINM this eventually got fixed.

Something similar is reported in bug#3782.

CC: (none) => ftg

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

indeed yes exactly the same

*** This bug has been marked as a duplicate of bug 3782 ***

Keywords: NEEDINFO => (none)
Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE