[Touch-packages] [Bug 2037965] Re: [Demo][Experimental] My brightness hotkey doesn't work on some PC
** Patch added: "systemd_249.11-0ubuntu3.12.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037965/+attachment/5705848/+files/systemd_249.11-0ubuntu3.12.debdiff ** Package changed: systemd (Ubuntu) => null-and-void ** Summary changed: - [Demo][Experimental] My brightness hotkey doesn't work on some PC + null ** Description changed: - hwdb lacks of the map for my brightness hotkey. + null -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037965 Title: null Status in NULL Project: New Bug description: null To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/2037965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037965] [NEW] null
Public bug reported: null ** Affects: null-and-void Importance: Undecided Status: New ** Summary changed: - My brightness hotkey doesn't work on some PC + [Demo][Experimental] My brightness hotkey doesn't work on some PC -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037965 Title: null Status in NULL Project: New Bug description: null To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/2037965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980
** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1998765 Title: libnl3 3.4.0 doesn't work with WCN3980 Status in OEM Priority Project: New Status in libnl3 package in Ubuntu: New Bug description: When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect to an AP. I tried a different libnl3 from BSP and found that WCN3980 can work correctly. The version used in BSP is 3.5.0. I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the root cause. According to the commit, it seems that the flag should be set for kernel later than 5.2. [1] https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon
** Changed in: oem-priority Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1969976 Title: DynamicUser=1 doesn't get along with services that need dbus-daemon Status in Fwupd: Fix Released Status in OEM Priority Project: Fix Committed Status in systemd: New Status in fwupd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Status in fwupd source package in Focal: Fix Committed Status in systemd source package in Focal: Won't Fix Status in fwupd source package in Impish: Won't Fix Status in systemd source package in Impish: Won't Fix Status in fwupd source package in Jammy: Fix Committed Status in systemd source package in Jammy: Won't Fix Bug description: Updating to systemd 245.4-4ubuntu3.16 has caused a regression in Ubuntu 20.04, that fwupd-refresh.service always fails to run. This has been root caused down to the changes in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538 Unfortunately this is an upstream issue introduced by stable systemd. https://github.com/systemd/systemd/issues/22737 The problem also occurs in Ubuntu 22.04 with a newer systemd release. As discussed in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61 it's a tradeoff of issues. So within Ubuntu something probably needs to be done about fwupd-refresh.service. One proposal is to remove DynamicUser=yes from the systemd unit, but this will mean fwupdgmr refresh runs as root. It's relatively sandboxed by other security mechanisms, but still not ideal. Could we repurpose any other service account? Or alternatively we can make a new fwupd service account that this systemd unit uses. To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1969976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon
Test method: "systemctl start fwupd-refresh.service" and check syslog to see if the fwupd metadata could be updated. Per test on focal, use existing 1.7.5-3~20.04.1, still can reproduce this issue. After install 1.7.9-1~20.04.1 from the proposed channel, can't reproduce this issue. Given so, mark verification-done-focal ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1969976 Title: DynamicUser=1 doesn't get along with services that need dbus-daemon Status in Fwupd: Fix Released Status in OEM Priority Project: In Progress Status in systemd: New Status in fwupd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Status in fwupd source package in Focal: Fix Committed Status in systemd source package in Focal: Won't Fix Status in fwupd source package in Impish: Won't Fix Status in systemd source package in Impish: Won't Fix Status in fwupd source package in Jammy: Fix Committed Status in systemd source package in Jammy: Won't Fix Bug description: Updating to systemd 245.4-4ubuntu3.16 has caused a regression in Ubuntu 20.04, that fwupd-refresh.service always fails to run. This has been root caused down to the changes in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538 Unfortunately this is an upstream issue introduced by stable systemd. https://github.com/systemd/systemd/issues/22737 The problem also occurs in Ubuntu 22.04 with a newer systemd release. As discussed in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61 it's a tradeoff of issues. So within Ubuntu something probably needs to be done about fwupd-refresh.service. One proposal is to remove DynamicUser=yes from the systemd unit, but this will mean fwupdgmr refresh runs as root. It's relatively sandboxed by other security mechanisms, but still not ideal. Could we repurpose any other service account? Or alternatively we can make a new fwupd service account that this systemd unit uses. To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1969976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon
given #23, jammy is tested and test passed, thank you. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1969976 Title: DynamicUser=1 doesn't get along with services that need dbus-daemon Status in Fwupd: Fix Released Status in OEM Priority Project: In Progress Status in systemd: New Status in fwupd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Status in fwupd source package in Focal: Fix Committed Status in systemd source package in Focal: Won't Fix Status in fwupd source package in Impish: Won't Fix Status in systemd source package in Impish: Won't Fix Status in fwupd source package in Jammy: Fix Committed Status in systemd source package in Jammy: Won't Fix Bug description: Updating to systemd 245.4-4ubuntu3.16 has caused a regression in Ubuntu 20.04, that fwupd-refresh.service always fails to run. This has been root caused down to the changes in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538 Unfortunately this is an upstream issue introduced by stable systemd. https://github.com/systemd/systemd/issues/22737 The problem also occurs in Ubuntu 22.04 with a newer systemd release. As discussed in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61 it's a tradeoff of issues. So within Ubuntu something probably needs to be done about fwupd-refresh.service. One proposal is to remove DynamicUser=yes from the systemd unit, but this will mean fwupdgmr refresh runs as root. It's relatively sandboxed by other security mechanisms, but still not ideal. Could we repurpose any other service account? Or alternatively we can make a new fwupd service account that this systemd unit uses. To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1969976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon
** Changed in: oem-priority Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1969976 Title: DynamicUser=1 doesn't get along with services that need dbus-daemon Status in Fwupd: Fix Released Status in OEM Priority Project: In Progress Status in systemd: New Status in fwupd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Status in fwupd source package in Focal: Fix Committed Status in systemd source package in Focal: Won't Fix Status in fwupd source package in Impish: Won't Fix Status in systemd source package in Impish: Won't Fix Status in fwupd source package in Jammy: Fix Committed Status in systemd source package in Jammy: Won't Fix Bug description: Updating to systemd 245.4-4ubuntu3.16 has caused a regression in Ubuntu 20.04, that fwupd-refresh.service always fails to run. This has been root caused down to the changes in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538 Unfortunately this is an upstream issue introduced by stable systemd. https://github.com/systemd/systemd/issues/22737 The problem also occurs in Ubuntu 22.04 with a newer systemd release. As discussed in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61 it's a tradeoff of issues. So within Ubuntu something probably needs to be done about fwupd-refresh.service. One proposal is to remove DynamicUser=yes from the systemd unit, but this will mean fwupdgmr refresh runs as root. It's relatively sandboxed by other security mechanisms, but still not ideal. Could we repurpose any other service account? Or alternatively we can make a new fwupd service account that this systemd unit uses. To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1969976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1760106] Re: Enable configuring resume offset via sysfs
** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1760106 Title: Enable configuring resume offset via sysfs Status in OEM Priority Project: Fix Released Status in klibc package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in klibc source package in Bionic: New Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in klibc source package in Cosmic: New Status in linux source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Cannot hibernate & resume from a swapfile [Test Case] * Create or enlarge swapfile to be big enough for hibernation * Attempt to hibernate and resume [Regression Potential] * Hibernation is not reliable technology in itself, and multiple things may cause failure to resume. Thus it is sufficient to validate this bug after swapfile is attempted for hibernation and the disk offset kernel parameter is modified. Irrespective if actual suspending or resume were successful or not. [Other Info] * Original bug report In 4.17 a new attribute is introduced to configure the hibernation resume offset. Since Ubuntu enables a swapfile by default this attribute is important to be able to make hibernation work "out of the box". The patch in the kernel is here: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9 Systemd support for adopting this change is available here: https://github.com/systemd/systemd/pull/8406 As of 3/30/18 it's not yet been merged however. Klibc support for adopting this change is available here: https://www.zytor.com/pipermail/klibc/2018-March/003986.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760106/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) ** Tags removed: verification-done-jammy verification-needed ** Tags added: fwupd ** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1969976 Title: DynamicUser=1 doesn't get along with services that need dbus-daemon Status in Fwupd: Fix Released Status in OEM Priority Project: Confirmed Status in systemd: New Status in fwupd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Status in fwupd source package in Focal: Confirmed Status in systemd source package in Focal: Won't Fix Status in fwupd source package in Impish: Won't Fix Status in systemd source package in Impish: Won't Fix Status in fwupd source package in Jammy: Confirmed Status in systemd source package in Jammy: Won't Fix Bug description: Updating to systemd 245.4-4ubuntu3.16 has caused a regression in Ubuntu 20.04, that fwupd-refresh.service always fails to run. This has been root caused down to the changes in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538 Unfortunately this is an upstream issue introduced by stable systemd. https://github.com/systemd/systemd/issues/22737 The problem also occurs in Ubuntu 22.04 with a newer systemd release. As discussed in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61 it's a tradeoff of issues. So within Ubuntu something probably needs to be done about fwupd-refresh.service. One proposal is to remove DynamicUser=yes from the systemd unit, but this will mean fwupdgmr refresh runs as root. It's relatively sandboxed by other security mechanisms, but still not ideal. Could we repurpose any other service account? Or alternatively we can make a new fwupd service account that this systemd unit uses. To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1969976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon
as the deb is removed from jammy proposed, change back to confimed ** Changed in: fwupd (Ubuntu Jammy) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1969976 Title: DynamicUser=1 doesn't get along with services that need dbus-daemon Status in Fwupd: Fix Released Status in systemd: New Status in fwupd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Status in fwupd source package in Focal: Confirmed Status in systemd source package in Focal: Won't Fix Status in fwupd source package in Impish: Won't Fix Status in systemd source package in Impish: Won't Fix Status in fwupd source package in Jammy: Confirmed Status in systemd source package in Jammy: Won't Fix Bug description: Updating to systemd 245.4-4ubuntu3.16 has caused a regression in Ubuntu 20.04, that fwupd-refresh.service always fails to run. This has been root caused down to the changes in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538 Unfortunately this is an upstream issue introduced by stable systemd. https://github.com/systemd/systemd/issues/22737 The problem also occurs in Ubuntu 22.04 with a newer systemd release. As discussed in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61 it's a tradeoff of issues. So within Ubuntu something probably needs to be done about fwupd-refresh.service. One proposal is to remove DynamicUser=yes from the systemd unit, but this will mean fwupdgmr refresh runs as root. It's relatively sandboxed by other security mechanisms, but still not ideal. Could we repurpose any other service account? Or alternatively we can make a new fwupd service account that this systemd unit uses. To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1969976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time
no activity for 2 years. ** Changed in: oem-priority Importance: Critical => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1868915 Title: [focal] nm-online -s --timeout=10 timeout every time Status in MAAS: Invalid Status in OEM Priority Project: New Status in network-manager package in Ubuntu: Triaged Bug description: Also created bug on upstream : https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398 This issue will cause "NetworkManager-wait-online.service: Failed with result 'exit-code'." And cloud-init.service is counting on this service for network status. So this issue will finally cause MaaS deploying failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 [modified: lib/systemd/system/NetworkManager-wait-online.service] ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Wed Mar 25 12:43:13 2020 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-20200316-60+fossa-staging+X09 IfupdownConfig: source /etc/network/interfaces.d/*.cfg InstallationDate: Installed on 2020-03-25 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200316-08:40 IpRoute: default via 192.168.101.1 dev eno1 proto static metric 100 10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 100 NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device "/sys/class/net/bonding_masters": No such device X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME netplan-eno1 10838d80-caeb-349e-ba73-08ed16d4d666 ethernet 158577 廿廿年三月廿五日 (週三) 十二時39分37秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/netplan-eno1.nmconnection nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected starting full enabled disabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1868915/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in OEM Priority Project: Fix Released Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: - Impact software-properties-gtk hit an exception when dealing some drivers - Test Case On a Dell XPS 13 9320 enable ppa:oem-solutions-group/intel-ipu6 and try to install libcamhal-ipu6ep0 using software-properties-gtk https://errors.ubuntu.com/problem/d3c26abd1d80970615ad06cff24972cee3001e57 should not include reports on the new version - Regression potential The change make the driver code ignore one extra type of error, it shouldn't impact on any of the already working cases. Ensure that drivers that were hitting the error correctly install now [racb] It's possible that we accidentally catch and hide a real error due to an unrelated TypeError exception being raised inside the try block. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center software-properties-gtk 0.99.22 3) What you expected to happen No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. 4) What happened instead It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
** Changed in: oem-priority Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: In Progress Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Bug description: [Impact] 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] * 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1896098] Re: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack
originate bug fixed ** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1896098 Title: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack Status in OEM Priority Project: Fix Released Status in pulseaudio package in Ubuntu: Invalid Bug description: I suspect this is a pulseaudio or alsa bug. Our test team reported this: 1. Prepare Padme-3 machine and Install Ubuntu_20.04 OS . 2. Boot system. 3. Play audio or video file. 4. Open Settings > Sound. 5. Hot attach headset. 6. Notice that headset is selected as output device in sound settings and sound can be heard from headset => EXPECTED 7. While playback, select Internal Speaker as output device => KEYPOINT 9. Notice:SUT havo no sound from Internal Speakers => PROBLEM I was able to confirm this - it seems with the headphones connected that I can't select the system speakers. If I don't have headphones connected I can switch between dock audio and system speakers correctly - so it's just related to the audio jack Thanks Mark To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in pulseaudio source package in Groovy: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a headset to the problematic Dell AIO machine will not automatically select headset-mic/headphone-mic, and they also do not show up in Gnome sound settings, leading to failure to record any sound. With the new proposed package, on those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
I checked software-properties/0.99.22.2 in jammy-proposed and it does fix the problem. ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Assignee: (unassigned) => Shih-Yuan Lee (fourdollars) ** Changed in: oem-priority Status: New => Fix Committed ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in OEM Priority Project: Fix Committed Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Committed Bug description: - Impact software-properties-gtk hit an exception when dealing some drivers - Test Case On a Dell XPS 13 9320 enable ppa:oem-solutions-group/intel-ipu6 and try to install libcamhal-ipu6ep0 using software-properties-gtk https://errors.ubuntu.com/problem/d3c26abd1d80970615ad06cff24972cee3001e57 should not include reports on the new version - Regression potential The change make the driver code ignore one extra type of error, it shouldn't impact on any of the already working cases. Ensure that drivers that were hitting the error correctly install now [racb] It's possible that we accidentally catch and hide a real error due to an unrelated TypeError exception being raised inside the try block. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center software-properties-gtk 0.99.22 3) What you expected to happen No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. 4) What happened instead It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970190] Re: [Feature]Wrong default vaule for Brazil Keyboard layout on ThinkPad
** Also affects: oem-priority Importance: Undecided Status: New ** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1970190 Title: [Feature]Wrong default vaule for Brazil Keyboard layout on ThinkPad Status in OEM Priority Project: New Status in console-setup package in Ubuntu: New Bug description: On ThinkPad, when I select 'Portuguese(Brazil)', it will use 'Portuguese(Brazil)' on second column, but the default value should be 'Portuguese(Brazil)-Portuguese(Brazil, IBM/Lenovo ThinkPad)'. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1970190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
** Description changed: - 1) Ubuntu 22.04 - 2) software-properties-gtk 0.99.22 - 3) No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 - 4) It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. + 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu + Ubuntu 22.04 + + 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center + software-properties-gtk 0.99.22 + + 3) What you expected to happen + No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 + It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. + + 4) What happened instead + It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in OEM Priority Project: New Status in software-properties package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center software-properties-gtk 0.99.22 3) What you expected to happen No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. 4) What happened instead It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in OEM Priority Project: New Status in software-properties package in Ubuntu: New Bug description: 1) Ubuntu 22.04 2) software-properties-gtk 0.99.22 3) No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 4) It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969460] [NEW] software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
Public bug reported: 1) Ubuntu 22.04 2) software-properties-gtk 0.99.22 3) No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 4) It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: jammy oem-priority wayland-session ** Attachment added: "_usr_bin_software-properties-gtk.1001.crash" https://bugs.launchpad.net/bugs/1969460/+attachment/5581435/+files/_usr_bin_software-properties-gtk.1001.crash ** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in OEM Priority Project: New Status in software-properties package in Ubuntu: New Bug description: 1) Ubuntu 22.04 2) software-properties-gtk 0.99.22 3) No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 4) It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome
per test on jammy updated on 2022/03/28, wayland mode, OSK works fine with firefox snap (v98.0.2-1, r1154) ** Also affects: oem-priority Importance: Undecided Status: New ** Tags added: 2-in-1 ** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831039 Title: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome Status in OEM Priority Project: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: When using wayland - onscreen keyboard not open in text inputs in many applications such as firefox or chrome. Ubuntu 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-06-09 (1455 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcEnviron: LANG=cs_CZ.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-31 (368 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1831039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966356] Re: ibus input method not working
Hmm, weird that I can't reproduce this issue now. I'll set this to in- complete temporary. Btw, I try to add nomodeset to booting parameter, and I found that I can't run in Wayland mode. It's only x11 mode (and the icon to select between wayland and x11 mode is not there) ** Changed in: ibus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1966356 Title: ibus input method not working Status in ibus package in Ubuntu: Incomplete Bug description: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. Note: per test, add --xim works for below cases: 1. x11 mode 2. Wayland mode, x11 client, test by using microsoft edge. 3. Wayland mode, Wayland client, tested by using gnome-terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966356] Re: ibus input method not working
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1966356 Title: ibus input method not working Status in ibus package in Ubuntu: New Bug description: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. Note: per test, add --xim works for below cases: 1. x11 mode 2. Wayland mode, x11 client, test by using microsoft edge. 3. Wayland mode, Wayland client, tested by using gnome-terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966356] [NEW] ibus input method not working
Public bug reported: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. Note: per test, add --xim works for below cases: 1. x11 mode 2. Wayland mode, x11 client, test by using microsoft edge. 3. Wayland mode, Wayland client, tested by using gnome-terminal. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Description changed: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. - Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, + Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, by modify /usr/lib/systemd/user/gnome-session.target.wants/org.freedesktop.IBus.session.GNOME.service, then it works. ** Description changed: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. - Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, by modify /usr/lib/systemd/user/gnome-session.target.wants/org.freedesktop.IBus.session.GNOME.service, + Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. + + Note: per test, add --xim works for below cases: + + 1. x11 mode + 2. Wayland mode, x11 client, test by using microsoft edge. + 3. Wayland mode, Wayland client, tested by using gnome-terminal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1966356 Title: ibus input method not working Status in ibus package in Ubuntu: New Bug description: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. Note: per test, add --xim works for below cases: 1. x11 mode 2. Wayland mode, x11 client, test by using microsoft edge. 3. Wayland mode, Wayland client, tested by using gnome-terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
For Today, the version of MondemManager in jammy 1.18.6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960768] Re: fwupd crash on stop
saw the new libgusb goes to jammy channel. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: Fix Released Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Fix Released Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960768] Re: fwupd crash on stop
I test the libgusb from jammy-proposed, and it fixed this issue on a machine that previously can reliably reproduce this issue. Guess it's on it's way to jammy or jammy-update channel. ** Changed in: oem-priority Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: Fix Released Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Fix Released Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960768] Re: fwupd crash on stop
debian sid now has libgusb version 0.3.10. And it's in jammy-proposed now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: In Progress Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Confirmed Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960768] Re: fwupd crash on stop
** Also affects: libusb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: In Progress Status in fwupd package in Ubuntu: New Status in libusb package in Ubuntu: New Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952735] Re: Add Microphone mute key mapping for Dell machine
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952735 Title: Add Microphone mute key mapping for Dell machine Status in OEM Priority Project: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell machine add new microphone mute key on keyboard, add this key mapping to make it work. [Test Plan] * Use a Dell machine, which has this microphone mute key, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952735/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952735] Re: Add Microphone mute key mapping for Dell machine
** Changed in: oem-priority Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952735 Title: Add Microphone mute key mapping for Dell machine Status in OEM Priority Project: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell machine add new microphone mute key on keyboard, add this key mapping to make it work. [Test Plan] * Use a Dell machine, which has this microphone mute key, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952735/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952083] Re: Add support for Beige Goby
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1952083 Title: Add support for Beige Goby Status in amd: New Status in OEM Priority Project: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Released Bug description: Impact] New hardware support for AMD's Beige Goby needs a commit backported to mesa. This is only needed on focal, skipping hirsute (no kernel support there). Fixed in impish and up. [Test plan] Install updates, boot a BG machine and check that the desktop has full hardware acceleration. [Where problems could occur] Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1952083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952083] Re: Add support for Beige Goby
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal ** Changed in: oem-priority Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1952083 Title: Add support for Beige Goby Status in amd: New Status in OEM Priority Project: Fix Committed Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Bug description: Impact] New hardware support for AMD's Beige Goby needs a commit backported to mesa. This is only needed on focal, skipping hirsute (no kernel support there). Fixed in impish and up. [Test plan] Install updates, boot a BG machine and check that the desktop has full hardware acceleration. [Where problems could occur] Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1952083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946343] Re: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
** Changed in: dell Status: Confirmed => Fix Committed ** Changed in: oem-priority Status: In Progress => Fix Released ** Changed in: dell Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1946343 Title: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3 Status in Dell Ubuntu Project: Fix Released Status in OEM Priority Project: Fix Released Status in base-files package in Ubuntu: Invalid Bug description: Refer: https://answers.launchpad.net/ubuntu/+question/698949 I recently bought a Dell laptop with Ubuntu pre-installed in it. Looks like it came with Ubuntu 20.04.2 and OEM Linux Kernel in it. After my initial login (on October 1, 2021), the 'Software Updater' GUI prompted me for updates, which I went ahead with. However at the end of it, I noticed that I was still at 20.04.2 with Linux Kernel at 5.10.0-1045-oem. lsb_release -a --- No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1) Release:20.04 Codename: focal uname -a - Linux dev-linux 5.10.0-1045-oem #47-Ubuntu SMP Wed Aug 18 10:41:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Then I manually tried sudo apt update and sudo apt upgrade / dist- upgrade from the terminal, but nothing got upgraded. When I invoked the GUI 'Software Updater' again, it showed me that my system was already up-to-date. However, as 20.04.3 was released end of Aug 2021, I was expecting that I should be at that release after my initial updates. Since that didn't happen, I asked a question regarding this in askubuntu followed by launchpad https://answers.launchpad.net/ubuntu/+question/698949, thinking my update had failed for some unknown reason. However, based on some inputs from other users, we were able to narrow down the problem to /usr/lib/os-release file not having the right contents in it. Every other file including /usr/lib/os-release.oem- release, /etc/issue, /etc/issue.net specifies that I am on 20.04.3. Whereas only /usr/lib/os-release (and its symlink /etc/release) specifies my current release as 20.04.2. Even the lsb_release -a command always displays the output of /usr/lib/os-release file only. $ cat /usr/lib/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /usr/lib/os-release.oem-release NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /etc/issue Ubuntu 20.04.3 LTS \n \l $ cat /etc/issue.net Ubuntu 20.04.3 LTS If you look at the timestamp of these files, strangely os-release had a newer timestamp of Oct 1 compared to other files. $ ls -l /usr/lib/os-release -rw-r--r-- 1 root root 406 Oct 1 20:31 /usr/lib/os-release $ ls -l /usr/lib/os-release.oem-release -rw-r--r-- 1 root root 382 Aug 4 07:53 /usr/lib/os-release.oem-release $ ls -l /etc/issue -rw-r--r-- 1 root root 26 Aug 4 07:53 /etc/issue $ ls -l /etc/issue.net -rw-r--r-- 1 root root 19 Aug 4 07:53 /etc/issue.net Please note that, other software package updates, and linux kernel updates are happening automatically without any issues so far for me. Few days back even got a new kernel update. $ uname -a Linux vivek-dev-linux 5.10.0-1049-oem #51-Ubuntu SMP Mon Sep 27 11:01:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Workarounds Attempted - 1. Commented out all non-ubuntu external sources from /etc/apt/*.list. Then performed an apt clean + update + upgrade. But still nothing happened and the same issue remained. 2. Tried performing apt-install --reinstall base-files. But still nothing changed: $ sudo apt install --reinstall base-files Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 4 not upgraded. Need to get 60.6 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 base-files amd64 11ubuntu5.4 [60.6
[Touch-packages] [Bug 1946343] Re: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
** Changed in: oem-priority Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1946343 Title: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3 Status in Dell Ubuntu Project: Confirmed Status in OEM Priority Project: In Progress Status in base-files package in Ubuntu: Invalid Bug description: Refer: https://answers.launchpad.net/ubuntu/+question/698949 I recently bought a Dell laptop with Ubuntu pre-installed in it. Looks like it came with Ubuntu 20.04.2 and OEM Linux Kernel in it. After my initial login (on October 1, 2021), the 'Software Updater' GUI prompted me for updates, which I went ahead with. However at the end of it, I noticed that I was still at 20.04.2 with Linux Kernel at 5.10.0-1045-oem. lsb_release -a --- No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1) Release:20.04 Codename: focal uname -a - Linux dev-linux 5.10.0-1045-oem #47-Ubuntu SMP Wed Aug 18 10:41:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Then I manually tried sudo apt update and sudo apt upgrade / dist- upgrade from the terminal, but nothing got upgraded. When I invoked the GUI 'Software Updater' again, it showed me that my system was already up-to-date. However, as 20.04.3 was released end of Aug 2021, I was expecting that I should be at that release after my initial updates. Since that didn't happen, I asked a question regarding this in askubuntu followed by launchpad https://answers.launchpad.net/ubuntu/+question/698949, thinking my update had failed for some unknown reason. However, based on some inputs from other users, we were able to narrow down the problem to /usr/lib/os-release file not having the right contents in it. Every other file including /usr/lib/os-release.oem- release, /etc/issue, /etc/issue.net specifies that I am on 20.04.3. Whereas only /usr/lib/os-release (and its symlink /etc/release) specifies my current release as 20.04.2. Even the lsb_release -a command always displays the output of /usr/lib/os-release file only. $ cat /usr/lib/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /usr/lib/os-release.oem-release NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /etc/issue Ubuntu 20.04.3 LTS \n \l $ cat /etc/issue.net Ubuntu 20.04.3 LTS If you look at the timestamp of these files, strangely os-release had a newer timestamp of Oct 1 compared to other files. $ ls -l /usr/lib/os-release -rw-r--r-- 1 root root 406 Oct 1 20:31 /usr/lib/os-release $ ls -l /usr/lib/os-release.oem-release -rw-r--r-- 1 root root 382 Aug 4 07:53 /usr/lib/os-release.oem-release $ ls -l /etc/issue -rw-r--r-- 1 root root 26 Aug 4 07:53 /etc/issue $ ls -l /etc/issue.net -rw-r--r-- 1 root root 19 Aug 4 07:53 /etc/issue.net Please note that, other software package updates, and linux kernel updates are happening automatically without any issues so far for me. Few days back even got a new kernel update. $ uname -a Linux vivek-dev-linux 5.10.0-1049-oem #51-Ubuntu SMP Mon Sep 27 11:01:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Workarounds Attempted - 1. Commented out all non-ubuntu external sources from /etc/apt/*.list. Then performed an apt clean + update + upgrade. But still nothing happened and the same issue remained. 2. Tried performing apt-install --reinstall base-files. But still nothing changed: $ sudo apt install --reinstall base-files Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 4 not upgraded. Need to get 60.6 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 base-files amd64 11ubuntu5.4 [60.6 kB] Fetched 60.6 kB in 1s (55.7 kB/s) (Reading database ... 191154 files and directories currently installed.) Preparing to
[Touch-packages] [Bug 1946343] Re: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
** Changed in: oem-priority Status: New => Confirmed ** Changed in: dell Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1946343 Title: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3 Status in Dell Ubuntu Project: Confirmed Status in OEM Priority Project: Confirmed Status in base-files package in Ubuntu: Invalid Bug description: Refer: https://answers.launchpad.net/ubuntu/+question/698949 I recently bought a Dell laptop with Ubuntu pre-installed in it. Looks like it came with Ubuntu 20.04.2 and OEM Linux Kernel in it. After my initial login (on October 1, 2021), the 'Software Updater' GUI prompted me for updates, which I went ahead with. However at the end of it, I noticed that I was still at 20.04.2 with Linux Kernel at 5.10.0-1045-oem. lsb_release -a --- No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1) Release:20.04 Codename: focal uname -a - Linux dev-linux 5.10.0-1045-oem #47-Ubuntu SMP Wed Aug 18 10:41:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Then I manually tried sudo apt update and sudo apt upgrade / dist- upgrade from the terminal, but nothing got upgraded. When I invoked the GUI 'Software Updater' again, it showed me that my system was already up-to-date. However, as 20.04.3 was released end of Aug 2021, I was expecting that I should be at that release after my initial updates. Since that didn't happen, I asked a question regarding this in askubuntu followed by launchpad https://answers.launchpad.net/ubuntu/+question/698949, thinking my update had failed for some unknown reason. However, based on some inputs from other users, we were able to narrow down the problem to /usr/lib/os-release file not having the right contents in it. Every other file including /usr/lib/os-release.oem- release, /etc/issue, /etc/issue.net specifies that I am on 20.04.3. Whereas only /usr/lib/os-release (and its symlink /etc/release) specifies my current release as 20.04.2. Even the lsb_release -a command always displays the output of /usr/lib/os-release file only. $ cat /usr/lib/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /usr/lib/os-release.oem-release NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /etc/issue Ubuntu 20.04.3 LTS \n \l $ cat /etc/issue.net Ubuntu 20.04.3 LTS If you look at the timestamp of these files, strangely os-release had a newer timestamp of Oct 1 compared to other files. $ ls -l /usr/lib/os-release -rw-r--r-- 1 root root 406 Oct 1 20:31 /usr/lib/os-release $ ls -l /usr/lib/os-release.oem-release -rw-r--r-- 1 root root 382 Aug 4 07:53 /usr/lib/os-release.oem-release $ ls -l /etc/issue -rw-r--r-- 1 root root 26 Aug 4 07:53 /etc/issue $ ls -l /etc/issue.net -rw-r--r-- 1 root root 19 Aug 4 07:53 /etc/issue.net Please note that, other software package updates, and linux kernel updates are happening automatically without any issues so far for me. Few days back even got a new kernel update. $ uname -a Linux vivek-dev-linux 5.10.0-1049-oem #51-Ubuntu SMP Mon Sep 27 11:01:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Workarounds Attempted - 1. Commented out all non-ubuntu external sources from /etc/apt/*.list. Then performed an apt clean + update + upgrade. But still nothing happened and the same issue remained. 2. Tried performing apt-install --reinstall base-files. But still nothing changed: $ sudo apt install --reinstall base-files Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 4 not upgraded. Need to get 60.6 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 base-files amd64 11ubuntu5.4 [60.6 kB] Fetched 60.6 kB in 1s (55.7 kB/s) (Reading database ... 191154 files and directories
[Touch-packages] [Bug 1946343] Re: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
** Changed in: dell Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1946343 Title: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3 Status in Dell Ubuntu Project: New Status in OEM Priority Project: New Status in base-files package in Ubuntu: Invalid Bug description: Refer: https://answers.launchpad.net/ubuntu/+question/698949 I recently bought a Dell laptop with Ubuntu pre-installed in it. Looks like it came with Ubuntu 20.04.2 and OEM Linux Kernel in it. After my initial login (on October 1, 2021), the 'Software Updater' GUI prompted me for updates, which I went ahead with. However at the end of it, I noticed that I was still at 20.04.2 with Linux Kernel at 5.10.0-1045-oem. lsb_release -a --- No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1) Release:20.04 Codename: focal uname -a - Linux dev-linux 5.10.0-1045-oem #47-Ubuntu SMP Wed Aug 18 10:41:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Then I manually tried sudo apt update and sudo apt upgrade / dist- upgrade from the terminal, but nothing got upgraded. When I invoked the GUI 'Software Updater' again, it showed me that my system was already up-to-date. However, as 20.04.3 was released end of Aug 2021, I was expecting that I should be at that release after my initial updates. Since that didn't happen, I asked a question regarding this in askubuntu followed by launchpad https://answers.launchpad.net/ubuntu/+question/698949, thinking my update had failed for some unknown reason. However, based on some inputs from other users, we were able to narrow down the problem to /usr/lib/os-release file not having the right contents in it. Every other file including /usr/lib/os-release.oem- release, /etc/issue, /etc/issue.net specifies that I am on 20.04.3. Whereas only /usr/lib/os-release (and its symlink /etc/release) specifies my current release as 20.04.2. Even the lsb_release -a command always displays the output of /usr/lib/os-release file only. $ cat /usr/lib/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /usr/lib/os-release.oem-release NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /etc/issue Ubuntu 20.04.3 LTS \n \l $ cat /etc/issue.net Ubuntu 20.04.3 LTS If you look at the timestamp of these files, strangely os-release had a newer timestamp of Oct 1 compared to other files. $ ls -l /usr/lib/os-release -rw-r--r-- 1 root root 406 Oct 1 20:31 /usr/lib/os-release $ ls -l /usr/lib/os-release.oem-release -rw-r--r-- 1 root root 382 Aug 4 07:53 /usr/lib/os-release.oem-release $ ls -l /etc/issue -rw-r--r-- 1 root root 26 Aug 4 07:53 /etc/issue $ ls -l /etc/issue.net -rw-r--r-- 1 root root 19 Aug 4 07:53 /etc/issue.net Please note that, other software package updates, and linux kernel updates are happening automatically without any issues so far for me. Few days back even got a new kernel update. $ uname -a Linux vivek-dev-linux 5.10.0-1049-oem #51-Ubuntu SMP Mon Sep 27 11:01:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Workarounds Attempted - 1. Commented out all non-ubuntu external sources from /etc/apt/*.list. Then performed an apt clean + update + upgrade. But still nothing happened and the same issue remained. 2. Tried performing apt-install --reinstall base-files. But still nothing changed: $ sudo apt install --reinstall base-files Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 4 not upgraded. Need to get 60.6 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 base-files amd64 11ubuntu5.4 [60.6 kB] Fetched
[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: Fix Released Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Released Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Released Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Fix Released Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1613605] Re: unity-system-compositor crashes on boot on xenial/arm64
** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1613605 Title: unity-system-compositor crashes on boot on xenial/arm64 Status in Canonical System Image: Fix Released Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Bug description: xenial/arm64/frieza channel ubuntu-touch/staging/ubuntu unity-system-compositor crashes on boot with the crash file attached According to vicamo it crashes in glibc timezone functions. It could share the same root cause than bug 1613602. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
** Changed in: oem-priority Status: Confirmed => Won't Fix ** Changed in: oem-priority Assignee: Alex Tu (alextu) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Won't Fix Status in apt package in Ubuntu: Invalid Status in nvidia-graphics-drivers-455 package in Ubuntu: Invalid Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: 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) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) 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) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
** Changed in: oem-priority Assignee: Yuan-Chen Cheng (ycheng-twn) => Alex Tu (alextu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Invalid Status in nvidia-graphics-drivers-455 package in Ubuntu: Invalid Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: 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) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) 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) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-455 package in Ubuntu: Incomplete Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: 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) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) 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) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
per quick test, we need focal/apt 2.0.5 to fix this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-455 package in Ubuntu: Incomplete Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: 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) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) 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) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
For completeness, apt pkg versions in focal are focal: 2.0.2 focal-security: 2.0.2ubuntu0.2 focal-update 2.0.5 If 2.0.2ubuntu0.2 can cover this, then we are all clear, since it will be upgraded by unattended upgrade. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-455 package in Ubuntu: Incomplete Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: 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) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) 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) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901000] Re: dmesg need permission after kernel 5.8
*** This bug is a duplicate of bug 1821415 *** https://bugs.launchpad.net/bugs/1821415 Hi Brian, I think this is not a duplicate. However, this bug seems to only exist on the early kernel. For now, the dmesg no longer needs root permission. ** Changed in: apport (Ubuntu) Status: Confirmed => Fix Released ** Changed in: apport (Ubuntu Groovy) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1901000 Title: dmesg need permission after kernel 5.8 Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in apport source package in Groovy: Fix Released Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319494] Re: Ubuntu installation image should come with mdadm
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Status: New => Fix Released ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1319494 Title: Ubuntu installation image should come with mdadm Status in OEM Priority Project: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: It would be great if the Ubuntu installation image came with mdadm. If was unlucky enough to be Internetless while installing Ubuntu, I wouldn't be able to install to or create a RAID array. I know that Ubuntu has lessened its restrictions on installation image size, and since mdadm's installed size is 1.2MB, I think it should be included. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.18.7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.340 Date: Wed May 14 17:27:51 2014 ExecutablePath: /usr/lib/ubiquity/bin/ubiquity InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity InterpreterPath: /usr/bin/python3.4 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1319494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793472] Re: [wishlist] Add mdadm into desktop by default
Intel VROC (Intel Virtual RAID on CPU) needs mdadm to install on it per OEM test result. Intel reference document like below does mention that: https://www.intel.com/content/dam/support/us/en/documents/memory-and- storage/ssd-software/Linux_VROC_6-0_User_Guide.pdf ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High ** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1793472 Title: [wishlist] Add mdadm into desktop by default Status in OEM Priority Project: New Status in ubuntu-meta package in Ubuntu: New Bug description: Consider the situation that we have OEM systems with software raid devices and the desktop image will be installed on them as primary storage. Another work is to patch casper to support md (Please refer bug #1793444). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1793472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908023] Re: Installing libgbm1 will make other packages removed
** No longer affects: hwe-next ** No longer affects: mesa (Ubuntu) ** Summary changed: - Installing libgbm1 will make other packages removed + installation stopped by an exception from mark_install() in Cache class of python3-apt ** Description changed: - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 20.04/20.04.1 + Exception in the installation - 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - libgbm1/20.0.4-2ubuntu1 libgbm1/20.0.8-0ubuntu1~20.04.1 + Aug 12 19:26:59 ubuntu /plugininstall.py: Exception during installation: + Aug 12 19:26:59 ubuntu /plugininstall.py: Traceback (most recent call last): + Aug 12 19:26:59 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 235, in run + Aug 12 19:26:59 ubuntu /plugininstall.py: self.install_extras() + Aug 12 19:26:59 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1212, in install_extras + Aug 12 19:26:59 ubuntu /plugininstall.py: self.do_install(filtered_extra_packages) + Aug 12 19:26:59 ubuntu /plugininstall.py: File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 941, in do_install + Aug 12 19:26:59 ubuntu /plugininstall.py: mark_install(cache, pkg) + Aug 12 19:26:59 ubuntu /plugininstall.py: File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 553, in mark_install + Aug 12 19:26:59 ubuntu /plugininstall.py: raise InstallStepError( + Aug 12 19:26:59 ubuntu /plugininstall.py: ubiquity.install_misc.InstallStepError: Unable to install 'libgbm1' due to conflicts. - 3) What you expected to happen - Not so many packages will be removed when executing `apt-get --yes install libgbm1`. + This happen in oem project because we have lots pkg to upgrade during + installation because the design of factory process need it. - 4) What happened instead - Executing `apt-get --yes install libgbm1` will make many other packages to be removed. + As package list have certain dependency, and the the order that we get + the pkg from the python set object is not good for underlying apt + engine, then exception will raise. ** Changed in: oem-priority Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1908023 Title: installation stopped by an exception from mark_install() in Cache class of python3-apt Status in OEM Priority Project: In Progress Bug description: Exception in the installation Aug 12 19:26:59 ubuntu /plugininstall.py: Exception during installation: Aug 12 19:26:59 ubuntu /plugininstall.py: Traceback (most recent call last): Aug 12 19:26:59 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 235, in run Aug 12 19:26:59 ubuntu /plugininstall.py: self.install_extras() Aug 12 19:26:59 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1212, in install_extras Aug 12 19:26:59 ubuntu /plugininstall.py: self.do_install(filtered_extra_packages) Aug 12 19:26:59 ubuntu /plugininstall.py: File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 941, in do_install Aug 12 19:26:59 ubuntu /plugininstall.py: mark_install(cache, pkg) Aug 12 19:26:59 ubuntu /plugininstall.py: File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 553, in mark_install Aug 12 19:26:59 ubuntu /plugininstall.py: raise InstallStepError( Aug 12 19:26:59 ubuntu /plugininstall.py: ubiquity.install_misc.InstallStepError: Unable to install 'libgbm1' due to conflicts. This happen in oem project because we have lots pkg to upgrade during installation because the design of factory process need it. As package list have certain dependency, and the the order that we get the pkg from the python set object is not good for underlying apt engine, then exception will raise. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1908023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908023] Re: Installing libgbm1 will make other packages removed
** Tags added: oem-priority originate-from-1899905 somerville -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1908023 Title: Installing libgbm1 will make other packages removed Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in mesa package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 20.04/20.04.1 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center libgbm1/20.0.4-2ubuntu1 libgbm1/20.0.8-0ubuntu1~20.04.1 3) What you expected to happen Not so many packages will be removed when executing `apt-get --yes install libgbm1`. 4) What happened instead Executing `apt-get --yes install libgbm1` will make many other packages to be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908023] Re: Installing libgbm1 will make other packages to be removed
There is such problem when using http://old- releases.ubuntu.com/releases/20.04/ubuntu-20.04-desktop-amd64.iso + focal-updates. ** Attachment added: "libgbm1.20.04+updates.log" https://bugs.launchpad.net/oem-priority/+bug/1908023/+attachment/5443334/+files/libgbm1.20.04+updates.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1908023 Title: Installing libgbm1 will make other packages removed Status in OEM Priority Project: Confirmed Status in mesa package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 20.04/20.04.1 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center libgbm1/20.0.4-2ubuntu1 libgbm1/20.0.8-0ubuntu1~20.04.1 3) What you expected to happen Not so many packages will be removed when executing `apt-get --yes install libgbm1`. 4) What happened instead Executing `apt-get --yes install libgbm1` will make many other packages to be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1908023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908023] Re: Installing libgbm1 will make other packages to be removed
There is such problem when using http://releases.ubuntu.com/releases/20.04/ubuntu-20.04.1-desktop- amd64.iso + focal-proposed. ** Attachment added: "libgbm1.20.04.1+proposed.log" https://bugs.launchpad.net/oem-priority/+bug/1908023/+attachment/5443335/+files/libgbm1.20.04.1+proposed.log ** Changed in: oem-priority Assignee: (unassigned) => Shih-Yuan Lee (fourdollars) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed ** Summary changed: - Installing libgbm1 will make other packages to be removed + Installing libgbm1 will make other packages removed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1908023 Title: Installing libgbm1 will make other packages removed Status in OEM Priority Project: Confirmed Status in mesa package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 20.04/20.04.1 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center libgbm1/20.0.4-2ubuntu1 libgbm1/20.0.8-0ubuntu1~20.04.1 3) What you expected to happen Not so many packages will be removed when executing `apt-get --yes install libgbm1`. 4) What happened instead Executing `apt-get --yes install libgbm1` will make many other packages to be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1908023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908023] Re: Installing libgbm1 will make other packages to be removed
$ sudo apt-get --dry-run install libgbm1 # There is no such problem on Ubuntu 18.04. Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: libegl-mesa0 libglapi-mesa libglx-mesa0 libwayland-client0 libwayland-server0 The following packages will be upgraded: libegl-mesa0 libgbm1 libglapi-mesa libglx-mesa0 libwayland-client0 libwayland-server0 6 upgraded, 0 newly installed, 0 to remove and 826 not upgraded. Inst libwayland-server0 [1.14.0-2] (1.16.0-1ubuntu1.1~18.04.3 Ubuntu:18.04/bionic-security, Ubuntu:18.04/bionic-updates [amd64]) Inst libegl-mesa0 [18.0.0~rc5-1ubuntu1] (20.0.8-0ubuntu1~18.04.1 Ubuntu:18.04/bionic-updates [amd64]) [] Inst libgbm1 [18.0.0~rc5-1ubuntu1] (20.0.8-0ubuntu1~18.04.1 Ubuntu:18.04/bionic-updates [amd64]) [] Inst libglx-mesa0 [18.0.0~rc5-1ubuntu1] (20.0.8-0ubuntu1~18.04.1 Ubuntu:18.04/bionic-updates [amd64]) [] Inst libglapi-mesa [18.0.0~rc5-1ubuntu1] (20.0.8-0ubuntu1~18.04.1 Ubuntu:18.04/bionic-updates [amd64]) [] Inst libwayland-client0 [1.14.0-2] (1.16.0-1ubuntu1.1~18.04.3 Ubuntu:18.04/bionic-security, Ubuntu:18.04/bionic-updates [amd64]) Conf libwayland-server0 (1.16.0-1ubuntu1.1~18.04.3 Ubuntu:18.04/bionic-security, Ubuntu:18.04/bionic-updates [amd64]) Conf libegl-mesa0 (20.0.8-0ubuntu1~18.04.1 Ubuntu:18.04/bionic-updates [amd64]) Conf libgbm1 (20.0.8-0ubuntu1~18.04.1 Ubuntu:18.04/bionic-updates [amd64]) Conf libglx-mesa0 (20.0.8-0ubuntu1~18.04.1 Ubuntu:18.04/bionic-updates [amd64]) Conf libglapi-mesa (20.0.8-0ubuntu1~18.04.1 Ubuntu:18.04/bionic-updates [amd64]) Conf libwayland-client0 (1.16.0-1ubuntu1.1~18.04.3 Ubuntu:18.04/bionic-security, Ubuntu:18.04/bionic-updates [amd64]) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1908023 Title: Installing libgbm1 will make other packages removed Status in OEM Priority Project: Confirmed Status in mesa package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 20.04/20.04.1 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center libgbm1/20.0.4-2ubuntu1 libgbm1/20.0.8-0ubuntu1~20.04.1 3) What you expected to happen Not so many packages will be removed when executing `apt-get --yes install libgbm1`. 4) What happened instead Executing `apt-get --yes install libgbm1` will make many other packages to be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1908023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908023] [NEW] Installing libgbm1 will make other packages removed
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 20.04/20.04.1 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center libgbm1/20.0.4-2ubuntu1 libgbm1/20.0.8-0ubuntu1~20.04.1 3) What you expected to happen Not so many packages will be removed when executing `apt-get --yes install libgbm1`. 4) What happened instead Executing `apt-get --yes install libgbm1` will make many other packages to be removed. ** Affects: oem-priority Importance: Critical Assignee: Shih-Yuan Lee (fourdollars) Status: Confirmed ** Affects: mesa (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 Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1908023 Title: Installing libgbm1 will make other packages removed Status in OEM Priority Project: Confirmed Status in mesa package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 20.04/20.04.1 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center libgbm1/20.0.4-2ubuntu1 libgbm1/20.0.8-0ubuntu1~20.04.1 3) What you expected to happen Not so many packages will be removed when executing `apt-get --yes install libgbm1`. 4) What happened instead Executing `apt-get --yes install libgbm1` will make many other packages to be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1908023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
It exists in queue https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=network, which is network manager 1.22.10-1ubuntu2.2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit Status in OEM Priority Project: New Status in OEM Priority Project focal series: Invalid Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Focal: In Progress Bug description: [Impact] In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager). The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. So, the management of wake-on-LAN still is done by NetworkManager. The killer 500s Wi-Fi does not want the network-manger to manager the wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set. (The driver will manager itself.) When the network-manager managers the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS resumed from suspend. [Test Case] On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. Step 1. Enter suspend (s2idle) Setp 2. Resume from suspend After resume from suspend, the Wi-Fi function still is normal. You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 [Regression Potential] * This patch modifies the wake on lan parameters, please test that the corresponding feature still works fine with the different configuration values. 1. Magic packet test: Set Wake on Wireless to off Send magic packet to the system Ensure it does not wake up Set Wake on Wirless to on Send magic packet to the system Ensure it does wake up 2. Wi-Fi function test after resumed from suspend: After resume from suspend, the Wi-Fi should work normally. Scan APs. Connect to an AP. [Other Info] * platform: add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status check (!597) · Merge Requests · NetworkManager / NetworkManager · GitLab - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/597#note_588639 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837174] Re: auto compress if save filename ends with .gz
** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1837174 Title: auto compress if save filename ends with .gz Status in Apport: Confirmed Status in OEM Priority Project: Fix Released Status in apport package in Ubuntu: Fix Released Bug description: email plain text file will be likely cause problem. gzip the save file could help lots of back and forth. Proposed to gzip the file if filename ends with ".gz". To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1837174/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893899] Re: update alsa/audio related infomation collection code in apport
** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1893899 Title: update alsa/audio related infomation collection code in apport Status in OEM Priority Project: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Groovy: Fix Released Bug description: what need to change 1. try to use /usr/sbin/alsa-info before try /usr/share/alsa-base/alsa-info.sh (weird for me that two copy of alsa-info co-exists, but anyway) 2. add pa-info (exist after focal) 3. add ucm2 directory. (exist after focal) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1888352 Title: use builtin dump_acpi_tables.py in hookutils Status in Apport: New Status in OEM Priority Project: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Status in apport source package in Groovy: Fix Released Bug description: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. To SRU to focal: [Impact] * for OEM project, lts is been used. And collect log is important. With built-in tool to get acpidump, we don't need to install extra tool in the end-customer's machine. That make it much easier for the oem process. * By call built-in utility, we no lounger need to install extra tools to collect data that's both complete and convenient for HWE people to work on. [Test Case] * before this applied, run oem-getlog without install acpidump. we can't get the dump data. After this applied, we can just dump the data HWE need. * test step: install the new package, run sudo -E oem-getlogs [-c case_id] to get the use apport-unpack to unpack the apport file. check the acpidump file. HWE people know much better on check the acpidump file. Give the dump_acpi_tables.py just updated and SRUed by HWE/ACPI/UEFI expert, it's pretty safe to do so. [Regression Potential] * Given the modification change the way to collect log, even it failed, it won't break apport itself. Just the collected log might contain data not so valid. * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they just reviewed and updated the dump_acpi_tables.py script, I believe it will have good quality. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893899] Re: update alsa/audio related infomation collection code in apport
Is there a quick and clean way to extract alsa-info from output of pa- info? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1893899 Title: update alsa/audio related infomation collection code in apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Incomplete Status in apport source package in Groovy: Incomplete Bug description: what need to change 1. try to use /usr/sbin/alsa-info before try /usr/share/alsa-base/alsa-info.sh (weird for me that two copy of alsa-info co-exists, but anyway) 2. add pa-info (exist after focal) 3. add ucm2 directory. (exist after focal) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Status: New => Fix Released ** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in OEM Priority Project: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch ucm-shuffle-code-in-compound_merge.patch
[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils
** Changed in: oem-priority Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1888352 Title: use builtin dump_acpi_tables.py in hookutils Status in Apport: New Status in OEM Priority Project: Fix Committed Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Status in apport source package in Groovy: Fix Released Bug description: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. To SRU to focal: [Impact] * for OEM project, lts is been used. And collect log is important. With built-in tool to get acpidump, we don't need to install extra tool in the end-customer's machine. That make it much easier for the oem process. * By call built-in utility, we no lounger need to install extra tools to collect data that's both complete and convenient for HWE people to work on. [Test Case] * before this applied, run oem-getlog without install acpidump. we can't get the dump data. After this applied, we can just dump the data HWE need. * test step: install the new package, run sudo -E oem-getlogs [-c case_id] to get the use apport-unpack to unpack the apport file. check the acpidump file. HWE people know much better on check the acpidump file. Give the dump_acpi_tables.py just updated and SRUed by HWE/ACPI/UEFI expert, it's pretty safe to do so. [Regression Potential] * Given the modification change the way to collect log, even it failed, it won't break apport itself. Just the collected log might contain data not so valid. * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they just reviewed and updated the dump_acpi_tables.py script, I believe it will have good quality. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils
given #14, verified done ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1888352 Title: use builtin dump_acpi_tables.py in hookutils Status in Apport: New Status in OEM Priority Project: In Progress Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Status in apport source package in Groovy: Fix Released Bug description: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. To SRU to focal: [Impact] * for OEM project, lts is been used. And collect log is important. With built-in tool to get acpidump, we don't need to install extra tool in the end-customer's machine. That make it much easier for the oem process. * By call built-in utility, we no lounger need to install extra tools to collect data that's both complete and convenient for HWE people to work on. [Test Case] * before this applied, run oem-getlog without install acpidump. we can't get the dump data. After this applied, we can just dump the data HWE need. * test step: install the new package, run sudo -E oem-getlogs [-c case_id] to get the use apport-unpack to unpack the apport file. check the acpidump file. HWE people know much better on check the acpidump file. Give the dump_acpi_tables.py just updated and SRUed by HWE/ACPI/UEFI expert, it's pretty safe to do so. [Regression Potential] * Given the modification change the way to collect log, even it failed, it won't break apport itself. Just the collected log might contain data not so valid. * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they just reviewed and updated the dump_acpi_tables.py script, I believe it will have good quality. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils
for the apport.gz, per what I know, it's all plain text after we un-gzip it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1888352 Title: use builtin dump_acpi_tables.py in hookutils Status in Apport: New Status in OEM Priority Project: In Progress Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Status in apport source package in Groovy: Fix Released Bug description: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. To SRU to focal: [Impact] * for OEM project, lts is been used. And collect log is important. With built-in tool to get acpidump, we don't need to install extra tool in the end-customer's machine. That make it much easier for the oem process. * By call built-in utility, we no lounger need to install extra tools to collect data that's both complete and convenient for HWE people to work on. [Test Case] * before this applied, run oem-getlog without install acpidump. we can't get the dump data. After this applied, we can just dump the data HWE need. * test step: install the new package, run sudo -E oem-getlogs [-c case_id] to get the use apport-unpack to unpack the apport file. check the acpidump file. HWE people know much better on check the acpidump file. Give the dump_acpi_tables.py just updated and SRUed by HWE/ACPI/UEFI expert, it's pretty safe to do so. [Regression Potential] * Given the modification change the way to collect log, even it failed, it won't break apport itself. Just the collected log might contain data not so valid. * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they just reviewed and updated the dump_acpi_tables.py script, I believe it will have good quality. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils
this is output of dump_acpi_tables.py on that machine. ** Attachment added: "dump_acpi_tables.py.log" https://bugs.launchpad.net/apport/+bug/1888352/+attachment/5408887/+files/dump_acpi_tables.py.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1888352 Title: use builtin dump_acpi_tables.py in hookutils Status in Apport: New Status in OEM Priority Project: In Progress Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Status in apport source package in Groovy: Fix Released Bug description: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. To SRU to focal: [Impact] * for OEM project, lts is been used. And collect log is important. With built-in tool to get acpidump, we don't need to install extra tool in the end-customer's machine. That make it much easier for the oem process. * By call built-in utility, we no lounger need to install extra tools to collect data that's both complete and convenient for HWE people to work on. [Test Case] * before this applied, run oem-getlog without install acpidump. we can't get the dump data. After this applied, we can just dump the data HWE need. * test step: install the new package, run sudo -E oem-getlogs [-c case_id] to get the use apport-unpack to unpack the apport file. check the acpidump file. HWE people know much better on check the acpidump file. Give the dump_acpi_tables.py just updated and SRUed by HWE/ACPI/UEFI expert, it's pretty safe to do so. [Regression Potential] * Given the modification change the way to collect log, even it failed, it won't break apport itself. Just the collected log might contain data not so valid. * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they just reviewed and updated the dump_acpi_tables.py script, I believe it will have good quality. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils
this is output of acpidump-acpica on that machine ** Attachment added: "acpidump-acpica.log" https://bugs.launchpad.net/apport/+bug/1888352/+attachment/5408884/+files/acpidump-acpica.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1888352 Title: use builtin dump_acpi_tables.py in hookutils Status in Apport: New Status in OEM Priority Project: In Progress Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Status in apport source package in Groovy: Fix Released Bug description: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. To SRU to focal: [Impact] * for OEM project, lts is been used. And collect log is important. With built-in tool to get acpidump, we don't need to install extra tool in the end-customer's machine. That make it much easier for the oem process. * By call built-in utility, we no lounger need to install extra tools to collect data that's both complete and convenient for HWE people to work on. [Test Case] * before this applied, run oem-getlog without install acpidump. we can't get the dump data. After this applied, we can just dump the data HWE need. * test step: install the new package, run sudo -E oem-getlogs [-c case_id] to get the use apport-unpack to unpack the apport file. check the acpidump file. HWE people know much better on check the acpidump file. Give the dump_acpi_tables.py just updated and SRUed by HWE/ACPI/UEFI expert, it's pretty safe to do so. [Regression Potential] * Given the modification change the way to collect log, even it failed, it won't break apport itself. Just the collected log might contain data not so valid. * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they just reviewed and updated the dump_acpi_tables.py script, I believe it will have good quality. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils
the oem-getlogs file using the apport 2.20.11-0ubuntu27.9 from the proposed channel. I am going to find uefi expert to double check ** Attachment added: "oemlogs-f1-test-20200907111510+0800.apport.gz" https://bugs.launchpad.net/oem-priority/+bug/1888352/+attachment/5408229/+files/oemlogs-f1-test-20200907111510+0800.apport.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1888352 Title: use builtin dump_acpi_tables.py in hookutils Status in Apport: New Status in OEM Priority Project: In Progress Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Status in apport source package in Groovy: Fix Released Bug description: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. To SRU to focal: [Impact] * for OEM project, lts is been used. And collect log is important. With built-in tool to get acpidump, we don't need to install extra tool in the end-customer's machine. That make it much easier for the oem process. * By call built-in utility, we no lounger need to install extra tools to collect data that's both complete and convenient for HWE people to work on. [Test Case] * before this applied, run oem-getlog without install acpidump. we can't get the dump data. After this applied, we can just dump the data HWE need. * test step: install the new package, run sudo -E oem-getlogs [-c case_id] to get the use apport-unpack to unpack the apport file. check the acpidump file. HWE people know much better on check the acpidump file. Give the dump_acpi_tables.py just updated and SRUed by HWE/ACPI/UEFI expert, it's pretty safe to do so. [Regression Potential] * Given the modification change the way to collect log, even it failed, it won't break apport itself. Just the collected log might contain data not so valid. * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they just reviewed and updated the dump_acpi_tables.py script, I believe it will have good quality. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils
** Changed in: oem-priority Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1888352 Title: use builtin dump_acpi_tables.py in hookutils Status in Apport: New Status in OEM Priority Project: In Progress Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Status in apport source package in Groovy: Fix Released Bug description: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. To SRU to focal: [Impact] * for OEM project, lts is been used. And collect log is important. With built-in tool to get acpidump, we don't need to install extra tool in the end-customer's machine. That make it much easier for the oem process. * By call built-in utility, we no lounger need to install extra tools to collect data that's both complete and convenient for HWE people to work on. [Test Case] * before this applied, run oem-getlog without install acpidump. we can't get the dump data. After this applied, we can just dump the data HWE need. * test step: install the new package, run sudo -E oem-getlogs [-c case_id] to get the use apport-unpack to unpack the apport file. check the acpidump file. HWE people know much better on check the acpidump file. Give the dump_acpi_tables.py just updated and SRUed by HWE/ACPI/UEFI expert, it's pretty safe to do so. [Regression Potential] * Given the modification change the way to collect log, even it failed, it won't break apport itself. Just the collected log might contain data not so valid. * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they just reviewed and updated the dump_acpi_tables.py script, I believe it will have good quality. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893899] Re: update alsa/audio realted infomation collection code
** Information type changed from Proprietary to Public ** Also affects: apport (Ubuntu) Importance: Undecided Status: New ** Summary changed: - update alsa/audio realted infomation collection code + update alsa/audio realted infomation collection code in apport ** Patch added: "apport-diff-groovy-audio-info-refinement.patch" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1893899/+attachment/5406852/+files/apport-diff-groovy-audio-info-refinement.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1893899 Title: update alsa/audio realted infomation collection code in apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: New Bug description: what need to change 1. try to use /usr/sbin/alsa-info before try /usr/share/alsa-base/alsa-info.sh (weird for me that two copy of alsa-info co-exists, but anyway) 2. add pa-info (exist after focal) 3. add ucm2 directory. (exist after focal) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893899] Re: update alsa/audio realted infomation collection code in apport
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1893899 Title: update alsa/audio realted infomation collection code in apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: New Bug description: what need to change 1. try to use /usr/sbin/alsa-info before try /usr/share/alsa-base/alsa-info.sh (weird for me that two copy of alsa-info co-exists, but anyway) 2. add pa-info (exist after focal) 3. add ucm2 directory. (exist after focal) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils
** Description changed: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. + + To SRU to focal: + + [Impact] + + * for OEM project, lts is been used. And collect log is important. +With built-in tool to get acpidump, we don't need to install +extra tool in the end-customer's machine. That make it much +easier for the oem process. + + * By call built-in utility, we no lounger need to install extra +tools to collect data that's both complete and convenient for +HWE people to work on. + + [Test Case] + + * before this applied, run oem-getlog without install acpidump. +we can't get the dump data. After this applied, we can just dump +the data HWE need. + + * test step: install the new package, run + +sudo -E oem-getlogs [-c case_id] to get the + +use apport-unpack to unpack the apport file. + +check the acpidump file. HWE people know much better on check +the acpidump file. Give the dump_acpi_tables.py just updated and SRUed +by HWE/ACPI/UEFI expert, it's pretty safe to do so. + + [Regression Potential] + + * Given the modification change the way to collect log, even it +failed, it won't break apport itself. Just the collected log +might contain data not so valid. + + * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they +just reviewed and updated the dump_acpi_tables.py script, I +believe it will have good quality. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1888352 Title: use builtin dump_acpi_tables.py in hookutils Status in Apport: New Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in apport source package in Groovy: Fix Released Bug description: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. To SRU to focal: [Impact] * for OEM project, lts is been used. And collect log is important. With built-in tool to get acpidump, we don't need to install extra tool in the end-customer's machine. That make it much easier for the oem process. * By call built-in utility, we no lounger need to install extra tools to collect data that's both complete and convenient for HWE people to work on. [Test Case] * before this applied, run oem-getlog without install acpidump. we can't get the dump data. After this applied, we can just dump the data HWE need. * test step: install the new package, run sudo -E oem-getlogs [-c case_id] to get the use apport-unpack to unpack the apport file. check the acpidump file. HWE people know much better on check the acpidump file. Give the dump_acpi_tables.py just updated and SRUed by HWE/ACPI/UEFI expert, it's pretty safe to do so. [Regression Potential] * Given the modification change the way to collect log, even it failed, it won't break apport itself. Just the collected log might contain data not so valid. * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they just reviewed and updated the dump_acpi_tables.py script, I believe it will have good quality. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils
please kindly also SRU it to focal, since oem project use lts mostly. I'll take responsibility to verify sru or other thing I can do. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1888352 Title: use builtin dump_acpi_tables.py in hookutils Status in Apport: New Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: In Progress Status in apport source package in Groovy: In Progress Bug description: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890772] Re: Some external 4K monitor is not working properly
** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: 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. --- 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 MachineType: Dell Inc. Vostro 5301 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1890772/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in pulseaudio source package in Bionic: Fix Released Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
on a bionic machine that's fully upgraded (proposed channel is off) The pulseaudio is still the previous version as [1]. I manually run the test, also get the same failure. The steps to run it is: 1. apt-get install ffmpeg # 7:3.4.8-0ubuntu0.2 2. apt-get source ffmpeg ; cd ffmpeg-3.4.8/debian/tests 3. mkdir tmp ; export ADTTMP=`pwd`/tmp 4. ./encdec It also have 1 failure: failures: 1 avi;v=zmbv; streamcopy return code: 1 Given above result, I believe ffmpeg have a failed test case in the first place, and it's not caused by this SRU. [1] ii libpulse-mainloop-glib0:amd64 1:11.1-1ubuntu7.9 amd64PulseAudio client libraries (glib support) ii libpulse0:amd64 1:11.1-1ubuntu7.9 amd64PulseAudio client libraries ii libpulsedsp:amd64 1:11.1-1ubuntu7.9 amd64PulseAudio OSS pre-load library ii pulseaudio1:11.1-1ubuntu7.9 amd64PulseAudio sound server ii pulseaudio-module-bluetooth 1:11.1-1ubuntu7.9 amd64Bluetooth module for PulseAudio sound server ii pulseaudio-utils 1:11.1-1ubuntu7.9 amd64Command line tools for the PulseAudio sound server -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
per https://autopkgtest.ubuntu.com/packages/ffmpeg/bionic/amd64 1. ffmpeg 7:3.4.8-0ubuntu0.2 never passed autopkgtest before. 2. ffmpeg autopkgtest also been triggered by vim and failed at the same place. above result is consistent with the fact that it's a regression by itself. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
the autopkgtests failed at "autopkgtest for ffmpeg/7:3.4.8-0ubuntu0.2" search for: "FAILED: avi;v=zmbv; streamcopy return code: 1" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
Manually download pulseaduio 1:11.1-1ubuntu7.10 and kernel 4.15.0-1093-oem into oem bionic image tested on the target that previously can reproduce this issue. In first boot, plug-in headset, and pop-up windows is properly display. After select headset, the output is correctly selected, and use the test in gnome-control-center it can properly output left/right audio. So I verified passed. ** Changed in: oem-priority Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in linux-oem package in Ubuntu: New Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882248] [NEW] plug headset won't proper reconfig ouput to it on machine with default output
Public bug reported: target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. ** Affects: oem-priority Importance: Critical Assignee: Yuan-Chen Cheng (ycheng-twn) Status: Confirmed ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: bionic oem-priority originate-1881842 somerville ** Information type changed from Proprietary to Public ** Also affects: pulseaudio Importance: Undecided Status: New ** No longer affects: pulseaudio ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags added: bionic ** Tags added: originate-1881842 ** Tags added: somerville ** Changed in: oem-priority Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882248 Title: plug headset won't proper reconfig ouput to it on machine with default output Status in OEM Priority Project: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1882248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881094] Re: Support kernel 5.4 Intel sound driver on bionic
** Merge proposal linked: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881094 Title: Support kernel 5.4 Intel sound driver on bionic Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Invalid Status in pulseaudio source package in Bionic: New Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function 1. enable Pre-released updates in Developer Options Software & Updates > Developer Options > Pre-released updates (bionic-proposed) 2. $ sudo apt update 3. $ sudo apt install linux-generic-hwe-18.04-wip 4. $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately
** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1878351 Title: System shutdown directly by pressing power button and releasing immediately Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: kchsieh@kchsieh-laptop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS (fossa-bulbasaur X23) Release: 20.04 kchsieh@kchsieh-laptop:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expect: When press the button, the endSeesionDialog should show up. Actual: The system shutdown directly. When the issue happend: endSessionDialog is not triggered immediately after the first power button event, but triggered after the second power button event. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-10 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: systemd 245.4-4ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875339] Re: xorg does not use nvidia gpu on a I+N machine.
quick check the log, there is: Is nvidia kernel module available? no However, what installed is linux-modules-nvidia-440-5.4.0-26-generic, which install the nvidia.ko to /lib/modules/5.4.0-26-generic/kernel/nvidia-440/nvidia.ko instead of the directory that gpu-manager check, which is /lib/modules/%s/updates/dkms. ** Also affects: ubuntu-drivers-common Importance: Undecided Status: New ** No longer affects: xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1875339 Title: xorg does not use nvidia gpu on a I+N machine. Status in OEM Priority Project: Confirmed Status in Ubuntu Drivers Common: New Bug description: On a machine with I+N, I install with focal 20.04 image. I didn't turn on auto-login. I checked "install 3rd party driver" during installation. It does install Nvidia driver (440.82+really.440.64-0ubuntu6). On first boot, I double check by run 'prime-select query'. It return nvidia. run nvidia-smi, no program is using NV GPU. --- $ glxinfo -B name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086) Device: Mesa Intel(R) UHD Graphics 630 (CFL GT2) (0x3e9b) Version: 20.0.4 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.0.4 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.0.4 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.0.4 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 --- Run lsmod | grep nvidia, I got: --- nvidia_uvm970752 0 nvidia_drm 49152 0 nvidia_modeset 1114112 1 nvidia_drm nvidia 20430848 8 nvidia_uvm,nvidia_modeset drm_kms_helper184320 2 nvidia_drm,i915 ipmi_msghandler 106496 2 ipmi_devintf,nvidia drm 491520 11 drm_kms_helper,nvidia_drm,i915 --- I run $ sudo prime-select intel $ sudo prime-select nvidia $ sudo reboot After reboot, nothing changed. However, previously, on the same machine, I once get it works. (nvidia-smi show some X related process use GPU, glxinfo -B show Nvidia). I remembered I create another admin account, and later on, I found it's fixed. I didn't remember what else exactly make it happened. I re-installed again, and try to do more tests, can't fix it so far. LP: #1875315 have all the log that it first fixed. --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 18:58:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a] Subsystem: Dell GP107GLM [Quadro P620] [1028:091a] InstallationDate: Installed on 2020-04-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 3541 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=8c0e264c-f63c-4d5a-b85f-6faf4008b9e6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10
[Touch-packages] [Bug 1875339] Re: xorg does not use nvidia gpu on a I+N machine.
Here it is. Feel free if you need further log. ** Attachment added: "gpu-manager.log" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875339/+attachment/5362440/+files/gpu-manager.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1875339 Title: xorg does not use nvidia gpu on a I+N machine. Status in OEM Priority Project: Confirmed Status in xorg package in Ubuntu: New Bug description: On a machine with I+N, I install with focal 20.04 image. I didn't turn on auto-login. I checked "install 3rd party driver" during installation. It does install Nvidia driver (440.82+really.440.64-0ubuntu6). On first boot, I double check by run 'prime-select query'. It return nvidia. run nvidia-smi, no program is using NV GPU. --- $ glxinfo -B name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086) Device: Mesa Intel(R) UHD Graphics 630 (CFL GT2) (0x3e9b) Version: 20.0.4 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.0.4 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.0.4 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.0.4 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 --- Run lsmod | grep nvidia, I got: --- nvidia_uvm970752 0 nvidia_drm 49152 0 nvidia_modeset 1114112 1 nvidia_drm nvidia 20430848 8 nvidia_uvm,nvidia_modeset drm_kms_helper184320 2 nvidia_drm,i915 ipmi_msghandler 106496 2 ipmi_devintf,nvidia drm 491520 11 drm_kms_helper,nvidia_drm,i915 --- I run $ sudo prime-select intel $ sudo prime-select nvidia $ sudo reboot After reboot, nothing changed. However, previously, on the same machine, I once get it works. (nvidia-smi show some X related process use GPU, glxinfo -B show Nvidia). I remembered I create another admin account, and later on, I found it's fixed. I didn't remember what else exactly make it happened. I re-installed again, and try to do more tests, can't fix it so far. LP: #1875315 have all the log that it first fixed. --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 18:58:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a] Subsystem: Dell GP107GLM [Quadro P620] [1028:091a] InstallationDate: Installed on 2020-04-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 3541 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=8c0e264c-f63c-4d5a-b85f-6faf4008b9e6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A
[Touch-packages] [Bug 1875339] Re: xorg does not use nvidia gpu on a I+N machine.
pnPrecision3541:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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 ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) ** Changed in: oem-priority Status: New => Confirmed ** Description changed: On a machine with I+N, I install with focal 20.04 image. I didn't turn on auto-login. I checked "install 3rd party driver" during installation. It does install Nvidia driver (440.82+really.440.64-0ubuntu6). On first boot, I double check by run 'prime-select query'. It return nvidia. run nvidia-smi, no program is using NV GPU. --- $ glxinfo -B name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086) Device: Mesa Intel(R) UHD Graphics 630 (CFL GT2) (0x3e9b) Version: 20.0.4 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.0.4 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.0.4 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.0.4 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 --- Run lsmod | grep nvidia, I got: --- nvidia_uvm970752 0 nvidia_drm 49152 0 nvidia_modeset 1114112 1 nvidia_drm nvidia 20430848 8 nvidia_uvm,nvidia_modeset drm_kms_helper184320 2 nvidia_drm,i915 ipmi_msghandler 106496 2 ipmi_devintf,nvidia drm 491520 11 drm_kms_helper,nvidia_drm,i915 --- I run $ sudo prime-select intel $ sudo prime-select nvidia $ sudo reboot After reboot, nothing changed. However, previously, on the same machine, I once get it works. (nvidia-smi show some X related process use GPU, glxinfo -B show Nvidia). I remembered I create another admin account, and later on, I found it's fixed. I didn't remember what else exactly make it happened. I re-installed again, and try to do more tests, can't fix it so far. + LP: #1875315 have all the log that it first fixed. --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 18:58:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a] Subsystem: Dell GP107GLM [Quadro P620] [1028:091a] InstallationDate: Installed on 2020-04-27 (0 days ago) InstallationMedi
[Touch-packages] [Bug 1875339] [NEW] on first boot and XXX, xorg does not use nvidia gpu on a I+N machine.
Public bug reported: On a machine with I+N, I install with focal 20.04 image. I didn't turn on auto-login. I check install 3d party driver during installation. It does install Nvidia driver (440.82+really.440.64-0ubuntu6). On first boot, I double check by run 'prime-select query'. It return nvidia. run nvidia-smi, no program is using NV GPU. --- $ glxinfo -B name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086) Device: Mesa Intel(R) UHD Graphics 630 (CFL GT2) (0x3e9b) Version: 20.0.4 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.0.4 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.0.4 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.0.4 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 --- Run lsmod | grep nvidia, I got: --- nvidia_uvm970752 0 nvidia_drm 49152 0 nvidia_modeset 1114112 1 nvidia_drm nvidia 20430848 8 nvidia_uvm,nvidia_modeset drm_kms_helper184320 2 nvidia_drm,i915 ipmi_msghandler 106496 2 ipmi_devintf,nvidia drm 491520 11 drm_kms_helper,nvidia_drm,i915 --- I run $ sudo prime-select intel $ sudo prime-select nvidia $ sudo reboot After reboot, nothing changed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 18:58:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a] Subsystem: Dell GP107GLM [Quadro P620] [1028:091a] InstallationDate: Installed on 2020-04-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 3541 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=8c0e264c-f63c-4d5a-b85f-6faf4008b9e6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Description changed: - This is my 2nd install. + On a machine with I+N, I install with focal 20.04 image. I didn't turn + on auto-login. I check install 3d party driver during installation. It + does install Nvidia driver (440.82+really.440.64-0ubuntu6). + + On first
[Touch-packages] [Bug 1859581] Re: land oem-getlogs in focal and enable apport-unpack to process apport.gz file
@Brain, Thanks! ** No longer affects: apport ** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1859581 Title: land oem-getlogs in focal and enable apport-unpack to process apport.gz file Status in OEM Priority Project: Fix Released Status in apport package in Ubuntu: Fix Released Bug description: LP: #1841157 seems forgeting to include oem-getlogs in debian/apport.install. Also, add the attached patch so that apport-unpack can process apport.gz that oem-getlogs generate directly. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1859581/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
** Also affects: apport (Ubuntu) Importance: Undecided Status: New ** No longer affects: apport (Ubuntu Eoan) ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed ** No longer affects: apport (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in apport source package in Focal: New Status in linux-firmware source package in Focal: In Progress Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859581] Re: land oem-getlogs in focal and enable apport-unpack to process apport.gz file
@Brain, mind also add this patch, since we found the lspci tree structure will be useful as HWE is doing certain low level pci status debugging. ** Patch added: "lspci-vt.diff" https://bugs.launchpad.net/oem-priority/+bug/1859581/+attachment/5347511/+files/lspci-vt.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1859581 Title: land oem-getlogs in focal and enable apport-unpack to process apport.gz file Status in Apport: New Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: In Progress Bug description: LP: #1841157 seems forgeting to include oem-getlogs in debian/apport.install. Also, add the attached patch so that apport-unpack can process apport.gz that oem-getlogs generate directly. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1859581/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864813] Re: As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once.
** Tags removed: focal ** Tags added: bionic ** Tags added: originate-1863700 ** Tags added: somerville -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1864813 Title: As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once. Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: The dummy output in gnome-contol-center (g-c-c) will exists if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. However, in bionic, it will disappear as the headset is plugged and selected. After it disappears, a reboot won't make it appear again. bionic: gnome-control-center: 1:3.28.2-0ubuntu0.18.04.6 pulseaudio: 1:11.1-1ubuntu7.4 In Focal, dummy output won't disappear. focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840416] Re: 2.4g wifi connection failed randomly during wpa re-key
per comment 1, the module tested is Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1840416 Title: 2.4g wifi connection failed randomly during wpa re-key Status in OEM Priority Project: Confirmed Status in network-manager package in Ubuntu: New Bug description: I'm not sure this issue caused by WIFI AP or WIFI module. From log, it looks the tested machine can not get new key from WIFI AP randomly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-1030.35-oem 4.15.18 Uname: Linux 4.15.0-1030-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 16 14:51:12 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-08-14 (2 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 IpRoute: default via 10.101.46.1 dev wlp2s0 proto dhcp metric 600 10.101.46.0/24 dev wlp2s0 proto kernel scope link src 10.101.46.198 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Canonical-2.4GHz-g f0a4469e-23e9-4899-a498-49a50b3a8e21 wifi 1565938016 廿十九年八月十六日 (週五) 十四時46分56秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/5 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 Canonical-2.4GHz-g f0a4469e-23e9-4899-a498-49a50b3a8e21 /org/freedesktop/NetworkManager/ActiveConnection/5 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1840416/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864813] Re: As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once.
bionic pactl log as just boot, after plug headset and remove headset. ** Summary changed: - As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c + As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once. ** Description changed: - There will be an dummy output in gnome-contol-center (g-c-c) if + The dummy output in gnome-contol-center (g-c-c) will exists if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. - Reprudced in bionic and focal. + However, in bionic, it will disappear as the headset is plugged and selected. + After it disappears, a reboot won't make it appear again. - In Focal, As the earphone is plugged, dummy output disappears. - As it's unplugged, it appears again. + In Focal, dummy output won't disappear. - Per test in focal: - pulseaudio 1:13.0-3ubuntu2 - gnome-control-center 1:3.35.91-0ubuntu1 + focal: + pulseaudio 1:13.0-3ubuntu2 + gnome-control-center 1:3.35.91-0ubuntu1 ** Description changed: The dummy output in gnome-contol-center (g-c-c) will exists if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. However, in bionic, it will disappear as the headset is plugged and selected. After it disappears, a reboot won't make it appear again. + bionic: + gnome-control-center: 1:3.28.2-0ubuntu0.18.04.6 + pulseaudio: 1:11.1-1ubuntu7.4 + In Focal, dummy output won't disappear. focal: - pulseaudio 1:13.0-3ubuntu2 - gnome-control-center 1:3.35.91-0ubuntu1 + pulseaudio 1:13.0-3ubuntu2 + gnome-control-center 1:3.35.91-0ubuntu1 ** Attachment added: "pactl-logs.tar" https://bugs.launchpad.net/oem-priority/+bug/1864813/+attachment/5331500/+files/pactl-logs.tar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1864813 Title: As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once. Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: The dummy output in gnome-contol-center (g-c-c) will exists if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. However, in bionic, it will disappear as the headset is plugged and selected. After it disappears, a reboot won't make it appear again. bionic: gnome-control-center: 1:3.28.2-0ubuntu0.18.04.6 pulseaudio: 1:11.1-1ubuntu7.4 In Focal, dummy output won't disappear. focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864813] Re: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c
Yes, I think I have chance to access the HW and provide details soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1864813 Title: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: There will be an dummy output in gnome-contol-center (g-c-c) if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. Reprudced in bionic and focal. In Focal, As the earphone is plugged, dummy output disappears. As it's unplugged, it appears again. Per test in focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864813] Re: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c
In bionic, the dummy output disappears in certain case and never show up again in certain cases. I do like to know which is the *corrected* behaviors so I know which one we should work on. Agree that it’s not a major bug IMHO. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1864813 Title: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: There will be an dummy output in gnome-contol-center (g-c-c) if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. Reprudced in bionic and focal. In Focal, As the earphone is plugged, dummy output disappears. As it's unplugged, it appears again. Per test in focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864813] [NEW] As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c
Public bug reported: There will be an dummy output in gnome-contol-center (g-c-c) if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. Reprudced in bionic and focal. In Focal, As the earphone is plugged, dummy output disappears. As it's unplugged, it appears again. Per test in focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 ** Affects: oem-priority Importance: Medium Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Medium ** Description changed: - There will be an dummy output if + There will be an dummy output in gnome-contol-center (g-c-c) if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. Reprudced in bionic and focal. In Focal, As the earphone is plugged, dummy output disappears. As it's unplugged, it appears again. - Per test in focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1864813 Title: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: There will be an dummy output in gnome-contol-center (g-c-c) if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. Reprudced in bionic and focal. In Focal, As the earphone is plugged, dummy output disappears. As it's unplugged, it appears again. Per test in focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847967] Re: oem kernel packages treated differently from generic kernel ones
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Released Status in apport source package in Disco: Won't Fix Status in apport source package in Eoan: Fix Released Status in apport source package in Focal: Fix Released Bug description: [SRU Justification] [Impact] When `apport-bug linux` was executed on systems with linux-oem, linux-oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. [Fix] Fix already merged in Focal: https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2724 . SRU merge proposals in: * https://code.launchpad.net/~vicamo/ubuntu/bionic/apport/bug-1847967/+merge/376380 * https://code.launchpad.net/~vicamo/ubuntu/disco/apport/bug-1847967/+merge/376381 * https://code.launchpad.net/~vicamo/ubuntu/eoan/apport/bug-1847967/+merge/374263 [Test Case] 1. Boot with linux-oem or linux-oem-osp1 kernel and try to collect apport logs with: $ apport-cli --save saved.apport linux-oem-osp1 2. Make sure the report contains PCI/ALSA/DMI/Sysfs info. [Regression Potential] Low. original bug description When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1857720] Re: apport-collect -p linux-oem-osp1 not get useful information
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1857720 Title: apport-collect -p linux-oem-osp1 not get useful information Status in OEM Priority Project: Fix Released Status in apport package in Ubuntu: Invalid Bug description: This is a test of 'apport-collect -p linux-oem-osp1' LP: #1857719 test in pc enablement tools project (apport-collect -p linux-oem-osp1) This is a test of 'apport-collect -p linux' 1857718 test in pc enablement tools project (apport-collect -p linux) looks the first one not get enough information for debugging. What package should apply to 'apport-collect -p' if I would like to report a bug for machine running linux-oem-osp1 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1857720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841157] Re: have /usr/bin/oem-getlogs in apport to collect all in one logs
** Changed in: oem-priority Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1841157 Title: have /usr/bin/oem-getlogs in apport to collect all in one logs Status in Apport: New Status in OEM Priority Project: Fix Released Status in apport package in Ubuntu: Fix Released Bug description: plan to use command like $ sudo oem-getlogs to collect all logs that oem project could need. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1841157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841157] Re: have /usr/bin/oem-getlogs in apport to collect all in one logs
for #6, create new bug LP: #1859581 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1841157 Title: have /usr/bin/oem-getlogs in apport to collect all in one logs Status in Apport: New Status in OEM Priority Project: In Progress Status in apport package in Ubuntu: Fix Released Bug description: plan to use command like $ sudo oem-getlogs to collect all logs that oem project could need. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1841157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841157] Re: have /usr/bin/oem-getlogs in apport to collect all in one logs
just found that oem-getlog is not included in focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1841157 Title: have /usr/bin/oem-getlogs in apport to collect all in one logs Status in Apport: New Status in OEM Priority Project: In Progress Status in apport package in Ubuntu: Fix Released Bug description: plan to use command like $ sudo oem-getlogs to collect all logs that oem project could need. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1841157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841157] Re: have /usr/bin/oem-getlogs in apport to collect all in one logs
just found that oem-getlogs is not listed in debian/apport.install in focal. Can we include it? In the mean time, we need the apport-unpack patch so that it can unpack apport.gz file directly. Please check attached patch. ** Patch added: "apport-unpack.patch" https://bugs.launchpad.net/oem-priority/+bug/1841157/+attachment/5320064/+files/apport-unpack.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1841157 Title: have /usr/bin/oem-getlogs in apport to collect all in one logs Status in Apport: New Status in OEM Priority Project: In Progress Status in apport package in Ubuntu: Fix Released Bug description: plan to use command like $ sudo oem-getlogs to collect all logs that oem project could need. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1841157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841157] Re: have /usr/bin/oem-getlogs in apport to collect all in one logs
add_hooks_info works, however, there seems certain limitation and something out of current design scope. For example, check source_xorg.py, there is code flow like: if is_xorg_input_package(pkg): code a else: code b If I want to get log from code a and b, I need to use code like: report.add_hooks_info(None, srcpackage='xserver-xorg-input-evdev') report.add_hooks_info(None, srcpackage='xorg') It does not really work because, the pkg will be "Unknown" because the code get the source pkg from the report object, instead of srcpackage parameter. Even it works, other code the collect log will run twice, and the will make the code run longer. (Given we potentially want to add lots of packages, the duplicate log collected will increase.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1841157 Title: have /usr/bin/oem-getlogs in apport to collect all in one logs Status in Apport: New Status in OEM Priority Project: In Progress Status in apport package in Ubuntu: Fix Released Bug description: plan to use command like $ sudo oem-getlogs to collect all logs that oem project could need. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1841157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports
** Changed in: oem-priority Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1834138 Title: PA: Don't restore the streams to sinks/sources with only unavailable ports Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Disco: Fix Released Status in pulseaudio source package in Eoan: Fix Released Bug description: SRU Document: [Impact] The Lenovo P520 machine has dual analogue codecs, so there are two sinks and two sources in the PA, one has the front headphone and front microphone, the other has the rear lineout, linein and rear microphone, and the rear microphone always shows up in the gnome- sound-setting, When we plug a microphone to front audio jack, there are two input devices: rear mic and front mic in the gnome-sound- setting, and suppose users select the the front mic to record sound via audio app like arecord, the front mic will be bond the arecord, after the front mic is unplugged, there is only one rear mic left in the gnome-sound-setting, but the binding will not be changed, the arecrod still bind to front mic, under this situation if users record sound via arecord, they will find they can't record any sound from any other input devices even they are listed in the gnome-sound-setting. This problem also happens to output devices too. [Test Case] After applying this patch, I did the same test: unplug the front mic, then use the arecord to record sound, the app can record sound from rear mic now. After I plug the front mic back, the arecord still record from front mic. Also did the similar test for output devices, it worked as expected too. [Regression Potential] Low, Just make a simple check when creating new streams (sink_input/source_output), If the restored device (sink/source) has ports and all ports are unavialble, it will not restore the binding, otherwise it will work as before. For the Bionic, This SRU also includes the fix of LP: #1556439, this fix is safe and is very low possible to introduce any regression too, because it just adds a sink-input/source-output state checking, if the sink-input/source-output is unlinking or unlinked, it is useless to move it to a new sink/source, furthermore it will trigger an assertion that make the pulseaudio crash, adding this check can fix this problem (LP: #1556439). [Other Info] No more info here To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp