[Touch-packages] [Bug 1888041] [NEW] default output is ignored and reset after reboot
Public bug reported: I have lots of possible outputs, like speakers, wireless headset, and HDMI output. I select speakers as default, but on reboot it always select the wireless headset. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 18 01:59:22 2020 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7803 dmi.board.asset.tag: Default string dmi.board.name: CROSSHAIR VI HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7803:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1888041 Title: default output is ignored and reset after reboot Status in pulseaudio package in Ubuntu: New Bug description: I have lots of possible outputs, like speakers, wireless headset, and HDMI output. I select speakers as default, but on reboot it always select the wireless headset. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 18 01:59:22 2020 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7803 dmi.board.asset.tag: Default string dmi.board.name: CROSSHAIR VI HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7803:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888041/+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 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)
[Expired for wayland (Ubuntu) because there has been no activity for 60 days.] ** Changed in: wayland (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1877568 Title: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing) Status in gnome-terminal package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Status in wayland package in Ubuntu: Expired Bug description: Since upgrading to 20.04 and switching to Wayland, Gnome terminal occasionally crashes. I interpret the corresponding logs to mean that it's actually Wayland that fails to do something in the background, which then takes down Gnome terminal: touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client. touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client communication (pid 11639) touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events from display: Katkennut putki touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded. touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded. touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: Failed with result 'exit-code'. I have yet to nail down the precise circumstances, as this has (so far) been somewhat rare, having occurred perhaps once or twice a week. Since the log mentions pointer, I should perhaps mention that I've set `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome terminal also exhibits other misbehaviour wrt. to this, occasionally refusing to get focus, or alternatively losing the focus, despite mouse cursor being over the terminal window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xwayland 2:1.20.8-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 15:22:28 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed (WARNING! Diff between built and installed module!) xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] InstallationDate: Installed on 2016-10-13 (1302 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A
[Touch-packages] [Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)
[Expired for gnome-terminal (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-terminal (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1877568 Title: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing) Status in gnome-terminal package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Status in wayland package in Ubuntu: Expired Bug description: Since upgrading to 20.04 and switching to Wayland, Gnome terminal occasionally crashes. I interpret the corresponding logs to mean that it's actually Wayland that fails to do something in the background, which then takes down Gnome terminal: touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client. touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client communication (pid 11639) touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events from display: Katkennut putki touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded. touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded. touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: Failed with result 'exit-code'. I have yet to nail down the precise circumstances, as this has (so far) been somewhat rare, having occurred perhaps once or twice a week. Since the log mentions pointer, I should perhaps mention that I've set `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome terminal also exhibits other misbehaviour wrt. to this, occasionally refusing to get focus, or alternatively losing the focus, despite mouse cursor being over the terminal window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xwayland 2:1.20.8-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 15:22:28 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed (WARNING! Diff between built and installed module!) xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] InstallationDate: Installed on 2016-10-13 (1302 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz:
[Touch-packages] [Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1877568 Title: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing) Status in gnome-terminal package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Status in wayland package in Ubuntu: Expired Bug description: Since upgrading to 20.04 and switching to Wayland, Gnome terminal occasionally crashes. I interpret the corresponding logs to mean that it's actually Wayland that fails to do something in the background, which then takes down Gnome terminal: touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client. touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client communication (pid 11639) touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events from display: Katkennut putki touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded. touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded. touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: Failed with result 'exit-code'. I have yet to nail down the precise circumstances, as this has (so far) been somewhat rare, having occurred perhaps once or twice a week. Since the log mentions pointer, I should perhaps mention that I've set `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome terminal also exhibits other misbehaviour wrt. to this, occasionally refusing to get focus, or alternatively losing the focus, despite mouse cursor being over the terminal window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xwayland 2:1.20.8-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 15:22:28 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed (WARNING! Diff between built and installed module!) xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] InstallationDate: Installed on 2016-10-13 (1302 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A
[Touch-packages] [Bug 1878782] Re: Bluetooth is on but scanned devices are not showing.
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/1878782 Title: Bluetooth is on but scanned devices are not showing. Status in bluez package in Ubuntu: Expired Bug description: Bluetooth in spite of being switched on, shows the same image as when it is off in the paired devices menu. I cannot access my paired devices. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dashtrox 1582 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 15 13:48:16 2020 InstallationDate: Installed on 2020-05-12 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 1TCN27WW(V2.08) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15ISK dmi.modalias: dmi:bvnLENOVO:bvr1TCN27WW(V2.08):bd07/06/2018:svnLENOVO:pn80UD:pvrLenovoideapad110-15ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15ISK: dmi.product.family: ideapad 110-15ISK dmi.product.name: 80UD dmi.product.sku: LENOVO_MT_80UD_BU_idea_FM_ideapad 110-15ISK dmi.product.version: Lenovo ideapad 110-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878782/+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 1879113] Re: package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
[Expired for pygobject (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pygobject (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1879113 Title: package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in pygobject package in Ubuntu: Expired Bug description: Installing ra1nstorm virtual Mac ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-gi-cairo 3.26.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun May 17 13:06:06 2020 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-05-16 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.3 SourcePackage: pygobject Title: package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1879113/+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 1887610] Autopkgtest regression report (pulseaudio/1:13.99.1-1ubuntu3.5)
All autopkgtests for the newly accepted pulseaudio (1:13.99.1-1ubuntu3.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: openjdk-8/8u252-b09-1ubuntu1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#pulseaudio [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1887610 Title: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode' Status in HWE Next: New Status in OEM Priority Project: In Progress Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Confirmed Status in pulseaudio source package in Eoan: Won't Fix Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] On some I+N machines (inlcuding lenovo and dell machines), after setting the graphic mode to perofermance mode, and open the gnome sound seting, run suspend/resume test, the audio devices will disappear from UI, instead a dummy audio shows on the UI, and from then on, the audio can't work anymore. [Fix] The root cause is after resuming, the pulseaudio try to recover the PCM device, but at that moment, the devices nodes at /dev/snd/ are not accessible yet sometimes, it will make snd_pcm_open fail and the pulseaudio will calll unload_module to unload alsa audio card. I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(), this will retry the snd_pcm_open() a couple of times if it fails. [Test Case] Install the pulseaudio wit this fix, set the graphic mode to performance mode, open the sound setting, then run suspend/resume 90 times, after test check the audio devices on the UI, the speaker, digital mic are still on the UI, and they could work well. [Regression Risk] Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open() doesn't fail, this patch will not introduce any change, if snd_pcm_open() fails, it just retry a couple of times, so it will not introduce the regression in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1887610/+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 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu8 --- pulseaudio (1:13.99.1-1ubuntu8) groovy; urgency=medium * d/p/0033-alsa-make-the-unsuspend-more-robust.patch: - resolve cases where there is no available audio entry in sound settings after suspending in 'Performance mode' (LP: #1887610) -- Hui Wang Wed, 15 Jul 2020 15:29:05 +0800 ** Changed in: pulseaudio (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1887610 Title: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode' Status in HWE Next: New Status in OEM Priority Project: In Progress Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Confirmed Status in pulseaudio source package in Eoan: Won't Fix Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] On some I+N machines (inlcuding lenovo and dell machines), after setting the graphic mode to perofermance mode, and open the gnome sound seting, run suspend/resume test, the audio devices will disappear from UI, instead a dummy audio shows on the UI, and from then on, the audio can't work anymore. [Fix] The root cause is after resuming, the pulseaudio try to recover the PCM device, but at that moment, the devices nodes at /dev/snd/ are not accessible yet sometimes, it will make snd_pcm_open fail and the pulseaudio will calll unload_module to unload alsa audio card. I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(), this will retry the snd_pcm_open() a couple of times if it fails. [Test Case] Install the pulseaudio wit this fix, set the graphic mode to performance mode, open the sound setting, then run suspend/resume 90 times, after test check the audio devices on the UI, the speaker, digital mic are still on the UI, and they could work well. [Regression Risk] Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open() doesn't fail, this patch will not introduce any change, if snd_pcm_open() fails, it just retry a couple of times, so it will not introduce the regression in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1887610/+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 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'
@Jpodjarny, And please also upload the dmesg. BTW, how did you update, only update the pulseaudio or upgrade many packages? And what is the pulseaudio version now (checking it by running dpkg -s pulseaudio | grep Version). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1887610 Title: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode' Status in HWE Next: New Status in OEM Priority Project: In Progress Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Bionic: Confirmed Status in pulseaudio source package in Eoan: Won't Fix Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Bug description: [Impact] On some I+N machines (inlcuding lenovo and dell machines), after setting the graphic mode to perofermance mode, and open the gnome sound seting, run suspend/resume test, the audio devices will disappear from UI, instead a dummy audio shows on the UI, and from then on, the audio can't work anymore. [Fix] The root cause is after resuming, the pulseaudio try to recover the PCM device, but at that moment, the devices nodes at /dev/snd/ are not accessible yet sometimes, it will make snd_pcm_open fail and the pulseaudio will calll unload_module to unload alsa audio card. I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(), this will retry the snd_pcm_open() a couple of times if it fails. [Test Case] Install the pulseaudio wit this fix, set the graphic mode to performance mode, open the sound setting, then run suspend/resume 90 times, after test check the audio devices on the UI, the speaker, digital mic are still on the UI, and they could work well. [Regression Risk] Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open() doesn't fail, this patch will not introduce any change, if snd_pcm_open() fails, it just retry a couple of times, so it will not introduce the regression in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1887610/+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 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'
@Jpodjarny, Could you please run pa-info > audio-log.txt, then upload the audio- log.txt? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1887610 Title: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode' Status in HWE Next: New Status in OEM Priority Project: In Progress Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Bionic: Confirmed Status in pulseaudio source package in Eoan: Won't Fix Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Bug description: [Impact] On some I+N machines (inlcuding lenovo and dell machines), after setting the graphic mode to perofermance mode, and open the gnome sound seting, run suspend/resume test, the audio devices will disappear from UI, instead a dummy audio shows on the UI, and from then on, the audio can't work anymore. [Fix] The root cause is after resuming, the pulseaudio try to recover the PCM device, but at that moment, the devices nodes at /dev/snd/ are not accessible yet sometimes, it will make snd_pcm_open fail and the pulseaudio will calll unload_module to unload alsa audio card. I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(), this will retry the snd_pcm_open() a couple of times if it fails. [Test Case] Install the pulseaudio wit this fix, set the graphic mode to performance mode, open the sound setting, then run suspend/resume 90 times, after test check the audio devices on the UI, the speaker, digital mic are still on the UI, and they could work well. [Regression Risk] Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open() doesn't fail, this patch will not introduce any change, if snd_pcm_open() fails, it just retry a couple of times, so it will not introduce the regression in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1887610/+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 1781597] Re: [SRU] WoWLAN settings are not supported
** Tags removed: verification-done-cosmic ** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1781597 Title: [SRU] WoWLAN settings are not supported Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Triaged Status in network-manager source package in Cosmic: Fix Released Bug description: [Impact] WoWLAN lets us wake up the system by sending wake packets over the wifi connection. This is something requested by some OEM projects, for bionic server images. NM 1.12 supports configuring this feature, so this can be achieved by backporting that support to 1.10 (bionic version). These are the MPs for cosmic and bionic: https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468 https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465 [Test Case] First, the wifi card must support WoWLAN. This can be checked by running $ iw phy and searching for "WoWLAN support:" in the output. If it is supported, with the patch applied a connection configured with wowlan can be created with: $ sudo nmcli d wifi connect password $ sudo nmcli c modify 802-11-wireless.wake-on-wlan 8 $ sudo nmcli c down $ sudo nmcli c up We can check with 'iw' that WoWLAN is active for the connection: $ iw phy phy0 wowlan show WoWLAN is enabled: * wake up on magic packet In this case we have configured the connection to wake up the system when a 'magic' packet is received. We can then suspend the system with $ sudo systemctl suspend And we should be able to wake the system from another device with the command $ sudo etherwake -i [Regression Potential] Although the patch is not especially small, it is a backport of changes that have been merged upstream, with very little modifications to make it compile in 1.10. It is also a rather isolated feature that should not conflict with existing ones. The feature will be activated only if configured from the command line, so the risk of regressions should be small. Note also that the patch will be removed as soon as Ubuntu moves to NM 1.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+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 1884033] Re: initramfs-tools
** Package changed: ubuntu-release-upgrader (Ubuntu) => initramfs-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1884033 Title: initramfs-tools Status in initramfs-tools package in Ubuntu: New Bug description: 2020-06-18 09:52:28,921 ERROR got an error from dpkg for pkg: 'initramfs-tools': 'installed initramfs-tools package post-installation script subprocess returned error exit status 1' 2020-06-18 09:52:28,921 DEBUG running apport_pkgfailure() initramfs-tools: installed initramfs-tools package post-installation script subprocess returned error exit status 1 2020-06-18 09:52:32,418 ERROR Exception during pm.DoInstall() Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-6xnl7bxz/DistUpgrade/DistUpgradeView.py", line 220, in run res = pm.do_install(self.writefd) apt_pkg.Error: E:Sub-process /usr/bin/dpkg returned an error code (1) 2020-06-18 09:52:32,461 ERROR SystemError from cache.commit(): installArchives() failed 2020-06-18 09:52:32,462 ERROR found exception: 'E:Sub-process /usr/bin/dpkg returned an error code (1)' # lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 # apt-cache policy 500 http://security.ubuntu.com/ubuntu focal-security/universe i386 Packages release v=20.04,o=Ubuntu,a=focal-security,n=focal,l=Ubuntu,c=universe,b=i386 origin security.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1884033/+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 1884033] [NEW] initramfs-tools
You have been subscribed to a public bug: 2020-06-18 09:52:28,921 ERROR got an error from dpkg for pkg: 'initramfs-tools': 'installed initramfs-tools package post-installation script subprocess returned error exit status 1' 2020-06-18 09:52:28,921 DEBUG running apport_pkgfailure() initramfs-tools: installed initramfs-tools package post-installation script subprocess returned error exit status 1 2020-06-18 09:52:32,418 ERROR Exception during pm.DoInstall() Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-6xnl7bxz/DistUpgrade/DistUpgradeView.py", line 220, in run res = pm.do_install(self.writefd) apt_pkg.Error: E:Sub-process /usr/bin/dpkg returned an error code (1) 2020-06-18 09:52:32,461 ERROR SystemError from cache.commit(): installArchives() failed 2020-06-18 09:52:32,462 ERROR found exception: 'E:Sub-process /usr/bin/dpkg returned an error code (1)' # lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 # apt-cache policy 500 http://security.ubuntu.com/ubuntu focal-security/universe i386 Packages release v=20.04,o=Ubuntu,a=focal-security,n=focal,l=Ubuntu,c=universe,b=i386 origin security.ubuntu.com ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- initramfs-tools https://bugs.launchpad.net/bugs/1884033 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. -- 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 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
Yes! Google Chrome. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 jackpoll_ms :
[Touch-packages] [Bug 1885562] Re: [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode
This bug was fixed in the package nss - 2:3.49.1-1ubuntu4 --- nss (2:3.49.1-1ubuntu4) groovy; urgency=medium * Symlink chk files to fix self-verification in FIPS mode (LP: #1885562) -- Dariusz Gadomski Wed, 01 Jul 2020 14:48:13 +0200 ** Changed in: nss (Ubuntu Groovy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1885562 Title: [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode Status in nss package in Ubuntu: Fix Released Status in nss source package in Bionic: In Progress Status in nss source package in Focal: In Progress Status in nss source package in Groovy: Fix Released Bug description: [Impact] * Prevents using some parts of nss in FIPS mode - e.g. libfreeblpriv3.so (failed asserts). The library during initialization tries to verify it's own binaries against signatures in chk files shipped along with it (created at build time). They are installed at /usr/lib/$(DEB_HOST_MULTIARCH)/nss while it tries to look for them at /usr/lib/$(DEB_HOST_MULTIARCH). [Test Case] * Setup Ubuntu 18.04 in FIPS mode. * sudo apt install chrony * sudo chronyd -d * chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed. [Regression Potential] * Fix introduces 2 new artifacts to the filesystem (symlinks to the chk files). It may cause alerts in e.g. CI systems. [Other Info] Original bug description: In FIPS mode there are some additional checks performed. They lead to verifying binaries signatures. Those signatures are shipped in the libnss3 package as *.chk files installed in /usr/lib/$(DEB_HOST_MULTIARCH)/nss. Along with those files are the libraries themselves (libfreebl3.so libfreeblpriv3.so libnssckbi.so libnssdbm3.so libsoftokn3.so). Those libraries are symlinked to be present in /usr/lib/$(DEB_HOST_MULTIARCH): ls -l /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so lrwxrwxrwx 1 root root 21 Jun 10 18:54 /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so -> nss/libfreeblpriv3.so The client binaries are linked against the symlinks, so when the verification happens (lib/freebl/shvfy.c) the mkCheckFileName function takes path to the symlink to the shlib and replaces the .so extension with .chk. Then it tries to open that file. Obviosly it fails, because the actual file is in /usr/lib/$(DEB_HOST_MULTIARCH)/nss. [Test case] sudo apt install chrony sudo chronyd -d chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed. Potential solutions: Solution A: Drop the /usr/lib/$(DEB_HOST_MULTIARCH)/nss directory and put all signatures and libs in /usr/lib/$(DEB_HOST_MULTIARCH). Solution B: Create symlinks to *.chk files in /usr/lib/$(DEB_HOST_MULTIARCH) (like it is done for *.so). Solution C: Implement and upstream NSS feature of resolving symlinks and looking for *.chk where the symlinks lead to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1885562/+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 1887959] Re: Unable to upgrade several qt5 packages (libqt5gui5, …)
Thank you for the quick response. Yes, with that apt seems to be able to resolve the conflicts. ``` $ sudo apt install libqt5core5a Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libqt5dbus5 libqt5gui5 libqt5network5 libqt5printsupport5 libqt5sql5 libqt5svg5 libqt5widgets5 libqt5xml5 Suggested packages: qt5-image-formats-plugins qtwayland5 Recommended packages: qttranslations5-l10n qt5-gtk-platformtheme libqt5sql5-sqlite | libqt5sql5-mysql | libqt5sql5-odbc | libqt5sql5-psql | libqt5sql5-tds | libqt5sql5-ibase The following packages will be REMOVED: automoc kdelibs-bin kdelibs5-dev kdoctools libattica0.4 libdbusmenu-qt2 libkcmutils4 libkde3support4 libkdeclarative5 libkdecore5 libkdesu5 libkdeui5 libkdewebkit5 libkdnssd4 libkemoticons4 libkfile4 libkhtml5 libkidletime4 libkimproxy4 libkio5 libkjsapi4 libkjsembed4 libkmediaplayer4 libknewstuff2-4 libknewstuff3-4 libknotifyconfig4 libkntlm4 libkparts4 libkprintutils4 libkpty4 libkrosscore4 libkrossui4 libktexteditor4 libkunitconversion4 libkutils4 libphonon-dev libphonon4 libplasma3 libqca2 libqt4-dbus libqt4-declarative libqt4-designer libqt4-dev libqt4-dev-bin libqt4-help libqt4-network libqt4-opengl libqt4-qt3support libqt4-script libqt4-scripttools libqt4-sql libqt4-svg libqt4-test libqt4-xml libqt4-xmlpatterns libqtcore4 libqtdbus4 libqtgui4 libqtwebkit4 libsolid4 libthreadweaver4 phonon-backend-null qdbus qt4-linguist-tools The following packages will be upgraded: libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5printsupport5 libqt5sql5 libqt5svg5 libqt5widgets5 libqt5xml5 9 upgraded, 0 newly installed, 64 to remove and 3 not upgraded. Need to get 9,045 kB of archives. After this operation, 207 MB disk space will be freed. ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1887959 Title: Unable to upgrade several qt5 packages (libqt5gui5, …) Status in qtbase-opensource-src package in Ubuntu: New Bug description: After upgrading from Ubuntu 19.10 (maybe 18.04) to 20.04, I am unable to upgrade the packages below. The following packages have been kept back: libboost-date-time-dev libboost-dev libboost-filesystem-dev libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5printsupport5 libqt5sql5 libqt5svg5 libqt5widgets5 libqt5xml5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1887959/+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 1887478] Re: missing symlinks for login and logout files used by gnome
Debian is upstream to Ubuntu. Here is a MR at freedesktop.org. https://gitlab.freedesktop.org/xdg/xdg-sound-theme/-/merge_requests/1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sound-theme-freedesktop in Ubuntu. https://bugs.launchpad.net/bugs/1887478 Title: missing symlinks for login and logout files used by gnome Status in sound-theme-freedesktop package in Ubuntu: Triaged Bug description: Merge request submitted upstream in Debian to fix the issue. https://salsa.debian.org/gnome-team/sound-theme-freedesktop/-/merge_requests/1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1887478/+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 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: In Progress Status in rpcbind source package in Bionic: In Progress Status in rpcbind package in Debian: Fix Released Status in Fedora: Confirmed Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, and also adds a check for the existence of an environment variable "RPCBIND_RMTCALLS_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change the default to remain in place after an upgrade to Focal. Using the environment variable, instead of changing or adding the cmdline parameter, allows anyone using the variable to disable the remote calls default to upgrade to Focal without breaking rpcbind. After the upgrade to Focal, the environment variable (defined in /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored without any change needed to the rpcbind package in Focal or later. [original description] As this backports that functionality, it Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+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 1856428] Re: Disable TLS below 1.2 by default
** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/nss/+git/nss/+merge/387608 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1856428 Title: Disable TLS below 1.2 by default Status in gnutls28 package in Ubuntu: Fix Released Status in golang-1.13 package in Ubuntu: New Status in nss package in Ubuntu: Fix Released Status in openssl package in Ubuntu: Fix Released Bug description: Disable TLS 1.0, TLS1.1, DTLS1.0 As part of focal commitment, we shall disable obsolete protocols by default. Users can override this behaviour with a config file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1856428/+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 1885562] Re: [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode
** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/nss/+git/nss/+merge/387608 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1885562 Title: [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode Status in nss package in Ubuntu: In Progress Status in nss source package in Bionic: In Progress Status in nss source package in Focal: In Progress Status in nss source package in Groovy: In Progress Bug description: [Impact] * Prevents using some parts of nss in FIPS mode - e.g. libfreeblpriv3.so (failed asserts). The library during initialization tries to verify it's own binaries against signatures in chk files shipped along with it (created at build time). They are installed at /usr/lib/$(DEB_HOST_MULTIARCH)/nss while it tries to look for them at /usr/lib/$(DEB_HOST_MULTIARCH). [Test Case] * Setup Ubuntu 18.04 in FIPS mode. * sudo apt install chrony * sudo chronyd -d * chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed. [Regression Potential] * Fix introduces 2 new artifacts to the filesystem (symlinks to the chk files). It may cause alerts in e.g. CI systems. [Other Info] Original bug description: In FIPS mode there are some additional checks performed. They lead to verifying binaries signatures. Those signatures are shipped in the libnss3 package as *.chk files installed in /usr/lib/$(DEB_HOST_MULTIARCH)/nss. Along with those files are the libraries themselves (libfreebl3.so libfreeblpriv3.so libnssckbi.so libnssdbm3.so libsoftokn3.so). Those libraries are symlinked to be present in /usr/lib/$(DEB_HOST_MULTIARCH): ls -l /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so lrwxrwxrwx 1 root root 21 Jun 10 18:54 /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so -> nss/libfreeblpriv3.so The client binaries are linked against the symlinks, so when the verification happens (lib/freebl/shvfy.c) the mkCheckFileName function takes path to the symlink to the shlib and replaces the .so extension with .chk. Then it tries to open that file. Obviosly it fails, because the actual file is in /usr/lib/$(DEB_HOST_MULTIARCH)/nss. [Test case] sudo apt install chrony sudo chronyd -d chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed. Potential solutions: Solution A: Drop the /usr/lib/$(DEB_HOST_MULTIARCH)/nss directory and put all signatures and libs in /usr/lib/$(DEB_HOST_MULTIARCH). Solution B: Create symlinks to *.chk files in /usr/lib/$(DEB_HOST_MULTIARCH) (like it is done for *.so). Solution C: Implement and upstream NSS feature of resolving symlinks and looking for *.chk where the symlinks lead to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1885562/+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 1888004] Re: Bash crashed with exit code 2 after a makefile script ended up with make saying "Clang - no input files"
This issue occurs when using buildscripts and make -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1888004 Title: Bash crashed with exit code 2 after a makefile script ended up with make saying "Clang - no input files" Status in bash package in Ubuntu: New Bug description: Immediately after I ran the build script in bash in vscode, the moment the "clang - no input files" error appeared, bash crashed with an exit code of 2. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity Date: Fri Jul 17 14:30:11 2020 InstallationDate: Installed on 2020-07-06 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1888004/+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 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'
I lost my sound after update: orge2@jorge-Mate-20-4:~$ pactl --version pactl 13.99.1 Compilado con libpulse 13.99.0 Linked con libpulse 13.99.0 jorge2@jorge-Mate-20-4:~$ pactl list short sinks 0 auto_null module-null-sink.c s16le 2ch 44100Hz SUSPENDED jorge2@jorge-Mate-20-4:~$ lspci | grep Audio 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) jorge2@jorge-Mate-20-4:~$ pacmd dump ### Configuration dump generated at Fri Jul 17 14:53:48 2020 ### Configuration dump generated at Fri Jul 17 15:24:44 2020 load-module module-device-restore load-module module-stream-restore load-module module-card-restore load-module module-augment-properties load-module module-switch-on-port-available load-module module-switch-on-connect load-module module-udev-detect load-module module-alsa-card device_id="0" name="pci-_00_1b.0" card_name="alsa_card.pci-_00_1b.0" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1" load-module module-native-protocol-unix load-module module-default-device-restore load-module module-always-sink load-module module-null-sink sink_name=auto_null sink_properties='device.description="Salida Ficticia"' load-module module-intended-roles load-module module-suspend-on-idle load-module module-console-kit load-module module-systemd-login load-module module-position-event-sounds load-module module-role-cork load-module module-snap-policy load-module module-filter-heuristics load-module module-filter-apply load-module module-x11-publish display=:0 xauthority=/home/jorge2/.Xauthority load-module module-x11-cork-request display=:0 xauthority=/home/jorge2/.Xauthority load-module module-x11-xsmp display=:0 xauthority=/home/jorge2/.Xauthority session_manager=local/jorge-Mate-20-4:@/tmp/.ICE-unix/1812,unix/jorge-Mate-20-4:/tmp/.ICE-unix/1812 load-module module-cli-protocol-unix set-sink-volume auto_null 0x101b3 set-sink-mute auto_null no suspend-sink auto_null yes set-source-volume auto_null.monitor 0x1 set-source-mute auto_null.monitor no suspend-source auto_null.monitor yes set-card-profile alsa_card.pci-_00_1b.0 off set-default-sink auto_null set-default-source auto_null.monitor ### EOF jorge2@jorge-Mate-20-4:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1887610 Title: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode' Status in HWE Next: New Status in OEM Priority Project: In Progress Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Bionic: Confirmed Status in pulseaudio source package in Eoan: Won't Fix Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Bug description: [Impact] On some I+N machines (inlcuding lenovo and dell machines), after setting the graphic mode to perofermance mode, and open the gnome sound seting, run suspend/resume test, the audio devices will disappear from UI, instead a dummy audio shows on the UI, and from then on, the audio can't work anymore. [Fix] The root cause is after resuming, the pulseaudio try to recover the PCM device, but at that moment, the devices nodes at /dev/snd/ are not accessible yet sometimes, it will make snd_pcm_open fail and the pulseaudio will calll unload_module to unload alsa audio card. I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(), this will retry the snd_pcm_open() a couple of times if it fails. [Test Case] Install the pulseaudio wit this fix, set the graphic mode to performance mode, open the sound setting, then run suspend/resume 90 times, after test check the audio devices on the UI, the speaker, digital mic are still on the UI, and they could work well. [Regression Risk] Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open() doesn't fail, this patch will not introduce any change, if snd_pcm_open() fails, it just retry a couple of times, so it will not introduce the regression in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1887610/+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 1888004] [NEW] Bash crashed with exit code 2 after a makefile script ended up with make saying "Clang - no input files"
Public bug reported: Immediately after I ran the build script in bash in vscode, the moment the "clang - no input files" error appeared, bash crashed with an exit code of 2. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity Date: Fri Jul 17 14:30:11 2020 InstallationDate: Installed on 2020-07-06 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1888004 Title: Bash crashed with exit code 2 after a makefile script ended up with make saying "Clang - no input files" Status in bash package in Ubuntu: New Bug description: Immediately after I ran the build script in bash in vscode, the moment the "clang - no input files" error appeared, bash crashed with an exit code of 2. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity Date: Fri Jul 17 14:30:11 2020 InstallationDate: Installed on 2020-07-06 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1888004/+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 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
** Description changed: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc - udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind + udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] - this adds a method to disable rpcbind from listening to the 'random' - port. any regression would likely prevent rpcbind from starting, or may - cause problems with the interaction between rpcinfo and rpcbind, as - rpcinfo may use the random reserved port in some cases, as detailed in - the Debian bug. + this adds a way to disable rpcbind from listening to the 'random' port. + any regression would likely prevent rpcbind from starting, or may cause + problems with the interaction between rpcinfo and rpcbind, as rpcinfo + may use the random reserved port in some cases, as detailed in the + Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. - TBD: specific method to disable rmtcalls in backport + Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, + and also adds a check for the existence of an environment variable "RPCBIND_RMTCALLS_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. + This allows 1) retaining the existing default behavior of rpcbind in x + and b, while also 2) providing a mechanism to change that default for + anyone who does *not* want remote calls to be enabled, and 3) allowing + the mechanism to change the default to remain in place after an upgrade + to Focal. Using the environment variable, instead of changing or adding + the cmdline parameter, allows anyone using the variable to disable the + remote calls default to upgrade to Focal without breaking rpcbind. After + the upgrade to Focal, the environment variable (defined in + /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored + without any change needed to the rpcbind package in Focal or later. [original description] As this backports that functionality, it Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: In Progress Status in rpcbind source package in Bionic: In Progress Status in rpcbind package in Debian: Fix Released Status in Fedora: Confirmed Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of
[Touch-packages] [Bug 1869116] Re: smartctl-validate is borked in a recent release
** No longer affects: util-linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869116
Title:
smartctl-validate is borked in a recent release
Status in lxd:
New
Status in MAAS:
Fix Committed
Status in MAAS 2.7 series:
New
Status in MAAS 2.8 series:
New
Bug description:
Bug (maybe?) details first, diatribe second.
Bug Summary: multi-hdd / raid with multiple drives / multiple devices
or something along those lines cannot be commissioned anymore: 2.4.x
worked fine, 2.7.0 does not.
Here is the script output of smartctl-validate:
-
# /dev/sda (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66c9220df4ac)
Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial
'6842b2b0740e9900260e66c9220df4ac' not found!
This indicates the storage device has been removed or the OS is unable to
find it due to a hardware failure. Please re-commission this node to
re-discover the storage devices, or delete this device manually.
Given parameters:
{'storage': {'argument_format': '{path
}', 'type': 'storage', 'value': {'id_path':
'/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66c9220df4ac', 'model': 'PERC 6/i',
'name': 'sda', 'physical_blockdevice_id': 33, 'serial':
'6842b2b0740e9900260e66c9220df4ac'
}
}
}
Discovered storage devices: [
{'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66c9220df4ac'
},
{'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66f924ecece0'
},
{'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL':
'10092013112645'
}
]
Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1'
}
-
-
# /dev/sdb (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66f924ecece0)
Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial
'6842b2b0740e9900260e66f924ecece0' not found!
This indicates the storage device has been removed or the OS is unable to
find it due to a hardware failure. Please re-commission this node to
re-discover the storage devices, or delete this device manually.
Given parameters: {'storage': {'argument_format': '{path
}', 'type': 'storage', 'value': {'id_path':
'/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66f924ecece0', 'model': 'PERC 6/i',
'name': 'sdb', 'physical_blockdevice_id': 34, 'serial':
'6842b2b0740e9900260e66f924ecece0'
}
}
}
Discovered storage devices: [
{'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66c9220df4ac'
},
{'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66f924ecece0'
},
{'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL':
'10092013112645'
}
]
Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1'
}
-
You can see that it says the storage cannot be found and immediately
lists it as a discovered device. It does it for both tests (one for
each drive), and for both servers
Bug Details:
I had maas 2.4.x for the longest time over my journey (see below journey) and
have never had any problems re-commissioning (or deleting and re-discovering
over boot PXE) 2 of my servers (r610, r710).
r610 has an iPERC 6, four 10K X00GB drives configured in a RAID10, 1 virtual
disk.
r710 has an iPERC 6, 6x 2TB drives, configured in a RAID10, 2 virtual disks
So commission after commission trying to get through my journey, 0
problems. After I finally get everything figured out on the juju,
network/vlan, quad-nic end, I go to re-commission and I cannot.
smartctl-validate fails on both, over and over again. I even destroyed
and re-created the raid/VDs, still not.
After spending so much time on it I remembered that it was the first
time I had tried to re-commission these two servers since doing an
upgrade from 2.4.x->2.7 in an effort to use the updated KVM
integration to add a couple more guests. Once I got all everything
figured out I went to re-commission everything and boom.
[Upgrade path notes]
In full disclosure, in case this matters. I was on apt install of 2.4.x and
using snap for 2.7, except it didn't work. So I read on how to do apt 2.7 and
did that and did not uninstall snap 2.7 yet. I wanted to migrate from apt to
snap but do not know how to without losing all maas data and could not find
docs on it, so a problem for another day. But in case that is part of the
problem for some odd reason, I wanted to share.
[Diatribe]
My journey to get maas+juju+openstack+kubernets has been less then stellar. I
have ran into problem after problem; albeit some of which were my own. I am so
close, after spending the last 6 months on/off when I had time, and really
hardcore the last 4 days. The last half day of which has been this little gem.
Maas has been pretty fun to work with but some thing
[Touch-packages] [Bug 1869116] Re: smartctl-validate is borked in a recent release
** Changed in: maas
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869116
Title:
smartctl-validate is borked in a recent release
Status in lxd:
New
Status in MAAS:
Fix Committed
Status in MAAS 2.7 series:
New
Status in MAAS 2.8 series:
New
Bug description:
Bug (maybe?) details first, diatribe second.
Bug Summary: multi-hdd / raid with multiple drives / multiple devices
or something along those lines cannot be commissioned anymore: 2.4.x
worked fine, 2.7.0 does not.
Here is the script output of smartctl-validate:
-
# /dev/sda (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66c9220df4ac)
Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial
'6842b2b0740e9900260e66c9220df4ac' not found!
This indicates the storage device has been removed or the OS is unable to
find it due to a hardware failure. Please re-commission this node to
re-discover the storage devices, or delete this device manually.
Given parameters:
{'storage': {'argument_format': '{path
}', 'type': 'storage', 'value': {'id_path':
'/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66c9220df4ac', 'model': 'PERC 6/i',
'name': 'sda', 'physical_blockdevice_id': 33, 'serial':
'6842b2b0740e9900260e66c9220df4ac'
}
}
}
Discovered storage devices: [
{'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66c9220df4ac'
},
{'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66f924ecece0'
},
{'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL':
'10092013112645'
}
]
Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1'
}
-
-
# /dev/sdb (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66f924ecece0)
Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial
'6842b2b0740e9900260e66f924ecece0' not found!
This indicates the storage device has been removed or the OS is unable to
find it due to a hardware failure. Please re-commission this node to
re-discover the storage devices, or delete this device manually.
Given parameters: {'storage': {'argument_format': '{path
}', 'type': 'storage', 'value': {'id_path':
'/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66f924ecece0', 'model': 'PERC 6/i',
'name': 'sdb', 'physical_blockdevice_id': 34, 'serial':
'6842b2b0740e9900260e66f924ecece0'
}
}
}
Discovered storage devices: [
{'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66c9220df4ac'
},
{'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66f924ecece0'
},
{'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL':
'10092013112645'
}
]
Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1'
}
-
You can see that it says the storage cannot be found and immediately
lists it as a discovered device. It does it for both tests (one for
each drive), and for both servers
Bug Details:
I had maas 2.4.x for the longest time over my journey (see below journey) and
have never had any problems re-commissioning (or deleting and re-discovering
over boot PXE) 2 of my servers (r610, r710).
r610 has an iPERC 6, four 10K X00GB drives configured in a RAID10, 1 virtual
disk.
r710 has an iPERC 6, 6x 2TB drives, configured in a RAID10, 2 virtual disks
So commission after commission trying to get through my journey, 0
problems. After I finally get everything figured out on the juju,
network/vlan, quad-nic end, I go to re-commission and I cannot.
smartctl-validate fails on both, over and over again. I even destroyed
and re-created the raid/VDs, still not.
After spending so much time on it I remembered that it was the first
time I had tried to re-commission these two servers since doing an
upgrade from 2.4.x->2.7 in an effort to use the updated KVM
integration to add a couple more guests. Once I got all everything
figured out I went to re-commission everything and boom.
[Upgrade path notes]
In full disclosure, in case this matters. I was on apt install of 2.4.x and
using snap for 2.7, except it didn't work. So I read on how to do apt 2.7 and
did that and did not uninstall snap 2.7 yet. I wanted to migrate from apt to
snap but do not know how to without losing all maas data and could not find
docs on it, so a problem for another day. But in case that is part of the
problem for some odd reason, I wanted to share.
[Diatribe]
My journey to get maas+juju+openstack+kubernets has been less then stellar. I
have ran into problem after problem; albeit some of which were my own. I am so
close, after spending the last 6 months on/off when I had time, and really
hardcore the last 4 days. The last half day of which has been this little gem.
Maas has been pretty fun to work with
[Touch-packages] [Bug 1672931] Re: [regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of native GTK/Qt (and so menus don't appear in the titlebar)
** Changed in: libertine/devel Status: In Progress => Triaged ** Changed in: libertine/devel Assignee: Christopher Townsend (townsend) => (unassigned) ** Changed in: libertine/devel Milestone: 1.8 => None ** Changed in: libertine/trunk Milestone: 1.8 => None ** Changed in: ubuntu-app-launch (Ubuntu) Status: In Progress => Triaged ** Changed in: ubuntu-app-launch (Ubuntu) Assignee: Christopher Townsend (townsend) => (unassigned) ** Changed in: xorg-server (Ubuntu) Status: In Progress => Triaged ** Changed in: xorg-server (Ubuntu) Assignee: Christopher Townsend (townsend) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1672931 Title: [regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of native GTK/Qt (and so menus don't appear in the titlebar) Status in Canonical System Image: Confirmed Status in Libertine: Triaged Status in Libertine devel series: Triaged Status in Libertine trunk series: Triaged Status in gtk+3.0 package in Ubuntu: Fix Released Status in libertine package in Ubuntu: Triaged Status in qtubuntu package in Ubuntu: Confirmed Status in ubuntu-app-launch package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Triaged Bug description: Qt & GTK apps on Unity8 are defaulting to Xmir instead of native GTK/Qt on Mir. I noticed a slight change in appearance and performance, but also: dan 25410 0.1 0.2 423316 38996 ?Sl 11:14 0:00 Xmir -rootless -displayfd 3 -mir org.gnome.Calculator dan 25456 1.8 0.5 606084 91736 ?Sl 11:14 0:03 Xmir -rootless -displayfd 3 -mir org.gnome.Nautilus dan 25611 1.7 0.2 345312 35520 ?Sl 11:18 0:00 Xmir -rootless -displayfd 3 -mir webbrowser-app_webbrowser-app_10 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672931/+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 1869116] Re: smartctl-validate is borked in a recent release
** Also affects: maas/2.7
Importance: Undecided
Status: New
** Changed in: maas/2.7
Importance: Undecided => Critical
** Changed in: maas/2.7
Assignee: (unassigned) => Lee Trager (ltrager)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869116
Title:
smartctl-validate is borked in a recent release
Status in lxd:
New
Status in MAAS:
Triaged
Status in MAAS 2.7 series:
New
Status in MAAS 2.8 series:
New
Status in util-linux package in Ubuntu:
Confirmed
Bug description:
Bug (maybe?) details first, diatribe second.
Bug Summary: multi-hdd / raid with multiple drives / multiple devices
or something along those lines cannot be commissioned anymore: 2.4.x
worked fine, 2.7.0 does not.
Here is the script output of smartctl-validate:
-
# /dev/sda (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66c9220df4ac)
Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial
'6842b2b0740e9900260e66c9220df4ac' not found!
This indicates the storage device has been removed or the OS is unable to
find it due to a hardware failure. Please re-commission this node to
re-discover the storage devices, or delete this device manually.
Given parameters:
{'storage': {'argument_format': '{path
}', 'type': 'storage', 'value': {'id_path':
'/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66c9220df4ac', 'model': 'PERC 6/i',
'name': 'sda', 'physical_blockdevice_id': 33, 'serial':
'6842b2b0740e9900260e66c9220df4ac'
}
}
}
Discovered storage devices: [
{'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66c9220df4ac'
},
{'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66f924ecece0'
},
{'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL':
'10092013112645'
}
]
Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1'
}
-
-
# /dev/sdb (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66f924ecece0)
Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial
'6842b2b0740e9900260e66f924ecece0' not found!
This indicates the storage device has been removed or the OS is unable to
find it due to a hardware failure. Please re-commission this node to
re-discover the storage devices, or delete this device manually.
Given parameters: {'storage': {'argument_format': '{path
}', 'type': 'storage', 'value': {'id_path':
'/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66f924ecece0', 'model': 'PERC 6/i',
'name': 'sdb', 'physical_blockdevice_id': 34, 'serial':
'6842b2b0740e9900260e66f924ecece0'
}
}
}
Discovered storage devices: [
{'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66c9220df4ac'
},
{'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66f924ecece0'
},
{'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL':
'10092013112645'
}
]
Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1'
}
-
You can see that it says the storage cannot be found and immediately
lists it as a discovered device. It does it for both tests (one for
each drive), and for both servers
Bug Details:
I had maas 2.4.x for the longest time over my journey (see below journey) and
have never had any problems re-commissioning (or deleting and re-discovering
over boot PXE) 2 of my servers (r610, r710).
r610 has an iPERC 6, four 10K X00GB drives configured in a RAID10, 1 virtual
disk.
r710 has an iPERC 6, 6x 2TB drives, configured in a RAID10, 2 virtual disks
So commission after commission trying to get through my journey, 0
problems. After I finally get everything figured out on the juju,
network/vlan, quad-nic end, I go to re-commission and I cannot.
smartctl-validate fails on both, over and over again. I even destroyed
and re-created the raid/VDs, still not.
After spending so much time on it I remembered that it was the first
time I had tried to re-commission these two servers since doing an
upgrade from 2.4.x->2.7 in an effort to use the updated KVM
integration to add a couple more guests. Once I got all everything
figured out I went to re-commission everything and boom.
[Upgrade path notes]
In full disclosure, in case this matters. I was on apt install of 2.4.x and
using snap for 2.7, except it didn't work. So I read on how to do apt 2.7 and
did that and did not uninstall snap 2.7 yet. I wanted to migrate from apt to
snap but do not know how to without losing all maas data and could not find
docs on it, so a problem for another day. But in case that is part of the
problem for some odd reason, I wanted to share.
[Diatribe]
My journey to get maas+juju+openstack+kubernets has been less then stellar. I
have ran into problem after problem; albeit some of which were my own. I am so
[Touch-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
In addition, After closing all applications and trying, the sound works again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 jackpoll_ms :
[Touch-packages] [Bug 1869116] Re: smartctl-validate is borked in a recent release
** Merge proposal linked:
https://code.launchpad.net/~ltrager/maas/+git/maas/+merge/387605
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869116
Title:
smartctl-validate is borked in a recent release
Status in lxd:
New
Status in MAAS:
Triaged
Status in MAAS 2.7 series:
New
Status in MAAS 2.8 series:
New
Status in util-linux package in Ubuntu:
Confirmed
Bug description:
Bug (maybe?) details first, diatribe second.
Bug Summary: multi-hdd / raid with multiple drives / multiple devices
or something along those lines cannot be commissioned anymore: 2.4.x
worked fine, 2.7.0 does not.
Here is the script output of smartctl-validate:
-
# /dev/sda (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66c9220df4ac)
Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial
'6842b2b0740e9900260e66c9220df4ac' not found!
This indicates the storage device has been removed or the OS is unable to
find it due to a hardware failure. Please re-commission this node to
re-discover the storage devices, or delete this device manually.
Given parameters:
{'storage': {'argument_format': '{path
}', 'type': 'storage', 'value': {'id_path':
'/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66c9220df4ac', 'model': 'PERC 6/i',
'name': 'sda', 'physical_blockdevice_id': 33, 'serial':
'6842b2b0740e9900260e66c9220df4ac'
}
}
}
Discovered storage devices: [
{'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66c9220df4ac'
},
{'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66f924ecece0'
},
{'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL':
'10092013112645'
}
]
Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1'
}
-
-
# /dev/sdb (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66f924ecece0)
Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial
'6842b2b0740e9900260e66f924ecece0' not found!
This indicates the storage device has been removed or the OS is unable to
find it due to a hardware failure. Please re-commission this node to
re-discover the storage devices, or delete this device manually.
Given parameters: {'storage': {'argument_format': '{path
}', 'type': 'storage', 'value': {'id_path':
'/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66f924ecece0', 'model': 'PERC 6/i',
'name': 'sdb', 'physical_blockdevice_id': 34, 'serial':
'6842b2b0740e9900260e66f924ecece0'
}
}
}
Discovered storage devices: [
{'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66c9220df4ac'
},
{'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66f924ecece0'
},
{'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL':
'10092013112645'
}
]
Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1'
}
-
You can see that it says the storage cannot be found and immediately
lists it as a discovered device. It does it for both tests (one for
each drive), and for both servers
Bug Details:
I had maas 2.4.x for the longest time over my journey (see below journey) and
have never had any problems re-commissioning (or deleting and re-discovering
over boot PXE) 2 of my servers (r610, r710).
r610 has an iPERC 6, four 10K X00GB drives configured in a RAID10, 1 virtual
disk.
r710 has an iPERC 6, 6x 2TB drives, configured in a RAID10, 2 virtual disks
So commission after commission trying to get through my journey, 0
problems. After I finally get everything figured out on the juju,
network/vlan, quad-nic end, I go to re-commission and I cannot.
smartctl-validate fails on both, over and over again. I even destroyed
and re-created the raid/VDs, still not.
After spending so much time on it I remembered that it was the first
time I had tried to re-commission these two servers since doing an
upgrade from 2.4.x->2.7 in an effort to use the updated KVM
integration to add a couple more guests. Once I got all everything
figured out I went to re-commission everything and boom.
[Upgrade path notes]
In full disclosure, in case this matters. I was on apt install of 2.4.x and
using snap for 2.7, except it didn't work. So I read on how to do apt 2.7 and
did that and did not uninstall snap 2.7 yet. I wanted to migrate from apt to
snap but do not know how to without losing all maas data and could not find
docs on it, so a problem for another day. But in case that is part of the
problem for some odd reason, I wanted to share.
[Diatribe]
My journey to get maas+juju+openstack+kubernets has been less then stellar. I
have ran into problem after problem; albeit some of which were my own. I am so
close, after spending the last 6 months on/off when I had time, and really
hardcore the last 4 days. The last
[Touch-packages] [Bug 1869116] Re: smartctl-validate is borked in a recent release
** Merge proposal linked:
https://code.launchpad.net/~ltrager/maas/+git/maas/+merge/387603
** Merge proposal linked:
https://code.launchpad.net/~ltrager/maas/+git/maas/+merge/387604
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869116
Title:
smartctl-validate is borked in a recent release
Status in lxd:
New
Status in MAAS:
Triaged
Status in MAAS 2.7 series:
New
Status in MAAS 2.8 series:
New
Status in util-linux package in Ubuntu:
Confirmed
Bug description:
Bug (maybe?) details first, diatribe second.
Bug Summary: multi-hdd / raid with multiple drives / multiple devices
or something along those lines cannot be commissioned anymore: 2.4.x
worked fine, 2.7.0 does not.
Here is the script output of smartctl-validate:
-
# /dev/sda (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66c9220df4ac)
Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial
'6842b2b0740e9900260e66c9220df4ac' not found!
This indicates the storage device has been removed or the OS is unable to
find it due to a hardware failure. Please re-commission this node to
re-discover the storage devices, or delete this device manually.
Given parameters:
{'storage': {'argument_format': '{path
}', 'type': 'storage', 'value': {'id_path':
'/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66c9220df4ac', 'model': 'PERC 6/i',
'name': 'sda', 'physical_blockdevice_id': 33, 'serial':
'6842b2b0740e9900260e66c9220df4ac'
}
}
}
Discovered storage devices: [
{'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66c9220df4ac'
},
{'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66f924ecece0'
},
{'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL':
'10092013112645'
}
]
Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1'
}
-
-
# /dev/sdb (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66f924ecece0)
Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial
'6842b2b0740e9900260e66f924ecece0' not found!
This indicates the storage device has been removed or the OS is unable to
find it due to a hardware failure. Please re-commission this node to
re-discover the storage devices, or delete this device manually.
Given parameters: {'storage': {'argument_format': '{path
}', 'type': 'storage', 'value': {'id_path':
'/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66f924ecece0', 'model': 'PERC 6/i',
'name': 'sdb', 'physical_blockdevice_id': 34, 'serial':
'6842b2b0740e9900260e66f924ecece0'
}
}
}
Discovered storage devices: [
{'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66c9220df4ac'
},
{'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66f924ecece0'
},
{'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL':
'10092013112645'
}
]
Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1'
}
-
You can see that it says the storage cannot be found and immediately
lists it as a discovered device. It does it for both tests (one for
each drive), and for both servers
Bug Details:
I had maas 2.4.x for the longest time over my journey (see below journey) and
have never had any problems re-commissioning (or deleting and re-discovering
over boot PXE) 2 of my servers (r610, r710).
r610 has an iPERC 6, four 10K X00GB drives configured in a RAID10, 1 virtual
disk.
r710 has an iPERC 6, 6x 2TB drives, configured in a RAID10, 2 virtual disks
So commission after commission trying to get through my journey, 0
problems. After I finally get everything figured out on the juju,
network/vlan, quad-nic end, I go to re-commission and I cannot.
smartctl-validate fails on both, over and over again. I even destroyed
and re-created the raid/VDs, still not.
After spending so much time on it I remembered that it was the first
time I had tried to re-commission these two servers since doing an
upgrade from 2.4.x->2.7 in an effort to use the updated KVM
integration to add a couple more guests. Once I got all everything
figured out I went to re-commission everything and boom.
[Upgrade path notes]
In full disclosure, in case this matters. I was on apt install of 2.4.x and
using snap for 2.7, except it didn't work. So I read on how to do apt 2.7 and
did that and did not uninstall snap 2.7 yet. I wanted to migrate from apt to
snap but do not know how to without losing all maas data and could not find
docs on it, so a problem for another day. But in case that is part of the
problem for some odd reason, I wanted to share.
[Diatribe]
My journey to get maas+juju+openstack+kubernets has been less then stellar. I
have ran into problem after problem; albeit some of which were my own. I am so
close, after
[Touch-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
Hello, I opened YouTube, using chrome, and there is no sound. I tried firefox, and I was also unsuccessful! The speakers are making little pops! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index :
[Touch-packages] [Bug 1887977] Re: Bluetooth headset is not reconnecting automatically if disconnected in between
** Description changed: Some times Bluetooth headset is not reconnecting automatically if disconnected in between. I need to remove the bluetooth headset and again pair it, then it is connecting. 1. Ubuntu Version - 20.04 2. Software version - bluez Installed: 5.53-0ubuntu3 3. Expected result : Every time when I restart the laptop or resume it the headset should connect automatically - 4. Some times when I restart the laptop or resume the laptop, then eventhough headset is switched on bluetooth connection is not established. Instead if I remove the the headset from bluetooth list and again newly pair it with laptop then headset it connected. Verified the bluetooth head set by connecting it to mobile phone and other os like windows/mac os and it seems there is no issue with headset. + 4. Issues Faced : Some times when I restart the laptop or resume the laptop, then eventhough headset is switched on bluetooth connection is not established. Instead if I remove the the headset from bluetooth list and again newly pair it with laptop then headset it connected. Verified the bluetooth head set by connecting it to mobile phone and other os like windows/mac os and it seems there is no issue with headset. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 17 19:58:10 2020 InstallationDate: Installed on 2020-05-04 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 002: ID 0408:a060 Quanta Computer, Inc. HD Webcam - Bus 001 Device 003: ID 8087:0aaa Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 0408:a060 Quanta Computer, Inc. HD Webcam + Bus 001 Device 003: ID 8087:0aaa Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a609dea6-45d9-4ed8-8a46-ba56dae5a117 ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.19 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.19 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.19 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.19:bd07/13/2018:svnAcer:pnNitroAN515-52:pvrV1.19:rvnCFL:rnFreed_CFS:rvrV1.19:cvnAcer:ct10:cvrV1.19: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.19 dmi.sys.vendor: Acer hciconfig: - hci0:Type: Primary Bus: USB - BD Address: 18:56:80:A6:CA:8D ACL MTU: 1021:4 SCO MTU: 96:6 - UP RUNNING PSCAN - RX bytes:16973 acl:0 sco:0 events:2752 errors:0 - TX bytes:678011 acl:0 sco:0 commands:2750 errors:0 + hci0:Type: Primary Bus: USB + BD Address: 18:56:80:A6:CA:8D ACL MTU: 1021:4 SCO MTU: 96:6 + UP RUNNING PSCAN + RX bytes:16973 acl:0 sco:0 events:2752 errors:0 + TX bytes:678011 acl:0 sco:0 commands:2750 errors:0 -- 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/1887977 Title: Bluetooth headset is not reconnecting automatically if disconnected in between Status in bluez package in Ubuntu: New Bug description: Some times Bluetooth headset is not reconnecting automatically if disconnected in between. I need to remove the bluetooth headset and again pair it, then it is connecting. 1. Ubuntu Version - 20.04 2. Software version - bluez Installed: 5.53-0ubuntu3 3. Expected result : Every time when I restart the laptop or resume it the headset should connect automatically 4. Issues Faced : Some times when I restart the laptop or resume the laptop, then eventhough headset is switched on bluetooth connection is not established. Instead if I remove the the headset from bluetooth list and again newly pair it with laptop then headset it connected. Verified the bluetooth head set by connecting it to mobile phone and other os like windows/mac os and it seems there is no issue with headset. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules:
[Touch-packages] [Bug 1882494] Re: [UBUNTU 20.04] zlib not working on all s390x systems configurations
** Changed in: zlib (Ubuntu Eoan) Status: Invalid => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1882494 Title: [UBUNTU 20.04] zlib not working on all s390x systems configurations Status in Ubuntu on IBM z Systems: Triaged Status in zlib package in Ubuntu: New Status in zlib source package in Eoan: Won't Fix Status in zlib source package in Focal: New Status in zlib source package in Groovy: New Bug description: Pull request (https://github.com/madler/zlib/pull/410) and tagged https://github.com/iii-i/zlib/tree/dfltcc-20200511. The new code contains the following improvements: * Added support for switching between software and hardware compression. * Added --dfltcc configure flag (the old way of building it still works). Switching between software and hardware compression is not simply a nice-to-have feature, but is actually required by Java - that's why we are requesting an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882494/+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 1887959] Re: Unable to upgrade several qt5 packages (libqt5gui5, …)
What happens when you try to "apt install libqt5core5a"? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1887959 Title: Unable to upgrade several qt5 packages (libqt5gui5, …) Status in qtbase-opensource-src package in Ubuntu: New Bug description: After upgrading from Ubuntu 19.10 (maybe 18.04) to 20.04, I am unable to upgrade the packages below. The following packages have been kept back: libboost-date-time-dev libboost-dev libboost-filesystem-dev libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5printsupport5 libqt5sql5 libqt5svg5 libqt5widgets5 libqt5xml5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1887959/+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 1884265] Re: [fips] ntpq segfaults when attempting to use MD5 from FIPS-openssl library.
ACK on the debdiff in comment #11, uploaded with a slight LP tag fix for
processing by the SRU team. Thanks!
** Changed in: openssl (Ubuntu Bionic)
Status: Confirmed => In Progress
--
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/1884265
Title:
[fips] ntpq segfaults when attempting to use MD5 from FIPS-openssl
library.
Status in openssl package in Ubuntu:
In Progress
Status in openssl source package in Bionic:
In Progress
Bug description:
[Impact]
In FIPS mode on Bionic MD5 is semi-disabled causing some applications to
segfault.
ntpq uses crypto hashes to authenticate its requests. By default it
uses md5. However, when compiled with openssl it creates a lists of
acceptable hashes from openssl that can be used.
This issue is only applicable in bionic and when using fips-openssl.
[Test Steps]
Test case:
sudo apt install ntp
ntpq -p
Segmentation fault (core dumped)
What happens there is ntpq wants to iterate all available digests
(list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this
task.
EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c.
For FIPS mode it adds:
EVP_add_digest(EVP_md5());
What happens later in ntpq is (list_md_fn function inside ntpq.c):
ctx = EVP_MD_CTX_new();
EVP_DigestInit(ctx, EVP_get_digestbyname(name));
EVP_DigestFinal(ctx, digest, _len);
First digest it gets is MD5, but while running EVP_DigestInit for it, it gets
to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex):
#ifdef OPENSSL_FIPS
if (FIPS_mode()) {
if (!(type->flags & EVP_MD_FLAG_FIPS)
&& !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
return 0;
}
}
#endif
Due to type->flags for MD5 being 0 there's an error set
(EVP_R_DISABLED_FOR_FIPS).
After getting back to ntpq.c:
ctx->engine and ctx->digest are not set (due to the mentioned error), hence
inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c)
OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE);
causes a segfault (ctx->digest is NULL).
So either MD5 shouldn't be added in FIPS mode or it should have the
EVP_MD_FLAG_FIPS to be properly initialized.
[Regression Potential]
I don't think this should regress ntpq + openssl from the Ubuntu
archive.
Current archive ntpq + openssl behaviour:
openssl includes all message digests and hands ntpq a sorted digest-list.
ntpq doesn't check return from EVP_Digest(Init|Final) and assumes all is well
and sticks all digests into its list regardless if it is working or not.
i.e.
ntpq> help keytype
function: set key type to use for authenticated requests, one of:
MD4, MD5, RIPEMD160, SHA1, SHAKE128
If somehow openssl library is corrupted and sends back erroneous
results, its possible the authentication will just not ever work.
Newly fixed archive ntpq + oenssl beahviour:
openssl includes all message digests and hands ntpq a sorted digest-list.
ntpq checks each one and includes each working digest. With a non-corrupted
openssl, everything works fine and ntpq includes each into its list. Ends up
with a list identical to the one above.
If somehow opensll library is corrupted and sends back erroneous
results, ntpq will hopefully catch it by checking return code and
include only those algos that appear to be working. Its possible
authentication will work for ntpq.
The difference will be seen in ntpq + fips-openssl. ntpq will check
return, and for fips-not-approved algos, return will indicate an
error. So these algos will be skipped and ntpq will not include into
its digest list. Resulting in a much shorter list of only fips-
approved algos.
i.e.
ntpq> help keytype
function: set key type to use for authenticated requests, one of:
SHA1, SHAKE128
Since md5 is ntpq's default auth algo, this will need to be changed to one of
the above algos in the config files.
But I think it is somewhat understood that MD5 is bad in a FIPS environment.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1884265/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
I'm having similar issues to this bug and those described by Dmitrii in https://bugs.launchpad.net/charm-ceph-osd/+bug/1883585 specifically comment #2 and the last comment. It appears that if I run 'udevadm trigger --subsystem-match=block', I get my by-dname devices for bcaches, but if I run udevadm trigger w/out a subsystem match, something is triggering later than the block subsystem that is removing the links. Here are the runs with --verbose to show what appears to be getting probed on each run: https://pastebin.ubuntu.com/p/VPvSKRfGt4/ This is with 5.3.0-62 kernel on Bionic. I also have core and canonical-livepatch snaps installed as did the environment where Dmitrii has run into this. -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: New Status in linux source package in Bionic: New Status in linux-signed source package in Bionic: New Status in systemd source package in Bionic: New Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Triaged Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
Relevant package revisions for comment #50: bcache-tools 1.0.8-2build1 snapd2.45.1+18.04.2 systemd 237-3ubuntu10.41 udev 237-3ubuntu10.41 and snaps: Name VersionRev Tracking Publisher Notes canonical-livepatch 9.5.5 95latest/stable canonical✓ - core 16-2.45.2 9665 latest/stable canonical✓ core -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: New Status in linux source package in Bionic: New Status in linux-signed source package in Bionic: New Status in systemd source package in Bionic: New Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Triaged Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1882494] Re: [UBUNTU 20.04] zlib not working on all s390x systems configurations
Changing the Eoan entry to Invalid, since Eoan reached it's EOL: https://lists.ubuntu.com/archives/ubuntu-announce/2020-July/000258.html ** Changed in: zlib (Ubuntu Eoan) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1882494 Title: [UBUNTU 20.04] zlib not working on all s390x systems configurations Status in Ubuntu on IBM z Systems: Triaged Status in zlib package in Ubuntu: New Status in zlib source package in Eoan: Invalid Status in zlib source package in Focal: New Status in zlib source package in Groovy: New Bug description: Pull request (https://github.com/madler/zlib/pull/410) and tagged https://github.com/iii-i/zlib/tree/dfltcc-20200511. The new code contains the following improvements: * Added support for switching between software and hardware compression. * Added --dfltcc configure flag (the old way of building it still works). Switching between software and hardware compression is not simply a nice-to-have feature, but is actually required by Java - that's why we are requesting an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882494/+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 1887968] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1887968/+attachment/5393575/+files/Lspci.txt
--
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/1887968
Title:
Pairing with bluetooth mice fails
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a .Raz
65 72 20 41 74 68 65 72
[Touch-packages] [Bug 1887968] Re: Pairing with bluetooth mice fails
Hi Sebastien,
journalctl log Attached.
** Attachment added: "journalctl.txt"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887968/+attachment/5393587/+files/journalctl.txt
--
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/1887968
Title:
Pairing with bluetooth mice fails
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a
[Touch-packages] [Bug 1887968] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1887968/+attachment/5393584/+files/ProcModules.txt
--
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/1887968
Title:
Pairing with bluetooth mice fails
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a .Raz
65 72 20 41
[Touch-packages] [Bug 1887968] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1887968/+attachment/5393583/+files/ProcInterrupts.txt
--
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/1887968
Title:
Pairing with bluetooth mice fails
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a .Raz
65 72
[Touch-packages] [Bug 1887968] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1887968/+attachment/5393585/+files/UdevDb.txt
--
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/1887968
Title:
Pairing with bluetooth mice fails
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a .Raz
65 72 20 41 74 68 65
[Touch-packages] [Bug 1887572] Re: rsync blocked in -proposed due to configure.sh warning (dep8 test)
This bug was fixed in the package rsync - 3.2.1-1ubuntu2 --- rsync (3.2.1-1ubuntu2) groovy; urgency=medium * d/t/upstream-tests: Don't quote $CROSS_COMPILE when invoking configure.sh. When we do it, the script will mistakenly generate a warning to stderr saying that "you should use --build, --host, --target", which will make the test fail. (LP: #1887572) -- Sergio Durigan Junior Tue, 14 Jul 2020 15:34:24 -0400 ** Changed in: rsync (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1887572 Title: rsync blocked in -proposed due to configure.sh warning (dep8 test) Status in rsync package in Ubuntu: Fix Released Bug description: rsync 3.2.1-1ubuntu1 has been blocked in proposed due to a problem when invoking configure.sh inside the debian/tests/upstream-tests script: autopkgtest [18:04:18]: summary upstream-tests FAIL stderr: configure.sh: WARNING: you should use --build, --host, --target Exit request sent. The problem is that configure.sh is being executed like this: ./configure.sh "$CROSS_COMPILE" in this scenario, $CROSS_COMPILE is an empty variable, which means that this will evaluate to: ./configure.sh "" which will trigger the autotools warning above. The easy solution here is to just remove the quotes. I'm working on this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1887572/+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 1887968] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1887968/+attachment/5393576/+files/Lspci-vt.txt
--
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/1887968
Title:
Pairing with bluetooth mice fails
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a .Raz
65 72 20 41 74 68
[Touch-packages] [Bug 1887968] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1887968/+attachment/5393582/+files/ProcEnviron.txt
--
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/1887968
Title:
Pairing with bluetooth mice fails
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a .Raz
65 72 20 41
[Touch-packages] [Bug 1887968] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1887968/+attachment/5393578/+files/Lsusb-t.txt
--
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/1887968
Title:
Pairing with bluetooth mice fails
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a .Raz
65 72 20 41 74 68
[Touch-packages] [Bug 1887968] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1887968/+attachment/5393579/+files/Lsusb-v.txt
--
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/1887968
Title:
Pairing with bluetooth mice fails
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a .Raz
65 72 20 41 74 68
[Touch-packages] [Bug 1887968] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1887968/+attachment/5393581/+files/ProcCpuinfoMinimal.txt
--
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/1887968
Title:
Pairing with bluetooth mice fails
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a .Raz
[Touch-packages] [Bug 1887968] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1887968/+attachment/5393580/+files/ProcCpuinfo.txt
--
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/1887968
Title:
Pairing with bluetooth mice fails
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a .Raz
65 72 20 41
[Touch-packages] [Bug 1887968] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1887968/+attachment/5393577/+files/Lsusb.txt
--
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/1887968
Title:
Pairing with bluetooth mice fails
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a .Raz
65 72 20 41 74 68 65 72
[Touch-packages] [Bug 1887968] Dependencies.txt
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1887968/+attachment/5393574/+files/Dependencies.txt
--
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/1887968
Title:
Pairing with bluetooth mice fails
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a .Raz
65 72 20
[Touch-packages] [Bug 1887968] Re: Pairing with bluetooth mice fails
apport information
** Tags added: apport-collected focal
** Description changed:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems to
use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice. However
bluetooth seems to work with other devices. I'm under the impression
that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a .Raz
65 72 20 41 74 68 65 72 69 73er Atheris
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#6 [hci0] 8.343656
Extended scan: Disabled (0x00)
Filter duplicates: Disabled (0x00)
Duration: 0 msec (0x)
[Touch-packages] [Bug 1887977] [NEW] Bluetooth headset is not reconnecting automatically if disconnected in between
Public bug reported: Some times Bluetooth headset is not reconnecting automatically if disconnected in between. I need to remove the bluetooth headset and again pair it, then it is connecting. 1. Ubuntu Version - 20.04 2. Software version - bluez Installed: 5.53-0ubuntu3 3. Expected result : Every time when I restart the laptop or resume it the headset should connect automatically 4. Some times when I restart the laptop or resume the laptop, then eventhough headset is switched on bluetooth connection is not established. Instead if I remove the the headset from bluetooth list and again newly pair it with laptop then headset it connected. Verified the bluetooth head set by connecting it to mobile phone and other os like windows/mac os and it seems there is no issue with headset. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 17 19:58:10 2020 InstallationDate: Installed on 2020-05-04 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:a060 Quanta Computer, Inc. HD Webcam Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a609dea6-45d9-4ed8-8a46-ba56dae5a117 ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.19 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.19 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.19 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.19:bd07/13/2018:svnAcer:pnNitroAN515-52:pvrV1.19:rvnCFL:rnFreed_CFS:rvrV1.19:cvnAcer:ct10:cvrV1.19: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.19 dmi.sys.vendor: Acer hciconfig: hci0: Type: Primary Bus: USB BD Address: 18:56:80:A6:CA:8D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:16973 acl:0 sco:0 events:2752 errors:0 TX bytes:678011 acl:0 sco:0 commands:2750 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1887977 Title: Bluetooth headset is not reconnecting automatically if disconnected in between Status in bluez package in Ubuntu: New Bug description: Some times Bluetooth headset is not reconnecting automatically if disconnected in between. I need to remove the bluetooth headset and again pair it, then it is connecting. 1. Ubuntu Version - 20.04 2. Software version - bluez Installed: 5.53-0ubuntu3 3. Expected result : Every time when I restart the laptop or resume it the headset should connect automatically 4. Some times when I restart the laptop or resume the laptop, then eventhough headset is switched on bluetooth connection is not established. Instead if I remove the the headset from bluetooth list and again newly pair it with laptop then headset it connected. Verified the bluetooth head set by connecting it to mobile phone and other os like windows/mac os and it seems there is no issue with headset. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 17 19:58:10 2020 InstallationDate: Installed on 2020-05-04 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:a060 Quanta Computer, Inc. HD Webcam Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a609dea6-45d9-4ed8-8a46-ba56dae5a117 ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2018 dmi.bios.vendor: Insyde Corp.
[Touch-packages] [Bug 1887976] [NEW] package libxt6 1:1.1.5-1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libxt6/changelog.Debian.gz' partilhado, que é diferente de outras instân
Public bug reported: error ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libxt6 1:1.1.5-1 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.9 AptOrdering: libxt6:i386: Install NULL: ConfigurePending Architecture: amd64 CompositorRunning: None Date: Fri Jul 17 11:30:18 2020 DistUpgraded: 2020-07-09 12:07:43,389 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho “./xorg_fix_proprietary.py” (Arquivo ou diretório inexistente) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 450.57, 5.3.0-62-generic, x86_64: installed DpkgTerminalLog: A preparar para desempacotar .../libxt6_1%3a1.1.5-1_i386.deb ... A descompactar libxt6:i386 (1:1.1.5-1) sobre (1:1.1.5-1) ... dpkg: erro ao processar o arquivo /var/cache/apt/archives/libxt6_1%3a1.1.5-1_i386.deb (--unpack): a tentar sobreescrever '/usr/share/doc/libxt6/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libxt6:i386 ErrorMessage: a tentar sobreescrever '/usr/share/doc/libxt6/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libxt6:i386 GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1331] NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1332] InstallationDate: Installed on 2020-07-09 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 004: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Nitro AN515-54 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=a01360a5-1be4-42d8-acb6-d4a957e1c1c0 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4ubuntu0.1 SourcePackage: libxt Title: package libxt6 1:1.1.5-1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libxt6/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libxt6:i386 UpgradeStatus: Upgraded to eoan on 2020-07-09 (7 days ago) dmi.bios.date: 05/11/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.30 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Octavia_CFS dmi.board.vendor: CFL dmi.board.version: V1.30 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.30 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.30:bd05/11/2020:svnAcer:pnNitroAN515-54:pvrV1.30:rvnCFL:rnOctavia_CFS:rvrV1.30:cvnAcer:ct10:cvrV1.30: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-54 dmi.product.sku: dmi.product.version: V1.30 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: libxt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxt in Ubuntu. https://bugs.launchpad.net/bugs/1887976 Title: package libxt6 1:1.1.5-1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libxt6/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libxt6:i386 Status in libxt package in Ubuntu: New Bug description: error ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libxt6 1:1.1.5-1 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.9 AptOrdering: libxt6:i386: Install NULL: ConfigurePending Architecture: amd64 CompositorRunning: None Date: Fri Jul 17 11:30:18 2020 DistUpgraded: 2020-07-09 12:07:43,389 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho “./xorg_fix_proprietary.py” (Arquivo ou diretório inexistente) (8)) DistroCodename: eoan DistroVariant: ubuntu
[Touch-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
** Changed in: bluez (Ubuntu) Status: Incomplete => In Progress -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: In Progress Bug description: [Impact] * only impact Bionic machines because series after Bionic already included this patch. [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * low, becuase [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+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 1887898] Re: Bluetooth sound card not detected
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: bluez (Ubuntu) Importance: Undecided => Low ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1887898 Title: Bluetooth sound card not detected Status in bluez package in Ubuntu: Incomplete Bug description: I am able to use my inbuilt mic but unable to use external mic using neither Bluetooth nor mic with USB. My headphones are absolutely working fine with other devices (Mobile Phone or other laptop with windows) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: manoj 1480 F pulseaudio /dev/snd/controlC0: manoj 1480 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jul 17 12:31:29 2020 InstallationDate: Installed on 2019-10-15 (275 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.6A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.46 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6A:bd05/13/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.46:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: D7Z60PC#ACJ dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887898/+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 1887968] Re: Pairing with bluetooth mice fails
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect 1887968
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.
** Changed in: bluez (Ubuntu)
Importance: Undecided => Low
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
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/1887968
Title:
Pairing with bluetooth mice fails
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No
[Touch-packages] [Bug 1887968] Re: Pairing with bluetooth mice fails
Could you also add your 'journalctl -b 0' after getting the issue?
--
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/1887968
Title:
Pairing with bluetooth mice fails
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a .Raz
65 72 20 41 74 68 65 72 69 73er Atheris
< HCI Command: LE Set
[Touch-packages] [Bug 1887968] [NEW] Pairing with bluetooth mice fails
Public bug reported:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems to
use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice. However
bluetooth seems to work with other devices. I'm under the impression
that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
> #2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
> #4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
> #5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a .Raz
65 72 20 41 74 68 65 72 69 73er Atheris
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#6 [hci0] 8.343656
Extended scan: Disabled (0x00)
Filter duplicates: Disabled (0x00)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
> #7 [hci0] 8.345617
LE Set
[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home
Hello, please see https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887964 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1874381 Title: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home Status in Ubuntu on IBM z Systems: Confirmed Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Bug description: After upgrading an LPAR configured with LVM from 18.04 to 20.04 /home is no longer mounted. During boot the console shows Timed out waiting for device /dev/mapper/s5lp8--vg-home Please see the attached dist-upgrade logs and console output for more detail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381/+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 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798
Sorry, turns out the /etc/systemd/system service file needs to be a symlink to trigger the bug. This will do it: su - cat < /crashsystemd@.service [Unit] Description=Template for instance %i [Service] ExecStart=/bin/true EOF cd /etc/systemd/system ln -s /crashsystemd@.service crashsystemd.service systemctl daemon-reload systemctl start crashsystemd After the 'systemctl start crashsystemd' my terminal says: Failed to start crashsystemd.service: Connection reset by peer See system logs and 'systemctl status crashsystemd.service' for details. and in the systemd logs I see: Jul 17 23:20:33 jturner-desktop systemd[1]: Assertion 'u->instance' failed at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting. Things are pretty broken now. 'systemctl' and 'reboot' commands won't work. Don't forget to delete the /etc/systemd/system/crashsystemd.service symlink before rebooting. -- 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/1887744 Title: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798 Status in systemd package in Ubuntu: New Bug description: On an Ubuntu 20.04 server, when I started a newly installed systemd service 'systemctl start testemail2jira.service', systemd trips on an assertion (from journalctl): Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as pid 2906637. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution. apport generates a core dump which I trust is attached. The server still works, but my terminal keeps showing: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) and pauses for 25s after each command. In case it's relevant, the i was trying to start had just been symlinked into /etc/systemd/system/: root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service lrwxrwxrwx 1 root root 82 Jul 16 13:48 /etc/systemd/system/testemail2jira.service -> /opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service File contents: [Unit] Description=Check that email to %i JIRA works [Service] #Type=oneshot # Note: I keep the config file, testemail2jira.json5 and rsa.* files in emailprocessing/, one directory below testemail2jira/, so that they can be version-controlled independently. # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add testemail2jira/ to WorkingDirectory and remove it from the ExecStart command WorkingDirectory=/opt/atlassian/%i/current/emailprocessing ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python testemail2jira/testemail2jira.py User=root [Install] WantedBy=multi-user.target Perhaps the problem is that my service file is a template (testemail2jira@.service), but I symlinked it as a regular 'testemail2jira.service'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 16 14:13:06 2020 InstallationDate: Installed on 2020-05-27 (49 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/sda ro console=ttyS0,19200n8 net.ifnames=0 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 'Error:'] failed with exit code 1: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-3.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1887744/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1887959] [NEW] Unable to upgrade several qt5 packages (libqt5gui5, …)
Public bug reported: After upgrading from Ubuntu 19.10 (maybe 18.04) to 20.04, I am unable to upgrade the packages below. The following packages have been kept back: libboost-date-time-dev libboost-dev libboost-filesystem-dev libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5printsupport5 libqt5sql5 libqt5svg5 libqt5widgets5 libqt5xml5 ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1887959 Title: Unable to upgrade several qt5 packages (libqt5gui5, …) Status in qtbase-opensource-src package in Ubuntu: New Bug description: After upgrading from Ubuntu 19.10 (maybe 18.04) to 20.04, I am unable to upgrade the packages below. The following packages have been kept back: libboost-date-time-dev libboost-dev libboost-filesystem-dev libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5printsupport5 libqt5sql5 libqt5svg5 libqt5widgets5 libqt5xml5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1887959/+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 1887959] Re: Unable to upgrade several qt5 packages (libqt5gui5, …)
``` $ apt list --upgradable Listing... Done libboost-date-time-dev/focal 1.71.0.0ubuntu2 ppc64el [upgradable from: 1.67.0.2] libboost-dev/focal 1.71.0.0ubuntu2 ppc64el [upgradable from: 1.67.0.2] libboost-filesystem-dev/focal 1.71.0.0ubuntu2 ppc64el [upgradable from: 1.67.0.2] libqt5core5a/focal 5.12.8+dfsg-0ubuntu1 ppc64el [upgradable from: 5.12.4+dfsg-4ubuntu1.1] libqt5dbus5/focal 5.12.8+dfsg-0ubuntu1 ppc64el [upgradable from: 5.12.4+dfsg-4ubuntu1.1] libqt5gui5/focal 5.12.8+dfsg-0ubuntu1 ppc64el [upgradable from: 5.12.4+dfsg-4ubuntu1.1] libqt5network5/focal 5.12.8+dfsg-0ubuntu1 ppc64el [upgradable from: 5.12.4+dfsg-4ubuntu1.1] libqt5printsupport5/focal 5.12.8+dfsg-0ubuntu1 ppc64el [upgradable from: 5.12.4+dfsg-4ubuntu1.1] libqt5sql5/focal 5.12.8+dfsg-0ubuntu1 ppc64el [upgradable from: 5.12.4+dfsg-4ubuntu1.1] libqt5svg5/focal 5.12.8-0ubuntu1 ppc64el [upgradable from: 5.12.4-1] libqt5widgets5/focal 5.12.8+dfsg-0ubuntu1 ppc64el [upgradable from: 5.12.4+dfsg-4ubuntu1.1] libqt5xml5/focal 5.12.8+dfsg-0ubuntu1 ppc64el [upgradable from: 5.12.4+dfsg-4ubuntu1.1] ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1887959 Title: Unable to upgrade several qt5 packages (libqt5gui5, …) Status in qtbase-opensource-src package in Ubuntu: New Bug description: After upgrading from Ubuntu 19.10 (maybe 18.04) to 20.04, I am unable to upgrade the packages below. The following packages have been kept back: libboost-date-time-dev libboost-dev libboost-filesystem-dev libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5printsupport5 libqt5sql5 libqt5svg5 libqt5widgets5 libqt5xml5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1887959/+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 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'
** Changed in: oem-priority Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1887610 Title: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode' Status in HWE Next: New Status in OEM Priority Project: In Progress Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Bionic: Confirmed Status in pulseaudio source package in Eoan: Won't Fix Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Bug description: [Impact] On some I+N machines (inlcuding lenovo and dell machines), after setting the graphic mode to perofermance mode, and open the gnome sound seting, run suspend/resume test, the audio devices will disappear from UI, instead a dummy audio shows on the UI, and from then on, the audio can't work anymore. [Fix] The root cause is after resuming, the pulseaudio try to recover the PCM device, but at that moment, the devices nodes at /dev/snd/ are not accessible yet sometimes, it will make snd_pcm_open fail and the pulseaudio will calll unload_module to unload alsa audio card. I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(), this will retry the snd_pcm_open() a couple of times if it fails. [Test Case] Install the pulseaudio wit this fix, set the graphic mode to performance mode, open the sound setting, then run suspend/resume 90 times, after test check the audio devices on the UI, the speaker, digital mic are still on the UI, and they could work well. [Regression Risk] Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open() doesn't fail, this patch will not introduce any change, if snd_pcm_open() fails, it just retry a couple of times, so it will not introduce the regression in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1887610/+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 1876506] Re: eoan to focal upgrade hangs when lvm snapshot is present
The maintainer script becomes a zombie, because perl -w ... debconf/frontend ... memtest86+.postinst is stuck in a read() from fd 9, which is a pipe. ** Package changed: memtest86+ (Ubuntu) => ubuntu ** Package changed: ubuntu => debconf (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1876506 Title: eoan to focal upgrade hangs when lvm snapshot is present Status in debconf package in Ubuntu: Confirmed Status in debconf source package in Focal: Confirmed Bug description: When upgrading from 19.10 (w/ LVM + encypted disks) to 20.04, the installer hangs when trying to probe an LVM snapshot volume created before the upgrade. Steps to reproduce: lvcreate -s -L 20G -n preupgrade /dev/vgubuntu/root do-release-upgrade -d The installer will hang after the following message: /usr/sbin/grub-probe: error: unknown filesystem. Found Ubuntu 19.10 (19.10) on /dev/mapper/vgubuntu-preupgrade done Resolution: Killing the grub-mount process which is probing the LVM snapshot seems to unhang the installer and allow the upgrade to complete without issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1876506/+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 1871641] Re: Ubuntu never finishes booting: A start job is running for Hold until boot process finishes up (3min 7s / no limit) -- removing 'splash' kernel parm fixes it
** Tags added: id-5f10737aea5c871f9fb256f6 -- 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/1871641 Title: Ubuntu never finishes booting: A start job is running for Hold until boot process finishes up (3min 7s / no limit) -- removing 'splash' kernel parm fixes it Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Boot process freezes at the splash screen and nothing happens after that. The computer can be suspended and it is able to return from suspend. Boot is possible by pressing escape early in the process to bypass plymouth. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plymouth 0.9.4git20200323-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 Date: Wed Apr 8 14:30:13 2020 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2020-04-08 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 7469A23 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6DET72WW (3.22 ) dmi.board.name: 7469A23 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6DET72WW(3.22):bd10/25/2012:svnLENOVO:pn7469A23:pvrThinkPadX200s:rvnLENOVO:rn7469A23:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X200s dmi.product.name: 7469A23 dmi.product.version: ThinkPad X200s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871641/+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 1876506] [NEW] eoan to focal upgrade hangs when lvm snapshot is present
You have been subscribed to a public bug: When upgrading from 19.10 (w/ LVM + encypted disks) to 20.04, the installer hangs when trying to probe an LVM snapshot volume created before the upgrade. Steps to reproduce: lvcreate -s -L 20G -n preupgrade /dev/vgubuntu/root do-release-upgrade -d The installer will hang after the following message: /usr/sbin/grub-probe: error: unknown filesystem. Found Ubuntu 19.10 (19.10) on /dev/mapper/vgubuntu-preupgrade done Resolution: Killing the grub-mount process which is probing the LVM snapshot seems to unhang the installer and allow the upgrade to complete without issue. ** Affects: debconf (Ubuntu) Importance: Critical Status: Confirmed ** Affects: debconf (Ubuntu Focal) Importance: Critical Status: Confirmed ** Tags: eoan2focal id-5ecfe91fc5987a8563b27f1f -- eoan to focal upgrade hangs when lvm snapshot is present https://bugs.launchpad.net/bugs/1876506 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. -- 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 1790205] Re: systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is.
So, as has been previously stated here, and as is documented in section 5 of the journald.conf man page (install man-db, run 'man 5 journald.conf'), journald will, by default, limit the journals' disk allocation to either a maximum of 10% of available disk space, or to the absolute size of 4GB, whichever is lower. Example 1: You have a 120 GB disk, 70 GB are in use, leaving 50 GB. 10% of 50 GB are 5 GB, but the absolute value of 4 GB is lower, so journald will at most take 4 GB storage on this system (and dynamically less, if the disk grows fuller). Example 2: You have a 20 GB disk, 12 GB are in use, leaving 8 GB. 10% of 8 GB are 800 MB, which is less than 4 GB, so journald will at most take 800 MB storage on this system (and dynamically more or less, if disk allocation changes). Benjamin is now reporting 4.1 GB allocated, which is more than 4 GB, and with the details above, this is unexpected. What could be the reason? These limits are applied both when journald starts, and when vacuuming takes place. So if Benjamins' logs have grown by 100 MB since journald started, this can easily explain this situation. They will be reduced to 4 GB (or less, if the disk runs full) again next time vacuuming takes place (such as when journald is restarted). So unless these limits are considered a problem (why? disk space is cheap, and you can modify them as needed if you're on a special (embedded?) platform), I don't see a problem here. -- 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/1790205 Title: systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is. Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: After running Bionic for 3 months, I had 2.6 GB of journals. I would not expect from a normal desktop user that they should have to run commands like `sudo journalctl --vacuum-time=10d`. I would nominate this command as a sane default to have running at each reboot to ensure that logs do not exceed 500 MB: sudo journalctl --vacuum-size=500M Supposedly, a server should by default retain more logs, so perhaps this should be implemented through a configuration package "systemd- configuration-desktop" as a dependency of the ubuntu-desktop meta package? . as it turns out, it's hard to see how much disk space is used, and what the upper limit is, even when it is set and respected by default. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1790205/+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 1887898] Re: Bluetooth sound card not detected
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Package changed: ubuntu => bluez (Ubuntu) ** Information type changed from Private Security to Public -- 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/1887898 Title: Bluetooth sound card not detected Status in bluez package in Ubuntu: New Bug description: I am able to use my inbuilt mic but unable to use external mic using neither Bluetooth nor mic with USB. My headphones are absolutely working fine with other devices (Mobile Phone or other laptop with windows) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: manoj 1480 F pulseaudio /dev/snd/controlC0: manoj 1480 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jul 17 12:31:29 2020 InstallationDate: Installed on 2019-10-15 (275 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.6A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.46 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6A:bd05/13/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.46:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: D7Z60PC#ACJ dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887898/+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 1877536] Re: BlueZ 5.54 release
This bug was fixed in the package bluez - 5.54-0ubuntu1 --- bluez (5.54-0ubuntu1) groovy; urgency=medium * New upstream release 5.54 (LP: #1877536) - Fix issue with HOGP to accept data only from bonded devices. - Fix issue with A2DP sessions being connected at the same time. - Fix issue with class UUID matches before connecting profile. - Add support for handling MTU auto-tuning option for AVDTP. - Add support for new policy for Just-Works repairing. - Add support for Enhanced ATT bearer (EATT). * Dropped CVE-2020-0556-[1-4].patch as release 5.54 onward is not affected. * Dropped (already unused) CVE-2017-1000250.patch as release 5.47 onward is not affected. -- Daniel van Vugt Fri, 08 May 2020 16:28:03 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi- bin/cvename.cgi?name=2017-1000250 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0556 -- 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/1877536 Title: BlueZ 5.54 release Status in bluez package in Ubuntu: Fix Released Bug description: Release BlueZ 5.54 to groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1877536/+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 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'
Hello Hui, or anyone else affected, Accepted pulseaudio into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1887610 Title: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode' Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Bionic: Confirmed Status in pulseaudio source package in Eoan: Won't Fix Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Bug description: [Impact] On some I+N machines (inlcuding lenovo and dell machines), after setting the graphic mode to perofermance mode, and open the gnome sound seting, run suspend/resume test, the audio devices will disappear from UI, instead a dummy audio shows on the UI, and from then on, the audio can't work anymore. [Fix] The root cause is after resuming, the pulseaudio try to recover the PCM device, but at that moment, the devices nodes at /dev/snd/ are not accessible yet sometimes, it will make snd_pcm_open fail and the pulseaudio will calll unload_module to unload alsa audio card. I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(), this will retry the snd_pcm_open() a couple of times if it fails. [Test Case] Install the pulseaudio wit this fix, set the graphic mode to performance mode, open the sound setting, then run suspend/resume 90 times, after test check the audio devices on the UI, the speaker, digital mic are still on the UI, and they could work well. [Regression Risk] Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open() doesn't fail, this patch will not introduce any change, if snd_pcm_open() fails, it just retry a couple of times, so it will not introduce the regression in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1887610/+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 1882161] Update Released
The verification of the Stable Release Update for pulseaudio has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882161 Title: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] * On the Dell machines with multi function audio jack, the headphone/headset can't output sound automatically, which is different from ubuntu 18.04. The headphone/headset should be able to output sound automatically after plugging in the audio jack. [Test Case] * On Tiger Lake platform Reproduce step: 1. plug headphone/headset 2. open g-c-c sound to check Expect result: The output device should switch to headphone or headset, since headphone's priority is higher in ucm2 config. Actual result: The output device is still internal speaker. [Regression Potential] * The change insert the ucm device by its priority, the potential regression is low, since if the change is not working properly, the side effect is that the order of ucm devices are wrong, and it won't switch to the correct output device as expect, but user can still config it manually. [Other] * This bug originates from an OEM private bug #1875597, then ubuntu users reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329 and the 1st issue of #1881659 have the same root cause as #1875597 * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, finally the audio jack is set to Mic2 mode, this make the audio jack can't output sound anymore. To fix it, let the audio jack set to Headset MIC mode by default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the device event to module-switch-on-port-available by the order of priority in the umc2. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882161/+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 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.4 --- pulseaudio (1:13.99.1-1ubuntu3.4) focal; urgency=medium * d/p/0032-alsa-mixer-store-the-ucm_device-with-the-order-of-th.patch - switch the port on ucm devices based on the priority (LP: #1882161) -- Hui Wang Fri, 05 Jun 2020 09:52:22 +0800 ** Changed in: pulseaudio (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882161 Title: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] * On the Dell machines with multi function audio jack, the headphone/headset can't output sound automatically, which is different from ubuntu 18.04. The headphone/headset should be able to output sound automatically after plugging in the audio jack. [Test Case] * On Tiger Lake platform Reproduce step: 1. plug headphone/headset 2. open g-c-c sound to check Expect result: The output device should switch to headphone or headset, since headphone's priority is higher in ucm2 config. Actual result: The output device is still internal speaker. [Regression Potential] * The change insert the ucm device by its priority, the potential regression is low, since if the change is not working properly, the side effect is that the order of ucm devices are wrong, and it won't switch to the correct output device as expect, but user can still config it manually. [Other] * This bug originates from an OEM private bug #1875597, then ubuntu users reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329 and the 1st issue of #1881659 have the same root cause as #1875597 * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, finally the audio jack is set to Mic2 mode, this make the audio jack can't output sound anymore. To fix it, let the audio jack set to Headset MIC mode by default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the device event to module-switch-on-port-available by the order of priority in the umc2. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882161/+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 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority
Hello! Seeing that this is priority for the OEM team, I'll conditionally release this early - and on a Friday (oh no!). The problem with this is that we'd have to make sure that if this does regress anything, there is someone to react quickly during the weekend. I'll be available, but I'd appreciate if someone from the OEM team could also keep eyes out for any news of regression. Please give me a poke if anything like that happens. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882161 Title: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] * On the Dell machines with multi function audio jack, the headphone/headset can't output sound automatically, which is different from ubuntu 18.04. The headphone/headset should be able to output sound automatically after plugging in the audio jack. [Test Case] * On Tiger Lake platform Reproduce step: 1. plug headphone/headset 2. open g-c-c sound to check Expect result: The output device should switch to headphone or headset, since headphone's priority is higher in ucm2 config. Actual result: The output device is still internal speaker. [Regression Potential] * The change insert the ucm device by its priority, the potential regression is low, since if the change is not working properly, the side effect is that the order of ucm devices are wrong, and it won't switch to the correct output device as expect, but user can still config it manually. [Other] * This bug originates from an OEM private bug #1875597, then ubuntu users reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329 and the 1st issue of #1881659 have the same root cause as #1875597 * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, finally the audio jack is set to Mic2 mode, this make the audio jack can't output sound anymore. To fix it, let the audio jack set to Headset MIC mode by default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the device event to module-switch-on-port-available by the order of priority in the umc2. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882161/+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 1887372] Re: Cannot create lvm upon IMSM raid array
** Tags added: rls-gg-incoming ** Changed in: lvm2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1887372 Title: Cannot create lvm upon IMSM raid array Status in lvm2 package in Ubuntu: Confirmed Bug description: The issue has been observed on 2.3.7 (Ubuntu 20.04). Reported to lvm team: https://bugzilla.redhat.com/show_bug.cgi?id=1855251 Steps to Reproduce: 1. Create IMSM raid array: #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G 2. Create lvm volume on raid: # pvcreate -ff -y /dev/md/vol # vgcreate group0 /dev/md/vol # lvcreate -Z y -y -l +100%FREE group0 -n lvm0 Actual results: Vg creation fails. Expected results: LVM should be able to determine the best drive and ignore duplicates. Additional info: IMSM metadata is written at the end of the drive. The first drive sector belongs to the raid volume and other metadata saved there (like lvm) can be recognized directly on raid members. The following patches should fix the issue (not verified yet): https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+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 1861177] Re: seccomp_rule_add is very slow
#VERIFICATION BIONIC ---> Old version # dpkg -l | grep libseccomp ii libseccomp2:amd64 2.4.3-1ubuntu3.18.04.2 amd64 high level interface to Linux seccomp filter # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done MAX TIME : 8.148s ---> New version # dpkg -l | grep libseccomp ii libseccomp2:amd64 2.4.3-1ubuntu3.18.04.3 amd64 high level interface to Linux seccomp filter # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done MAX TIME : 2.713s ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1861177 Title: seccomp_rule_add is very slow Status in snapd: Invalid Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: Fix Committed Status in libseccomp source package in Bionic: Fix Committed Status in libseccomp source package in Eoan: Fix Committed Status in libseccomp source package in Focal: Fix Committed Status in libseccomp source package in Groovy: Fix Released Bug description: [IMPACT] There is a known and patched issue with version 2.4 of libseccomp where certain operations have a large performance regression. This is causing some packages that use libseccomp such as container orchestration systems to occasionally time out or otherwise fail under certain workloads. Please consider porting the patch into the various Ubuntu versions that have version 2.4 of libseccomp and into the backports. The performance patch from version 2.5 (yet to be released) applies cleanly on top of the 2.4 branch of libseccomp. For more information, and for a copy of the patch (which can also be cherry picked from the upstream libseccomp repos) see the similar Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913 Upstream issue : https://github.com/seccomp/libseccomp/issues/153 Upstream fix : https://github.com/seccomp/libseccomp/pull/180/ [Test Case] For this test case we use Docker on Ubuntu Groovy (20.10) : --> Current libseccomp version #dpkg -l | grep libseccomp ii libseccomp2:amd64 2.4.3-1ubuntu3 amd64high level interface to Linux seccomp filter ## pull ubuntu image # docker pull ubuntu ## create a container # docker run --name test_seccomp -it 74435f89ab78 /bin/bash ## run test case # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done ... MAX TIME : real 0m10,319s user 0m0,018s sys 0m0,033s --> Patched libseccomp version # dpkg -l | grep libseccomp ii libseccomp2:amd64 2.4.3-1ubuntu4 amd64high level interface to Linux seccomp filter # docker start test_seccomp ## run test case # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done ... MAX TIME : real 0m3,650s user 0m0,025s sys 0m0,028s [Regression Potential] The first of the 2 patches cleans up the code that adds rules to a single filter without changing the logic of the code. The second patch introduces the idea of shadow transactions. On a successful transaction commit the old transaction checkpoint is preserved and is brought up to date with the current filter. The next time a new transaction starts, it checks is the a shadow transaction exist and if so the shadow is used instead of creating a new checkpoint from scratch [1]. This is the patch that mitigates the performance regression. Any potential regression will involve the parts of the code that add rules to filters and/or the code that creates and checks the shadow transactions. [Other] Affected releases : Groovy, Focal, Eoan, Bionic, Xenial. [1] https://github.com/seccomp/libseccomp/pull/180/commits/bc3a6c0453b0350ee43e4925482f705a2fbf5a4d To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1861177/+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 1887919] Re: autopkgtest failure with libselinux 3.1
The change in SELinux causing the failures: https://github.com/SELinuxProject/selinux/commit/9eb9c9327563014ad6a807814e7975424642d5b9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1887919 Title: autopkgtest failure with libselinux 3.1 Status in glibc package in Ubuntu: New Status in lxc package in Ubuntu: New Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/amd64/g/glibc/20200717_023434_9a6a8@/log.gz ... x86_64-linux-gnu-gcc-9 nss_files/files-service.c -c -std=gnu11 -fgnu89-inline -pipe -O2 -g -O3 -Wall -Wwrite-strings -Wundef -Werror -fmerge-all-constants -frounding-math -fstack-protector-strong -Wstrict-prototypes -Wold-style-definition -fmath-errno -fPIC -fcf-protection -U_FORTIFY_SOURCE -isystem /tmp/autopkgtest.p9VjWR/build.CPS/src/debian/include -I../include -I/tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss -I/tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc -I../sysdeps/unix/sysv/linux/x86_64/64 -I../sysdeps/unix/sysv/linux/x86_64 -I../sysdeps/unix/sysv/linux/x86/include -I../sysdeps/unix/sysv/linux/x86 -I../sysdeps/x86/nptl -I../sysdeps/unix/sysv/linux/wordsize-64 -I../sysdeps/x86_64/nptl -I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux -I../sysdeps/nptl -I../sysdeps/pthread -I../sysdeps/gnu -I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix/x86_64 -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/x86_64/64 -I../sysdeps/x86_64/fpu/multiarch -I../sysdeps/x86_64/fpu -I../sysdeps/x86/fpu/include -I../sysdeps/x86/fpu -I../sysdeps/x86_64/multiarch -I../sysdeps/x86_64 -I../sysdeps/x86 -I../sysdeps/ieee754/float128 -I../sysdeps/ieee754/ldbl-96/include -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64/wordsize-64 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/wordsize-64 -I../sysdeps/ieee754 -I../sysdeps/generic -I.. -I../libio -I. -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/9/include -isystem /tmp/autopkgtest.p9VjWR/build.CPS/src/debian/include -D_LIBC_REENTRANT -include /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/libc-modules.h -DMODULE_NAME=libnss_files -include ../include/libc-symbols.h -DPIC -DSHARED -DTOP_NAMESPACE=glibc -o /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os -MD -MP -MF /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os.dt -MT /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os makedb.c: In function ‘set_file_creation_context’: makedb.c:849:3: error: ‘security_context_t’ is deprecated [-Werror=deprecated-declarations] 849 | security_context_t ctx; | ^~ makedb.c:863:3: error: ‘matchpathcon’ is deprecated: Use selabel_lookup instead [-Werror=deprecated-declarations] 863 | if (matchpathcon (outname, S_IFREG | mode, ) == 0 && ctx != NULL) | ^~ In file included from makedb.c:50: /usr/include/selinux/selinux.h:500:12: note: declared here 500 | extern int matchpathcon(const char *path, |^~~~ ... https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/l/lxc/20200717_015751_af18d@/log.gz ... libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -fPIC -DPIC -DLXCROOTFSMOUNT=\"/usr/lib/x86_64-linux-gnu/lxc\" -DLXCPATH=\"/var/lib/lxc\" -DLXC_GLOBAL_CONF=\"/etc/lxc/lxc.conf\" -DLXCINITDIR=\"/usr/lib/x86_64-linux-gnu\" -DLIBEXECDIR=\"/usr/lib/x86_64-linux-gnu\" -DLXCTEMPLATEDIR=\"/usr/share/lxc/templates\" -DLXCTEMPLATECONFIG=\"/usr/share/lxc/config\" -DLOGPATH=\"/var/log/lxc\" -DLXC_DEFAULT_CONFIG=\"/etc/lxc/default.conf\" -DLXC_USERNIC_DB=\"/run/lxc/nics\" -DLXC_USERNIC_CONF=\"/etc/lxc/lxc-usernet\" -DDEFAULT_CGROUP_PATTERN=\"\" -DRUNTIME_PATH=\"/run\" -DSBINDIR=\"/usr/sbin\" -DAPPARMOR_CACHE_DIR=\"/var/cache/lxc/apparmor\" -I ../../src -I ../../src/lxc -I ../../src/lxc/storage -I ../../src/lxc/cgroups -DHAVE_APPARMOR -DHAVE_SECCOMP -DHAVE_SELINUX -pthread -g -O2 -fdiagnostics-color -Wimplicit-fallthrough=5 -Wcast-align -fno-strict-aliasing -fstack-clash-protection -fstack-protector-strong --param=ssp-buffer-size=4 -g -Werror=implicit-function-declaration -Wlogical-op -Wmissing-include-dirs -Winit-self -Wunused-but-set-variable -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=return-type -Werror=incompatible-pointer-types -Wformat=2 -Wshadow -Wendif-labels -Werror=overflow -fdiagnostics-show-option -Werror=shift-count-overflow -Werror=shift-overflow=2 -Wdate-time -Wnested-externs -fasynchronous-unwind-tables -pipe -fexceptions -Wvla -std=gnu11 -Werror -MT lsm/liblxc_la-selinux.lo -MD -MP -MF
[Touch-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
I have a freshly installed 20.10 system running on a 2012 MacBook Air (MBA 5,2) and it is completely silent and cold when being idle: rbalint@chaos:~$ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 2.80 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 2.80 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 915 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes 2600 MHz max turbo 4 active cores 2600 MHz max turbo 3 active cores 2600 MHz max turbo 2 active cores 2800 MHz max turbo 1 active cores @seb128, @juliank I'm not sure if there is anything to fix in the user space, but please report which laptops you experienced issues with. Those may need firmware/kernel fixes. ** Changed in: systemd (Ubuntu Groovy) Status: New => Invalid -- 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/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: Invalid Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
@Alex, sorry I though you were familiar with the SRU process, see https://wiki.ubuntu.com/StableReleaseUpdates for details especially 'A [Regression Potential] section with a discussion of how regressions are most likely to manifest, or may manifest even if it is unlikely, as a result of this change.' 'low, becuase' isn't really enough... Also I saw the debdiff, did you read my points about the description and email used in that one? -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Incomplete Bug description: [Impact] * only impact Bionic machines because series after Bionic already included this patch. [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * low, becuase [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+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 1887919] Re: autopkgtest failure with libselinux 3.1
I plan fixing the glibc failure together with other issues early next week. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1887919 Title: autopkgtest failure with libselinux 3.1 Status in glibc package in Ubuntu: New Status in lxc package in Ubuntu: New Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/amd64/g/glibc/20200717_023434_9a6a8@/log.gz ... x86_64-linux-gnu-gcc-9 nss_files/files-service.c -c -std=gnu11 -fgnu89-inline -pipe -O2 -g -O3 -Wall -Wwrite-strings -Wundef -Werror -fmerge-all-constants -frounding-math -fstack-protector-strong -Wstrict-prototypes -Wold-style-definition -fmath-errno -fPIC -fcf-protection -U_FORTIFY_SOURCE -isystem /tmp/autopkgtest.p9VjWR/build.CPS/src/debian/include -I../include -I/tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss -I/tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc -I../sysdeps/unix/sysv/linux/x86_64/64 -I../sysdeps/unix/sysv/linux/x86_64 -I../sysdeps/unix/sysv/linux/x86/include -I../sysdeps/unix/sysv/linux/x86 -I../sysdeps/x86/nptl -I../sysdeps/unix/sysv/linux/wordsize-64 -I../sysdeps/x86_64/nptl -I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux -I../sysdeps/nptl -I../sysdeps/pthread -I../sysdeps/gnu -I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix/x86_64 -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/x86_64/64 -I../sysdeps/x86_64/fpu/multiarch -I../sysdeps/x86_64/fpu -I../sysdeps/x86/fpu/include -I../sysdeps/x86/fpu -I../sysdeps/x86_64/multiarch -I../sysdeps/x86_64 -I../sysdeps/x86 -I../sysdeps/ieee754/float128 -I../sysdeps/ieee754/ldbl-96/include -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64/wordsize-64 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/wordsize-64 -I../sysdeps/ieee754 -I../sysdeps/generic -I.. -I../libio -I. -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/9/include -isystem /tmp/autopkgtest.p9VjWR/build.CPS/src/debian/include -D_LIBC_REENTRANT -include /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/libc-modules.h -DMODULE_NAME=libnss_files -include ../include/libc-symbols.h -DPIC -DSHARED -DTOP_NAMESPACE=glibc -o /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os -MD -MP -MF /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os.dt -MT /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os makedb.c: In function ‘set_file_creation_context’: makedb.c:849:3: error: ‘security_context_t’ is deprecated [-Werror=deprecated-declarations] 849 | security_context_t ctx; | ^~ makedb.c:863:3: error: ‘matchpathcon’ is deprecated: Use selabel_lookup instead [-Werror=deprecated-declarations] 863 | if (matchpathcon (outname, S_IFREG | mode, ) == 0 && ctx != NULL) | ^~ In file included from makedb.c:50: /usr/include/selinux/selinux.h:500:12: note: declared here 500 | extern int matchpathcon(const char *path, |^~~~ ... https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/l/lxc/20200717_015751_af18d@/log.gz ... libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -fPIC -DPIC -DLXCROOTFSMOUNT=\"/usr/lib/x86_64-linux-gnu/lxc\" -DLXCPATH=\"/var/lib/lxc\" -DLXC_GLOBAL_CONF=\"/etc/lxc/lxc.conf\" -DLXCINITDIR=\"/usr/lib/x86_64-linux-gnu\" -DLIBEXECDIR=\"/usr/lib/x86_64-linux-gnu\" -DLXCTEMPLATEDIR=\"/usr/share/lxc/templates\" -DLXCTEMPLATECONFIG=\"/usr/share/lxc/config\" -DLOGPATH=\"/var/log/lxc\" -DLXC_DEFAULT_CONFIG=\"/etc/lxc/default.conf\" -DLXC_USERNIC_DB=\"/run/lxc/nics\" -DLXC_USERNIC_CONF=\"/etc/lxc/lxc-usernet\" -DDEFAULT_CGROUP_PATTERN=\"\" -DRUNTIME_PATH=\"/run\" -DSBINDIR=\"/usr/sbin\" -DAPPARMOR_CACHE_DIR=\"/var/cache/lxc/apparmor\" -I ../../src -I ../../src/lxc -I ../../src/lxc/storage -I ../../src/lxc/cgroups -DHAVE_APPARMOR -DHAVE_SECCOMP -DHAVE_SELINUX -pthread -g -O2 -fdiagnostics-color -Wimplicit-fallthrough=5 -Wcast-align -fno-strict-aliasing -fstack-clash-protection -fstack-protector-strong --param=ssp-buffer-size=4 -g -Werror=implicit-function-declaration -Wlogical-op -Wmissing-include-dirs -Winit-self -Wunused-but-set-variable -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=return-type -Werror=incompatible-pointer-types -Wformat=2 -Wshadow -Wendif-labels -Werror=overflow -fdiagnostics-show-option -Werror=shift-count-overflow -Werror=shift-overflow=2 -Wdate-time -Wnested-externs -fasynchronous-unwind-tables -pipe -fexceptions -Wvla -std=gnu11 -Werror -MT lsm/liblxc_la-selinux.lo -MD -MP -MF lsm/.deps/liblxc_la-selinux.Tpo -c lsm/selinux.c -fPIC -DPIC -o
[Touch-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
@seb128, yes, I modified the description and the debdiff is there in #4. ** Description changed: - steps: + [Impact] + + * only impact Bionic machines because series after Bionic already + included this patch. + + [Test Case] + 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. - 4. blutoothd segfault shows in dmesg after a while. - 5. Bluetooth shows off on setting UI of right top corner. + 4. the bluetooth should still work to pair another bluetooth device. - dmesg shows: - [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] + [Regression Potential] + + * low, becuase + + [Other Info] + + * NO. -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Incomplete Bug description: [Impact] * only impact Bionic machines because series after Bionic already included this patch. [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * low, becuase [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+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 1887478] Re: missing symlinks for login and logout files used by gnome
Thanks for the details, the url in the description is a Debian change, not an upstream one though, but let's see if it gets reviewed there ** Changed in: sound-theme-freedesktop (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sound-theme-freedesktop in Ubuntu. https://bugs.launchpad.net/bugs/1887478 Title: missing symlinks for login and logout files used by gnome Status in sound-theme-freedesktop package in Ubuntu: Triaged Bug description: Merge request submitted upstream in Debian to fix the issue. https://salsa.debian.org/gnome-team/sound-theme-freedesktop/-/merge_requests/1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1887478/+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 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
@Alex, thanks, a few comments: * could you make the bug SRU compliant (adding a description of the impact and the regression potential) * it would be nice to have an user friendly description of what the patch is solving in the changelog, also the email you used is not a valid one * could you include details on what upstream version / ubuntu serie already include the fix? -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Incomplete Bug description: [Impact] * only impact Bionic machines because series after Bionic already included this patch. [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * low, becuase [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+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 1887919] [NEW] autopkgtest failure with libselinux 3.1
Public bug reported: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/amd64/g/glibc/20200717_023434_9a6a8@/log.gz ... x86_64-linux-gnu-gcc-9 nss_files/files-service.c -c -std=gnu11 -fgnu89-inline -pipe -O2 -g -O3 -Wall -Wwrite-strings -Wundef -Werror -fmerge-all-constants -frounding-math -fstack-protector-strong -Wstrict-prototypes -Wold-style-definition -fmath-errno -fPIC -fcf-protection -U_FORTIFY_SOURCE -isystem /tmp/autopkgtest.p9VjWR/build.CPS/src/debian/include -I../include -I/tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss -I/tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc -I../sysdeps/unix/sysv/linux/x86_64/64 -I../sysdeps/unix/sysv/linux/x86_64 -I../sysdeps/unix/sysv/linux/x86/include -I../sysdeps/unix/sysv/linux/x86 -I../sysdeps/x86/nptl -I../sysdeps/unix/sysv/linux/wordsize-64 -I../sysdeps/x86_64/nptl -I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux -I../sysdeps/nptl -I../sysdeps/pthread -I../sysdeps/gnu -I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix/x86_64 -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/x86_64/64 -I../sysdeps/x86_64/fpu/multiarch -I../sysdeps/x86_64/fpu -I../sysdeps/x86/fpu/include -I../sysdeps/x86/fpu -I../sysdeps/x86_64/multiarch -I../sysdeps/x86_64 -I../sysdeps/x86 -I../sysdeps/ieee754/float128 -I../sysdeps/ieee754/ldbl-96/include -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64/wordsize-64 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/wordsize-64 -I../sysdeps/ieee754 -I../sysdeps/generic -I.. -I../libio -I. -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/9/include -isystem /tmp/autopkgtest.p9VjWR/build.CPS/src/debian/include -D_LIBC_REENTRANT -include /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/libc-modules.h -DMODULE_NAME=libnss_files -include ../include/libc-symbols.h -DPIC -DSHARED -DTOP_NAMESPACE=glibc -o /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os -MD -MP -MF /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os.dt -MT /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os makedb.c: In function ‘set_file_creation_context’: makedb.c:849:3: error: ‘security_context_t’ is deprecated [-Werror=deprecated-declarations] 849 | security_context_t ctx; | ^~ makedb.c:863:3: error: ‘matchpathcon’ is deprecated: Use selabel_lookup instead [-Werror=deprecated-declarations] 863 | if (matchpathcon (outname, S_IFREG | mode, ) == 0 && ctx != NULL) | ^~ In file included from makedb.c:50: /usr/include/selinux/selinux.h:500:12: note: declared here 500 | extern int matchpathcon(const char *path, |^~~~ ... https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/l/lxc/20200717_015751_af18d@/log.gz ... libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -fPIC -DPIC -DLXCROOTFSMOUNT=\"/usr/lib/x86_64-linux-gnu/lxc\" -DLXCPATH=\"/var/lib/lxc\" -DLXC_GLOBAL_CONF=\"/etc/lxc/lxc.conf\" -DLXCINITDIR=\"/usr/lib/x86_64-linux-gnu\" -DLIBEXECDIR=\"/usr/lib/x86_64-linux-gnu\" -DLXCTEMPLATEDIR=\"/usr/share/lxc/templates\" -DLXCTEMPLATECONFIG=\"/usr/share/lxc/config\" -DLOGPATH=\"/var/log/lxc\" -DLXC_DEFAULT_CONFIG=\"/etc/lxc/default.conf\" -DLXC_USERNIC_DB=\"/run/lxc/nics\" -DLXC_USERNIC_CONF=\"/etc/lxc/lxc-usernet\" -DDEFAULT_CGROUP_PATTERN=\"\" -DRUNTIME_PATH=\"/run\" -DSBINDIR=\"/usr/sbin\" -DAPPARMOR_CACHE_DIR=\"/var/cache/lxc/apparmor\" -I ../../src -I ../../src/lxc -I ../../src/lxc/storage -I ../../src/lxc/cgroups -DHAVE_APPARMOR -DHAVE_SECCOMP -DHAVE_SELINUX -pthread -g -O2 -fdiagnostics-color -Wimplicit-fallthrough=5 -Wcast-align -fno-strict-aliasing -fstack-clash-protection -fstack-protector-strong --param=ssp-buffer-size=4 -g -Werror=implicit-function-declaration -Wlogical-op -Wmissing-include-dirs -Winit-self -Wunused-but-set-variable -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=return-type -Werror=incompatible-pointer-types -Wformat=2 -Wshadow -Wendif-labels -Werror=overflow -fdiagnostics-show-option -Werror=shift-count-overflow -Werror=shift-overflow=2 -Wdate-time -Wnested-externs -fasynchronous-unwind-tables -pipe -fexceptions -Wvla -std=gnu11 -Werror -MT lsm/liblxc_la-selinux.lo -MD -MP -MF lsm/.deps/liblxc_la-selinux.Tpo -c lsm/selinux.c -fPIC -DPIC -o lsm/.libs/liblxc_la-selinux.o [01m[Klsm/selinux.c:[m[K In function ‘[01m[Kselinux_process_label_get[m[K’: [01m[Klsm/selinux.c:35:2:[m[K [01;31m[Kerror: [m[K‘[01m[Ksecurity_context_t[m[K’ is deprecated [[01;31m[K-Werror=deprecated-declarations[m[K] 35 | [01;31m[Ksecurity_context_t[m[K ctx; | [01;31m[K^~[m[K cc1: all warnings being treated as errors make[3]: Leaving
[Touch-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
this is the debdiff which applied the patch , and I also host the modified code there : https://code.launchpad.net/~alextu/ubuntu/+source/bluez/+git/bluez/+ref/lp1887910 -bluetoothd-segv-keyboard ** Patch added: "bluez_5.48-0ubuntu3.5.debdiff" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887910/+attachment/5393459/+files/bluez_5.48-0ubuntu3.5.debdiff -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Incomplete Bug description: [Impact] * only impact Bionic machines because series after Bionic already included this patch. [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * low, becuase [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+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 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
It's good you know the fix already. Otherwise you might need this workaround to get a core dump: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/comments/3 -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Incomplete Bug description: steps: 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. blutoothd segfault shows in dmesg after a while. 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+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 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
Is the issue fixed in the current version? Do you plan to work on a SRU and targetting what serie? ** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Incomplete Bug description: steps: 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. blutoothd segfault shows in dmesg after a while. 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+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 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
after this patch, the issue can not be reproduced:
commit 24249e091ab3a935f6ea87b7f7355c689c045a80 (HEAD -> refs/heads/master)
Author: Luiz Augusto von Dentz
Date: Mon Apr 9 14:48:41 2018 +0300
shared/queue: Handle NULL as direct match on queue_remove_if
As with queue_find when function is set to NULL use direct_match as
callback.
diff --git a/src/shared/queue.c b/src/shared/queue.c
index 5ddb8326d..60df11143 100644
--- a/src/shared/queue.c
+++ b/src/shared/queue.c
@@ -280,9 +280,12 @@ void *queue_remove_if(struct queue *queue,
queue_match_func_t function,
{
struct queue_entry *entry, *prev = NULL;
- if (!queue || !function)
+ if (!queue)
return NULL;
+ if (!function)
+ function = direct_match;
+
entry = queue->head;
** Tags added: oem-priority originate-from-1886187 timbuktu
--
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/1887910
Title:
[bionic]blutoothd segfault when you cancel the keyboard pairing during
the dialog for pairing code
Status in OEM Priority Project:
In Progress
Status in bluez package in Ubuntu:
New
Bug description:
steps:
1. pair bluetooth keyboard
2. see the dialog asking user input the code for pairing.
3. press "esc" to cancel it.
4. blutoothd segfault shows in dmesg after a while.
5. Bluetooth shows off on setting UI of right top corner.
dmesg shows:
[ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp
7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000]
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1887910/+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 1887910] [NEW] [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
Public bug reported: steps: 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. blutoothd segfault shows in dmesg after a while. 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] ** Affects: oem-priority Importance: Critical Assignee: Alex Tu (alextu) Status: In Progress ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1886187 timbuktu ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => In Progress -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: New Bug description: steps: 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. blutoothd segfault shows in dmesg after a while. 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+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 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc
The issue there seems to be with the servers not up to current standard and what gnutls enforce, is there anything that needs to be done from the online accounts or evolution? ** Changed in: gnome-online-accounts (Ubuntu) Importance: Undecided => Low ** Changed in: evolution (Ubuntu) Importance: Undecided => Low ** Changed in: evolution (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-online-accounts (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1860461 Title: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough)." Status in evolution package in Ubuntu: Incomplete Status in gnome-online-accounts package in Ubuntu: Incomplete Status in gnutls28 package in Ubuntu: Incomplete Bug description: After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client with the following error: "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough)." I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and to install 19.10 dependency libhogweed4 3.4.1-1 to fix it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgnutls30 3.6.9-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Tue Jan 21 17:48:39 2020 InstallationDate: Installed on 2017-06-21 (943 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnutls28 UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1885562] Re: [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode
** Description changed: + [Impact] + + * Prevents using some parts of nss in FIPS mode - e.g. + libfreeblpriv3.so (failed asserts). The library during initialization + tries to verify it's own binaries against signatures in chk files + shipped along with it (created at build time). They are installed at + /usr/lib/$(DEB_HOST_MULTIARCH)/nss while it tries to look for them at + /usr/lib/$(DEB_HOST_MULTIARCH). + + [Test Case] + + * Setup Ubuntu 18.04 in FIPS mode. + * sudo apt install chrony + * sudo chronyd -d + * chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed. + + [Regression Potential] + + * Fix introduces 2 new artifacts to the filesystem (symlinks to the chk + files). It may cause alerts in e.g. CI systems. + + [Other Info] + Original bug description: + In FIPS mode there are some additional checks performed. They lead to verifying binaries signatures. Those signatures are shipped in the libnss3 package as *.chk files installed in /usr/lib/$(DEB_HOST_MULTIARCH)/nss. Along with those files are the libraries themselves (libfreebl3.so libfreeblpriv3.so libnssckbi.so libnssdbm3.so libsoftokn3.so). Those libraries are symlinked to be present in /usr/lib/$(DEB_HOST_MULTIARCH): ls -l /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so lrwxrwxrwx 1 root root 21 Jun 10 18:54 /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so -> nss/libfreeblpriv3.so The client binaries are linked against the symlinks, so when the verification happens (lib/freebl/shvfy.c) the mkCheckFileName function takes path to the symlink to the shlib and replaces the .so extension with .chk. Then it tries to open that file. Obviosly it fails, because the actual file is in /usr/lib/$(DEB_HOST_MULTIARCH)/nss. [Test case] sudo apt install chrony sudo chronyd -d chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed. Potential solutions: Solution A: Drop the /usr/lib/$(DEB_HOST_MULTIARCH)/nss directory and put all signatures and libs in /usr/lib/$(DEB_HOST_MULTIARCH). Solution B: Create symlinks to *.chk files in /usr/lib/$(DEB_HOST_MULTIARCH) (like it is done for *.so). Solution C: Implement and upstream NSS feature of resolving symlinks and looking for *.chk where the symlinks lead to. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1885562 Title: [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode Status in nss package in Ubuntu: In Progress Status in nss source package in Bionic: In Progress Status in nss source package in Focal: In Progress Status in nss source package in Groovy: In Progress Bug description: [Impact] * Prevents using some parts of nss in FIPS mode - e.g. libfreeblpriv3.so (failed asserts). The library during initialization tries to verify it's own binaries against signatures in chk files shipped along with it (created at build time). They are installed at /usr/lib/$(DEB_HOST_MULTIARCH)/nss while it tries to look for them at /usr/lib/$(DEB_HOST_MULTIARCH). [Test Case] * Setup Ubuntu 18.04 in FIPS mode. * sudo apt install chrony * sudo chronyd -d * chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed. [Regression Potential] * Fix introduces 2 new artifacts to the filesystem (symlinks to the chk files). It may cause alerts in e.g. CI systems. [Other Info] Original bug description: In FIPS mode there are some additional checks performed. They lead to verifying binaries signatures. Those signatures are shipped in the libnss3 package as *.chk files installed in /usr/lib/$(DEB_HOST_MULTIARCH)/nss. Along with those files are the libraries themselves (libfreebl3.so libfreeblpriv3.so libnssckbi.so libnssdbm3.so libsoftokn3.so). Those libraries are symlinked to be present in /usr/lib/$(DEB_HOST_MULTIARCH): ls -l /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so lrwxrwxrwx 1 root root 21 Jun 10 18:54 /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so -> nss/libfreeblpriv3.so The client binaries are linked against the symlinks, so when the verification happens (lib/freebl/shvfy.c) the mkCheckFileName function takes path to the symlink to the shlib and replaces the .so extension with .chk. Then it tries to open that file. Obviosly it fails, because the actual file is in /usr/lib/$(DEB_HOST_MULTIARCH)/nss. [Test case] sudo apt install chrony sudo chronyd -d chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed. Potential solutions: Solution A: Drop the /usr/lib/$(DEB_HOST_MULTIARCH)/nss directory and put all signatures and libs in /usr/lib/$(DEB_HOST_MULTIARCH). Solution B: Create symlinks to *.chk files in /usr/lib/$(DEB_HOST_MULTIARCH) (like it is done for *.so). Solution C: Implement and upstream NSS feature of resolving symlinks and looking for *.chk where the symlinks
[Touch-packages] [Bug 1590656] Re: apport-kde from xenial crashes due to charset encodings
In focal there are no longer problems with this, issues can be reported via drkonqui and everything works normally. ** Changed in: apport (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1590656 Title: apport-kde from xenial crashes due to charset encodings Status in apport package in Ubuntu: Fix Released Bug description: When using apport-collect in an environment with kde, it consistently crashes --- $ apport-collect 1589997 dpkg-query: no packages found matching linux Traceback (most recent call last): File "/usr/share/apport/apport-kde", line 530, in sys.exit(UserInterface.run_argv()) File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 653, in run_argv return self.run_update_report() File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 569, in run_update_report response = self.ui_present_report_details(allowed_to_report) File "/usr/share/apport/apport-kde", line 367, in ui_present_report_details desktop_info) File "/usr/share/apport/apport-kde", line 184, in __init__ self.ui.ui_update_view(self) File "/usr/share/apport/apport-kde", line 358, in ui_update_view QTreeWidgetItem(keyitem, [str(line)]) UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 21: ordinal not in range(128) - There is a patch in a comment in this bug (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1368911) by @schmod, but the bug is for apport, hence I am opening this as a new one. I tested the patch on my system and now it works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1590656/+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 1790205] Re: systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is.
Same issue on Bionic, installed May 15 (2 months ago): ➜ ~ sudo journalctl --disk-usage Archived and active journals take up 4.1G in the file system. My logs are definitely clogged with endless JavaScript errors from gnome-shell. Something I would not expect to slowly consume all disk space. What could be helpful feedback for this issue? -- 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/1790205 Title: systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is. Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: After running Bionic for 3 months, I had 2.6 GB of journals. I would not expect from a normal desktop user that they should have to run commands like `sudo journalctl --vacuum-time=10d`. I would nominate this command as a sane default to have running at each reboot to ensure that logs do not exceed 500 MB: sudo journalctl --vacuum-size=500M Supposedly, a server should by default retain more logs, so perhaps this should be implemented through a configuration package "systemd- configuration-desktop" as a dependency of the ubuntu-desktop meta package? . as it turns out, it's hard to see how much disk space is used, and what the upper limit is, even when it is set and respected by default. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1790205/+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
