Version: (using KDE KDE 3.3.0) Installed from: Debian testing/unstable Packages OS: Linux I have used the 'lisa' browsing option in konqueror in fedora 3.I had no problems what so ever with configuring lisa browsing to my requirements and the performance was flawless.. it does not work out that well in debian(unstable) here is what i did to get lisa running.. 1. su + /etc/init.d/lisa start -- the start was successful 2. kcontrol --> configue lisa browsing 3.(only in fedora) I went to menu-->system settings -->server settings --> services and made sure that lisa port was open (it already was as i had started it).. I was not able to do this debian as gaurdog does not list lisa port in its list of services. 4.open konqueror and click on the '+' near the lisa option following was the response: Fedora: all the ips with smb/fish/ftp/http shares were listed ... no problems. Debian: konqueror went into a spin!..i had to force kill it. Sometimes, it said 'lisa not started..try starting the lisa deamon'. It is unpredictable at best. I have checked the lisa.conf files in both cases and they are the same. I am sure that there are no problems on the network setup side.(smb:/ in the address bar still shows the local workgroups, and smb://xx.xx.xx.. shows the shares. However lan:/ has the same effect of sending konq into a dizzy. and here is an observation.. from some random experiments: 1. when i say lan://xx where xx is a valid ip address of a comp which had lisa running, (in this case xx was a pc with fedora 3 and lisa interface with kde was working with konq..perfectly well.. I am not sure if this is a relevant point) all the ips with shares were shown as folders with the address bar reading "lan://xx//" clicks on the folders now shown worked perfectly well and the address bar read "lan://xx//visitng ip/" in each case. This stopped happening as soon as the lisa deamon was stopped in the xx comp. My guess it was using the lisa running on the other ps.. i am not sure as this is the only test that i have wrt to this aspect.
B.Aswin: Can you reproduce this bug with recent KDE version? This testcase is quite involved & unlikely to get someone else to be able to successfully reproduce with exact set up - it's already been 2 years! Thanks for the help.
Feedback timeout. This bug will be reopened if additional information is provided.