| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
Deduplicate code between gphoto2 and mtp by creating a convenience
library call libgvfscommon-gphoto2 which is only built if either libmtp
is used or gphoto2 with gudev is used.
https://bugzilla.gnome.org/show_bug.cgi?id=736285
|
| |
|
|
|
|
|
|
|
| |
From release 147, the gudev API was marked as stable, so require that
version.
https://bugzilla.gnome.org/show_bug.cgi?id=722354
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=676187
|
| |
|
|
|
|
|
|
|
|
| |
When g_bus_unwatch_name () is called, it frees the associated Client and
so the name variable becomes invalid. So, ensure that nothing uses the
name variable after this call.
https://bugzilla.gnome.org/show_bug.cgi?id=710679
|
|
|
|
|
|
|
|
| |
The places sidebar in nautilus and the places menu in the shell
use symbolic icons exclusively, so make sure one is provided, to
avoid falling back to a generic "network mount" icon.
https://bugzilla.gnome.org/show_bug.cgi?id=723251
|
|
|
|
|
|
|
| |
Replace _ and - with spaces, and apply that pass on
the product string too.
https://bugzilla.gnome.org/show_bug.cgi?id=723251
|
|
|
|
|
|
| |
Make the buffer really static, as the comment above documents.
https://bugzilla.gnome.org/show_bug.cgi?id=723251
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=721510
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=712382
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=712382
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=712382
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that dbus-activated session services have their stdout/stderr
connected to the systemd journal (as of recent dbus), these debug
messages now show up by default.
The #define DEBUG_ENABLED was apparently turned on by accident in
commit 8315eaf84e52c6a00a4905f1f6a73182db9e8015 - we can just turn it
off again.
(Why is this not just g_debug()? Who knows...)
https://bugzilla.gnome.org/show_bug.cgi?id=711365
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=591228
|
|
|
|
|
| |
https://bugzilla.redhat.com/show_bug.cgi?id=951731
https://bugzilla.gnome.org/show_bug.cgi?id=702577
|
|
|
|
| |
https://bugzilla.redhat.com/show_bug.cgi?id=951731
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
Mount
Some volume monitors, like gnome-online-accounts, want their
mount implementation to be called even though the volume has an
activation root. Allow them to advertise so using the expansion
fields of the volume DBus representation.
https://bugzilla.gnome.org/show_bug.cgi?id=696279
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=695834
|
|
|
|
|
|
|
|
|
|
| |
New udev/blkid expose more ISO9660 properties, including 'Boot System
ID'. Existance of this property implies that media is bootable. The
libosinfo udev rules that provided the 'OSINFO_BOOTABLE' property will
soon be ditched as a result but we better keep the check for backward
compatibility.
https://bugzilla.gnome.org/show_bug.cgi?id=694007
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=686526
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Use a dynamically allocated buffer instead to avoid any
multi-threading dangers.
|
| | |
|
| | |
|
| |
| |
| |
| | |
We can consider the volume monitor done at this point.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| | |
A matter of developer's taste, but since the function has been simplified
a lot, no need to keep the goto around.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| | |
... and also the new Block:HintSymbolicIcon icon just added to udisks
master.
Signed-off-by: David Zeuthen <zeuthen@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: David Zeuthen <zeuthen@gmail.com>
|
| |
| |
| | |
Signed-off-by: David Zeuthen <zeuthen@gmail.com>
|
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|