[banshee] [GioHardware] Don't be overzealous in ignoring mount removed events



commit a022dfcff6354664221c5a90c895659ed19d9876
Author: Alan McGovern <alan mcgovern gmail com>
Date:   Sat Sep 25 13:24:30 2010 +0100

    [GioHardware] Don't be overzealous in ignoring mount removed events
    
    We were actually ignoring every mount removed event because when
    the mount was removed, the mountpath would always be null. This worked
    fine for devices who emit a VolumeRemoved event when they were
    unmounted but for devices like iPhones who only emit a MountRemoved, it
    meant they stayed listed in banshee forever.

 .../Banshee.Hardware.Gio/LowLevel/Manager.cs       |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/src/Backends/Banshee.Gio/Banshee.Hardware.Gio/LowLevel/Manager.cs b/src/Backends/Banshee.Gio/Banshee.Hardware.Gio/LowLevel/Manager.cs
index 1275856..213e747 100644
--- a/src/Backends/Banshee.Gio/Banshee.Hardware.Gio/LowLevel/Manager.cs
+++ b/src/Backends/Banshee.Gio/Banshee.Hardware.Gio/LowLevel/Manager.cs
@@ -92,7 +92,7 @@ namespace Banshee.Hardware.Gio
         {
             // Manually get the mount as gio-sharp translates it to the wrong managed object
             var mount = GLib.MountAdapter.GetObject ((GLib.Object) args.Args [0]);
-            if (mount.Volume == null || mount.Root == null || mount.Root.Path == null) {
+            if (mount.Volume == null) {
                 return;
             }
 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]