Bug 511273 - With multiple network cards, network Interfaces are shown doubled on wrong device
Summary: With multiple network cards, network Interfaces are shown doubled on wrong de...
Status: REPORTED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Networks widget (other bugs)
Version First Reported In: 6.4.5
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-28 16:21 UTC by Ilya
Modified: 2025-12-02 23:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Extra Main interface on enp2 And Extra Testing ON enp5 (33.93 KB, image/png)
2025-10-28 16:21 UTC, Ilya 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ilya 2025-10-28 16:21:05 UTC 
Created attachment 186262 [details]
Extra Main interface on enp2 And Extra Testing ON enp5

SUMMARY

Wrong duplication of network intefaces on wrong dev

STEPS TO REPRODUCE
1. Connect device to extenal network card 
2. Set static IP to it or do any other settings
3. done

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.16.12-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics
Memory: 32 GB of RAM (31.2 GB usable)
Graphics Processor: NVIDIA GeForce RTX 5060

ip a result:
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 noprefixroute 
       valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 74:56:3c:2a:c0:78 brd ff:ff:ff:ff:ff:ff
    altname enx74563c2ac078
    inet 192.168.88.254/24 brd 192.168.88.255 scope global dynamic noprefixroute enp5s0
       valid_lft 351sec preferred_lft 351sec
    inet6 fe80::d5:8dd7:c0a3:c1fc/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: enp2s0f0u4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:e0:4c:36:6b:21 brd ff:ff:ff:ff:ff:ff
    altname enx00e04c366b21
Comment 1 Ilya 2025-10-28 16:26:07 UTC 
Fixed it with
nmcli connection modify "Main" connection.interface-name enp5s0
nmcli connection modify "Testing" connection.interface-name enp2s0f0u4

But what the reason of this bug? why does they are not bounded automatically?
Comment 2 Ilya 2025-10-28 19:47:31 UTC 
After changing settings of the connection (for example: change static ip to auto) it happends again
Comment 3 Nate Graham 2025-10-29 20:47:24 UTC 
Did you set any of this up in the first place using `nmcli`?
Comment 4 Ilya 2025-10-30 06:12:08 UTC 
(In reply to Nate Graham from comment #3)
> Did you set any of this up in the first place using `nmcli`?

Never used nmcli before this problem appeared