Bug 497539 - Dolphin stopped recognizing Android devices
Summary: Dolphin stopped recognizing Android devices
Status: CONFIRMED
Alias: None
Product: kio-extras
Classification: Frameworks and Libraries
Component: MTP (show other bugs)
Version: 24.12.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-16 07:58 UTC by nili
Modified: 2025-03-24 04:55 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nili 2024-12-16 07:58:50 UTC
Once i connected my Android with a USB type-C cable the Android icon appeared on Dolphin places sidebar. Lately, these last few weeks it doesn't show to dolphin anymore.

I haven't made any changes except upgrading the distributor, also i haven't changed any settings on my phone. Current libmtp, "libmtp-udev 1.1.22", a previous version was fine and shown on my file manager.

If you need any additional information, please ask me.

Operating System: openSUSE Tumbleweed 20241215
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.11.8-1-default (64-bit)
Graphics Platform: Wayland
Comment 1 Rafael Linux User 2024-12-18 09:03:46 UTC
I confirm the problem and that it is a KDE issue after an update. In KDE Plasma Version 6.2.4, KDE Frameworks Version: 6.8.0, and Qt Version 6.8.0, the system detects that the mobile phone is connected when plugged in by cable and notifies it. However, it does NOT appear listed in the connected devices list in Dolphin. 
If you click on the KDE notification in the "Open with Dolphin" option, Dolphin opens and becomes "frozen."

On another machine that I have more updated (the version that corresponds to Tumbleweed from last week), Dolphin does show the device, but after accessing it, Dolphin always ends up freezing.

On both machines, the file manager "Caja," however, perfectly detects the device (as Dolphin used to do) and allows navigation through the content of my mobile without any problem.

Operating System: openSUSE Tumbleweed 20241202
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.8-1-default (64-bit)
Graphics Platform: Wayland
Comment 2 Robby Engelmann 2025-01-02 10:54:11 UTC
same here using openSUSEs master git snapshots..

Operating System: openSUSE Tumbleweed 20250101
KDE Plasma Version: 6.2.80
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Kernel Version: 6.12.6-1-default (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-13700H
Memory: 62.5 GiB of RAM
Graphics Processor: Intel® Iris® Xe Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO InfinityBook Pro Gen8 (MK1)
Comment 3 Robby Engelmann 2025-02-08 06:48:57 UTC
Still valid here.
As a workaround I now put mtp:/ to the location text field (do not know how it is exactly called) and the device is accessible. You may also put this by right-click to the Favorite Locations.

However, would be nice if the device again is automatically shown and accessible through the Disks widget.
Comment 4 nili 2025-02-08 14:57:17 UTC
Thanks Rob, but i still can't access my S23+ on Tumbleweed.

Dolpin mtp:/
No MTP-Compatible device found

Still doesn't recognize it as icon on dolphin, nor a prompt on KDE status notification once i plug USB-C cable.

libmtp-udev - v1.1.22
kio-extras - v24.12.2

Also i don't get any output running dolphin from konsole/terminal.

√ 02/08/25 15:47
tumbleweed nili 0022 ~
$ dolphin

With KDE Connect the connection is successful. But i'm interested manged via dolphin as i find it more practical and works better.
Comment 5 Helmut Walle 2025-02-09 04:00:55 UTC
Further details from a Tumbleweed system with recent update status:

NAME="openSUSE Tumbleweed"
# VERSION="20250206"

Packages (QUESTION: why do we have both kio-extras and kio-extras5, and which one does kio-5.xxx use? Is kio by any chance using kio-extras5 and kio-fuse-5.xxx, whereas dolphin is now using kio-extras-24.xxx? That could possibly explain the disconnect - or is this a red herring?):

kio-5.116.0-1.2.x86_64
kio-extras-24.12.1-1.1.x86_64
kio-extras5-24.02.2-1.2.x86_64
kio-fuse-5.1.0-1.4.x86_64
libmtp9-1.1.22-1.2.x86_64
libmtp-udev-1.1.22-1.2.x86_64
dolphin-24.12.1-1.2.x86_64

android-file-transfer-linux-4.3.0~git.20240730T195303.cf7036c7f7df-1.2.x86_64

Tests - mobile phones tried: Samsung Galaxy A50 and A55:

1. Plug in A50 (screen unlocked)
2. Responses: on the phone: Allow/Deny prompt as expected; on PC/TW: device notification in sys tray as expected.
3. Hit "Allow" on the phone
4. Hit "Open in File Manager" on PC / sys tray pop-up
5. Response: Dolphin opens in user's home directory; Dolphin "Devices" list does not show phone - FAIL!
6. Enter "mtp:/" into Dolphin location field.
7. Response: Dolphin shows phone now as it should. Access to phone storage, both internal ("Phone") and Card works as it should have after step 4. above. But obviously entering "mtp:/" should not be needed to get there...

Further tests:

- I have performed everything above again, and it is very repeatable.
- Testing with the other phone model, A55, produces the same results.
- Android File Transfer fails with "No MTP devices found", although it does see a USB device.
- lsusb sees the phone(s): "Bus 003 Device 017: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy series, misc. (MTP mode)"
- dmesg says something like:

[ 1368.284329] [   T5446] usb 3-4: new high-speed USB device number 17 using xhci_hcd
[ 1368.409102] [   T5446] usb 3-4: New USB device found, idVendor=04e8, idProduct=6860, bcdDevice= 5.04
[ 1368.409114] [   T5446] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1368.409117] [   T5446] usb 3-4: Product: SAMSUNG_Android
[ 1368.409120] [   T5446] usb 3-4: Manufacturer: SAMSUNG
[ 1368.409123] [   T5446] usb 3-4: SerialNumber: [...]
[ 1368.411543] [   T5446] cdc_acm 3-4:1.1: ttyACM0: USB ACM device

