[Bug 1464054] Re: Fails to create a snappy image when using --install
I used the package version 0.27-0ubuntu1 from https://launchpad.net /~snappy-dev/+archive/ubuntu/tools-proposed which included the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464054 Title: Fails to create a snappy image when using --install To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1464054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464054] Re: Fails to create a snappy image when using --install
Is there an updated version of the package available? I'm also seeing this on 0.23-0ubuntu2 of the ubuntu-device-flash package but I couldn't see if a more recent version had been made available in a PPA that includes this fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464054 Title: Fails to create a snappy image when using --install To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1464054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450980] Re: Python 3.4.3 package fails to install with deboostrap on armhf
FWIW, using a '--variant=minbase' works around the issue with qemu- debootstrap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450980 Title: Python 3.4.3 package fails to install with deboostrap on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1450980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450980] Re: Python 3.4.3 package fails to install with deboostrap on armhf
I see this when doing a live-build for vivid. Live building utopic completes just fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450980 Title: Python 3.4.3 package fails to install with deboostrap on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1450980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094138] Re: Modem Manager Locks Dual FTDI Serial Ports
This also affects FTDI's newer FT230X series. VID:0403, PID:6015 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094138 Title: Modem Manager Locks Dual FTDI Serial Ports To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1094138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094138] Re: Modem Manager Locks Dual FTDI Serial Ports
Ahh---that makes sense about the USB to Serial adapter--thanks for explaining Alekasander. As a USB-to-serial adapter is a generic device that may or may not be connected to a modem, a manually-launched scan makes sense. In the interim though, it makes sense that distros adjust the blacklist to fit their user base. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094138 Title: Modem Manager Locks Dual FTDI Serial Ports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1094138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094138] [NEW] Modem Manager Locks Dual FTDI Serial Ports
Public bug reported: As per Question #217761, I'm submitting a bug report in order to include a patch. Details from question follow: I'm trying to connect serial console to an embedded device and but I'm not able to connect for the first 36 seconds after connection as modem-manager has locked the /dev/ttyUSB1 file (as shown by '$ sudo lsof /dev/ttyUSB1'). By blacklisting the USB ID (0403:6010) of the device in the '77-mm-usb-devices-blacklist.rhles' udev rule, I can immediately access the device. Much like the commonly used single FTDI USB-serial converter chip (USD ID 0403:6001) that is blacklisted in this file 77-mm-usb-device-blacklist.rules, I think the dual version (USB ID 0403:6010) chould also be added as it is commonly used in JTAG debugged boards and embedded devices. ... ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: modemmanager 0.6.0.0.really-0ubuntu1 [modified: lib/udev/rules.d/77-mm-usb-device-blacklist.rules] ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Thu Dec 27 14:07:21 2012 InstallationDate: Installed on 2012-12-23 (3 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity ** Patch added: ft2232-blacklist.patch https://bugs.launchpad.net/bugs/1094138/+attachment/3469297/+files/ft2232-blacklist.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094138 Title: Modem Manager Locks Dual FTDI Serial Ports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1094138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094138] Re: Modem Manager Locks Dual FTDI Serial Ports
Are there any modems using a FT2232 chip without a custom USB device ID? I suggested the change on the basis that the chip is commonly used in embedded devices (e.g. http://www.tincantools.com/product.php?productid=16134 and https://www.gumstix.com/store/product_info.php?products_id=262) without the extra eeprom used to set a custom VID/PID but expected (perhaps naively) that modem designers would actually want a unique identifier for their particular device. I certainly understand dropping the patch if there are Modem out there that would be broken by this change. This is good to hear that the probe will be shorter in future versions and avoiding automatic probing seems like a good change :). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094138 Title: Modem Manager Locks Dual FTDI Serial Ports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1094138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771537] Re: Beagle XM lacks proper 1Ghz support
I some success running a Gumstix Overo (Storm series, OMAP37xx) at 1GHz. Started with * http://arago-project.org/git/projects/?p=linux-omap3.git;a=shortlog;h=refs/heads/OMAPPSP_04.02.00.07 Used tag *v2.6.37_OMAPPSP_04.02.00.07 And applied the attached patch (0001-am37x-) This is not a mainline-able solution. ** Patch added: 1GHz patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/771537/+attachment/3234244/+files/0001-am37x-Adding-ABB-Support-for-1GHz-OPP.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771537 Title: Beagle XM lacks proper 1Ghz support To manage notifications about this bug go to: https://bugs.launchpad.net/linaro-ubuntu/+bug/771537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 797491] Re: overo lcd43 touchscreen does not work
I can confirm this bug in linux-linaro-2.6.38 master and have tested Andy's patch with both a DVI monitor attached and a LTE430WQ panel attached. Both types of screens worked although the 4.3 panel showed a vertical bar at one point in the image. It was not necessary to add the omapdss.def_disp=lcd43 argument. Note, lgphilips 3.5 panels aren't fixed by this patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/797491 Title: overo lcd43 touchscreen does not work To manage notifications about this bug go to: https://bugs.launchpad.net/linux-linaro/+bug/797491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
