[Bug 1793444] Re: Request to support software raid devices, vroc raid also need this
** Tags added: intel originate-from-1922657 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793444 Title: Request to support software raid devices, vroc raid also need this To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1793444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818881] Re: ath10k_pci crashing
It can be reproduced on XPS 19 9380 + Ubuntu 20.04 + 5.8.0-45-generic. It's happening for a while on 20.04, I'm not sure the issue start from which version of kernel or firmware. $ apt list linux-firmware Listing... Done linux-firmware/focal-updates,focal-updates,now 1.187.10 all [installed,automatic] 2:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Bigfoot Networks, Inc. Killer 1435 Wireless-AC [1a56:143a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818881/+attachment/5481628/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818881 Title: ath10k_pci crashing To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1818881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915003] Re: SRU: Always update the initramfs when changing power profile
# suggestion: On nvidia settings UI, there's no message saying it's building initrd after user select on-demand mode. So, the nvidia settings looks like just hangs up when it's building initrd. If user have multiple kernel before selecting on-demand, user might be confused and treat it as nvidia settings UI hangs up then force close it or reboot machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915003] Re: SRU: Always update the initramfs when changing power profile
# verified pass on focal: ## package version as expected. ubuntu@dell-bto-focal-fossa-nvstaging-202005-27873:~$ apt list ubuntu-drivers-common nvidia-prime Listing... Done nvidia-prime/focal-proposed,focal-proposed,now 0.8.16~0.20.04.1 all [installed,automatic] ubuntu-drivers-common/focal-updates,now 1:0.8.6.5~0.20.04.1 amd64 [installed,automatic] ## check if module option in initrd in on-demand mode. $ sudo prime-select on-demand Info: selecting the on-demand profile Writing /lib/modprobe.d/nvidia-runtimepm.conf Updating the initramfs. Please wait for the operation to complete: Done ### then I see the module option in initrd correctly. main/usr/lib/modprobe.d/nvidia-runtimepm.conf:1:options nvidia "NVreg_DynamicPowerManagement=0x02" ## check if module option not in initrd in nvidia mode. $ sudo prime-select nvidia Info: selecting the nvidia profile Deleting /lib/modprobe.d/nvidia-runtimepm.conf Done ### then the module option "NVreg_DynamicPowerManagement=0x02" is removed from initrd correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915003] Re: Always update the initramfs when changing power profile
** Also affects: nvidia-drivers-ubuntu Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: Always update the initramfs when changing power profile To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914670] Re: No HDMI detection
the certification page for target platform for reference : https://certification.ubuntu.com/hardware/202007-28054 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914670 Title: No HDMI detection To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914670] Re: No HDMI detection
** Tags added: fossa-meera-tgl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914670 Title: No HDMI detection To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914670] Re: No HDMI detection
Hi Ian, could you please also provide us the report of what #1 needed? And if convenient, please also provide the tarball created by `sosreport` and `oem-getlogs`. I'm curious about the content of your `lspci -vvvnnk` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914670 Title: No HDMI detection To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914670] Re: No HDMI detection
Hi Ian, We sometime get compatibility issue form different external device and even the HDMI cord(e.g. LP: #1890772). To check if it's a external device issue, could you please help to do some test: 1. Will BIOS shows on external HDMI monitor if you plugged HDMI before booting up your machine? 2. If lower resolution make you HDMI monitor light up? - I saw you make it light up after manually xrander command, how if you change the resolution up and down? (I'm wondering if it related to LP: #1890772) ** Also affects: oem-priority 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/1914670 Title: No HDMI detection To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series
** Tags removed: verification-done-focal ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913200 Title: Introduce the new NVIDIA 460-server series and update the 460 series To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series
I verified it with focal on one machine supported Nvidia runtime pm, machine: 202010-28303 , $ cat /sys/class/dmi/id/product_sku 0A48 $ uname -r 5.10.0-1010-oem $ apt list ubuntu-drivers-common nvidia-prime nvidia-driver-460 Listing... Done nvidia-driver-460/focal-proposed,now 460.39-0ubuntu0.20.04.1 amd64 [installed] nvidia-prime/focal-updates,focal-updates,now 0.8.15.3~0.20.04.1 all [installed,automatic] ubuntu-drivers-common/focal-updates,now 1:0.8.6.3~0.20.04.2 amd64 [installed] $ DISPLAY=:0 checkbox-cli run com.canonical.certification::miscellanea/check-nvidia Outcome: job passed Finalizing session that hasn't been submitted anywhere: checkbox-run-2021-01-28T08.46.29 ==[ Results ]=== ☑ : Generate an entry for each graphics card present in the system. ☑ : check if nvidia dgpu behave as we expected. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913200 Title: Introduce the new NVIDIA 460-server series and update the 460 series To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1905600] Re: Support fingerprint identification in the driver of Synaptics fingerprint reader
Hi Shengyao, Why you set state to in progress? Did you find something regression ? Shengyao Xue <1905...@bugs.launchpad.net> 於 2021年1月25日 週一 下午3:50 寫道： > ** Changed in: oem-priority >Status: Fix Committed => In Progress > > ** Changed in: oem-priority > Assignee: Bin Li (binli) => Shengyao Xue (xueshengyao) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1905600 > > Title: > Support fingerprint identification in the driver of Synaptics > fingerprint reader > > Status in OEM Priority Project: > In Progress > Status in libfprint package in Ubuntu: > Fix Released > Status in libfprint source package in Focal: > Fix Committed > Status in libfprint source package in Groovy: > Fix Committed > > Bug description: > [Impact] > > On Ubuntu 20.04, with Synaptics fingerprint reader, users can use one > fingerprint to login system, but if users add more fingerprints, they > still can only one of those to login, other fingerprints do not work. > > To fix this issue, we need support fingerprint identification in the > driver of Synaptics fingerprint reader, by backport this libfprint commit > to Focal: > https://gitlab.freedesktop.org/libfprint/libfprint/commit/e27b65c9 > > [Test Case] > > I tried backport the commit above to libfprint > (1:1.90.2+tod1-0ubuntu1~20.04.2) in Focal and tested on 3 > ThinkPads(both use the 06cb:00bd Synaptics fingerprint reader), the > multiple fingerprints works well. > > We have other OEM platforms with Synaptics fingerprint reader, we can > use it to validate the changes if needed. > > [Regression Potential] > > the commit comes from Synaptics' engineer, just affects one file: > libfprint/drivers/synaptics/synaptics.c, and only add identification > support in that file, so the regression potential should be low. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/oem-priority/+bug/1905600/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905600 Title: Support fingerprint identification in the driver of Synaptics fingerprint reader To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1905600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904583] Re: SRU: Backport the latest developments on drivers detection and hybrid graphics
I just verified on focal on a machine with BIOS ID:097E (202005-27873): - kernel : 5.6.0-1042-oem $ apt list nvidia-prime ubuntu-drivers-common Listing... Done nvidia-prime/focal,focal,now 0.8.14 all [installed,automatic] ubuntu-drivers-common/now 1:0.8.6.3~0.20.04.2 amd64 [installed,local] $ sudo cat /sys/class/dmi/id/bios_version 1.4.0 $ sudo cat /sys/class/dmi/id/product_sku 097E The Nvidia device sleep as expected. (checked by powertop) The Nvidia renderer works as expected when the user execute an application with "Launch using Dedeicated graphic card" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904583 Title: SRU: Backport the latest developments on drivers detection and hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1904583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793444] Re: Request to support software raid devices, vroc raid also need this
@brian-murray, This patch is there for a while, is it possible to include it to 21.04 then have a backport to Focal? So that we can apply the Intel VROC feature to desktop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793444 Title: Request to support software raid devices, vroc raid also need this To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1793444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793444] Re: Request to support software raid devices, vroc raid also need this
** Tags added: originate-from-1909188 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793444 Title: Request to support software raid devices, vroc raid also need this To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1793444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908885] Re: Fix drm_WARN_ON(common_len <= 0)
** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908885 Title: Fix drm_WARN_ON(common_len <= 0) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904583] Re: SRU: Backport the latest developments on drivers detection and hybrid graphics
** Tags added: originate-from-1905818 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904583 Title: SRU: Backport the latest developments on drivers detection and hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1904583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904583] Re: SRU: Backport the latest developments on drivers detection and hybrid graphics
** Tags added: originate-from-1896445 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904583 Title: SRU: Backport the latest developments on drivers detection and hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1904583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905591] Re: no brightness control after update from 450 to 455
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905591 Title: no brightness control after update from 450 to 455 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1905591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904583] Re: Backport the latest developments on drivers detection and hybrid graphics
** Tags added: oem-priority originate-from-1840753 somerville ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904583 Title: Backport the latest developments on drivers detection and hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1904583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902861] Re: drm/i915/dp_mst - wait longer during the clock recovery for Display port
** Tags removed: originate-from-1897246 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902861 Title: drm/i915/dp_mst - wait longer during the clock recovery for Display port To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902861] Re: drm/i915/dp_mst - wait longer during the clock recovery for Display port
** Changed in: oem-priority Importance: Undecided => Critical ** Tags added: originate-from-1897246 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902861 Title: drm/i915/dp_mst - wait longer during the clock recovery for Display port To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902861] Re: drm/i915/dp_mst - wait longer during the clock recovery for Display port
** Tags added: originate-from-1900092 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902861 Title: drm/i915/dp_mst - wait longer during the clock recovery for Display port To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425462/+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/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425463/+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/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425476/+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/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] Re: dmesg need permission after kernel 5.8
the followed attached message from `apport-collect` shows it did ask permission, but still shows error message in launchpad description. $ id uid=1001(ubuntu) gid=1001(ubuntu) groups=1001(ubuntu),27(sudo) $ apport-collect -p linux-image-5.8.0-25-generic 1901000 AUTHENTICATING FOR org.freedesktop.policykit.exec === Authentication is needed to run `/usr/bin/dmesg' as the super user Multiple identities can be used for authentication: 1. u,,, (u) 2. ,,, (ubuntu) Choose identity to authenticate as (1-2): 2 Password: AUTHENTICATION FAILED === AUTHENTICATING FOR org.freedesktop.policykit.exec === Authentication is needed to run `/usr/share/apport/dump_acpi_tables.py' as the super user Multiple identities can be used for authentication: 1. u,,, (u) 2. ,,, (ubuntu) Choose identity to authenticate as (1-2): 2 Password: AUTHENTICATION FAILED === No journal files were opened due to insufficient permissions. Unexcepted message in bug description: ``` CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized ``` ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425467/+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/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425472/+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/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425477/+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/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425474/+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/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425478/+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/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425465/+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/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425473/+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/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425468/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] [NEW] dmesg need permission after kernel 5.8
Public bug reported: apport used to collect dmesg well before kernel 5.8. But not it just show permission issue while collect dmesg so that apport not able to upload dmesg information for launchpad bugs after kernel 5.8. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apport 2.20.11-0ubuntu50 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 +0800:2020-10-15 18:43:15.784183502 +0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash Date: Thu Oct 22 18:54:46 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2157 F pulseaudio CasperMD5CheckResult: skip CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) MachineType: Dell Inc. Precision 5550 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 06/01/2020 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0203K4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 7654321 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5550 dmi.product.sku: 097E dmi.sys.vendor: Dell Inc. ** Affects: oem-priority Importance: Critical Status: Confirmed ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected groovy ** Tags added: apport-collected ** Description changed: apport used to collect dmesg well before kernel 5.8. But not it just show permission issue while collect dmesg so that apport not able to upload dmesg information for launchpad bugs after kernel 5.8. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apport 2.20.11-0ubuntu50 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 +0800:2020-10-15 18:43:15.784183502 +0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash Date: Thu Oct 22 18:54:46 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 2157 F pulseaudio + CasperMD5CheckResult: skip + CurrentDmesg: + Error: command ['pkexec', 'dmesg'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie + Error executing command as another user: Not authorized + + This incident has been reported. + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2020-10-15 (7 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" -
[Bug 1901000] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425469/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425464/+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/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425470/+files/PaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425466/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425475/+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/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425471/+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/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901000] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1901000/+attachment/5425461/+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/1901000 Title: dmesg need permission after kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900137] Re: PRIME on demand mode uses the wrong GPU
A verification result on a laptop with Nvidia GPU that supports runtime pm. It looks good. 01:00.0 3D controller [0302]: NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) the ubuntu-drivers-common was from: - https://launchpad.net/~alextu/+archive/ubuntu/nvidia-drivers-testing/+sourcepub/11671516/+listing-archive-extra - https://git.launchpad.net/~alextu/+git/ubuntu-drivers-common/commit/?id=32cc96ebb3aa82af5798ac426947c2e33400699f nvidia-prime : 0.8.15 nvidia-driver-450 : 450.80.02-0ubuntu1 verified steps: - ubuntu@u-Precision-5550:~$ DISPLAY=:0 __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | pastebinit https://paste.ubuntu.com/p/MXwVdc9Jn4/ - ubuntu@u-Precision-5550:~$ DISPLAY=:0 __NV_PRIME_RENDER_OFFLOAD=0 __GLX_VENDOR_LIBRARY_NAME="" glxinfo | pastebinit https://paste.ubuntu.com/p/N4pSt3c4H6/ ** Attachment added: "oemlogs-u-Precision-5550-20201019113812+0800.apport.gz" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1900137/+attachment/5423923/+files/oemlogs-u-Precision-5550-20201019113812+0800.apport.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900137 Title: PRIME on demand mode uses the wrong GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1900137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10
** Also affects: oem-priority 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/1849947 Title: Dell XPS 13 (7390) Display Flickering - 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1849947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895855] Re: FFE: support for NVIDIA runtimepm (hybrid gfx)
** Tags added: originate-from-1840753 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895855 Title: FFE: support for NVIDIA runtimepm (hybrid gfx) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1895855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895855] Re: FFE: support for NVIDIA runtimepm (hybrid gfx)
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895855 Title: FFE: support for NVIDIA runtimepm (hybrid gfx) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1895855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
same to #10, the issue is fixed. I verified the installation passed on focal docker image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
It sounds weird to me that focal user will always get an error during installing nvidia-driver-450 after this SRU be done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
got an error message during installation. from a machine from certification pool 201903-26932 $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal $ sudo apt-get install nvidia-driver-450 . E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) ** Attachment added: "install-nv-450.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1887674/+attachment/5409328/+files/install-nv-450.log ** Tags removed: verification-done-focal ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem
hi reporter and any affected user, I can not find any released image included oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10 Same as #4 comment, the only iwlwifi dkms we provided is backport- iwlwifi-dkms. Could you please show me the `ubuntu-report show`? or bto.xml in the recovery partition, so that I know which OEM image you are using. ** Changed in: oem-priority Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850089 Title: iwlwifi fails with linux-image-4.15.0-1059-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1850089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Changed in: oem-priority Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Also affects: hwe-next 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/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
reply to #39, yes it's a trade off that we don't either want user get darkscreen when then randomly plug display port for case like #38 or user get lower bpc on their working display port. So far, there seems no solid way to make sure both requirement. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
according to #40 and conversation on mattermost with Kai-Heng. HWE is planning to add quirk for the faulty dongles so that the dark screen during boot time[1] can be fixed. [1] https://gitlab.freedesktop.org/drm/intel/-/issues/1890 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem
** Tags added: somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850089 Title: iwlwifi fails with linux-image-4.15.0-1059-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1850089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
I afraid we can not just trust (EDID_version >= 1.4 && EDID_supports_10bit). Because this issue caused by any problematic component in the middle of pipeline. To ensure the compatibility, better to just defautly set bpc=8. Think of one scenario, a speaker get his Ubuntu machine onto stage, plug the HDMI or DP projector which works well on latest speaker who is using Windows machine. Then, he get dark screen or audio function lost I guess the Ubuntu user might not aware it's caused by bpc. The default behavior should offer better user experience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1066 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1066 ** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/-/issues/1066 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/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1108 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1108 ** Also affects: xorg-server via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1108 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/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1890772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
Thanks for understanding. There's an upstream bug discussing this similar issue, we can follow their effort there. https://gitlab.freedesktop.org/drm/intel/-/issues/1890 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #1890 https://gitlab.freedesktop.org/drm/intel/-/issues/1890 ** Description changed: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` - Would like to open this bug to open discussion for enhancing user experience. + Would like to open this bug to open discussion for enhancing user + experience. + + existed upstream bug: + - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem 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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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 ** Changed in: oem-priority Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1890772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
I think different from #32. To adding a GUI configure bpc is a long-term plan. Before that,the default behavior should be designed to get the best user experience. As we all know, there're lot of hardware components on the pipline of display path(e.g. socket, converter, dongle, cable, monitor) With any lower quality component on the pipeline, dark screen or function lost is not acceptable. It should be better to provide lower default bpc than dark user's screen. Afterall, user can adjust the bpc by command in short-term or by UI in long-term plan. But if we just dark user's screen, user mostly thinks the hardware is broken or Ubuntu provides poor compatibility(if they compare the same component to Windows). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1890772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889384] Re: ASPM not enabled on child devices behind VMD controller
** Tags added: originate-from-1889754 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889384 Title: ASPM not enabled on child devices behind VMD controller To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1889384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888656] Re: [MIR] tlp
Yes, we adopted TLP for factory image on certified machines from Bionic. And we are adopting TLP to both factory image and stock Ubuntu on certified machines from Focal. Idealy, we have those machines in SRU pool so that TLP could be tested during every SRU cycle. For the certified machine, we applied customized TLP configuration [1] with more aggressive setting to gain more powersaving. Of cause, the malfunction driver issue in powersaving also be covered by the same package. [1] https://code.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-fix-misc-cnl-tlp-estar-conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888656 Title: [MIR] tlp To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1888656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891599] Re: installation stopped by an random exception from mark_install() in Cache class of python3-apt
** Tags added: originate-from-1891603 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891599 Title: installation stopped by an random exception from mark_install() in Cache class of python3-apt To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891599] Re: installation stopped by an random exception from mark_install() in Cache class of python3-apt
I'm trying to upload log, but keep getting launchpad opps. (Error ID: OOPS-6b4d02cb9bb92efa8664d821b400a951) So, I will try uploading syslog later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891599 Title: installation stopped by an random exception from mark_install() in Cache class of python3-apt To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891599] Re: installation stopped by an random exception from mark_install() in Cache class of python3-apt
I'm trying to upload log, but keep getting launchpad opps. So, I will try uploading syslog later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891599 Title: installation stopped by an random exception from mark_install() in Cache class of python3-apt To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891599] [NEW] installation stopped by an random exception from mark_install() in Cache class of python3-apt
Public bug reported: An exception is randomly happening while ubiquity calling cachedpkg.mark_install() [1]. cachedpkg.mark_install() came from Cache class of python3-apt package. It looks a timing issue while ubiquity calling cachedpkg.mark_install(), and a retry can workaround it. The reproduce rate is be about 1/15. Looks there're 2 things can be improved. 1. improve the fault tolerance of Ubiquity while it calling external library. 2. impvove the fault tolerance of python3-apt. [1] https://git.launchpad.net/ubuntu/+source/ubiquity/tree/ubiquity/install_misc.py?h=ubuntu /focal-updates#n534 ** Affects: oem-priority Importance: Critical Assignee: Alex Tu (alextu) Status: New ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1891118 somerville ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891599 Title: installation stopped by an random exception from mark_install() in Cache class of python3-apt To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891599] Re: installation stopped by an random exception from mark_install() in Cache class of python3-apt
for 1. improve the fault tolerance of Ubiquity while it calling external library. We are trying to have severial times retry in ubiquity before thow out the exception. And the installation testing is in progress. ** Tags added: oem-priority originate-from-1891118 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891599 Title: installation stopped by an random exception from mark_install() in Cache class of python3-apt To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878602] Re: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail
** Tags added: oem-priority originate-from-1880498 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878602 Title: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806334] Re: Thunderbolt 2 storage not auto mounted and show in file manager
** Description changed: - OS 18.04 + OS 18.04 & 20.04 Plug thunderbolt 2 storage device, can see the device in lsblk as /dev/sda (and /dev/sda1 is a ext4 partition) however I can't see it in file manager (check attachment, it say TBT3 in the picture, however I use TBT2 and I can reproduce it) + + public bug: https://github.com/storaged-project/udisks/issues/793 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806334 Title: Thunderbolt 2 storage not auto mounted and show in file manager To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1806334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Tags added: originate-from-1887915 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1890772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Tags added: oem-priority originate-from-1886778 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1890772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889539] Re: System power cutoff unexpectedly when running unigine-heaven benchmark
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) ** Tags added: originate-from-1875552 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889539 Title: System power cutoff unexpectedly when running unigine-heaven benchmark To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1889539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806334] Re: Thunderbolt 2 storage not auto mounted and show in file manager
** Summary changed: - Thunderbolt 2 storage won't show in file manager + Thunderbolt 2 storage not auto mounted and show in file manager ** Also affects: udisks2 (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/1806334 Title: Thunderbolt 2 storage not auto mounted and show in file manager To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1806334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889378] Re: dbus method 'Sleep' not work
** Description changed:
+ refer to https://salsa.debian.org/utopia-team/network-
+
manager/-/blob/debian/master/introspection/org.freedesktop.NetworkManager.xml#L157
- refer to
https://salsa.debian.org/utopia-team/network-manager/-/blob/debian/master/introspection/org.freedesktop.NetworkManager.xml#L157
+
-
-
-
+ Control the NetworkManager daemon's sleep state. When asleep, all
+ interfaces that it manages are deactivated. When awake, devices are
+ available to be activated. This command should not be called directly
by
+ users or clients; it is intended for system suspend/resume tracking.
+ -->
+
+
+
But the network not be deactivated after the Sleep method be called.
+
+ steps:
+ 1.$ gdbus call --system --dest org.freedesktop.NetworkManager --object-path
/org/freedesktop/NetworkManager --method org.freedesktop.NetworkManager.Sleep
true
+
+ 2.$ journal ctl ; # see the dbus method be called correctly.
+ 七 29 16:21:10 u-XPS-13-9310 sudo[2822]:u : TTY=pts/1 ; PWD=/home/u
; USER=root ; COMMAND=/usr/bin/gdbus call --system --dest
org.freedesktop.NetworkManager --object-path /org/freedesktop/NetworkManage
+ r --method org.freedesktop.NetworkManager.Sleep true
+ 七 29 16:21:10 u-XPS-13-9310 sudo[2822]: pam_unix(sudo:session): session
opened for user root by (uid=0)
+ 七 29 16:21:10 u-XPS-13-9310 NetworkManager[843]: [1596010870.8622]
manager: sleep: sleep requested (sleeping: no enabled: yes)
+ 七 29 16:21:10 u-XPS-13-9310 NetworkManager[843]: [1596010870.8626]
device (p2p-dev-wlp0s20f3): state change: disconnected -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
+ 七 29 16:21:10 u-XPS-13-9310 NetworkManager[843]: [1596010870.8632]
manager: NetworkManager state is now ASLEEP
+ 七 29 16:21:10 u-XPS-13-9310 NetworkManager[843]: [1596010870.8635]
audit: op="sleep-control" arg="on" pid=2825 uid=0 result="success"
+
+ 3. $ ping 8.8.8.8 ; # still work unexpectedly
+
+ Note: this issue can be reproduced on the latest version of network-
+ manager source : https://git.launchpad.net/network-
+ manager/commit/?id=6e17a2e7ad9453c0afe34dab0e6768ad8ee447c2
** Changed in: oem-priority
Assignee: (unassigned) => Alex Tu (alextu)
** Changed in: oem-priority
Importance: Undecided => High
** Description changed:
refer to https://salsa.debian.org/utopia-team/network-
manager/-/blob/debian/master/introspection/org.freedesktop.NetworkManager.xml#L157
But the network not be deactivated after the Sleep method be called.
steps:
- 1.$ gdbus call --system --dest org.freedesktop.NetworkManager --object-path
/org/freedesktop/NetworkManager --method org.freedesktop.NetworkManager.Sleep
true
+ 1.$ gdbus call --system --dest org.freedesktop.NetworkManager --object-path
/org/freedesktop/NetworkManager --method org.freedesktop.NetworkManager.Sleep
true
- 2.$ journal ctl ; # see the dbus method be called correctly.
- 七 29 16:21:10 u-XPS-13-9310 sudo[2822]:u : TTY=pts/1 ; PWD=/home/u
; USER=root ; COMMAND=/usr/bin/gdbus call --system --dest
org.freedesktop.NetworkManager --object-path /org/freedesktop/NetworkManage
- r --method org.freedesktop.NetworkManager.Sleep true
- 七 29 16:21:10 u-XPS-13-9310 sudo[2822]: pam_unix(sudo:session): session
opened for user root by (uid=0)
- 七 29 16:21:10 u-XPS-13-9310 NetworkManager[843]: [1596010870.8622]
manager: sleep: sleep requested (sleeping: no enabled: yes)
- 七 29 16:21:10 u-XPS-13-9310 NetworkManager[843]: [1596010870.8626]
device (p2p-dev-wlp0s20f3): state change: disconnected -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
- 七 29 16:21:10 u-XPS-13-9310 NetworkManager[843]: [1596010870.8632]
manager: NetworkManager state is now ASLEEP
- 七 29 16:21:10 u-XPS-13-9310 NetworkManager[843]: [1596010870.8635]
audit: op="sleep-control" arg="on" pid=2825 uid=0 result="success"
+ 2.$ journal ctl ; # see the dbus method be called correctly.
+ NetworkManager[843]: [1596010870.8622] manager: sleep: sleep
requested (sleeping: no enabled: yes)
+ NetworkManager[843]: [1596010870.8626] device (p2p-dev-wlp0s20f3):
state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state:
'managed')
+ NetworkManager[843]: [1596010870.8632] manager: NetworkManager state
is now ASLEEP
+ NetworkManager[843]: [1596010870.8635] audit: op="sleep-control"
arg="on" pid=2825 uid=0 result="success"
3. $ ping 8.8.8.8 ; # still work unexpectedly
Note: this issue can be reproduced on the latest version of network-
manager source : https://git.launchpad.net/network-
manager/commit/?id=6e17a2e7ad9453c0afe34dab0e6768ad8ee447c2
** Description changed:
refer to https://salsa.debian.org/utopia-team/network-
manager/-/blob/debian/master
[Bug 1889378] [NEW] dbus method 'Sleep' not work
Public bug reported: refer to https://salsa.debian.org/utopia-team/network-manager/-/blob/debian/master/introspection/org.freedesktop.NetworkManager.xml#L157 But the network not be deactivated after the Sleep method be called. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: oem-priority 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/1889378 Title: dbus method 'Sleep' not work To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1889378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
It's seems not just one patch can fix this issue. I found another corner case that still can trigger a blutoothd segmentation fault. I pair one Bluetooth keyboard but cancel before input pairing keycode. Before timeout of latest keyboard pairing, I pair another Bluetooth keyboard and still cancel it before input pairing keycode. Please hold this SRU process and I'm debugging for that corner case. ** Changed in: bluez (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
** Changed in: bluez (Ubuntu Bionic) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884183] Re: [MIR] oem-somerville-bulbasaur-meta
verified on target machine with -proposed archive enabled, it works well as expected. Please also refer to attached output message from test script. ** Attachment added: "stock_ubuntu_platform_meta.sh.log" https://bugs.launchpad.net/oem-priority/+bug/1884183/+attachment/5394790/+files/stock_ubuntu_platform_meta.sh.log ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884183 Title: [MIR] oem-somerville-bulbasaur-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1884183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872383] Re: blk_update_request error when mount nvme partition
** Tags added: originate-from-1888359 timbuktu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872383 Title: blk_update_request error when mount nvme partition To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
sorry for bad habit that I miss-understanded before. I revised it and put detail information there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
** Description changed: [Impact] - * only impact Bionic machines because series after Bionic already - included this patch. + This patch is for this issue: + steps: + 1. pair bluetooth keyboard + 2. see the dialog asking user input the code for pairing. + 3. press "esc" to cancel it. + 4. blutoothd segfault shows in dmesg after a while. + 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] + [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] - * low, because the same patch from upstream is already there on Groovy, - Focal and Eoan. + * This patch workaround the case that a queue node was created but not + yet assigned function before user input pairing keycode. If the user + cancel the paring before inputting pairing keycode then assign the + function pointer a dummy 'direct_match'. + + * Bluetoothd responses to Bluetooth functions and "queue" is a shared + common data structure, so in case of regression happens then blutoothd + systemd service would be crashed. + + * We can verify this by operating add/remove BT devices to trigger + queue operations. + + * I verified on target machine BIOS ID:0983 on BT mouse, keyboard, + headset on pairing, remove and functionality checking. [Other Info] * NO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
Sorry, the debugging and debdiff was done on the target machine so that the email ID was missed. This attached new debdiff also included the patch and lp number information in the changelog. And also updated the truncated description. ** Patch added: "bluez_5.48-0ubuntu3.5.debdiff" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887910/+attachment/5394261/+files/bluez_5.48-0ubuntu3.5.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
** Description changed: [Impact] - * only impact Bionic machines because series after Bionic already + * only impact Bionic machines because series after Bionic already included this patch. [Test Case] - 1. pair bluetooth keyboard - 2. see the dialog asking user input the code for pairing. - 3. press "esc" to cancel it. - 4. the bluetooth should still work to pair another bluetooth device. + 1. pair bluetooth keyboard + 2. see the dialog asking user input the code for pairing. + 3. press "esc" to cancel it. + 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] - * low, becuase + * low, because the same patch from upstream is already there on Groovy, + Focal and Eoan. [Other Info] - * NO. + * NO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
@seb128, yes, I modified the description and the debdiff is there in #4. ** Description changed: - steps: + [Impact] + + * only impact Bionic machines because series after Bionic already + included this patch. + + [Test Case] + 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. - 4. blutoothd segfault shows in dmesg after a while. - 5. Bluetooth shows off on setting UI of right top corner. + 4. the bluetooth should still work to pair another bluetooth device. - dmesg shows: - [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] + [Regression Potential] + + * low, becuase + + [Other Info] + + * NO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
this is the debdiff which applied the patch , and I also host the modified code there : https://code.launchpad.net/~alextu/ubuntu/+source/bluez/+git/bluez/+ref/lp1887910 -bluetoothd-segv-keyboard ** Patch added: "bluez_5.48-0ubuntu3.5.debdiff" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887910/+attachment/5393459/+files/bluez_5.48-0ubuntu3.5.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887910] [NEW] [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
Public bug reported: steps: 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. blutoothd segfault shows in dmesg after a while. 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] ** Affects: oem-priority Importance: Critical Assignee: Alex Tu (alextu) Status: In Progress ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1886187 timbuktu ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
after this patch, the issue can not be reproduced:
commit 24249e091ab3a935f6ea87b7f7355c689c045a80 (HEAD -> refs/heads/master)
Author: Luiz Augusto von Dentz
Date: Mon Apr 9 14:48:41 2018 +0300
shared/queue: Handle NULL as direct match on queue_remove_if
As with queue_find when function is set to NULL use direct_match as
callback.
diff --git a/src/shared/queue.c b/src/shared/queue.c
index 5ddb8326d..60df11143 100644
--- a/src/shared/queue.c
+++ b/src/shared/queue.c
@@ -280,9 +280,12 @@ void *queue_remove_if(struct queue *queue,
queue_match_func_t function,
{
struct queue_entry *entry, *prev = NULL;
- if (!queue || !function)
+ if (!queue)
return NULL;
+ if (!function)
+ function = direct_match;
+
entry = queue->head;
** Tags added: oem-priority originate-from-1886187 timbuktu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887910
Title:
[bionic]blutoothd segfault when you cancel the keyboard pairing during
the dialog for pairing code
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882885] Re: FP Auth enroll for Multi user Scenario
I just follow your instructions on XPS 9300 with goodix fingerprint driver. `apt-get update; apt-get dist-upgrade -y; apt-get install -y libfprint-2-tod1-goodix` (there's an online update is on-going, after that, libfprint-2-tod1-goodix will be installed automatically) But I can not reproduce the issue you encountered. I will guess you are encountering the known issue there: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1865838It will stop FP authentication after several incorrect fingerprints without error display. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882885 Title: FP Auth enroll for Multi user Scenario To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882885] Re: FP Auth enroll for Multi user Scenario
also attached the logs from oem-getlogs from apport package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882885 Title: FP Auth enroll for Multi user Scenario To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882885] Re: FP Auth enroll for Multi user Scenario
also attached the logs from oem-getlogs from apport package. ** Attachment added: "oemlogs-u-XPS-13-9300-20200713183746+0800.apport.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882885/+attachment/5392305/+files/oemlogs-u-XPS-13-9300-20200713183746+0800.apport.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882885 Title: FP Auth enroll for Multi user Scenario To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884229] Re: tpm2_createprimary failed on non-supported algorithm sha3_256
this issue is waiting for upstream release a new version included the fix. [1] [2] [1] https://github.com/tpm2-software/tpm2-tools/issues/2110 [2] https://github.com/tpm2-software/tpm2-tools/releases ** Changed in: oem-priority Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884229 Title: tpm2_createprimary failed on non-supported algorithm sha3_256 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1884229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884183] Re: [MIR] oem-somerville-bulbasaur-meta
** Description changed: [Availability] - This is a pilot running meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet. + This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet. oem-somerville-bulbasaur 20.04~ubuntu1 for focal in https://launchpad.net/~oem-solutions-engineers/+archive/ubuntu/oem-projects-meta [Rationale] We want to improve the hardware support for OEM platform on focal. [Security] No CVE/known security issue. [Quality assurance] I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on target OEM platform and it works as expected. oem-somerville-bulbasaur-meta will be upgraded to 20.04ubuntu1 from OEM archive. [Dependencies] It only depends on ubuntu-oem-keyring. [Standards compliance] This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM. [Maintenance] Canonical OEM Enablement Team will take care of the maintenance. [Background information] Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details. Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to verify this MIR against the reference package in the archive. Copied from bug #1868254 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884183 Title: [MIR] oem-somerville-bulbasaur-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1884183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844410] Re: [TGL] Thunderbolt support (Tiger Lake)
Does the #10 target to 5.6.0.1019.16 for focal? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844410 Title: [TGL] Thunderbolt support (Tiger Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1844410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884229] Re: tpm2_createprimary failed on non-supported algorithm sha3_256
No, we don't need this MP while upstream fixed it. But we need another MP to check the return code. ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884229 Title: tpm2_createprimary failed on non-supported algorithm sha3_256 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1884229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885673] [NEW] won't auto-select input when headset is plugged and selected in pop-up window
Public bug reported: Step to reproduce: 1. plug-in headset 2. select headset in pop-up window. 3. check g-c-c Expected result: correct input is selected so that mic on the headset just works Actual result: The correct input is not selected. a patch is there waiting for upstream review : https://gitlab.gnome.org/GNOME/libgnome-volume- control/-/merge_requests/10 ** Affects: oem-priority Importance: High Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1875597 originate-from-1882905 somerville ** Summary changed: - mixer-control: adding ucm port names for audio device selection + won't auto-select input when headset is plugged and selected in pop-up window Edit ** Summary changed: - won't auto-select input when headset is plugged and selected in pop-up window Edit + won't auto-select input when headset is plugged and selected in pop-up window ** Description changed: - Recently Intel added a new audio driver in the Linux kernel, it is - called sof driver. This driver is needed on the laptops which - connect the digital mic to the PCH instead of the codec. To make the - sof driver work with pulseaudio, the ucm is mandatory. Intel - wrote the ucm for the machines with multi-function audio jack, with - this ucm, the port names are different from the ones without ucm, this - is the port names with the ucm: - [In] Dmic: Digital Microphone (priority: 100, latency offset: 0 usec) - Part of profile(s): Hdmi3, Hdmi2, Hdmi1, HiFi - [In] Headphone Microphone: Headphone Microphone (priority: 100, latency offset: 0 usec, available) - Part of profile(s): Hdmi3, Hdmi2, Hdmi1, HiFi - [In] Headset Microphone: Headset Microphone (priority: 100, latency offset: 0 usec, available) - Part of profile(s): Hdmi3, Hdmi2, Hdmi1, HiFi - [Out] Headphone: Headphone (priority: 200, latency offset: 0 usec, available) - Part of profile(s): HiFi - [Out] Speaker: Speaker (priority: 100, latency offset: 0 usec) - Part of profile(s): HiFi - To make the audio device selection work, let's add those new port - names. - And with the ucm, the Dmic (internal mic) is on one source since the - dmic connects to PCH, the headphone-mic and headset mic are on another - source since they connect to the codec. This needs us to add calling - set_default_source() in the source_info_cb(), it is safe even for old - machines on which internal mic, headphone-mic and headset-mic are on - the same source. + Step to reproduce: + + 1. plug-in headset + 2. select headset in pop-up window. + 3. check g-c-c + + Expected result: + correct input is selected so that mic on the headset just works + + Actual result: + The correct input is not selected. + + a patch is there waiting for upstream review : + https://gitlab.gnome.org/GNOME/libgnome-volume- + control/-/merge_requests/10 ** Tags added: oem-priority originate-from-1882905 somerville ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Importance: Critical => High ** Tags added: originate-from-1875597 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885673 Title: won't auto-select input when headset is plugged and selected in pop-up window To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1885673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884183] Re: [MIR] oem-somerville-bulbasaur-meta
** Patch added: "oem-somerville-bulbasaur-meta_20.04~ubuntu2.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1884183/+attachment/5386741/+files/oem-somerville-bulbasaur-meta_20.04~ubuntu2.debdiff ** Changed in: ubuntu Status: Invalid => New ** Changed in: oem-priority Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884183 Title: [MIR] oem-somerville-bulbasaur-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1884183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority
** Tags added: oem-priority originate-from-1880192 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882161 Title: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884229] Re: tpm2_createprimary failed on non-supported algorithm sha3_256
** Description changed: tpm2-tss not yet support sha3_256. In this test case on a machine reported it support sha3_256 then call `tpm2_createprimary -Q -g sha3_256 -G rsa -c context.out` - And the test case will marked as error even tpm2_createprimary returned - "5 - Non supported scheme. Applicable to tpm2_testparams." + The this test case will be marked as error. + + + tpm2_createprimary should returned "5 - Non supported scheme. Applicable to tpm2_testparams." , so that we can skip the non-supported algorithm. upstream bug: https://github.com/tpm2-software/tpm2-tools/issues/2110 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884229 Title: tpm2_createprimary failed on non-supported algorithm sha3_256 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1884229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
