https://bugs.kde.org/show_bug.cgi?id=519849
Bug ID: 519849
Summary: Local device shown as "connected and trusted" with
full plugin access causes user confusion
Classification: Applications
Product: kdeconnect
Version First 23.08.5
Reported In:
Platform: Ubuntu
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: desktop-application
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 192081
--> https://bugs.kde.org/attachment.cgi?id=192081&action=edit
Device initially shown as "untrusted"
Summary:
KDE Connect displays the local device in the device list and automatically
transitions it from "untrusted" to "trusted and connected" on startup.
This behavior can confuse users into thinking that the system has connected to
another external device, even though it is only recognizing itself.
Additionally, when selecting the local device, all plugins (e.g., Remote Input,
Share File, Multimedia Control) are shown as if interacting with another
device.
Steps to Reproduce:
1. Open KDE Connect on a desktop system
2. On initial launch, observe the device list:
- The local device may appear as "untrusted"
3. After initialization, observe:
- The same device becomes "trusted and connected" automatically
4. Click on the local device
5. Observe that all plugins are available (Remote Input, Share File, etc.)
Current Behavior:
- The local device is listed alongside other devices
- It may initially appear as "untrusted"
- It then automatically transitions to "trusted and connected"
- All plugins are visible and appear usable
- No clear distinction is made between local and remote devices
Expected Behavior:
Option A (Preferred):
- Do not display the local device in the device list
Option B:
- Display it separately with a clear label such as "This Device" or "Local
Device"
Option C:
- Keep it visible but:
- Prevent automatic "trusted and connected" status for the local device
- Disable or hide non-meaningful plugins (e.g., Remote Input, Share File)
- Add a note indicating that these actions are intended for remote devices
only
Why This Matters:
- The automatic transition from "untrusted" to "trusted and connected" suggests
a successful connection event
- Users may believe they are connected to another device when they are not
- The UI exposes features that are not meaningful for self-interaction
- This can be especially confusing for new users
Environment:
- OS: Ubuntu 22.04 LTS
- KDE Connect version: (paste output of kdeconnect-cli --version)
- Device: Local system (hostname)
Additional Notes:
Originally attempted to report this on GitLab but was redirected here.
This appears to be intentional behavior, but from a UX perspective, it may
benefit from clearer distinction or simplification.
Attachments:
- Screenshot 1: Device initially shown as "untrusted"
- Screenshot 2: Device shown as "trusted and connected"
- Screenshot 3: Plugin list for local device
--
You are receiving this mail because:
You are watching all bug changes.
