[Touch-packages] [Bug 1537774] Re: Viewfinder frozen and all buttons disabled after taking HDR picture
I also have this issue with my Meizu mx4. I have found a hard reboot is the only thing that gets my phone is able again. I find this happens when I have the camera set at the highest resolution although I haven't tried it at lower res. Doesn't seem to be an issue with the selfish camera. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1537774 Title: Viewfinder frozen and all buttons disabled after taking HDR picture Status in Canonical System Image: Confirmed Status in camera-app package in Ubuntu: Confirmed Bug description: Reported by royden in https://bugs.launchpad.net/ubuntu/+source /camera-app/+bug/1475895/comments/6 "Testing the fix released for Bug #1519766 (and likely #1478693) I can reliably freeze the camera-app (v. 3.0.0.616) on rc-proposed Arale r227 by taking HDR images. Freeze happens around the 3rd or 4th shot of the same subject as reported in Bug #1519766. HDR shots of shaded lamp in semi-dark room (taking up 3/4 of view) trigger freeze on 4/5th shot. HDR shots of lamp on small table at distance in semi-dark room do not reliably trigger freeze. Normal shots do not trigger freeze, with or without zoom AFAIKS. Freeze comprises either the viewfinder holding the image of the attempted capture and app being no longer responsive and needing to be closed. Re-opening produces "Cannot access camera" error message screen, with access permission or some other error as cause. Reboot needed to regain camera function. Other freeze seen was a return of the viewfinder to a dark screen, and the same error message screen appearing." To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574079] Re: USB audio device is not recognized after startup in 16.04
My usb audio is no longer working at all with 16.04. I am rolling back to previous LTS as this sucks and has remained as unassigned for a while now. I wonder if it is worth raising a separate bug as the fwupd "fix released" is a misnomer for myself and others. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1574079 Title: USB audio device is not recognized after startup in 16.04 Status in alsa-driver package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Fix Released Bug description: Hi @all, I used the same USB audio device in all previous Ubuntu versions (Focusrite Scarlet 2i2). It is supposed to be class compliant and works an all distros flawless (even RPI2 and OSMC). After upgrading from 15.10 to 16.04 it stopped to work: after start-up it does not show up as an audio device at all (also not recognized by aplay -l). I can workaround this by unplugging it and plugging it in again after Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time plugging it in again it shows up and works great without any further issues until next restart. Maybe worth to note that I recognized today that fwupd uses continuously 100% CPU load, so I just killed it today. My Hardware (Main-board/CPU) is a bit older (Intel E8400), so could probably be some compatibility issue... regards, Tobias ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tobias 1553 F...m pulseaudio /dev/snd/controlC1: tobias 1553 F pulseaudio /dev/snd/controlC0: tobias 1553 F pulseaudio /dev/snd/controlC2: tobias 1553 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 20:09:04 2016 InstallationDate: Installed on 2015-09-19 (217 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) dmi.bios.date: 09/30/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1238 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574079] Re: USB audio device is not recognized after startup in 16.04
This fix does not work for Cambridge Audio dac Magic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1574079 Title: USB audio device is not recognized after startup in 16.04 Status in alsa-driver package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Fix Released Bug description: Hi @all, I used the same USB audio device in all previous Ubuntu versions (Focusrite Scarlet 2i2). It is supposed to be class compliant and works an all distros flawless (even RPI2 and OSMC). After upgrading from 15.10 to 16.04 it stopped to work: after start-up it does not show up as an audio device at all (also not recognized by aplay -l). I can workaround this by unplugging it and plugging it in again after Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time plugging it in again it shows up and works great without any further issues until next restart. Maybe worth to note that I recognized today that fwupd uses continuously 100% CPU load, so I just killed it today. My Hardware (Main-board/CPU) is a bit older (Intel E8400), so could probably be some compatibility issue... regards, Tobias ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tobias 1553 F...m pulseaudio /dev/snd/controlC1: tobias 1553 F pulseaudio /dev/snd/controlC0: tobias 1553 F pulseaudio /dev/snd/controlC2: tobias 1553 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 20:09:04 2016 InstallationDate: Installed on 2015-09-19 (217 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) dmi.bios.date: 09/30/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1238 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574079] Re: USB audio device is not recognized after startup in 16.04
I have reinstalled Ubuntu 16.04 afresh today and after a complete update this is still an issue with my Cambridge Audio USB soundcard. Removing fwupd did do the trick this time. However if I was new to Linux this wouldn't give a good first impression and indeed could have been a deal breaker. I noticed there was an update to fwupd whilst I was updating the system; but as I said this didn't work for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1574079 Title: USB audio device is not recognized after startup in 16.04 Status in alsa-driver package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Fix Released Bug description: Hi @all, I used the same USB audio device in all previous Ubuntu versions (Focusrite Scarlet 2i2). It is supposed to be class compliant and works an all distros flawless (even RPI2 and OSMC). After upgrading from 15.10 to 16.04 it stopped to work: after start-up it does not show up as an audio device at all (also not recognized by aplay -l). I can workaround this by unplugging it and plugging it in again after Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time plugging it in again it shows up and works great without any further issues until next restart. Maybe worth to note that I recognized today that fwupd uses continuously 100% CPU load, so I just killed it today. My Hardware (Main-board/CPU) is a bit older (Intel E8400), so could probably be some compatibility issue... regards, Tobias ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tobias 1553 F...m pulseaudio /dev/snd/controlC1: tobias 1553 F pulseaudio /dev/snd/controlC0: tobias 1553 F pulseaudio /dev/snd/controlC2: tobias 1553 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 20:09:04 2016 InstallationDate: Installed on 2015-09-19 (217 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) dmi.bios.date: 09/30/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1238 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574079] Re: USB audio device is not recognized after startup in 16.04
Can I just add that this affects my Cambridge Audio DAC Magic100 also. I have found that it seems to effect Ubuntu and Ubuntu mate but strangely not Kubuntu. I tried Ubuntu again 3 days ago and this is still a problem. In fact as I get small shocks from the case I'm a little reluctant to pursue this further. I note killing fwupd solves the issue which is interesting as it doesn't seem to work for Kubuntu Maybe off by default? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1574079 Title: USB audio device is not recognized after startup in 16.04 Status in alsa-driver package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Fix Released Bug description: Hi @all, I used the same USB audio device in all previous Ubuntu versions (Focusrite Scarlet 2i2). It is supposed to be class compliant and works an all distros flawless (even RPI2 and OSMC). After upgrading from 15.10 to 16.04 it stopped to work: after start-up it does not show up as an audio device at all (also not recognized by aplay -l). I can workaround this by unplugging it and plugging it in again after Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time plugging it in again it shows up and works great without any further issues until next restart. Maybe worth to note that I recognized today that fwupd uses continuously 100% CPU load, so I just killed it today. My Hardware (Main-board/CPU) is a bit older (Intel E8400), so could probably be some compatibility issue... regards, Tobias ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tobias 1553 F...m pulseaudio /dev/snd/controlC1: tobias 1553 F pulseaudio /dev/snd/controlC0: tobias 1553 F pulseaudio /dev/snd/controlC2: tobias 1553 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 20:09:04 2016 InstallationDate: Installed on 2015-09-19 (217 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) dmi.bios.date: 09/30/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1238 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1473428] Re: battery indicator does not update after charge [meizu ubuntu phone]
Just to add a little info from my own experience I have found that when the phone is fully charged and then shows this issue with the indicator, the following corrects it: 1) turn the Meizu off 2) plug in the recharge cable and wait for the screen to indicate it is charging and then go blank (important) 3) unplug and turn on and all is well!! Is there someone looking into this as it is slightly disconcerting not knowing how much charge is left? The latest OTA8 has not fixed it for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1473428 Title: battery indicator does not update after charge [meizu ubuntu phone] Status in indicator-power package in Ubuntu: Confirmed Bug description: Battery charge indicator does not update after phone is charged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1473428/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
