| Summary: | Allow applications to disconnect device via DBus | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | rugk <7429c5c9> |
| Component: | kcm_kdeconnect | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
rugk
2017-08-21 20:39:31 UTC
Why is this needed in the first place? With the current design, devices automatically try to discover and connect to each other. This means that if we added a 'disconnect' button, after a while the devices would connect again. At least when using the button on Android, it does not happen. And at least the GNOME extension runs the device discovery only for a limited time and only if you click on a button. So when implemented a disconnect would mean "disconnect until I click the button to reconnect again". Reasons for disconnecting a device are diverse, e.g. saving power or so. Hello from KDE's bug team! The KDE Connect page in System Settings was recently removed, in favor of a new standalone app used to configure KDE Connect. As such, this Bugzilla ticket is no longer relevant due to the software it's about no longer existing. Please open new bug reports for the desktop ap at https://bugs.kde.org/enter_bug.cgi?product=kdeconnect&component=desktop-application. Thanks! |