IMO, no. #25653 complained that gpilotd was looking for /proc/bus/usb/devices, and the fix is to read /sys/bus/usb if it is available. This is now done (unless HAL is being used...)
This bug, #30015, is complaining that gnome-pilot doesn't give the user any guide to choosing the correct ttyUSB device for syncing. In a perfect world, HAL would tell gpilotd where the palm device is. In practice, HAL doesn't seem to be robustly detecting the presence of a palm device, so the user is stuck having to supply the device name to gnome-pilot, and HAL is just used to tell gpilotd that a USB device (any USB device) has appeared. I haven't yet followed up with the HAL people (I am positively not a HAL guru) to see why HAL is letting me down. As soon as HAL gets to the stage where it can be relied upon to detect all palm pda devices, and distinguish between visor and non-visor (i.e. libusb) connections, I'll be more than happy to make things simple for the users. -- should automatically detect attached devices and use the apporpriate port https://launchpad.net/bugs/30015 -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
