Whoa - stop!

Comment 9 does not describe Bug 354243 directly, but rather, a related
situation.  That's what all those words I typed into Comment 9 mean. I
had hoped the the additional information would be helpful.  I'm sorry it
wasn't.

I opened Bug 354243 specifically because of the "confusion" evident in
Bug 209520.  But the gist of both bugs is this:  There is something
wrong with Nautilus and/or its dependencies - recent versions of
Nautilus are not robust in browsing network shares.

I intended, in Bug 354243, to offer a reproducible demonstration of this
failure.  Comments 1 and 4 outline that demonstration, but again:

The network in Bug 354243 is a vanilla router; a vanilla computer; an
Iomega MDHD500-N network hard drive, running firmware K1.08 L1.0 W1.5;
and an Ubuntu 9.04 beta desktop i386 CD, running in LIVE SESSION.

(Sorry to shout, but last is important:  live session eliminates user
error in configuration, and, more important, live session is supposed to
demonstrate Ubuntu's capabilities with a wide variety of hardware.)

And I will anticipate the objection that this is an Iomega problem:
Windows finds the Iomega NAS; smbclient finds it; smb4k even mounts it -
it's not trying to hide itself.  The Iomega NAS is just one among many
"black-box" embedded SAMBA servers that a robust, desktop-ready file
manager needs to be able to browse.  Current Nautilus fails.

-- 
Nautilus fails to browse any share on network to which Iomega Home Network Hard 
Drive (MDHD500-N, firmware K108.W15) is attached.
https://bugs.launchpad.net/bugs/354243
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Reply via email to