Nemo hangs after phone being plugged in for a while

Distribution

Mint 22.3

Package version

6.6.3

Frequency

Quite often

Bug description

Nemo hangs whenever I try to open it by the terminal or by the desktop icon.
But, the bug stopped when I unplugged my phone which Nemo had previously recognized as a storage device, despite the phone being set to "No data transfer."

Steps to reproduce

Make sure Nemo is running
Plug in an android phone, and make sure its "Use USB for" setting is set to "No Data Transfer". Nemo will not hang right there, but it will regardless recognise the phone as a storage device, and open it to desktop to reveal an empty folder. This happens even if "No data transfer" was set even before the phone was plugged in to the computer.
Sorry, but this step is uncertain, not fully sure what happens to cause this bug but I suspect that it has something to do with Nemo's cache expiring or something? The bug seems to happen completely randomly, sometimes hours after an initial OS boot so I'm not sure what it could be.
Open Nemo. If whatever has required has happened, it'll hang. Opening Nemo in terminal will result in a timeout.
Unplug the phone, and Nemo will immediately open up as normal.

Expected behavior

Instead of hanging or waiting eternally, it should recognize the drive isn't behaving properly or is refusing to connect and move on to the next drive instead of waiting an unreasonable amount of time.

Additional information

The version of Android for the phone is Android 15.
When running "nemo" in terminal, it hangs until eventually it receives a time-out from the system.
I have been unable to find the source of the problem.
I am uncertain of whether this happens with iOS too.

This is happening to me too. I just came searching for an answer.

