summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* build: Use GNOME module post_install()Matt Turner2023-05-032-17/+4
|
* Post branch version bumpOndrej Holy2023-05-021-1/+1
|
* mtp: Emit delete event on device when disconnected António Fernandes2023-04-291-0/+5
| | | | | Otherwise clients won't realize the root file is gone. Related to https://gitlab.gnome.org/GNOME/nautilus/-/issues/371
* Update Turkish translationSabri Ünal2023-04-231-8/+8
|
* Revert "smb: Allow renaming a file to the same name with a different case"Corey Berla2023-04-111-8/+1
| | | | This reverts commit f99b812d16d29f9fa6dd090f4ccb6058c004e012.
* smb: Allow renaming a file to the same name with a different caseCorey Berla2023-04-111-1/+8
| | | | | | | | | | | | | We check to see if the desired file name already exists before doing a renaming by stat'ing the file (to prevent smb from destroying an existing file). Since smb is not case sensitive, the check for an existing file mistakenly returns true if we are only changing the filename's case. Add a second check to see whether we are simply changing the case of the filename. Fixes: https://gitlab.gnome.org/GNOME/gvfs/-/issues/672
* Update Abkhazian translationNart Tlisha2023-04-051-49/+4181
|
* Update Bulgarian translationAlexander Shopov2023-03-311-1/+1
|
* trash: Sync trash dir items when files changerong wang2023-03-311-2/+19
| | | | | | | | | | | | In the case of an application monitoring the trash can, delete a file on the mounted device to the trash can, and then unmount the device. At this time, if you check the status of the trash can, you will find that the number of files queried is inconsistent with the number of files obtained through the enumeration job. This is because the number of files queried includes some files that do not exist when the device is unmounted. The solution is to synchronize the status of the trash can in time to ensure that the trash can does not record files that do not exist.
* Post release version bumpOndrej Holy2023-03-171-1/+1
|
* Release version 1.50.41.50.4Ondrej Holy2023-03-171-0/+8
|
* Update Turkish translationSabri Ünal2023-03-101-35/+36
|
* gdaemonfile: Remove dead codeOndrej Holy2023-02-281-9/+0
| | | | | | | The file_transfer function contains a statement ensuring that the operation fails when files are on different mounts. But this statement is never reached. This case is correctly handled inside the create_proxy_for_file2 functio. Let's remove the dead code.
* dav: Prevent g_object_unref call with NULL pointerOndrej Holy2023-02-281-1/+1
| | | | | | | | When the push method in DAV baclend is called with a nonexistent source file, the `GLib-GObject-CRITICAL **: 12:07:04.743: g_object_unref: assertion 'G_IS_OBJECT (object)' failed` message is printed because the `g_object_unref` function is called for a `NULL` pointer. Let's use `g_clear_object` instead to avoid this.
* gdaemonfile: Disable push/pull for FlatpakOndrej Holy2023-02-281-2/+4
| | | | | | | | | The push/pull methods rely on local paths. This is a problem for Flatpak applications because the GVfs daemons run outside of it, so the same local path might refer to a different file. Let's disable the push/pull methods for Flatpak applications to fix errors when moving/copying. Related: https://github.com/flathub/org.libreoffice.LibreOffice/issues/23
* Update Turkish translationSabri Ünal2023-02-221-64/+63
|
* http: Fill `GFileInfo` with uncompressed sizesLucas Chollet2023-02-081-0/+23
| | | | | | | | | | | | | Currently, using `FileProgressCallback` is quite confusing as `current_num_bytes` is in uncompressed bytes unlike `total_num_bytes` which is in compressed bytes. In order to solve this issue, we disable compression in `query_info` by setting the "Accept-Encoding" flag to `identity` (none). Then whenever `query_info_on_read` is called, we make sure that the request wasn't set to accept compresssion and fallback to `query_info` if it is the case. Fixes #195
* Fix string comparisonSergio Costas Rodriguez2023-02-063-3/+3
| | | | | | | | In several places, the code compares to strings by comparing their pointers instead of using g_strcmp0(). Although this seems to work, it is incorrect. This MR fixes it.
* Update Belarusian translationVasil Pupkin2023-01-231-510/+665
|
* Post release version bumpOndrej Holy2023-01-061-1/+1
|
* Release version 1.50.31.50.3Ondrej Holy2023-01-061-0/+11
|
* dav: Prevent usage of NULL when user is not specifiedOndrej Holy2023-01-061-2/+4
| | | | | | | | | | | When the username is not part of an URI, then the following message is printed: `GVFS-CRITICAL **: 12:31:47.663: g_mount_spec_set_with_len_internal: assertion 'value != NULL' failed`. This is because `g_mount_spec_set` is called with `NULL`. It possibly lead to crash when it is build with the `G_DISABLE_CHECKS` option. This bug was introduced recently by the commit 6636d89f. Let's check the value before setting it to fix this. Related: https://gitlab.gnome.org/GNOME/gvfs/-/issues/644
* Update Abkhazian translationNart Tlisha2023-01-051-4/+4
|
* ftp: Update ftp->connections when the connection is releasedwangrong2023-01-051-0/+1
| | | | | | | | | | After gvfsd-ftp is connected to the ftp server, if the ftp server stops, the gvfsd-ftp sending request will be stuck, even after the ftp server is started, it still cannot be recovered. This is because ftp->connections is not updated when the connection is released，Thus let ftp->connections decrement by one when the connection is released. https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/149
* fuse: Decrease file handle reference when open file failwangrong2023-01-051-0/+3
| | | | | | | | When the file fails to open, vfs_release() will not be called, which makes the file handle unable to be released, which will cause subsequent creation of the same name file to fail. Related: https://gitlab.gnome.org/GNOME/gvfs/-/issues/660
* daemon: PATH-expand the sftp backend ssh clientAlex Stewart2022-12-142-5/+1
| | | | | | | | | | | | | | | | | Meson is currently configured to search the gvfs builder's PATH for an ssh client, and hardcode its fullpath as the canonical ssh client for the gvfs sftp backend. This setup breaks in cases where the builder has a different ssh client from the final runtime root, or where the client's pathes differ. Builders using OpenEmbedded or buildroot workspaces are particularly affected. Instead, set SSH_PROGRAM to `ssh` so that it gets PATH-expanded at runtime. Closes: https://gitlab.gnome.org/GNOME/gvfs/-/issues/465 Signed-off-by: Alex Stewart <alex.stewart@ni.com>
* test: Resolve trash flakyness by waiting before listing the contentSebastien Bacher2022-12-141-0/+1
| | | | | The action is done asynchronous by the service and without the delay the trash is sometime showing empty when it shouldn't.
* test: Remove deprecated --no-debug udisks argument from the scriptSebastien Bacher2022-12-141-1/+1
| | | | | The option has been deprecated in udisks for years and is just displaying a warning in the log
* backend: Add support for xx-large and x-large thumbnailsOndrej Holy2022-12-131-19/+18
| | | | | | | | | GVfs doesn't support x-large and xx-large thumbnails currently. Consequently, thumbnails are not shown for remote locations in Nautilus on HiDPI screens. GLib added support for them over glib!2941 recently. Let's do the similar change for GVfs. Relates: glib#2767
* Add Interlingue translationOlga Smirnova2022-12-092-0/+3421
| | | | (cherry picked from commit da9b31e0310bd917773f30cdbf3626c5b9c04ea1)
* Update Abkhazian translationNart Tlisha2022-12-021-5/+5
|
* Refer to Discourse instead of mailing listOndrej Holy2022-11-092-4/+2
| | | | | GNOME mailing lists and IRC are retired. Let's refer people to GNOME Discourse instead.
* Update Abkhazian translationNart Tlisha2022-10-311-3906/+5
|
* Update Chinese (Taiwan) translationFreddy Cheng2022-10-181-176/+180
|
* Update Abkhazian translationNart Tlisha2022-10-031-12/+3914
|
* Update Turkish translationSabri Ünal2022-09-181-1190/+166
|
* Update Finnish translationJiri Grönroos2022-09-151-189/+171
|
* Fix error in Lithuanian translationAurimas Černius2022-08-221-173/+174
|
* Update Abkhazian translationNart Tlisha2022-07-291-75/+12
|
* Add Abkhazian translationNart Tlisha2022-07-262-0/+2276
|
* ci: Enable all the backends for which we have installed-testsBastien Nocera2022-07-191-0/+6
|
* ci: Indent meson optionsBastien Nocera2022-07-191-1/+6
| | | | To make it easier to add new ones without changing a whole line.
* Update Serbian translationМарко Костић2022-07-151-199/+169
|
* goa: Prevent automounts when resuming from suspensionOndrej Holy2022-07-011-2/+0
| | | | | | | | | | | | When on WiFi, the NextCloud account is automatically mounted after resuming from suspension. This is because the `Account.AttentionNeeded` property changes its value and GOA volume monitor calls mount operation in that case. It is not obvious to me why this code is here. Also this is maybe bug on GOA side. But anyway, other backends simply just unmount when something changes, but don't mount again automatically. I suppose we should do the same here as well to avoid these unwanted automounts. Fixes: https://gitlab.gnome.org/GNOME/gvfs/-/issues/634
* Update Basque translationAsier Sarasua Garmendia2022-06-261-50/+49
|
* Add Georgian translationZurab Kargareteli2022-06-052-0/+2223
|
* Post release version bumpOndrej Holy2022-05-261-1/+1
|
* Release version 1.50.21.50.2Ondrej Holy2022-05-261-0/+6
|
* smb: Remove redundant variableOndrej Holy2022-05-051-10/+1
| | | | | The `mount_try_again` variable is redundant since it is set to `TRUE` in all cases. Let's remove it to sligtly improve readability of the code.
* smb: Rework anonymous handling to avoid EINVALOndrej Holy2022-05-051-15/+4
| | | | | | | | | | | After the recent samba change, the "Invalid Argument" error can be still returned when anonymous login is requested even after the commit 747c7f6. This is because `smbc_setOptionNoAutoAnonymousLogin` is called after returning from the `auth_callback` function (i.e. there is one redundant iteration). Let's rework the handling a bit and call that immediately, which bypasses the issue. Fixes: https://gitlab.gnome.org/GNOME/gvfs/-/issues/619
View Lorry Controller Status