Recently updated Zorin and now having issues with opening Nautilus File Manager which usually takes around 5 mins. Text Editor also has about a 1 min delay.
Troubleshooting......
Re-install nautilus (Didn't Fix)
sudo killall nautilus
sudo apt-get install --reinstall nautilus nautilus-data gnome-system-monitor
Revert Kernel (Didn't Fix)
uname -rs
find /boot/vmli*
dpkg --list | grep linux-image
apt install linux-image-5.15.0-75-generic linux-headers-5.15.0-75-generic -y
apt install grub-customizer -y
# set kernel version in grub-customizer then reboot
uname -rs
Log Review
sudo killall nautilus
nautilus -c
running nautilus_self_check_file_utilities
running nautilus_self_check_file_operations
running nautilus_self_check_directory
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.AfcuVolumeMonitor: Timeout was reached (g-io-error-quark, 24)
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.AfcVolumeMonitor: Timeout was reached (g-io-error-quark, 24)
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.AfcVolumeMonitor: Timeout was reached (g-io-error-quark, 24)
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.AfcVolumeMonitor: Timeout was reached (g-io-error-quark, 24)
....<Repeats....>
journalctl -f
Sep 02 12:17:45 device nautilus[3135]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x55847f92a6a0
Sep 02 12:17:45 device nautilus[3135]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x55847f7069d0
Sep 02 12:18:00 device org.gnome.Nautilus[3135]: running nautilus_self_check_file_utilities
Sep 02 12:18:00 device org.gnome.Nautilus[3135]: running nautilus_self_check_file_operations
Sep 02 12:18:00 device org.gnome.Nautilus[3135]: running nautilus_self_check_directory
Sep 02 12:18:00 device org.gnome.Nautilus[3135]: FAIL: check failed in ../src/nautilus-directory.c, line 1987
Sep 02 12:18:00 device org.gnome.Nautilus[3135]: evaluated: g_hash_table_size (directories)
Sep 02 12:18:00 device org.gnome.Nautilus[3135]: expected: 1
Sep 02 12:18:00 device org.gnome.Nautilus[3135]: got: 17
Sep 02 12:19:56 device dbus-daemon[2415]: [session uid=1000 pid=2415] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.139' (uid=1000 pid=8206 comm="nautilus -c " label="unconfined")
Sep 02 12:19:56 device systemd[2330]: Starting Virtual filesystem service - Apple File Conduit monitor...
Sep 02 12:19:56 device gvfs-afc-volume-monitor[8217]: /usr/libexec/gvfs-afc-volume-monitor: error while loading shared libraries: libimobiledevice.so.6: cannot open shared object file: No such file or directory
Sep 02 12:19:56 device systemd[2330
Sep 02 12:19:56 device systemd[2330]: gvfs-afc-volume-monitor.service: Failed with result 'exit-code'.
Sep 02 12:19:56 device systemd[2330]: Failed to start Virtual filesystem service - Apple File Conduit monitor.
! Issue = Apple File Conduit monitor !
ls -lah /usr/libexec/gvfs-afc-volume-monitor
-rwxr-xr-x 1 root root 111K Mar 3 2023 /usr/libexec/gvfs-afc-volume-monitor
Any advice how to solve this issue would be appreciated.