[Bug 527774] [NEW] Sync ifuse 0.9.7-1 (universe) from Debian unstable (main)
Public bug reported: Binary package hint: ifuse We already have libimobiledevice 0.9.7 in universe, but ifuse is still at 0.9.5 and depending on libiphone which is not available in the repositories (and should not due to project rename). Changelog: ifuse (0.9.7-1) unstable; urgency=low * New upstream release (Closes: #568133) * debian/control - Replace build-depends on libiphone-dev by libimobiledevice-dev. - Bump Standards-Version to 3.8.4 (no change needed). -- Julien Lavergne julien.laver...@gmail.com Tue, 09 Feb 2010 23:22:21 +0100 ** Affects: ifuse (Ubuntu) Importance: Undecided Status: New ** Tags: ifuse libimobiledevice lucid -- Sync ifuse 0.9.7-1 (universe) from Debian unstable (main) https://bugs.launchpad.net/bugs/527774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 426378] [NEW] Please include libusb-1.0 version 1.0.3
Public bug reported: libusb-1.0 v1.0.3 has been released. Would be great if you include this into karmic as it contains important bug fixes, esp. an essential fix that allows to send packets with a buffer size of 0. This is required for devices like the iPhone/iPod touch to work properly. see: http://git.stuge.se/?p=libusb.git;a=summary http://sourceforge.net/projects/libusb/files/libusb-1.0/ ** Affects: libusb-1.0 (Ubuntu) Importance: Undecided Status: New -- Please include libusb-1.0 version 1.0.3 https://bugs.launchpad.net/bugs/426378 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386002] Re: Please package changes in r12140..12143 (iPhone/Touch)
Martin, what udev rules are you talking about? The default ubuntu udev rules do not deal with Apple PTP devices. Everything else is implemented with libiphone+usbmuxd which ships with a udev rule on its own. -- Please package changes in r12140..12143 (iPhone/Touch) https://bugs.launchpad.net/bugs/386002 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386002] Re: Please package changes in r12140..12143 (iPhone/Touch)
Ah, forgot something, will there be a backport for Jaunty? -- Please package changes in r12140..12143 (iPhone/Touch) https://bugs.launchpad.net/bugs/386002 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386002] Re: Please package changes in r12140..12143 (iPhone/Touch)
Martin, thanks for the quick answers. I took a look at the udev rules that are produced by print-camera-list, they seem to be used to set the ownership and permissions of the usb device files. AFAIK these udev rules are not used within Jaunty; and in Karmic, not even the fdi rules are generated automatically. So it should be no problem. -- Please package changes in r12140..12143 (iPhone/Touch) https://bugs.launchpad.net/bugs/386002 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386002] Re: Please package changes in r12140..12143 (iPhone/Touch)
Ah well I see. But I just found a problem. The fdi file shipped with the debian file does not contain any matching except info.subsystem usb. This is because print-camera-list is built with a libtool wrapper script that seems to be used during package building instead of the final binary file. This should not, but indeed does, produce a different output than the final binary file which is located in packaging/generic/.libs/print-camera-list after building. Possibly the udev file is also generated Besides that, there is another problem. If I use the correct print-camera-list program with the hal-fdi argument, the fdi file is generated BUT the matching for Apple iPhones is still incorrect, using usb.interface.class=0, usb.interface.subclass=0, and usb.interface.protocol=0. Attached is the corrected patch from above using 6:1:1. @Marcus: You should fix this in libgphoto2 SVN, too. @Martin: Perhaps you should use ./packaging/generic/.libs/print-camera-list udev-rules [...] and ./packaging/generic/.libs/print-camera-list hal-fdi instead of ./packaging/generic/print-camera-list udev-rules [...] and ./packaging/generic/print-camera-list hal-fdi inside the debian/rules file which worked for me. ** Attachment added: xx-corrected.patch http://launchpadlibrarian.net/27908913/xx-corrected.patch -- Please package changes in r12140..12143 (iPhone/Touch) https://bugs.launchpad.net/bugs/386002 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386002] Re: Please package changes in r12140..12143 (iPhone/Touch)
concerning debian/rules: My suggestions works but print-camera-list is executed with the installed version of libgphoto2 and not the one that has just been compiled. Perhaps it might be better NOT to ship static files for udev/fdi and put the file creation back into libgphoto2-2.postinst to make sure the files are really created with the latest version of the library. Attached is a patch that adds iPod Touch 1G and renames the already present iPod Touch entry to iPod Touch 2G, just to be complete. If the iPhone 3G S product_id has been verified, you can add it too (I bet it is 0x1294). ** Attachment added: ipod_touch.patch http://launchpadlibrarian.net/27909661/ipod_touch.patch -- Please package changes in r12140..12143 (iPhone/Touch) https://bugs.launchpad.net/bugs/386002 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 296710] Re: warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
That's right Paul. I'm having issues now too, as I have defective usb 2.0 hardware (usb 1.1 is working flawlessly via the same usb connector) so I used to unload the ehci-hcd which is not possible anymore with the latest kernel revision 2.6.28-11.40 because *hci-hcd are built-in now. So I either have to get new hardware or recompile my kernel... -- warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd https://bugs.launchpad.net/bugs/296710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354832] Re: impossible to unload ehci_hcd on detective hardware (since compiled in)
I recently had another usb 2.0 specific issue with a web cam on another (non-defective) system. I wanted to try out for a friend if my web cam is working smoothly with usb 1.1, because his hardware doesn't has usb 2.0 support. So I plugged in the web cam into another system with non- defective usb 2.0 hardware. The cam worked right away (e.g. with cheese) -- but after unloading the ehci-hcd module, it produced even smoother video! So I'd really like to keep the ability to remove the usb 2.0 support from the kernel by unloading ehci-hcd. -- impossible to unload ehci_hcd on detective hardware (since compiled in) https://bugs.launchpad.net/bugs/354832 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
