Bug 471368

Summary: Bluetooth from phone to computer tethering connection weirdness
Product: [I don't know] kde Reporter: Yani <akayanni>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED UPSTREAM    
Severity: normal CC: nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Yani 2023-06-23 08:28:37 UTC
Using the Google Pixel 6 phone as an internet connection and Bluetooth as the transfer protocol.

I've had a connection issue that I've tracked down to the following.

Phone set to USB tethering, connected to Bluetooth OK, fails to get a network connection.

Reboot and restarts later I have this down to...

It works perfectly only when you have Bluetooth connected and change the switch on the phone from Tethered Bluetooth
If it is on -- off to on again.

Something isn't happening when the Bluetooth is on where it doesn't recognized that it is tethered until you turn tethering off and on, on the phone/device.

If you disconnect the network connect then try to restart it, it cycles on "setting network address" until it gives up.

Easily resolved by the user but with a decent case of what the is going on here.


(Sorry i didn't know the right cat to put the bug)







Operating System: Rocky Linux 9.2
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.3
Kernel Version: 5.14.0-284.11.1.el9_2.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 64 × AMD EPYC 7551P 32-Core Processor
Memory: 125.2 GiB of RAM
Graphics Processor: AMD Radeon RX 6700 XT
Manufacturer: Supermicro
Product Name: Super Server
System Version: 0123456789
Comment 1 Nate Graham 2023-08-04 20:09:29 UTC
All the heavy lifting for this is provided by the bluez and networkmanager upstream projects. KDE code simply uses those and can't be the cause of this problem. I'd recommend that you report the bug to your distro, as they can help you perform the troubleshooting needed to identify exactly which component is at fault.