[Touch-packages] [Bug 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled
Hi Jérôme, Apparently I missed your message as well. These patches have been included in kernel v5.7, and oem-6.0 has EOL-ed. ** No longer affects: bluez (Ubuntu) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-6.0 (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => Invalid -- 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/1823076 Title: System wakes up immediately after suspend if Bluetooth is still enabled Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem-6.0 source package in Bionic: Invalid Status in linux source package in Focal: Confirmed Status in linux-oem-6.0 source package in Focal: Won't Fix Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823076/+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 1971712] Re: Add support for Intel DG2
** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1971712] Re: Add support for Intel DG2
SRU V4: https://lists.ubuntu.com/archives/kernel- team/2022-May/130484.html (oem-5.17) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1971712] Re: Add support for Intel DG2
SRU V3: https://lists.ubuntu.com/archives/kernel- team/2022-May/130313.html (linux-oem-5.17) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in linux-oem-5.17 source package in Jammy: New Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1971712] Re: Add support for Intel DG2
SRU V2: * https://lists.ubuntu.com/archives/kernel-team/2022-May/130305.html (linux-oem-5.17) * https://lists.ubuntu.com/archives/kernel-team/2022-May/130306.html (linux-meta-oem-5.17) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in linux-oem-5.17 source package in Jammy: New Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1940504] Re: Support Alder Lake P graphics
SRU: https://lists.ubuntu.com/archives/kernel-
team/2021-August/123678.html (linux-firmware:focal)
** Changed in: linux-firmware (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
** Changed in: linux-firmware (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux-firmware (Ubuntu Focal)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Description changed:
+ [SRU Justification:linux-firmware]
+
+ [Impact]
+
+ It shows the firmware is missing, and runtime power management has been
+ disabled:
+
+ i915 :00:02.0: [drm] Failed to load DMC firmware
+ i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.
+
+ [Fix]
+
+ Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").
+
+ [Test Case]
+
+ Verified on Intel ADL-M/ADL-P RVPs.
+
+ [Where problems could occur]
+
+ It's a new firmware for new GPU, not possible to introduce regressions.
+
+ [Other Info]
+
+ Impish has this already. And while ADL-P/M support begins since v5.14,
+ only focal (for oem-5.14) is being nominated.
+
+ =
+
+ [SRU Justification:mesa,libdrm]
+
NOTE: this is for focal only, hirsute/impish do not and will not have
kernel support for this.
[Impact]
ADL-P machines need to use the native driver.
[Fix]
Backport support from upstream.
libdrm: a single patch from 2.4.107
mesa: three commits to add pci-id's and a workaround
kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports
[Test case]
Boot a machine and check that it's using the native driver and that the usual
workloads are fine.
[Where things could go wrong]
For older gpu's there's little to go wrong, since the commits are for ADL-P
only.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1940504
Title:
Support Alder Lake P graphics
Status in libdrm package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in mesa package in Ubuntu:
Fix Released
Status in libdrm source package in Focal:
Fix Committed
Status in linux-firmware source package in Focal:
In Progress
Status in linux-oem-5.13 source package in Focal:
New
Status in mesa source package in Focal:
Fix Committed
Bug description:
[SRU Justification:linux-firmware]
[Impact]
It shows the firmware is missing, and runtime power management has been
disabled:
i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.
[Fix]
Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").
[Test Case]
Verified on Intel ADL-M/ADL-P RVPs.
[Where problems could occur]
It's a new firmware for new GPU, not possible to introduce
regressions.
[Other Info]
Impish has this already. And while ADL-P/M support begins since v5.14,
only focal (for oem-5.14) is being nominated.
=
[SRU Justification:mesa,libdrm]
NOTE: this is for focal only, hirsute/impish do not and will not have
kernel support for this.
[Impact]
ADL-P machines need to use the native driver.
[Fix]
Backport support from upstream.
libdrm: a single patch from 2.4.107
mesa: three commits to add pci-id's and a workaround
kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports
[Test case]
Boot a machine and check that it's using the native driver and that the usual
workloads are fine.
[Where things could go wrong]
For older gpu's there's little to go wrong, since the commits are for ADL-P
only.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1940504] Re: Support Alder Lake P graphics
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1940504 Title: Support Alder Lake P graphics Status in libdrm package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in libdrm source package in Focal: Fix Committed Status in linux-firmware source package in Focal: New Status in linux-oem-5.13 source package in Focal: New Status in mesa source package in Focal: Fix Committed Bug description: NOTE: this is for focal only, hirsute/impish do not and will not have kernel support for this. [Impact] ADL-P machines need to use the native driver. [Fix] Backport support from upstream. libdrm: a single patch from 2.4.107 mesa: three commits to add pci-id's and a workaround kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports [Test case] Boot a machine and check that it's using the native driver and that the usual workloads are fine. [Where things could go wrong] For older gpu's there's little to go wrong, since the commits are for ADL-P only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1926062] Re: [hirsute/impish] Realtek RTL8821AE 802.11ac PCIe [10ec:8821] Subsystem [17aa:a814]: Can't turn bluetooth on again after turning it off
** Summary changed: - [hirsute/impish] Can't turn bluetooth on again after turning it off + [hirsute/impish] Realtek RTL8821AE 802.11ac PCIe [10ec:8821] Subsystem [17aa:a814]: Can't turn bluetooth on again after turning it off ** Description changed: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS + + Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: - LANGUAGE=en_IN:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_IN - SHELL=/bin/bash + LANGUAGE=en_IN:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_IN + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: - hci0:Type: Primary Bus: USB - BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 - DOWN - RX bytes:744804 acl:76 sco:0 events:105989 errors:0 - TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 + hci0:Type: Primary Bus: USB + BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 + DOWN + RX bytes:744804 acl:76 sco:0 events:105989 errors:0 + TX bytes:51871528 acl:113157 sco:0 commands:192 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/1926062 Title: [hirsute/impish] Realtek RTL8821AE 802.11ac PCIe [10ec:8821] Subsystem [17aa:a814]: Can't turn bluetooth on again after turning it off Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29
[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275 was marked as a duplicate of https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859. https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 is probably a duplicate of 2859, too. ** Description changed: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 + https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #2859 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3)
[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
Re-attach full dmesg log with this issue reproduced on RKL SDP (202102-28687) running 5.12-rc8. ** Attachment added: "journalctl.RKL-SDP.5.12.0-8-generic.gz" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1918855/+attachment/5490979/+files/journalctl.RKL-SDP.5.12.0-8-generic.gz ** Attachment removed: "dmesg.RKL-SDP.5.12.0-8-generic" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1918855/+attachment/5490918/+files/dmesg.RKL-SDP.5.12.0-8-generic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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 1918855] Re: Xorg xserver got signal 6 to abort
Attach also dmesg from drm-tip today, version 5.12.0-051200rc8drmtip20210422-generic on RKL SDP installed Focal. Also using linux-firmware from upstream master HEAD. ** Attachment added: "journalctl.5.12.0-051200rc8drmtip20210422-generic.gz" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1918855/+attachment/5490974/+files/journalctl.5.12.0-051200rc8drmtip20210422-generic.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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
Re: [Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
Also reproduced on RKL SDP (202102-28687) running 5.12-rc8. Checking drm-tip. ** Attachment added: "dmesg.RKL-SDP.5.12.0-8-generic" https://bugs.launchpad.net/bugs/1918855/+attachment/5490918/+files/dmesg.RKL-SDP.5.12.0-8-generic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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 1918855] Re: Xorg xserver got signal 6 to abort
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275#note_796719:
```
if (ret < 0) {
#ifdef DEBUG
const bool color = INTEL_DEBUG & DEBUG_COLOR;
fprintf(stderr, "%siris: Failed to submit batchbuffer: %-80s%s\n",
color ? "\e[1;41m" : "", strerror(-ret), color ? "\e[0m" : "");
#endif
abort();
}
```
which means `submit_batch` failed, which means `DRM_IOCTL_I915_GEM_EXECBUFFER2`
failed.
(keep a note here)
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #4275
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855
Title:
Xorg xserver got signal 6 to abort
Status in Mesa:
Unknown
Status in OEM Priority Project:
New
Status in mesa package in Ubuntu:
New
Bug description:
I run checkbox job
com.canonical.certification::memory/memory_stress_ng on focal, and the
xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1918855/+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 1915491] Re: Dell Latitude E7470 wifi adapter (Intel Corporation Wireless 8260 [8086:24f3]) installed but can't be found in Settings
** Tags added: hwe-networking-wifi ** Summary changed: - Dell Latitude E7470 wifi adapter (Intel Corporation Wireless 8260 [8086:24f3]) installed but can't be found in Settings + Dell Latitude E7470 wifi adapter (Intel Corporation Wireless 8260 [8086:24f3] subsystem [8086:0050]) installed but can't be found in Settings -- 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/1915491 Title: Dell Latitude E7470 wifi adapter (Intel Corporation Wireless 8260 [8086:24f3] subsystem [8086:0050]) installed but can't be found in Settings Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: # Summary: > ## Wifi Adpter Not found ## Steps to Reproduce: - I don't know ## Expected Results: Wifi should always be available ## Problem Description: Sometimes when startup my pc there is no wifi icon on the top right corner menu. When checking the wifi settings on the settings window it shows that the wifi adapter not found. But after restarting the pc, everything back to normal again. This is happening too frequently now. * * * Screenshot: https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 12 11:13:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Latitude E7470 [1028:06dc] InstallationDate: Installed on 2021-01-06 (36 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E7470 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.3 dmi.board.name: 047I7V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915491/+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 1910405] Re: bluetoothd hangs and cannot be killed
jan 11 11:59:05 omer kernel: Bluetooth: hci0: Received unexpected HCI Event jan 11 11:59:05 omer kernel: Bluetooth: hci0: Received unexpected HCI Event jan 11 11:59:05 omer kernel: Bluetooth: hci0: Received unexpected HCI Event jan 11 11:59:05 omer kernel: Bluetooth: hci0: Received unexpected HCI Event jan 11 11:59:47 omer bluetoothd[13716]: Suspend: Connection timed out (110) jan 11 11:59:47 omer kernel: Bluetooth: hci0: Received unexpected HCI Event Looks like a firmware issue and bug 1905214 updated firmware intel/ibt-20-1-3.sfi to REL13705 in Focal while it remains REL0310 in Bionic. Could you try download following two files and place them in /lib/firmware/intel. They are the firmware blobs currently used in Focal. Backup first of course. * https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-firmware/plain/intel/ibt-20-1-3.ddc?h=focal * https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-firmware/plain/intel/ibt-20-1-3.sfi?h=focal Upstream linux-firmware has even newer revisions. Please try following two if Focal's still don't resolve your problem: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/intel/ibt-20-1-3.ddc * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/intel/ibt-20-1-3.sfi ** Tags added: hwe-bluetooth ** Summary changed: - bluetoothd hangs and cannot be killed + Intel Bluetooth AX200 [8086:2723] Subsystem [1a56:1653]: bluetoothd hangs and cannot be killed -- 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/1910405 Title: Intel Bluetooth AX200 [8086:2723] Subsystem [1a56:1653]: bluetoothd hangs and cannot be killed Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hi, When having a bluetooth headphone (JBL Live) connected using the A2DP pulseaudio sink, the output sound suddenly stops during a music streaming of videocall session. Sometimes just disconnecting and reconnecting the headphone works, but some times reconnection is not possible anymore due to the hanging of bluetoothd. Bluetoothd still appears in the processes list, but cannot be killed, neither with "sudo service bluetooth stop" or "kill -9": $ ps afx | grep blue 9597 tty2 Sl+0:01 | \_ gnome-control-center bluetooth 5405 ?Ss 0:00 \_ /usr/lib/bluetooth/obexd 10694 pts/0S+ 0:00 \_ grep blue 20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd All programs keep working normally, only bluetooth is affected as well as the bluetooth settings page. The only solution is a hard reboot. A soft reboot doesn't even work: the systems keeps trying to end the bluetoothd process so one needs to press the power button for a few seconds to terminate the process. $ bluetoothd --version 5.48 $ uname -a Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working nice for over one year now just like previous versions. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-11-22 (415 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 7390 Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78 Tags: bionic Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/22/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:1D:96:DA:70:EA ACL MTU: 1021:4 SCO
[Touch-packages] [Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
Verified 1.22.10-1ubuntu2.2 from focal-proposed with packages network- manager, libnm0, gir1.2-nm-1.0, network-manager-config-connectivity- ubuntu installed. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit Status in OEM Priority Project: New Status in OEM Priority Project focal series: Invalid Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Focal: Fix Committed Bug description: [Impact] In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager). The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. So, the management of wake-on-LAN still is done by NetworkManager. The killer 500s Wi-Fi does not want the network-manger to manager the wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set. (The driver will manager itself.) When the network-manager managers the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS resumed from suspend. [Test Case] On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. Step 1. Enter suspend (s2idle) Setp 2. Resume from suspend After resume from suspend, the Wi-Fi function still is normal. You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 [Regression Potential] * This patch modifies the wake on lan parameters, please test that the corresponding feature still works fine with the different configuration values. 1. Magic packet test: Set Wake on Wireless to off Send magic packet to the system Ensure it does not wake up Set Wake on Wirless to on Send magic packet to the system Ensure it does wake up 2. Wi-Fi function test after resumed from suspend: After resume from suspend, the Wi-Fi should work normally. Scan APs. Connect to an AP. [Other Info] * platform: add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status check (!597) · Merge Requests · NetworkManager / NetworkManager · GitLab - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/597#note_588639 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+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 1898186] Re: Qualcomm Atheros Communications AR3011 USB 0cf3:3005 Bluetooth headset stopped connecting
I was wrong. You're referring to AR3011 connected to usb bus. But please still try the rfkill command above. -- 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/1898186 Title: Qualcomm Atheros Communications AR3011 USB 0cf3:3005 Bluetooth headset stopped connecting Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: 1. expected to connect the stereo headset via Bluetooth as usual. 2. Headset stopped connecting 3. Updated again, checked the headset on Android. It works on Android, but not in Ubuntu. - after a recent system update (1-3 years ago), the stereo headset stopped connecting. maybe something related #295012 Bluetooth ALSA Crash with Skype ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 2 16:41:55 2020 InstallationDate: Installed on 2020-05-02 (152 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire V5-571G ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=17fd49fa-ba18-4d43-b4ca-a3ad62753fd3 ro zswap.enabled=1 quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.17 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.17 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.17 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.17:bd02/27/2013:svnAcer:pnAspireV5-571G:pvrV2.17:rvnAcer:rnAspireV5-571G:rvrV2.17:cvnAcer:ct9:cvrV2.17: dmi.product.family: Aspire V5-571G dmi.product.name: Aspire V5-571G dmi.product.sku: Aspire V5-571G_072D_2.17 dmi.product.version: V2.17 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: E0:91:53:65:99:10 ACL MTU: 1022:8 SCO MTU: 121:3 UP RUNNING PSCAN ISCAN RX bytes:18789 acl:40 sco:0 events:408 errors:0 TX bytes:2538 acl:36 sco:0 commands:135 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1898186/+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 1898186] Re: Qualcomm Atheros AR9285 [168c:002b] Subsystem [1b9a:0c03] [Qualcomm Atheros Communications AR3011] Bluetooth headset stopped connecting
lspci has: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01) Subsystem: XAVi Technologies Corp. WB214E 802.11bgn Wireless Half-size Mini PCIe Card [AR9002WB-1NGCD] [1b9a:0c03] Maybe a AR5BWB222 precisely: https://www.notebookcheck.net/Review-Acer- Aspire-V5-571G-Notebook.78314.0.html#toc-connectivity Syslog has: bluetoothd[901]: Failed to set mode: Blocked through rfkill (0x12) Can you execute `rfkill list` and paste the result? You may want to try `rfkill unblock all` if you find anything listed as blocked. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: hwe-bluetooth ** Summary changed: - Qualcomm Atheros AR9285 [168c:002b] Subsystem [1b9a:0c03] [Qualcomm Atheros Communications AR3011] Bluetooth headset stopped connecting + Qualcomm Atheros Communications AR3011 USB 0cf3:3005 Bluetooth headset stopped connecting -- 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/1898186 Title: Qualcomm Atheros Communications AR3011 USB 0cf3:3005 Bluetooth headset stopped connecting Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: 1. expected to connect the stereo headset via Bluetooth as usual. 2. Headset stopped connecting 3. Updated again, checked the headset on Android. It works on Android, but not in Ubuntu. - after a recent system update (1-3 years ago), the stereo headset stopped connecting. maybe something related #295012 Bluetooth ALSA Crash with Skype ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 2 16:41:55 2020 InstallationDate: Installed on 2020-05-02 (152 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire V5-571G ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=17fd49fa-ba18-4d43-b4ca-a3ad62753fd3 ro zswap.enabled=1 quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.17 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.17 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.17 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.17:bd02/27/2013:svnAcer:pnAspireV5-571G:pvrV2.17:rvnAcer:rnAspireV5-571G:rvrV2.17:cvnAcer:ct9:cvrV2.17: dmi.product.family: Aspire V5-571G dmi.product.name: Aspire V5-571G dmi.product.sku: Aspire V5-571G_072D_2.17 dmi.product.version: V2.17 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: E0:91:53:65:99:10 ACL MTU: 1022:8 SCO MTU: 121:3 UP RUNNING PSCAN ISCAN RX bytes:18789 acl:40 sco:0 events:408 errors:0 TX bytes:2538 acl:36 sco:0 commands:135 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1898186/+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 1898186] Re: Qualcomm Atheros AR9285 [168c:002b] Subsystem [1b9a:0c03] [Qualcomm Atheros Communications AR3011] Bluetooth headset stopped connecting
** Summary changed: - [Qualcomm Atheros Communications AR3011] Bluetooth headset stopped connecting + Qualcomm Atheros AR9285 [168c:002b] Subsystem [1b9a:0c03] [Qualcomm Atheros Communications AR3011] Bluetooth headset stopped connecting -- 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/1898186 Title: Qualcomm Atheros AR9285 [168c:002b] Subsystem [1b9a:0c03] [Qualcomm Atheros Communications AR3011] Bluetooth headset stopped connecting Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: 1. expected to connect the stereo headset via Bluetooth as usual. 2. Headset stopped connecting 3. Updated again, checked the headset on Android. It works on Android, but not in Ubuntu. - after a recent system update (1-3 years ago), the stereo headset stopped connecting. maybe something related #295012 Bluetooth ALSA Crash with Skype ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 2 16:41:55 2020 InstallationDate: Installed on 2020-05-02 (152 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire V5-571G ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=17fd49fa-ba18-4d43-b4ca-a3ad62753fd3 ro zswap.enabled=1 quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.17 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.17 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.17 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.17:bd02/27/2013:svnAcer:pnAspireV5-571G:pvrV2.17:rvnAcer:rnAspireV5-571G:rvrV2.17:cvnAcer:ct9:cvrV2.17: dmi.product.family: Aspire V5-571G dmi.product.name: Aspire V5-571G dmi.product.sku: Aspire V5-571G_072D_2.17 dmi.product.version: V2.17 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: E0:91:53:65:99:10 ACL MTU: 1022:8 SCO MTU: 121:3 UP RUNNING PSCAN ISCAN RX bytes:18789 acl:40 sco:0 events:408 errors:0 TX bytes:2538 acl:36 sco:0 commands:135 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1898186/+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 1893325] Re: Date has issue after adjusting it ahead of 1 April 2020
https://github.com/systemd/systemd/commit/021dd87bc055a5bfb2dcef83fc868fe24648b959 This is a result of systemd source epoch adjustment. So for all the distributions running systemd as the init daemon, they will share the same behavior. It's a "feature". ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** No longer affects: coreutils (Ubuntu) ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1893325 Title: Date has issue after adjusting it ahead of 1 April 2020 Status in systemd package in Ubuntu: Invalid Bug description: OS: 20.04 Steps to reproduce: Adjust system time to ahead of "1 April 2020" and reboot Expected result: System time is modified successfully after restart Actual result: The adjustment won't be saved after restart and the system time change to 1 April 2020 Note: If set the system time after 1 April 2020, the change will be saved after restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1893325/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
That should be a regression introduced in bug 1861451, which is to allow gathering information as root under non-gui env. -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in apport source package in Bionic: Fix Committed Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: Fix Released Status in linux-firmware source package in Focal: Invalid Bug description: Updated Description to match SRU requirements for bionic [Impact] linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks/source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. [Test Case] 1) On an Ubuntu 18.04 LTS system run 'apport-cli linux-firmware'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. [Regression Potential] Very limited, as we are just adding a symlink from linux-firmware to the linux source package hook. this change has been available in Focal and Groovy without problem Original Description ProblemType: BugDistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: allSourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1644445] Re: avila xenial+systemd port takes too long to boot to GUI
** Changed in: lxc-android-config (Ubuntu) Status: In Progress => Won't Fix ** Changed in: ubuntu-touch-session (Ubuntu) Status: In Progress => Won't Fix ** Changed in: repowerd (Ubuntu) Status: In Progress => Won't Fix ** Changed in: canonical-devices-system-image Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/165 Title: avila xenial+systemd port takes too long to boot to GUI Status in Canonical System Image: Invalid Status in lxc-android-config package in Ubuntu: Won't Fix Status in repowerd package in Ubuntu: Won't Fix Status in ubuntu-touch-session package in Ubuntu: Won't Fix Bug description: We found devices will take about 80 seconds to show the ubuntu flash UI, and after about 60 seconds to show the login UI. So it will take more than 2 minutes to boot up the system. [[1. on xenial+systemd/arm64]]: Second boot time: Without flight mode: 25s to ubuntu splash, 93s to login dialog With flight mode: 46s to ubuntu splash, 120s to login dialog Without flight mode, but disable ofono completely: 84s to ubuntu splash, 143s to login dialog. Worse cases are also observed. $ adb shell system-image-cli -i current build number: 84 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-11-17 03:23:16 version version: 84 version ubuntu: 20161117 version device: 20161014.0 version custom: 20161117 [[2. on vivid+upstart/armhf]]: Second boot time: Without flight mode: The worse case I got is 78s to ubuntu splash, 92s to login dialog. However I have this only once and am never able to reproduce the same. The usual cases have almost no difference from the following two cases. All boot to splash in 10s and login dialog in around 22s. With flight mode: 9s to ubuntu splash, 19s to login dialog Without flight mode, but disable ofono completely: 9s to ubuntu splash, 21s to login dialog $ adb shell system-image-cli -i current build number: 235 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en last update: 2016-11-19 11:56:02 version version: 235 version ubuntu: 20161119 version device: 20160809.0 version custom: 20160831--42-26-vivid [[Debug Tips]] 1. Flash xenial user build: $ ubuntu-device-flash touch --bootstrap --wipe \ --channel=ubuntu-touch/staging/ubuntu \ --device=frieza_arm64 [--recovery-image=recovery.img] 2. Flash vivid user build: $ ubuntu-device-flash touch --bootstrap --wipe \ --channel=ubuntu-touch/rc-proposed/bq-aquaris-pd.en \ --device=frieza [--recovery-image=recovery.img] To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/165/+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 1643459] Re: additional writable paths for other system services
** Changed in: lxc-android-config (Ubuntu) Status: In Progress => Won't Fix ** Changed in: udisks2 (Ubuntu) Status: New => Won't Fix ** Changed in: canonical-devices-system-image Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1643459 Title: additional writable paths for other system services Status in Canonical System Image: Invalid Status in lxc-android-config package in Ubuntu: Won't Fix Status in udisks2 package in Ubuntu: Won't Fix Bug description: /var/tmp: rtkit systemd service uses PrivateTmp /var/lib/udisks2: udisks2 /var/lib/dhcp: isc-dhcp-server leases files To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1643459/+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 1641549] Re: migrate lxc android container to lxd
** Changed in: urfkill (Ubuntu) Status: New => Won't Fix ** Changed in: lxc-android-config (Ubuntu) Status: New => Won't Fix ** Changed in: canonical-devices-system-image Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Invalid Status in lxc-android-config package in Ubuntu: Won't Fix Status in urfkill package in Ubuntu: Won't Fix Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. apply changes from https://code.launchpad.net/~vicamo/lxc-android- config/lxd-migration/+merge/311103 . This cause the system to automatically import android initrd as an lxd image and to start it up on boot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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 1642535] Re: need /var/snap writable-path for snappy global data
** Changed in: lxc-android-config (Ubuntu) Status: New => Won't Fix ** Changed in: canonical-devices-system-image Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1642535 Title: need /var/snap writable-path for snappy global data Status in Canonical System Image: Invalid Status in lxc-android-config package in Ubuntu: Won't Fix Bug description: This is a follow-up for bug 1632272. From snap-confine source code[1], when running on classic distribution as we're for ubuntu-touch, some additional paths are mounted. They are /dev, /etc, /home, /root, /proc, /sys, /tmp, /var/snap, /var/lib/snapd, /var/tmp, /run, /lib/modules, /media, etc. Among them, /var/snap is necessary for lxd snap global data like pid file, daemon socket, and images. [1]: https://github.com/snapcore/snap-confine/blob/master/src/mount- support.c#L556 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642535/+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 1641561] Re: make android lxc as a snap
** Changed in: lxc-android-config (Ubuntu) Status: New => Won't Fix ** Changed in: canonical-devices-system-image Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641561 Title: make android lxc as a snap Status in Canonical System Image: Invalid Status in lxc-android-config package in Ubuntu: Won't Fix Bug description: With snapd running in current Ubuntu Touch Xenial port, we'd like to package whole android container as a snap for the final all-snap target. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641561/+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 1885496] Re: Intel Wireless 8260 [8086:24f3] Subsystem [8086:9010] Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu
** Summary changed: - Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu + Intel Wireless 8260 [8086:24f3] Subsystem [8086:9010] Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu -- 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/1885496 Title: Intel Wireless 8260 [8086:24f3] Subsystem [8086:9010] Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Current behavior: In gnome-control-center I see the Bluetooth slider is set to Off and the status shows "Bluetooth Turned Off". My Bluetooth audio receiver which had previously been paired can still control VLC, or any other compatible media player with a Pause/Play button. If no compatible app is running then an error icon appears.[0] Expected behavior: when gnome-control-center Bluetooth shows Disabled, then no bluetooth device should be able to communicate with the computer. Security: This is way out of my wheelhouse, but if this goes beyond my use case, could this have security implications? Just the fact that the bluetooth subsystem is functional when the UI says it is not, seems like a bad sign, correct? EDIT: as a next step, when I enabled Bluetooth in gnome-control- center I see the device's status as "Disconnected" and the device does not appear as a possible sound output device in Sound settings. In this Bluetooth enabled state, the pause/play button still works. When I disable all Bluetooth, the pause/play button still works. EDIT2: I'm not sure what the gnome-control-center Bluetooth On/Off slider is supposed to do, but while gnome-control-center Bluetooth shows disabled the service is still running. $ service bluetooth status bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2020-06-26 10:09:48 PDT; 2 days ago Docs: man:bluetoothd(8) Main PID: 935 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38343) Memory: 3.0M CGroup: /system.slice/bluetooth.service └─935 /usr/lib/bluetooth/bluetoothd Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth daemon 5.53 Jun 26 10:09:48 nyuk systemd[1]: Started Bluetooth service. Jun 26 10:09:48 nyuk bluetoothd[935]: Starting SDP server Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth management interface 1.14 initialized Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSink/sbc Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/sbc Jun 26 20:55:06 nyuk bluetoothd[935]: /org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd0: fd(37) ready Jun 26 20:56:12 nyuk bluetoothd[935]: /org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd1: fd(37) ready Jun 26 21:23:45 nyuk bluetoothd[935]: Failed to set mode: Blocked through rfkill (0x12) Jun 28 20:58:41 nyuk bluetoothd[935]: Failed to set mode: Blocked through rfkill (0x12) [0] https://i.imgur.com/e2nM7hA.png ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 28 21:11:45 2020 InstallationDate: Installed on 2020-06-17 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 002 Device 002: ID 152d:0567 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=7d791ec0-a9ea-415e-b7ec-6260b85b55f7 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: SYSKLi35.86A.0045.2016.0527.1055 dmi.board.asset.tag: �=\� dmi.board.name: NUC6i5SYB dmi.board.vendor: Intel corporation dmi.board.version: H81131-504 dmi.chassis.type: 3 dmi.modalias:
[Touch-packages] [Bug 1885496] Re: Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu
** Tags added: hwe-bluetooth -- 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/1885496 Title: Intel Wireless 8260 [8086:24f3] Subsystem [8086:9010] Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Current behavior: In gnome-control-center I see the Bluetooth slider is set to Off and the status shows "Bluetooth Turned Off". My Bluetooth audio receiver which had previously been paired can still control VLC, or any other compatible media player with a Pause/Play button. If no compatible app is running then an error icon appears.[0] Expected behavior: when gnome-control-center Bluetooth shows Disabled, then no bluetooth device should be able to communicate with the computer. Security: This is way out of my wheelhouse, but if this goes beyond my use case, could this have security implications? Just the fact that the bluetooth subsystem is functional when the UI says it is not, seems like a bad sign, correct? EDIT: as a next step, when I enabled Bluetooth in gnome-control- center I see the device's status as "Disconnected" and the device does not appear as a possible sound output device in Sound settings. In this Bluetooth enabled state, the pause/play button still works. When I disable all Bluetooth, the pause/play button still works. EDIT2: I'm not sure what the gnome-control-center Bluetooth On/Off slider is supposed to do, but while gnome-control-center Bluetooth shows disabled the service is still running. $ service bluetooth status bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2020-06-26 10:09:48 PDT; 2 days ago Docs: man:bluetoothd(8) Main PID: 935 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38343) Memory: 3.0M CGroup: /system.slice/bluetooth.service └─935 /usr/lib/bluetooth/bluetoothd Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth daemon 5.53 Jun 26 10:09:48 nyuk systemd[1]: Started Bluetooth service. Jun 26 10:09:48 nyuk bluetoothd[935]: Starting SDP server Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth management interface 1.14 initialized Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSink/sbc Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/sbc Jun 26 20:55:06 nyuk bluetoothd[935]: /org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd0: fd(37) ready Jun 26 20:56:12 nyuk bluetoothd[935]: /org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd1: fd(37) ready Jun 26 21:23:45 nyuk bluetoothd[935]: Failed to set mode: Blocked through rfkill (0x12) Jun 28 20:58:41 nyuk bluetoothd[935]: Failed to set mode: Blocked through rfkill (0x12) [0] https://i.imgur.com/e2nM7hA.png ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 28 21:11:45 2020 InstallationDate: Installed on 2020-06-17 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 002 Device 002: ID 152d:0567 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=7d791ec0-a9ea-415e-b7ec-6260b85b55f7 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: SYSKLi35.86A.0045.2016.0527.1055 dmi.board.asset.tag: �=\� dmi.board.name: NUC6i5SYB dmi.board.vendor: Intel corporation dmi.board.version: H81131-504 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0045.2016.0527.1055:bd05/27/2016:svn:pn:pvr:rvnIntelcorporation:rnNUC6i5SYB:rvrH81131-504:cvn:ct3:cvr: hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:F8:FA:D3 ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:14600494 acl:95
[Touch-packages] [Bug 1869940] Re: QCA6174 [168c:003e] Subsystem [1a56:1535]: No networks available/visible after suspend
*** This bug is a duplicate of bug 1883536 *** https://bugs.launchpad.net/bugs/1883536 ** This bug has been marked a duplicate of bug 1883536 Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:1535] WiFi does not work after suspend -- 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/1869940 Title: QCA6174 [168c:003e] Subsystem [1a56:1535]: No networks available/visible after suspend Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: WiFI network disconnected and no networks visible after resume from suspend. Had to reboot the machine to get networking (WiFI) back up and running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 21:18:43 2020 InstallationDate: Installed on 2020-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) IpRoute: default via 192.168.1.1 dev wlp59s0 proto dhcp metric 600 169.254.0.0/16 dev wlp59s0 scope link metric 1000 192.168.1.0/24 dev wlp59s0 proto kernel scope link src 192.168.1.30 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME DORIAN 2c3f821d-0865-4747-974a-2f861ee0dc38 wifi 1585682245 tis 31 mar 2020 21:17:25 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp59s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/DORIAN.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp59s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 DORIAN 2c3f821d-0865-4747-974a-2f861ee0dc38 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp59s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869940/+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 1822633] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:1535] Pairing failure with BLE 4.0
** Summary changed:
- Pairing failure with BLE 4.0
+ Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:1535] Pairing failure
with BLE 4.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/1822633
Title:
Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:1535] Pairing
failure with BLE 4.0
Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
When attempting to pair a BLE 4.0 pen using Bluez, we receive
authentication errors.
Here is the FW from Jason.
Details:
===
I added a few debug statements (patch attached) to the kernel's
net/bluetooth/smp.c:smp_sig_channel() function
(https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
When I try to pair the PN579X, I get the following logs:
[ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
[ 5653.563053] DBG: Processing code...
[ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
[ 5653.709577] DBG: Processing code...
[ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
[ 5653.807089] DBG: Processing code...
[ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
[ 5654.148557] DBG: Processing code...
[ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
[ 5654.197027] DBG: Processing code...
[ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
[ 5654.245828] DBG: Processing code...
[ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
[ 5654.246182] DBG: Processing code...
[ 5657.610656] input: Dell Active Pen PN579X Keyboard as
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
[ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5
When I try to pair the PN557W, however, I only get the following:
[ 64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
[ 64.924906] DBG: AuthReq = 00
[ 64.924907] ERR: Code not allowed on existing connection
[ 64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from
bc:82:5d:fa:5e:b7
[ 64.940314] NET: Registered protocol family 38
[ 65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
[ 65.022331] DBG: Processing code...
The "allowed" value is a bitmap, so 0024 means that only event
code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
beginning of the connection but *only* if the "smp" variable hasn't
been set yet. It looks like the host starts the pairing process and
initializes the "smp" variable, which then prevents code 11 from being
allowed.
I did try to force the code to allow code 11 at any time, but this
didn't seem to help the situation any. The device still sent code 5
("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
the trace above. Worse, the kernel logs a general protection fault
several seconds afterwards, so it clearly doesn't like the workaround.
I also find it odd that the "AuthReq = 00". I found a copy of the core
Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
AuthReq flags. All zero would seem to indicate that no security is
requested, and I'm not sure if the kernel enforces a minimum security
level or something.
Finally, I also tried the suggestion at
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/ on the assumption
that maybe this is an issue caused by LE communication rather than classic
BR/EDR communication. Alas, my computer wasn't even able to start the pairing
process after making the change.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-01-21 (70 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
InterestingModules: bnep btusb bluetooth
MachineType: Dell Inc. XPS 13 9360
Package: linux
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic
root=UUID=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Tags: third-party-packages bionic
Uname: Linux 4.15.0-46-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin
[Touch-packages] [Bug 1822633] Re: Pairing failure with BLE 4.0
** Tags added: hwe-networking-wifi
** Tags removed: hwe-networking-wifi
** Tags added: hwe-bluetooth
--
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/1822633
Title:
Pairing failure with BLE 4.0
Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
When attempting to pair a BLE 4.0 pen using Bluez, we receive
authentication errors.
Here is the FW from Jason.
Details:
===
I added a few debug statements (patch attached) to the kernel's
net/bluetooth/smp.c:smp_sig_channel() function
(https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
When I try to pair the PN579X, I get the following logs:
[ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
[ 5653.563053] DBG: Processing code...
[ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
[ 5653.709577] DBG: Processing code...
[ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
[ 5653.807089] DBG: Processing code...
[ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
[ 5654.148557] DBG: Processing code...
[ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
[ 5654.197027] DBG: Processing code...
[ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
[ 5654.245828] DBG: Processing code...
[ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
[ 5654.246182] DBG: Processing code...
[ 5657.610656] input: Dell Active Pen PN579X Keyboard as
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
[ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5
When I try to pair the PN557W, however, I only get the following:
[ 64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
[ 64.924906] DBG: AuthReq = 00
[ 64.924907] ERR: Code not allowed on existing connection
[ 64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from
bc:82:5d:fa:5e:b7
[ 64.940314] NET: Registered protocol family 38
[ 65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
[ 65.022331] DBG: Processing code...
The "allowed" value is a bitmap, so 0024 means that only event
code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
beginning of the connection but *only* if the "smp" variable hasn't
been set yet. It looks like the host starts the pairing process and
initializes the "smp" variable, which then prevents code 11 from being
allowed.
I did try to force the code to allow code 11 at any time, but this
didn't seem to help the situation any. The device still sent code 5
("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
the trace above. Worse, the kernel logs a general protection fault
several seconds afterwards, so it clearly doesn't like the workaround.
I also find it odd that the "AuthReq = 00". I found a copy of the core
Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
AuthReq flags. All zero would seem to indicate that no security is
requested, and I'm not sure if the kernel enforces a minimum security
level or something.
Finally, I also tried the suggestion at
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/ on the assumption
that maybe this is an issue caused by LE communication rather than classic
BR/EDR communication. Alas, my computer wasn't even able to start the pairing
process after making the change.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-01-21 (70 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
InterestingModules: bnep btusb bluetooth
MachineType: Dell Inc. XPS 13 9360
Package: linux
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic
root=UUID=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Tags: third-party-packages bionic
Uname: Linux 4.15.0-46-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/24/2017
dmi.bios.vendor: Dell Inc.
[Touch-packages] [Bug 1881612] Re: Intel AX1650i Bluetooth will not work in HSP/HFP (Headset/Hands-free)
** Tags added: hwe-bluetooth -- 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/1881612 Title: Intel AX1650i Bluetooth will not work in HSP/HFP (Headset/Hands-free) Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: On Dell Inspiron 3593 running Ubuntu 20.04, Bluetooth Headset Vipex VX-BH001 works in A2DP, but not in HSP/HFP. (So it cannot be used as a microphone.) Same headset works correctly on an older Dell Latitude under both 20.04 and 18.04, and works on the same laptop when using an external USB bluetooth adapter, so I conclude the issue is probably with the iwlwifi driver or firmware. The bluetooth headset pairs okay, but in sound settings if I switch configuration to "Headset Head Unit (HSP/HFP)", then the "test" dialog under "output" will not play sound, and the "input" panel does not show any incoming audio. I tried upgrading to -proposed kernel and installing updated firmware in /lib/firmware, but without improvement. I also note that 'modinfo iwlwifi' on my laptop lists support for firmware up to iwlwifi-Qu-c0-hr-b0-52.ucode, but linux-firmware.git has newer firmware published: iwlwifi-Qu-c0-jf-b0-55.ucode ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.6.0-1011.11-oem 5.6.14 Uname: Linux 5.6.0-1011-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: magnus207273 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 10:58:12 2020 InstallationDate: Installed on 2020-05-24 (8 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: pulseaudio Symptom: audio Symptom_Card: Vipex VX-BH001 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: magnus207273 F pulseaudio Symptom_Type: No sound at all Title: [Vipex VX-BH001, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0TGVJN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd03/24/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn0TGVJN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881612/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
@Brian, can we have this backport to Bionic as well? Bionic is to end extended desktop/server support on 2023 and extended security support on 2028, so it's still likely to receive bug reports in the future on Bionic. -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: Fix Released Status in linux-firmware source package in Focal: Invalid Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. Test Case - 1) On an Ubuntu 20.04 LTS system run 'apport-cli linux-firmware'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. Regression Potential None, as we are just adding a symlink from linux-firmware to the linux source package hook. Original Description ProblemType: BugDistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: allSourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1869940] Re: QCA6174 [168c:003e] Subsystem [1a56:1535]: No networks available/visible after suspend
** Summary changed: - No networks available/visible after suspend + QCA6174 [168c:003e] Subsystem [1a56:1535]: No networks available/visible after suspend ** Tags added: hwe-networking-wifi -- 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/1869940 Title: QCA6174 [168c:003e] Subsystem [1a56:1535]: No networks available/visible after suspend Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: WiFI network disconnected and no networks visible after resume from suspend. Had to reboot the machine to get networking (WiFI) back up and running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 21:18:43 2020 InstallationDate: Installed on 2020-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) IpRoute: default via 192.168.1.1 dev wlp59s0 proto dhcp metric 600 169.254.0.0/16 dev wlp59s0 scope link metric 1000 192.168.1.0/24 dev wlp59s0 proto kernel scope link src 192.168.1.30 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME DORIAN 2c3f821d-0865-4747-974a-2f861ee0dc38 wifi 1585682245 tis 31 mar 2020 21:17:25 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp59s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/DORIAN.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp59s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 DORIAN 2c3f821d-0865-4747-974a-2f861ee0dc38 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp59s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869940/+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 1870442] Re: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on.
** Tags added: hwe-networking-wifi -- 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/1870442 Title: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on. Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: When I was trying to connect to the network after rebooting the computer, and I disabled verification before the reboot, the laptop connected, but then, even though no other computers had this problem, the speed of the wi-fi shut down, and then the connection with the router dropped. All this until I turned Airplane Mode on and Wi-Fi on my PC for a brief second before disabling airplane mode and reenabling Wi-Fi. Ubuntu 18.04.4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Thu Apr 2 18:25:30 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 6fbfa44b-461e-4067-b37a-26f63bc54f88 wifi 1585866147 Thu 02 Apr 2020 06:22:27 PM EDT yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 0c4f5994-e9fb-3218-9aa5-d46003ebcd5a ethernet 1585865851 Thu 02 Apr 2020 06:17:31 PM EDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 6fbfa44b-461e-4067-b37a-26f63bc54f88 /org/freedesktop/NetworkManager/ActiveConnection/1 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CasperVersion: 1.394.3 DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH
[Touch-packages] [Bug 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled
@Jerome, could you help testing my backport of the patches you mentioned to v5.6 in https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1823076: $ sudo add-apt-repository ppa:vicamo/ppa-1823076 $ sudo apt install linux-image-unsigned-5.6.0-1010-oem=5.6.0-1010.10+lp1823076 \ linux-modules-5.6.0-1010-oem=5.6.0-1010.10+lp1823076 If that also works for you, we can begin SRU process to fix this issue in Ubuntu. -- 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/1823076 Title: System wakes up immediately after suspend if Bluetooth is still enabled Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+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 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1823076 -- 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/1823076 Title: System wakes up immediately after suspend if Bluetooth is still enabled Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+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 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]
** Tags added: hwe-touchpad -- 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/1825499 Title: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6] Status in systemd: Fix Released Status in libinput package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Status in libinput package in Fedora: Confirmed Bug description: After installing Kubuntu 19.04, I found that vertical sensitivity is much higher than horizontal sensitivity. Installing xserver-xorg-input-synaptics improved the situation a bit and enabled KDE touchpad setting that were disabled. It's very annoying. Laptop: HP Pavilion g6. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Fri Apr 19 12:00:02 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: D4Z91EA#ABV dmi.product.version: 088512005D160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1825499/+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 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started
https://www.reddit.com/r/AnnePro/comments/e76ij8/csr_40_bluetooth_dongle_on_linux/ It seems this dongle currently takes an additional patch to enable. Does it work for you? -- 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/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: In the GUI, I can go to the Bluetooth settings and it shows BT to be off. I turn on the little switch at the top but nothing else changes. If I navigate away from this page and then back, the switch is off again. If I try to reset the device on the command line I get: seb@eragon:~$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 14:39:55 2020 EcryptfsInUse: Yes InterestingModules: bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash vt.handoff=1 pti=off SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+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 1871182] Re: [RTL810xE] No ethernet connection
** No longer affects: 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/1871182 Title: [RTL810xE] No ethernet connection Status in linux package in Ubuntu: Fix Released Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871182/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
Resubmit to apport as https://code.launchpad.net/~vicamo/ubuntu/+source/apport/+git/apport/+merge/382559 instead per comment #11. ** Merge proposal linked: https://code.launchpad.net/~vicamo/ubuntu/+source/apport/+git/apport/+merge/382559 ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Eoan) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Focal) Status: In Progress => Invalid ** Changed in: apport (Ubuntu Focal) Status: New => In Progress ** Changed in: apport (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: In Progress Status in linux-firmware source package in Focal: Invalid Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started
** Tags added: hwe-bluetooth -- 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/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: In the GUI, I can go to the Bluetooth settings and it shows BT to be off. I turn on the little switch at the top but nothing else changes. If I navigate away from this page and then back, the switch is off again. If I try to reset the device on the command line I get: seb@eragon:~$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 14:39:55 2020 EcryptfsInUse: Yes InterestingModules: bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash vt.handoff=1 pti=off SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+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 1871182] Re: [RTL810xE] No ethernet connection
@Ryan, those error messages are irrelevant here. Could you try to: 1. remove 'realtek' from your /etc/modules temporarily 2. run `sudo update-initramfs -v -u` and attach the output messages 3. run `unmkinitramfs /boot/initrd.img-$(uname -r) some_temp_folder && find some_temp_folder -name realtek.ko` and check if realtek.ko is packed. 4. if it doesn't appear in the extracted folder, you may want to redo comment #4 to add it back after these experiments. The result from my side is positive, but maybe for some reason realtek.ko was not included automatically for you. -- 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/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
Resent as https://lists.ubuntu.com/archives/kernel- team/2020-April/108993.html -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in apport source package in Focal: New Status in linux-firmware source package in Focal: In Progress Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=b1eb2c4cd057624312e0412f6c4be000f7fc3617 These legacy tools has been marked deprecated since 2017. You should try migrating to bluetoothctl instead. ** No longer affects: linux (Ubuntu) -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'
Not a kernel 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1822587] Re: wifi service stops occasionally.
*** This bug is a duplicate of bug 1864505 ***
https://bugs.launchpad.net/bugs/1864505
** This bug has been marked a duplicate of bug 1864505
RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] wifi service stops
periodically
--
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/1822587
Title:
wifi service stops occasionally.
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
wifi service stops occasionally: ('?' in the top right icon). an old
bug that disappeared a few updates back, back now after yesterday's
update. 'service network-manager restart' gets it working again.
annoying as i thought it gone.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: network-manager 1.12.4-1ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 1 14:50:50 2019
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2016-07-30 (975 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IpRoute:
default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600
169.254.0.0/16 dev wlp3s0f0 scope link metric 1000
192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.100 metric
600
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=false
ProcEnviron:
LANGUAGE=en_ZA:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_ZA.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to cosmic on 2018-12-06 (116 days ago)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
CONNECTIONCON-UUID CON-PATH
wlp3s0f0 wifi connected
/org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD
01a82e09-44b7-4509-af07-4bf05f76759a
/org/freedesktop/NetworkManager/ActiveConnection/1
1C:AF:05:F7:CE:56 btdisconnected
/org/freedesktop/NetworkManager/Devices/4 ----
--
enp2s0f1 ethernet unavailable
/org/freedesktop/NetworkManager/Devices/2 ----
--
lo loopback unmanaged
/org/freedesktop/NetworkManager/Devices/1 ----
--
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1822587/+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 1861645] Re: PC fails to shutdown.
@Prakash, for syslog file, it's under /var/log/syslog. -- 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/1861645 Title: PC fails to shutdown. Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: I have a pc with Motherboard Gigabyte H370M D3H, Processor Intel Core I3 8100 3.6Ghz 6MbL3, RAM Corsair 16Mb 2400 Hz. I can reboot pc without any problem, but pc is stuck on ubuntu logo when I shutdown. while shutdown keyboard and mouse are turned off but pc remains on. I have to turn the mains power off to shutdown the pc. I think this is a major bug in Ubuntu 19.10. I searched for a solution on the internet but could not find any that works. Kindly help to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prakash1438 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-31 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 003: ID 1a2c:0e24 China Resource Semico Co., Ltd USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H370M-D3H Package: systemd 242-7ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=a883551d-0fff-4cdb-bc6d-d442860a0ec0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 RfKill: Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: H370M D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnH370M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: H370M-D3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861645/+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 1860806] Re: Ubuntu 18.04 and 19.04 new ethernet problem
*** This bug is a duplicate of bug 1576953 *** https://bugs.launchpad.net/bugs/1576953 ** This bug has been marked a duplicate of bug 1576953 8086:153a e1000e driver failed with error -3 -- 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/1860806 Title: Ubuntu 18.04 and 19.04 new ethernet problem Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860806/+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 1861645] Re: PC fails to shutdown.
@ppshenoy, could you reboot with following kernel parameters and paste the screenshot (probably by camera) when it stuck at shutting down and syslog file? 1. replace following line in your /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with: GRUB_CMDLINE_LINUX_DEFAULT="systemd.log_level=debug" 2. run `update-grub` to update grub config 3. reboot with aforementioned changes 4. shutdown and take a picture of messages printed in the console mode. 5. attach both the picture and syslog -- 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/1861645 Title: PC fails to shutdown. Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: I have a pc with Motherboard Gigabyte H370M D3H, Processor Intel Core I3 8100 3.6Ghz 6MbL3, RAM Corsair 16Mb 2400 Hz. I can reboot pc without any problem, but pc is stuck on ubuntu logo when I shutdown. while shutdown keyboard and mouse are turned off but pc remains on. I have to turn the mains power off to shutdown the pc. I think this is a major bug in Ubuntu 19.10. I searched for a solution on the internet but could not find any that works. Kindly help to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prakash1438 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-31 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 003: ID 1a2c:0e24 China Resource Semico Co., Ltd USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H370M-D3H Package: systemd 242-7ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=a883551d-0fff-4cdb-bc6d-d442860a0ec0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 RfKill: Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: H370M D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnH370M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: H370M-D3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861645/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones
@Francis, anything I can help here? -- 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/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: In Progress Status in apport source package in Disco: In Progress Status in apport source package in Eoan: In Progress Status in apport source package in Focal: Fix Released Bug description: [SRU Justification] [Impact] When `apport-bug linux` was executed on systems with linux-oem, linux-oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. [Fix] Fix already merged in Focal: https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2724 . SRU merge proposals in: * https://code.launchpad.net/~vicamo/ubuntu/bionic/apport/bug-1847967/+merge/376380 * https://code.launchpad.net/~vicamo/ubuntu/disco/apport/bug-1847967/+merge/376381 * https://code.launchpad.net/~vicamo/ubuntu/eoan/apport/bug-1847967/+merge/374263 [Test Case] 1. Boot with linux-oem or linux-oem-osp1 kernel and try to collect apport logs with: $ apport-cli --save saved.apport linux-oem-osp1 2. Make sure the report contains PCI/ALSA/DMI/Sysfs info. [Regression Potential] Low. original bug description When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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
Re: [Touch-packages] [Bug 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled
Please power off your laptop completely and power it on again after 1 minute. Paste dmesg log since boot and your linux-firmware version, then we may know which file to fix. smartman <1823...@bugs.launchpad.net> 於 2019年12月27日 週五 00:55 寫道： > I am having this issue also. Turning off bluetooth with bluez (Bluetooth > Manager) applet icon and manually stopping bluetooth service the suspend > works. Otherwise I have seen suspends but usually just wakes up in a few > seconds. Lenovo P53 with Ubuntu 19.10 and kernel 5.3.0-24-generic > > -- > You received this bug notification because you are subscribed to linux > in Ubuntu. > https://bugs.launchpad.net/bugs/1823076 > > Title: > System wakes up immediately after suspend if Bluetooth is still > enabled > > Status in bluez package in Ubuntu: > Confirmed > Status in linux package in Ubuntu: > Confirmed > > Bug description: > After replacing my USB mouse with a BT mouse, I noticed my machine > would no longer suspend without immediately waking up. i.e. I suspend > and see the light go into the slow fade in and out for one cycle and > then goes solid and the display wakes up again. If I disable BT (via > blueman applet) suspend works fine. > > I've fixed this by shutting down the BT service before suspend, and > starting it back up on wake, as indicated here: > https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- > after-suspend > > Perhaps this script should be included in blueZ as suspend issues seem > very hard to debug and the immediate wake after suspend could be > caused many any number of things. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: bluez 5.48-0ubuntu3.1 [modified: > lib/systemd/system/bluetooth.service] > ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 > Uname: Linux 4.15.0-46-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.6 > Architecture: amd64 > CurrentDesktop: XFCE > Date: Wed Apr 3 13:16:14 2019 > InstallationDate: Installed on 2019-02-09 (53 days ago) > InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > InterestingModules: rfcomm bnep btusb bluetooth > MachineType: Intel(R) Client Systems NUC8i3BEH > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic > root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 > SourcePackage: bluez > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/15/2018 > dmi.bios.vendor: Intel Corp. > dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 > dmi.board.name: NUC8BEB > dmi.board.vendor: Intel Corporation > dmi.board.version: J72693-304 > dmi.chassis.type: 3 > dmi.chassis.vendor: Intel Corporation > dmi.chassis.version: 2.0 > dmi.modalias: > dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: > dmi.product.family: Intel NUC > dmi.product.name: NUC8i3BEH > dmi.product.version: J72753-303 > dmi.sys.vendor: Intel(R) Client Systems > hciconfig: >hci0:Type: Primary Bus: USB > BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 > UP RUNNING > RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 > TX bytes:12331 acl:74 sco:0 commands:204 errors:0 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+subscriptions > -- 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/1823076 Title: System wakes up immediately after suspend if Bluetooth is still enabled Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate:
[Touch-packages] [Bug 1847967] Re: oem kernel packages treated differently from generic kernel ones
** Description changed: + [SRU Justification] + + [Impact] + When `apport-bug linux` was executed on systems with linux-oem, linux-oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. + + [Fix] + Fix already merged in Focal: https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2724 . + + SRU merge proposals in: + * https://code.launchpad.net/~vicamo/ubuntu/bionic/apport/bug-1847967/+merge/376380 + * https://code.launchpad.net/~vicamo/ubuntu/disco/apport/bug-1847967/+merge/376381 + * https://code.launchpad.net/~vicamo/ubuntu/eoan/apport/bug-1847967/+merge/374263 + + [Test Case] + 1. Boot with linux-oem or linux-oem-osp1 kernel and try to collect apport logs with: + + $ apport-cli --save saved.apport linux-oem-osp1 + + 2. Make sure the report contains PCI/ALSA/DMI/Sysfs info. + + [Regression Potential] + Low. + + original bug description + When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. -- 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/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: Fix Committed Status in apport source package in Bionic: In Progress Status in apport source package in Disco: In Progress Status in apport source package in Eoan: In Progress Status in apport source package in Focal: Fix Committed Bug description: [SRU Justification] [Impact] When `apport-bug linux` was executed on systems with linux-oem, linux-oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. [Fix] Fix already merged in Focal: https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2724 . SRU merge proposals in: * https://code.launchpad.net/~vicamo/ubuntu/bionic/apport/bug-1847967/+merge/376380 * https://code.launchpad.net/~vicamo/ubuntu/disco/apport/bug-1847967/+merge/376381 * https://code.launchpad.net/~vicamo/ubuntu/eoan/apport/bug-1847967/+merge/374263 [Test Case] 1. Boot with linux-oem or linux-oem-osp1 kernel and try to collect apport logs with: $ apport-cli --save saved.apport linux-oem-osp1 2. Make sure the report contains PCI/ALSA/DMI/Sysfs info. [Regression Potential] Low. original bug description When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones
Created: * https://code.launchpad.net/~vicamo/ubuntu/bionic/apport/bug-1847967/+merge/376380 * https://code.launchpad.net/~vicamo/ubuntu/disco/apport/bug-1847967/+merge/376381 * https://code.launchpad.net/~vicamo/ubuntu/eoan/apport/bug-1847967/+merge/374263 ** Branch linked: lp:~vicamo/ubuntu/bionic/apport/bug-1847967 ** Branch linked: lp:~vicamo/ubuntu/disco/apport/bug-1847967 ** Changed in: apport (Ubuntu Bionic) Status: New => In Progress ** Changed in: apport (Ubuntu Disco) Status: New => In Progress ** Changed in: apport (Ubuntu Eoan) Status: New => In Progress -- 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/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: Fix Committed Status in apport source package in Bionic: In Progress Status in apport source package in Disco: In Progress Status in apport source package in Eoan: In Progress Status in apport source package in Focal: Fix Committed Bug description: When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones
** Changed in: apport (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: Fix Committed Status in apport source package in Bionic: New Status in apport source package in Disco: New Status in apport source package in Eoan: New Status in apport source package in Focal: Fix Committed Bug description: When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones
Yes, it was made before Focal was out, but definitely want it to be SRU- ed to all series with linux-oem/linux-oem-osp1 kernels. ** Also affects: apport (Ubuntu Focal) Importance: Undecided Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Also affects: apport (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Disco) Importance: Undecided Status: New -- 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/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: In Progress Status in apport source package in Bionic: New Status in apport source package in Disco: New Status in apport source package in Eoan: New Status in apport source package in Focal: In Progress Bug description: When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones
So before the merge proposal[1] is accepted, you can take following
steps to file a bug with all the information for kernel packages:
1. find out the source package name for the binary kernel package. It
should be "linux-signed-oem[-osp1]" for signed kernel packages, and
"linux-oem[-osp1]" for unsigned ones.
$ apt show ${pkg} | grep ^Source:
2. create symlinks for apport:
$ sudo ln -s source_linux.py /usr/share/apport/package-
hooks/source_${srcpkg}.py
3. appport-bug ${pkg}
--
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/1847967
Title:
oem kernel packages treated differently from generic kernel ones
Status in OEM Priority Project:
New
Status in apport package in Ubuntu:
In Progress
Bug description:
When `apport-bug linux` was executed on systems with linux-oem, linux-
oem-osp1 kernels, many details are not included as generic linux
kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones
Maybe the best solution is to install such links in every kernel related source packages built kernel image packages themselves. :X -- 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/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: In Progress Bug description: When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones
--- debian/apport.links 2018-05-09 23:42:20 + +++ debian/apport.links 2019-10-17 06:20:03 + @@ -1,4 +1,10 @@ +/usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-meta-oem-osp1.py +/usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-meta-oem.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-meta.py +/usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-oem-osp1.py +/usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-oem.py +/usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-signed-oem-osp1.py +/usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-signed-oem.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-signed.py /usr/bin/apport-bug /usr/bin/ubuntu-bug /usr/share/man/man1/apport-bug.1.gz /usr/share/man/man1/ubuntu-bug.1.gz ** Branch linked: lp:~vicamo/ubuntu/eoan/apport/bug-1847967 ** Changed in: apport (Ubuntu) Status: New => In Progress -- 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/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: In Progress Bug description: When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones
sudo ln -s source_linux.py /usr/share/apport/package-hooks/source_linux-oem.py sudo ln -s source_linux.py /usr/share/apport/package-hooks/source_linux-oem-osp1.py Above commands would fix this issue. Judging from all other source_linux* symlinks are created by apport package itself (via %srcpkg/debian/apport.links), I suggest we add two more links for oem /oem-osp1 kernels, too. -- 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/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: New Bug description: When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones
** Description changed: - (To be filled with details) + When `apport-bug linux` was executed on systems with linux-oem, linux- + oem-osp1 kernels, many details are not included as generic linux kernel + does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. -- 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/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: New Bug description: When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones
** Summary changed: - oem kernel packages treat differently from generic kernel ones + oem kernel packages treated differently from generic kernel ones -- 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/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: New Bug description: (To be filled with details) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1847967] [NEW] oem kernel packages treat differently from generic kernel ones
Public bug reported: (To be filled with details) ** Affects: oem-priority Importance: Undecided Status: New ** Affects: apport (Ubuntu) Importance: Undecided Assignee: You-Sheng Yang (vicamo) Status: New ** Tags: oem-priority -- 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/1847967 Title: oem kernel packages treat differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: New Bug description: (To be filled with details) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez
** Tags added: ubuntu-certified -- 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/1759836 Title: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in bluez source package in Bionic: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Invalid Status in bluez source package in Disco: Fix Released Status in linux source package in Disco: Invalid Status in systemd source package in Disco: Invalid Status in bluez source package in Eoan: Fix Released Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Invalid Status in bluez package in Debian: New Bug description: [impact] on specific Dell systems, with a specific usb bluetooth device built- in, the udev rule 'hid2hci' provided by the 'bluez' package causes an endless loop of uevents resulting from 'bind' or 'unbind' kernel uevents. These new events were added to the kernel after the 'hid2hci' udev rule was written. [test case] the specific Dell system is required to be able to reproduce this, or at least the specific usb bluetooth hardware included in that system. Reproducing this is reportedly easy, for example comment 75 indicates it happens on every boot. When this happens, any process monitor (e.g. ps, top, etc) will show the 'udevd' process using 100% of a cpu, and 'udevadm monitor' should show repeated 'bind' and 'unbind' events as mentioned in comment 39. [regression potential] as this alters what kernel uevents the 'hid2hci' udev rule processes, regressions would involve the affected usb bluetooth device failing to be set up, or otherwise not processing the uevents correctly. [other info] this is not fixed yet upstream, as of my last check, but has been submitted upstream as mentioned in comment 95. original description: -- The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works okay but the internal mic doesn't work. When I plug in headset, the mic on headset also doens't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilian 1689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 12:27:10 2019 InstallationDate: Installed on 2019-09-21 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.vendor: TIMI dmi.bios.version: RMRCM400P0100 dmi.board.name: TM1901 dmi.board.vendor: TIMI dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.modalias: dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 14 dmi.product.sku: TM1901-24822 dmi.sys.vendor: TIMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules
That patch has also been obsoleted in Debian recently, and upstream
systemd has no longer support 70-persistent-net.rules thing. Any reason
you cannot move to new naming scheme?
--
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/1842651
Title:
Regression: after Uprade from udev_237-3ubuntu10.25 to
udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
-persistent-network.rules
Status in OEM Priority Project:
New
Status in systemd package in Ubuntu:
New
Bug description:
Since the latest update from udev_237-3ubuntu10.25 and
systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
systemd_237-3ubuntu10.26 the renaming of network interfaces by
/etc/udev/rules/70-persistent-network.rules does not work.
/etc/udev/rules/70-persistent-network.rules:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
/var/log/syslog:
systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File
exists
When I downgrade the packages to the version with 237-3ubuntu10.25 the
following messages are in /var/log/syslog:
Sep 4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2:
renamed from eth0
Sep 4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed
from eth1
The latest version does not rename the interfaces temporary if there
is a conflict!
Manually installing the old packages with
dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
did fix the problem temporary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+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 1837700] Re: Dell system takes a long time to connect network with external dock
** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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/1837700 Title: Dell system takes a long time to connect network with external dock Status in HWE Next: New Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: Fix Committed Bug description: Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. [1]: https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c [3]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules [4]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch [5]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch?h=ubuntu-bionic To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1837700/+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 1837700] Re: Dell system takes a long time to connect network with external dock
** Merge proposal linked: https://code.launchpad.net/~vicamo/ubuntu/+source/systemd/+git/systemd/+merge/370592 ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/1837700 Title: Dell system takes a long time to connect network with external dock Status in HWE Next: New Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: In Progress Bug description: Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. [1]: https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c [3]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules [4]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch [5]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch?h=ubuntu-bionic To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1837700/+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 1837700] Re: Dell system takes a long time to connect network with external dock
Above MR to Debian closed because that's already in experimental branch[1] for v242. [1]: https://salsa.debian.org/systemd- team/systemd/commit/3d45a7af959cf260bffcb1ad0262973b5750ae36 -- 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/1837700 Title: Dell system takes a long time to connect network with external dock Status in HWE Next: New Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Bug description: Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. [1]: https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c [3]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules [4]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch [5]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch?h=ubuntu-bionic To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1837700/+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 1837700] Re: Dell system takes a long time to connect network with external dock
Merge request to Debian Systemd package: https://salsa.debian.org /systemd-team/systemd/merge_requests/42 ** Tags added: oem-priority originate-from-1835860 somerville -- 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/1837700 Title: Dell system takes a long time to connect network with external dock Status in HWE Next: New Status in systemd package in Ubuntu: New Bug description: Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. [1]: https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c [3]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules [4]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch [5]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch?h=ubuntu-bionic To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1837700/+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 1837700] Re: Dell system takes a long time to connect network with external dock
** Description changed: - TBD + Dell has a feature called MAC addrss passthrough[1] that would force usb + ethernet adapters to be assigned with a predefined MAC address stored in + BIOS or so. This feature has been landed to mainline kernel in driver + r8152[2]. So whenever a r8152 managed device is plugged into Dell + devices with MAC addrss passthrough enabled, this driver will set NIC + MAC to a predefined one. + + And some Dell devices have already one built-in r8152 NIC port. On these + devices, when a second r8152 NIC is plugged in, a Debian originated udev + rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command + `net_id` to give a persistent name, and that will be based on MAC + address. However, since the system has already initialized the built-in + r8152 NIC with that name, renaming the second interface with this name + will always fail. + + While Debian still carries a patch called "Revert-udev-network-device- + renaming-immediately-give.patch"[4] that tries to keep support of + already deprecated "75-persistent-net-generator.rules" based interface + renaming mechanism, this patch also propagated into Ubuntu[5]. This + patch will retry renaming with a 90 seconds timeout when the error code + is -EEXIST, so the uevent processing will always be blocked in the last + ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. + + [1]: https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en + [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c + [3]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules + [4]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch + [5]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch?h=ubuntu-bionic -- 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/1837700 Title: Dell system takes a long time to connect network with external dock Status in systemd package in Ubuntu: New Bug description: Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that
[Touch-packages] [Bug 1837700] [NEW] Dell system takes a long time to connect network with external dock
Public bug reported: TBD ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1837700 Title: Dell system takes a long time to connect network with external dock Status in systemd package in Ubuntu: New Bug description: TBD ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700/+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
