#Programs Frequently Become Unresponsive

1 messages · Page 1 of 1 (latest)

outer lintel
#

Every time I open a program, it stops responding after a while, usually when downloading, clicking the close configuration window, trying to download something from Trivant, or sometimes just by double-clicking something or randomly. If I wait for it to respond, it never does, and I always have to force-quit the program once it becomes unresponsive. What should I do?

slim oriole
#

very strange. can you drop to a tty when this happens and gather dmesg output to fpaste

vivid thicket
#

same here! I did a rollback to the previous deployment now its fine!

                   Digest: sha256:c8ab34147557c6fc7c749db19954858c8fa0ba9350d63807908c58f1f9124fd0
                  Version: 42.20250815.0 (2025-08-15T06:55:16Z)
                   Commit: ad43ea9def33497e3a0b475fcbbaa68d13dba32afb1ec1ee123109f8284a69c0
                StateRoot: default

  ostree-unverified-registry:ghcr.io/secureblue/silverblue-nvidia-open-hardened:latest (index: 2)
                   Digest: sha256:a7777b835047b59a7106c8cf79d0c2588ad6f9f9a1e8578f24500df8e8d26cca
                  Version: 42.20250816.0 (2025-08-16T19:58:15Z)
                   Commit: ef06928202d624d0083ea7ed41e2a1246ff9bd3d642f3dc8088ac99100dbd347
                StateRoot: default
# 
                 Upgraded: akmod-nvidia 3:575.64.05-1.fc42 -> 3:580.76.05-1.fc42
                           apr 1.7.5-2.fc42 -> 1.7.6-3.fc42
                           distribution-gpg-keys 1.113-1.fc42 -> 1.114-1.fc42
                           jxl-pixbuf-loader 1:0.11.1-2.fc42 -> 1:0.11.1-4.fc42
                           kmod-nvidia-6.15.9-201.fc42.x86_64 3:575.64.05-1.fc42 -> 3:580.76.05-1.fc42
                           libjxl 1:0.11.1-2.fc42 -> 1:0.11.1-4.fc42
                           libnvidia-cfg 3:575.64.05-1.fc42 -> 3:580.76.05-1.fc42
                           libnvidia-fbc 3:575.64.05-1.fc42 -> 3:580.76.05-1.fc42
                           libnvidia-gpucomp 3:575.64.05-1.fc42 -> 3:580.76.05-1.fc42
                           libnvidia-ml 3:575.64.05-1.fc42 -> 3:580.76.05-1.fc42
                           libtiff 4.7.0-6.fc42 -> 4.7.0-7.fc42
                           libusb1 1.0.29-1.fc42 -> 1.0.29-3.fc42
                           nvidia-driver 3:575.64.05-1.fc42 -> 3:580.76.05-1.fc42
                           nvidia-driver-cuda 3:575.64.05-1.fc42 -> 3:580.76.05-1.fc42
                           nvidia-driver-cuda-libs 3:575.64.05-1.fc42 -> 3:580.76.05-1.fc42
                           nvidia-driver-libs 3:575.64.05-1.fc42 -> 3:580.76.05-1.fc42
                           nvidia-kmod-common 3:575.64.05-1.fc42 -> 3:580.76.05-1.fc42
                           nvidia-libXNVCtrl 3:575.64.05-1.fc42 -> 3:580.76.05-1.fc42
                           nvidia-modprobe 3:575.64.05-1.fc42 -> 3:580.76.05-1.fc42
                           nvidia-persistenced 3:575.64.05-1.fc42 -> 3:580.76.05-1.fc42
                           nvidia-settings 3:575.64.05-1.fc42 -> 3:580.76.05-1.fc42
slim oriole
#

sounds like nvidia introduced a serious bug in their new 580 driver

vivid thicket
#

ahh thats the thing!

lavish cosmos
#

Something else is going on... my file managers and even terminals were not responding so I reinstalled 3 times now.This is not a hardware issue I almost suspect the Nvidia drivers could be doing something they always want me to enable and install them despite the open source ones being installed.

slim oriole
#

it's one of the many reasons we're switching away from it

slim oriole
vivid thicket
wanton current
#

I have the same issue lately but only with certain flatpaks. I'm on kinoite-nvidia-hardened:latest with nvidia 580.76.05.

#

happens only when I try to close an app

zinc shell
#

Same is happening to me. Most likely an nvidia bug.
If application is run with VK_DRIVER_FILES= it launches/closes just fine.(wont use gpu)

wanton current
zinc shell