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

https://bugzilla.gnome.org/show_bug.cgi?id=682284

Felix Möller authored Jul 30, 2012 and Tomáš Bžatek committed Jul 30, 2012

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>

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

Use G_DBUS_PROXY_FLAGS_DO_NOT_CONNECT_SIGNALS and G_DBUS_PROXY_FLAGS_DO_NOT_LOAD_PROPERTIES
flags where applicable.

https://bugzilla.gnome.org/show_bug.cgi?id=676111

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.

This is detailed in this bug

 https://bugzilla.gnome.org/show_bug.cgi?id=661711



Also extend the private D-Bus protocol used between the client- and
service-side for out-of-process volume monitors. In particular,
introduce a new a{sv} member that we can use in the future to for
expansion without breaking ABI.
Signed-off-by: David Zeuthen <davidz@redhat.com>

Once constructed, it's a) more efficient; and b) simplifies the code;
if we keep the proxy for a remote volume monitor process around.

More importantly, this change sidesteps some thorny bugs in the
current implementation where the remote volume monitor proxy has been
disposed but not yet finalized - for some volume monitors, this can
happen not only pathological situations but also when running
e.g. gvfs-mount(1) to mount a volume.

https://bugzilla.gnome.org/show_bug.cgi?id=660295

Signed-off-by: David Zeuthen <davidz@redhat.com>

Found by Coverity Scan analysis

This makes gvfs build with recent glib again, see bug #619537

David Zeuthen authored Jun 30, 2009 and Alexander Larsson committed Jul 08, 2009

- 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

This is the GVfs implementation for the new GIO API for
starting/stopping drives. See

http://bugzilla.gnome.org/show_bug.cgi?id=585591

for details.

2009-03-26  Carlos Garnacho  <carlosg@gnome.org>

        Bug 576083 – pre-unmount signals not being triggered

        * monitor/hal/ghalmount.c (unmount_do) (unmount_do_cb): Emit
        ::mount-pre-unmount and wait 500msec before actually trying to
        unmount.
        * monitor/proxy/gproxyshadowmount.c (real_mount_pre_unmount_cb): Proxy
        the shadowed mount pre-unmount signal.
        * monitor/proxy/gproxyvolumemonitor.c (filter_function): GMount
        doesn't have the ::pre-unmount signal yet, so don't emit it.

svn path=/trunk/; revision=2350

2009-03-17  Alexander Larsson  <alexl@redhat.com>

        Bug 575552 – icons for audio cds duplicated on the desktop after remounts

        * monitor/proxy/gproxyvolumemonitor.c:
	Dispose volumes when removed

        * monitor/proxy/gproxyvolume.c:
	When disposed, disconnect from union volume monitor so that we don't get
	a mount_added for a later mount and create a shadow mount for that.


svn path=/trunk/; revision=2338

2009-03-04  Alexander Larsson  <alexl@redhat.com>

	* monitor/proxy/gproxyvolumemonitor.c:
	Break circular dependencies on dispose.



svn path=/trunk/; revision=2285

