| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The `PartOf` directive sets up a one-way dependency between
`graphical-session.target` and our services, so that when
`graphical-session.target` is stopped or restarted, our services also get
stopped or restarted.
This ensures that gvfs daemons that were started in the context of a GUI
login session (through dbus activation) do not continue to run after the
user has logged out.
See `systemd.unit(5)` for more info.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This puts all gvfs systemd services (which are all dbus-activated through
`SystemdService=`) inside of the `session` slice that was introduced in
v249 (https://github.com/systemd/systemd/pull/16603) and described in
https://systemd.io/DESKTOP_ENVIRONMENTS/ and `systemd.special(7)`
This allows sysadmins or OS integrators to assign higher-priority
`systemd.resource-control(5)` on `session.slice` and have it propagate
down to important session services such as gvfs, so that the gvfs daemons
receive sufficient priority for resource allocations to keep the session
running smoothly under load.
Note that it still works on older systemd
(the slice, which is just a cgroup inner directory, is created on demand)
|
|
|
|
|
|
|
| |
GVfs build with --werror fails currently because of glib!1719. Let's
drop the volatile qualifier as it doesn't help with atomicity anyway.
Relates: https://gitlab.gnome.org/GNOME/glib/-/issues/600
|
|
|
|
|
|
|
|
|
|
| |
Since commit f5ee590e, it is not possible to access Nextcloud/ownCloud
shares with self-signed (or invalid) certificates. This is because
the mount operation is handled by GOA volume monitor and the prompt
to accept certificate is not shown. Let's update the volume monitor
to handle just passwords and show the prompt to the client.
Fixes: https://gitlab.gnome.org/GNOME/gvfs/issues/251
|
|
|
|
|
|
|
|
| |
Target executables used as monitors do not depend on `libgvfscommon`
or `libgvfsdaemon`, which are `gvfs` libraries installed outside of
the default library directory.
Due to this reason, they don't need to set `rpath` parameter.
|
|
|
|
|
|
|
|
|
| |
Although usually directory variables are set by using the `prefix`
directory, this might cause issues due to parameters that need
relative directories.
In order to ease the transition `prefix` directory has been stripped
from directory variables and only has been appended when necessary.
|
|
|
|
|
|
|
|
|
| |
The names of the variables in meson corresponding to the variables
obtained from the pkg-config files has been fixed by using a
pattern.
The pattern uses the dependency name as the prefix and the obtained
variable as the suffix.
|
|
|
|
|
|
|
| |
Add missing trailing commas that avoids getting noise when another
file/parameter is added and eases reviewing changes[0].
[0] https://gitlab.gnome.org/GNOME/dconf/merge_requests/11#note_291585
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All the available monitors install a set of files: volume monitor
files, DBus service files, etc...
These build commands are mostly common and only file names change,
which are built using a given pattern. These build commands have
been replaced by only one set of build commands that adapt to
monitors needs by changing their name and simplifies the entire
process.
These changes also help installing `GOA` and `MTP` necessary test
files.
|
|
|
|
| |
This reverts commit c25bc351bb2605e57bc9a6d9250c9d4748c3d9e0.
|
|
|
|
| |
This reverts commit f4ee93b06cfc4d9f727f9174e40d08097a25d571.
|
|
|
|
| |
This reverts commit 22e9f7721b891b17cd726f1bf92b15a35be34d22.
|
|
|
|
| |
This reverts commit db31059d1b7b11b597b03064329fb1e8899b11f2.
|
|
|
|
|
|
|
|
|
| |
Although usually directory variables are set by using the `prefix`
directory, this might cause issues due to parameters that need
relative directories.
In order to ease the transition `prefix` directory has been stripped
from directory variables and only has been appended when necessary.
|
|
|
|
|
|
|
|
|
| |
The names of the variables in meson corresponding to the variables
obtained from the pkg-config files has been fixed by using a
pattern.
The pattern uses the dependency name as the prefix and the obtained
variable as the suffix.
|
|
|
|
|
|
|
| |
Add missing trailing commas that avoids getting noise when another
file/parameter is added and eases reviewing changes[0].
[0] https://gitlab.gnome.org/GNOME/dconf/merge_requests/11#note_291585
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All the available monitors install a set of files: volume monitor
files, DBus service files, etc...
These build commands are mostly common and only file names change,
which are built using a given pattern. These build commands have
been replaced by only one set of build commands that adapt to
monitors needs by changing their name and simplifies the entire
process.
These changes also help installing `GOA` and `MTP` necessary test
files.
|
|
|
|
|
|
|
| |
To avoid the burden of maintaining multiple build systems, this
patch removes autotools support.
https://bugzilla.gnome.org/show_bug.cgi?id=786149
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gvfs is using a set of glib libraries (gio-2.0, gio-unix-2.0, glib,
gobject-2.0) in almost all the created objects. However, these
dependencies are not always necessary.
gvfs' meson port also uses some internal dependencies formed by
built libraries. This internal dependencies depend on other
dependendecies as well.
These both issues have been fixed by reviewing all the internal
dependencies and built objects.
https://bugzilla.gnome.org/show_bug.cgi?id=794365
|
|
|
|
|
|
|
|
|
|
|
|
| |
When systemd user units installation is disabled, SystemdService
entry should also not be present on D-Bus service files.
This patch adds a common D-Bus service file template allowing,
an homogeneus D-Bus service file generation and also a
SystemService entry conditioned to the systemd user units
installation option.
https://bugzilla.gnome.org/show_bug.cgi?id=786149
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of being hardcoded, D-Bus, systemd and GIO modules paths
can be checked by using the information in their correspondant
pkg-config files.
This patch uses the information on pkg-config files by default,
and also allows the user to provide this information to avoid
overwriting system files.
https://bugzilla.gnome.org/show_bug.cgi?id=786149
|
|
|
|
|
|
|
|
| |
meson is a build system focused on speed an ease of use, which
helps speeding up the software development. This patch adds meson
support along autotools.
https://bugzilla.gnome.org/show_bug.cgi?id=786149
|
|
|
|
|
|
|
|
|
| |
Password-based authentication used for ownCloud/Nextcloud was broken
by GTask port (commit fdda284). GTask is used as user_data for async
callbacks currently, however, user_data is incorrectly cast to MountOp
in this case. Use g_task_get_task_data in order to fix this issue.
https://bugzilla.gnome.org/show_bug.cgi?id=780496
|
|
|
|
|
|
| |
GSimpleAsyncResult is deprecated in favour of GTask and should be replaced.
https://bugzilla.gnome.org/show_bug.cgi?id=747412
|
|
|
|
|
|
|
|
|
|
|
| |
This option allows maintainers to specify the directory that contain
a systemd user units, or disable it. Default location for these units
is /usr/lib/systemd/user. This patch will switch from hard-coded path
to configurable one.
The patch was modified by Ondrej Holy <oholy@redhat.com>.
https://bugzilla.gnome.org/show_bug.cgi?id=760293
|
|
|
|
|
|
|
|
| |
When using "systemd --user" in conjunction with "dbus-daemon --session
--systemd-activation", this ensures that each daemon is correctly placed
in its own cgroup, instead of being treated as part of dbus.service.
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=755760
|
|
|
|
|
|
|
| |
The Google Drive backend would be OAuth2-based, so we should include
such accounts too.
https://bugzilla.gnome.org/show_bug.cgi?id=739008
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows you to easily allow access to gvfs from a sandbox.
Just give it talk access to org.gtk.vfs.* and everything will work.
This change does three things:
Change the existing mountpoint dbus names from
org.gtk.vfs.mountpoint.foo
to
org.gtk.vfs.mountpoint_foo
For other mountpoints, always own:
org.gtk.vfs.mountpoint_$pid
Change the dbus name of the volume monitors from
org.gtk.Private.fooMonitor
to
org.gtk.vfs.fooMonitor
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Passing GoaAccount:id to GetPassword makes no logical sense. It works
because it is ignored by GOA for ownCloud accounts.
The ID is meant as a key when an account might have multiple passwords.
eg., an email account can have separate passwords for IMAP and SMTP,
and the keys can be "imap-password", "smtp-password". This is not the
case for ownCloud and the ID field is ignored by GOA because the key
is always "password". Since ownCloud is the only password-based
account that this volume monitor supports, let's just use "password".
https://bugzilla.gnome.org/show_bug.cgi?id=739078
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=738883
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=738878
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=591228
|
|
|
|
|
|
|
|
| |
Now that we can be in charge of mounts even if we have the shadow
mount infrastructure, we should export it so that tracking
of the associated GDaemonMount works correctly.
https://bugzilla.gnome.org/show_bug.cgi?id=696279
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=695834
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=686526
|