[Bug 1879876] Re: Screen should not rotate automatically on a laptop
** Bug watch added: gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues #306 https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/306 ** Also affects: iio-sensor-proxy via https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/306 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879876 Title: Screen should not rotate automatically on a laptop To manage notifications about this bug go to: https://bugs.launchpad.net/iio-sensor-proxy/+bug/1879876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879876] Re: Screen should not rotate automatically on a laptop
The legitimate chassis type to enable the rotation feature should be: Tablet (0x1E) Convertible (0x1F) Detachable (0x20) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879876 Title: Screen should not rotate automatically on a laptop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1879876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879876] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1879876/+attachment/5375007/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879876 Title: Screen should not rotate automatically on a laptop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1879876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879876] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1879876/+attachment/5375008/+files/ProcEnviron.txt ** Tags added: originate-from-1871572 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879876 Title: Screen should not rotate automatically on a laptop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1879876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879876] Re: Screen should not rotate automatically on a laptop
apport information ** Tags added: apport-collected focal ** Description changed: There are recently more machines shipped with an accelerometer to bring about the automatic rotation feature on pad-like or 2in1 products. However, manufacturers sometimes share designs between platforms; a laptop may mount an accelerometer on its panel. The user experience on laptops with a fixed keyboard/touchpad that rotates automatically is somehow annoying, and the touchpad motion is confusing. - The SMBIOS specification defines chassis type in section 7.4.1. - Softwares can determine to rotate automatically or not by checking this - value, or at least not to rotate on a laptop(0x09) and notebook(0x0A). + The SMBIOS specification defines chassis type in section 7.4.1. Softwares can determine to rotate automatically or not by checking this value, or at least not to rotate on a laptop(0x09) and notebook(0x0A). + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-05-05 (15 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) + Package: gdm3 3.34.1-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 + Tags: focal + Uname: Linux 5.6.0-1010-oem x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1879876/+attachment/5375006/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879876 Title: Screen should not rotate automatically on a laptop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1879876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879876] Re: Screen should not rotate automatically on a laptop
** Also affects: gdm Importance: Undecided Status: New ** No longer affects: gdm ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Che Cheng (cktenn) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879876 Title: Screen should not rotate automatically on a laptop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1879876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879876] [NEW] Screen should not rotate automatically on a laptop
Public bug reported: There are recently more machines shipped with an accelerometer to bring about the automatic rotation feature on pad-like or 2in1 products. However, manufacturers sometimes share designs between platforms; a laptop may mount an accelerometer on its panel. The user experience on laptops with a fixed keyboard/touchpad that rotates automatically is somehow annoying, and the touchpad motion is confusing. The SMBIOS specification defines chassis type in section 7.4.1. Softwares can determine to rotate automatically or not by checking this value, or at least not to rotate on a laptop(0x09) and notebook(0x0A). ** Affects: oem-priority Importance: Undecided Assignee: Che Cheng (cktenn) Status: New ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879876 Title: Screen should not rotate automatically on a laptop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1879876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866156] Re: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected.
** Tags added: originate-from-1805928 ** Changed in: oem-priority Status: New => Triaged ** Changed in: oem-priority Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866156] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1866156/+attachment/5333712/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866156] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1866156/+attachment/5333713/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866156] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1866156/+attachment/5333711/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866156] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1866156/+attachment/5333708/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866156] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1866156/+attachment/5333709/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866156] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1866156/+attachment/5333701/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866156] Re: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected.
apport information ** Tags added: apport-collected bionic ** Description changed: Dell laptops have an option for power management in the BIOS setting to control WLAN radio. If enabled, it will sense the connection of the system to a wired network and subsequently disable the selected wireless radios (WLAN and/or WWAN). Upon disconnection from the wired network, the selected wireless radios will be re-enabled. - When Dell docking station (the ethernet is Realtek r8153 USB - controller), with runtime PM enabled, is the wired network, WLAN radio - won't be re-enabled after unplugging ethernet cable. By checking rfkill, - the radio is hard blocked. Disable runtime PM of the r8153 USB device - can work around this issue. + When Dell docking station (the ethernet is Realtek r8153 USB controller), with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. Disable runtime PM of the r8153 USB device can work around this issue. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: u 2160 F pulseaudio + 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-20190418-59+beaver-osp1-highsparrow+X32 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-01-10 (54 days ago) + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 + MachineType: Dell Inc. Latitude 9510 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-1040-oem-osp1 N/A + linux-backports-modules-5.0.0-1040-oem-osp1 N/A + linux-firmware 1.173.14 + Tags: bionic + Uname: Linux 5.0.0-1040-oem-osp1 x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/24/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 0.2.6 + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 31 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr: + dmi.product.family: Latitude + dmi.product.name: Latitude 9510 + dmi.product.sku: 0983 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1866156/+attachment/5333700/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866156] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1866156/+attachment/5333705/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866156] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1866156/+attachment/5333703/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866156] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1866156/+attachment/5333707/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866156] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1866156/+attachment/5333710/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866156] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1866156/+attachment/5333706/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866156] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1866156/+attachment/5333704/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866156] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1866156/+attachment/5333702/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866156] [NEW] Wireless LAN RF is hardware blocked forever after r8153 ethernet connected.
Public bug reported: Dell laptops have an option for power management in the BIOS setting to control WLAN radio. If enabled, it will sense the connection of the system to a wired network and subsequently disable the selected wireless radios (WLAN and/or WWAN). Upon disconnection from the wired network, the selected wireless radios will be re-enabled. When Dell docking station (the ethernet is Realtek r8153 USB controller), with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. Disable runtime PM of the r8153 USB device can work around this issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 2160 F pulseaudio 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-20190418-59+beaver-osp1-highsparrow+X32 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-10 (54 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Latitude 9510 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-1040-oem-osp1 N/A linux-backports-modules-5.0.0-1040-oem-osp1 N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 5.0.0-1040-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.2.6 dmi.board.vendor: Dell Inc. dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 9510 dmi.product.sku: 0983 dmi.sys.vendor: Dell Inc. ** Affects: oem-priority Importance: Undecided Assignee: Che Cheng (cktenn) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bionic ihv-realtek ** Attachment added: "Ubuntu 18.04 + Docking + WLAN Radio Issue.mp4" https://bugs.launchpad.net/bugs/1866156/+attachment/5333692/+files/Ubuntu%2018.04%20+%20Docking%20+%20WLAN%20Radio%20Issue.mp4 ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Che Cheng (cktenn) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863724] Re: Add missing pci-id's for Comet Lake (CML)
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863724 Title: Add missing pci-id's for Comet Lake (CML) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1863724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857409] Re: alsa/sof: load different firmware on different platforms
** Also affects: linux Importance: Undecided Status: New ** Project changed: linux => oem-priority ** Changed in: oem-priority Assignee: (unassigned) => Che Cheng (cktenn) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857409 Title: alsa/sof: load different firmware on different platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859387] Re: intel/sof: update the intel sof firmware to v1.3-0f73628 for cml and cnl
** Changed in: oem-priority Assignee: (unassigned) => Che Cheng (cktenn) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859387 Title: intel/sof: update the intel sof firmware to v1.3-0f73628 for cml and cnl To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1859387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855420] Re: dmicheck Type 41 result doesn't reflect real condition
>From the lscpi out, the ethernet is on PCi 02:00.0. It is not in DMI type 41 table. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/1855420/+attachment/5313971/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855420 Title: dmicheck Type 41 result doesn't reflect real condition To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1855420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855420] Re: dmicheck Type 41 result doesn't reflect real condition
** Description changed: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ There are packages like systemd relies on SMBIOS type 41 information to determine the onboard network interface renaming mechanism. However, manufacturers don't always offer the correct information, so the expected ifname enoX becomes enpXsX. In the case -- # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 3.1 present. Handle 0x2900, DMI type 41, 11 bytes Onboard Device Reference Designation: To Be Filled by O.E.M. Type: Video Status: Enabled Type Instance: 0 Bus Address: :00:02.0 Handle 0x2901, DMI type 41, 11 bytes Onboard Device Reference Designation: To Be Filled by O.E.M. Type: Ethernet Status: Disabled Type Instance: 0 Bus Address: :00:1f.6 Handle 0x2902, DMI type 41, 11 bytes Onboard Device Reference Designation: To Be Filled by O.E.M. Type: Sound Status: Disabled Type Instance: 0 Bus Address: :00:1f.3 Handle 0x2903, DMI type 41, 11 bytes Onboard Device Reference Designation: To Be Filled by O.E.M. Type: SATA Controller Status: Disabled Type Instance: 0 Bus Address: :00:17.0 --- - According to the SMBIOS specification section 7.42.3, "Type Instance" should be started with 1, and all devices mentioned are enabled, but the test result of fwts dmicheck type 41 item still passed. + According to the SMBIOS specification section 7.42.3, "Type Instance" should be unique, and all devices mentioned are enabled, but the test result of fwts dmicheck type 41 item still passed. Description: Ubuntu 18.04.2 LTS Release: 18.04 fwts: 18.03.00-0ubuntu5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 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-20190418-59+beaver-osp1-loras+X22 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-05 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: fwts 18.03.00-0ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-1028.32-oem-osp1 5.0.21 Tags: bionic Uname: Linux 5.0.0-1028-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855420 Title: dmicheck Type 41 result doesn't reflect real condition To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1855420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855420] Re: dmicheck Type 41 result doesn't reflect real condition
** Description changed: There are packages like systemd relies on SMBIOS type 41 information to determine the onboard network interface renaming mechanism. However, - manufacturers don't always offer the correct information. + manufacturers don't always offer the correct information, so the + expected ifname enoX becomes enpXsX. In the case -- # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 3.1 present. Handle 0x2900, DMI type 41, 11 bytes Onboard Device - Reference Designation: To Be Filled by O.E.M. - Type: Video - Status: Enabled - Type Instance: 0 - Bus Address: :00:02.0 + Reference Designation: To Be Filled by O.E.M. + Type: Video + Status: Enabled + Type Instance: 0 + Bus Address: :00:02.0 Handle 0x2901, DMI type 41, 11 bytes Onboard Device - Reference Designation: To Be Filled by O.E.M. - Type: Ethernet - Status: Disabled - Type Instance: 0 - Bus Address: :00:1f.6 + Reference Designation: To Be Filled by O.E.M. + Type: Ethernet + Status: Disabled + Type Instance: 0 + Bus Address: :00:1f.6 Handle 0x2902, DMI type 41, 11 bytes Onboard Device - Reference Designation: To Be Filled by O.E.M. - Type: Sound - Status: Disabled - Type Instance: 0 - Bus Address: :00:1f.3 + Reference Designation: To Be Filled by O.E.M. + Type: Sound + Status: Disabled + Type Instance: 0 + Bus Address: :00:1f.3 Handle 0x2903, DMI type 41, 11 bytes Onboard Device - Reference Designation: To Be Filled by O.E.M. - Type: SATA Controller - Status: Disabled - Type Instance: 0 - Bus Address: :00:17.0 + Reference Designation: To Be Filled by O.E.M. + Type: SATA Controller + Status: Disabled + Type Instance: 0 + Bus Address: :00:17.0 --- According to the SMBIOS specification section 7.42.3, "Type Instance" should be started with 1, and all devices mentioned are enabled, but the test result of fwts dmicheck type 41 item still passed. Description: Ubuntu 18.04.2 LTS Release: 18.04 fwts: 18.03.00-0ubuntu5 - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 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-20190418-59+beaver-osp1-loras+X22 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X22 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-05 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: fwts 18.03.00-0ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-1028.32-oem-osp1 5.0.21 Tags: bionic Uname: Linux 5.0.0-1028-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855420 Title: dmicheck Type 41 result doesn't reflect real condition To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1855420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855420] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1855420/+attachment/5310196/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855420 Title: dmicheck Type 41 result doesn't reflect real condition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/1855420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855420] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1855420/+attachment/5310195/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855420 Title: dmicheck Type 41 result doesn't reflect real condition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/1855420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855420] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1855420/+attachment/5310197/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855420 Title: dmicheck Type 41 result doesn't reflect real condition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/1855420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855420] [NEW] dmicheck Type 41 result doesn't reflect real condition
Public bug reported: There are packages like systemd relies on SMBIOS type 41 information to determine the onboard network interface renaming mechanism. However, manufacturers don't always offer the correct information. In the case -- # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 3.1 present. Handle 0x2900, DMI type 41, 11 bytes Onboard Device Reference Designation: To Be Filled by O.E.M. Type: Video Status: Enabled Type Instance: 0 Bus Address: :00:02.0 Handle 0x2901, DMI type 41, 11 bytes Onboard Device Reference Designation: To Be Filled by O.E.M. Type: Ethernet Status: Disabled Type Instance: 0 Bus Address: :00:1f.6 Handle 0x2902, DMI type 41, 11 bytes Onboard Device Reference Designation: To Be Filled by O.E.M. Type: Sound Status: Disabled Type Instance: 0 Bus Address: :00:1f.3 Handle 0x2903, DMI type 41, 11 bytes Onboard Device Reference Designation: To Be Filled by O.E.M. Type: SATA Controller Status: Disabled Type Instance: 0 Bus Address: :00:17.0 --- According to the SMBIOS specification section 7.42.3, "Type Instance" should be started with 1, and all devices mentioned are enabled, but the test result of fwts dmicheck type 41 item still passed. Description:Ubuntu 18.04.2 LTS Release:18.04 fwts: 18.03.00-0ubuntu5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 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-20190418-59+beaver-osp1-loras+X22 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-05 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: fwts 18.03.00-0ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-1028.32-oem-osp1 5.0.21 Tags: bionic Uname: Linux 5.0.0-1028-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True ** Affects: fwts (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bionic ** Attachment added: "results.log" https://bugs.launchpad.net/bugs/1855420/+attachment/5310194/+files/results.log ** Tags added: apport-collected bionic ** Description changed: There are packages like systemd relies on SMBIOS type 41 information to determine the onboard network interface renaming mechanism. However, manufacturers don't always offer the correct information. In the case -- # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 3.1 present. Handle 0x2900, DMI type 41, 11 bytes Onboard Device Reference Designation: To Be Filled by O.E.M. Type: Video Status: Enabled Type Instance: 0 Bus Address: :00:02.0 Handle 0x2901, DMI type 41, 11 bytes Onboard Device Reference Designation: To Be Filled by O.E.M. Type: Ethernet Status: Disabled Type Instance: 0 Bus Address: :00:1f.6 Handle 0x2902, DMI type 41, 11 bytes Onboard Device Reference Designation: To Be Filled by O.E.M. Type: Sound Status: Disabled Type Instance: 0 Bus Address: :00:1f.3 Handle 0x2903, DMI type 41, 11 bytes Onboard Device Reference Designation: To Be Filled by O.E.M. Type: SATA Controller Status: Disabled Type Instance: 0 Bus Address: :00:17.0 --- According to the SMBIOS specification section 7.42.3, "Type Instance" should be started with 1, and all devices mentioned are enabled, but the test result of fwts dmicheck type 41 item still passed. Description: Ubuntu 18.04.2 LTS Release: 18.04 fwts: 18.03.00-0ubuntu5 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + 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-20190418-59+beaver-osp1-loras+X22 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-12-05 (1 days ago) + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 + Package: fwts 18.03.00-0ubuntu5 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.0.0-1028.32-oem-osp1 5.0.21 + Tags: bionic + Uname: Linux 5.0.0-1028-oem-osp1 x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True -- You
[Bug 1843381] Re: Dell system takes a long time to connect network with external dock
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843381 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843381] Re: Dell system takes a long time to connect network with external dock
I can confirm that systemd 237-3ubuntu10.33 fixes this issue for me on bionic. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843381 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843381] Re: Dell system takes a long time to connect network with external dock
I can confirm that systemd 237-3ubuntu10.32 fixes this issue for me on disco. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843381 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843381] Re: Dell system takes a long time to connect network with external dock
I can confirm that systemd 240-6ubuntu5.8 fixes this issue for me on disco. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843381 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851216] [NEW] System hangs at early boot
Public bug reported: After upgrading kernel to linux-image-4.15.0-1061 (proposed), system hangs at very beginning of booting. Only grub message "loading..." is printed. Remove "splash quiet" from grub kernel command line and this time no message is printed on console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1060-oem 4.15.0-1060.69 ProcVersionSignature: Ubuntu 4.15.0-1060.69-oem 4.15.18 Uname: Linux 4.15.0-1060-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: u 1977 F...m pulseaudio /dev/snd/pcmC1D0p: u 1977 F...m pulseaudio /dev/snd/controlC0: u 1977 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 4 17:15:56 2019 InstallationDate: Installed on 2019-11-04 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Precision 5530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1060-oem root=UUID=baa02b0a-d18f-41d2-9e2b-2d057742013c ro mem_sleep_default=deep nvidia-drm.modeset=1 quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-1060-oem N/A linux-backports-modules-4.15.0-1060-oem N/A linux-firmware 1.173.9 SourcePackage: linux-oem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0184M4 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd06/27/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0184M4:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.sys.vendor: Dell Inc. ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851216 Title: System hangs at early boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1851216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844650] Re: No authentication window pops up if thunderbolt device be plugged before booting
@Rex The link is on also-affect project list. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1794 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844650 Title: No authentication window pops up if thunderbolt device be plugged before booting To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1844650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843381] Re: Dell system takes a long time to connect network with external dock
@ddstreet Tested on bionic/disco/eoan. All of them do not rename the second usbnet with MAC passthrough function, it keeps ifname eth0. Thank you so much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843381 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844650] Re: No authentication window pops up if thunderbolt device be plugged before booting
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1794 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1794 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1794 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844650 Title: No authentication window pops up if thunderbolt device be plugged before booting To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1844650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843381] Re: Dell system takes a long time to connect network with external dock
Yes, since it will be the same result as udev failed to rename it, it doesn't matter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843381 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844650] Re: No authentication window pops up if thunderbolt device be plugged before booting
I'll submit an issue to gnome-shell project. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844650 Title: No authentication window pops up if thunderbolt device be plugged before booting To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1844650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844650] Re: No authentication window pops up if thunderbolt device be plugged before booting
Gnome shell will show a notification on the login/unlock screen instructing users to disconnect and reconnect an unauthenticated device when 1. User logged out 2. Screen is locked But the notification won't show if no one has been logging in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844650 Title: No authentication window pops up if thunderbolt device be plugged before booting To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1844650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843381] Re: Dell system takes a long time to connect network with external dock
I would like to explain the original intention of the design in the udev rule. Since it is not possible letting two NICs to have the same ifname, I tend to find a way to assign a persistent name that would not duplicate on a system for each usbnet. It is meant to break the current rule, so I was trying to reduce the number of potential victims. I found that people using NetworkManager, which identifies connections by UUID, won't be affected. Restrict the system vendor also helps to mitigate the impact. I admit unsetting the duplicated ifname does solve the original issue without regression in a real case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843381 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839016] Re: Suspend is iterrupted by ALT key
** Also affects: oem-priority/bionic Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839016 Title: Suspend is iterrupted by ALT key To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1839016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839016] Re: Suspend is iterrupted by ALT key
The issue cannot be reproduced on 19.10 daily (2019-10-14). GNOME Shell 3.34.1 When trying to reproduce the issue by pressing a key repeatedly after pressing the suspend button, the locked screen will show for a short period of time (less than 2 seconds), then the system keeps going to sleep. I think gnome-shell 3.34.1 do fix this, need to find out how to fix in bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839016 Title: Suspend is iterrupted by ALT key To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1839016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843381] Re: Dell system takes a long time to connect network with external dock
@ddstreet Based on https://salsa.debian.org/systemd- team/systemd/merge_requests/56#note_113429, is https://salsa.debian.org /systemd-team/systemd/merge_requests/55 suitable for the SRU workaround? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843381 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843381] Re: Dell system takes a long time to connect network with external dock
@Dan I've submitted a merge request to Debian that only applies to Dell system the idea mentioned in comment #4, it modifies the rule 73 -special-net-names.rules. https://salsa.debian.org/systemd-team/systemd/merge_requests/55 Please help to review this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843381 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843381] Re: Dell system takes a long time to connect network with external dock
There is 73-special-net-names.rules which 73-usb-net-by-mac.rules was
split from, and it'll execute prior to 73-usb-net-by-mac.rules.
We can keep the fixed internal MAC passthrough interface using MAC
address as interface name, and let removable dongles using pathname by
adding following line to 73-special-net-names.rules.
ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb", NAME=="",
ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="8153",
ATTRS{removable}=="removable", IMPORT{builtin}="net_id",
NAME="$env{ID_NET_NAME_PATH}"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843381
Title:
Dell system takes a long time to connect network with external dock
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843381] Re: Dell system takes a long time to connect network with external dock
I would like to propose to write a rule to rename a removable Realtek 8153 interface with ID_NET_NAME_PATH instead of ID_NET_NAME_MAC. The solution may impact users using Realtek 8153 and manipulate it by the interface name since the name is not consistent and will change when switching USB port. Networkmanager is not affected since it identifies interfaces via UUID. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843381 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844102] Re: Can't enable WLAN on Dell platform when enabling control WLAN radio then unplug LAN
** Tags added: originate-from-1805928 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844102 Title: Can't enable WLAN on Dell platform when enabling control WLAN radio then unplug LAN To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1844102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844102] Re: Can't enable WLAN on Dell platform when enabling control WLAN radio then unplug LAN
** Also affects: linux Importance: Undecided Status: New ** Project changed: linux => oem-priority ** Changed in: oem-priority Assignee: (unassigned) => Che Cheng (cktenn) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844102 Title: Can't enable WLAN on Dell platform when enabling control WLAN radio then unplug LAN To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1844102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844102] [NEW] Can't enable WLAN on Dell platform when enabling control WLAN radio then unplug LAN
Public bug reported: There is a BIOS option to control WLAN radio on Dell laptop. When plugging LAN cable, the WLAN radio is blocked, unplugging LAN cable and the WLAN radio should be unblocked. Dell also has docking stations like WD19 series that equipped with USB LAN. The LAN chip on WD19 series is Realtek 8153 gigabit ethernet. The issue is when turning on WLAN radio control and plugging the docking station with LAN connection, the wireless network will be turned off. While disconnecting LAN, the wireless network remains off. The Realtek 8153 runtime power management is set to auto by TLP package. If the power management is set to on, then this issue can't be reproduced. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1148 F pulseaudio Date: Mon Sep 16 16:24:15 2019 InstallationDate: Installed on 2019-09-12 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190912) MachineType: Dell Inc. XPS 13 9380 ProcEnviron: LANGUAGE=zh_TW:zh TERM=xterm-256color PATH=(custom, no user) LANG=zh_TW.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=UUID=1a9b9bc1-0d98-4e39-9fd1-a1bad1681880 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0SSY11 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/20/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0SSY11:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. ** Affects: linux Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844102 Title: Can't enable WLAN on Dell platform when enabling control WLAN radio then unplug LAN To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1844102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843381] Re: Dell system takes a long time to connect network with external dock
** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Che Cheng (cktenn) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843381 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843381] [NEW] Dell system takes a long time to connect network with external dock
Public bug reported: This is a bug reopen from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700 The original one caused systemd regressed. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651 This issue needs an alternative solution. 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 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd Importance: Undecided Status: New ** Project changed: systemd => oem-priority -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843381 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837700] Re: Dell system takes a long time to connect network with external dock
** Changed in: oem-priority Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837700 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1837700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837700] Re: Dell system takes a long time to connect network with external dock
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837700 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1837700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837700] Re: Dell system takes a long time to connect network with external dock
I can confirm that systemd 240-6ubuntu5.4 fixes this issue for me on disco. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837700 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1837700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837700] Re: Dell system takes a long time to connect network with external dock
I can confirm that systemd 237-3ubuntu10.26 fixes this issue for me on bionic. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837700 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1837700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839016] Re: Suspend is iterrupted by ALT key
** Also affects: gnome-shell Importance: Undecided Status: New ** Project changed: gnome-shell => oem-priority ** Changed in: oem-priority Importance: Undecided => Medium ** Changed in: oem-priority Importance: Medium => High ** Changed in: oem-priority Assignee: (unassigned) => Che Cheng (cktenn) ** Description changed: When trying to suspend the system via pressing the power button in the system tray with ALT key pressed, it is possible to interrupt the system to enter sleep mode and fall back to screen lock. While trying to unlock the screen, the system goes to sleep immediately. Gnome-shell is able to suspend the system by drop-down menu in the system tray. By pressing ALT key or long-press the power button until it switches to suspend icon. The system will suspend if it is by the long- press power button, while with ALT key pressed, there is a failure rate that causes the suspend process to be interrupted. The second issue is that if the suspend process is interrupted, the locked screen is shown. While trying to unlock the screen by inputting password, the system will go sleeping after that. STEPS TO REPRODUCE: 1. To suspend system via pressing the power button in the drop-down system tray with ALT key pressed. 2. During system is going to sleep, e.g., screen going dark, emulate a key bounce by pressing ALT key again. RESULTS: - The system going to sleep without a problem. + The locked screen shows up and goes to sleep after tens of seconds. While trying to unlock screen, system enter suspend after unlocking successfully. EXPECTED RESULTS: - The locked screen shows up and goes to sleep after tens of seconds. While trying to unlock screen, system enter suspend after unlocking successfully. + The system going to sleep without a problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839016 Title: Suspend is iterrupted by ALT key To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1839016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839016] [NEW] Suspend is iterrupted by ALT key
Public bug reported: When trying to suspend the system via pressing the power button in the system tray with ALT key pressed, it is possible to interrupt the system to enter sleep mode and fall back to screen lock. While trying to unlock the screen, the system goes to sleep immediately. Gnome-shell is able to suspend the system by drop-down menu in the system tray. By pressing ALT key or long-press the power button until it switches to suspend icon. The system will suspend if it is by the long- press power button, while with ALT key pressed, there is a failure rate that causes the suspend process to be interrupted. The second issue is that if the suspend process is interrupted, the locked screen is shown. While trying to unlock the screen by inputting password, the system will go sleeping after that. STEPS TO REPRODUCE: 1. To suspend system via pressing the power button in the drop-down system tray with ALT key pressed. 2. During system is going to sleep, e.g., screen going dark, emulate a key bounce by pressing ALT key again. RESULTS: The system going to sleep without a problem. EXPECTED RESULTS: The locked screen shows up and goes to sleep after tens of seconds. While trying to unlock screen, system enter suspend after unlocking successfully. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: originate-from-1838504 ** Also affects: gnome-shell Importance: Undecided Status: New ** No longer affects: gnome-shell ** Tags added: originate-from-1838504 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839016 Title: Suspend is iterrupted by ALT key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1839016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837700] Re: Dell system takes a long time to connect network with external dock
Need fix landing in bionic before 31st of August. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837700 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1837700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837700] Re: Dell system takes a long time to connect network with external dock
** Description changed: - 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. + update for SRU process: + + [Impact] + 1. On system featured mac passthrough, e.g., Dell/Lenovo laptop, or system occasionally install two USB ethernet with same MAC address, the system will suffer 90 seconds for network interface renaming mechanism before the last USB ethernet interface to activate. + + [Test Case] + 1. Install ubuntu on Dell laptop. + 2. Connect the Dell laptop with two Realtek 8153 USB ethernet dongle. Users can observe the last one will take 90 seconds for renaming to rename0. + 3. Users can also find that the two USB ethernet have the same MAC address. + + [Regression Potential] + To resolve the issue, drop a debian patch from systemd package. The debian patch is to revert an upstream commit to support 75-persistent-net-generator.rules udev rule. Since the udev rule is deprecated, the regression potential should be relatively low. + + --- + + + 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]:
