I can't modify the password of my Wi-Fi hotspot

The default is too long, so I’ve attempted to set it to an 8-character integer. However, when I select “Apply”, I see:

When I scan the QR code, it still displays the old password, despite the KCM returning what I’ve set.

Environment

  1. sudo lshw -C network returns:

    description: Ethernet interface
    product: Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak]
    vendor: Intel Corporation
    physical id: 0
    bus info: pci@0000:49:00.0
    logical name: wlp73s0
    version: 1a
    width: 64 bits
    clock: 33MHz
    capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical
    configuration: broadcast=yes driver=iwlwifi driverversion=6.14.11-300.fc42.x86_64 firmware=89.7f71c7f4.0 ty-a0-gf-a0-89.uc ip=10.42.0.1 latency=0 link=yes multicast=yes
    resources: irq:45 memory:a0200000-a0203fff
    
  1. kinfo returns:

    Operating System: Fedora Linux 42
    KDE Plasma Version: 6.4.0
    KDE Frameworks Version: 6.15.0
    Qt Version: 6.9.1
    Kernel Version: 6.14.11-300.fc42.x86_64 (64-bit)
    Graphics Platform: Wayland
    Manufacturer: ASRock
    Product Name: X670E Taichi
    

I don’t know how to query QDBus for whatever that path is, nor can I feasibly run find on / for that filename that might or not exist.

There are a couple of D-Bus tools that can do that, e.g. qdbusviewer (usually in some Qt dev package), d-feet, and various command line tools.

However, in this case they would probably not be much help since the error says that an object (D-Bus end point) is missing.

I.e. the UI thinks there should be a corresponding Settings object on the NetworkManager side but apparently there isn’t.

This could potentially be solved by restarting the UI (probably logout/login) so that it has to query NM again or using a different frontend, e.g. nmcli for the command line.

Or removing the hotspot config and re-creating it.

Path in this case is not a file system path.
It is part of a D-Bus end point address.

Essentially each D-Bus service has a name, which is the primary address.

Within that connection a client can address specific end point objects using a “D-Bus path”.
Such a path looks like a file system path but is “virtual” within the service..
A way to point to an object within a tree of objects.

1 Like

@krake, I was referring to the .psk file referenced in the other notification, but thank you. (I do wish there were a virtual DBus filesystem, like there is for devices in /dev!)

I’d run qdbus org.kde.Shutdown /Shutdown org.kde.Shutdown.logoutAndReboot, and that indeed remediated the inconsistency between kcm_networkmanagement and plasmashell. However, it’s achieved that by merely reverting my password, and it reproduces:

I can try restarting the service if that’d help narrow this, but it looks like 3 problems:

  1. The Network KCM might not refresh upon preference application failure, and silently fails when something fails, unlike the Plasmoid.

  2. The plasmoid fails to access these preferences, irrespective of whether the KCM does.

There’s also that the “Hotspot” button remains activated when it’s not, if the last attempt to activate it failed. You can see that at the start of the video.

I’d try to report these, but I’ve no idea of what causes them, and there’s rather too many problems to report for me to have the time to fill the BZ template for each.

I might be able to check this on my laptop some time this week but unfortunately not today.

Does it work if you remove the hot spot config and create a new one with an acceptable password?

1 Like

@krake, that’s a good point. I’ve just tested this on my laptop, and the password remains unapplied (although the notifications don’t appear):

Reproduction

Environment

  1. sudo lshw -C network returns:

    description: Ethernet interface
    product: MT7922 802.11ax PCI Express Wireless Network Adapter
    vendor: MEDIATEK Corp.
    physical id: 0
    bus info: pci@0000:01:00.0
    logical name: wlp1s0
    version: 00
    width: 64 bits
    clock: 33MHz
    capabilities: pciexpress msi pm bus_master cap_list ethernet physical
    configuration: broadcast=yes driver=mt7921e driverversion=6.14.11-300.fc42.x86_64 firmware=____000000-20241106163310 ip=192.168.1.219 latency=0 link=yes multicast=yes
    resources: iomemory:800-7ff irq:132 memory:8010900000-80109fffff memory:90b00000-90b07fff
    
  1. kinfo returns:

    Operating System: Fedora Linux 42
    KDE Plasma Version: 6.4.0
    KDE Frameworks Version: 6.15.0
    Qt Version: 6.9.1
    Kernel Version: 6.14.11-300.fc42.x86_64 (64-bit)
    Graphics Platform: Wayland
    Manufacturer: Framework
    Product Name: Laptop 16 (AMD Ryzen 7040 Series)
    System Version: A7
    

By deleting it in the KCM?

Maybe also check which version if network-manager you have.
Probably a very new one since you are on Fedora.

I am on 1.46 since I am KDE Neon which, for base OS stuff, is essentially Ubuntu LTS 24.04

Yes.
Basically testing if just changing the password fails or if the hotspot does not work even when created with a valid password.

Might even be a difference if one tries to change from a valid to a new valid password and only setup with a non-valid password causes the change issue later.

1 Like

@krake, hopefully, one of the undermentioned demonstrates this:

rpm -qa | Select-String -Pattern '-nm|NetworkManager'

NetworkManager-libnm-1.52.0-1.fc42.x86_64
NetworkManager-1.52.0-1.fc42.x86_64
NetworkManager-openvpn-1.12.0-3.fc42.x86_64
NetworkManager-team-1.52.0-1.fc42.x86_64
NetworkManager-wwan-1.52.0-1.fc42.x86_64
NetworkManager-wifi-1.52.0-1.fc42.x86_64
NetworkManager-l2tp-1.20.20-2.fc42.x86_64
NetworkManager-libreswan-1.2.24-2.fc42.x86_64
NetworkManager-pptp-1.2.12-9.fc42.x86_64
NetworkManager-openconnect-1.2.10-7.fc42.x86_64
NetworkManager-libreswan-gnome-1.2.24-2.fc42.x86_64
NetworkManager-ppp-1.52.0-1.fc42.x86_64
NetworkManager-bluetooth-1.52.0-1.fc42.x86_64
NetworkManager-adsl-1.52.0-1.fc42.x86_64
NetworkManager-config-connectivity-fedora-1.52.0-1.fc42.noarch
NetworkManager-libnm-1.52.0-1.fc42.i686
NetworkManager-vpnc-1.4.0-3.fc42.x86_64
kf6-networkmanager-qt-6.15.0-1.fc42.x86_64
plasma-nm-6.4.1-1.fc42.x86_64
plasma-nm-l2tp-6.4.1-1.fc42.x86_64
plasma-nm-openconnect-6.4.1-1.fc42.x86_64
plasma-nm-openswan-6.4.1-1.fc42.x86_64
plasma-nm-openvpn-6.4.1-1.fc42.x86_64
plasma-nm-pptp-6.4.1-1.fc42.x86_64
plasma-nm-vpnc-6.4.1-1.fc42.x86_64

It appears to reproduce regardless, for the undermentioned occurs upon activating the hotspot on a reboot:

Additionally, it now (I don’t think this was true beforehand) doesn’t appear when connected to a Wi-Fi network:

I remember experiencing this > 3 years ago on an old laptop that I still have, and expecting that it was due to its aged hardware. However, on a Framework 16? It can’t have that poor of a Wi-Fi chip!

I would interpret that as version 1.52 for network manager.

The device not being available sounds like a different type of error but also quite bad.

Does it get listed when you do something like

ip address

in a shell?

1 Like

@krake, yeah, ip addr works. It prints lo, Wi-Fi, and Ethernet.