[Pkg-ltsp-devel] Bug#575031: ltspfs: issue KDE popups

[Petter Reinholdtsen]

Based on input from Dario Freddi on IRC, I ran "lshal --monitor" in
Debian/Lenny while inserting a USB stick, to see what hal events were
generated.

First, these three showed up:

  23:00:09.685: usb_device_90c_1000_A800000000026288 added
  23:00:10.007: usb_device_90c_1000_A800000000026288_if0 added
  23:00:10.086: usb_device_1d6b_2_0000_00_1d_7_usbraw_0 added

Then these showed up shortly after, and after the last one a popup
showed up in KDE.

  23:00:14.841: usb_device_90c_1000_A800000000026288_if0_scsi_host added
  23:00:14.865: usb_device_90c_1000_A800000000026288_if0_scsi_host_scsi_device_lun0 added
  23:00:15.091: storage_serial_Corsair_Flash_Voyager_A800000000026288_0_0 added
  23:00:15.102: storage_serial_Corsair_Flash_Voyager_A800000000026288_0_0 property info.interfaces = {'org.freedesktop.Hal.Device.Storage.Removable'} (new)
  23:00:16.362: volume_uuid_1f59d4b0_08d4_4551_aa27_f777df5cffb6 added

Next, I asked the media applet to safely remove the device, and these
events happend:

  23:00:27.012: storage_serial_Corsair_Flash_Voyager_A800000000026288_0_0 property storage.removable.media_available = false
  23:00:27.025: storage_serial_Corsair_Flash_Voyager_A800000000026288_0_0 property storage.partitioning_scheme = ''
  23:00:27.041: volume_uuid_1f59d4b0_08d4_4551_aa27_f777df5cffb6 removed

Finally I pulled the USB stick out, and these events happened:

  23:00:31.784: storage_serial_Corsair_Flash_Voyager_A800000000026288_0_0 removed
  23:00:31.791: usb_device_90c_1000_A800000000026288_if0_scsi_host_scsi_device_lun0 removed
  23:00:31.794: usb_device_90c_1000_A800000000026288_if0_scsi_host removed
  23:00:31.803: usb_device_90c_1000_A800000000026288_if0 removed
  23:00:31.812: usb_device_1d6b_2_0000_00_1d_7_usbraw_0 removed
  23:00:31.820: usb_device_90c_1000_A800000000026288 removed

With KDE in Lenny there is a problem with umask settings for mounts,
ref <URL: http://bugs.skolelinux.org/show_bug.cgi?id=1378 >.  We
probably need to check if this is fixed in KDE 4.

Happy hacking,
-- 
Petter Reinholdtsen