[kio-extras] [Bug 478285] New: Android phone not detected since updating to Plasma 6
Steven Eastland
bugzilla_noreply at kde.org
Fri Dec 8 22:56:06 GMT 2023
https://bugs.kde.org/show_bug.cgi?id=478285
Bug ID: 478285
Summary: Android phone not detected since updating to Plasma 6
Classification: Frameworks and Libraries
Product: kio-extras
Version: 24.01.80
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: MTP
Assignee: unassigned-bugs at kde.org
Reporter: seastland at gmail.com
CC: elvis.angelaccio at kde.org
Target Milestone: ---
SUMMARY
I can't access my phone in Plasma 6. When I plug it in in and select "File
transfer / Android Auto" in the USB settings, the device notifier doesn't see
it, nor is it visible in Dolphin's Places panel. It is detected by the kernel:
$ lsusb
Bus 001 Device 025: ID 18d1:4ee2 Google Inc. Nexus/Pixel Device (MTP + debug)
mtp-detect seems to think KDE has access to the device already:
$ mtp-detect libmtp
version: 1.1.21
Listing raw device(s)
Device 0 (VID=18d1 and PID=4ee2) is a Google Inc Nexus/Pixel (MTP+ADB).
Found 1 device(s):
Google Inc: Nexus/Pixel (MTP+ADB) (18d1:4ee2) @ bus 1, dev 27
Attempting to connect device(s)
libusb_claim_interface() reports device is busy, likely in use by GVFS or KDE
MTP device handling alreadyLIBMTP PANIC: Unable to initialize device
Unable to open raw device 0
OK.
I am running Arch with the latest packages installed. I'm comfortable editing
config files, etc. but I don't know how or where to look for any debug output
for the kio-mtp process.
STEPS TO REPRODUCE
1. Plug in Android device and make it available for file transfer via MTP
OBSERVED RESULT
The device does not show in the device notifier or Dolphin's places panel.
EXPECTED RESULT
The device should be accessible in the device notifier and Dolphin's places
panel.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel: 6.6.4-arch1-1 (64-bit)
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list