On Wed, Oct 29, 2025 at 4:55 PM Michael D. Setzer II via users <[email protected]> wrote: > > Recently seen a delay of around 30 seconds with both chrome and > chromium on Fedora 42? Before both would be almost instant. > > line > ppoll([{fd=56, events=POLLIN}], 1, {tv_sec=24, > tv_nsec=999962000}, NULL, 8) = 0 (Timeout) > > Seems fd=56 is linked to libscret? > > openat(AT_FDCWD, "/lib64/libsecret-1.so.0", > O_RDONLY|O_CLOEXEC) = 56
A Ppoll call makes no sense to be used/timeout for a file/library. You have to be careful with fds, they get closed and reused all of the time, so likely there was an earlier open of 56 and a close of 56 before the openat you have. So you need to find what call opened 56 before the ppoll timeout. It is probably going to be some network socket based on ppoll being used. And given google chrome does DUMB things (like complaining that it cannot UPDATE its code-big shocker since it is installed as ROOT but running as a USER and was installed from an RPM). Whoever coded it for Linux ASSUMES that Linux works like Windows. -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
