On Sun, 8 Dec 2019 14:25:30 -0500 Tom Horsley <horsley1953@xxxxxxxxx> wrote: > On Sun, 08 Dec 2019 19:12:02 +0000 > Patrick O'Callaghan wrote: > > > Maybe do an 'strace' on the process. > > I've done that, but nothing obvious is going on. However > I now have a definite clue: > > In my fedora 31 virtual machine, the hang happens the > same way. > > If I use virt-manager to tell it to emulate IvyBridge > instead of native cpu, there is no hang! > > I have this feeling there is one of those gnu-indirect > functions in the library that is busted for whatever > architecture feature it is checking for on an i9-9900K > and that indirectly screws up something in gtk2. The fact that the delay is exactly 30 seconds supports this, as that sounds like a timeout value that is set. Do you have any custom tweaks left around that apply to your old cpu and not to your new one? There are no bugs open against i9-9900k in the fedora bugzilla, so if this is real and not an artifact of leftover cruft, no one is looking at it. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/users@xxxxxxxxxxxxxxxxxxxxxxx
