Description of problem: Anytime the network service is stopped, the network cable is unplugged, any connection loss to the outside at all causes the desktop to bog down real bad. It looks/behaves like it is frozen but really if you allow the operation like opening Dolphin several minutes it does eventually open. As soon as the network link is re-established everything becomes snappy again. FYI: This happens whether you use the network manager service or not. Version-Release number of selected component (if applicable): Unknown How reproducible: Always Steps to Reproduce: 1. Disable Network Manager in Services GUI 2. Configure a static IP for eth0 using "Network Configuration" GUI 3. Observe connection works and desktop responds well 4. Open terminal window and place on desktop #6 5. Go to terminal and su to root and exec /etc/init.d/network stop 6. Observe the link go down 7. Attempt to switch to another desktop, open dolphin, etc. 8. At this time you will see the desktop appear to freeze but give it a while and it will eventually do what you ask. 9. Go back to terminal exec /etc/init.d/network start 10. Observe the link come up 11. Now any desktop operation like opening Dolphin is immediately responsive Actual results: Desktop actions have a severe latency when network link is down. It appears to actually freeze but waiting minutes you will see the desktop eventually respond. Expected results: Desktop actions execute at same speed whether network link is up or down. Additional info: Apologies for choosing kdebase4 component, I couldn't find a kdeplasma entry. Fresh install of F10 from DVD with all update from repo. Contact me if you would like me to capture any debug info. This is a development machine so if we have to install specialized stuff to capture the info you need that's not a problem. Thanks for the assistance. Cheers!
It dawned on me but I do have four CIFS shares mounted from fstab. I just tested to see if taking them down first using /etc/init.d/netfs stop has an effect and it does. If those shares are unmounted first then the desktop doesn't lag. Prior to F10 I did not have to unmount my cifs shares so to me this is new. I jumped from F8 to F10 so I do not know if this would exist in F9. Please adjust the priority and component since running "netfs stop" can be a suitable workaround until the culprit is found.
yeah, not a good idea to keep stalled/stale shares open... ever (imo). I believe there are several upstream bugs open for similar issues, I'll go digging.
>>not a good idea I find it odd that previous versions (e.g., F8) didn't suffer the same effect. >>there are several upstream bugs open for similar issues, I'll go digging If you find them will you please post a link to them here so I can investigate. Thanks a bunch
I guess I found only one: https://bugs.kde.org/show_bug.cgi?id=184062
There is this local one reported in the upstream issue you mentioned. Guess I will mark this issue as closed-upstream too. Thanks for the digging I appreciate it. https://bugzilla.redhat.com/show_bug.cgi?id=529373