Commits on Source (40)
-
Ondrej Holy authored129819c5
-
Kjartan Maraas authored9983be6d
-
Milo Casagrande authored4dd360dd
-
Ondrej Holy authored47caf9fc
-
Ondrej Holy authored3a1428a4
-
Damjan Jovanovic authored
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
981787fd -
Trần Ngọc Quân authored28cebaec
-
Jan Alexander Steffens (heftig) authored
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.
d34ad86e -
Ondrej Holy authored
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.
9f7d3171 -
Nathan Follens authored8d104bd1
-
Мирослав Николић authored5918bb5f
-
Jordi Mas authored4bb8a42f
-
Ondrej Holy authored
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
06f90d28 -
Ondrej Holy authored
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
5f9cffd1 -
Ondrej Holy authored
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
034ca8bd -
Ondrej Holy authored
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
117d5318 -
Ondrej Holy authored
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
c615cfe1 -
Dz Chen authored4f95a2a0
-
Diego Escalante Urrelo authored
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
1e2867ef -
Ondrej Holy authoreda971ec4b
-
Laurent Bigonville authored010dbfe4
-
Laurent Bigonville authorede51a8c57
-
Laurent Bigonville authored
Support is disabled at build time on non-linux architectures
232a7fb1 -
Laurent Bigonville authored57015b89
-
Laurent Bigonville authored3d648022
-
Simon McVittie authored45431d31
-
Simon McVittie authored
Update to upstream version '1.48.0' with Debian dir e343fc021100fb4a0d8255de6835febdd27582c6
9c65012b -
Simon McVittie authored09fe6f4f
-
Simon McVittie authored
Update to upstream version '1.48.1' with Debian dir e343fc021100fb4a0d8255de6835febdd27582c6
8c55fc00 -
Simon McVittie authored6e7773c4
-
Simon McVittie authored
Gbp-Dch: ignore
c93ddc22 -
Simon McVittie authored
Let's put the new upstream release first since it's the biggest change.
49805df2 -
Simon McVittie authoreddd0ad5e4
-
Simon McVittie authoredc6c6a923
-
Simon McVittie authored7af0ed5a
-
Simon McVittie authored
We still need these symlinks for now (at least gvfsd-archive, because nemo hard-codes it), and Lintian is being over-zealous to diagnose a symlink from /usr/lib into /usr/libexec as an error.
937961b6 -
Simon McVittie authoredde975fc1
-
Simon McVittie authoreda569da2f
-
Sebastien Bacher authored13ea4396
-
Sebastien Bacher authored185706db
debian/gvfs-backends.lintian-overrides
0 → 100644
debian/gvfs-daemons.lintian-overrides
0 → 100644
debian/gvfs-fuse.lintian-overrides
0 → 100644