What other information can we provide to narrow this down?
Comment 6 Helmut Walle 2025-02-09 04:32:37 UTC
Further to my comments below, I have another TW system that I have been able to roll back to a snapshot where everything still worked as it should. Details as follows - so this is the status of early November 2024, and from memory, the MTP functionality broke shortly after that date:

NAME="openSUSE Tumbleweed"
# VERSION="20241108"

Packages - NOTE: kio-extras5 is not installed; this package has apparently only been added at the time when this MTP functionality broke. What prompted this change that resulted in going from just kio-extras before to both kio-extras and kio-extras5 now?

kio-5.116.0-1.1.x86_64
kio-extras-24.08.2-1.1.x86_64
package kio-extras5 is not installed
kio-fuse-5.1.0-1.3.x86_64
libmtp9-1.1.21-1.5.x86_64
libmtp-udev-1.1.21-1.5.x86_64
dolphin-24.12.0-2.1.x86_64

With this configuration, Dolphin does show the phone's contents as it should, after first hitting "Open in File Manager" in the KDE pop-up, which then causes the phone to pop up the "Allow/Deny" prompt - and once "Allow" is selected there, Dolphin correctly shows the phone's contents.
Comment 7 Helmut Walle 2025-02-09 05:11:18 UTC
Further to my earlier two comments today, I have also installed a fresh Leap 15.6 yesterday to test this, and it works, but the package configuration is yet different again from the two TW systems that I have tested...

NAME="openSUSE Leap"
VERSION="15.6"

kio-5.115.0-150600.1.4.x86_64
package kio-extras is not installed
kio-extras5-23.08.5-bp156.1.3.x86_64
kio-fuse-5.1.0-bp156.1.3.x86_64
libmtp9-1.1.21-150600.1.3.x86_64
libmtp-udev-1.1.21-150600.1.3.x86_64
dolphin-23.08.5-bp156.2.2.x86_64

Sooo - in this case, kio-extras5 is present, but we have no kio-extras, whereas in the correctly working / rolled-back TW, it is vice-versa. And in the broken TW, we see both kio-extras5 and kio-extras.
Comment 8 John 2025-02-24 18:12:36 UTC
This bug seems to me to be a duplicate of:
https://bugs.kde.org/show_bug.cgi?id=497140
Since both are for openSUSE Tumbleweed and Plasma Version: 6.2.4
Even though they are put under different products.
Can anyone check if this is indeed a duplicate and mark it properly if so?
Thanks!
Comment 9 Rafael Linux User 2025-02-25 00:09:33 UTC
(In reply to John from comment #8)
> This bug seems to me to be a duplicate of:
> https://bugs.kde.org/show_bug.cgi?id=497140
> Since both are for openSUSE Tumbleweed and Plasma Version: 6.2.4
> Even though they are put under different products.
> Can anyone check if this is indeed a duplicate and mark it properly if so?
> Thanks!

Although they are the same problem, the description of the issue and the details are clearer in this thread than in the one that was created first.

Also, the thread you reference mentions "frameworks-solid," but it's "kio" that gives the impression of malfunctioning, as demonstrated by the fact that other file managers like "PCMan" do allow direct access to the mobile phone's storage.

In any case, the problem is recent, because a few months ago access was simple and without problems with Dolphin or Krusader.
Comment 10 John 2025-02-25 08:26:15 UTC
(In reply to Rafael Linux User from comment #9)
> (In reply to John from comment #8) 
> Although they are the same problem, the description of the issue and the
> details are clearer in this thread than in the one that was created first.
> 
> Also, the thread you reference mentions "frameworks-solid," but it's "kio"
> that gives the impression of malfunctioning, as demonstrated by the fact
> that other file managers like "PCMan" do allow direct access to the mobile
> phone's storage.
> 
> In any case, the problem is recent, because a few months ago access was
> simple and without problems with Dolphin or Krusader.

I understand, thanks for the explanation!
Has anyone here tried what I tried with the 'solid-hardware6' command in the other bug report?, more specifically, this:
https://bugs.kde.org/show_bug.cgi?id=497140#c5
And the next reply after it.
Maybe it helps with debugging and finding the root of the problem.
With KIO I don't know any commands, if it has any that can be typed in the terminal.

For me on Debian, everything still works as before, but I have not used PCMan or Krusader, just Dolphin.
Comment 11 nili 2025-03-22 09:09:22 UTC
With all my modest efforts to fix it myself, thinking that i have some shortcomings on my part, i have not been able to find anything, thanks also the mod on forums.opensuse for their helps.

I am ready to provide other info if you ask me.

Current OS Details:

Operating System: openSUSE Tumbleweed 20250320
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.6-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-10700 CPU @ 2.90GHz
Memory: 30.9 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
Manufacturer: Dell Inc.
Product Name: OptiPlex 5080

Continued on opensuse forums.
https://forums.opensuse.org/t/no-mtp-compatible-devices-found/183573

My solid-hardware6 list
https://forums.opensuse.org/t/no-mtp-compatible-devices-found/183573/19