The bug is that because gvfs reports 0 bytes used and 0 bytes free, some
applications either warn about no space available when saving files to
the share, and other applications just refuse to save files to the
share. I don't know how I can say it any more clearer as that is
essentially what I init
Oh that's a mistake. I thought CIFS and Samba was the same thing, but
the bug still remains.
--
Can't save files to Samba (cifs) shares because they report 0 bytes free
https://bugs.launchpad.net/bugs/373477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Yes it's reproducible (and in my case it's never unreproducible).
Install Ubuntu 9.04.
Via the Places menu, choose "Connect to server" and connect to a Samba server.
After connection, an icon appears on the desktop. Right-click it and show the
properties.
Then you see "0 bytes used" and "0 bytes
** Attachment added: "screenshot.gif"
http://launchpadlibrarian.net/26449701/screenshot.gif
--
Can't save files to Samba (cifs) shares because they report 0 bytes free
https://bugs.launchpad.net/bugs/373477
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Public bug reported:
Binary package hint: gvfs
I have several shares on a Samba file server that I use from Windows and
Ubuntu clients. The Windows clients all report the available free space
correctly. The Ubuntu clients (versions 8.10 and 9.04) always report 0
bytes used and 0 bytes free when I
The latest 'fix' doesn't fix the bug for me. This is my situation for if
you want to try to reproduce it:
1. Make a Samba share on another server. Mine are unpublished i.e. you don't
see them when browsing the network, but you can "cd" and log into them after
which they become visible in Nautilu
Elaboration about point 2 above: I use Gnome Commander to open a source
code file by navigating via the ~/.gvfs directory
--
gvfs fuse mount is not functional after logout and subsequent login
https://bugs.launchpad.net/bugs/212789
You received this bug notification because you are a member of Ub
I have a Shuttle SN26P with the same sound chip and the same problem.
There are probably a lot more Shuttles with this same sound chip. I hope
it gets fixed one year since the patch seems to be hanging around for a
long time already and I don't want to start patching and compiling
kernels in a supp
Oh yes and I was using Ubuntu 8.04 with the 2.6.24-18-generic kernel.
--
Unsupported sound chip: VIA VT1720/24 (VIA Envy24PT)
https://bugs.launchpad.net/bugs/16041
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing li