On Thu, 2018-11-15 at 20:05 +0800, Ed Greshko wrote: > On 11/15/18 6:52 PM, Patrick O'Callaghan wrote: > > On Wed, 2018-11-14 at 15:58 +0000, Patrick O'Callaghan wrote: > > > On Wed, 2018-11-14 at 20:27 +0800, Ed Greshko wrote: > > > > Oh, and I guess, one other thing. > > > > > > > > How about creating a new user and leave that vanilla user logged in over night? > > > Yes, that's about all I can think of for now. > > I did that and it froze within about 20 minutes of logging in. This was > > in a parallel session while I continued working in my main session. > > That test session has nothing else running and is still frozen after > > about 18 hours. > > > > Meanwhile my normal session was frozen for a few minutes when I came > > back this morning but has since woken up spontaneously. > > > > All this is with the NFS NAS automounted but not being used. > > > I think I would use that term "not being used" lightly. > > I only use NFSv4 and I am currently not reading or writing to the NAS. However, in > looking at network traffic with wireshark I see my system sending periodic TCP Keep-Alive > packets as well as NFS Renew CID packets. I would guess NFSv3 do do similar. The NAS spins down when not being used, though I guess it could still respond to this kind of thing. > That said, I don't see how those interactions would cause Plasma Freeze. Indeed not. Unless Plasma is for some reason checking all filesystems, but I don't think it's that stupid. I'm running strace on the plasmashell process to see if anything jumps out when it freezes/unfreezes. poc _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx
