Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
...so that they are recognizable on a first sight.
|
|
and kill the iters.
|
|
Reorganize saved references for used objects, getting rid of
some FIXMEs.
|
|
Use G_DBUS_PROXY_FLAGS_DO_NOT_CONNECT_SIGNALS and G_DBUS_PROXY_FLAGS_DO_NOT_LOAD_PROPERTIES
flags where applicable.
|
|
|
|
|
|
|
|
And conform to usual GNOME naming conventions.
|
|
A fallout of port away from convenient G_DBUS_TYPE_CSTRING type and
_g_dbus_message_append_args() + _g_dbus_message_iter_get_args() functions
that masked NULL strings as non-NULL empty strings ("") for transferring
over d-bus and on the other side reconstructed the original value.
Portions of other code treat non-NULL strings differently even if they
were empty. This fixes e.g. opening http URLs via gvfs-open.
|
|
|
|
|
|
|
|
Port of most of the gvfs core, few bits still missing. Lot of debug prints around,
will be removed in further commits. Same amount of TODOs and FIXMEs.
Notes:
* kill serials?
* get rid of mainloops where applicable (copy/move progress callback, enumerator)
* fix keyring integration
* use gdbus builtin fd passing within gvfsdaemon.c, kill the extra_fd stuff
|
|
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>
|
|
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=676111
|
|
Turned out zeroing memory is not enough in some cases so let's be
on the safe side and properly initialize all non-static mutexes.
Also, don't initialize/clear the static ones.
|
|
A continuation to https://bugzilla.gnome.org/show_bug.cgi?id=661148
|
|
GStaticMutex and GStaticRWLock have been replaced by GMutex
and GRWLock, and g_thread_init() is no longer needed.
https://bugzilla.gnome.org/show_bug.cgi?id=661148
|
|
Especially now that deprecations are proper gcc warnings, no need
to hardcode this.
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=656511
|
|
|
|
g_mount_info_apply_prefix will take an given path and prepend the
mount_prefix of the given mount_info, if there is any. It will free the old
string in this case. Otherwise it is a NOOP.
|
|
Turns out the header is properly shipped by libluray.
|
|
This means we can finally get localised versions, and
support the biggest thumbnails.
https://bugzilla.gnome.org/show_bug.cgi?id=646984
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=641856
|
|
The wrong iterator passed in caused some items to be silently dropped
plus it led to string dup of wrong pointer.
See bug 614544 for reference.
|
|
This makes gvfs build with recent glib again, see bug #619537
|
|
Sometimes we may get unexpected data from dbus which was leading
to an endless loop.
See bug 614544 for reference.
|
|
The "default location" of the given mount is a path that reflects
the main entry point for the user (e.g. the home directory, or the
root of the volume).
Backends can use g_vfs_backend_set_default_location () to set the
default location (before registering the mount).
https://bugzilla.gnome.org/show_bug.cgi?id=561998
|
|
Using the BDMV/META/DL/bdmt_eng.xml file on BDMV discs,
we can load better names and icons for the disc.
Adds expat requirement to the common library if it is found.
https://bugzilla.gnome.org/show_bug.cgi?id=600887
|
|
Don't consume the ending character.
|
|
This leak was pointed out by clang, and reported in bug 594832.
|
|
When the host has already been resolved and is present in cache,
it's returned immediately. But we always started a mainloop
resulting in endless waiting for an event which had been received
before that. This applies for the sync call.
This is just a workaround, the sync code should be ported over avahi.
See bug 555436 (comments 30-32) for details.
|
|
This prevents mismatches during mount spec comparation, e.g. with
trailing slash in mount_prefix ("/subdir" vs. "/subdir/").
See bug 590730 for details.
|
|
- Port everything to use _with_operation() variants of unmount/eject
methods
- Add support for g_file_poll_mountable()
- new job class: GVfsJobPollMountable
- Pass mount operation for unmount/eject ops on GDaemonFile and
GDaemonMount
- receive in the appropriate GVfsJob classes
- also pass unmount flags where it was missing
- port all backends to use this
- Teach GMountSource and GMountOperationDBus about the new
GMountOperation::show-processes signal
- also provide new API
- g_mount_source_is_dummy() - e.g. when the client didn't
passed NULL for the GMountOperation
- g_mount_source_abort() - to send the ::abort signal to the
client-side GMountOperation
- make the client-side of GMountSource return ::reply with
NOT_HANDLED when we do an abort
- Refactor the mount operation handling in GProxyVolumeMonitor
- Pass mount operation for unmount/ejects in GProxyVolumeMonitor
- Pass the process id of the actual reader/writer in OpenForRead
and OpenForWrite daemon methods
- add some private API for making the FUSE client set the
pid of the POSIX client (otherwise it looks like the FUSE
client is blocking) and pass the right pid.
This is because the FUSE client is basically impersonating the
POSIX processes.
- Make the process id mentioned above available in appropriate
GVfsJob classes
- GVfsJobOpenForRead
- GVfsJobOpenForWrite
- GVfsChannel
- Provide API to get a list of all blocking clients, e.g. an array
of GPid
- g_vfs_daemon_get_blocking_processes()
- Provide convenience API to easily doing the right thing on unmount;
e.g. interact with the user about blocking processes - see the gphoto2
backend for example usage
- g_vfs_backend_has_blocking_processes()
- g_vfs_backend_unmount_with_operation() and
g_vfs_backend_unmount_with_operation_finish()
- Only the gphoto2 backend supports ::show-processes right now. Support
for other backends will be added shortly.
- Implement support for ::show-processes in the GDU volume monitor
- right now we don't support "Unmount Anyway" since it requires
ABI changes in libgdu.so - this will be changed as soon as there's
a new gnome-disk-utility release
|
|
|
|
|
|
We'll be showing this of publically as the id of metadata databases, so
it better be somewhat shorter and nicer.
|
|
|
|
|
|
|
|
This daemon singleton handles updates to metadata stores.
All clients that wishes to write metadata should talk to
it via dbus.
This way all writes are serialized to avoid data loss on
concurrent writes.
|