FUNG Chi Chuen Sampson wrote:
While trying to collect a backtrace for org.gnome.Tetravex, I got this in gdb:
===
Downloading separate debug info for /lib64/liblzma.so.5... Download failed: Timer expired. Continuing without debug info for /lib64/libbrotlicommon.so.1. Missing separate debuginfo for /lib64/libbrotlicommon.so.1 Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/0e/bb3270fdbf40dbe56ea79d6630ac594b897ffe.debug Download failed: Timer expired. Continuing without debug info for /lib64/libzstd.so.1. Missing separate debuginfo for /lib64/libzstd.so.1 Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/33/70d80a1bf749b3c2baaad0188c864ee9e4bbc4.debug Downloading separate debug info for /lib64/liblz4.so.1... Download failed: Timer expired. Continuing without debug info for /home/fcc/.var/app/org.gnome.Tetravex/cache/debuginfod_client/a2429c266188acc10181f6936915f35274bb4a38/debuginfo. Error while reading shared library symbols for /lib64/liblz4.so.1: could not find '.gnu_debugaltlink' file for /home/fcc/.var/app/org.gnome.Tetravex/cache/debuginfod_client/a2429c266188acc10181f6936915f35274bb4a38/debuginfo Downloading separate debug info for /lib64/libcap.so.2...
I was wondering what the user experience would be like in such a situation. Could you estimate how long you had to wait in total? Was there a long delay before each "Timer expired" message, or only one delay?
Björn Persson