OK, then the idea about router settings is probably null for this issue. I’m not understanding this issue well enough, can’t yet grasp where a second IP is coming from.
@pujithadimuthu could you please show all current output of:
$ nmcli device show
$ nmcli connection show
$ hostname -I
I know some of it has been done before but it would help me to have all in one list.
Also maybe clarify something. To get your system to work with Internet you have to delete enp3s0 and the recreate enp3s0 with a static address? Is that correct?
From my experience if you set a static IP address and the router has an active DHCP server your network interface takes both IP address, at least with NetworkManager. Here is a simple tutorial on how to handle static IP with or without NetworkManager.
GENERAL.DEVICE: lo
GENERAL.TYPE: loopback
GENERAL.HWADDR: 00:00:00:00:00:00
GENERAL.MTU: 65536
GENERAL.STATE: 10 (unmanaged)
GENERAL.CONNECTION: –
GENERAL.CON-PATH: –
IP4.ADDRESS[1]: 127.0.0.1/8
IP4.GATEWAY: –
IP6.ADDRESS[1]: ::1/128
IP6.GATEWAY: –
~
~
~
~
~
[root@pujitha-pc ~]# nmcli connection show
NAME UUID TYPE DEVICE
System enp3s0 63aa2036-8665-f54d-9a92-c3035bad03f7 ethernet enp3s0
System wlan0 113f1f4e-535e-c25b-8849-2c6f770a6501 ethernet –
[root@pujitha-pc ~]#
Also maybe clarify something. To get your system to work with Internet you have to delete enp3s0 and the recreate enp3s0 with a static address? Is that correct?
No I edit the IP settings. Added it in MCC and Configuer network Connections.
This KDE crash is a big issue. I checked it in couple of websites and done what they told. It is not fixed yet. Most of the distros has this KDE crash problem. some one has to look at it too…
I guess you may configure your router to not use a DHCP server with your client (for instance you ay use the MAC address of your network interface). However you may try to shut down NetworkManager (systemctl stop NetworkManager) and set up a static IP from command line.
I deleted all the connections and created a connection named enp0s3
after reboot The system automatically created another connection.
As I remember using the same name. IP is 192.168.2.2 I disconnected it and connected my Static IP connection IP 192.168.2.102.
After Reboot Why system create a auto connection using the same name? You can try.
After couple of reboots auto connection removed.
But see the output
[root@pujitha-pc network-scripts]# cd /etc/sysconfig/network-scripts/
[root@pujitha-pc network-scripts]# ls
cellular.d ifdown ifdown-isdn ifup ifup-ipv6 ifup-routes network-functions-ipv6
hostname.d ifdown-bnep ifdown-post ifup-aliases ifup-isdn ifup-sit vpn.d ifcfg-enp0s3 ifdown.d ifdown-ppp ifup-bnep ifup-plip ifup-tunnel wireless.d ifcfg-enp3s0.bak ifdown-eth ifdown-routes ifup.d ifup-plusb ifup-wireless
ifcfg-lo ifdown-hso ifdown-sit ifup-eth ifup-post init.ipv6-global
ifcfg-wlan0 ifdown-ipv6 ifdown-tunnel ifup-hso ifup-ppp network-functions
[root@pujitha-pc network-scripts]# cat ifcfg-enp0s3
ETHTOOL_OPTS=“autoneg on”
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
IPADDR=192.168.2.102
PREFIX=24
GATEWAY=192.168.2.1
DNS1=8.8.8.8
DNS2=8.8.4.4
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=enp0s3
UUID=da6b36ca-8a7f-429c-a65c-8e854089a65d
ONBOOT=yes
[root@pujitha-pc network-scripts]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 90:fb:a6:99:79:b6 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.2/24 brd 192.168.2.255 scope global dynamic enp3s0
valid_lft 86083sec preferred_lft 86083sec
inet 192.168.2.102/24 brd 192.168.2.255 scope global secondary noprefixroute enp3s0
valid_lft forever preferred_lft forever
inet6 fe80::d123:585:a183:3d36/64 scope link noprefixroute
valid_lft forever preferred_lft forever
[root@pujitha-pc network-scripts]# ip a s enp0s3
Device “enp0s3” does not exist.
[root@pujitha-pc network-scripts]#
@pujithadimuthu I just today realized that this is you asking to reopen an older thread. As that thread begins with update issue in Lx 3.02 circa May 2017 and also because we did not get off to a good discussion communications wise we think it would be better to start a new thread.
My understanding at this time is that you are having issues with KDE/Plasma5 desktop crashing. I’m sure that is frustrating I know it was for me when I was experiencing some similar issues when Lx 3 was in Alpha, Beta, and the first months after General Release. So if we could get a new thread started with a Title that accurately describes the problem that would be super.
Some or our developers have come up with some more better ways to get information that we need to get to the bottom of this in. System or Desktop crash or freeze issues are some of the most difficult type of problems for developers and others to get to exactly what is happening and why it is happening so good accurate information is needed.
When you see me use this phrase it is partly meant in humor, and is meant to be a comment about us users in general, not directed at a particular individual. The person I’ve seen this happen to the most is me.
Seems like all of us in Linux experience discovering a problem on our computer, then going through the process of solving it, and in that process realizing that something we did ourself caused the problem.
