summaryrefslogtreecommitdiff
path: root/monitor
Commit message (Collapse)AuthorAgeFilesLines
* udisks2: Restore Unicode quotation marksPiotr Drąg2017-11-281-1/+1
| | | | | | See https://developer.gnome.org/hig/stable/typography.html https://bugzilla.gnome.org/show_bug.cgi?id=772219
* proxy: Port GProxyDrive to GTaskOndrej Holy2017-11-281-225/+131
| | | | | | GSimpleAsyncResult is deprecated in favour of GTask and should be replaced. https://bugzilla.gnome.org/show_bug.cgi?id=747412
* proxy: Port GProxyMount to GTaskOndrej Holy2017-11-281-69/+53
| | | | | | GSimpleAsyncResult is deprecated in favour of GTask and should be replaced. https://bugzilla.gnome.org/show_bug.cgi?id=747412
* proxy: Port GProxyVolume to GTaskOndrej Holy2017-11-281-82/+49
| | | | | | GSimpleAsyncResult is deprecated in favour of GTask and should be replaced. https://bugzilla.gnome.org/show_bug.cgi?id=747412
* udisks2: Port GVfsUDisks2Mount to GTaskOndrej Holy2017-11-281-209/+157
| | | | | | GSimpleAsyncResult is deprecated in favour of GTask and should be replaced. https://bugzilla.gnome.org/show_bug.cgi?id=747412
* udisks2: Port GVfsUDisks2Utils to GTaskOndrej Holy2017-11-281-76/+43
| | | | | | GSimpleAsyncResult is deprecated in favour of GTask and should be replaced. https://bugzilla.gnome.org/show_bug.cgi?id=747412
* udisks2: Port GVfsUDisks2Volume to GTaskOndrej Holy2017-11-281-226/+157
| | | | | | GSimpleAsyncResult is deprecated in favour of GTask and should be replaced. https://bugzilla.gnome.org/show_bug.cgi?id=747412
* udisks2: Port GVfsUDisks2Drive to GTaskOndrej Holy2017-11-281-173/+72
| | | | | | GSimpleAsyncResult is deprecated in favour of GTask and should be replaced. https://bugzilla.gnome.org/show_bug.cgi?id=747412
* build: Make SystemdService entry conditionalIñigo Martínez2017-11-076-59/+114
| | | | | | | | | | | | 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
* build: Fix GIO_MODULE_DIR in GDU volume monitorIñigo Martínez2017-11-071-1/+1
| | | | | | | 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
* build: Enable elogind support in mesonIñigo Martínez2017-11-012-3/+3
| | | | | | | 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
* build: Improve installation on system pathsIñigo Martínez2017-10-316-18/+18
| | | | | | | | | | | | 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
* build: Fix missing GDU monitor service fileIñigo Martínez2017-10-311-0/+2
| | | | | | | | | 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
* build: Reorder meson options and update descriptionOndrej Holy2017-10-311-1/+1
| | | | | | | | 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
* build: Port to meson build systemIñigo Martínez2017-10-3117-0/+468
| | | | | | | | 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
* monitor: Remove device file checksOndrej Holy2017-10-314-4/+4
| | | | | | | | 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
* gphoto2: Fix wrong format specifier in debug printOndrej Holy2017-10-311-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=789491
* gphoto2: Uncomment debug printsOndrej Holy2017-10-271-12/+8
| | | | | | | | 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
* gphoto2: Fix volume removal with current udev behaviorOndrej Holy2017-10-271-11/+6
| | | | | | | | 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
* mtp: Fix volume removal with current udev behaviorOndrej Holy2017-10-261-11/+6
| | | | | | | | 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
* proxy: Fix shadow mount handling for equal pathsOndrej Holy2017-08-211-1/+2
| | | | | | | | | | | | 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
* goa: Fix password-based authenticationOndrej Holy2017-07-191-1/+1
| | | | | | | | | 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
* udisks2: Refactor notification handlingOndrej Holy2017-01-114-15/+9
| | | | | | | | | 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
* udisks2: Improve unmount notificationsOndrej Holy2017-01-111-4/+4
| | | | | | | 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
* monitor: Mark error strings as translatableOndrej Holy2017-01-061-13/+13
| | | | | | | 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
* udisks2: Always use generic notification when unmountingOndrej Holy2016-11-181-1/+1
| | | | | | | | | | | | "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
* udisks2: Add support for uuidOndrej Holy2016-11-101-0/+6
| | | | | | | | 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
* goa: Port GVfsGoaVolume to GTaskOndrej Holy2016-10-261-103/+69
| | | | | | GSimpleAsyncResult is deprecated in favour of GTask and should be replaced. https://bugzilla.gnome.org/show_bug.cgi?id=747412
* Drop hal volume monitor and fallback code in gphoto2 and cdda backendMichael Biebl2016-10-1933-7872/+17
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=770671
* udisks2: Remove obsoleted codeOndrej Holy2016-10-171-5/+0
| | | | | Let's remove code for gio < 2.31.19, GVfs already requires a newer version.
* Revert "udisks2: Filter out system mounts"Ondrej Holy2016-10-171-3/+0
| | | | This reverts commit 078588c4698742eb8c3308275f5bc457f72b2302.
* Revert "udisks2: Use device path to match mount points also"Ondrej Holy2016-10-171-3/+1
| | | | This reverts commit b77369832fd6fb97e1f036998663f2488ff15022.
* udisks2: Fix handling of volumes with multiple mountpointsOndrej Holy2016-10-101-2/+4
| | | | | | | | | Volume is not included currently if it has multiple mount points and one of them is not considered as user interesting. Change this logic and include all volumes with at least one user interesting mount point. https://bugzilla.gnome.org/show_bug.cgi?id=772306
* Use Unicode in translatable stringsPiotr Drąg2016-10-033-5/+5
| | | | | | See https://developer.gnome.org/hig/stable/typography.html https://bugzilla.gnome.org/show_bug.cgi?id=772219
* udisks2: Filter out system mountsOndrej Holy2016-10-031-0/+3
| | | | | | | | | | | | | | System mounts (i.e. autofs) can be considered as user interesting currently if mount paths are user interesting. However, we should not handle those mounts as GMounts, because consequently redundant mounts are offered by volume monitor. It also causes automounts of autofs filesystems. $ mount | grep /media/test systemd-1 on /media/test type autofs ... localhost:/home/oholy on /media/test type nfs4 ... https://bugzilla.gnome.org/show_bug.cgi?id=771740
* udisks2: Use device path to match mount points alsoOndrej Holy2016-10-031-1/+3
| | | | | | | | | | | | | Mount path is used to match mount points currently, however device path should be used also in order to be sure it is really corresponding mount point. Same mount path can be used for multiple mount entries (it is also used e.g. for autofs). $ mount | grep /media/test systemd-1 on /media/test type autofs ... localhost:/home/oholy on /media/test type nfs4 ... https://bugzilla.gnome.org/show_bug.cgi?id=771740
* afc: Fix volume init with a locked deviceBastien Nocera2016-06-091-22/+10
| | | | | | | | | | | | | | | | | The first time we connect the device, we won't be able to create a lockdown client with a handshake, so the volume won't be created at all and will not show up in nautilus. Furthermore, we were checking the OS version with a paired lockdown client (which is not needed, an unpaired one will do just as well) and checking whether HouseArrest was supported even if the service was different. So, we never needed to have a paired lockdown client in the first place, and we only need to check for the OS version if HouseArrest is what was requested. https://bugzilla.gnome.org/show_bug.cgi?id=767399
* afc: Add more debug when initialisation failsBastien Nocera2016-06-091-1/+4
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=767399
* udisks2: Fix "format not a string literal" warningsBastien Nocera2016-06-091-9/+8
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=767349
* monitor: Add g_drive_is_removable() supportOndrej Holy2016-05-203-3/+43
| | | | | | | | | | | | | | | Nautilus wants to show entries in the sidebar only for removable devices. It uses currently sort of conditions to determine which devices should be shown. Those condition fails in some cases unfortunatelly. Lets provide g_drive_is_removable() which uses udisks Removable property to determine which devices should be shown. It should return true for all drives with removable media, or flash media, or drives on usb and firewire buses. Add support for this property also in gvfs-mount tool. Bump GLib version accordingly. https://bugzilla.gnome.org/show_bug.cgi?id=765457
* udisks2: Fix wrong types to avoid warningsOndrej Holy2016-04-292-2/+2
| | | | | | | Commit beea21e introduced incompatible-pointer-types warnings, because incompatible types was used. Fix the wrong types to avoid such warnings. https://bugzilla.gnome.org/show_bug.cgi?id=763890
* udisks2: Fix crash when mounting encrypted volumeOndrej Holy2016-04-181-1/+2
| | | | | | | | | | | | | Code handling external unlocks during mount operation was added by the commit beea21e recently. Unfortunately, it may cause crashes due to accessing already freed memory, because gvfs_udisks2_volume_monitor_update waits for pending dbus messages using udisks_client_settle, thus another main context iteration may happen (i.e. mount operation may finish and mount data may be freed) before accessing mount data pointer. The mount data pointer has to be obtained after gvfs_udisks2_volume_monitor_update call in order to fix this crashes. https://bugzilla.gnome.org/show_bug.cgi?id=765146
* udisks2: Abort mount operation if volume is unlockedOndrej Holy2016-04-061-25/+80
| | | | | | | | | | | | Mount operation for encrypted volumes consists from two udisks2 calls (unlock and mount). Volume monitor is able to mount already unlocked volumes. However password prompt doesn't disappear if the volume is unlocked externally and any reaction causes mount operation failure. The volume may be unlocked externally by e.g. project Tang, see https://github.com/latchset/tang for more details. Abort mount operation and continue with mounting in such situations. https://bugzilla.gnome.org/show_bug.cgi?id=763890
* udisks2: Lock unlocked volumes on eject/stopOndrej Holy2016-04-061-56/+160
| | | | | | | | | | The eject/stop operation fails currently with "Cannot eject drive in use: Encrypted device /dev/sdb1 is unlocked" if any volume is unlocked and isn't mounted. The volume monitor is able to mount already unlocked volumes, so it should be able to eject unlocked volumes also. Lock the unlocked volumes if there are any before eject/stop operation. https://bugzilla.gnome.org/show_bug.cgi?id=763890
* afc: Add debug info when house arrest fails to startBastien Nocera2016-03-191-0/+1
| | | | | | As can happen with some iOS and libplist combinations. https://bugzilla.gnome.org/show_bug.cgi?id=749639
* afc: Don't mount the default AFC serviceBastien Nocera2016-03-191-8/+2
| | | | | | | | | | | | | There's no interesting data for users in afc:/// so it's best to show iDevices through MTP instead. The only reason we'd want to use this mount is if we had support for accessing the iTunes database. Unfortunately, this database needs to be encrypted, and we don't know how to encrypt it. Even then, we would probably want the default AFC service to be hidden so only applications access it, and not users. https://bugzilla.gnome.org/show_bug.cgi?id=749639
* gphoto2: Show iDevices through MTPBastien Nocera2016-03-191-9/+0
| | | | | | | There's no interesting data for users in afc:/// so it's best to show iDevices through MTP instead. Stop hiding iDevices through the MTP. https://bugzilla.gnome.org/show_bug.cgi?id=749639
* udisks2: Send unmount notification only once when stoppingOndrej Holy2016-02-291-1/+2
| | | | | | | | | | Unmount notification is sent for each volume when stopping drive, which is wrong. It may lead to data loss, because user may unplug the device after the first notification, before the device is really stopped. It should be handled similary as an eject operation and send the notification only once for the drive. https://bugzilla.gnome.org/show_bug.cgi?id=760523
* udisks2: Avoid crashes during unmountOndrej Holy2016-02-151-1/+1
| | | | | | | | | Commit c014b64 was pushed to prevent race between unmount reply and retry timer. Result of mount operation reply should be stored if unmount operation is in progress, however it isn't, because the conditional statement is always true. Fix the condition accordingly. https://bugzilla.gnome.org/show_bug.cgi?id=678555
* build: Add --with-systemduserunitdir optionYaroslav Shmelev2016-01-227-7/+14
| | | | | | | | | | | 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
View Lorry Controller Status