Fedora 43 strange behaviour - Gnome "Files" slow to start - 1 minute

Hi there,

I already posted how I had and still have issues lunching flatpacks but it does not stop there. Now when I click on the Files icon it takes 1 min for the file explorer to appear.

Can anybody help? It’s really annoying.

Update*** Now flatpaks work except for MS edge which starts working and then shoutdowns.

Post the output from inxi -Fzxx so we can see the full specs, versions and details of your tin. Post this as pre-formatted text </> otherwise it’s a nightmare to read.

  1. Run the journalctl -f in a terminal.
  2. Start up “Files” (which I assume is some Gnome program as you don’t specify your desktop in the tags)
  3. Post whatever output is spewed into the output of the journalctl in the terminal window.
$ inxi -Fzxx
System:
  Kernel: 6.18.8-200.fc43.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
  Desktop: GNOME v: 49.3 tk: GTK v: 3.24.51 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 43 (Workstation Edition)
Machine:
  Type: Laptop System: Acer product: Aspire A515-47 v: V1.03
    serial: <superuser required>
  Mobo: BC model: Ganymede_BCU v: V1.03 serial: <superuser required>
    part-nu: 0000000000000000 Firmware: UEFI vendor: Insyde v: 1.03
    date: 07/21/2022
Battery:
  ID-1: BAT1 charge: 47.8 Wh (100%) condition: 47.8/48 Wh (99.5%) volts: 12.17
    min: 11.25 model: LGC AP18C8K serial: <filter> charging: status: full
    cycles: N/A
CPU:
  Info: 8-core model: AMD Ryzen 7 5825U with Radeon Graphics bits: 64
    type: MT MCP arch: Zen 3 rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
  Speed (MHz): avg: 1996 min/max: 411/2000 boost: enabled cores: 1: 1996
    2: 1996 3: 1996 4: 1996 5: 1996 6: 1996 7: 1996 8: 1996 9: 1996 10: 1996
    11: 1996 12: 1996 13: 1996 14: 1996 15: 1996 16: 1996 bogomips: 63881
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
    ssse3 svm
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Barcelo
    vendor: Acer Incorporated ALI driver: amdgpu v: kernel arch: GCN-5 pcie:
    speed: 8 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1,HDMI-A-1
    bus-ID: 04:00.0 chip-ID: 1002:15e7 temp: 41.0 C
  Device-2: Chicony ACER HD User Facing driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 1-3:2 chip-ID: 04f2:b773
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: gnome-shell driver: gpu: amdgpu display-ID: 0
  Monitor-1: eDP-1 model: ChiMei InnoLux 0x15e7 res: 1920x1080 dpi: 142
    diag: 394mm (15.5")
  API: OpenGL v: 4.6 vendor: amd mesa v: 25.3.4 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir ACO DRM
    3.64 6.18.8-200.fc43.x86_64) device-ID: 1002:15e7 display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Renoir/Cezanne HDMI/DP Audio
    vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel pcie:
    speed: 8 GT/s lanes: 16 bus-ID: 04:00.1 chip-ID: 1002:1637
  Device-2: Advanced Micro Devices [AMD] Audio Coprocessor
    vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel pcie:
    speed: 8 GT/s lanes: 16 bus-ID: 04:00.5 chip-ID: 1022:15e2
  Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio
    vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel pcie:
    speed: 8 GT/s lanes: 16 bus-ID: 04:00.6 chip-ID: 1022:15e3
  API: ALSA v: k6.18.8-200.fc43.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.10 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Acer Incorporated ALI driver: r8169 v: kernel pcie: speed: 2.5 GT/s
    lanes: 1 port: 2000 bus-ID: 02:00.0 chip-ID: 10ec:8168
  IF: enp2s0 state: down mac: <filter>
  Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    vendor: Foxconn driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1
    bus-ID: 03:00.0 chip-ID: 14c3:0616
  IF: wlp3s0 state: down mac: <filter>
  Device-3: ASIX AX88179 Gigabit Ethernet driver: ax88179_178a type: USB
    rev: 3.0 speed: 5 Gb/s lanes: 1 bus-ID: 2-2:2 chip-ID: 0b95:1790
  IF: enp4s0f3u2 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: bridge0 state: up speed: 1000 Mbps duplex: unknown mac: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
  IF-ID-3: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
  IF-ID-4: virbr0 state: down mac: <filter>
  IF-ID-5: ztu7tnnyt5 state: unknown speed: 10000 Mbps duplex: full
    mac: <filter>
