summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* gdbus: gmountoperationdbus.c: Move referenced objects aroundTomas Bzatek2012-07-311-24/+26
| | | | | Reorganize saved references for used objects, getting rid of some FIXMEs.
* gdbus: Construct proxies without connecting signals and propertiesTomas Bzatek2012-07-317-8/+8
| | | | | Use G_DBUS_PROXY_FLAGS_DO_NOT_CONNECT_SIGNALS and G_DBUS_PROXY_FLAGS_DO_NOT_LOAD_PROPERTIES flags where applicable.
* gdbus: Use G_VARIANT_TYPE_HANDLE for fd_id argumentsTomas Bzatek2012-07-315-12/+43
|
* gdbus: Move annotations to the interface XML fileTomas Bzatek2012-07-312-6/+3
|
* gdbus: Fix srcdir != builddir and make the build more quietTomas Bzatek2012-07-314-4/+7
|
* gdbus: Push new GVfsJobProgress classTomas Bzatek2012-07-312-0/+172
| | | | Forgotten from the 722ebaf0ab949ca5b844a387dc684b4e3185db75 commit
* gdbus: Remove unused extra_fd stuffTomas Bzatek2012-07-312-197/+15
|
* gdbus: Use private GMainContext for sync enumeratorTomas Bzatek2012-07-313-22/+40
| | | | | | 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.
* gdbus: Make copy progress workTomas Bzatek2012-07-3111-441/+226
| | | | | | | ...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.
* gdbus: Fix mount tracker signals emittingTomas Bzatek2012-07-311-41/+5
| | | | This allows clients to react on GVfs mounts appearing and disappearing.
* gdbus: Fix mountable mounting with URITomas Bzatek2012-07-311-1/+1
|
* gdbus: More signal handler disconnectionTomas Bzatek2012-07-311-0/+1
| | | | Not really a problem in this case, but let's be on a safe side.
* gdbus: Properly disconnect signal handlersTomas Bzatek2012-07-311-0/+1
| | | | ...not doing that leads to accessing freed memory
* gdbus: Make cancellation workTomas Bzatek2012-07-318-30/+330
| | | | | | This mimics the old behaviour and works for sync and async. Requires new glib for g_dbus_connection_get_last_serial().
* gdbus: Fixup d-bus interface naming styleTomas Bzatek2012-07-311-18/+18
| | | | And conform to usual GNOME naming conventions.
* gdbus: Treat empty non-NULL strings for the "ay" type as NULLTomas Bzatek2012-07-315-6/+13
| | | | | | | | | | 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.
* gdbus: Remove last traces of libdbus in metadata sourcesTomas Bzatek2012-07-313-5/+1
|
* gdbus: Remove no longer valid commentTomas Bzatek2012-07-311-2/+0
|
* gdbus: Enable daemon finalizationTomas Bzatek2012-07-311-3/+1
| | | | | | The crasher may have been possibly fixed in bug 669211. It's hard to hit the code path as long as gvfsdaemon calls hard exit().
* gdbus: Silence unmount failuresTomas Bzatek2012-07-312-10/+7
| | | | | | | | | | ...and fix wrong typecast due to using an object we haven't reff'ed. The failure we're making silent were coming from a failed d-bus call to mount tracker. Also turned out the org.gtk.vfs.MountTracker.unregisterMount() has never been implemented, daemon mounttracker is watching for clients disconnects anyway.
* gdbus: Tweak mount finalizationTomas Bzatek2012-07-313-6/+30
|
* gdbus: Handle not yet spawned mountablesTomas Bzatek2012-07-311-14/+9
| | | | This makes http backend working again.
* gdbus: Remove unused daemon protocol definesTomas Bzatek2012-07-311-106/+0
|
* gdbus: Remove unused includeTomas Bzatek2012-07-311-1/+0
| | | | So that nothing depends on gvfsdbusutils.h, which is full of old libdbus code.
* gdbus: Port the fuse daemonTomas Bzatek2012-07-311-69/+84
|
* gdbus: Port the sftp backendTomas Bzatek2012-07-311-56/+54
| | | | Traces of gnome-keyring GetEnvironment() call.
* gdbus: Port the OpenIconForRead operationTomas Bzatek2012-07-318-285/+225
|
* gdbus: Bring libdbus threads initialization backTomas Bzatek2012-07-311-0/+8
| | | | | | | | I hate reverting things but this seems to be required for proper libdbus threads initialization, further used by gnome-keyring. This has actually been fixed in gnome-keyring recently (bug 659162) but gvfs can still be used with gnome-keyring-2.32.
* gdbus: Handle client connection dying during monitoringTomas Bzatek2012-07-311-11/+21
| | | | Handle a connection dying and unregister its subscription.
* gdbus: Monitoring portTomas Bzatek2012-07-313-214/+398
|
* gdbus: Improve registered paths activation on daemon sideTomas Bzatek2012-07-313-35/+67
| | | | | | | | | | | | | | | | | This changes the way registered paths (i.e. interface skeleton exports) are activated on daemon side. We're keeping a list of connections on which every registered path is exported so that if connection is closed or the path is unregistered we always free the right interface skeletons. We also keep track of active client (peer-to-peer) connections so that if a new path is registered, it's automatically exported to all active connections. Needed since client connections are usually shared. It also has a nice side-effect of reacting to dirty disconnects (e.g. the client dies). This whole registration machinery needs unique object paths (for the hash table) but that's not a problem in the current state.
* gdbus: Handle NULL mount_info in create_proxy_for_file2()Tomas Bzatek2012-07-311-1/+2
|
* gdbus: Fix mismerged structTomas Bzatek2012-07-311-2/+3
|
* gdbus: Core daemon and client portTomas Bzatek2012-07-3181-6720/+6519
| | | | | | | | | | | 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
* udisks2: Remove UDISKS_CHECK_VERSION ifdefs since we require 1.97 nowTomas Bzatek2012-07-312-10/+2
|
* build: Update udisks2 requirement to version 1.97Chris Kühl2012-07-311-1/+1
| | | | | | | | | | | | The use of udisks_loop_get_setup_by_uid, udisks_client_get_loop_for_block, udisks_loop_get_autoclear, udisks_loop_get_setup_by_uid, & udisks_loop_call_set_autoclear in gvfsudisks2volume.c cause the build to fail without a udisks2 version >= 1.97. https://bugzilla.gnome.org/show_bug.cgi?id=680863 Signed-off-by: Tomas Bzatek <tbzatek@redhat.com>
* Spelling correction "filesystem" -> "file system"Felix Möller2012-07-317-7/+7
| | | | | | | Unify the spelling. For the discussion see: https://bugzilla.gnome.org/show_bug.cgi?id=520902 Signed-off-by: Tomas Bzatek <tbzatek@redhat.com>
* Rename gvfs-fuse-daemon to gvfsd-fuseTomas Bzatek2012-07-302-5/+5
| | | | | | ...to stay consistent with the rest of the daemons. https://bugzilla.gnome.org/show_bug.cgi?id=680819
* Update the Address of the FSFFelix Möller2012-07-30304-611/+611
| | | | | | | | | | | | | | | 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>
* afc: Use consistent debug env varMatthias Clasen2012-07-301-1/+1
| | | | | | | | | All the other backend-specific env vars to trigger debugging spew are named GVFS_<foo>_DEBUG. Make afc follow this pattern, too. https://bugzilla.gnome.org/show_bug.cgi?id=680733 Signed-off-by: Tomas Bzatek <tbzatek@redhat.com>
* computer: Mark items as not renamableMarcus Carlson2012-07-301-0/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=617056
* 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
* Updated Galician translationsFran Diéguez2012-07-301-78/+89
|
* Updated Norwegian Nynorsk translationÅsmund Skjæveland2012-07-291-179/+169
|
* Fix a comment typoMatthias Clasen2012-07-281-1/+1
|
* 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>
View Lorry Controller Status