| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=686637
|
|
|
|
|
|
|
| |
We should *not* disable exit on close for the shared
session bus connection, this means that apps won't
properly exit with the session!
(cherry picked from commit baa03b1333cf83cbb9618e0bebd8038df8cc50b2)
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=685248
|
|
|
|
|
|
|
| |
This makes cancel much cleaner and solves a problem
where we were trying to use a previously disposed proxy.
https://bugzilla.gnome.org/show_bug.cgi?id=683985
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=683770
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=682878
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=681458
|
|
|
|
|
|
| |
This happens in jhbuild.
https://bugzilla.gnome.org/show_bug.cgi?id=682885
|
| |
|
|
|
|
| |
Don't link to libdbus and remove libdbus utility functions.
|
| |
|
|
|
|
|
|
| |
The mount may be already gone or monitoring cleanup is done too late;
in that case handle this case gracefully since the monitoring doesn't
exist anymore.
|
|
|
|
|
| |
This is a valid error used to indicate that we should (auto)mount first
and should not be presented to the user.
|
|
|
|
|
| |
Found out that if the remote call fails, some variables are left
uninitialized and causes assertion failures while we don't need them.
|
| |
|
|
|
|
|
|
| |
This hopefully covers all public methods.
Seems like this fixes several memleaks as well.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Use G_DBUS_PROXY_FLAGS_DO_NOT_CONNECT_SIGNALS and G_DBUS_PROXY_FLAGS_DO_NOT_LOAD_PROPERTIES
flags where applicable.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
It's little messy due to shared code across sync calls with private
main context and async calls that don't have it's mainloop and can't use
private context.
|
|
|
|
|
|
|
| |
...by turning sync copy calls async and running mainloop for progress
interface skeleton be able to process incoming calls.
Also, new class GVfsJobProgress has been introduced mostly for code sharing.
|
|
|
|
|
|
| |
This mimics the old behaviour and works for sync and async.
Requires new glib for g_dbus_connection_get_last_serial().
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
So that nothing depends on gvfsdbusutils.h, which is full of old libdbus code.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
...to stay consistent with the rest of the daemons.
https://bugzilla.gnome.org/show_bug.cgi?id=680819
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
Use G_DBUS_PROXY_FLAGS_DO_NOT_CONNECT_SIGNALS and G_DBUS_PROXY_FLAGS_DO_NOT_LOAD_PROPERTIES
flags where applicable.
|
|
|
|
|
|
|
|
| |
Don't allocate whole padding block, write in smaller pieces instead.
As an bonus, check for block write result and break if error occurred,
passing it further up.
Found by David Zeuthen.
|
|
|
|
|
|
|
|
|
|
| |
When ftruncate is called with a size greater than the current size
of the file, the expected behavior is that the file size increases to
the requested size, and the new space is zero-filled. SQLite depends
on this behavior when opening a database using 'write-ahead log'
journaling.
Based on original patch by Jeff Smith <whydoubt@yahoo.com>
|
|
|
|
|
|
|
|
|
| |
When GDBusProxy is constructed for a well-known name, it tracks the name
owner itself and no recreation when it changes is necessary. When name owner
is lost, an autostart attempt is made on a next call.
This patch removes name watching completely but retains metadata proxy creation
on a first use.
|
| |
|
|
|
|
|
|
|
|
| |
This is a complete port of volume monitors and metadata to GDBus.
The (private) d-bus API has been mostly preserved except of
MountOp methods.
No difference in functionality should be observed.
|
|
|
|
|
|
|
|
| |
If runtime dir is not specifically set we don't fall back to
~/.cache/gvfs, as that unnecessarily invalidates all existing
documentation and scripts using ~/.gvfs.
However, if it is set, we still use it.
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=646391
Signed-off-by: Tomas Bzatek <tbzatek@redhat.com>
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=583927
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Last piece in order to fix https://bugzilla.gnome.org/show_bug.cgi?id=661148
|
|
|
|
| |
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
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=659815
|
|
|
|
|
| |
GLib recently became less forgiving about single includes
like this.
|