Bluetooth:
  Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 1-4:3 chip-ID: 0489:e0e4
  Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: disabled
    rfk-block: hardware: no software: yes address: N/A


journalctl -f
Feb 10 22:18:58 device bijiben-shell-search-provider[213039]: Updating resource <I will get back to you as soon as I finish up a meeting.> urn:bnode:599
Feb 10 22:18:58 device bijiben-shell-search-provider[213039]: Updating resource <Untitled (5)> urn:bnode:600
Feb 10 22:18:58 device bijiben-shell-search-provider[213039]: Creating resource <Untitled (7)> /home/quokka/.local/share/bijiben/63b731c7-6c38-41e9-9210-85c277fb125e.note
Feb 10 22:18:58 device bijiben-shell-search-provider[213039]: Updating resource <Security Audit> urn:bnode:604
Feb 10 22:18:58 device bijiben-shell-search-provider[213039]: Updating resource <Firewall config> urn:bnode:603
Feb 10 22:18:58 device bijiben-shell-search-provider[213039]: Updating resource < Automatic Security Updates> urn:bnode:602
Feb 10 22:18:58 device bijiben-shell-search-provider[213039]: Updating resource <SELinux Hardening> urn:bnode:601
Feb 10 22:19:05 device org.gnome.Characters[213037]: JS LOG: Characters Application exiting
Feb 10 22:19:07 device systemd[3755]: Started vte-spawn-90dc2220-e9ea-40b4-aebf-e974a420097a.scope - VTE child process 213963 launched by org.gnome.Terminal process 209449.
Feb 10 22:19:07 device PackageKit[209979]: search-file transaction /42859_aeadaebb from uid 1000 finished with success after 201ms
Feb 10 22:19:10 device systemd[3755]: dbus-:1.2-org.gnome.Nautilus@17.service: Consumed 13.763s CPU time, 246.1M memory peak.
Feb 10 22:19:10 device gnome-shell[4297]: Received error from D-Bus search provider org.gnome.Boxes.desktop: Gio.IOErrorEnum: Cannot invoke method; proxy is for the well-known name “org.gnome.Boxes.SearchProvider” without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Feb 10 22:19:10 device systemd[3755]: Started dbus-:1.2-app.drey.Dialect.SearchProvider@19.service.
Feb 10 22:19:10 device systemd[3755]: Started dbus-:1.2-org.gnome.Calculator.SearchProvider@19.service.
Feb 10 22:19:10 device systemd[3755]: Started dbus-:1.2-org.gnome.Characters@19.service.
Feb 10 22:19:10 device systemd[3755]: Started dbus-:1.2-org.gnome.Contacts.SearchProvider@18.service.
Feb 10 22:19:10 device systemd[3755]: Started dbus-:1.2-org.gnome.Nautilus@18.service.
Feb 10 22:19:10 device systemd[3755]: Started dbus-:1.2-org.gnome.Notes.SearchProvider@18.service.
Feb 10 22:19:10 device systemd[3755]: Started dbus-:1.2-org.gnome.Photos@26.service.
Feb 10 22:19:10 device systemd[3755]: Started dbus-:1.2-org.gnome.clocks@19.service.
Feb 10 22:19:10 device search_provider[214151]: /usr/share/dialect/search_provider:109: SyntaxWarning: 'return' in a 'finally' block
Feb 10 22:19:10 device search_provider[214151]:   return True
Feb 10 22:19:10 device gnome-shell[4297]: Received error from D-Bus search provider org.gnome.Boxes.desktop: Gio.IOErrorEnum: Cannot invoke method; proxy is for the well-known name “org.gnome.Boxes.SearchProvider” without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Feb 10 22:19:11 device gnome-shell[4297]: Received error from D-Bus search provider org.gnome.Boxes.desktop: Gio.IOErrorEnum: Cannot invoke method; proxy is for the well-known name “org.gnome.Boxes.SearchProvider” without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Feb 10 22:19:11 device bijiben-shell-search-provider[214156]: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed
Feb 10 22:19:11 device systemd[3755]: Started dbus-:1.2-com.intel.dleyna\x2drenderer@25.service.
Feb 10 22:19:11 device org.gnome.Characters[214153]: JS LOG: Characters Application started
Feb 10 22:19:11 device bijiben-shell-search-provider[214156]: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed
Feb 10 22:19:11 device bijiben-shell-search-provider[214156]: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed
Feb 10 22:19:11 device bijiben-shell-search-provider[214156]: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed
Feb 10 22:19:11 device dleyna-renderer-service[214250]: dLeyna core version 0.8.3
Feb 10 22:19:11 device dleyna-renderer-service[214250]: dleyna-renderer-service version 0.8.3
Feb 10 22:19:11 device bijiben-shell-search-provider[214156]: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed
Feb 10 22:19:11 device dleyna-renderer-service[214250]: Type[0] Level[0x13] Mask[0x4C] Flags[0x4F]
Feb 10 22:19:11 device dleyna-renderer-service[214250]: Load file [/home/quokka/.config/dleyna-renderer-service.conf]
Feb 10 22:19:11 device dleyna-renderer-service[214250]: [General settings]
Feb 10 22:19:11 device dleyna-renderer-service[214250]: Never Quit: F
Feb 10 22:19:11 device dleyna-renderer-service[214250]: Connector Name: dbus
Feb 10 22:19:11 device dleyna-renderer-service[214250]: Port: 0
Feb 10 22:19:11 device dleyna-renderer-service[214250]: Push host port: 0
Feb 10 22:19:11 device dleyna-renderer-service[214250]: [Logging settings]
Feb 10 22:19:11 device dleyna-renderer-service[214250]: Log Type : 0
Feb 10 22:19:11 device dleyna-renderer-service[214250]: Log Level: 0x13
Feb 10 22:19:11 device dleyna-renderer-service[214250]: [Network filtering settings]
Feb 10 22:19:11 device dleyna-renderer-service[214250]: Enabled : F
Feb 10 22:19:11 device dleyna-renderer-service[214250]: Entries: (null)
Feb 10 22:19:11 device search_provider[214151]: /usr/share/dialect/search_provider:302: DeprecationWarning: 'asyncio.set_event_loop_policy' is deprecated and slated for removal in Python 3.16
Feb 10 22:19:11 device search_provider[214151]:   asyncio.set_event_loop_policy(GLibEventLoopPolicy())
Feb 10 22:19:11 device search_provider[214151]: /usr/share/dialect/search_provider:100: DeprecationWarning: Gio.DBusConnection.register_object is deprecated
Feb 10 22:19:11 device search_provider[214151]:   connection.register_object(
Feb 10 22:19:13 device PackageKit[209979]: resolve transaction /42860_aaaddbdb from uid 1000 finished with success after 7ms
Feb 10 22:19:13 device PackageKit[209979]: resolve transaction /42861_dacecdde from uid 1000 finished with success after 7ms
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <SELinux Hardening> urn:bnode:601
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource < Automatic Security Updates> urn:bnode:602
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <Firewall config> urn:bnode:603
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <Security Audit> urn:bnode:604
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Creating resource <Untitled (7)> /home/quokka/.local/share/bijiben/63b731c7-6c38-41e9-9210-85c277fb125e.note
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <Untitled (5)> urn:bnode:600
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <I will get back to you as soon as I finish up a meeting.> urn:bnode:599
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <Untitled (3)> urn:bnode:594
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <Untitled> urn:bnode:589
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <VIP> urn:bnode:583
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <Meta> urn:bnode:585
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <tasks> urn:bnode:586
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <Workflow> urn:bnode:587
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <SEC> urn:bnode:588
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <Untitled (2)> urn:bnode:590
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <DPO> urn:bnode:591
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <Audio> urn:bnode:593
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <Toolkit> urn:bnode:592
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <Privacy Policy> urn:bnode:595
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <Untitled (4)> urn:bnode:598
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <Untitled (6)> urn:bnode:597
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <Checks> urn:bnode:605
Feb 10 22:19:14 device bijiben-shell-search-provider[214156]: Updating resource <MobSF> urn:bnode:606

$ journalctl
Oct 30 09:03:28 device chronyd[1079]: System clock wrong by -1.701776 seconds
Oct 30 09:03:26 device systemd-journald[667]: Time jumped backwards, rotating.
Oct 30 09:03:26 device systemd-resolved[1039]: Clock change detected. Flushing caches.
Oct 30 09:03:26 device chronyd[1079]: System clock was stepped by -1.701776 seconds
Oct 30 09:03:26 device chronyd[1079]: System clock TAI offset set to 37 seconds
Oct 30 09:03:27 device audit: BPF prog-id=85 op=LOAD
Oct 30 09:03:27 device audit: BPF prog-id=86 op=LOAD
Oct 30 09:03:27 device audit: BPF prog-id=87 op=LOAD
Oct 30 09:03:27 device systemd[1]: Starting plocate-updatedb.service - Update the plocate database...
Oct 30 09:03:28 device tailscaled[1299]: open-conn-track: timeout opening (TCP 100.85.10.13:60272 => 3.8.95.119:80); no associated peer node
Oct 30 09:03:28 device tailscaled[1299]: open-conn-track: timeout opening (TCP 100.85.10.13:40908 => 152.2.23.104:80); no associated peer node
Oct 30 09:03:28 device tailscaled[1299]: open-conn-track: timeout opening (TCP 100.85.10.13:35090 => 38.145.32.21:80); no associated peer node
Oct 30 09:03:29 device tailscaled[1299]: open-conn-track: timeout opening (TCP 100.85.10.13:40916 => 152.2.23.104:80); no associated peer node
Oct 30 09:03:31 device tailscaled[1299]: open-conn-track: timeout opening (TCP 100.85.10.13:40926 => 152.2.23.104:80); no associated peer node
Oct 30 09:03:31 device tailscaled[1299]: [RATELIMIT] format("open-conn-track: timeout opening %v; no associated peer node")
Oct 30 09:03:33 device systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 30 09:03:33 device audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd">
Oct 30 09:03:39 device tailscaled[1299]: [RATELIMIT] format("open-conn-track: timeout opening %v; no associated peer node") (6 dropped)
Oct 30 09:03:39 device tailscaled[1299]: open-conn-track: timeout opening (TCP 100.85.10.13:60272 => 3.8.95.119:80); no associated peer node
Oct 30 09:03:39 device tailscaled[1299]: open-conn-track: timeout opening (TCP 100.85.10.13:35090 => 38.145.32.21:80); no associated peer node
Oct 30 09:03:39 device tailscaled[1299]: [RATELIMIT] format("open-conn-track: timeout opening %v; no associated peer node")
Oct 30 09:03:40 device tailscaled[1299]: logtail: upload succeeded after 1 failures and 52s
Oct 30 09:03:48 device tailscaled[1299]: [RATELIMIT] format("open-conn-track: timeout opening %v; no associated peer node") (9 dropped)
Oct 30 09:03:48 device tailscaled[1299]: open-conn-track: timeout opening (TCP 100.85.10.13:37022 => 85.236.55.6:80); no associated peer node
Oct 30 09:03:49 device tailscaled[1299]: open-conn-track: timeout opening (TCP 100.85.10.13:40916 => 152.2.23.104:80); no associated peer node
Oct 30 09:03:49 device tailscaled[1299]: [RATELIMIT] format("open-conn-track: timeout opening %v; no associated peer node")
Oct 30 09:03:51 device kernel: usb 3-1: new high-speed USB device number 2 using xhci_hcd
Oct 30 09:03:52 device kernel: usb 3-1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice= 6.56
Oct 30 09:03:52 device kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 30 09:03:52 device kernel: usb 3-1: Product: USB2.1 Hub
Oct 30 09:03:52 device kernel: usb 3-1: Manufacturer: GenesysLogic
Oct 30 09:03:52 device kernel: hub 3-1:1.0: USB hub found
Oct 30 09:03:52 device kernel: hub 3-1:1.0: 4 ports detected
Oct 30 09:03:52 device kernel: usb 3-1.2: new low-speed USB device number 3 using xhci_hcd
Oct 30 09:03:52 device kernel: usb 3-1.2: New USB device found, idVendor=258a, idProduct=0001, bcdDevice= 1.00
Oct 30 09:03:52 device kernel: usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 30 09:03:52 device kernel: usb 3-1.2: Product: USB KEYBOARD
Oct 30 09:03:52 device kernel: usb 3-1.2: Manufacturer: SINO WEALTH

this is from October 30th, so I assume it was posted in error.

No, when I entered the command, I got that output.

There was a similar issue with GNOME Files, but it should have been fixed by now:

It’s been resolved. The only issue I am experiencing is when I lunch flatpaks, they start to run and then shutdown for no apparent reason.

Your inxi and journalctl outputs are missing records — probably you only copied the lines visible on your display. Here is the full list of section headers:


% inxi -Fzxx|grep -v '^ '
System:
Machine:
Battery:
CPU:
Graphics:
Audio:
Network:
Bluetooth:
Drives:
Partition:
Swap:
Sensors:
Info:

The journal collects massive amounts of detail, so it is important to learn how to select the records associated with your flatpak issue.
Please read https://docs.fedoraproject.org/en-US/quick-docs/viewing-logs/.

1 Like