gvfs issueshttps://gitlab.gnome.org/GNOME/gvfs/-/issues2024-03-12T21:39:41Zhttps://gitlab.gnome.org/GNOME/gvfs/-/issues/721SMB-client: file extension is not seen case sensitive2024-03-12T21:39:41ZA NymusSMB-client: file extension is not seen case sensitiveAs per GNOME/nautilus#3356, the problem seems to be that `gio move /path/to/test.TXT smb://ip/share/` rewrites existing `test.txt` file instead of creating `test.TXT` on the server.As per GNOME/nautilus#3356, the problem seems to be that `gio move /path/to/test.TXT smb://ip/share/` rewrites existing `test.txt` file instead of creating `test.TXT` on the server.https://gitlab.gnome.org/GNOME/gvfs/-/issues/436Network folder caching2024-03-10T15:20:44ZIvan Molodetskikhyalterz@gmail.comNetwork folder caching### Use cases
<!-- Describe what problem(s) the user is experiencing and that this request
is trying to solve. -->
When exploring a remote location (in my case a Samba filesystem) I frequently open a folder, see that what I'm looking for...### Use cases
<!-- Describe what problem(s) the user is experiencing and that this request
is trying to solve. -->
When exploring a remote location (in my case a Samba filesystem) I frequently open a folder, see that what I'm looking for is not there, and go back up to check other folders. Every time I go back the contents are fetched again which takes more than 10 seconds, making the process extremely slow.
### Desired behavior
<!-- Describe the desired functionality. -->
The contents are extremely likely to remain unchanged, so they should be cached and shown instantly. New contents can be requested either manually via F5. Alternatively, they can be requested automatically and replace the cached contents when the request completes (although this could result in an issue of the user clicking right after the new contents are shown and going down a wrong folder if contents did change).
### Benefits of the solution
<!-- List the possible benefits of the solution and how it fits in the project. -->
Exploring network shares over a slow connection ~~stops being a torture~~ becomes twice as fast, and more, depending on the user's folder access pattern.
### Possible drawbacks
<!--
Describe possible drawbacks of the feature and list how it could affect
the project i.e. UI discoverability, complexity, impact in more or less
number of users, etc.
-->
New contents for cached folders are not shown right away. However, if the user expects the contents to change, they can use F5 manually.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/gvfs/-/issues/506Web Service Discovery2024-01-05T07:54:50ZYuri6037Web Service DiscoveryHello,
I would like to request for Web Service Discovery protocol to be implemented in order to allow nautilus to list Windows 10 Machines.Hello,
I would like to request for Web Service Discovery protocol to be implemented in order to allow nautilus to list Windows 10 Machines.https://gitlab.gnome.org/GNOME/gvfs/-/issues/307Impossible to open smb share file2023-12-15T13:24:43ZBugzillaImpossible to open smb share file## Submitted by Laurent
Assigned to **gvf..@..e.bugs**
**[Link to original bug (#785249)](https://bugzilla.gnome.org/show_bug.cgi?id=785249)**
## Description
Created attachment 356152
The error message after open click on server i...## Submitted by Laurent
Assigned to **gvf..@..e.bugs**
**[Link to original bug (#785249)](https://bugzilla.gnome.org/show_bug.cgi?id=785249)**
## Description
Created attachment 356152
The error message after open click on server icon in widows network
In nautilus application
- select "Other palce"
- select windows network
- and click on server
=> if the server use only SMB2 or SMB3 it cannot be mounted.
The error message displayed is "L'obtention de la liste des partages du serveur a échoué : Connexion terminée par expiration du délai d'attente"
This workflow is reproducible with gvfs command:
- use gvfs-mount smb://Mulet.local/
=> result of command is : "Erreur lors du montage de l'emplacement : L'obtention de la liste des partages du serveur a échoué : Connexion terminée par expiration du délai d'attente"
All work if the server use "SMB1" but it is a security fail.
**Attachment 356152**, "The error message after open click on server icon in widows network":
![Capture_d_écran_de_2017-07-21_23-08-32](/uploads/b14cff3679cfc9c73d6321f593ccdbca/Capture_d_écran_de_2017-07-21_23-08-32.png)https://gitlab.gnome.org/GNOME/gvfs/-/issues/703Opening SMB Share Spins on 'Permission denied' Error2023-11-15T09:04:17ZazdleOpening SMB Share Spins on 'Permission denied' ErrorTrying to connect to my share has suddenly started hanging, spinning up my system's fans, until I kill the gvfsd process.
Running `gvfsd` with `GVFS_SMB_DEBUG=10 GVFS_DEBUG=1` it spews out these messages:
```
smb: do_mount - try #15471...Trying to connect to my share has suddenly started hanging, spinning up my system's fans, until I kill the gvfsd process.
Running `gvfsd` with `GVFS_SMB_DEBUG=10 GVFS_DEBUG=1` it spews out these messages:
```
smb: do_mount - try #15471
smbc_stat(smb://homonoia.poop.casa/data)
SMBC_getatr: sending qpathinfo
map_errno_from_nt_status: 32 bit codes: code=c0000022
cli_status_to_errno: 0xc0000022 -> 13
smb: do_mount - [smb://nas.home.arpa/data; 15471] res = -1, cancelled = 0, errno = [13] 'Permission denied'
```
As far as I can tell it's doing it in a tight loop (that "try #15471" was after only a couple of seconds) and never gives up.
I don't know enough to know for sure that this is a bug in gvfs itself, but it happens when I try to open the share via gnome files, Déjà Dup, or `gio mount`. Though, I assume it most likely is because those debug messages continue after quitting/killing/timing-out the application that is trying to connect.https://gitlab.gnome.org/GNOME/gvfs/-/issues/702Files moved in between folders in samba mount causing "Not a directory" error2023-11-14T11:52:20ZDavid CalanoFiles moved in between folders in samba mount causing "Not a directory" error# Affected version
- Nightly flatpak: Yes
- Other: Pop!_OS 22.04, Nautilus 42.6
# Steps to reproduce
1. Open nautilus and mount samba directory
2. Navigate to source directory and move a file to target directory using Nautilus (ie cut/p...# Affected version
- Nightly flatpak: Yes
- Other: Pop!_OS 22.04, Nautilus 42.6
# Steps to reproduce
1. Open nautilus and mount samba directory
2. Navigate to source directory and move a file to target directory using Nautilus (ie cut/paste, drag/drop, "Move to..." context option)
# Current behavior
An error pops up, as seen in the first screenshot, and an empty folder with the same name as the file in question is created in the target directory. In version 42.6 this occurs at the same time as the popup, in the nightly, this is happening after I cancel the popup.
# Expected behavior
File is moved from one folder to another
# Additional information
This only occurs in Nautilus, I can move the file just fine over command line using `mv` and `gio move` as suggested on the element channel.
![Screenshot_from_2023-10-24_19-35-15](/uploads/9611c934b6d9be1c7069a4e855541db7/Screenshot_from_2023-10-24_19-35-15.png)
![Screenshot_from_2023-10-24_19-41-46](/uploads/0f1b3ace6eb9351770056b1cb27e7239/Screenshot_from_2023-10-24_19-41-46.png)
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/gvfs/-/issues/483Add support for interfaces in IPv6 addresses2023-10-14T06:35:16ZMarcusWAdd support for interfaces in IPv6 addressesMy computer has a peer-to-peer connection with my NAS and therefore I tried to access it's SMB share using the NAS's link local address:
```
gio mount smb://fe80::202:c9ff:fe53:366a%enp2s0/Data
```
But this gives me an `Invalid Argument...My computer has a peer-to-peer connection with my NAS and therefore I tried to access it's SMB share using the NAS's link local address:
```
gio mount smb://fe80::202:c9ff:fe53:366a%enp2s0/Data
```
But this gives me an `Invalid Argument` error message. The same happens when mounting through nautilus.
Trying to mount the same share as a native mount works fine:
```
mount -t cifs -o ... //fe80::202:c9ff:fe53:366a%enp2s0/Data /mnt/Data
```
gvfs: `1.44.1`
gio: `2.64.3`https://gitlab.gnome.org/GNOME/gvfs/-/issues/693Problem with accessing smb shared folder, domain typed in the credentials win...2023-10-12T11:53:22ZMiguel RozsasProblem with accessing smb shared folder, domain typed in the credentials window is ignored# Affected version
- nautilus-45.0-1.1
# Steps to reproduce
1. On the Nautilus file manager, other locations, Network section there is nothing there. On the bottom, there is a text field where I typed: "smb://192.168.1.46/miguel", pr...# Affected version
- nautilus-45.0-1.1
# Steps to reproduce
1. On the Nautilus file manager, other locations, Network section there is nothing there. On the bottom, there is a text field where I typed: "smb://192.168.1.46/miguel", press connect and fill the form with the credentials.
2.
# Current behavior
1. I got the error message: "Unable to access location. Failed to mount windows share; Invalid arguments"
# Expected behavior
opening the shared location
# Additional information
On a terminal, as root, if I try:
`mount -t cifs -o credentials=/tmp/cred.txt //192.168.1.46/miguel /mnt/spare`
it succeeded using the same credentials as in file /tmp/cred.txt. So I am not in mistake about my credentials or smb server address and share.
On the same machine but using KDE, on dolphin file manager, network places, shared folders (SMB) the samba server is shown, no fuzz to access this share.
I could verified that in the nautilus credentials window, the text in DOMAIN field is ignored !
This field is pre-filled with the WORKGROUP name in /etc/samba/smb.conf file (which is, in my case, different from the workgroup of the samba share I was trying to access)
If I change the WORKGROUP in /etc/samba/smb.conf to the domain it is expected by the samba share I am trying to access then I got the access to that samba share.
No matter what I type on the credentials window, looks like the one set in /etc/samba/smb.conf takes precedence.
So the field DOMAIN should be READ-only on the credentials window OR the credentials window must honor what the user type in.
Running on :
openSUSE Tumbleweed 20230929
Kernel Version: 6.5.4-1-default (64-bit)
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600https://gitlab.gnome.org/GNOME/gvfs/-/issues/682valgrind tool detected memory leaks in gvfsd-smb-browse.2023-07-26T08:02:17Zwang xiaomengvalgrind tool detected memory leaks in gvfsd-smb-browse.On a Linux operating system (CentOS 9 or OpenEuler), i installed the gvfs and gvfs-debuginfo packages, then executed the command "valgrind --tool=memcheck --leak-check=full --show-reachable=yes --track-origins=yes --log-file=valgrind.log...On a Linux operating system (CentOS 9 or OpenEuler), i installed the gvfs and gvfs-debuginfo packages, then executed the command "valgrind --tool=memcheck --leak-check=full --show-reachable=yes --track-origins=yes --log-file=valgrind.log -v /usr/libexec/gvfsd-smb-browse".
It shows "definitely lost" and there are two processes in log file valrgrind.log, both of which have leaks. The first process has more leaks, and the second process leaks has been located. Please analyze the leak detection results of the first process to determine whether it is a genuine leak and how to solve it.
The log:
[valgrind-centos9.log](/uploads/3d8de4f284970b7cbffd7646e8d37b6a/valgrind-centos9.log)https://gitlab.gnome.org/GNOME/gvfs/-/issues/672Renaming a file by changing case, doesn't work on Networked Drives2023-06-28T14:26:04ZMatthew HudsonRenaming a file by changing case, doesn't work on Networked Drives# Affected version
- Nightly flatpak: Yes <!-- Delete the unwanted answers -->
- Other: 43.0
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Open Networked location
2. Right Click to ...# Affected version
- Nightly flatpak: Yes <!-- Delete the unwanted answers -->
- Other: 43.0
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Open Networked location
2. Right Click to Rename File / or F2
3. Change case of a letter in filename
4. Press Enter or click Rename
5. Filename does not change
# Current behavior
<!-- Describe the current behavior. -->
Filename does not change
# Expected behavior
<!-- Describe the expected behavior. -->
Filename to change to adjusted name
# Additional information
<!--
Provide more information that could be relevant.
If the issue is a crash, provide a stack trace following the steps in:
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces
-->
<!-- Ignore the text under this line. -->Corey BerlaCorey Berlahttps://gitlab.gnome.org/GNOME/gvfs/-/issues/649Unable to write to gvfs mount point2022-11-09T08:40:23ZMichael MonrealUnable to write to gvfs mount pointI "mounted" smb://nas/restore using Nautilus. Using the file manager and GNOME apps I can read and write from and to the share. However I also want to access the mount point using a script. I can read just fine from /run/user/1000/gvfs/s...I "mounted" smb://nas/restore using Nautilus. Using the file manager and GNOME apps I can read and write from and to the share. However I also want to access the mount point using a script. I can read just fine from /run/user/1000/gvfs/smb-share:server=nas, see:
```
[micmon@fedora ~]$ ls -la /run/user/1000/gvfs/smb-share:server=nas,share=restore/
total 0
drwx------. 1 micmon micmon 0 Oct 3 14:21 .
dr-x------. 3 micmon micmon 0 Oct 3 14:15 ..
-rwx------. 1 micmon micmon 0 Oct 2 08:08 Plaintext.txt
drwx------. 1 micmon micmon 0 Oct 2 22:09 .Trash-1000
```
But I cannot write:
```
[micmon@fedora ~]$ touch /run/user/1000/gvfs/smb-share:server=nas,share=restore/test
touch: cannot touch '/run/user/1000/gvfs/smb-share:server=nas,share=restore/test': Permission denied
```
The mount command shows the mount point as being RW:
```
[micmon@fedora ~]$ mount | grep gvfs
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
```
And my user is really UID 1000:
```
[micmon@fedora ~]$ id
uid=1000(micmon) gid=1000(micmon) groups=1000(micmon),10(wheel) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
```
Is there a way to make this work? Unfortunately something breaks mounting SMB shares using fstab without root rights on my system.https://gitlab.gnome.org/GNOME/gvfs/-/issues/651Permission denied calling SMBC_getatr when file not exists2022-11-09T08:38:02ZVíctor Daniel Martínez OlierPermission denied calling SMBC_getatr when file not existsDescription of problem:
Permission denied calling `SMBC_getatr` when file not exists.
Apparently `SMBC_getatr` no longer uses `errno` but instead returns `NTSTATUS`:
https://github.com/samba-team/samba/commit/d4f8fdd69a1278d8473d541dc6...Description of problem:
Permission denied calling `SMBC_getatr` when file not exists.
Apparently `SMBC_getatr` no longer uses `errno` but instead returns `NTSTATUS`:
https://github.com/samba-team/samba/commit/d4f8fdd69a1278d8473d541dc6b32014a369bcd0
Reverting the previous commit fixes the bug:
I rebuilt the samba SRPM using a mock and added the patch to SPEC and everything works perfect:
https://koji.fedoraproject.org/koji/buildinfo?buildID=2062333
```
$ git format-patch -1 --stdout d4f8fdd69a1278d8473d541dc6b32014a369bcd0 > 0001-libsmb-Convert-SMBC_getatr-to-NTSTATUS.patch
0001-libsmb-Convert-SMBC_getatr-to-NTSTATUS.patch
```
https://koji.fedoraproject.org/koji/buildinfo?buildID=2062333
```
...
Patch100: 0001-libsmb-Convert-SMBC_getatr-to-NTSTATUS.patch
...
%prep
xzcat %{SOURCE0} | gpgv2 --quiet --keyring %{SOURCE2} %{SOURCE1} -
%autosetup -n samba-%{version}%{pre_release} -N
%autopatch -M 99
%patch100 -p1 -R
...
```
Version-Release number of selected component (if applicable):
```
$ rpm -qa gvfs-*
gvfs-client-1.50.2-2.fc37.x86_64
gvfs-afc-1.50.2-2.fc37.x86_64
gvfs-fuse-1.50.2-2.fc37.x86_64
gvfs-goa-1.50.2-2.fc37.x86_64
gvfs-afp-1.50.2-2.fc37.x86_64
gvfs-archive-1.50.2-2.fc37.x86_64
gvfs-gphoto2-1.50.2-2.fc37.x86_64
gvfs-mtp-1.50.2-2.fc37.x86_64
gvfs-smb-1.50.2-2.fc37.x86_64
```
```
$ rpm -qa gvfs-smb samba-* libsmbclient*
gvfs-smb-1.50.2-2.fc37.x86_64
samba-common-4.17.0-1.fc37.noarch
samba-client-libs-4.17.0-1.fc37.x86_64
samba-common-libs-4.17.0-1.fc37.x86_64
libsmbclient-4.17.0-1.fc37.x86_64
samba-client-4.17.0-1.fc37.x86_64
```
```
$ rpm -q glib2
glib2-2.73.3-3.fc37.x86_64
```
How reproducible:
Steps to Reproduce:
Working:
```
$ gio mount -u "smb://bar@SERVER/foo/"
$ gio mount "smb://bar@SERVER/foo/"
$ date | gio save /run/user/1000/gvfs/smb-share:server=SERVER\,share=foo\,user=bar/folder/test.txt
$ echo $?
0
$ cat /run/user/1000/gvfs/smb-share:server=SERVER\,share=foo\,user=bar/folder/test.txt
Thu Sep 15 03:49:57 PM -05 2022
```
Not working (Permission denied):
```
$ gio mount -u "smb://bar@SERVER/foo/"
$ gio mount "smb://bar@SERVER/foo/"
$ date | tee /run/user/1000/gvfs/smb-share\:server\=SERVER\,share\=foo\,user\=bar/folder/another-test.txt
tee: '/run/user/1000/gvfs/smb-share:server=192.168.44.1,share=backups,user=bar/folder/another-test.txt': Permission denied
Thu Sep 15 03:55:20 PM -05 2022
$ echo $?
1
$ date | tee /run/user/1000/gvfs/smb-share\:server\=SERVER\,share\=foo\,user\=bar/folder/test.txt (the file exists because it was created above with "gio save")
$ echo $?
0
```
Actual results:
`$ date | gio save /run/user/1000/gvfs/smb-share:server=SERVER\,share=foo\,user=bar/folder/test.txt (OK)`
`$ date | tee /run/user/1000/gvfs/smb-share\:server\=SERVER\,share\=foo\,user\=bar/folder/another-test.txt (Fail: Permission denied)`
Expected results:
`$ date | tee /run/user/1000/gvfs/smb-share\:server\=SERVER\,share\=foo\,user\=bar/folder/another-test.txt (OK)`
Additional info:
Log messages in `GVFS_SMB_DEBUG=10 GVFS_DEBUG=1 /usr/libexec/gvfsd --replace`:
With `gio save`:
```
smb: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=4762)
smb: Queued new job 0x7f0b100068f0 (GVfsJobQueryInfo)
smbc_stat(smb://SERVER/foo/folder)
SMBC_getatr: sending qpathinfo
smb: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=4762)
smb: Queued new job 0x7f0b10006d50 (GVfsJobQueryInfo)
smb: send_reply(0x7f0b100068f0), failed=0 ()
smbc_stat(smb://SERVER/foo/folder)
SMBC_getatr: sending qpathinfo
smb: send_reply(0x7f0b10006d50), failed=0 ()
smb: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=4762)
smb: Queued new job 0x7f0b10006df0 (GVfsJobQueryInfo)
smbc_stat(smb://SERVER/foo)
SMBC_getatr: sending qpathinfo
smb: send_reply(0x7f0b10006df0), failed=0 ()
smb: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=4762)
smb: Queued new job 0x7f0b10006c10 (GVfsJobQueryInfo)
smbc_stat(smb://SERVER/foo/folder)
SMBC_getatr: sending qpathinfo
smb: send_reply(0x7f0b10006c10), failed=0 ()
smb: backend_dbus_handler org.gtk.vfs.Mount:OpenForWriteFlags (pid=5003)
smb: Queued new job 0x7f0b08022190 (GVfsJobOpenForWrite)
map_open_params_to_ntcreate: fname = \folder\test.txt, deny_mode = 0x42, open_func = 0x10
map_open_params_to_ntcreate: file \folder\test.txt, access_mask = 0x12019f, share_mode = 0x3, create_disposition = 0x2, create_options = 0x40 private_flags = 0x0
smb: send_reply(0x7f0b08022190), failed=0 ()
smb: Added new job source 0x7f0b08044570 (GVfsWriteChannel)
smb: Queued new job 0x55aefce02eb0 (GVfsJobWrite)
smb: send_reply(0x55aefce02eb0), bytes=32, failed=0 ()
smb: Queued new job 0x55aefcdf5950 (GVfsJobCloseWrite)
smb: send_reply(0x55aefcdf5950), failed=0 ()
```
With `date | tee`:
```
smb: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=4762)
smb: Queued new job 0x7f0b10006cb0 (GVfsJobQueryInfo)
smbc_stat(smb://SERVER/foo/folder)
smb: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=4762)
smb: Queued new job 0x7f0b10006b70 (GVfsJobQueryInfo)
SMBC_getatr: sending qpathinfo
smb: send_reply(0x7f0b10006cb0), failed=0 ()
smbc_stat(smb://SERVER/foo/folder)
SMBC_getatr: sending qpathinfo
smb: send_reply(0x7f0b10006b70), failed=0 ()
smb: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=4762)
smb: Queued new job 0x7f0b10002400 (GVfsJobQueryInfo)
smbc_stat(smb://SERVER/foo/folder/another-test.txt)
SMBC_getatr: sending qpathinfo
map_errno_from_nt_status: 32 bit codes: code=c0000022
cli_status_to_errno: 0xc0000022 -> 13
smb: send_reply(0x7f0b10002400), failed=1 (Permission denied)
```
Red Hat Bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=2127301https://gitlab.gnome.org/GNOME/gvfs/-/issues/525[gvfs-smb] cp: read error: Invalid argument2022-07-01T07:53:44Zralph isenmann[gvfs-smb] cp: read error: Invalid argumentHello,
we use gvfs to allow our users to mount different network shares from our institute, currently we only mount smb/cifs network shares. We also pass the directories, which are created by gvfs under `/run/user/UID/gvfs/*`, into cont...Hello,
we use gvfs to allow our users to mount different network shares from our institute, currently we only mount smb/cifs network shares. We also pass the directories, which are created by gvfs under `/run/user/UID/gvfs/*`, into containers to enable data and persistent storage there.
In general, the whole setup works and it is possible to navigate and read and write files in the remote directories, but errors occur when copying large files to the system. The first time I noticed the error was with a 100MB file, which I had copied to and from the remote for pre-metering. Currently, I test this behavior with the Ubuntu installation ISO. This error is similar to #473 and #442.
### system environment
```bash
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic
```
```bash
./gvfsd --version
gvfs 1.36.1
```
### copy command
```bash
# copy command in container from samba share
/data # cp common/Network\ Trash\ Folder/blub/ubuntu-20.04.1-live-server-amd64.iso tmpfile
cp: read error: Invalid argument
```
### debug log gvfsd
````bash
#/usr/lib/gvfsd -r -d
...
...
smb: Queued new job 0x55b3af65dd50 (GVfsJobRead)
smb: send_reply(0x55b3af65dd50), bytes=131072, failed=0 ()
smb: Queued new job 0x7fe6980132b0 (GVfsJobRead)
smb: send_reply(0x7fe6980132b0), bytes=0, failed=0 ()
smb: Queued new job 0x55b3af65dde0 (GVfsJobQueryInfoRead)
smb: Queued new job 0x55b3af66a040 (GVfsJobQueryInfoRead)
smb: Queued new job 0x55b3af623ee0 (GVfsJobQueryInfoRead)
smb: Queued new job 0x55b3af624cc0 (GVfsJobCloseRead)
smb: send_reply(0x55b3af624cc0), failed=1 (Software caused connection abort)
````
### debug log gvfsd-fuse
```bash
#/usr/lib/gvfs/gvfsd-fuse -o allow_root -o big_writes -d /run/user/ID/gvfs
...
...
unique: 14814, opcode: READ (15), nodeid: 16, insize: 80, pid: 19281
read[139942382603168] 131072 bytes from 958136320 flags: 0x8000
read[139942382603168] 131072 bytes from 958136320
unique: 14814, success, outsize: 131088
unique: 14815, opcode: READ (15), nodeid: 16, insize: 80, pid: 19281
read[139942382603168] 131072 bytes from 958267392 flags: 0x8000
read[139942382603168] 131072 bytes from 958267392
unique: 14815, success, outsize: 131088
unique: 14816, opcode: GETATTR (3), nodeid: 16, insize: 56, pid: 19281
getattr /smb-share:server=fs1-2-common.rz.hs-offenburg.de,share=common/Network Trash Folder/blub/ubuntu-20.04.1-live-server-amd64.iso
unique: 14816, error: -22 (Invalid argument), outsize: 16
unique: 14817, opcode: GETATTR (3), nodeid: 16, insize: 56, pid: 19281
getattr /smb-share:server=fs1-2-common.rz.hs-offenburg.de,share=common/Network Trash Folder/blub/ubuntu-20.04.1-live-server-amd64.iso
unique: 14817, error: -22 (Invalid argument), outsize: 16
unique: 14818, opcode: GETATTR (3), nodeid: 16, insize: 56, pid: 19281
getattr /smb-share:server=fs1-2-common.rz.hs-offenburg.de,share=common/Network Trash Folder/blub/ubuntu-20.04.1-live-server-amd64.iso
unique: 14818, error: -22 (Invalid argument), outsize: 16
unique: 14819, opcode: RELEASE (18), nodeid: 16, insize: 64, pid: 0
release[139942382603168] flags: 0x8000
unique: 14819, success, outsize: 16
```https://gitlab.gnome.org/GNOME/gvfs/-/issues/619Invalid Argument when mounting smb share2022-05-05T08:27:43ZGamerBene19Invalid Argument when mounting smb shareI do get an "Invalid Argument" error when trying to mount an smb share with gvfs **with** the fix from !138.
The problem was initially fixed and now occurs again.
### (Package) Versions
```bash
[~] <> * yay -Q gvfs gvfs-smb smbclient
g...I do get an "Invalid Argument" error when trying to mount an smb share with gvfs **with** the fix from !138.
The problem was initially fixed and now occurs again.
### (Package) Versions
```bash
[~] <> * yay -Q gvfs gvfs-smb smbclient
gvfs 1.50.0+r5+g747c7f6e-1
gvfs-smb 1.50.0+r5+g747c7f6e-1
smbclient 4.16.0-5
[~] <> * smbclient -V
Version 4.16.0
```
As far as I can tell the most recent version of `gvfs-smb` [includes the fix](https://github.com/archlinux/svntogit-packages/commit/b895c21ab32b2856048199d456b5cc2509b9312b) from !138.
### Steps to reproduce
1. Have an up to date Arch system and a SMB-Share that can be mounted anonymously
2. Install packages for gvfs smb: `sudo pacman -S gvfs gvfs-smb` (`smbclient` is a dependency of `gvfs-smb`)
3. Try to mount share with gvfs (e.g. with `gio`): `gio mount -a smb://host.addr/share`
### Logs
See [gvfsd.log.gio](/uploads/4917c43c68260ccfdf099c22ee61a0cc/gvfsd.log.gio) for the log when trying to mount with `gio` and [gvfsd.log.thunar](/uploads/e5bcc1ee51428d410c49a97dc71b7502/gvfsd.log.thunar) for the try with `thunar`.
I have replaced the domain and IP of my host with `<DOMAIN>` and `<IP>` respectively.
Issue #611 is probably related.GNOME 42https://gitlab.gnome.org/GNOME/gvfs/-/issues/611Invalid Argument with samba 4.16.02022-05-05T08:06:09ZEdward ClarkInvalid Argument with samba 4.16.0
# Affected version
- Other: Fedora 36 ... Information for build nautilus-42.0-1.fc36
ID 1936262
Package Name nautilus
Version 42.0
Release 1.fc36
# Steps to reproduce
1. Open Files
2. Click Other Locations
3. Select Network Drive
4. C...
# Affected version
- Other: Fedora 36 ... Information for build nautilus-42.0-1.fc36
ID 1936262
Package Name nautilus
Version 42.0
Release 1.fc36
# Steps to reproduce
1. Open Files
2. Click Other Locations
3. Select Network Drive
4. Click on shared folder
# Current behavior
Responds with Unable to access location. Failed to mount Windows share: Invalid argument
![Screenshot_from_2022-03-23_14-51-03](/uploads/ce920ec20b0379cbedc5a5062477afa6/Screenshot_from_2022-03-23_14-51-03.png)
# Expected behavior
Open shared folder
# Additional information
Worked without issue on 42.rc
<!-- Ignore the text under this line. -->GNOME 42https://gitlab.gnome.org/GNOME/gvfs/-/issues/399Files on smb share reported as not writable2021-09-19T10:59:49ZAndre MirandaFiles on smb share reported as not writableThis is a follow-up of glib#1689, that issue was fixed but now Thunar checks for `G_FILE_ATTRIBUTE_FILESYSTEM_READONLY` and `G_FILE_ATTRIBUTE_ACCESS_CAN_WRITE`, the latter yields `FALSE` for destination folders on a SMB share.
Please us...This is a follow-up of glib#1689, that issue was fixed but now Thunar checks for `G_FILE_ATTRIBUTE_FILESYSTEM_READONLY` and `G_FILE_ATTRIBUTE_ACCESS_CAN_WRITE`, the latter yields `FALSE` for destination folders on a SMB share.
Please use the following sample app to reproduce: https://gist.github.com/andreldm/007a07c2fd361e938cac42e1d5c04bd9
The result is:
```
$ ~/fs_sample $(pwd)
/run/user/1000/gvfs/smb-share:server=192.168.1.112,share=share/foo is a directory
is /run/user/1000/gvfs/smb-share:server=192.168.1.112,share=share/foo on read only filesystem? FALSE
can /run/user/1000/gvfs/smb-share:server=192.168.1.112,share=share/foo be written? FALSE
```
However that folder (foo) is writable, I can create files and move files to it using cp/mv
Downstream bug: [Xfce 15367](https://bugzilla.xfce.org/show_bug.cgi?id=15367)https://gitlab.gnome.org/GNOME/gvfs/-/issues/567Can't browse shared successfully scanned folder2021-06-02T20:14:37ZDaniel KorostilCan't browse shared successfully scanned folder```
gio --version
2.68.2
```
```
samba --version
Version 4.14.4
```
```
gio list smb://mydomain.local/public/
autotests
Projects
Users
```
```
gio list smb://mydomain.local/public/Users
gio: smb://mydomain.local/public/Users: No such fil...```
gio --version
2.68.2
```
```
samba --version
Version 4.14.4
```
```
gio list smb://mydomain.local/public/
autotests
Projects
Users
```
```
gio list smb://mydomain.local/public/Users
gio: smb://mydomain.local/public/Users: No such file or directory
```
Why does it happen? If you need more info, please let me know.https://gitlab.gnome.org/GNOME/gvfs/-/issues/554gvfs invalid arguments error SMB2 SMB32021-03-29T22:09:06ZdotMItsugvfs invalid arguments error SMB2 SMB3Our Windows Server was updated yesterday. Windows share doesn't support SMB1 now. If I try to mount share with nautilus or gvfs (nautilus uses gvfs) I get an error invalid arguments.
smbclient in cli works good with force SMB2/3.
gio lis...Our Windows Server was updated yesterday. Windows share doesn't support SMB1 now. If I try to mount share with nautilus or gvfs (nautilus uses gvfs) I get an error invalid arguments.
smbclient in cli works good with force SMB2/3.
gio list shows directories
gio mount write error
![Снимок_экрана_от_2021-03-23_13-16-54](/uploads/ddfd7b09708f434a73bffa5dcbdec7d1/Снимок_экрана_от_2021-03-23_13-16-54.png)
![Снимок_экрана_от_2021-03-23_13-17-23](/uploads/dd71ddc2451f099d1d6f6f3e772af3c6/Снимок_экрана_от_2021-03-23_13-17-23.png)
Distro: Fedora 32https://gitlab.gnome.org/GNOME/gvfs/-/issues/529GFileInfo: g_file_query_info() attribute string broken, remote filesystems.2020-12-08T06:29:41ZMatt VotavaGFileInfo: g_file_query_info() attribute string broken, remote filesystems.I was having issues with finding the content-type of a file on smb:// with an application, so I wrote a test to investigate.
It seems like the attribute string in g_file_query_info() has incorrect behavior.
I think wildcard must only b...I was having issues with finding the content-type of a file on smb:// with an application, so I wrote a test to investigate.
It seems like the attribute string in g_file_query_info() has incorrect behavior.
I think wildcard must only be supported at the end of the string, so the one I can't really explain is `"standard::fast-content-type"` not working in combination with smb:// or other network FSes.
Weird also, is the `application/x-zerosize` when the file is local; the file is not zero-sized.
| g_file_query_info() attributes| file:// | smb:// |
| ----------------------------- | ------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| "*" | standard::content-type: application/x-zerosize<br>standard::fast-content-type: application/octet-stream | standard::content-type: (null)<br>standard::fast-content-type: application/octet-stream |
| "standard::content-type" | standard::content-type: application/x-zerosize<br>standard::fast-content-type: (null) | standard::content-type: (null)<br>standard::fast-content-type: (null) |
| "standard::fast-content-type" | standard::content-type: (null)<br>standard::fast-content-type: application/octet-stream | standard::content-type: (null)<br>standard::fast-content-type: (null) |
| "standard::*content-type" | standard::content-type: (null)<br>standard::fast-content-type: (null) | standard::content-type: (null)<br>standard::fast-content-type: (null) |
| "standard::*" | standard::content-type: application/x-zerosize<br>standard::fast-content-type: application/octet-stream | standard::content-type: (null)<br>standard::fast-content-type: application/octet-stream |https://gitlab.gnome.org/GNOME/gvfs/-/issues/460gvfs-smb is broken with 1.44.1 release2020-06-23T10:46:07ZShaleen jaingvfs-smb is broken with 1.44.1 releaseHi,
With gnome shell 3.36 and after upgrading gvfs-smb to 1.44.1 release, I'm unable to mount a samba directory.
This is the error I get while trying to do so via nautilus:
```
nautilus[421066]: Called "net usershare info" but it fail...Hi,
With gnome shell 3.36 and after upgrading gvfs-smb to 1.44.1 release, I'm unable to mount a samba directory.
This is the error I get while trying to do so via nautilus:
```
nautilus[421066]: Called "net usershare info" but it failed: 'net usershare' returned error 1: Can't load /etc/samba/smb.conf - run testparm to debug it
```
OS: Arch Linux