Bug 529373
| Summary: | Stopping network link causes excessive desktop latency | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kevin <kevin.wilson> |
| Component: | kdebase-workspace | Assignee: | Than Ngo <than> |
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 10 | CC: | fedora, fedora, jreznik, kevin, lorenzo, ltinkl, rdieter, smparrish, than |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-10-19 12:22:19 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Kevin
2009-10-16 12:41:35 UTC
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 |