2009-02-26  David Zeuthen  <davidz@redhat.com>

	Lots of proxy monitor fixes.

	Reviewed by: Alexander Larsson  <alexl@redhat.com>

	o  add support for proxying GMountOperation to the remote volume
	   monitor process.

	o  add support for proxying GCancellable to the remote volume
	   monitor process.

	o  make each volume monitor process track callers and cancels
	   operations initiated by callers that disconnects from the bus

	o  makes the client side proxy monitor track the remote monitor. If
	   the monitor process disconnects, then all drives/volumes/mounts
	   are removed. If the monitor process reconnects, we reseed the
	   internal monitor and add drives/volumes/mounts.

	o  Each monitor process now uses ALLOW_REPLACEMENT when claiming a
	   name and also kills itself on NameLost (e.g. if it is
	   replaced). Coupled with the above disconnection/reconnection logic
	   it this makes it a lot more tolerable to hack on a remote volume
	   monitor. Simply just compile it, start it and the
	   existing (system-wide) copy will kill itself. And all the
	   clients (Nautilus, panel, drive applet, gvfsd-computer, etc.) will
	   reconnect and do the right thing.

	o  make the get_mount_for_mount_path() method on the class
	   GNativeVolumeMonitor actually work. It turns out that at least
	   gvfs-mount -u needs that.

	o  use /org/gtk/Private/RemoteVolumeMonitor instead of / as the
	   object name. Cf. the version D-Bus debacle on Lennart Poettering's
	   blog.

	o  make the proxy monitor client module resident

	o For shadow mounts, redirect can_eject() and eject() to the
	  volume for the shadow mount. Without this patch eject on
	  e.g. cdda:// volumes won't work since cdda:// volumes are
	  GDaedmonMount and these don't implement eject.

	* monitor/proxy/*.[ch]: See above.


svn path=/trunk/; revision=2253

2008-12-01  Alexander Larsson  <alexl@redhat.com>

        * client/gdaemonmount.c:
        * client/gdaemonvolumemonitor.c:
        * monitor/proxy/Makefile.am:
        * monitor/proxy/gproxydrive.c:
        * monitor/proxy/gproxymount.c:
        * monitor/proxy/gproxyvolume.c:
        * monitor/proxy/gproxyvolume.h:
        * monitor/proxy/gproxyvolumemonitor.c:
        * monitor/proxy/gproxyvolumemonitor.h:
        * monitor/proxy/remote-volume-monitor-module.c:
	* monitor/proxy/gproxyshadowmount.[ch]:
	Use the new support for shadow mounts instead
	of g_volume_monitor_adopt_orphan_mount

	Patch from David Zeuthen (#555332)
	
        * programs/gvfs-mount.c:
	Add support to monitor volume monitor events


svn path=/trunk/; revision=2119

2008-10-21  Alexander Larsson  <alexl@redhat.com>

        * configure.ac:
	Require glib 2.19.1 for GIcon serialization support
	
        * common/gvfsdaemonprotocol.c:
	Use g_icon_to_string & co instead of home-brewed serialization
	
        * monitor/proxy/gproxydrive.c:
        * monitor/proxy/gproxymount.c:
        * monitor/proxy/gproxyvolume.c:
        * monitor/proxy/gproxyvolumemonitor.c:
        * monitor/proxy/gproxyvolumemonitor.h:
        * monitor/proxy/gvfsproxyvolumemonitordaemon.c:
	Use g_icon_to_string & co instead of home-brewed serialization


svn path=/trunk/; revision=2069

2008-09-23  Alexander Larsson  <alexl@redhat.com>

        * monitor/proxy/gproxyvolumemonitor.[ch]:
        * monitor/proxy/gproxyvolumemonitor.h:
        * monitor/proxy/remote-volume-monitor-module.c:
	Only call the IsSupported dbus call when the class
	is actually needed instead of on gio init.
	Don't integrate internal session bus with mainloop
	during is_support code, as that is not necessary yet, and
	it caused problem if done in a thread.
	
	This fixes the trash crash issue in bug #547568.

2008-09-23  Alexander Larsson  <alexl@redhat.com>

        * client/Makefile.am:
        * common/Makefile.am:
        * common/gmountsource.c:
        * common/gmounttracker.c:
        * monitor/gphoto2/Makefile.am:
        * monitor/hal/Makefile.am:
        * monitor/proxy/Makefile.am:
	Link all modules against the installed libgvfscommon instead
	of duplicating the statically linked one. This is safe wrt
	namespace conflicts, because the modules are opened RTLD_LOCAL
	so the dependencies will not pollute the global namespace.

        * client/gdaemonvfs.c:
	Make the gvfsdbus module persistant. This means we will never
	unload it, and thus not unload libgvfscommon which could
	be problematic. This is not a huge problem, as:
	 + The gio modules will not be loaded anyway unless you use gio
	 + The gvfsdbus module will be persistent anyway as soon as
	   the app references the GVfs object, which likely all gio apps do
	 + The module load order doesn't matter wrt unload order, because
	   all gio modules are loaded before any one is unloaded.
	


svn path=/trunk/; revision=2021

svn path=/trunk/; revision=1858

2008-07-29  David Zeuthen  <davidz@redhat.com>

        * client/gdaemonmount.c:
        * common/gmounttracker.c:
        * common/gmounttracker.h:
        * daemon/gvfsbackend.c:
        * daemon/gvfsbackend.h:
        * daemon/gvfsbackendcdda.c:
        * daemon/gvfsbackendgphoto2.c:
        * daemon/mount.c:
        Add x-content/* support to daemon mounts. Right now a backend
        can only set the x-content/* type ahead of time. We might want
        to add support dynamically obtaining it too (e.g. support
        force_rescan).

        * monitor/hal/ghalmount.c:
        * monitor/hal/ghalvolume.c:
        * monitor/hal/ghalvolumemonitor.c:
        * monitor/hal/hal-utils.c:
        * monitor/hal/hal-utils.h:
        Add x-content/* support to the HAL volume monitor.

        * monitor/proxy/gproxymount.c:
        * monitor/proxy/gproxymount.h:
        * monitor/proxy/gproxyvolumemonitor.c:
        * monitor/proxy/gproxyvolumemonitor.h:
        * monitor/proxy/gvfsproxyvolumemonitordaemon.c:
        Add x-content/* support to proxy volume monitor. Also fix
        a number of bugs the initial implementation had.

        * programs/gvfs-mount.c:
        Print out x-content-types.


svn path=/trunk/; revision=1845

svn path=/trunk/; revision=1839

2008-07-23  David Zeuthen  <davidz@redhat.com>

	* monitor/proxy/gproxyvolumemonitor.c
	(g_proxy_volume_monitor_finalize): Fix crasher (#544399)


svn path=/trunk/; revision=1834

2008-07-21  David Zeuthen  <davidz@redhat.com>

	* monitor/proxy/gproxyvolumemonitor.c
	(g_proxy_volume_monitor_setup_session_bus_connection): Use the
	correct hash functions for the hash table of existing proxy
	volume monitors


svn path=/trunk/; revision=1826

2008-07-16  David Zeuthen  <davidz@redhat.com>

        * monitor/proxy/gproxyvolumemonitor.c:
        * monitor/proxy/gproxyvolumemonitor.h:
        * monitor/proxy/remote-volume-monitor-module.c:
        Avoid setting up proxy volume monitors if no session bus is
        available. Fixes a crasher with the Fedora NetworkManager system
        settings plug-in that is now using GIO to do file monitoring.


svn path=/trunk/; revision=1818

2008-07-08  David Zeuthen  <davidz@redhat.com>

        Provide infrastructure for out of process volume monitors and
        port the hal volume monitor to use it (#520132).

        * Makefile.am:
        * configure.ac:
        Add the monitor and monitor/proxy directories.

        * hal/Makefile.am:
        Don't build a gio module for the hal volume monitor; instead
        build a volume monitor daemon.

        * hal/ghaldrive.[ch]:
        * hal/ghalmount.[ch]:
        * hal/ghalvolume.[ch]:
        * hal/ghalvolumemonitor.[ch]:
        * hal/hal-device.[ch]:
        * hal/hal-device.[ch]:
        * hal/hal-pool.[ch]:
        Make all types static and implement g_volume_get_activation_root()
        added to gio (#541793). Also emit the drive-eject-button
        signal (#541794).

        * hal/hal-module.c:
        Removed since the monitor is being moved out of process.

        * hal/hal-volume-monitor-daemon.c:
        * hal/hal.monitor:
        * hal/org.gtk.Private.HalVolumeMonitor.service.in:
        New files for remote volume monitor.

        * monitor/Makefile.am:
        New file.

        * monitor/proxy/*:
        Add proxy volume monitor gio module (the D-Bus client side of
        out-of-process volume monitors) and a static library for providing
        the D-Bus server side of out of process volume monitors.

        * programs/gvfs-mount.c:
        Print activation uri for a volumes and icons for drives.
        Also unref volume monitor when no longer in use.


svn path=/trunk/; revision=1815