Bug 411562 - Bluetooth dun connection cannot be edited in plasma-nm
Summary: Bluetooth dun connection cannot be edited in plasma-nm
Status: REPORTED
Alias: None
Product: plasma-nm
Classification: Plasma
Component: editor (show other bugs)
Version: 5.18.6
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-03 16:18 UTC by gumb
Modified: 2021-06-09 05:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gumb 2019-09-03 16:18:40 UTC
On openSUSE Leap 15.1, default Plasma 5.12.8LTS with Frameworks 5.55.0 and Qt 5.9.7.

From within the Plasma Bluetooth module I linked to my phone and set up a dun connection, which I subsequently got working. It then appears in the plasma-nm connections editor, but when changing any option for that connection, the Apply button remains greyed out. It is not possible to effect any change with the OK button or by selecting another connection and receiving a prompt. If I OK the dialog, when I return none of my changes have been saved.

The most troublesome effect of this is that the connection also automatically assumes priority and keeps trying to connect every few minutes, regardless of whether I already have another active and stable connection, and regardless of whether bluetooth is activated on the device. This could result in data being unknowingly transferred over my phone's bluetooth connection, with myriad consequences, not least an unexpected huge phone bill! Since no firewall zone has been selected or is indeed selectable when creating the connection, this also opens up potential security issues.

I've been able to resolve the problem after editing the file relating to the connection in /etc/NetworkManager/system-connections/ by adding these lines under the [connection] section:
autoconnect=false
autoconnect-priority=-1
zone=external

and then rebooting (probably a restart command would have done the trick). But other users could be unaware that this dun connection is poaching priority and transferring their data, or indeed they may edit the connection, click OK and think all is well.
Comment 1 stakanov.s 2019-09-03 17:06:13 UTC
I can confirm this for 15.1 opensuse as well, with different hardware.
Comment 2 Jan Grulich 2020-01-06 10:09:23 UTC
I cannot reproduce. I tried it now and once I changed autoconnect or connection name it enabled the apply button.

Looking into the code, the only thing that we check whether the connection is valid is hardware adress of the bluetooth adapter. Can you check whether it's valid?
Comment 3 gumb 2021-06-09 05:47:22 UTC
I've not used the bluetooth connection in the intervening time but am modifying the bug report to the Plasma 5.18.6LTS version that is current default in openSUSE 15.2, since I see that the problem still persists with any changes I make to the connection not provoking the Apply button to activate.

In answer to the previous question, I think the hardware address of the bluetooth adaptor must be valid since I was able to establish and use the connection previously.