**[code]
System:
Kernel: 6.8.0-124-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc
Desktop: Cinnamon v: 6.6.7 tk: GTK v: 3.24.41 wm: Muffin v: 6.6.3 vt: 7 dm: LightDM v: 1.30.0
Distro: Linux Mint 22.3 Zena base: Ubuntu 24.04 noble
Machine:
Type: Desktop Mobo: Gigabyte model: B550M AORUS PRO-P serial:
uuid: UEFI: American Megatrends LLC. v: F19 date: 10/29/2025
CPU:
Info: 8-core model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64 type: MT MCP smt: enabled
arch: Zen 3 rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
Speed (MHz): avg: 2793 high: 4616 min/max: 400/4673 cores: 1: 3672 2: 400 3: 3669 4: 4616
5: 3673 6: 400 7: 400 8: 3695 9: 3657 10: 3693 11: 4112 12: 400 13: 3665 14: 3658 15: 400
16: 4591 bogomips: 121375
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series] vendor: Gigabyte driver: amdgpu
v: kernel arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports: active: DP-1 empty: HDMI-A-1
bus-ID: 05:00.0 chip-ID: 1002:1638 class-ID: 0300 temp: 29.0 C
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00") s-diag: 777mm (30.58")
Monitor-1: DP-1 mapped: DisplayPort-0 model: Dell S2721DGF serial: res: 2560x1440
hz: 60 dpi: 109 size: 597x336mm (23.5x13.23") diag: 685mm (27") modes: max: 2560x1440
min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: swrast
gbm: drv: kms_swrast surfaceless: drv: radeonsi x11: drv: radeonsi inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.2.8-0ubuntu0.24.04.1 glx-v: 1.4
direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir ACO DRM 3.57 6.8.0-124-generic)
device-ID: 1002:1638
API: Vulkan v: 1.3.275 layers: 7 surfaces: xcb,xlib device: 0 type: integrated-gpu driver: N/A
device-ID: 1002:1638 device: 1 type: cpu driver: N/A device-ID: 10005:0000
Audio:
Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie:
speed: 8 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 1002:1637 class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel pcie:
speed: 8 GT/s lanes: 16 bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.8.0-124-generic status: kernel-api
Server-1: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel pcie: speed: 5 GT/s
lanes: 1 port: f000 bus-ID: 03:00.0 chip-ID: 10ec:8125 class-ID: 0200
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac:
IF-ID-1: bridge1 state: up speed: 1000 Mbps duplex: unknown mac:
IF-ID-2: virbr0 state: down mac:
Bluetooth:
Device-1: TP-Link Bluetooth USB Adapter driver: btusb v: 0.8 type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 bus-ID: 5-1.1.1:5 chip-ID: 2357:0604 class-ID: e001 serial:
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: bt-v: 5.1 lmp-v: 10
sub-v: d922 hci-v: 10 rev: dfc6 class-ID: 7c0104
Drives:
Local Storage: total: 1.82 TiB used: 730.96 GiB (39.2%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WD BLACK SN750 SE 1TB size: 931.51 GiB
speed: 63.2 Gb/s lanes: 4 tech: SSD serial: fw-rev: 711250WD temp: 30.9 C scheme: GPT
ID-2: /dev/sda vendor: Western Digital model: WD10EURX-63FH1Y0 size: 931.51 GiB speed: 6.0 Gb/s
tech: N/A serial: fw-rev: 1A01 scheme: MBR
Partition:
ID-1: / size: 611.19 GiB used: 278.45 GiB (45.6%) fs: ext4 dev: /dev/nvme0n1p5
ID-2: /boot/efi size: 96 MiB used: 37 MiB (38.6%) fs: vfat dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 10 rev: 2.0 speed: 480 Mb/s lanes: 1
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 1-2:2 info: Razer USA DeathAdder Elite type: mouse,keyboard
driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s lanes: 1 power: 500mA
chip-ID: 1532:005c class-ID: 0300
Device-2: 1-9:3 info: Integrated Express RGB LED Controller type: HID
driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s lanes: 1 power: 100mA
chip-ID: 048d:5702 class-ID: 0300
Hub-2: 1-10:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s lanes: 1 power: 100mA
chip-ID: 05e3:0608 class-ID: 0900
Hub-3: 2-0:1 info: super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s lanes: 1 chip-ID: 1d6b:0003
class-ID: 0900
Device-1: 2-4:2 info: USB Disk 20 type: mass storage driver: usb-storage interfaces: 1 rev: 3.2
speed: 5 Gb/s lanes: 1 power: 144mA chip-ID: 346d:5678 class-ID: 0806 serial:
Hub-4: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s lanes: 1
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 3-1:2 info: SINO WEALTH Wired Gaming Keyboard type: keyboard,HID
driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 12 Mb/s lanes: 1 power: 500mA
chip-ID: 258a:002a class-ID: 0300
Device-2: 3-2:3 info: GDMicro ZUOYA GMK26 type: keyboard,HID driver: hid-generic,usbhid
interfaces: 4 rev: 2.0 speed: 12 Mb/s lanes: 1 power: 500mA chip-ID: 28e9:3014 class-ID: 0300
Hub-5: 4-0:1 info: super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s lanes: 1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-6: 5-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s lanes: 1
chip-ID: 1d6b:0002 class-ID: 0900
Hub-7: 5-1:2 info: Microchip (formerly SMSC) USB2734 ports: 5 rev: 2.1 speed: 480 Mb/s lanes: 1
chip-ID: 0424:2734 class-ID: 0900
Hub-8: 5-1.1:3 info: Genesys Logic Hub ports: 4 rev: 2.1 speed: 480 Mb/s lanes: 1 power: 100mA
chip-ID: 05e3:0610 class-ID: 0900
Device-1: 5-1.1.1:5 info: TP-Link Bluetooth USB Adapter type: bluetooth driver: btusb
interfaces: 2 rev: 1.1 speed: 12 Mb/s lanes: 1 power: 500mA chip-ID: 2357:0604 class-ID: e001
serial:
Device-2: 5-1.5:4 info: Microchip (formerly SMSC) Hub Controller type: HID
driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 480 Mb/s lanes: 1 chip-ID: 0424:274b
class-ID: 0300
Device-3: 5-2:7 info: Motorola PCS XT1541 [Moto G 3rd Gen] type:
driver: usbfs interfaces: 1 rev: 2.1 speed: 480 Mb/s lanes: 1 power: 500mA chip-ID: 22b8:2e82
class-ID: 0000 serial:
Hub-9: 6-0:1 info: super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s lanes: 1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-10: 6-1:2 info: Microchip (formerly SMSC) USB5734 ports: 5 rev: 3.2 speed: 5 Gb/s lanes: 1
chip-ID: 0424:5734 class-ID: 0900
Hub-11: 6-1.1:3 info: Genesys Logic Hub ports: 4 rev: 3.2 speed: 5 Gb/s lanes: 1
chip-ID: 05e3:0626 class-ID: 0900
Sensors:
System Temperatures: cpu: 41.2 C mobo: 29.0 C gpu: amdgpu temp: 31.0 C
Fan Speeds (rpm): N/A
Repos:
Packages: 3764 pm: dpkg pkgs: 3684 pm: flatpak pkgs: 80
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/maarten-fonville-android-studio-noble.list
1: deb [signed-by=/etc/apt/keyrings/maarten-fonville-android-studio-noble.gpg] https: //ppa.launchpadcontent.net/maarten-fonville/android-studio/ubuntu noble main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb https: //mirror.cs.jmu.edu/pub/linuxmint/packages zena main upstream import backport
2: deb https: //atl.mirrors.clouvider.net/ubuntu noble main restricted universe multiverse
3: deb https: //atl.mirrors.clouvider.net/ubuntu noble-updates main restricted universe multiverse
4: deb https: //atl.mirrors.clouvider.net/ubuntu noble-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ noble-security main restricted universe multiverse
Active apt repos in: /etc/apt/sources.list.d/nodesource.sources
1: deb [arch=amd64] https: //deb.nodesource.com/node_20.x nodistro main
Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.sources
1: deb https: //repo.protonvpn.com/debian stable main
Active apt repos in: /etc/apt/sources.list.d/vscode.sources
1: deb [arch=amd64] https: //packages.microsoft.com/repos/code stable main
Active apt repos in: /etc/apt/sources.list.d/winehq-noble.sources
1: deb [arch=amd64 i386] https: //dl.winehq.org/wine-builds/ubuntu noble main
Info:
Memory: total: 32 GiB note: est. available: 30.69 GiB used: 4.62 GiB (15.0%)
Processes: 397 Power: uptime: 9m states: freeze,mem,disk suspend: deep wakeups: 0
hibernate: platform Init: systemd v: 255 target: graphical (5) default: graphical
Compilers: gcc: 13.3.0 alt: 11/12 Client: Unknown python3.12 client inxi: 3.3.34
[/code]
**

yeah basically im running this script to find out why if i get a core from it i can analyze it and find this particular hang and fix it

#!/usr/bin/env bash
TIMEOUT=1   # seconds
ping_nemo() {
    if [ -z "$DBUS_SESSION_BUS_ADDRESS" ]; then
        eval "$(dbus-launch --sh-syntax)"
    fi

    timeout "${TIMEOUT}s" \
        gdbus call --session --dest org.Nemo --object-path /org/Nemo --method org.freedesktop.DBus.Peer.Ping \
        >/dev/null
    return $?
}

get_nemo_pid() {
    local pids
    pids=$(pidof nemo) || return 1
    echo "${pids%% *}"
}

dump_core() {
    local pid=$1
    local ts
    ts=$(date -u +"%Y%m%d%H%M%S")
    local core_file="core.${pid}.${ts}"
    gdb -batch \
        -ex "attach ${pid}" \
        -ex "generate-core-file ${core_file}" \
        -ex "detach" \
        -ex "quit" \
        && echo "[INFO] Core dump written to ${core_file}" \
        || echo "[ERROR] GDB failed for PID ${pid}"
}

if ping_nemo; then
    exit 0
else
    echo "Nemo is not responding. Generating core dump..."
    NEMO_PID=$(get_nemo_pid) || {
        echo "[ERROR] Could not find Nemo PID." >&2
        exit 1
    }
    dump_core "$NEMO_PID"
fi

Omg I can't believe this is what's happening to me! I've had issues with Nemo on both PopOS and Ubuntu 24.04 when after a while it becomes unresponsive and then takes several minutes to restart. I just tried unplugging my /e/OS phone which was set to no data transfer and just like that it opened.

I'm also having this extremely frustrating issue. Whenever I plug the phone in, after a while, Files hangs. As soon as I unplug the phone, Files works again normally.

Phone: Motorola g84 5G
Phone OS: e/OS
Connection: Type C to Type C, Via a hub
Computer: HP EliteBook 845 G8
OS Version: Linux Mint 22.3 - Cinnamon 64-bit
Kernel Version: 7.0.0-30-generic

The same bug is reported in:
#3394
#3270

It's been going on for at least a few years, so it'd be good to see it get some attention because unplugging your phone is not an obvious fix for the file browser not working.

places-sidebar: query disk-full info async to avoid hangs on unrespon…

Same issue with Motorola Moto G56 5G — GVFS/PTP errors and Nemo timeout (Linux Mint 22.3)

I can confirm experiencing a very similar issue on Linux Mint 22.3 Cinnamon with a Motorola Moto G56 5G connected via USB.

Interestingly, another user in this thread reported the same behavior with a Motorola G84 5G, which may indicate a broader compatibility issue involving Motorola Android devices, GVFS/PTP and Nemo.

I collected diagnostic logs during the incident on October 18, 2026.

System information

Distribution: Linux Mint 22.3 Zena
Desktop environment: Cinnamon 6.6.9
File manager: Nemo 6.6.3
Kernel: 7.0.0-38-generic
GVFS: 1.54.4
libgphoto2: 2.5.31
Phone: Motorola Moto G56 5G
USB VID:PID: 22b8:2e82

Problem description

Nemo suddenly stopped opening directories, including my home directory.

Running the following commands:

nemo -q
nemo ~

resulted in Nemo becoming unresponsive and eventually producing this error:

Could not register nemo as a remote: Истекло время ожидания

The Russian text means "Connection timed out."

I also verified that the user D-Bus session remained responsive:

timeout 5 busctl --user list > /dev/null
echo "D-Bus exit code: $?"

Result:

D-Bus exit code: 0

This suggests that the entire D-Bus session was not unresponsive.

Relevant GVFS errors

The user journal repeatedly contained:

gvfsd: Error 2: PTP Layer error 02ff: Error getting friendlyname.
gvfsd: Error 2: Error 02ff: PTP I/O Error

Additional messages included:

PTP: reading event an error 0x05 occurred
Device 0 (VID=22b8 and PID=2e82) is a Motorola Moto G (ID2).
Android device detected, assigning default bug flags

After reconnecting the phone, another GVFS error appeared:

Error 1: Get Storage information failed.

Timeline — October 18, 2026

All times are local (UTC+02:00).

12:08:17 — Repeated GVFS PTP I/O errors while the phone was connected.
12:10:17 — Additional PTP errors.
12:11:56 — The USB device was disconnected.
12:14:29 — Nemo debug output showed successful creation and loading of the home directory window after the phone was disconnected.
12:15:49 — The Motorola device was connected again. GVFS subsequently reported a storage information error.

Nemo is currently working again. The issue appears intermittent, and I have not yet established a reliable reproduction procedure.

Interesting detail: USB device identification

Although my phone is a Motorola Moto G56 5G, the Linux kernel reports the following USB product string:

idVendor=22b8, idProduct=2e82
Product: moto g54 5G
Manufacturer: motorola

The device model reported by the USB descriptor differs from the actual phone model.

I am including this observation because it may be relevant when investigating device detection and compatibility.

Possible cause

Based on the available evidence, I suspect that Nemo may be performing a blocking operation while querying a connected Android device through GVFS/PTP.

If the device does not respond correctly, Nemo may become unresponsive instead of continuing normally.

However, the logs establish only a correlation between the GVFS errors and the Nemo failure, not a definitive root cause.

Expected behavior

Nemo should remain responsive even when an attached Android device fails to provide storage information or respond to PTP requests.

Problems accessing an external device should not prevent users from opening local directories.

Additional information

I noticed that commits referencing this issue propose asynchronous disk information queries in the Nemo places sidebar.

Could the maintainers confirm whether those changes are expected to address this behavior and whether they are available in any released version?

I have attached a sanitized diagnostic archive containing:

System and package versions
GVFS/PTP error messages
USB connection and disconnection events
Nemo debug output after recovery

Thank you for investigating this issue. I hope the additional logs and the information about another affected Motorola device will help identify the root cause.

nemo-recovered-debug-excerpt.log
phone-usb-events.log
gvfs-ptp-events.log
system-versions.txt

Navigation Menu

Repository navigation

Nemo hangs after phone being plugged in for a while #3764

Distribution

Package version

Frequency

Bug description

Steps to reproduce

Expected behavior

Additional information

Same issue with Motorola Moto G56 5G — GVFS/PTP errors and Nemo timeout (Linux Mint 22.3)

System information

Problem description

Relevant GVFS errors

Timeline — October 18, 2026

Interesting detail: USB device identification

Possible cause

Expected behavior

Additional information

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Nemo hangs after phone being plugged in for a while #3764

Description

Distribution

Package version

Frequency

Bug description

Steps to reproduce

Expected behavior

Additional information

Activity

mattbatt commented on Jun 9, 2026

loosestrife commented on Jun 23, 2026

geekysquirrel commented on Jul 18, 2026

eburger01 commented on Aug 28, 2026

0x00000109 commented on Oct 18, 2026

Same issue with Motorola Moto G56 5G — GVFS/PTP errors and Nemo timeout (Linux Mint 22.3)

System information

Problem description

Relevant GVFS errors

Timeline — October 18, 2026

Interesting detail: USB device identification

Possible cause

Expected behavior

Additional information

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions