Window appears with a delay

Dear all, I’m a brand new user, coming form Tuxedo_OS to try Silverblue! Just curious and because Fedora is advised by privacy and security experts. My first steps in the Fedora world!
Now I face the following issue: if I select Nautilus, I have to wait for about 30 - 45 seconds before the Nautilus windows appears. Same applies to other Gnome apps. What can be the cause and how can I solve it for a smooth experience? Btw, I have Nvidia drivers installed, my laptop is a Tuxedo Polaris 17 inch.

Welcome to Fedora @sparks-linux

First check if there is a update available and second if updated try to create a new user and see if you have the same issues.

1 Like

Thanks for the welcome words!

In the newly-created user I still face the same problem: apps windows don´t appear immediately. Sometimes I have to wait for 1 minute before they appear. I think my laptop is struggling with ram or something in combination with Silverblue. I don’t know.

The common advice for debugging anything on Linux is, to run it from the Terminal

Open it, and run nautilus.

Also please give us relevant system infos, found in the settings, scroll to the bottom

Also via the terminal the nautilus windows appeared with a delay.

I wanted to paste the system info here, but it seems not possible, for unknown reason. Now I upload the picture of the system info here, see below. It is in Dutch, but English terms are very similar to the Dutch words here.

Strange that the system info did not talk about the Nvidia graphic card, although I installed it following the procedure given in Troubleshooting :: Fedora Docs.

$ glxinfo | grep -e OpenGL.vendor -e OpenGL.renderer
OpenGL vendor string: AMD

and

$ lspci -n -n -k | grep -A 2 -e VGA -e 3D
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev a1)
Subsystem: AIstone Global Limited Device [1d05:1111]
Kernel driver in use: nvidia
06:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c5)
Subsystem: AIstone Global Limited Device [1d05:1111]
Kernel driver in use: amdgpu

Additional info: prior to the installation of Fedora Silverblue, I had serious issues after the big upgrade of Tuxedo_OS from 22.04 to 24.04: the movies are very laggy, video contact via Signal gives a lot of strong hicups and very bad sounds. That was the reason for me to change the OS to Fedora. The movies and Signal are much better now, however still with small hicups. I tend to think that Nvidia graphic card is a bit broken.

As you advice me in my other post about keys of my laptop, I’ll contact Tuxedo here.

1 Like

Added tuxedo

Strange that GNOME reports two AMD graphics cards.

Do you know which version of Nvidia are you on?

In case you have a container set up, can you install inxi and run inxi -Fzxx, then post the output here as preformatted text, using the </> button? No need to layer the package.

If not, please post the output of lspci -v | grep -i 'Display' -A 7.

I’m wondering if there are any BIOS/UEFI settings for the laptop that selects which GPU to use. Laptops that have dedicated GPUs sometimes have Mux switches that allow for one GPU to do all of the work or the other. If the laptop is set to only use the iGPU, then maybe that’s why only the AMD is being shown twice for some reason?

1 Like

Hi Mike,

I have Nvidia GeForce RTX 3060. The lspci command you gave, did not show any output. And no, I have not set up a container for Nvidia driver (I should learn more about containers!).

I found in the BIOS menu something, see picture atached here.


It is set to “MSHybrid” which seems okay.

Containers are not needed for installing the Nvidia driver, but can be useful to install utilities that are not available in the OSTree image and neither as Flatpaks, and layering them is not a requirement. The basics are simple, so if you’d like to start now, these would be the steps:

  • Create a Toolbx container: toolbox create. Give it a couple of minutes, because an F41 image required to create the container will be downloaded.
  • Enter the Toolbx container: toolbox enter.
  • Install inxi via dnf: sudo dnf install inxi.
  • Run inxi -Fzxx.
  • Copy the output and post it here as preformatted text.
  • Exit the Toolbx container: logout.

Please also post the output of rpm-ostree status, to see what nvidia packages have been layered, as well as the used kernel arguments by running rpm-ostree kargs.

output inxi:

System:
  Kernel: 6.11.6-300.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.43.1-2.fc41
  Desktop: GNOME v: N/A wm: gnome-shell dm: N/A Distro: Fedora Linux 41
    (Toolbx Container Image)
Machine:
  Type: Laptop System: TUXEDO product: TUXEDO Polaris AMD Gen3 (CZN)
    v: Standard serial: <superuser required>
  Mobo: NB02 model: GMxZGxx v: Standard serial: <superuser required>
    part-nu: POLARIS1XA03 UEFI: American Megatrends LLC. v: N.1.50A12
    date: 09/06/2022
Battery:
  ID-1: BAT0 charge: 45.6 Wh (100.0%) condition: 45.6/62.3 Wh (73.2%)
    volts: 16.8 min: 15.2 model: standard serial: <filter> status: full
