summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Release version 1.48.21.48.2Ondrej Holy2022-05-261-0/+8
|
* build: Remove incorrect i18n.merge_file argumentOndrej Holy2022-05-261-1/+0
| | | | | | | | | | The positional argument was being silently ignored until meson 0.60.0 where it fails with "ERROR: Function does not take positional arguments". Related: https://github.com/mesonbuild/meson/issues/9441 Fixes: https://gitlab.gnome.org/GNOME/gvfs/-/issues/599 (cherry picked from commit 17a067b9)
* 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 (cherry picked from commit 8c7e79042d819304ea38408d0d90313eef7a3869)
* smb: Ignore EINVAL for kerberos/ccache loginOndrej Holy2022-05-052-3/+15
| | | | | | | | | | With samba 4.16.0, mount operation fails with the "Invalid Argument" error when kerberos/ccache is misconfigured. Ignore this error, so user get a chance to login using the password... Fixes: https://gitlab.gnome.org/GNOME/gvfs/-/issues/611 (cherry picked from commit 747c7f6ea6c8b6a7ccd008bb47996ba7eb169bcc)
* sftp: Adapt on new OpenSSH password promptsOndrej Holy2021-10-261-6/+6
| | | | | | | | | | | | SFTP backend fails when connecting with the "Timed out when logging in" error with the recent OpenSSH versions. This is because their password prompts are now prefixed by the `(user@host)` string, which breaks our `g_str_has_prefix` checks. Let's use `strstr` instead to fix this issue and also to not break compatibility with old versions and other vendors. Fixes: https://gitlab.gnome.org/GNOME/gvfs/-/issues/584 (cherry picked from commit 15bf21e5dd2532ebf98400bd128e78d5bbd17938)
* Update Hebrew translationYaron Shahrabani2021-09-271-817/+1054
|
* Update Persian translationDanial Behzadi2021-09-221-2091/+1995
|
* Updated Danish translationAsk Hjorth Larsen2021-09-171-2251/+2331
|
* Update Basque translationAsier Sarasua Garmendia2021-09-081-86/+87
|
* Update Croatian translationGoran Vidović2021-09-051-395/+495
|
* Update Chinese (Taiwan) translationChao-Hsiung Liao2021-07-101-363/+463
|
* Update Russian translationAlexey Rubtsov2021-06-301-248/+2322
|
* Update Russian translationAlexey Rubtsov2021-06-281-2855/+279
|
* Update Slovak translationDušan Kazik2021-06-111-330/+423
|
* admin: Fix mount operation hang caused by pkexec failureOndrej Holy2021-06-071-1/+25
| | | | | | | | | Currently, the mount operation for the admin backend can hang when the authentication dialog is dismissed for example. This is because `pkexec` exits before spawning the `gvfsd-admin` daemon. Let's catch that case and return the "Permission denied" error. Fixes: https://gitlab.gnome.org/GNOME/gvfs/-/issues/565
* admin: Make the privileged group configurableOndrej Holy2021-06-074-5/+15
| | | | | | | | | Currently, `wheel` group is hardcoded in the `.rules` file which is there to prevent redundant password prompt when starting gvfsd-admin. The Debian based systems obviously uses `sudo` group instead of `wheel`. Let's make the privileged group configurable. https://gitlab.gnome.org/GNOME/gvfs/-/issues/565
* Update Occitan translationQuentin PAGÈS2021-05-131-1772/+1645
|
* Update Nepali translationPawan Chitrakar2021-05-041-1060/+1026
|
* Post release version bumpOndrej Holy2021-04-301-1/+1
|
* Release version 1.48.11.48.1Ondrej Holy2021-04-301-0/+8
|
* build: Use install prefix in systemd files pathsDiego Escalante Urrelo2021-04-231-2/+2
| | | | | | | | | | When installing gvfs into a prefix (like in jhbuild), we need to pass `gvfs_prefix` to meson's `get_pkgconfig_variable` to make sure that systemd unit files are installed to the installation prefix, instead of systemd's prefix (which will likely be your system's /usr). See: https://github.com/systemd/systemd/issues/18082 See: https://github.com/systemd/systemd/commit/1c2c7c6cb3d92315624f3711114e86b0acfbce63
* Update Chinese (China) translationDz Chen2021-04-161-354/+486
|
* client: Prevent socket leaks if socket dir is inaccessibleOndrej Holy2021-04-151-13/+75
| | | | | | | | | | | | | GVfs fallbacks to session bus if it is not possible to establish peer-to-peer connection (e.g. inside Flatpak sandbox). However, the DBus server is not terminated and the socket is leaked. The named sockets are counted as open files, so it can easily lead to "Too many open files" errors. Let's fallback to the session bus immediately if the socket dir is not accessible to prevent the leaks. This should fix the most common case, when the sockets are leaked. Fixes: https://gitlab.gnome.org/GNOME/gvfs/-/issues/542
* admin: Fail when peer credentials are not availableOndrej Holy2021-04-151-0/+9
| | | | | | | | | Currently, critical errors are printed when peer credentials aren't available (i.e. session bus fallback is used). Let's return an error immediately to prevent the criticals. Also add warning with suggestion to allow `--filesystem=xdg-run/gvfsd` access. https://gitlab.gnome.org/GNOME/gvfs/-/issues/305
* admin: Pass also XDG_RUNTIME_DIR to pkexec environmentOndrej Holy2021-04-152-1/+6
| | | | | | | | | | | Recently, GVfs switched from abstract sockets to named sockets. The sockets are created in the `XDG_RUNTIME_DIR` directory. This directory is not unfortunatelly set for `gvfsd-admin` and thus the root's cache dir is used instead, which is wrong. Let's pass the `XDG_RUNTIME_DIR` environment variable to the `pkexec` environment similarly to `DBUS_SESSION_BUS_ADDRESS`. Fixes: https://gitlab.gnome.org/GNOME/gvfs/-/issues/552
* daemon: Fix socket owner for gvfsd-adminOndrej Holy2021-04-151-0/+13
| | | | | | | | | | Recently, GVfs switched from abstract sockets to named sockets. The named sockets honors file permissions and thus the socket owner is root in the case `gvfsd-admin`. This obviously prevents client from connecting. Let's change the owner to the value of `PKEXEC_UID` to ensure that the socket is usable by the client. https://gitlab.gnome.org/GNOME/gvfs/-/issues/552
* daemon: Create socket dir from gvfsd daemonOndrej Holy2021-04-154-2/+14
| | | | | | | | | | | Recently, GVfs switched from abstract sockets to named sockets. The socket dir is currently created by the individual daemons immediately before starting DBus server. If gvfsd-admin is started at first, the socket dir is owned by root user and thus it isn't accesible for other daemons and clients. Let's create the socket dir early from the gvfsd daemon to ensure correct ownership. https://gitlab.gnome.org/GNOME/gvfs/-/issues/552
* Update Catalan translationJordi Mas2021-04-131-2/+2
|
* Update Serbian translationМирослав Николић2021-04-111-316/+425
|
* Update Dutch translationNathan Follens2021-04-011-404/+503
|
* ci: Add ipv6 in tags to fix random test suite failureswip/oholy/ci-fixOndrej Holy2021-04-011-0/+1
| | | | | | | | | The DAV test cases sometimes fails with "(98)Address already in use: AH00072: make_sock: could not bind to address 127.0.0.1:8088". This seems to happen only on runners which don't have ipv6 tag. Let's temporarily add the tag to fix those failures. It would be best to programmatically try some range of ports, but this is currently out of my time resources.
* daemon: Remove connection socket properlyJan Alexander Steffens (heftig)2021-03-241-67/+28
| | | | | | | | | | The naming scheme for the non-abstract socket was changed but `new_connection_data_free` was not adjusted to match. `GDBusServer` will remove the socket when it stops, but only if `g_dbus_server_start` was called. So we can simplify the process somewhat. Also don't bother removing the directory now that all sockets share it.
* Update Vietnamese translationNgọc Quân Trần2021-03-231-325/+410
|
* udisks2: Report unmount progress after showing blocking processesDamjan Jovanovic2021-03-191-11/+3
| | | | | | | | | | | | | | | The "show-unmount-progress" signal isn't emitted when unmounting is successful while the "show-processes" dialog is open. The "aborted" signal is sent to close the dialog, not to indicate an error, and shouldn't be taken into consideration when deciding whether to emit "show-unmount-progress". Further details on the bug report. Get gvfs_udisks2_unmount_notify_stop() to send "show-unmount-progress" whether there was a prior "aborted" or not. Closes https://gitlab.gnome.org/GNOME/gvfs/-/issues/546
* Post release version bumpOndrej Holy2021-03-191-1/+1
|
* Update NEWS for 1.48.0 release1.48.0Ondrej Holy2021-03-191-0/+4
|
* Update Italian translationMilo Casagrande2021-03-151-397/+482
|
* Update Norwegian Bokmål translationKjartan Maraas2021-03-131-339/+419
|
* Post release version bumpOndrej Holy2021-03-121-1/+1
|
* Update NEWS for 1.47.91 release1.47.91Ondrej Holy2021-03-121-0/+4
|
* Update Kazakh translationBaurzhan Muftakhidinov2021-03-111-358/+444
|
* Update Friulian translationFabio Tomat2021-03-101-141/+154
|
* Update Catalan translationJordi Mas2021-03-091-84/+81
|
* Update Finnish translationJiri Grönroos2021-03-091-54/+44
|
* Update French translationCharles Monzat2021-03-091-406/+496
|
* Updated Czech translationMarek Černocký2021-03-081-77/+89
|
* Update Catalan translationJordi Mas2021-03-071-353/+417
|
* Update Polish translationPiotr Drąg2021-03-071-399/+485
|
* Update British English translationZander Brown2021-03-071-402/+532
|
* Update Korean translationChangwoo Ryu2021-03-061-417/+482
|
View Lorry Controller Status