Bug 189693 - Make dolphin/konqueror discover smb shares via zeroconf/avahi
Summary: Make dolphin/konqueror discover smb shares via zeroconf/avahi
Status: CONFIRMED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: usability
: 194835 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-04-15 09:25 UTC by Jan Essert
Modified: 2020-10-11 10:03 UTC (History)
7 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 Jan Essert 2009-04-15 09:25:28 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Gentoo Packages

I really like the zeroconf/avahi integration into dolphin. Browsing SSH/SFTP shares is very easy and easy to discover for new users. What I really like is that shares are shown instantaneously.

Unfortunately, browsing SMB shares is rather slow, since it takes quite a time until shares are discovered, which I believe to be a limitation of the method, not of the KDE implementation.

Now, using avahi, it is quite simple to announce SMB shares to the local network, and it would be wonderful if dolphin could display those along with the SFTP shares. I hope that discovery of these is then as fast as all zeroconf discovery, which would lead to a much more pleasant experience.

Of course, since Windows machines usually do not announce SMB shares via zeroconf, we would have SMB shares at two points in the folder structure, but I do not think this is a problem.

I hope I have made clear what I mean, if not, ask me again :)
Thanks in advance!
Comment 1 Robin Perkins 2009-05-25 13:54:30 UTC
See also: 
https://bugzilla.samba.org/show_bug.cgi?id=5511
Comment 2 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:19:45 UTC
Resetting assignee to default as per bug #305719
Comment 3 Nate Graham 2017-10-24 19:49:44 UTC
*** Bug 194835 has been marked as a duplicate of this bug. ***