[Touch-packages] [Bug 1211102] Re: Get rid of 0.5s latency when playing audio over Bluetooth with A2DP
Same issue here. More or less often small disruptions. Seems like those add up and create the latency. Currently using Ubuntu 15.10. Speaker works totally fine with my phone. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1211102 Title: Get rid of 0.5s latency when playing audio over Bluetooth with A2DP Status in bluez package in Ubuntu: Confirmed Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 13.04 Release: 13.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center bluez: Instalados: 4.101- 0ubuntu8b1 Candidato: 4.101-0ubuntu8b1 Tabla de versión: *** 4.101-0ubuntu8b1 0 500 http://es.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen The audio always is sync when i listen music on my bluetooth device If i listen music or have a videoconference with skype.. it receive audio perfectly without delay. 4) What happened instead I experience a half a second delay when playing audio over Bluetooth with A2DP. This makes watching movies not possible as the sound is not synchronised with the video. + If i listen music, then stop about 5 minutes and then restart to listen music, it gets work bad. + If i get a skype videoconference, it gets too much delay. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Mon Aug 12 01:24:24 2013 InstallationDate: Installed on 2013-07-13 (29 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK Computer Inc. UX31E MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=89d221ec-829a-456e-963d-ec7ac2c7d47d ro crashkernel=384M-2G:64M,2G-:128M quiet splash rootfstype=ext4 vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.210:bd12/26/2011:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 74:2F:68:CE:17:57 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:407502 acl:14820 sco:0 events:8796 errors:0 TX bytes:7391611 acl:8717 sco:0 commands:45 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1211102/+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 1565293] Re: OpenSSL 1.0.1 fails to recognize cross-signed roots as trusted
Didn't you forget to rehash the certificates? But nevertheless, it's working without the root and with a fresh rehash. Found your patch, but didn't find a bug related to the patch. Don't know whether this should be closed as invalid or duplicate. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1565293 Title: OpenSSL 1.0.1 fails to recognize cross-signed roots as trusted Status in openssl package in Ubuntu: Incomplete Bug description: Google has it's own certificate authority "Google Internet Authority G2", which is signed by "GeoTrust Global CA". GeoTrust's certificate is already in the trust stores, but it's cross-signed by an older root named "Equifax Secure Certificate Authority". The Equifax uses a 1024 bit private key and has therefore been removed by Mozilla in their library (NSS), see https://bugzilla.mozilla.org/show_bug.cgi?id=1156844. Issuance from 1024 bit roots has been stopped in 2010 or 2011 IIRC and 1024 bit keys are no longer safe enough, so the root has been excluded from their root program. However, Ubuntu 12.04 and 14.04 do still ship with that root in their trust store. A bug in the currently default OpenSSL 1.0.1f (at least in 14.04) causes OpenSSL to error if that root is missing, even if the previous root certificate "GeoTrust Global CA" is already in the root and therefore trusted. It seems like it doesn't stop on the first trusted certificate but instead requires a complete chain, so requires the "Equifax Secure Certificate Authority" to be in the trust store. That behavior is fixed in OpenSSL 1.0.2. All 1024 bit roots should be removed from the default trust stores as soon as possible. For this to work, the OpenSSL bug has to be backported first. If this is not going to be fixed, at least in 2018, we'll have an issue, because that's the date where "Equifax Secure Certificate Authority" will expire. If Google and various other sites will not change their root to be non-cross-signed, many connections will break and fail. Domains I know to use old cross-signed certificates: google.com, yahoo.com. I didn't do any scans, those were just the first two I tried. The following will happen on Aug 22 2018 without a fix: kelunik@example:~$ faketime '2018-08-23 00:00:00' openssl s_client -quiet -verify_return_error -connect google.com:443 -CApath /usr/lib/ssl/certs depth=3 C = US, O = Equifax, OU = Equifax Secure Certificate Authority verify error:num=10:certificate has expired notAfter=Aug 22 16:41:51 2018 GMT verify return:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1565293/+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 1565293] Re: OpenSSL 1.0.1 fails to recognize cross-signed roots as trusted
We originally encountered that issue on Travis. After I couldn't reproduce it locally on my 15.10 machine, I downloaded Ubuntu Server 14.04 and could verify it in a VM. Seems like I forgot to install the latest updates, verified it's fixed in the latest version. I'll notify the Travis team, so they can update their images. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1565293 Title: OpenSSL 1.0.1 fails to recognize cross-signed roots as trusted Status in openssl package in Ubuntu: Incomplete Bug description: Google has it's own certificate authority "Google Internet Authority G2", which is signed by "GeoTrust Global CA". GeoTrust's certificate is already in the trust stores, but it's cross-signed by an older root named "Equifax Secure Certificate Authority". The Equifax uses a 1024 bit private key and has therefore been removed by Mozilla in their library (NSS), see https://bugzilla.mozilla.org/show_bug.cgi?id=1156844. Issuance from 1024 bit roots has been stopped in 2010 or 2011 IIRC and 1024 bit keys are no longer safe enough, so the root has been excluded from their root program. However, Ubuntu 12.04 and 14.04 do still ship with that root in their trust store. A bug in the currently default OpenSSL 1.0.1f (at least in 14.04) causes OpenSSL to error if that root is missing, even if the previous root certificate "GeoTrust Global CA" is already in the root and therefore trusted. It seems like it doesn't stop on the first trusted certificate but instead requires a complete chain, so requires the "Equifax Secure Certificate Authority" to be in the trust store. That behavior is fixed in OpenSSL 1.0.2. All 1024 bit roots should be removed from the default trust stores as soon as possible. For this to work, the OpenSSL bug has to be backported first. If this is not going to be fixed, at least in 2018, we'll have an issue, because that's the date where "Equifax Secure Certificate Authority" will expire. If Google and various other sites will not change their root to be non-cross-signed, many connections will break and fail. Domains I know to use old cross-signed certificates: google.com, yahoo.com. I didn't do any scans, those were just the first two I tried. The following will happen on Aug 22 2018 without a fix: kelunik@example:~$ faketime '2018-08-23 00:00:00' openssl s_client -quiet -verify_return_error -connect google.com:443 -CApath /usr/lib/ssl/certs depth=3 C = US, O = Equifax, OU = Equifax Secure Certificate Authority verify error:num=10:certificate has expired notAfter=Aug 22 16:41:51 2018 GMT verify return:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1565293/+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 1565293] [NEW] OpenSSL 1.0.1 fails to recognize cross-signed roots as trusted
Public bug reported: Google has it's own certificate authority "Google Internet Authority G2", which is signed by "GeoTrust Global CA". GeoTrust's certificate is already in the trust stores, but it's cross-signed by an older root named "Equifax Secure Certificate Authority". The Equifax uses a 1024 bit private key and has therefore been removed by Mozilla in their library (NSS), see https://bugzilla.mozilla.org/show_bug.cgi?id=1156844. Issuance from 1024 bit roots has been stopped in 2010 or 2011 IIRC and 1024 bit keys are no longer safe enough, so the root has been excluded from their root program. However, Ubuntu 12.04 and 14.04 do still ship with that root in their trust store. A bug in the currently default OpenSSL 1.0.1f (at least in 14.04) causes OpenSSL to error if that root is missing, even if the previous root certificate "GeoTrust Global CA" is already in the root and therefore trusted. It seems like it doesn't stop on the first trusted certificate but instead requires a complete chain, so requires the "Equifax Secure Certificate Authority" to be in the trust store. That behavior is fixed in OpenSSL 1.0.2. All 1024 bit roots should be removed from the default trust stores as soon as possible. For this to work, the OpenSSL bug has to be backported first. If this is not going to be fixed, at least in 2018, we'll have an issue, because that's the date where "Equifax Secure Certificate Authority" will expire. If Google and various other sites will not change their root to be non-cross-signed, many connections will break and fail. Domains I know to use old cross-signed certificates: google.com, yahoo.com. I didn't do any scans, those were just the first two I tried. The following will happen on Aug 22 2018 without a fix: kelunik@example:~$ faketime '2018-08-23 00:00:00' openssl s_client -quiet -verify_return_error -connect google.com:443 -CApath /usr/lib/ssl/certs depth=3 C = US, O = Equifax, OU = Equifax Secure Certificate Authority verify error:num=10:certificate has expired notAfter=Aug 22 16:41:51 2018 GMT verify return:0 ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1565293 Title: OpenSSL 1.0.1 fails to recognize cross-signed roots as trusted Status in openssl package in Ubuntu: New Bug description: Google has it's own certificate authority "Google Internet Authority G2", which is signed by "GeoTrust Global CA". GeoTrust's certificate is already in the trust stores, but it's cross-signed by an older root named "Equifax Secure Certificate Authority". The Equifax uses a 1024 bit private key and has therefore been removed by Mozilla in their library (NSS), see https://bugzilla.mozilla.org/show_bug.cgi?id=1156844. Issuance from 1024 bit roots has been stopped in 2010 or 2011 IIRC and 1024 bit keys are no longer safe enough, so the root has been excluded from their root program. However, Ubuntu 12.04 and 14.04 do still ship with that root in their trust store. A bug in the currently default OpenSSL 1.0.1f (at least in 14.04) causes OpenSSL to error if that root is missing, even if the previous root certificate "GeoTrust Global CA" is already in the root and therefore trusted. It seems like it doesn't stop on the first trusted certificate but instead requires a complete chain, so requires the "Equifax Secure Certificate Authority" to be in the trust store. That behavior is fixed in OpenSSL 1.0.2. All 1024 bit roots should be removed from the default trust stores as soon as possible. For this to work, the OpenSSL bug has to be backported first. If this is not going to be fixed, at least in 2018, we'll have an issue, because that's the date where "Equifax Secure Certificate Authority" will expire. If Google and various other sites will not change their root to be non-cross-signed, many connections will break and fail. Domains I know to use old cross-signed certificates: google.com, yahoo.com. I didn't do any scans, those were just the first two I tried. The following will happen on Aug 22 2018 without a fix: kelunik@example:~$ faketime '2018-08-23 00:00:00' openssl s_client -quiet -verify_return_error -connect google.com:443 -CApath /usr/lib/ssl/certs depth=3 C = US, O = Equifax, OU = Equifax Secure Certificate Authority verify error:num=10:certificate has expired notAfter=Aug 22 16:41:51 2018 GMT verify return:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1565293/+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 1464917] Re: reboot hangs at 'Reached target Shutdown'
Unfortunately, it only fixed it in the first reboot. The one now had that problem again, even with vivid-proposed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' Status in systemd package in Ubuntu: Confirmed Bug description: I rebooted my 15.04 system, and found it hanging indefinitely at the plymouth shutdown screen. Hitting esc to reveal the console showed a normal set of shutdown messages, ending with 'Reached target Shutdown' (paraphrased from memory). The system never rebooted on its own. I had to use SysRq to finish the shutdown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 13 11:53:10 2015 InstallationDate: Installed on 2010-09-24 (1723 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+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 1464917] Re: reboot hangs at 'Reached target Shutdown'
** Changed in: systemd (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' Status in systemd package in Ubuntu: Confirmed Bug description: I rebooted my 15.04 system, and found it hanging indefinitely at the plymouth shutdown screen. Hitting esc to reveal the console showed a normal set of shutdown messages, ending with 'Reached target Shutdown' (paraphrased from memory). The system never rebooted on its own. I had to use SysRq to finish the shutdown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 13 11:53:10 2015 InstallationDate: Installed on 2010-09-24 (1723 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+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 1464917] Re: reboot hangs at 'Reached target Shutdown'
I can confirm that updating to vivid-proposed fixes that behavior. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' Status in systemd package in Ubuntu: Confirmed Bug description: I rebooted my 15.04 system, and found it hanging indefinitely at the plymouth shutdown screen. Hitting esc to reveal the console showed a normal set of shutdown messages, ending with 'Reached target Shutdown' (paraphrased from memory). The system never rebooted on its own. I had to use SysRq to finish the shutdown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 13 11:53:10 2015 InstallationDate: Installed on 2010-09-24 (1723 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+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
