summaryrefslogtreecommitdiff
path: root/monitor
Commit message (Collapse)AuthorAgeFilesLines
...
* Merge branch 'mtp-backend'Philip Langdale2013-01-1111-1/+982
|\ | | | | | | | | | | | | | | | | | | This merge brings in the libmtp based backend for MTP devices. Previously, MTP devices were handled, with limited success by the GPhoto2 backend as MTP is nominally backwards compatible with PTP. The most serious limitation was that the GPhoto2 backend operated in a way that doesn't work reliably with Android 4.x based devices. This problem is rectified by the new MTP backend.
| * MTP: Review Feedback: Fix memory leaks and improve memory management.Philip Langdale2013-01-112-8/+5
| |
| * MTP: Review Feedback: Unconditional chain up finalize and dispose.Philip Langdale2013-01-112-6/+3
| |
| * MTP: Review Feedback: Fix warnings.Philip Langdale2013-01-111-2/+3
| |
| * MTP: Review Feedback: Remove use of static buffer.Philip Langdale2013-01-111-1/+3
| | | | | | | | | | Use a dynamically allocated buffer instead to avoid any multi-threading dangers.
| * MTP: Fix parentheses spacing.Philip Langdale2013-01-111-4/+4
| |
| * MTP: Fix review comments.Philip Langdale2013-01-111-10/+7
| |
| * MTP: Clean up formatting and style for MTP Volume Monitor.Philip Langdale2013-01-113-167/+141
| | | | | | | | We can consider the volume monitor done at this point.
| * MTP: Put conditional test in gphoto2 monitor for libmtp.Philip Langdale2013-01-111-1/+3
| |
| * MTP: Add conditional configuration against libmtp.Philip Langdale2013-01-111-1/+5
| |
| * MTP: Tidy up.Philip Langdale2013-01-115-32/+25
| |
| * MTP: Update .gitignorePhilip Langdale2013-01-111-0/+1
| |
| * MTP: Initial MTP volume monitor implementation.Philip Langdale2013-01-119-2/+1010
| |
| * MTP: Make gphoto2 monitor skip MTP devices.Philip Langdale2013-01-111-0/+5
| |
* | udisks2: don't set GDrive.can_stop to TRUE if drive has removable mediaDavid Zeuthen2012-12-111-7/+12
| | | | | | | | | | | | | | If the drive is using removable media, we want the shell and file manager to eject the media, not turn the drive off. Signed-off-by: David Zeuthen <zeuthen@gmail.com>
* | If a drive is hotplugged and CanPowerOff is TRUE, set can_stop to TRUEDavid Zeuthen2012-12-114-8/+197
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With this change, USB-connected drives that appear *during* the user session will now be powered off when the user clicks the "Eject" icon in the GUI. This involves powering off the USB port typically resulting in LEDs and other user-visible features turning off. In particular, bus-powered HDDs will completely turn off by virtue of being, well, bus-powered. This is generally what users expect and should make them feel all cozy, warm inside and, most importantly, more confident removing the device now that the LED is off. Or something. Since we only do this for devices detected *during* the user session, we should not run into problems with internal USB devices such as laptop SD card readers or the various 4-in-1 flash card readers in many workstations. This is actually important because removing the power to the USB port of an "internal" device is generally a bad idea as it requires a system restart to make the laptop BIOS power the port up again (or the user to crack open the chassis). (No, unfortunately there is no *reliable* way to determine if a USB device is "internal" (e.g. reachable and/or servicable by the user) or not. There are a couple of mechanisms - one is to look at various USB device descriptors - but none of them seem very reliable. So instead we simply look at whether the device is hotplugged.) See also this udisks commit http://cgit.freedesktop.org/udisks/commit/?id=81dcb6eeaeceb6c6faae1a40a5b34a65cd5af653 introducing the Drive:CanPowerOff property and the Drive.PowerOff() method. Signed-off-by: David Zeuthen <zeuthen@gmail.com>
* | udisks2: Initialize local variables to NULLTomas Bzatek2012-12-111-6/+6
| | | | | | | | | | | | | | We need to set initial value to local variables we're about to use later in the code. Found the volume monitor segfaulting on stable udisks-2.0.0
* | proxy volume monitor: Remove unnecessary gotoTomas Bzatek2012-12-101-9/+2
| | | | | | | | | | A matter of developer's taste, but since the function has been simplified a lot, no need to keep the goto around.
* | proxy volume monitor: Don't leak the_volume_monitors hash tableTomas Bzatek2012-12-101-1/+2
| | | | | | | | | | | | | | | | | | The the_volume_monitors hash table is a shared global instance, make sure to only initialize it once. Based on a patch by Tim Lunn <tim@feathertop.org> https://bugzilla.gnome.org/show_bug.cgi?id=689946
* | proxy volume monitor: Clarify when mutex is hold on constructionTomas Bzatek2012-12-101-0/+1
| | | | | | | | | | | | Found by reviewing usage of the global lock, this place is not obvious whether is inside the lock or not. Let's add a simple comment to make it clear.
* | udisks2: add support for mount option x-gvfs-symbolic-iconDavid Zeuthen2012-12-052-8/+29
| | | | | | | | | | | | | | ... and also the new Block:HintSymbolicIcon icon just added to udisks master. Signed-off-by: David Zeuthen <zeuthen@gmail.com>
* | udisks2: get icons via UDisksObjectInfo for block devices that are not drivesDavid Zeuthen2012-12-051-0/+21
| | | | | | | | Signed-off-by: David Zeuthen <zeuthen@gmail.com>
* | udisks2: don't leak GIcon when applying hintsDavid Zeuthen2012-12-051-0/+1
| | | | | | Signed-off-by: David Zeuthen <zeuthen@gmail.com>
* | udisks2: fix symbolic icons for devices without an UDisksDriveDavid Zeuthen2012-11-284-2/+22
| | | | | | | | | | | | | | We were returning folder-remote-symbolic which is incorrect since that should only be used for network filesystems. Signed-off-by: David Zeuthen <zeuthen@gmail.com>
* | Use UDisksObjectInfo API from udisks 2.0.90, if available, for symbolic iconsDavid Zeuthen2012-11-203-32/+167
| | | | | | | | | | | | | | | | | | | | | | | | Without this fix volumes would fall back to folder-remote-symbolic which is obviosly wrong. With this fix, it looks correct, see http://people.freedesktop.org/~david/gvfs-udisks2-symbolic-icons.png Right now we only use the API if it's available - things still work with udisks >= 1.97. Signed-off-by: David Zeuthen <zeuthen@gmail.com>
* | proxy volume monitor: Get session bus on demandTomas Bzatek2012-11-013-37/+16
| | | | | | | | | | | | | | | | | | | | | | Do not connect to session bus at module load, let proxies to get a bus when needed. No need to keep it active all the time. Proxies will return an error when a bus is unavailable. Also don't close the shared d-bus connection on module unload, let it be managed by proxies. https://bugzilla.gnome.org/show_bug.cgi?id=687074
* | proxy volume monitor: Don't disable exit_on_close on session busTomas Bzatek2012-11-011-1/+0
| | | | | | | | | | | | | | We're on shared session bus, let's exit when connection closes (usually tied to running desktop session). https://bugzilla.gnome.org/show_bug.cgi?id=687074
* | Remove calls to g_type_init(), bump GLib required versionColin Walters2012-10-301-2/+0
| | | | | | | | | | | | See http://git.gnome.org/browse/glib/commit/?id=2002479c02fa6e468fc3f67ddc663657a52ebde8 https://bugzilla.gnome.org/show_bug.cgi?id=687236
* | Allow specifying the dir for .monitor filesAlexander Larsson2012-10-121-3/+8
| | | | | | | | This will also be used for the test suite
* | udisks2: Add appropriate content type for media playersMartin Pitt2012-10-041-1/+6
| | | | | | | | | | | | | | | | If a device has an ID_MEDIA_PLAYER udev property, add the x-content/audio-player content type so that gvfs clients like nautilus offer opening an audio player instead of a file browser. https://bugzilla.gnome.org/show_bug.cgi?id=619583
* | proxy: don't emit connected/added signals at object creationCosimo Cecchi2012-09-251-1/+7
|/ | | | | | | | It's unnecessary to emit those signals when the object is created, and it can cause weird side-effects if applications e.g. play a sound on signal emission. https://bugzilla.gnome.org/show_bug.cgi?id=684677
* gdu volume monitor: Don't unref possibly NULL objectTomas Bzatek2012-09-141-1/+1
|
* gdu volume monitor: Handle gdu_pool_new() returning NULL gracefullyMichael Terry2012-09-141-21/+34
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=582579
* hal: Bring gvfsdbusutils.c back and make it privateTomas Bzatek2012-09-143-0/+583
| | | | | | | | | | ... in order to be able to compile. gvfsdbusutils.c was removed by commit 288e9153f1f though hal still needs it for compilation. Let's make it private to hal and strip unnecessary functions. https://bugzilla.gnome.org/show_bug.cgi?id=683367
* proxydrive: Use proper object castingTomas Bzatek2012-09-071-8/+8
| | | | | | Just a little cleanup to be on a safe side. https://bugzilla.gnome.org/show_bug.cgi?id=683191
* monitor: Unused variables cleanupTomas Bzatek2012-08-302-10/+1
|
* Add support for getting symbolic iconsWilliam Jon McCann2012-08-307-21/+162
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=681458
* Remove unused code from client libsAlexander Larsson2012-08-213-0/+3
| | | | | | | | The gvfsmountinfo.c (and its libbluray dependency) is unused by the client code, so we remove it from the common shared lib. We use a non-shared lib for this, as in practice only one of the monitors that use this code will be build/installed/used.
* mount-op: adapt to guint64->gint64 API changeCosimo Cecchi2012-08-215-14/+14
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=682284
* Port to libsecret instead of libgnome-keyringAlexander Larsson2012-08-201-45/+55
| | | | | | Based on an initial port by Stef Walter https://bugzilla.gnome.org/show_bug.cgi?id=679854
* udisks2: Remove UDISKS_CHECK_VERSION ifdefs since we require 1.97 nowTomas Bzatek2012-07-312-10/+2
|
* Spelling correction "filesystem" -> "file system"Felix Möller2012-07-311-1/+1
| | | | | | | Unify the spelling. For the discussion see: https://bugzilla.gnome.org/show_bug.cgi?id=520902 Signed-off-by: Tomas Bzatek <tbzatek@redhat.com>
* Update the Address of the FSFFelix Möller2012-07-3062-124/+124
| | | | | | | | | | | | | | | Updating the address of the FSF. This has been done by: while read file; do sed -i 's:59 Temple Place:51 Franklin Street:' $file sed -i 's:Suite 330:Fifth Floor:' $file sed -i 's:02111-1307:02110-1301:' $file done https://bugzilla.gnome.org/show_bug.cgi?id=656598 Signed-off-by: Tomas Bzatek <tbzatek@redhat.com>
* proxyvolumemonitor: Use GDBusProxy's name owner change notificationTomas Bzatek2012-07-301-25/+38
| | | | | | | | | | | Some GVolumeMonitor users don't run mainloop thus we're not able to do any async I/O. Using GDBusProxy name owner monitoring should get us the same functionality as separate g_bus_watch_name() call with the benefit of not doing any async I/O in GProxyVolumeMonitor constructor. This way we could populate volume monitor objects during initialization. https://bugzilla.gnome.org/show_bug.cgi?id=679821
* udisks2: ensure that encrypted loop devices also get padlock emblemDavid Zeuthen2012-07-261-1/+5
| | | | Signed-off-by: David Zeuthen <zeuthen@gmail.com>
* udisks2: set should_automount to TRUE for loop devices set up by the userDavid Zeuthen2012-07-261-0/+44
| | | | | | | Also set the Autoclear property after successfully mounting/unlocking devices on a loop device. Signed-off-by: David Zeuthen <zeuthen@gmail.com>
* udisks2: move up loop device validation checksDavid Zeuthen2012-07-261-33/+33
| | | | | | We also want these checks to apply to e.g. LUKS devices. Signed-off-by: David Zeuthen <zeuthen@gmail.com>
* udisks2: don't use object after unrefDavid Zeuthen2012-07-261-2/+2
| | | | | | | | Technically there's no problem here since UDisksClient still has a reference but it's pretty confusing. Fix it up by using g_clear_object(). Signed-off-by: David Zeuthen <zeuthen@gmail.com>
* udisks2: work around Linux bug for lingering partitions of cleared loop deviceDavid Zeuthen2012-07-261-1/+18
| | | | Signed-off-by: David Zeuthen <zeuthen@gmail.com>
* gdbus: Construct proxies without connecting signals and propertiesTomas Bzatek2012-07-201-2/+2
| | | | | Use G_DBUS_PROXY_FLAGS_DO_NOT_CONNECT_SIGNALS and G_DBUS_PROXY_FLAGS_DO_NOT_LOAD_PROPERTIES flags where applicable.
View Lorry Controller Status