CPU:
  Info: 8-core model: AMD Ryzen 7 5800H 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: 3436 min/max: 400/4463 boost: enabled cores: 1: 3436
    2: 3436 3: 3436 4: 3436 5: 3436 6: 3436 7: 3436 8: 3436 9: 3436 10: 3436
    11: 3436 12: 3436 13: 3436 14: 3436 15: 3436 16: 3436 bogomips: 102209
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q]
    vendor: AIstone Global driver: nvidia v: 565.57.01 arch: Ampere pcie:
    speed: 8 GT/s lanes: 8 ports: active: none empty: DP-1,HDMI-A-1,eDP-2
    bus-ID: 01:00.0 chip-ID: 10de:2520
  Device-2: Advanced Micro Devices [AMD/ATI] Cezanne [Radeon Vega Series /
    Radeon Mobile Series] vendor: AIstone Global driver: amdgpu v: kernel
    arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports: active: eDP-1 empty: none
    bus-ID: 06:00.0 chip-ID: 1002:1638 temp: 43.0 C
  Device-3: Bison HD Webcam driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 1-4:4 chip-ID: 5986:9109
  Display: wayland server: N/A compositor: gnome-shell driver: gpu: amdgpu
    display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x0977 res: 2560x1440 dpi: 171
    diag: 437mm (17.2")
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: NVIDIA GA106 High Definition Audio vendor: AIstone Global
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 8 bus-ID: 01:00.1
    chip-ID: 10de:228e
  Device-2: Advanced Micro Devices [AMD] ACP/ACP3X/ACP6x Audio Coprocessor
    vendor: AIstone Global driver: N/A pcie: speed: 8 GT/s lanes: 16
    bus-ID: 06:00.5 chip-ID: 1022:15e2
  Device-3: Advanced Micro Devices [AMD] Family 17h/19h HD Audio
    vendor: AIstone Global driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s
    lanes: 16 bus-ID: 06:00.6 chip-ID: 1022:15e3
  API: ALSA v: k6.11.6-300.fc41.x86_64 status: kernel-api
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: AIstone Global driver: r8169
    v: kernel pcie: speed: 5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0
    chip-ID: 10ec:8125
  IF: enp2s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie:
    speed: 5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:2723
  IF: wlp4s0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 3-4:3 chip-ID: 8087:0029
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 476.94 GiB used: 27.76 GiB (5.8%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 PRO 512GB
    size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 25.9 C
Partition:
  Message: No partition data found.
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 58.9 C mobo: N/A gpu: amdgpu temp: 42.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB note: est. available: 15.02 GiB used: 4.39 GiB (29.2%)
  Processes: 474 Power: uptime: 10m wakeups: 0 Init: systemd v: 256
    default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: N/A Shell: Bash
    v: 5.2.32 running-in: conmon inxi: 3.3.36

output rpm-ostree status:

State: idle
Deployments:
● fedora:fedora/41/x86_64/silverblue
                  Version: 41.20241109.0 (2024-11-09T00:42:19Z)
               BaseCommit: 61ab16e2273502cd443ca561fca67c621be7ac15de8b70cbafeb1ac281104f32
             GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1
      RemovedBasePackages: mesa-va-drivers 24.2.6-1.fc41
          LayeredPackages: kmod-nvidia libva-nvidia-driver mesa-va-drivers-freeworld openssl rpmfusion-free-release
                           rpmfusion-nonfree-release xorg-x11-drv-nvidia

  fedora:fedora/41/x86_64/silverblue
                  Version: 41.20241109.0 (2024-11-09T00:42:19Z)
               BaseCommit: 61ab16e2273502cd443ca561fca67c621be7ac15de8b70cbafeb1ac281104f32
             GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1
          LayeredPackages: kmod-nvidia openssl rpmfusion-free-release rpmfusion-nonfree-release xorg-x11-drv-nvidia

output rpm-ostree kargs:

rhgb quiet root=UUID=666e68ac-cbdf-48a3-8713-7e59cf4010df rootflags=subvol=root rw ostree=/ostree/boot.1/fedora/230f2c8bd1f03dee337acf958d78e4a077e765ca4690844b8969b9ada612ec42/0 rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init

Do you see anything useful? I’m curious! And great to have used the Toolbx!

Well, according to inxi, you seem to be on the latest version of Nvidia drivers. However, the 565.xx version, besides bringing some important updates, according to some reports here, seems not to be working for everybody.

So I would try to exclude/confirm that Nvidia version 565.xx is causing the issues. Here are some ideas you might want to try:

  • First exclude that the package libva-nvidia-driver is causing the issues. Probably not, but it’s easy to test by booting with the previous deployment, which doesn’t have this package layered;
  • Run Nautilus in debugging mode, with G_MESSAGES_DEBUG="all" nautilus. You might catch relevant information;
  • Temporarily suspend the discrete GPU (from BIOS) if possible;
  • Uninstall nvidia driver version 565.xx and test if issue still occurs (remember to remove the blocklisting kernel arguments);
  • If with the above step you cannot reproduce the issue, you might want to try to install the 560.xx version (which is in the rpmfusion-nonfree repo, so you would need to disable/uninstall the rpmfusion-nonfree-updates repo/package).

A word of caution: I have no Nvidia GPU on my systems, and have not tested the above steps.

  • liva-nvidia-driver will not help because I installed it in a later stadium, afther the issue took place.
  • running Nautilus in debugging mode gives no relevant information (no warning message)
  • suspending the dGPU is not possible, I think
  • uninstalling the nvidia driver following the (safe) instruction in RPMFusion page after I installed the nvidia drive according to rpm fusion:
rpm-ostree remove xorg-x11-drv-nvidia\*
error: Package/capability 'xorg-x11-drv-nvidia*' is not currently requested

How can I solve it?

Try without search operators:

rpm-ostree uninstall kmod-nvidia xorg-x11-drv-nvidia

I have just realized that you’re experiencing issues with other apps, not only nautilus, as per your original post.

Please check if this fix is working. If it does, you can find in that thread also the reasoning behind the issues.

2 Likes

This fix works, thanks!
Now I can look at other problems to be solved (such as no smooth experience with movies, sometimes the mouse freezes for about 2 seconds, no startup from sleep after closing the laptop lid, etc.). But for now this problem with windows can be considered as solved. Thank you again!

2 Likes