Error connecting MTP device (Pixel 6)

[eturpin]

Describe the bug
Strawberry is unable to connect to my phone when I double click on it. I get an alert modal that says:

Error connecting MTP device mtp://google_pixel_6_/?busnum=002&devnum=011: Could not open MTP device.

If I run strawberry from a terminal, I get these messages:

13:13:59.262 INFO  DeviceManager:602                Connecting QUrl("mtp://google_pixel_6_<redacted>?busnum=002&devnum=011")
13:13:59.262 INFO  ConnectedDevice:68               Connected QUrl("mtp://google_pixel_6_<redacted>/?busnum=002&devnum=011") "mtp://Google_Pixel_6_<redacted>/" false
13:13:59.262 DEBUG ConnectedDevice:73               CollectionBackend(0x557d0137c7c0) for device "mtp://Google_Pixel_6_<redacted>/" moved to thread QThread(0x557d011a52a0, name = "Database")
Device 0 (VID=18d1 and PID=4ee1) is a Google Inc Nexus/Pixel (MTP).
libusb_claim_interface() reports device is busy, likely in use by GVFS or KDE MTP device handling alreadyLIBMTP PANIC: Unable to initialize device
13:13:59.266 ERROR MtpConnection:112                "Could not open MTP device."
13:13:59.269 DEBUG CollectionModel:147              Collection model CollectionModel(0x557d0246cf00, name = "DeviceCollectionModel") deleted
13:13:59.269 DEBUG CollectionBackend:75             Collection backend CollectionBackend(0x557d0137c7c0, name = "DeviceCollectionBackend") deleted

When I connect my device, I see that it shows up in Gnome file manager, but if I eject it, Strawberry says "device not connected," and double clicking on it does nothing. Both Rhythmbox and Clementine are able to connect to my phone without me ejecting, so I'm guessing its a bug with Strawberry.

To Reproduce
Plug in phone to USB. Double-click device.

Expected behavior
I expect Strawberry to connect to my phone with me just double clicking on it.

System Information:

• Debian 12 (bookworm), x86_64
• 1.2.4 bookworm

[jonaski]

From the error message, this does not look like a bug to me, it looks like the device is busy. Make sure the device is not auto-mounted when connected, and any other application is not accessing it, a MTP device must not be mounted when connection is made, that leads to a busy error like this.