Oh interesting, I had no idea this existed... I did a grep for around when I was seeing the odd behaviour. This is what I found.
Feb 04 15:50:35 iridium.noblet.ca gvfsd[2776816]: Error 2: PTP Layer error 02ff: Error getting friendlyname. Feb 04 15:50:35 iridium.noblet.ca gvfsd[2776816]: Error 2: Error 02ff: PTP I/O Error Feb 04 15:52:35 iridium.noblet.ca gvfsd[2776816]: Error 2: PTP Layer error 02ff: Error getting friendlyname. Feb 04 15:52:35 iridium.noblet.ca gvfsd[2776816]: Error 2: Error 02ff: PTP I/O Error Feb 04 15:53:58 iridium.noblet.ca systemd[3352]: app-gnome- org.gnome.Evolution-2812865.scope: Consumed 56.950s CPU time, 602.7M memory peak. Feb 04 15:54:03 iridium.noblet.ca gvfsd[2776816]: PTP: reading event an error 0x05 occurred Feb 04 15:54:03 iridium.noblet.ca gvfsd[2776816]: Error 2: PTP Layer error 02ff: Error getting friendlyname. Feb 04 15:54:03 iridium.noblet.ca gvfsd[2776816]: Error 2: Error 02ff: PTP I/O Error Feb 04 15:54:03 iridium.noblet.ca gvfsd[2776816]: Error 2: PTP Layer error 02ff: Error getting friendlyname. Feb 04 15:54:03 iridium.noblet.ca gvfsd[2776816]: Error 2: Error 02ff: PTP I/O Error Looking into that it matches up with what I was seeing and a google search says those errors is an issue between linux and android devices and can cause file manager hangs... I wonder what is causing that communication error sometimes. -- Nathanael On Thu, 2026-02-05 at 00:01 +0100, Eric Ashley via devel wrote: > Does the journal have any nautilus messages logged during the hang? > > Feb 4, 2026, 17:58 by [email protected]: > > > Ok, so as usual I found an interesting bit of information after > > writing > > that. > > > > After about 10 minutes, the file manager window opened and there > > was an > > 'mtp' mount because my Pixel 9a was plugged in (mostly for charging > > purposes). When I unplugged it, nautilus sprang to life. So in an > > effort to reproduce it, I plugged it back in, but it just showed up > > properly as "Pixel 9a" instead of "mtp" and everything worked. > > > > I unplugged it, closed Nautilus, plugged it back in and opened > > Nautilus. It worked perfectly. > > > > > > So I don't know the root cause but have more info than I have had > > for > > the last few months. Any help would still be appreciated. > > > > Sincerely, > > -- > > Nathanael > > -- > > _______________________________________________ > > devel mailing list -- [email protected] > > To unsubscribe send an email to [email protected] > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: > > https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/[email protected] > > Do not reply to spam, report it: > > https://forge.fedoraproject.org/infra/tickets/issues/new > > -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
