Bug 50914
Summary: | Problems using Konqueror to copy files from SMB server. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | matthew <matthew> |
Component: | kdebase | Assignee: | Than Ngo <than> |
Status: | CLOSED UPSTREAM | QA Contact: | Aaron Brown <abrown> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-06-19 13:32:00 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
matthew
2001-08-04 18:53:53 UTC
Does the same thing happen if you mount the filesystem using the mount command and then access it in konqueror by going to the mount point? *** Bug 50915 has been marked as a duplicate of this bug. *** As requested, I mount the smb server with an smbmount command. I have seen no problems when doing this. Also, after further testing what I'm seeing is that in many situations the smbclient process that is serving the smb ioslave stays around after I am done browsing the smb share, or done copying files. When it sticks around it starts to use 100& CPU. Also, at one point the copy operation was reporting that it was "stalled" I hit cancel, and cpu usage went to 100% from the smbclient. This bug has been inappropriately marked MODIFIED. Please review the bug life cycle information at http://bugzilla.redhat.com/bugzilla/bug_status.cgi Changing bug status to ASSIGNED. I still have problems using konqueror to browse smb shares. No matther what version of Redhat I have tried, be it the roswell beta, RH7.3 or RH8.0, smb browsing does not work well at all with konqueror. Is it just me? please try kde-3.1.1a or newer, which you find it on ftp.kde.org. It should fix this problem |