ROSA Linux Bugzilla – Bug 6041
Network Manager and ISP's DHCP response make KDE unable to start applications
Last modified: 2015-08-12 12:35:15 MSD
Created attachment 4210 [details]
I have a pretty complicated network configuration. Main PC interface is being used as VLAN Trunk. One of VLANs (vlan 10) is connected to ISP ("Rostelekom", "rtk" for short) infrastructure. There is another VLAN (vlan 20) which is connected to LAN with D-link router.
Network is being configured via Network Manager. I haven't found out the correct way to setup trunk interface yet so eth0 is being assigned a dummy ip address manually, just to make NM get it to "UP" state. Vlans are being configured as VLAN type and do work but do not get started automatically neither at startup time nor after user login. I don't mind clicking "connect" button manually at the moment. It may be caused by me setting up trunk interface the wrong way. What actually bothers me is going below.
Description of problem:
When PC connects to vlan 20 it gets configured by D-Link router via DHCP. The interface gets configured with IP address, netmask, default router and DNS server addresses. This way everything goes good.
When PC connects to vlan 10 it gets configured by "Rostelekom" DHCP servers. The interface gets configured with slightly another set of options. And KDE gets unable to launch programs. It says "KDEInit не может запустить «/usr/bin/konsole»" ("KDEInit can't launch «/usr/bin/konsole»").
I see that hostname changes. This might be the reason. Or there might be other reasons.
Version-Release number of selected component (if applicable):
[root@linux tmp]# urpmq --evrd networkmanager
networkmanager: 0:1.0.2-6:2014.1|networkmanager: 0:0.9.10.0-4:2014.1
[root@linux tmp]# urpmq --evrd dhcp-client
dhcp-client: 3:4.3.0-2:2014.1|dhcp-client: 3:4.3.2-7:2014.1
Dunno. Will try the same thing without vlans.
Created attachment 4211 [details]
hw info before starting interface
Hardware probe attached has been collected before starting the interface. This is why it is being attached as an archive. Ther following probe has been made after the interface has started: