Thank you for taking the time to report this bug and help make Ubuntu
better. After looking though your bug report, there seems to be multiple
separate issues. When writing a bug report, it is generally better to
keep a particular report focused on one single problem, otherwise they
can become difficult to follow. Because of this, I am going to close
this report, but I will go through some of your points and advise what
to do next.

You may find it helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures

"When mounting a share using nautilus:
- nautilus never really mounts it, instead it creates a "shortcut" to the share 
using smb:// protocol
- many apps have no access to such a pseudo-mounted share making it useless in 
a enterprise environment when working on files hosted on that share (ex: gedit, 
totem, zend studio, wine apps ... )"

The 'smb:///' is basically part of the abstraction provided by GVFS/GIO.
The GNOME applications that you mention (Gedit, Totem, File-roller etc)
are currently being ported to GIO as part of the GNOME 2.24 develpment
cycle (which will be in Intrepid 8.10).

For other applications outside of GNOME, it would be the responsibility
of the application developers to port their applications to GIO (if they
wanted to). You could raise separate bug reports against these
applications. These reports would then be set to 'Wishlist' or 'Wont
Fix' by a bug triager.

You can still access Samba shares using non-GIO applications, using the
gvfs-fuse mount. Any Samba shared mounted via Nautilus will also appear
in ~/.gvfs, so your points above should be a non-issue at the moment.

"- free disk space is not available"

I assume you mean that Nautilus doesn't show the free space on a Samba
mount? If this is the case, then you might be better off opening a bug
report in the upstream bug tracker, as this is something that is
unlikely to be implemented directly by the Ubuntu team
(http://bugzilla.gnome.org/)

"- burning files with brasero is not possible (files exists but have
size of 0kb) Tried burning images pdf and .avi: same result"

I don't understand what you mean here, but this could be a bug. You should 
report this problem in it's own bug report, providing the following information:
1. the specific steps or actions you took that caused you to encounter the 
problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

"When mounting thought fstab
- it is far to complicated for an average user or a network administrator 
(doing such a configuration on all computer in an enterprise wastes time)"

I think you would be better off opening up a discussion about this on
http://brainstorm.ubuntu.com/

"- I had many problem burning files directly from a such mounted share
witch implies to copy the files to local computer to burn them"

This might be a bug or you might just need some support. I think you
would be better off reporting this problem in the support tracker where
somebody else can provide assistance. The support tracker can be found
at https://answers.launchpad.net/ubuntu. Your support request can be
converted to a bug report later on if this is needed.

"- if a share has a symlink, it is shown has a broken symlink (witch is not the 
case using a windows computer or the smb:// protocol)
- when copying a file, the progress is not shown properly."

These sound like they might be bugs, but I can't say for definate without more 
information. You should probably open separate bug reports for the two issues 
containing the following information:
1. the specific steps or actions you took that caused you to encounter the 
problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

Thank you

** Changed in: ubuntu
       Status: New => Invalid

-- 
Bad samba network shares support
https://bugs.launchpad.net/bugs/252699
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to