Bug 41284 - smb ioslave network browsing
Summary: smb ioslave network browsing
Status: RESOLVED FIXED
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: smb (show other bugs)
Version: 3.0.1
Platform: Mandrake RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Alexander Neundorf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-19 08:48 UTC by Scott Newton
Modified: 2003-07-31 10:06 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Newton 2002-04-19 08:44:10 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           konqueror
Version:           3.0.1 (using KDE 3.0.0 )
Severity:          normal
Installed from:    Mandrake RPMs
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: Not Specified

If you browse the netowk using for example:
smb://hostname
you can see the host fine. If you choose a directory under that hostname you can see that fine i.e.
smb://hostname/dir
Any attempt to get to a directory below that directory results in knoqueror just sitting there with the wheel turning.
If you do a ps -e -o args you never see more than
/usr/bin/smbclient //hostname/dir
rather than
/usr/bin/smbclient //hostname/dir/nextdir
If you run smbclient from the command line it can see the directory nextdir without any problems.
This problem has been see on three machines (the total number I have tried). They all are running Mandrake 8.2. The machines for the host to browse include W2k XP Solaris 2.6 (running samba 2.2.0) and Linux machines (running mostly samba 1.9.x). I have seen the same problem under KDE 2.2.2 and Redhat 7.2.
Once in a blue moon it will see the nextdir entries. Interesting though is if you stop the browse and then add a slash to the end of the URL in the URL bar the drop down box appears with the files and directories in that nextdir directory. If you hit enter on the URL with the slash added it fails to find the entries.
Konqueror does not crash so no backtrace is attached.
The expected behaviour would be that you could drill down any number of directories you liked using the smb ioslave.



(Submitted via bugs.kde.org)
Comment 1 Ivo S 2002-11-23 16:16:04 UTC
The same problem here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=75765
Comment 2 Scott Newton 2002-11-24 02:28:14 UTC
The problem still exists for KDE 3.0.4 on Mandrake 9.0. The Mandrake 9.0 is a new clean install, not an upgrade from 8.2.    
Comment 3 mark 2003-01-18 17:33:26 UTC
Appears fixed for me with KDE 3.1RC5 with Debian/woody packages. 
 
I connected to Windows share and quickly browsed down two directories. 
Comment 4 Scott Newton 2003-01-18 21:01:17 UTC
Subject: Re:  smb ioslave network browsing

On Sun, 19 Jan 2003 05:33, you wrote:
> ------- Additional Comments From mark@summersault.com  2003-01-18 17:33
> ------- Appears fixed for me with KDE 3.1RC5 with Debian/woody packages.
>
> I connected to Windows share and quickly browsed down two directories.

Hello Mark

I am currently using KDE 3.1 RC5 at home and KDE 3.1 RC6 at work, both on  
Mandrake 9.0. On both of these it doesn't work.

e.g. 
smb://beta - works
smb://beta/apps - works
smb://beta/apps/drivers - fails - just sits there with the konqueror wheel 
spinning. 

Any ideas?

Thanks
Scott

Comment 5 Ivo S 2003-03-06 12:56:42 UTC
Still no changes with KDE 3.1-7 on RedHat Public Beta Phoebe 8.0.94. 
 
Is there anything I can help with to get this issue fixed? 
Comment 6 jost 2003-03-07 18:08:16 UTC
same problems here

interestingly on new installs of RedHat 8 with or without upgraded samba 2.2.7
or kde 3.0.4 this problem exists. However, on machines that were upgraded from
RedHat 7.3 everything works fine. 

I have already spent days trying to figure out what the difference is between
the installs - but have had no luck so far. 

Thanks,
 - Jost
Comment 7 Alexander Neundorf 2003-03-17 18:41:39 UTC
with the help of jost diederich's I was able to fix this bug, if it still doesn't work for 
you, please notify me. 
 
Alex 
 
Comment 8 Ivo S 2003-03-17 21:11:31 UTC
What was the cause of this problem?
Comment 9 Andrea Aime 2003-04-04 14:36:43 UTC
Just for your information: it still doesn't work in
Mandrake 9.1. This is ridicolus. Is the fix you are speaking about
in KDE 3.1.1? 
Comment 10 bryan hunt 2003-04-04 14:53:03 UTC
Mandrake 9.1 is kde 3.1.0 not kde 3.1.1, also I don't think patches in the last  
8 days would have made it into kde 3.1.1 
 
I can confirm that this bug still exists in mandrake 9.1  
Comment 11 Fr 2003-07-31 10:06:55 UTC
I am using Mandrake 9.1 and it never worked for me, using KDE 3.1 and 3.1.1 
packages from Mandrake. Texstar's KDE 3.1.2 and 3.1.3 packages do not resolve 
the problem.  
 
There is no comment on which KDE version this bug is RESOLVED FIXED... It 
should be KDE 3.1.2 according to Alexander Neundorf on 
http://www.neundorf.net/. 
 
I use LinNeighBoorHood as a workaround, however the problem is still here. As 
this bug has the RESOLVED status, any feedback is appreciated.