With very high probability there is something GUI related going on, and nothing related to opening files per se. Booting a linux system involves a large number (100000s) of open calls. So it's either the X server / wayland compositor that pauses for whatever reason or the GUI framework that is blocking for some reason. I would rule out hardware problems if the machine is stable, those would crash the machine but not cause any "pauses". Some power management related stuff would be remotely possible (machine trying to go to sleep), but why would that be triggered by openening files.
Am Sonntag, dem 13.04.2025 um 13:47 -0400 schrieb gene heskett: > > I would check if there are some hanging network > > mounts. If possible, check hanging processes which state they are > > in > > ('D' means "uninterruptible wait", i.e. waiting for some blocking > > file- > > I/O to complete, hanging NFS mount could cause that). Check your > > DNS > > settings and if you usual hosts resolve. > > How do I see that in the time the freeze exists? Chicken/egg problem. > Hosts file based home network, anything powered up pins fine by name. > There is a dhcpd, configed to answer one MAC for a QIDI 3d printer > thats > hard coded. If only the app is affected (not the whole system) then opening a terminal window parallel to the app and running e.g. "htop" in that terminal and sort by process state could achieve that. But if really the whole system freezes, including mouse movements, CTRL-ALT-Fx console switching and the alt-sysrq-... chords I'm out of idea what could cause that. Sorry. You could try PINGing the problematic machine from another machine and look if those pings also stop, in that case some proper exorcism would be needed. SSHing into the box and running htop and/or "sudo journalctl -ef" in the ssh session could also give a hint if something fishy is going on. regards Robert _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users