Network applet shows unnamed conections

Help
,
1

I noticed this error first after updating to Plasma 6.2.2. But it’s possible that it was present before. I do have problems to describe the issue. Basically the applet shows connections which do not exist. These connections do not have any name. But the disconnect button is present. I hope this picture explains the issue.

NetworkWidget
NetworkWidget476×465 52.4 KB

My system

Operating System: Arch Linux
KDE Plasma Version: 6.2.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.6.59-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 9 7940HS w/ Radeon 780M Graphics
Memory: 30.6 GiB of RAM
Graphics Processor: AMD Radeon 780M
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ASUS TUF Gaming A16 FA617XS_FA617XS
System Version: 1.0

nmcli output
wlan0: connected to Tomate
“Realtek RTL8852BE 802.11ax”
wifi (rtw89_8852be), CC:47:40:02:AF:18, hw, mtu 1500
ip4 default
inet4 192.168.11.205/24
route4 192.168.11.0/24 metric 600
route4 default via 192.168.11.2 metric 600
inet6 fe80::532d:2640:27ae:152b/64
route6 fe80::/64 metric 1024

lo: connected (externally) to lo
“lo”
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
inet4 127.0.0.1/8
inet6 ::1/128

p2p-dev-wlan0: disconnected
“p2p-dev-wlan0”
wifi-p2p, hw

enp5s0: unavailable
“Realtek RTL8111/8168/8211/8411”
ethernet (r8169), 08:BF:B8:C0:F2:56, hw, mtu 1500

DNS configuration:
servers: 192.168.11.2
domains: zuhause.lan
interface: wlan0

2

Same on Kde Neon User Edition Plasma 6.2.2

3

Arch sure as it is a known QT related issue as stated by the KDE devs, but I wonder how in the world KDE Neon (KDEs own distro) could possibly use a known broken QT version. Unbelievable :rofl:.

As all involved parties, especially QT. should know about this issue it should probably be resolved someday.

1 Like
4

If this is a QT issue is there a bug report I can track.

5

On the KDE side of things, have to search for it as its already a month, it just said “RESOLVED UPSTREAM” in the bug tracker for the network applet and a friendly dev told me here that “resolved” in that case not meant actually “resolved” but (issue closed for KDE) “has to be resolved” in QT.
Which should mean, while i don’t looked into it any further, it has to be reported to “upstream”/QT, everything else would be insane.

Edit: here is the KDE bugtracker entry
https://bugs.kde.org/show_bug.cgi?id=493116
with the Link to the QT bugreport in it.
They changed the status from “RESOLVED UPSTREAM” to “VERIFIED UPSTREAM” wonder why :smirk: because now it seems actually “resolved” from some QT versions onward. Weird status naming if you ask me.

6

Tanks for the link to the bug tracker. Looks like its fixed in QT 6.8.1 and 6.9.0. Now I have to wait until those versions come to Arch.

1 Like