| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
The newly introduced MountOpReply2 interface is not expansible and
future changes would mean other complications. Let's make the interface
expansible thanks to a{sv} expansion argument instead of adding new
and new arguments and fallbacks...
|
|
|
|
|
|
| |
Simplify comments for translators to make them oneline. Multiline
comments seems doesn't work and the first part of the comment is
not really useful anyway.
|
|
|
|
|
| |
The newly added MountOpReplyData contains variables which are not
later used. Let's remove those unused variables.
|
|
|
|
|
|
|
|
| |
Add support for unlocking TrueCrypt and VeraCrypt compatible (TCRYPT)
volumes.
Add a new MountOpReply2 method to the dbus interface, which handles the
parameters required to unlock TCRYPT volumes.
|
|
|
|
| |
This reverts commit 550aaf87c222a1626273e579e566f889b43006cf.
|
|
|
|
|
| |
The proposed GitLab CI uses Fedora Rawhide which doesn't include the
latest GLib yet. Let's use g_unix_mount_get_options conditionaly.
|
|
|
|
|
|
|
|
| |
GAsyncReadyCallback is never called from g_drive_stop, because
source_tag is not set, but checked. This obviously causes issues
for client applications. Add missing source_tag.
Closes: https://gitlab.gnome.org/GNOME/gvfs/issues/1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GVfsUDisks2VolumeMonitor handles x-gvfs-hide/x-gvfs-show mount options
used to overwrite our heuristics whether the mount should be shown, or
hidden. Unfortunately, it works currently only for mounts with
corresponding fstab entries, because the options are read over
g_unix_mount_point_get_options. Let's use the newly introduced
g_unix_mount_get_options to allow reading of the options for all sort
of mounts (e.g. created over pam_mount, or manually mounted).
Update GLib dependency accordingly.
https://bugzilla.gnome.org/show_bug.cgi?id=795578
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For the same reasons that the equivalent change to the mtp backend
was desirable, we want to do this in the gphoto2 (ptp) backend.
Stable URIs allow things like bookmarking and external scripting
to work across plug/unplug events (which is to say, allows them
to work at all).
See the change description for the mtp backend for more details.
https://bugzilla.gnome.org/show_bug.cgi?id=795311
|
|
|
|
|
|
| |
udisks2 volume monitor contains some variables, or debug prints which
contains gdu prefixes, or functionality. Let's rename, or remove
that stuff.
|
|
|
|
|
| |
libgdu has been removed in 2011 and is superseded by libudisks2, so
there is no need to have gdu volume monitor in the tree.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, we generate our device uris using the USB bus number and
device number. The device number is a monotonically increasing number
that goes up for each new device plugged into a bus, and that
includes replugging a device.
This is inconvenient for a couple of reasons:
1: Modern Android devices actually trigger a replug event when you
switch them into File Transfer mode, so if you, or your file
manager opens a window before switching modes, that window
ends up being useless.
2: You can't write automation that encodes device uris as these
end up being unpredictable
This commit implements a change to the device uri to use the
ID_SERIAL field provided by udev. If the device has a serial
number, it will be combined with the product identity to
yield this value. If the device has no serial number, then
udev will fallback to using product identity only.
The end result is that a device with a real serial number
will always appear with the same uri, regardless of when or
where it is plugged in. If a device has no serial number, or
has a broken one (eg: all zeros, all the time), then one such
device will work fine, but if a second one is plugged in, it
will be ignored. We have chosen to ignore the device to avoid
implementing a fallback uri generation scheme.
The code becomes slightly more complicated because you cannot directly
look up a device in this way, and libmtp works with dev/bus numbers.
That requires a couple of additional lookups, but it's nothing
serious.
Note that this does not perfectly fix problem 1) because there's
no event triggered which causes Nautilus to refresh the device
window. If you manually refresh, you will see the contents.
https://bugzilla.gnome.org/show_bug.cgi?id=789561
https://bugzilla.gnome.org/show_bug.cgi?id=744267
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If an optical drive is hard-unplugged without ejecting a media first (or
the corresponding UDisksDrive object simply disappears from D-Bus for
example due to the udisksd termination) and an audio disk or an empty
media is inside, corresponding volumes/mounts are not properly removed.
Consequently, the number of the volumes/mounts increase when plugging
and unplugging such drive. This happens because those kinds of volumes/
mounts are handled by their drives in the monitor. Unfortunately, the
drive is removed before processing them and the mounts/volumes without
the drives are ignored consequently.
Let's do not rely on the drives and handle those volumes/mounts over
corresponding UDisksBlock objects, same as it is done for other kinds of
volumes.
https://bugzilla.gnome.org/show_bug.cgi?id=719423
|
|
|
|
|
|
|
| |
To avoid the burden of maintaining multiple build systems, this
patch removes autotools support.
https://bugzilla.gnome.org/show_bug.cgi?id=786149
|
|
|
|
|
|
|
|
| |
Our codes don't use GModule APIs directly, so there is no need for
gmodule.h includes. GModule has been replaced by GIOModule in our codes
long time ago. gmodule.h is included indirectly over gio.h anyway.
https://bugzilla.gnome.org/show_bug.cgi?id=794365
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
If there's no device file, which means libusb won't be able to open the
device, no need to print a warning, simply ignore the device.
https://bugzilla.gnome.org/show_bug.cgi?id=793925
|
|
|
|
|
|
|
| |
If there's no device file, which means libusb won't be able to open the
device, no need to print a warning, simply ignore the device.
https://bugzilla.gnome.org/show_bug.cgi?id=793925
|
|
|
|
|
|
|
| |
Currently, PARTLABEL and PARTUUID is not handled and consequently redundant
GVfsUDisks2Volume is presented. Add support for them.
https://bugzilla.gnome.org/show_bug.cgi?id=793545
|
|
|
|
|
|
|
| |
"device + 6" is used to skip "UUID=" prefix in the string, but it
should be "device + 5" since it has only 5 chars.
https://bugzilla.gnome.org/show_bug.cgi?id=793545
|
|
|
|
|
| |
g_object_ref() currently propagates parameter type to its return value,
so type casts needs to be added in order to prevent compiler warnings.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=786149
|
|
|
|
|
|
| |
See https://developer.gnome.org/hig/stable/typography.html
https://bugzilla.gnome.org/show_bug.cgi?id=772219
|
|
|
|
|
|
| |
GSimpleAsyncResult is deprecated in favour of GTask and should be replaced.
https://bugzilla.gnome.org/show_bug.cgi?id=747412
|
|
|
|
|
|
| |
GSimpleAsyncResult is deprecated in favour of GTask and should be replaced.
https://bugzilla.gnome.org/show_bug.cgi?id=747412
|
|
|
|
|
|
| |
GSimpleAsyncResult is deprecated in favour of GTask and should be replaced.
https://bugzilla.gnome.org/show_bug.cgi?id=747412
|
|
|
|
|
|
| |
GSimpleAsyncResult is deprecated in favour of GTask and should be replaced.
https://bugzilla.gnome.org/show_bug.cgi?id=747412
|
|
|
|
|
|
| |
GSimpleAsyncResult is deprecated in favour of GTask and should be replaced.
https://bugzilla.gnome.org/show_bug.cgi?id=747412
|
|
|
|
|
|
| |
GSimpleAsyncResult is deprecated in favour of GTask and should be replaced.
https://bugzilla.gnome.org/show_bug.cgi?id=747412
|
|
|
|
|
|
| |
GSimpleAsyncResult is deprecated in favour of GTask and should be replaced.
https://bugzilla.gnome.org/show_bug.cgi?id=747412
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
The GIO_MODULE_DIR macro is using an invalid variable for GIO module
dir. This patch fixes the variable name.
https://bugzilla.gnome.org/show_bug.cgi?id=786149
|
|
|
|
|
|
|
| |
This patch adds support for elogind in meson, which is systemd-login
extracted as a standalone package.
https://bugzilla.gnome.org/show_bug.cgi?id=788707
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
The GDU monitor service file is not created properly due to missing
service name variable declaration.
This patch adds the variable declaration which fixes the problem.
https://bugzilla.gnome.org/show_bug.cgi?id=786149
|
|
|
|
|
|
|
|
| |
meson_options.txt is hard to read. Let's create sorted groups of options
and unify the description. Also change some option names to match
correspoding backend names.
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
|
|
|
|
|
|
|
|
| |
The device file checks were added by mistake and it is not clear whether
it can't have some side-effect. Let's remove them and use g_strcmp0 for
sysfs path comparison for sure...
https://bugzilla.gnome.org/show_bug.cgi?id=789491
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=789491
|
|
|
|
|
|
|
|
| |
It doesn't make sense to have commented g_debug prints, then they are
totally unusable. Let's uncomment them, so they can be printed if
G_MESSAGES_DEBUG is specified...
https://bugzilla.gnome.org/show_bug.cgi?id=789491
|
|
|
|
|
|
|
|
| |
UDev events for devices without ID_GPHOTO2 property are ignored.
Although ID_GPHOTO2 seems don't have to be set for device when removing
and thus the volume is not removed. Let's ignore ID_GPHOTO2 when removing.
https://bugzilla.gnome.org/show_bug.cgi?id=789491
|
|
|
|
|
|
|
|
| |
UDev events for devices without ID_MTP_DEVICE property are ignored.
Although ID_MTP_DEVICE seems don't have to be set for device when removing
and thus the volume is not removed. Let's ignore ID_MTP_DEVICE when removing.
https://bugzilla.gnome.org/show_bug.cgi?id=789491
|
|
|
|
|
|
|
|
|
|
|
|
| |
Automatic shadow mount handling in some cases works currently only thanks
to the bug in g_daemon_file_prefix_matches implementation, which I am going
to fix. The problematic case is when activation_root is equal to mount_root
(e.g. Nextcloud integration). The bug in _prefix_matches causes that it
succeeds also if the paths are equal, but this is wrong as per the docs.
Let's use also g_file_equal when looking for shadow mounts in order to fix
this issue.
https://bugzilla.gnome.org/show_bug.cgi?id=786217
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
The generic_text variable is used currently to determine which strings
should be used for notifications. It is TRUE if unmounting (i.e. mount
is set) and FALSE otherwise (i.e. drive is set). Remove this variable
and make it more obvious...
https://bugzilla.gnome.org/show_bug.cgi?id=775891
|
|
|
|
|
|
|
| |
Do not address the user directly in the strings. Add a missing
description for the notifications.
https://bugzilla.gnome.org/show_bug.cgi?id=775891
|
|
|
|
|
|
|
| |
Error strings in gvfsproxyvolumemonitordaemon.c are not marked as
translatable and thus it might be shown untranslated in UI, mark them.
https://bugzilla.gnome.org/show_bug.cgi?id=776616
|
|
|
|
|
|
|
|
|
|
|
|
| |
"You can now unplug %s\n" is used for mounts with filesystem,
"%s has been unmounted\n" is used otherwise when unmounting.
It is confusing to say "unplug" for drives with multiple mounts,
or for drives, which need to be ejected, or stopped. I think
"unplug" should be used only when ejecting, or stopping. It might
lead to data loss if user unplug the device after unmounting one
of several mounts.
https://bugzilla.gnome.org/show_bug.cgi?id=774192
|
|
|
|
|
|
|
|
| |
gvfs_udisks2_volume_get_uuid returns NULL regardless of the output
from udisks_block_get_id_uuid currently. Set volume->uuid property
and handle its changes properly.
https://bugzilla.gnome.org/show_bug.cgi?id=772894
|
|
|
|
|
|
| |
GSimpleAsyncResult is deprecated in favour of GTask and should be replaced.
https://bugzilla.gnome.org/show_bug.cgi?id=747412
|