[Touch-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop
This impacts all arm64 installs, not just raspberry pi. The MIR for qrtr and protection-domain-mapper [0] was requested late in the Mantic cycle and was only approved by Security since it was promised to only be used for x13s hardware enablement. Hopefully Qualcomm IPC is only enabled for x13s kernels. As noted in the qrtr MIR: > We should be cautious of IPC routers running root permissions. Similar code > has > enabled vendor backdoors [1]. Furthermore, qrtr has nearly no documentation and has no inline code comments [2]. Please remove this from the mantic and noble's ubuntu-meta package. [0] https://bugs.launchpad.net/ubuntu/+source/qrtr/+bug/2038942 [1] https://redmine.replicant.us/projects/replicant/wiki/samsunggalaxybackdoor [2] https://github.com/linux-msm/qrtr -- 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/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2063961] [NEW] Microsoft 365 account keeps disconnecting
Public bug reported: When I use the new (24.04) settings and 'Online Accounts' to connect to Microsoft 365, it authenticates, works well for about 5 minutes and then disconnects. I have to remove that account and redo it every time I want to use it. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-settings 24.04.3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 19:04:06 2024 InstallationDate: Installed on 2024-04-27 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2063961 Title: Microsoft 365 account keeps disconnecting Status in ubuntu-settings package in Ubuntu: New Bug description: When I use the new (24.04) settings and 'Online Accounts' to connect to Microsoft 365, it authenticates, works well for about 5 minutes and then disconnects. I have to remove that account and redo it every time I want to use it. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-settings 24.04.3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 19:04:06 2024 InstallationDate: Installed on 2024-04-27 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2063961/+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 2059049] [NEW] adduser allows no password when PAM's pwquality is restrictively set
Public bug reported: If pam_pwqaulity is restrictively set a user can still be created by adduser without a password. e.g., ``` eslerm@mino:~$ cat /etc/pam.d/common-password |grep pwquality password requisite pam_pwquality.so retry=3 minlen=8 maxrepeat=3 ucredit=-1 lcredit=-1 dcredit=-1 ocredit=-1 difok=3 gecoscheck=1 reject_username enforce_for_root eslerm@mino:~$ sudo adduser bar info: Adding user `bar' ... info: Selecting UID/GID from range 1000 to 5 ... info: Adding new group `bar' (1002) ... info: Adding new user `bar' (1002) with group `bar (1002)' ... info: Creating home directory `/home/bar' ... info: Copying files from `/etc/skel' ... New password: BAD PASSWORD: The password contains less than 1 digits New password: BAD PASSWORD: The password contains less than 1 digits New password: BAD PASSWORD: The password contains less than 1 digits passwd: Have exhausted maximum number of retries for service passwd: password unchanged Try again? [y/N] N Changing the user information for bar Enter the new value, or press ENTER for the default Full Name []: Room Number []: Work Phone []: Home Phone []: Other []: Is the information correct? [Y/n] info: Adding new user `bar' to supplemental / extra groups `users' ... info: Adding user `bar' to group `users' ... eslerm@mino:~$ sudo cat /etc/shadow|grep bar bar:!:19802:0:9:7::: ``` This was raised as an issue to the Security team. Foundations suggested to file a bug. This is possibly only a feature request. If this behavior is unexpected by the maintainers, it is likely a security issue. I am leaning towards this being a feature request and not marking the bug for Public/Private Security. ** Affects: adduser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/2059049 Title: adduser allows no password when PAM's pwquality is restrictively set Status in adduser package in Ubuntu: New Bug description: If pam_pwqaulity is restrictively set a user can still be created by adduser without a password. e.g., ``` eslerm@mino:~$ cat /etc/pam.d/common-password |grep pwquality password requisite pam_pwquality.so retry=3 minlen=8 maxrepeat=3 ucredit=-1 lcredit=-1 dcredit=-1 ocredit=-1 difok=3 gecoscheck=1 reject_username enforce_for_root eslerm@mino:~$ sudo adduser bar info: Adding user `bar' ... info: Selecting UID/GID from range 1000 to 5 ... info: Adding new group `bar' (1002) ... info: Adding new user `bar' (1002) with group `bar (1002)' ... info: Creating home directory `/home/bar' ... info: Copying files from `/etc/skel' ... New password: BAD PASSWORD: The password contains less than 1 digits New password: BAD PASSWORD: The password contains less than 1 digits New password: BAD PASSWORD: The password contains less than 1 digits passwd: Have exhausted maximum number of retries for service passwd: password unchanged Try again? [y/N] N Changing the user information for bar Enter the new value, or press ENTER for the default Full Name []: Room Number []: Work Phone []: Home Phone []: Other []: Is the information correct? [Y/n] info: Adding new user `bar' to supplemental / extra groups `users' ... info: Adding user `bar' to group `users' ... eslerm@mino:~$ sudo cat /etc/shadow|grep bar bar:!:19802:0:9:7::: ``` This was raised as an issue to the Security team. Foundations suggested to file a bug. This is possibly only a feature request. If this behavior is unexpected by the maintainers, it is likely a security issue. I am leaning towards this being a feature request and not marking the bug for Public/Private Security. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2059049/+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 2059048] [NEW] adduser allows no password when PAM's pwquality is restrictively set
Public bug reported: If pam_pwqaulity is restrictively set a user can still be created by adduser without a password. e.g., ``` eslerm@mino:~$ cat /etc/pam.d/common-password |grep pwquality password requisite pam_pwquality.so retry=3 minlen=8 maxrepeat=3 ucredit=-1 lcredit=-1 dcredit=-1 ocredit=-1 difok=3 gecoscheck=1 reject_username enforce_for_root eslerm@mino:~$ sudo adduser bar info: Adding user `bar' ... info: Selecting UID/GID from range 1000 to 5 ... info: Adding new group `bar' (1002) ... info: Adding new user `bar' (1002) with group `bar (1002)' ... info: Creating home directory `/home/bar' ... info: Copying files from `/etc/skel' ... New password: BAD PASSWORD: The password contains less than 1 digits New password: BAD PASSWORD: The password contains less than 1 digits New password: BAD PASSWORD: The password contains less than 1 digits passwd: Have exhausted maximum number of retries for service passwd: password unchanged Try again? [y/N] N Changing the user information for bar Enter the new value, or press ENTER for the default Full Name []: Room Number []: Work Phone []: Home Phone []: Other []: Is the information correct? [Y/n] info: Adding new user `bar' to supplemental / extra groups `users' ... info: Adding user `bar' to group `users' ... eslerm@mino:~$ sudo cat /etc/shadow|grep bar bar:!:19802:0:9:7::: ``` This was raised as an issue to the Security team. Foundations suggested to file a bug. This is possibly only a feature request. If this behavior is unexpected by the maintainers, it is likely a security issue. I am leaning towards this being a feature request and not marking the bug for Public/Private Security. ** Affects: adduser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/2059048 Title: adduser allows no password when PAM's pwquality is restrictively set Status in adduser package in Ubuntu: New Bug description: If pam_pwqaulity is restrictively set a user can still be created by adduser without a password. e.g., ``` eslerm@mino:~$ cat /etc/pam.d/common-password |grep pwquality password requisite pam_pwquality.so retry=3 minlen=8 maxrepeat=3 ucredit=-1 lcredit=-1 dcredit=-1 ocredit=-1 difok=3 gecoscheck=1 reject_username enforce_for_root eslerm@mino:~$ sudo adduser bar info: Adding user `bar' ... info: Selecting UID/GID from range 1000 to 5 ... info: Adding new group `bar' (1002) ... info: Adding new user `bar' (1002) with group `bar (1002)' ... info: Creating home directory `/home/bar' ... info: Copying files from `/etc/skel' ... New password: BAD PASSWORD: The password contains less than 1 digits New password: BAD PASSWORD: The password contains less than 1 digits New password: BAD PASSWORD: The password contains less than 1 digits passwd: Have exhausted maximum number of retries for service passwd: password unchanged Try again? [y/N] N Changing the user information for bar Enter the new value, or press ENTER for the default Full Name []: Room Number []: Work Phone []: Home Phone []: Other []: Is the information correct? [Y/n] info: Adding new user `bar' to supplemental / extra groups `users' ... info: Adding user `bar' to group `users' ... eslerm@mino:~$ sudo cat /etc/shadow|grep bar bar:!:19802:0:9:7::: ``` This was raised as an issue to the Security team. Foundations suggested to file a bug. This is possibly only a feature request. If this behavior is unexpected by the maintainers, it is likely a security issue. I am leaning towards this being a feature request and not marking the bug for Public/Private Security. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2059048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10
I eventually figured out that the control bar for my external speaker had been turned off somehow in the process. I turned it on and it has worked fine since. On Thursday, February 29, 2024 at 07:46:16 AM EST, Pablo Fontoura <2043...@bugs.launchpad.net> wrote: Same thing here. Fresh 23.10 installation and no sound. My USB headset is working properly. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq: owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043524/+subscriptions -- 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/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq:owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage
[Touch-packages] [Bug 2054977] [NEW] systemd-networkd fails to renew DHCP v4 lease when renew attempt times out
Public bug reported: I'm seeing exactly what this gist describes: https://gist.github.com/raggi/1f8d0b9f45c5b62e7131b03e6e2ffe68 Summary: 1. Configure a machine with a DHCPv4 lease on a network with a DHCPv4 server. 2. Place machine under unusual load sufficient to cause a timeout on netlink requests. 3. Observe the interface failing with the following logs: systemd-networkd[139370]: eth0: Could not set DHCPv4 address: Connection timed out systemd-networkd[139370]: eth0: Failed The error seems to come from here: https://github.com/systemd/systemd/blob/v245.4/src/network/networkd-dhcp4.c#L781 Expected behavior The DHCPv4 client should retry the lease refresh when the issue is a timeout, eventually succeeding in these scenarios. Actual behavior Permanent loss of connectivity on the affected interface. Additional info: $ lsb_release -rd Description:Ubuntu 20.04.6 LTS Release:20.04 $ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.23 Candidate: 245.4-4ubuntu3.23 Version table: *** 245.4-4ubuntu3.23 500 500 http://ap-southeast-2.ec2.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 mirror+file:/etc/apt/source-mirrors.txt focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3.20 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 mirror+file:/etc/apt/source-mirrors.txt focal-security/main amd64 Packages 245.4-4ubuntu3 500 500 http://ap-southeast-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 mirror+file:/etc/apt/source-mirrors.txt focal/main amd64 Packages ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: dhcp systemd systemd-networkd -- 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/2054977 Title: systemd-networkd fails to renew DHCP v4 lease when renew attempt times out Status in systemd package in Ubuntu: New Bug description: I'm seeing exactly what this gist describes: https://gist.github.com/raggi/1f8d0b9f45c5b62e7131b03e6e2ffe68 Summary: 1. Configure a machine with a DHCPv4 lease on a network with a DHCPv4 server. 2. Place machine under unusual load sufficient to cause a timeout on netlink requests. 3. Observe the interface failing with the following logs: systemd-networkd[139370]: eth0: Could not set DHCPv4 address: Connection timed out systemd-networkd[139370]: eth0: Failed The error seems to come from here: https://github.com/systemd/systemd/blob/v245.4/src/network/networkd-dhcp4.c#L781 Expected behavior The DHCPv4 client should retry the lease refresh when the issue is a timeout, eventually succeeding in these scenarios. Actual behavior Permanent loss of connectivity on the affected interface. Additional info: $ lsb_release -rd Description:Ubuntu 20.04.6 LTS Release:20.04 $ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.23 Candidate: 245.4-4ubuntu3.23 Version table: *** 245.4-4ubuntu3.23 500 500 http://ap-southeast-2.ec2.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 mirror+file:/etc/apt/source-mirrors.txt focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3.20 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 mirror+file:/etc/apt/source-mirrors.txt focal-security/main amd64 Packages 245.4-4ubuntu3 500 500 http://ap-southeast-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 mirror+file:/etc/apt/source-mirrors.txt focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2054977/+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 2045931] Re: ps3 sixasis controller request pin to connect to bt
Regardless of how the bluetooth device works, enabling unbonded devices in BlueZ makes a computer vulnerable to CVE-2023-45866. It won't be enabled by the security team. Perhaps GNOME or other desktops could become more aware of gaming controllers with these issues to make pairing easier, without needing to open a terminal. If there are feature requests for this, please link them in this bug for others. -- 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/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Won't Fix Bug description: [ Workaround ] 1. Set ClassicBondedOnly=false in /etc/bluetooth/input.conf 2. Run: systemctl restart bluetooth # or reboot [ Original Description ] Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 2046857] [NEW] package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit statu
*** This bug is a duplicate of bug 2046856 *** https://bugs.launchpad.net/bugs/2046856 Public bug reported: Duplicate of 2046856 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: systemd-resolved 252.5-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: configdrive CloudName: configdrive CloudPlatform: configdrive CloudSerial: 20221022 CloudSubPlatform: config-disk (/dev/vdb) Date: Tue Dec 19 01:56:08 2023 DpkgTerminalLog: Setting up systemd-resolved (252.5-2ubuntu3) ... Converting /etc/resolv.conf to a symlink to /run/systemd/resolve/stub-resolv.conf... cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file dpkg: error processing package systemd-resolved (--configure): installed systemd-resolved package post-installation script subprocess returned error exit status 1 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: systemd Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-12-19 (0 days ago) mtime.conffile..etc.systemd.resolved.conf: 2023-08-25T21:57:40.440350 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cloud-image lunar need-duplicate-check ** This bug has been marked a duplicate of bug 2046856 package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 -- 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/2046857 Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Duplicate of 2046856 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: systemd-resolved 252.5-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: configdrive CloudName: configdrive CloudPlatform: configdrive CloudSerial: 20221022 CloudSubPlatform: config-disk (/dev/vdb) Date: Tue Dec 19 01:56:08 2023 DpkgTerminalLog: Setting up systemd-resolved (252.5-2ubuntu3) ... Converting /etc/resolv.conf to a symlink to /run/systemd/resolve/stub-resolv.conf... cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file dpkg: error processing package systemd-resolved (--configure): installed systemd-resolved package post-installation script subprocess returned error exit status 1 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: systemd Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-12-19 (0 days ago) mtime.conffile..etc.systemd.resolved.conf: 2023-08-25T21:57:40.440350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046857/+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 2046856] [NEW] package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit statu
Public bug reported: Issue in upgrade of version, more details to be added ProblemType: Package DistroRelease: Ubuntu 23.04 Package: systemd-resolved 252.5-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: configdrive CloudName: configdrive CloudPlatform: configdrive CloudSerial: 20221022 CloudSubPlatform: config-disk (/dev/vdb) Date: Tue Dec 19 01:45:42 2023 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: systemd Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-12-19 (0 days ago) mtime.conffile..etc.systemd.resolved.conf: 2023-08-25T21:57:40.440350 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cloud-image lunar need-duplicate-check -- 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/2046856 Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Issue in upgrade of version, more details to be added ProblemType: Package DistroRelease: Ubuntu 23.04 Package: systemd-resolved 252.5-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: configdrive CloudName: configdrive CloudPlatform: configdrive CloudSerial: 20221022 CloudSubPlatform: config-disk (/dev/vdb) Date: Tue Dec 19 01:45:42 2023 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: systemd Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-12-19 (0 days ago) mtime.conffile..etc.systemd.resolved.conf: 2023-08-25T21:57:40.440350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046856/+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 2046116] Re: bluetooth device connected but not recognised as output device
hi @werdem o/ What bluetooth device are you using? Your version of BlueZ has a security patch for vulnerability CVE-2023-45866 which disables support for certain legacy bluetooth devices. If your device does not support Classic Bonding, you can re-enable it by setting `ClassicBondedOnly=false` in `/etc/bluetooth/input.conf`, and then running `systemctl restart bluetooth`. More info in https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/comments/6 Please let me know if that enables your device. Keep in mind that enabling legacy devices enables the exploit. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45866 -- 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/2046116 Title: bluetooth device connected but not recognised as output device Status in bluez package in Ubuntu: New Bug description: bluetooth device connected but not recognised as output device ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 15:28:00 2023 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 81EK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=6f698382-a806-46af-9a4b-472e96795c6f ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2018 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: 7QCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 530-14IKB dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvr7QCN28WW:bd08/02/2018:br1.28:efr1.28:svnLENOVO:pn81EK:pvrLenovoYOGA530-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA530-14IKB:skuLENOVO_MT_81EK_BU_idea_FM_YOGA530-14IKB: dmi.product.family: YOGA 530-14IKB dmi.product.name: 81EK dmi.product.sku: LENOVO_MT_81EK_BU_idea_FM_YOGA 530-14IKB dmi.product.version: Lenovo YOGA 530-14IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 0C:54:15:91:FA:4F ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:83770 acl:295 sco:0 events:4208 errors:0 TX bytes:879445 acl:1667 sco:0 commands:1184 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2046116/+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 2045931] Re: ps3 sixasis controller request pin to connect to bt
Hello all o/ This is intentional. And easy to reverse. The patch for CVE-2023-45866 works as intended and is not a regression. https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/profiles/input?id=25a471a83e02e1effb15d5a488b3f0085eaeb675 If ClassicBondedOnly is not enforced, a nearby attacker can create a HID (like a keyboard and mouse) on the victims PC when bluetooth is discoverable. An HID can be used as a keyloggers or, of course, give direct control of the session. The CVE reporter has discussed this further on https://github.com/skysafe/reblog/tree/main/cve-2023-45866 And a talk and PoC release is forthcoming. Fortunately, it is easy to enable legacy devices by setting `ClassicBondedOnly=false` in `/etc/bluetooth/input.conf`, and then running `systemctl restart bluetooth`. I ver ified that a PS3 controller works well after this :) All other distros *should* be fixing this CVE. I would love it if bloggers in the Linux gaming sphere could raise awareness about this CVE and share how to enable legacy bluetooth device support. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45866 ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: bluez (Ubuntu) Assignee: Nishit Majithia (0xnishit) => Mark Esler (eslerm) -- 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/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Won't Fix Bug description: Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 2045855] Re: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt
hi @yudamjoo o/ Please check the end of your `DpkgTerminalLog.txt` file. To fix CVE-2023-45866 [0] a configuration file (`/etc/bluetooth/input.conf`) was changed. If there had been edits made to this file before updating BlueZ, apt will ask what you want to do with the configuration file. "Y" is likely the right option if you do not intend to have custom changes in `/etc/bluetooth/input.conf`. Here's an example of me asking apt to show the config differences ("D") before accepting the new changes ("Y"): ``` $ sudo apt install bluez Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be upgraded: bluez 1 upgraded, 0 newly installed, 0 to remove and 157 not upgraded. Need to get 1,106 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 https://redacted.launchpadcontent.net/ubuntu-security/ppa/ubuntu jammy/main amd64 bluez amd64 5.64-0ubuntu1.1 [1,106 kB] Fetched 1,106 kB in 1s (884 kB/s) (Reading database ... 161840 files and directories currently installed.) Preparing to unpack .../bluez_5.64-0ubuntu1.1_amd64.deb ... Unpacking bluez (5.64-0ubuntu1.1) over (5.64-0ubuntu1) ... Setting up bluez (5.64-0ubuntu1.1) ... Configuration file '/etc/bluetooth/input.conf' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** input.conf (Y/I/N/O/D/Z) [default=N] ? D --- /etc/bluetooth/input.conf 2023-03-21 08:04:20.023928226 -0500 +++ /etc/bluetooth/input.conf.dpkg-new 2023-11-29 05:31:28.0 -0600 @@ -17,8 +17,8 @@ # platforms may want to make sure that input connections only come from bonded # device connections. Several older mice have been known for not supporting # pairing/encryption. -# Defaults to false to maximize device compatibility. -ClassicBondedOnly=true +# Defaults to true for security. +#ClassicBondedOnly=true # LE upgrade security # Enables upgrades of security automatically if required. Configuration file '/etc/bluetooth/input.conf' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** input.conf (Y/I/N/O/D/Z) [default=N] ? Y Installing new version of config file /etc/bluetooth/input.conf ... Processing triggers for man-db (2.10.2-1) ... Processing triggers for dbus (1.12.20-2ubuntu4.1) ... ``` [0] https://ubuntu.com/security/notices/USN-6540-1 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45866 ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045855 Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt Status in bluez package in Ubuntu: New Bug description: I did not recognized the error. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: bluez:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Dec 7 15:44:57 2023 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2021-01-30 (1040 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. OptiPlex 7010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=1aa27b2f-8d22-4b4e-931f-bd8e304ed0d4 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: bluez Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to jammy on 2023-03-28 (253 days ago) dmi.bios.date: 03/25/2013 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0GY6Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6
Re: [Touch-packages] [Bug 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10
Thanks for your response, Piotr. I tried that, but wasn't given the option for "Play HiFi quality Music". Pro Audio was the only option in the drop down menu. There were some Analog Stereo options, but they were all unplugged and unavailable. Any other suggestions? On Wednesday, November 15, 2023 at 07:20:25 AM EST, Piotr Kowalczyk <2043...@bugs.launchpad.net> wrote: I had same issue. I managed to fix it with pavucontrol (in "configuration" tab I changed Profile to "Play HiFi quality Music" (earlier it was "Pro Audio"). -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: New Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq: owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043524/+subscriptions -- 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/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: New Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq:owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
[Touch-packages] [Bug 2043524] [NEW] audio disappeared after upgrade to Ubuntu 23.10
Public bug reported: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq:owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- 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/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: New Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq:owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043524/+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 2041694] [NEW] PAC -mbranch-protection causes seg faults and misbuilds
Public bug reported: In mantic, -mbranch-protection=standard is now a default dpkg compiler flag for arm64 [0]. This breaks libunwind and dependencies [1]. This has not affected any libunwind binaries, since rebuilds have not been performed since this change. >From local testing, the build will complete successfully, but tests will report seg faults. Please make test failures cause FTBFS. [0] https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2040518 [1] https://github.com/libunwind/libunwind/issues/647 ** Affects: libunwind (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/2041694 Title: PAC -mbranch-protection causes seg faults and misbuilds Status in libunwind package in Ubuntu: New Bug description: In mantic, -mbranch-protection=standard is now a default dpkg compiler flag for arm64 [0]. This breaks libunwind and dependencies [1]. This has not affected any libunwind binaries, since rebuilds have not been performed since this change. From local testing, the build will complete successfully, but tests will report seg faults. Please make test failures cause FTBFS. [0] https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2040518 [1] https://github.com/libunwind/libunwind/issues/647 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2041694/+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 2038365] Re: Audio
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2038365 Title: Audio Status in pulseaudio package in Ubuntu: New Bug description: Hi, I edited the daemon.conf file in Kubuntu 22.04, to have the quality of 50hz, in the hz part, float32le in the format, and src-sinc-best-quality. and when I updated it to 23.04 wayland, in the sound tab within the apport-bug, it appeared that pulseaudio was crashed. The sound is very low in distribution, you need to increase the volume a lot to have a loud sound, since kubuntu 22.04. When compared to Windows 11, it needs twice the volume. Example: Windows 11 is at 34%, in Kubuntu it needs to be at 72% or more. I also use the option to reach 150% on the volume bar. Even without changes to daemon.conf, the sound is low. I believe that improvements in hardware acceleration in general (GPU, audio, internet, etc.), across the entire distribution, will improve everything. Leaving hardware acceleration in general as the default, to gain performance. Thank you very much in advance. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pulseaudio 1:16.1+ dfsg1-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: PID USER ACCESS COMMAND /dev/snd/ controlC0: leandro 1571 F pipewire leandro 1577 F wireplumber /dev/snd/seq: leandro 1571 F pipewire CasperMD5CheckR result: unknown CurrentDesktop: KDE Date: Tuesday, October 3 14:35:56 2023 Installation date: installed on 2023/09/21 (12 days ago) Installation media: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Version amd64 (20230807.1) ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE= pt_BR:pt:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: Command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Updated to lunar on 9/25/2023 (7 days ago) dmi.bios.date: 12/06/2023 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios .version: GGCN55WW dmi.board. asset.tag: NO asset tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76466 WIN dmi.chassis. asset.tag: NO Asset tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis. version: IdeaPad 3 15ITL6 dmi.ec. firmware. release: 1.55 dmi.modalias: dmi:bvnLENOVO: bvrGGCN55WW: bd06/12/ 2023:br1. 55: efr1. 55:svnLENOVO: pn82MD: pvrIdeaPad315IT L6:rvnLENOVO: rnLNVNB161216: rvrSDK0T76466WI N:cvnLENOVO: ct10:cvrIdeaPad 315ITL6: skuLENOVO_ MT_82MD_ BU_idea_ FM_IdeaPad 31 5TIL6: dmi.product.family: IdeaPad 3 15ITL6 dmi.product.name: 82MD dmi.product.sku: LENOVO_ MT_82MD_ BU_idea_ FM_IdeaPad 3 15ITL6 dmi.product. version: IdeaPad 3 15ITL6 dmi.sys.vendor: LENOVO modified. conffile. .etc.pulse. daemon. conf: [modified] mtime.conffile. .etc.pulse. daemon. conf: 2023-09-21T21 :48: 25.302234 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2038365/+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 2029930] Re: wget crash when printing download rate
@halfgaar, I've requested that the Foundation's team review the priority of this bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/2029930 Title: wget crash when printing download rate Status in wget package in Ubuntu: Confirmed Status in wget package in Debian: Confirmed Bug description: All supported versions of Ubuntu suffer from crashes in wget in printing of the download speed. I've been getting this on various servers. It's been fixed upstream and should probably be included in 'updates' of all supported Ubuntu versions. https://git.savannah.gnu.org/git/wget.git Commit 04ab35666997fbb3cd5d72497415fb3dfd62dcc5 https://lists.gnu.org/archive/html/bug-wget/2023-08/msg1.html Patch attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2029930/+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 2035220] Re: cve-2023-4863
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/2035220 Title: cve-2023-4863 Status in chromium-browser package in Ubuntu: New Status in libwebp package in Ubuntu: New Status in chromium package in Debian: New Status in libwebp package in Debian: New Bug description: [$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at The University of Torontoʼs Munk School on 2023-09-06 https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html high profile remote vulnerability themusicgod1@eva1:~$ apt-cache policy chromium-browser chromium-browser: Installed: 1:85.0.4183.83-0ubuntu2.22.04.1 Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1 Version table: current available snap: chromium 116.0.5845.179 fix is in: chromium 116.0.5845.187 ubuntu: 22.04.3 LTS jammy ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 08:38:06 2023 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/sda2 ext4 228G 162G 55G 75% / tmpfs tmpfs 3.9G 66M 3.8G 2% /dev/shm /dev/sda2 ext4 228G 162G 55G 75% / InstallationDate: Installed on 2017-04-18 (2337 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: MSI MS-7994 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179 (17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745}) Snap.ChromiumVersion: Chromium 116.0.5845.179 snap SourcePackage: chromium-browser UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago) dmi.bios.date: 12/16/2016 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.80 dmi.board.asset.tag: Default string dmi.board.name: H110M GAMING (MS-7994) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7994 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035220/+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 2023463] [NEW] Cannot remove items from side panel
Public bug reported: Only an annoying bug I cannot remove the attached from my menu on the side panel. Other items are removed ok. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 14:22:20 2023 DistUpgraded: 2023-05-30 14:55:36,989 DEBUG /openCache(), new cache size 74014 DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:100c] InstallationDate: Installed on 2023-02-08 (123 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Aspire F5-572 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=d5663606-7967-4f64-9bf3-a8843f95c2b6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-05-30 (11 days ago) dmi.bios.date: 05/25/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Zoro_SL dmi.board.vendor: Acer dmi.board.version: V1.18 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.18:bd05/25/2017:br0.0:efr2.70:svnAcer:pnAspireF5-572:pvrV1.18:rvnAcer:rnZoro_SL:rvrV1.18:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireF5-572_100C_1.18: dmi.product.family: SKL dmi.product.name: Aspire F5-572 dmi.product.sku: Aspire F5-572_100C_1.18 dmi.product.version: V1.18 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic 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/2023463 Title: Cannot remove items from side panel Status in xorg package in Ubuntu: New Bug description: Only an annoying bug I cannot remove the attached from my menu on the side panel. Other items are removed ok. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 14:22:20 2023 DistUpgraded: 2023-05-30 14:55:36,989 DEBUG /openCache(), new cache size 74014 DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:100c] InstallationDate: Installed on 2023-02-08 (123 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Aspire F5-572 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=d5663606-7967-4f64-9bf3-a8843f95c2b6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-05-30 (11 days ago) dmi.bios.date: 05/25/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Zoro_SL dmi.board.vendor: Acer dmi.board.version: V1.18 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.18:bd05/25/2017:br0.0:efr2.70:svnAcer:pnAspireF5-572:pvrV1.18:rvnAcer:rnZoro_SL:rvrV1.18:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireF5-572_100C_1.18: dmi.product.family: SKL dmi.product.name: Aspire F5-572 dmi.product.sku: Aspire F5-572_100C_1.18 dmi.product.version: V1.18 dmi.sys.vendor: Acer
[Touch-packages] [Bug 2011313] [NEW] Ubuntu-Settings crashes after launch
Public bug reported: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2011313 Title: Ubuntu-Settings crashes after launch Status in ubuntu-settings package in Ubuntu: New Bug description: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2011313/+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 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04
I'm having similar issues. Following what Fabio mentioned, I think I had a firewall issue but disabling the firewall was not enough, I needed to restart the wifi after disabling the firewall. I guess that is the sequence which addresses the problem for Fabio too. -- 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/1971538 Title: My machine has Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+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 2003903] Re: [BPO] openssl/3.0.5-2ubuntu2 from kinetic
Thomas and Marc, thanks for the guidance and time spent here. :) I'll look into the SRU process. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2003903 Title: [BPO] openssl/3.0.5-2ubuntu2 from kinetic Status in openssl package in Ubuntu: Won't Fix Bug description: Humbly requesting backporting OpenSSL 3.0.5-2ubuntu2 from kinetic to jammy. [Impact] From the OpenSSL 3.0 migration guide: (https://www.openssl.org/docs/man3.0/man7/migration_guide.html) "Secure renegotiation is now required by default for TLS connections Support for RFC 5746 secure renegotiation is now required by default for SSL or TLS connections to succeed. Applications that require the ability to connect to legacy peers will need to explicitly set SSL_OP_LEGACY_SERVER_CONNECT. Accordingly, SSL_OP_LEGACY_SERVER_CONNECT is no longer set as part of SSL_OP_ALL." OpenSSL 3.0.2 doesn't allow you to enable UnsafeLegacyServerConnect in the openssl.cnf file. The OpenSSL team documented this option but forgot to implement it (https://github.com/openssl/openssl/pull/18296). Users are recommending enabling UnsafeLegacyRenegotiation (see https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/comments/32) (see more examples in "Other Info") When this is enabled, it makes OpenSSL 3 less secure than 1.1.1 (which is what the previous LTS, Focal, uses). Backporting the newer OpenSSL 3.0.5 would allow users to enable UnsafeLegacyConnect, while keeping UnsafeLegacyRenegotiation disabled. [Scope] Backport OpenSSL 3.0.5-2ubuntu2 from kinetic Backport to jammy [Other Info] Other places where users are recommending enabling UnsafeLegacyRenegotiation: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834/comments/6 https://ubuntuforums.org/showthread.php?t=2474436=14094091#post14094091 https://www.reddit.com/r/Ubuntu/comments/ufalf4/cannot_connect_to_eduroam_since_2204_update/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2003903/+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 2003903] [NEW] [BPO] openssl/3.0.5-2ubuntu2 from kinetic
Public bug reported: Humbly requesting backporting OpenSSL 3.0.5-2ubuntu2 from kinetic to jammy. [Impact] >From the OpenSSL 3.0 migration guide: (https://www.openssl.org/docs/man3.0/man7/migration_guide.html) "Secure renegotiation is now required by default for TLS connections Support for RFC 5746 secure renegotiation is now required by default for SSL or TLS connections to succeed. Applications that require the ability to connect to legacy peers will need to explicitly set SSL_OP_LEGACY_SERVER_CONNECT. Accordingly, SSL_OP_LEGACY_SERVER_CONNECT is no longer set as part of SSL_OP_ALL." OpenSSL 3.0.2 doesn't allow you to enable UnsafeLegacyServerConnect in the openssl.cnf file. The OpenSSL team documented this option but forgot to implement it (https://github.com/openssl/openssl/pull/18296). Users are recommending enabling UnsafeLegacyRenegotiation (see https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/comments/32) (see more examples in "Other Info") When this is enabled, it makes OpenSSL 3 less secure than 1.1.1 (which is what the previous LTS, Focal, uses). Backporting the newer OpenSSL 3.0.5 would allow users to enable UnsafeLegacyConnect, while keeping UnsafeLegacyRenegotiation disabled. [Scope] Backport OpenSSL 3.0.5-2ubuntu2 from kinetic Backport to jammy [Other Info] Other places where users are recommending enabling UnsafeLegacyRenegotiation: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834/comments/6 https://ubuntuforums.org/showthread.php?t=2474436=14094091#post14094091 https://www.reddit.com/r/Ubuntu/comments/ufalf4/cannot_connect_to_eduroam_since_2204_update/ ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2003903 Title: [BPO] openssl/3.0.5-2ubuntu2 from kinetic Status in openssl package in Ubuntu: New Bug description: Humbly requesting backporting OpenSSL 3.0.5-2ubuntu2 from kinetic to jammy. [Impact] From the OpenSSL 3.0 migration guide: (https://www.openssl.org/docs/man3.0/man7/migration_guide.html) "Secure renegotiation is now required by default for TLS connections Support for RFC 5746 secure renegotiation is now required by default for SSL or TLS connections to succeed. Applications that require the ability to connect to legacy peers will need to explicitly set SSL_OP_LEGACY_SERVER_CONNECT. Accordingly, SSL_OP_LEGACY_SERVER_CONNECT is no longer set as part of SSL_OP_ALL." OpenSSL 3.0.2 doesn't allow you to enable UnsafeLegacyServerConnect in the openssl.cnf file. The OpenSSL team documented this option but forgot to implement it (https://github.com/openssl/openssl/pull/18296). Users are recommending enabling UnsafeLegacyRenegotiation (see https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/comments/32) (see more examples in "Other Info") When this is enabled, it makes OpenSSL 3 less secure than 1.1.1 (which is what the previous LTS, Focal, uses). Backporting the newer OpenSSL 3.0.5 would allow users to enable UnsafeLegacyConnect, while keeping UnsafeLegacyRenegotiation disabled. [Scope] Backport OpenSSL 3.0.5-2ubuntu2 from kinetic Backport to jammy [Other Info] Other places where users are recommending enabling UnsafeLegacyRenegotiation: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834/comments/6 https://ubuntuforums.org/showthread.php?t=2474436=14094091#post14094091 https://www.reddit.com/r/Ubuntu/comments/ufalf4/cannot_connect_to_eduroam_since_2204_update/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2003903/+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 1963834] Re: openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
Can we reopen this and potentially backport OpenSSL 3.0.5 from kinetic to jammy? The "UnsafeLegacyServerConnect" option was mentioned above in #3. Unfortunately, that option was documented but not implemented in the 3.0.2 OpenSSL release available in the jammy repos. (See https://github.com/openssl/openssl/pull/18296) Enabling UnsafeLegacyRenegotiation is not acceptable and shouldn't be done. This is actually less secure than version 1.1.1 (which is what the previous LTS focal has available) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1963834 Title: openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] Status in openssl package in Ubuntu: Won't Fix Bug description: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 openssl: Installé : 3.0.1-0ubuntu1 Candidat : 3.0.1-0ubuntu1 Table de version : *** 3.0.1-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Using Ubuntu 22.04, I now get the following error message when attempting to connect to our office VPN using "gp-saml-gui (https://github.com/dlenski/gp-saml-gui)" : # dominique@Doombuntu:~$ .local/bin/gp-saml-gui server_url Looking for SAML auth tags in response to https://server_url/global-protect/prelogin.esp... usage: gp-saml-gui [-h] [--no-verify] [-C COOKIES | -K] [-g | -p] [-c CERT] [--key KEY] [-v | -q] [-x | -P | -S] [-u] [--clientos {Windows,Linux,Mac}] [-f EXTRA] server [openconnect_extra ...] gp-saml-gui: error: SSL error: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation disabled (_ssl.c:997) # # # gp-saml-gui uses python module requests. Using python ide, I can get the same results : # >>> r = requests.get('https://server_url') Traceback (most recent call last): File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, in urlopen httplib_response = self._make_request( File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 382, in _make_request self._validate_conn(conn) File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1012, in _validate_conn conn.connect() File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 411, in connect self.sock = ssl_wrap_socket( File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in ssl_wrap_socket ssl_sock = _ssl_wrap_socket_impl( File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl return ssl_context.wrap_socket(sock, server_hostname=server_hostname) File "/usr/lib/python3.10/ssl.py", line 512, in wrap_socket return self.sslsocket_class._create( File "/usr/lib/python3.10/ssl.py", line 1070, in _create self.do_handshake() File "/usr/lib/python3.10/ssl.py", line 1341, in do_handshake self._sslobj.do_handshake() ssl.SSLError: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation disabled (_ssl.c:997) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in send resp = conn.urlopen( File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755, in urlopen retries = retries.increment( File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 574, in increment raise MaxRetryError(_pool, url, error or ResponseError(cause)) urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='server_url', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, '[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation disabled (_ssl.c:997)'))) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/requests/api.py", line 76, in get return request('get', url, params=params, **kwargs) File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request return session.request(method=method, url=url, **kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, in send raise SSLError(e, request=request) requests.exceptions.SSLError: HTTPSConnectionPool(host='server_url', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, '[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy
[Touch-packages] [Bug 1892559] Re: [MIR] ccid opensc pcsc-lite
Desktop no longer has engineering goals to support smart cards. Foundations team might. Security Team is blocked until there is a mandate, an owning team, hardware funding, and possibly engineering support to resolve https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930530 Unassigning Security Team. ** Changed in: ccid (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) ** Changed in: opensc (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) ** Changed in: pcsc-lite (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid opensc pcsc-lite Status in ccid package in Ubuntu: In Progress Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: Invalid Status in pcsc-lite package in Ubuntu: New Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during the build. Includes debian/watch file. A handful of lintian issues Quilt packaging. [Dependencies] libpcsc-perl depends upon libpcsclite1, libc6, perl,
[Touch-packages] [Bug 1992102] [NEW] package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: using synaptic package manager to install uogrades, error message at end. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Oct 6 22:23:55 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-12-08 (2859 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-20 (47 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- 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/1992102 Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: using synaptic package manager to install uogrades, error message at end. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Oct 6 22:23:55 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-12-08 (2859 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-20 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992102/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
Yes @richardprammer, it appears ImagePullBackOff is one of the symptoms of this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
For anyone hitting this issue with AKS clusters: I have embedded the workaround above in a daemonset to avoid having to restart all nodes (for now) https://gist.github.com/skinny/96e7feb6b347299ebfacaa76295a82e7 - Please check the image+tag used in the daemonset to whatever is available in your cluster. - Deploy this daemonset to the cluster (default namespace is used) - After all pods are running 1/1 for a bit, you can delete it - Images can be pulled again :) HTH -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1978640] Re: FFTW_PRESERVE_INPUT does not always preserve input
** Changed in: fftw3 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fftw3 in Ubuntu. https://bugs.launchpad.net/bugs/1978640 Title: FFTW_PRESERVE_INPUT does not always preserve input Status in fftw3 package in Ubuntu: Invalid Bug description: libfftw3-dev: Installed: (none) Candidate: 3.3.8-2ubuntu8 Version table: 3.3.8-2ubuntu8 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages program to reproduce bug on Ubuntu 20.04 or 22.04 follows below expected: success (no assert) because the input was preserved observed: assert because the input was not preserved ```test_fftw_preserve.cc #include #include #include #include "assert.h" int main() { typedef std::complex cpx; int nfft = 125; fftwf_plan plan = fftwf_plan_many_dft(1,,1, NULL, NULL,1,nfft, NULL, NULL,1,nfft, FFTW_FORWARD, FFTW_ESTIMATE|FFTW_PRESERVE_INPUT|FFTW_UNALIGNED); std::vector in(nfft,cpx(1,2)); std::vector in_copied(in); std::vector out(nfft); fftwf_execute_dft(plan, reinterpret_cast(in.data()),reinterpret_cast(out.data())); assert(in == in_copied); fftwf_destroy_plan(plan); return 0; } ``` To run: ``` $ g++ test_fftw_preserve.cc -lfftw3f && ./a.out a.out: test_fftw_preserve.cc:21: int main(): Assertion `in == in_copied' failed. Aborted (core dumped) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1978640/+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 1978640] Re: FFTW_PRESERVE_INPUT does not always preserve input
I just realized that feeding NULL to the planner is not a supported mode. I withdraw the bug report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fftw3 in Ubuntu. https://bugs.launchpad.net/bugs/1978640 Title: FFTW_PRESERVE_INPUT does not always preserve input Status in fftw3 package in Ubuntu: New Bug description: libfftw3-dev: Installed: (none) Candidate: 3.3.8-2ubuntu8 Version table: 3.3.8-2ubuntu8 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages program to reproduce bug on Ubuntu 20.04 or 22.04 follows below expected: success (no assert) because the input was preserved observed: assert because the input was not preserved ```test_fftw_preserve.cc #include #include #include #include "assert.h" int main() { typedef std::complex cpx; int nfft = 125; fftwf_plan plan = fftwf_plan_many_dft(1,,1, NULL, NULL,1,nfft, NULL, NULL,1,nfft, FFTW_FORWARD, FFTW_ESTIMATE|FFTW_PRESERVE_INPUT|FFTW_UNALIGNED); std::vector in(nfft,cpx(1,2)); std::vector in_copied(in); std::vector out(nfft); fftwf_execute_dft(plan, reinterpret_cast(in.data()),reinterpret_cast(out.data())); assert(in == in_copied); fftwf_destroy_plan(plan); return 0; } ``` To run: ``` $ g++ test_fftw_preserve.cc -lfftw3f && ./a.out a.out: test_fftw_preserve.cc:21: int main(): Assertion `in == in_copied' failed. Aborted (core dumped) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1978640/+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 1978640] Re: FFTW_PRESERVE_INPUT does not always preserve input
Additional details: If `nfft` is changed from 125 to 128, the bug is not shown. If `fftwf_plan_many_dft` is called with buffer pointers, the bug is not shown. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fftw3 in Ubuntu. https://bugs.launchpad.net/bugs/1978640 Title: FFTW_PRESERVE_INPUT does not always preserve input Status in fftw3 package in Ubuntu: New Bug description: libfftw3-dev: Installed: (none) Candidate: 3.3.8-2ubuntu8 Version table: 3.3.8-2ubuntu8 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages program to reproduce bug on Ubuntu 20.04 or 22.04 follows below expected: success (no assert) because the input was preserved observed: assert because the input was not preserved ```test_fftw_preserve.cc #include #include #include #include "assert.h" int main() { typedef std::complex cpx; int nfft = 125; fftwf_plan plan = fftwf_plan_many_dft(1,,1, NULL, NULL,1,nfft, NULL, NULL,1,nfft, FFTW_FORWARD, FFTW_ESTIMATE|FFTW_PRESERVE_INPUT|FFTW_UNALIGNED); std::vector in(nfft,cpx(1,2)); std::vector in_copied(in); std::vector out(nfft); fftwf_execute_dft(plan, reinterpret_cast(in.data()),reinterpret_cast(out.data())); assert(in == in_copied); fftwf_destroy_plan(plan); return 0; } ``` To run: ``` $ g++ test_fftw_preserve.cc -lfftw3f && ./a.out a.out: test_fftw_preserve.cc:21: int main(): Assertion `in == in_copied' failed. Aborted (core dumped) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1978640/+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 1978640] [NEW] FFTW_PRESERVE_INPUT does not always preserve input
Public bug reported: libfftw3-dev: Installed: (none) Candidate: 3.3.8-2ubuntu8 Version table: 3.3.8-2ubuntu8 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages program to reproduce bug on Ubuntu 20.04 or 22.04 follows below expected: success (no assert) because the input was preserved observed: assert because the input was not preserved ```test_fftw_preserve.cc #include #include #include #include "assert.h" int main() { typedef std::complex cpx; int nfft = 125; fftwf_plan plan = fftwf_plan_many_dft(1,,1, NULL, NULL,1,nfft, NULL, NULL,1,nfft, FFTW_FORWARD, FFTW_ESTIMATE|FFTW_PRESERVE_INPUT|FFTW_UNALIGNED); std::vector in(nfft,cpx(1,2)); std::vector in_copied(in); std::vector out(nfft); fftwf_execute_dft(plan, reinterpret_cast(in.data()),reinterpret_cast(out.data())); assert(in == in_copied); fftwf_destroy_plan(plan); return 0; } ``` To run: ``` $ g++ test_fftw_preserve.cc -lfftw3f && ./a.out a.out: test_fftw_preserve.cc:21: int main(): Assertion `in == in_copied' failed. Aborted (core dumped) ``` ** Affects: fftw3 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "reproduction example" https://bugs.launchpad.net/bugs/1978640/+attachment/5597250/+files/test_fftw_preserve.cc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fftw3 in Ubuntu. https://bugs.launchpad.net/bugs/1978640 Title: FFTW_PRESERVE_INPUT does not always preserve input Status in fftw3 package in Ubuntu: New Bug description: libfftw3-dev: Installed: (none) Candidate: 3.3.8-2ubuntu8 Version table: 3.3.8-2ubuntu8 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages program to reproduce bug on Ubuntu 20.04 or 22.04 follows below expected: success (no assert) because the input was preserved observed: assert because the input was not preserved ```test_fftw_preserve.cc #include #include #include #include "assert.h" int main() { typedef std::complex cpx; int nfft = 125; fftwf_plan plan = fftwf_plan_many_dft(1,,1, NULL, NULL,1,nfft, NULL, NULL,1,nfft, FFTW_FORWARD, FFTW_ESTIMATE|FFTW_PRESERVE_INPUT|FFTW_UNALIGNED); std::vector in(nfft,cpx(1,2)); std::vector in_copied(in); std::vector out(nfft); fftwf_execute_dft(plan, reinterpret_cast(in.data()),reinterpret_cast(out.data())); assert(in == in_copied); fftwf_destroy_plan(plan); return 0; } ``` To run: ``` $ g++ test_fftw_preserve.cc -lfftw3f && ./a.out a.out: test_fftw_preserve.cc:21: int main(): Assertion `in == in_copied' failed. Aborted (core dumped) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1978640/+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 1977884] Re: package e2fsprogs 1.45.5-2ubuntu1 failed to install/upgrade: trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12
Hi Rabee, The metapackage android-sdk-platform-tools installs several packages, which includes e2fsprogs (https://packages.ubuntu.com/focal/android-sdk- platform-tools). It also make a symbolic link from /usr/lib/android- sdk/platform-tools/mke2fs.conf to /etc/mke2fs.conf All of which should not cause package conflicts. I attempted reproduce your bug by installing the latest version of Zorin in a VM (I had to use Zorin 16, since the default apt sources in Zorin 15 did not work). Then I installed android-sdk-platform-tools which brought e2fsprogs to version 1.45.5-2ubuntu1. The upgrade from e2fsprogs to version 1.45.5-2ubuntu1.1 worked smoothly on my VM environment. Does `ls -la /usr/lib/android-sdk/platform-tools/mke2fs.conf` print something like: `/usr/lib/android-sdk/platform-tools/mke2fs.conf -> /etc/mke2fs.conf`? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1977884 Title: package e2fsprogs 1.45.5-2ubuntu1 failed to install/upgrade: trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk- platform-tools 27.0.0+12 Status in e2fsprogs package in Ubuntu: New Bug description: The error happens during updates ProblemType: Package DistroRelease: Ubuntu 20.04 Package: e2fsprogs 1.45.5-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-113.127-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 7 11:06:48 2022 DpkgTerminalLog: Preparing to unpack .../00-e2fsprogs_1.45.5-2ubuntu1.1_amd64.deb ... Unpacking e2fsprogs (1.45.5-2ubuntu1.1) over (1.45.5-2ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-oRpMVG/00-e2fsprogs_1.45.5-2ubuntu1.1_amd64.deb (--unpack): trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12 DuplicateSignature: package:e2fsprogs:1.45.5-2ubuntu1 Unpacking e2fsprogs (1.45.5-2ubuntu1.1) over (1.45.5-2ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-oRpMVG/00-e2fsprogs_1.45.5-2ubuntu1.1_amd64.deb (--unpack): trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12 ErrorMessage: trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12 InstallationDate: Installed on 2020-06-05 (732 days ago) InstallationMedia: Zorin-OS 15.1 Education 64bit Python3Details: /usr/bin/python3.8, Python 3.8.10, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: e2fsprogs Title: package e2fsprogs 1.45.5-2ubuntu1 failed to install/upgrade: trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1977884/+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 1975644] [NEW] package ca-certificates 20211016 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1
Public bug reported: upgrade from focal->jammy requested me to report this issue ProblemType: Package DistroRelease: Ubuntu 22.04 Package: ca-certificates 20211016 ProcVersionSignature: Ubuntu 5.4.0-113.127-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue May 24 21:42:23 2022 Ec2AMI: ami-000ab5e1 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: vps2020-essential-2-4-80 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: ca-certificates Title: package ca-certificates 20211016 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-05-24 (0 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package ec2-images jammy need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1975644 Title: package ca-certificates 20211016 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: New Bug description: upgrade from focal->jammy requested me to report this issue ProblemType: Package DistroRelease: Ubuntu 22.04 Package: ca-certificates 20211016 ProcVersionSignature: Ubuntu 5.4.0-113.127-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue May 24 21:42:23 2022 Ec2AMI: ami-000ab5e1 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: vps2020-essential-2-4-80 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: ca-certificates Title: package ca-certificates 20211016 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-05-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1975644/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
still seeing Apr 9 15:30:54 drafting-table /usr/libexec/gdm-x-session[355145]: /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not found in an install which is "jammy daily iso from a week or two back with daily dist upgrades", under i3; $ dpkg -l gdm3 x11-common i3-wm Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii gdm3 42.0-1ubuntu2 amd64GNOME Display Manager ii i3-wm 4.20.1-1amd64improved dynamic tiling window manager ii x11-common 1:7.7+23ubuntu2 all X Window System (X.Org) infrastructure -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in gdm3 package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 1965466] [NEW] [DEFENDER P10, Realtek ALC293, Mic, Internal] No sound at all
Public bug reported: auto-generated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mdb2244 F pulseaudio /dev/snd/controlC1: mdb2244 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 18 02:51:06 2022 InstallationDate: Installed on 2018-12-10 (1193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Eingebautes Tongerät - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mdb2244 F pulseaudio /dev/snd/controlC1: mdb2244 F pulseaudio Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: No sound at all Title: [DEFENDER P10, Realtek ALC293, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 7.5 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RME1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH77Dx dmi.board.vendor: MEDION dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: N/A dmi.ec.firmware.release: 7.1 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RME1:bd08/29/2020:br7.5:efr7.1:svnMEDION:pnDEFENDERP10:pvrNotApplicable:rvnMEDION:rnNH77Dx:rvrNotApplicable:cvnMEDION:ct10:cvrN/A:skuML-21000930028862: dmi.product.family: Erazer dmi.product.name: DEFENDER P10 dmi.product.sku: ML-210009 30028862 dmi.product.version: Not Applicable dmi.sys.vendor: MEDION ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1965466 Title: [DEFENDER P10, Realtek ALC293, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: auto-generated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mdb2244 F pulseaudio /dev/snd/controlC1: mdb2244 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 18 02:51:06 2022 InstallationDate: Installed on 2018-12-10 (1193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Eingebautes Tongerät - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mdb2244 F pulseaudio /dev/snd/controlC1: mdb2244 F pulseaudio Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: No sound at all Title: [DEFENDER P10, Realtek ALC293, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 7.5 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RME1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH77Dx dmi.board.vendor: MEDION dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: N/A dmi.ec.firmware.release: 7.1 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RME1:bd08/29/2020:br7.5:efr7.1:svnMEDION:pnDEFENDERP10:pvrNotApplicable:rvnMEDION:rnNH77Dx:rvrNotApplicable:cvnMEDION:ct10:cvrN/A:skuML-21000930028862: dmi.product.family: Erazer dmi.product.name: DEFENDER P10 dmi.product.sku: ML-210009 30028862 dmi.product.version: Not Applicable dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965466/+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 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3
Canonical client has opened a case regarding this as a current issue preventing them from upgrading their systems from 14.04 to 18.04. This blocker is due to the version of openssh-server on Bionic not allowing the SolarWinds monitoring agent to establish a successful SSH connection, as it advertises SSH-1.99 as the protocol. I have updated the Impact statement in the initial comment with further information and references. Please re-evaluate this bug as having a current impact on some clients. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1863930 Title: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3 Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Bionic: Incomplete Bug description: [Impact] * The version check in ssh was broken no more following RFC 4253 and thereby denying some clients that it shouldn't. https://datatracker.ietf.org/doc/html/rfc4253#section-5.1 * It is intended for clients reporting SSH-1.99 to be treated as if they were advertising SSH-2.0, but with some backwards compatibility. * Upstream fixed that, and this request is to back-port the changes into 18.04 Bionic. * In practice this is affecting clients using the SolarWinds monitoring agent. Solarwinds SSH client advertises SSH-1.99 and Ubuntu 18.04 openssh-server is refusing the connection. * This results in the following error in the auth.log, and a failed connection from the agent. Protocol major versions differ for port : SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-WeOnlyDo.Net * More information from SolarWinds at the link below. They call out 18.04 as affected and recommend upgrading OpenSSH-server to 7.7 or greater. https://support.solarwinds.com/SuccessCenter/s/article/SAM-s-Linux- Unix-Script-monitor-fails-to-connect-on-a-server-running- OpenSSH-7-6?language=en_US [Test Case] # Prep * configure the ssh server to generally work # Testcase $ wget https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+attachment/5332797/+files/test_bug_1863930.py $ apt install python3-paramiko $ python3 test_bug_1863930.py localhost (or whatever your host is) Will report "Server is not patched." or "Server is patched. * for an extra regression check it might be worth to do some "normal" ssh connections as well [Regression Potential] * The change is very small and reviewable as well as being upstream and in all Ubuntu releases >=Cosmic for a while now so it seems safe. If anything the kind of regression to expect is that some former (wrong) connection denials will then succeed. I can only think of that being an issue in test suites but not in the real world. [Other Info] * n/a -- SSHD closes the connection and logs the error message below when a client presents a protoversion of "1.99": Protocol major versions differ for X.X.X.X port X: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX RFC 4253 only states that clients should treat a server's protoversion of "1.99" as equivalent to "2.0"; however, some backward-compatible clients send a protoversion of "1.99" and expect the server to treat it as "2.0". This regression was introduced in openssh-portable 7.6p1 from commit 97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06. I've attached a patch with both of those fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+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 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3
** Description changed: [Impact] * The version check in ssh was broken no more following RFC 4253 and - thereby denying some clients that it shouldn't + thereby denying some clients that it shouldn't. - * Upstream fixed that and this is backporting the changes to bionic. +https://datatracker.ietf.org/doc/html/rfc4253#section-5.1 + + * It is intended for clients reporting SSH-1.99 to be treated as if +they were advertising SSH-2.0, but with some backwards compatibility. + + * Upstream fixed that, and this request is to back-port the changes into +18.04 Bionic. + + * In practice this is affecting clients using the SolarWinds monitoring + agent. Solarwinds SSH client advertises SSH-1.99 and Ubuntu 18.04 + openssh-server is refusing the connection. + + * This results in the following error in the auth.log, and a failed + connection from the agent. + + Protocol major versions differ for port : + SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-WeOnlyDo.Net + + * More information from SolarWinds at the link below. They call out + 18.04 as affected and recommend upgrading OpenSSH-server to 7.7 or + greater. + + https://support.solarwinds.com/SuccessCenter/s/article/SAM-s-Linux-Unix- + Script-monitor-fails-to-connect-on-a-server-running- + OpenSSH-7-6?language=en_US [Test Case] # Prep * configure the ssh server to generally work # Testcase $ wget https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+attachment/5332797/+files/test_bug_1863930.py $ apt install python3-paramiko $ python3 test_bug_1863930.py localhost (or whatever your host is) Will report "Server is not patched." or "Server is patched. - * for an extra regression check it might be worth to do some "normal" ssh -connections as well + * for an extra regression check it might be worth to do some "normal" ssh + connections as well [Regression Potential] - * The change is very small and reviewable as well as being upstream and -in all Ubuntu releases >=Cosmic for a while now so it seems safe. -If anything the kind of regression to expect is that some former -(wrong) connection denials will then succeed. I can only think of -that being an issue in test suites but not in the real world. + * The change is very small and reviewable as well as being upstream and + in all Ubuntu releases >=Cosmic for a while now so it seems safe. + If anything the kind of regression to expect is that some former + (wrong) connection denials will then succeed. I can only think of + that being an issue in test suites but not in the real world. [Other Info] * n/a -- SSHD closes the connection and logs the error message below when a client presents a protoversion of "1.99": Protocol major versions differ for X.X.X.X port X: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX RFC 4253 only states that clients should treat a server's protoversion of "1.99" as equivalent to "2.0"; however, some backward-compatible clients send a protoversion of "1.99" and expect the server to treat it as "2.0". This regression was introduced in openssh-portable 7.6p1 from commit 97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06. I've attached a patch with both of those fixes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1863930 Title: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3 Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Bionic: Incomplete Bug description: [Impact] * The version check in ssh was broken no more following RFC 4253 and thereby denying some clients that it shouldn't. https://datatracker.ietf.org/doc/html/rfc4253#section-5.1 * It is intended for clients reporting SSH-1.99 to be treated as if they were advertising SSH-2.0, but with some backwards compatibility. * Upstream fixed that, and this request is to back-port the changes into 18.04 Bionic. * In practice this is affecting clients using the SolarWinds monitoring agent. Solarwinds SSH client advertises SSH-1.99 and Ubuntu 18.04 openssh-server is refusing the connection. * This results in the following error in the auth.log, and a failed connection from the agent. Protocol major versions differ for port : SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-WeOnlyDo.Net * More information from SolarWinds at the link below. They call out 18.04 as affected and recommend upgrading OpenSSH-server to 7.7 or greater. https://support.solarwinds.com/SuccessCenter/s/article/SAM-s-Linux- Unix-Script-monitor-fails-to-connect-on-a-server-running- OpenSSH-7-6?language=en_US [Test Case] # Prep * configure the ssh server to generally work #
[Touch-packages] [Bug 1954911] [NEW] Xorg freeze
Public bug reported: When I try to hookup my laptop to a smart TV using an HDMI it will not boot up at all. With my laptop running after booting normally and I plugin the HDMI cable it freeze up and the only way to unfreeze it is to hold the power down until it shuts off. I've done this at least twice maybe three times. Its like there is not an HDMI driver installed. I have been a computer tech since 1984 but as you know learning a new operating system is very time consuming. I started with Dr. DOS 6.0 and it was a great OP System but than of course MicroShaft but them out of business then I finally had to go to MS DOS 4.0 and its been down hill ever since. I'm 64 and working my way into Linux. Any ideas would be great ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_66_74_generic_81 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 15 05:09:06 2021 DistUpgraded: 2020-12-17 01:37:02,155 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics Controller [104d:9035] Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics Controller [104d:9035] MachineType: Sony Corporation VGN-FW351J ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-12-17 (363 days ago) dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R2050Y0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR2050Y0:bd11/07/2008:svnSonyCorporation:pnVGN-FW351J:pvrC60184W1:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-FW351J dmi.product.sku: N/A dmi.product.version: C60184W1 dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze 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/1954911 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: When I try to hookup my laptop to a smart TV using an HDMI it will not boot up at all. With my laptop running after booting normally and I plugin the HDMI cable it freeze up and the only way to unfreeze it is to hold the power down until it shuts off. I've done this at least twice maybe three times. Its like there is not an HDMI driver installed. I have been a computer tech since 1984 but as you know learning a new operating system is very time consuming. I started with Dr. DOS 6.0 and it was a great OP System but than of course MicroShaft but them out of business then I finally had to go to MS DOS 4.0 and its been down hill ever since. I'm 64 and working my way into Linux. Any ideas would be great ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_66_74_generic_81 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 15 05:09:06 2021 DistUpgraded: 2020-12-17 01:37:02,155 DEBUG icon theme changed, re-reading DistroCodename: focal
[Touch-packages] [Bug 1931813] [NEW] Alienware Area-51m / Realtek ALC215 multi-function headphone jacks configured incorrectly
Public bug reported: The built in laptop speakers / mic work ok There are two 3.5mm jack ports which end up configured one as a headphone socket and one as a microphone, whereas in Windows they are multi-function ports that support headsets. Adding `options snd-hda-intel index=0 model=dell-headset-multi` to /etc/modprobe.d/alsa-base.conf makes the port normally configured as headphones work (inserting anything shows a screen asking to know what was inserted -- headphones or headset) but the port normally configured as a microphone stays that way. I have done a bit of poking about but couldn't figure out how to make the pin configs the same (most of the documentation for compiling ALSA seems out of date). I ran RtHDDump on Windows and attached the output from that in case it's useful. Thanks! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 7732 F pulseaudio /dev/snd/pcmC0D0c: mark 7732 F...m pulseaudio /dev/snd/pcmC0D0p: mark 7732 F...m pulseaudio /dev/snd/controlC1: mark 7732 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 13 20:23:27 2021 InstallationDate: Installed on 2021-05-23 (21 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [Alienware Area-51m, Realtek ALC215, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 3/21/2019 dmi.bios.release: 1.3 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.2 dmi.board.name: Alienware Area-51m dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.2:bd3/21/2019:br1.3:svnAlienware:pnAlienwareArea-51m:pvr1.3.2:rvnAlienware:rnAlienwareArea-51m:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Area-51m dmi.product.sku: 08C4 dmi.product.version: 1.3.2 dmi.sys.vendor: Alienware mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-06-13T16:28:28.400989 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "RtHDDump.txt" https://bugs.launchpad.net/bugs/1931813/+attachment/5504408/+files/RtHDDump.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1931813 Title: Alienware Area-51m / Realtek ALC215 multi-function headphone jacks configured incorrectly Status in alsa-driver package in Ubuntu: New Bug description: The built in laptop speakers / mic work ok There are two 3.5mm jack ports which end up configured one as a headphone socket and one as a microphone, whereas in Windows they are multi-function ports that support headsets. Adding `options snd-hda-intel index=0 model=dell-headset-multi` to /etc/modprobe.d/alsa-base.conf makes the port normally configured as headphones work (inserting anything shows a screen asking to know what was inserted -- headphones or headset) but the port normally configured as a microphone stays that way. I have done a bit of poking about but couldn't figure out how to make the pin configs the same (most of the documentation for compiling ALSA seems out of date). I ran RtHDDump on Windows and attached the output from that in case it's useful. Thanks! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 7732 F pulseaudio /dev/snd/pcmC0D0c: mark 7732 F...m pulseaudio /dev/snd/pcmC0D0p: mark 7732 F...m pulseaudio /dev/snd/controlC1: mark 7732 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 13 20:23:27 2021 InstallationDate: Installed on 2021-05-23 (21 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording
[Touch-packages] [Bug 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
** Description changed: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). - There are already two customer cases from the US Army complaining about - this behavior - (https://canonical.lightning.force.com/lightning/r/Case/5004K03vkq4QAA/view - and - https://canonical.lightning.force.com/lightning/r/Case/5004K03tkbmQAA/view). + There are already two customer cases from Canonical clients complaining + about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Confirmed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to:
[Touch-packages] [Bug 1926009] Re: Incomplete display of text
Ok I have been able to rollback the xserver-xorg-video-amdgpu package from 19.1.0+git2104271106.aedbf47~f~mesarc0 to 19.1.0-1, and can confirm that the issue didn't reappear. ** Attachment added: "Output of apt-cache showpkg xserver-xorg-video-amdgpu" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926009/+attachment/5494229/+files/amdgpu-avail-versions.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/1926009 Title: Incomplete display of text Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/ubuntu/+source/xorg/+bug/1926009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1926009] Re: Incomplete display of text
Yes, of course leave this with me and I'll report back later. -- 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/1926009 Title: Incomplete display of text Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/ubuntu/+source/xorg/+bug/1926009/+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 1926009] Re: Incomplete display of text
I am happy to report that this issue looks to have been resolved. The roll back took a bit of time to do, and I am still not sure that I did it fully correctly. However it did the trick. I also note that there were some subsequent updates to both the Mesa libraries, and xserver-xorg-video-amdgpu driver, amongst which was a fix. Thank you, Sebastien, for all your help. it is very much appreciated. Many thanks, Mark. -- 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/1926009 Title: Incomplete display of text Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/ubuntu/+source/xorg/+bug/1926009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1926009] Re: Incomplete display of text
Certainly. I might not be able get to it for a day or two, but will let you know how I get on. Many thanks, Mark. On 27 April 2021 10:43:34 BST, Sebastien Bacher <1926...@bugs.launchpad.net> wrote: >Could you try rolling back those updates see if resolves your issue? > >-- >You received this bug notification because you are subscribed to the >bug >report. >https://bugs.launchpad.net/bugs/1926009 > >Title: > Incomplete display of text > >To manage notifications about this bug go to: >https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926009/+subscriptions -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- 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/1926009 Title: Incomplete display of text Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/ubuntu/+source/xorg/+bug/1926009/+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 1926009] Re: Incomplete display of text
> Could you add your 'journalctl -b 0' log after getting the issue? See attached. ** Attachment added: "Output of 'journalctl -b 0'" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926009/+attachment/5492531/+files/requested-journal-logs -- 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/1926009 Title: Incomplete display of text Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/ubuntu/+source/xorg/+bug/1926009/+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 1926009] Re: Incomplete display of text
The issue appears to have started around the 21st April, and apart from a couple of browser upgrades some misc packages, there appear to have been a number of Mesa related upgrades (see attached). ** Attachment added: "Grepped output from /var/log/dpkg.loc" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926009/+attachment/5492530/+files/upgradelog -- 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/1926009 Title: Incomplete display of text Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/ubuntu/+source/xorg/+bug/1926009/+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 1926009] [NEW] Incomplete display of text
Public bug reported: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages 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/1926009 Title: Incomplete display of text Status in xorg package in Ubuntu: New Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog
[Touch-packages] [Bug 1923333] [NEW] Benq G610HDA not being detected
Public bug reported: My monitor Benq G610HDA is not being detected by Ubuntu. Good VGI Cable, still Unknown display ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04: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 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-5ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 13:13:18 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.39, 5.8.0-45-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia, 460.39, 5.8.0-48-generic, x86_64: installed v4l2loopback, 0.12.3, 5.8.0-45-generic, x86_64: installed v4l2loopback, 0.12.3, 5.8.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:1a7d] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:1a7d] InstallationDate: Installed on 2021-02-08 (61 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. X455LB ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=def1bb03-4353-441e-b107-29aaf5b72e17 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X455LB.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X455LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX455LB.205:bd08/03/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnX455LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X455LB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution 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/192 Title: Benq G610HDA not being detected Status in xorg package in Ubuntu: New Bug description: My monitor Benq G610HDA is not being detected by Ubuntu. Good VGI Cable, still Unknown display ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: ""
[Touch-packages] [Bug 1922130] [NEW] Request addition of Fedora / Redhat "sftp-force-permissions" patch
Public bug reported: Fedora / Redhat ships openssh with a patch which adds "-m force permission" flag to sftp-server. This is quite a common feature request / support request on the various stackexchange sites - https://superuser.com/questions/332284/in-sftp- how-to-set-the-default-permission-for-all-files-in-a-folder You will see that someone has answered "add -m" there which is indeed the simplest answer by a distance but unfortunately it's a non standard patch: https://src.fedoraproject.org/rpms/openssh/blob/f34/f/openssh-6.7p1 -sftp-force-permission.patch This I think should supersede #563216 because they have been shipping this in production presumably since at least 2015 (I see it in fedora 22 branch), so it is a known stable patch compared to the one suggested there. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1922130 Title: Request addition of Fedora / Redhat "sftp-force-permissions" patch Status in openssh package in Ubuntu: New Bug description: Fedora / Redhat ships openssh with a patch which adds "-m force permission" flag to sftp-server. This is quite a common feature request / support request on the various stackexchange sites - https://superuser.com/questions/332284 /in-sftp-how-to-set-the-default-permission-for-all-files-in-a-folder You will see that someone has answered "add -m" there which is indeed the simplest answer by a distance but unfortunately it's a non standard patch: https://src.fedoraproject.org/rpms/openssh/blob/f34/f/openssh-6.7p1 -sftp-force-permission.patch This I think should supersede #563216 because they have been shipping this in production presumably since at least 2015 (I see it in fedora 22 branch), so it is a known stable patch compared to the one suggested there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1922130/+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 1920610] [NEW] The repository 'http://ddebs.ubuntu.com groovy Release' is not signed
*** This bug is a security vulnerability *** Public security bug reported: Did an update this morning and it looks like the key has expired. W: GPG error: http://ddebs.ubuntu.com groovy Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com groovy-updates Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com groovy-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ** Affects: ubuntu-keyring (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920610 Title: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed Status in ubuntu-keyring package in Ubuntu: New Bug description: Did an update this morning and it looks like the key has expired. W: GPG error: http://ddebs.ubuntu.com groovy Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com groovy-updates Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com groovy-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920610/+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 1906267] Re: IntelHD audio not detected after upgrading to Ubuntu 20.10
*** This bug is a duplicate of bug 1897965 *** https://bugs.launchpad.net/bugs/1897965 ** This bug has been marked a duplicate of bug 1897965 PulseAudio doesn't work when pipewire is installed (ie. KDE) -- 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/1906267 Title: IntelHD audio not detected after upgrading to Ubuntu 20.10 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn my computer on the sound card doesn't work. If I load Pulse Audio Volume Control and disable and then re-enable the audio controller (Family 17h (Models 00h-0fh) HD Audio Controller it will work again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 30 15:19:50 2020 InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic
[Touch-packages] [Bug 1906267] Re: IntelHD audio not detected after upgrading to Ubuntu 20.10
If that workaround has fixed the problem (I'm waiting a while to make sure) do I mark it as a duplicate of that bug? -- 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/1906267 Title: IntelHD audio not detected after upgrading to Ubuntu 20.10 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn my computer on the sound card doesn't work. If I load Pulse Audio Volume Control and disable and then re-enable the audio controller (Family 17h (Models 00h-0fh) HD Audio Controller it will work again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 30 15:19:50 2020 InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7
[Touch-packages] [Bug 1916729] Re: libnss3 package in Ubuntu 20.10 ships files under `/usr/lib/${DEB_HOST_MULTIARCH}` literally without expansion
*** This bug is a duplicate of bug 1908818 *** https://bugs.launchpad.net/bugs/1908818 ** This bug has been marked a duplicate of bug 1908818 pure packaging of libnss3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1916729 Title: libnss3 package in Ubuntu 20.10 ships files under `/usr/lib/${DEB_HOST_MULTIARCH}` literally without expansion Status in nss package in Ubuntu: Fix Released Status in nss source package in Groovy: Triaged Bug description: ``` brlin@groovy:~$ dpkg-query --listfiles libnss3 /. /usr /usr/lib /usr/lib/${DEB_HOST_MULTIARCH} ...stripped... /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so ``` The path appears to be a result of a failed parameter expansion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1916729/+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 1906267] Re: IntelHD audio not detected after upgrading to Ubuntu 20.10
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1906267 Title: IntelHD audio not detected after upgrading to Ubuntu 20.10 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn my computer on the sound card doesn't work. If I load Pulse Audio Volume Control and disable and then re-enable the audio controller (Family 17h (Models 00h-0fh) HD Audio Controller it will work again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 30 15:19:50 2020 InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
[Touch-packages] [Bug 1915870] Re: gnome session not starting (segfault with r300_dri.so)
Now I can confirm, applying the patch mentioned above brings my PC back to normal. Short summary for everyone else who might read this bug report: Download and save patch as patch.diff and run: sudo apt-build install --patch patch.diff libgl1-mesa-dri -- 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/1915870 Title: gnome session not starting (segfault with r300_dri.so) Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Status in mesa package in Fedora: Unknown Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+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 1915870] Re: gnome session not starting (segfault with r300_dri.so)
Hi, I agree, the fix seems to be this https://gitlab.freedesktop.org/mesa/mesa/-/commit/58e43594fc457eaaf1b1e01e48948959a82080bc But it's not yet available. So can anyone point me to an explanation how to build such a package from source and install it? I'll be able to patch it myself. And another question. Won't ubuntu-bug do the same as apport-cli -c? It also created a bug report (linked in my previous message). But it's somehow marked as private, so I'm not sure everyone can see it. Thanks all, for your help. -- 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/1915870 Title: gnome session not starting (segfault with r300_dri.so) Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Status in mesa package in Fedora: Unknown Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 48734] Re: Home permissions too open
On 18/01/2021 12:46, Launchpad Bug Tracker wrote: > This bug was fixed in the package adduser - 3.118ubuntu5 > > ** Changed in: adduser (Ubuntu Hirsute) >Status: Fix Committed => Fix Released \o/ Well done and thank you to everyone who worked to make this happen. I wonder if there will ever be another LP bug <50k that gets fix- released? Mark -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/48734 Title: Home permissions too open Status in adduser package in Ubuntu: Fix Released Status in shadow package in Ubuntu: Fix Released Status in adduser source package in Hirsute: Fix Released Status in shadow source package in Hirsute: Fix Released Status in Ubuntu RTM: Opinion Bug description: Binary package hint: debian-installer On a fresh dapper install i noticed that the file permissons for the home directory for the user created by the installer is set to 755, giving read access to everyone on the system. Surely this is a bad idea? If your set on the idea can we atleast have a option during the boot proccess? Also new files that are created via the console ('touch' etc.) are done so with '644' permissons, is there anything that can be done here? nautlius seems to create files at '600', which is a better setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/48734/+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 1906267] [NEW] IntelHD audio not detected after upgrading to Ubuntu 20.10
Public bug reported: After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn my computer on the sound card doesn't work. If I load Pulse Audio Volume Control and disable and then re-enable the audio controller (Family 17h (Models 00h-0fh) HD Audio Controller it will work again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 30 15:19:50 2020 InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1906267 Title: IntelHD audio not detected after upgrading to Ubuntu 20.10 Status in pulseaudio package in Ubuntu: New Bug description: After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn my computer on the sound card doesn't work. If I load Pulse Audio Volume Control and disable and then re-enable the audio controller (Family 17h (Models 00h-0fh) HD Audio Controller it will work again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 30 15:19:50 2020 InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1906267/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Thank you for the advice! I'm going to purchase and see if it works with my setup. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
would something like https://www.amazon.com/dp/B07J5WFPXX/ref=cm_sw_r_cp_apa_fabt1_IciRFb2QMGBDJ work? -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1897820] [NEW] systemd rejects cross-uid-namespace connections
Public bug reported: To reproduce: $ unshare -r systemd-run --user echo it works Failed to start transient service unit: Access denied There is prior-art in the RHEL-8 bug report and the fix: https://bugzilla.redhat.com/show_bug.cgi?id=1838081#c13 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.42 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 30 10:12:45 2020 InstallationDate: Installed on 2020-09-14 (15 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Hewlett-Packard p2-1320a ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=/dev/mapper/root--vg-lvroot ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.08 dmi.board.asset.tag: 3CR2450BRJ dmi.board.name: 2AE2 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.02 dmi.chassis.asset.tag: 3CR2450BRJ dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.08:bd08/29/2012:svnHewlett-Packard:pnp2-1320a:pvr1.00:rvnPEGATRONCORPORATION:rn2AE2:rvr1.02:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: p2-1320a dmi.product.version: 1.00 dmi.sys.vendor: Hewlett-Packard ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1897820 Title: systemd rejects cross-uid-namespace connections Status in systemd package in Ubuntu: New Bug description: To reproduce: $ unshare -r systemd-run --user echo it works Failed to start transient service unit: Access denied There is prior-art in the RHEL-8 bug report and the fix: https://bugzilla.redhat.com/show_bug.cgi?id=1838081#c13 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.42 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 30 10:12:45 2020 InstallationDate: Installed on 2020-09-14 (15 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Hewlett-Packard p2-1320a ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=/dev/mapper/root--vg-lvroot ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.08 dmi.board.asset.tag: 3CR2450BRJ dmi.board.name: 2AE2 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.02 dmi.chassis.asset.tag: 3CR2450BRJ dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.08:bd08/29/2012:svnHewlett-Packard:pnp2-1320a:pvr1.00:rvnPEGATRONCORPORATION:rn2AE2:rvr1.02:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: p2-1320a dmi.product.version: 1.00 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897820/+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] [NEW] Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack
Public bug reported: 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 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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 pulseaudio package in Ubuntu: New 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/ubuntu/+source/pulseaudio/+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
Re: [Touch-packages] [Bug 1882242] Re: June 4th network-manager update kills wireless networking
Thanks Sebastien. I'm beginning to suspect a faulty WiFi card. Wish there was some way to determine if that is the culprit. On Mon, Jun 8, 2020 at 4:30 PM Sebastien Bacher <1882...@bugs.launchpad.net> wrote: > The update mentioned fixes the iptables path on systemd not having > usrmerged, it's probably not the issue there > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1882242 > > Title: > June 4th network-manager update kills wireless networking > > Status in network-manager package in Ubuntu: > Incomplete > > Bug description: > network-manager problems > > June 4, 2020 apt update installed two networking packages: > network-manager_1.14.6-2+deb10u1_amd64.deb > libnm0_1.14.6-2+deb10u1_amd64.deb > > System: > Kernel: 5.4.0-33-generic x86_64 > Desktop: MATE 1.24.0 > Distro: Ubuntu 20.04 LTS (Focal Fossa) > Machine: > Type: Laptop System: Dell product: Latitude E6530 v: 01 > > After rebooting the laptop, the wireless access point(s) are no longer > available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- > Fi Networks" is grayed out. > > Network: > Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl > IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b > > $ sudo ip addr > > wlp2s0: mtu 1500 qdisc > fq_codel state DORMANT group default qlen 1000 > link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff > > $ sudo nmcli > wlp2s0: disconnected > "Broadcom and subsidiaries BCM43228" > wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 > > $ sudo nmcli device show > GENERAL.DEVICE: wlp2s0 > GENERAL.TYPE: wifi > GENERAL.HWADDR: 3C:77:E6:7C:5D:7B > GENERAL.MTU:1500 > GENERAL.STATE: 30 (disconnected) > GENERAL.CONNECTION: -- > GENERAL.CON-PATH: -- > > $ sudo nmcli radio wifi > enabled > > $ sudo iwlist wlp2s0 scanning > wlp2s0No scan results > > $ sudo iwlist wlp2s0 accesspoints > wlp2s0Interface doesn't have a list of Peers/Access-Points > > $ sudo iwlist wlp2s0 ap > wlp2s0Interface doesn't have a list of Peers/Access-Points > > $ sudo iwlist wlp2s0 wpakeys > wlp2s02 key sizes : 40, 104bits > 4 keys available : > Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported > > $ sudo iwconfig wlp2s0 > wlp2s0IEEE 802.11 ESSID:off/any > Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm > > Retry short limit:7 RTS thr:off Fragment thr:off > Encryption key:off > Power Management:on > > $ sudo rfkill list > 1: phy0: Wireless LAN > Soft blocked: no > Hard blocked: no > 2: brcmwl-0: Wireless LAN > Soft blocked: no > Hard blocked: no > 3: dell-wifi: Wireless LAN > Soft blocked: no > Hard blocked: no > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1882242/+subscriptions > -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results
[Touch-packages] [Bug 1882242] IfupdownConfig.txt
apport information ** Attachment added: "IfupdownConfig.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381759/+files/IfupdownConfig.txt -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1882242] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381768/+files/RfKill.txt -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1882242] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381767/+files/ProcCpuinfoMinimal.txt -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1882242] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381766/+files/PciNetwork.txt -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1882242] nmcli-con.txt
apport information ** Attachment added: "nmcli-con.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381770/+files/nmcli-con.txt -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1882242] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381769/+files/WifiSyslog.txt -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1882242] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381763/+files/NetDevice.lo.txt -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1882242] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381760/+files/IpAddr.txt -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1882242] NetDevice.eno1.txt
apport information ** Attachment added: "NetDevice.eno1.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381762/+files/NetDevice.eno1.txt -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1882242] NetDevice.wlp2s0.txt
apport information ** Attachment added: "NetDevice.wlp2s0.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381764/+files/NetDevice.wlp2s0.txt -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1882242] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381765/+files/NetworkManager.conf.txt -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1882242] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381761/+files/IwConfig.txt -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1882242] Re: June 4th network-manager update kills wireless networking
apport information ** Tags added: apport-collected focal ** Description changed: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi-Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.2 + Architecture: amd64 + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-06-04 (4 days ago) + InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + IpRoute: + default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 + 169.254.0.0/16 dev wlp2s0 scope link metric 1000 + 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 + NetworkManager.state: + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + NonfreeKernelModules: wl + Package: network-manager 1.22.10-1ubuntu2.1 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_US + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 + Tags: focal + Uname: Linux 5.4.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + nmcli-dev: + DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH + wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 + eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- + lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- + nmcli-nm: + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.22.10 connected started full enabled enabled enabled enabled enabled ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381757/+files/CRDA.txt -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager
[Touch-packages] [Bug 1882242] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381758/+files/Dependencies.txt -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1882242] Re: June 4th network-manager update kills wireless networking
Need to report that the Broadcom BCM43228 wifi card intermittently shows the Wi-Fi networks. It will show them only occasionally; usually after a cold boot. If the machine is rebooted, the Wi-Fi networks disappear. Can anyone tell me how to test a wifi card for hardware failure? -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: New Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1882242/+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 1664844] Re: No distinction between link-up and link-down interfaces
Is there an updated target release for the ability to describe configuration for an interface (such as name) but leave the interface down at boot? -- 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/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Triaged Status in netplan: In Progress Status in netplan.io package in Ubuntu: In Progress Status in systemd package in Ubuntu: New Status in netplan.io source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in netplan.io source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in netplan.io source package in Artful: Won't Fix Bug description: [Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". [Test case] Write a netplan configuration: network: version: 2 renderer: networkd ethernets: eth0: optional: yes dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. [Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no addresses), it's not possible to determine if its adminStatus should be enabled (link up) or disabled (link down). I can completely exclude an interface from the netplan configuration, but I think that implies that not only its adminStatus is "disabled" by default, but also netplan will not be able to do anything "nice" for the interface, such as rename it to what the user specified in MAAS. If I include the interface but don't specify any addresses or DHCP, it isn't clear if it will be link up (my current assumption) or link down. There should be a way to allow an interface to be recognized by netplan (and even partially configured, waiting for the user to run something like 'ifup ' on a manual but not auto-started interface in ifupdown), but marked administratively disabled. (adminStatus down) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1664844/+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 1882242] [NEW] June 4th network-manager update kills wireless networking
Public bug reported: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi-Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: New Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no To
[Touch-packages] [Bug 1881533] Re: Remove expired AddTrust_External_Root.crt because it breaks software
Please ignore my mistake in the activity above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1881533 Title: Remove expired AddTrust_External_Root.crt because it breaks software Status in ca-certificates package in Ubuntu: In Progress Status in ca-certificates source package in Xenial: In Progress Status in ca-certificates source package in Bionic: In Progress Status in ca-certificates source package in Eoan: In Progress Status in ca-certificates source package in Focal: In Progress Status in ca-certificates source package in Groovy: In Progress Bug description: The AddTrust_External_Root.crt certificate has expired: Data: Version: 3 (0x2) Serial Number: 1 (0x1) Signature Algorithm: sha1WithRSAEncryption Issuer: C=SE, O=AddTrust AB, OU=AddTrust External TTP Network, CN=AddTrust External CA Root Validity Not Before: May 30 10:48:38 2000 GMT Not After : May 30 10:48:38 2020 GMT Subject: C=SE, O=AddTrust AB, OU=AddTrust External TTP Network, CN=AddTrust External CA Root Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (2048 bit) Modulus: This causes various client-side errors on Ubuntu 16.04 machines, about SSL certificate expiration, using (lib)curl for instance. Ubuntu 18.04 and up seem OK. Removing 'mozilla/AddTrust_External_Root.crt' from /etc/ca- certificates.conf and running 'update-ca-certificates -f -v' helps. I'm not sure if removing it is universally the best solution, but I can't find any other bug reports about this on Launchpad, and this seems the quickest way to fix all clients. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1881533/+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 1880679] Re: a
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1880679 Title: a Status in xorg package in Ubuntu: New Bug description: b ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:11:42 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.34, 5.3.0-46-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-51-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-53-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225c] InstallationDate: Installed on 2020-02-16 (99 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20KGS95F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=fc676807-153f-4991-8967-03aee78f1c55 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGS95F00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: EP26487 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KGS95F00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS95F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGS95F00 dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1880679/+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 1881139] Re: [80XL, Realtek Generic, Mic, Internal] No sound at all
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1881139 Title: [80XL, Realtek Generic, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: ubuntu-bug tested the microphone and everything is good but i have to sound when i want to speack using skype or what's app. microphone does not work inside the applications. regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nima 14089 F pulseaudio /dev/snd/pcmC0D0p: nima 14089 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 19:25:50 2020 InstallationDate: Installed on 2020-04-24 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nima 14089 F pulseaudio Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: No sound at all Title: [80XL, Realtek Generic, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN29WW:bd09/30/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 80XL dmi.product.sku: LENOVO_MT_80XL_BU_idea_FM_ideapad 320-15IKB dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1881139/+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 1873354] [NEW] Application icons don't show when external monitor connected
Public bug reported: If I connect an external display to my Lenovo Thinkpad T420 via display port (laptop screen main display) and click the Applications icon in the dock, I see a brief animation and then tiny little icons appear for a split second before vanishing. The application icons appear as normal if I disconnect my external display. I've attached a screenshot which I managed to take just as the tiny icons were vanishing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 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: Thu Apr 16 21:24:32 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T420 [17aa:21ce] InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 4236PA8 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-24-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET79WW (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 4236PA8 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET79WW(1.49):bd09/05/2016:svnLENOVO:pn4236PA8:pvrThinkPadT420:rvnLENOVO:rn4236PA8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T420 dmi.product.name: 4236PA8 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 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 ** Attachment added: "screenshot of application icons" https://bugs.launchpad.net/bugs/1873354/+attachment/5355750/+files/screenshot.png -- 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/1873354 Title: Application icons don't show when external monitor connected Status in xorg package in Ubuntu: New Bug description: If I connect an external display to my Lenovo Thinkpad T420 via display port (laptop screen main display) and click the Applications icon in the dock, I see a brief animation and then tiny little icons appear for a split second before vanishing. The application icons appear as normal if I disconnect my external display. I've attached a screenshot which I managed to take just as the tiny icons were vanishing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 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: Thu Apr 16 21:24:32 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T420 [17aa:21ce] InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 4236PA8 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-24-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2016
[Touch-packages] [Bug 1873072] Re: nmcli setting wrong value for username in config file
Do you have any more information about who this should be reported to? Like a url? -- 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/1873072 Title: nmcli setting wrong value for username in config file Status in network-manager package in Ubuntu: New Bug description: If you try to set the username for an openvpn VPN connection via the cli with the nmcli command, it will set the wrong value in the network manager system-connections config file. command example: nmcli connection modify vpn_name vpn.user-name my.username the file /etc/NetworkManager/system-connections/vpn_name.nmconnection will have the value vpn.user-name set to my.username This value is not used by network manager or openvpn when trying to create the VPN connection, the correct value is vpn.username. This is the value set by the GUI editor. This appears to be this exact bug reported to Redhat back in 2014. https://bugzilla.redhat.com/show_bug.cgi?id=1060460 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 16:29:36 2020 InstallationDate: Installed on 2020-02-13 (62 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev enx98e743e4fd54 proto dhcp metric 100 default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev enx98e743e4fd54 proto kernel scope link src 192.168.1.192 metric 100 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.193 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1873072/+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 1873072] [NEW] nmcli setting wrong value for username in config file
Public bug reported: If you try to set the username for an openvpn VPN connection via the cli with the nmcli command, it will set the wrong value in the network manager system-connections config file. command example: nmcli connection modify vpn_name vpn.user-name my.username the file /etc/NetworkManager/system-connections/vpn_name.nmconnection will have the value vpn.user-name set to my.username This value is not used by network manager or openvpn when trying to create the VPN connection, the correct value is vpn.username. This is the value set by the GUI editor. This appears to be this exact bug reported to Redhat back in 2014. https://bugzilla.redhat.com/show_bug.cgi?id=1060460 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 16:29:36 2020 InstallationDate: Installed on 2020-02-13 (62 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev enx98e743e4fd54 proto dhcp metric 100 default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev enx98e743e4fd54 proto kernel scope link src 192.168.1.192 metric 100 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.193 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1873072 Title: nmcli setting wrong value for username in config file Status in network-manager package in Ubuntu: New Bug description: If you try to set the username for an openvpn VPN connection via the cli with the nmcli command, it will set the wrong value in the network manager system-connections config file. command example: nmcli connection modify vpn_name vpn.user-name my.username the file /etc/NetworkManager/system-connections/vpn_name.nmconnection will have the value vpn.user-name set to my.username This value is not used by network manager or openvpn when trying to create the VPN connection, the correct value is vpn.username. This is the value set by the GUI editor. This appears to be this exact bug reported to Redhat back in 2014. https://bugzilla.redhat.com/show_bug.cgi?id=1060460 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 16:29:36 2020 InstallationDate: Installed on 2020-02-13 (62 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev enx98e743e4fd54 proto dhcp metric 100 default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev enx98e743e4fd54 proto kernel scope link src 192.168.1.192 metric 100 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.193 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1873072/+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 1864558] Re: Printer adds automatically at boot with notification or if printer deleted
The bug referenced above #1725955 goes back to 2017. This issue I describe has only started with focal 20.04 (I don't get the issue on 19.10 or any earlier release with the same laptop/network/printer setup). Even if I don't remove the printer I still get the notification that a my HP Envy wireless printer has been added each time I reboot, popping up on the Ubuntu logon/greeter screen. If I can help by providing more info or further testing please ask. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1864558 Title: Printer adds automatically at boot with notification or if printer deleted Status in cups package in Ubuntu: New Bug description: When booting 20.04 I get a notification on the logon screen each time advising that my wireless printer has been setup. If I remove the printer via settings, then as soon as it's removed, it gets re-added and I see the same notification as I do on the logon screen about the printer having been setup. I've attached a screenshot of this notification. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 21:49:43 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1864558/+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 1870748] Re: Authentication Window Stays Open
I attempted to make a change to a repository by launching Software & Updates and editing an unselected package from eoan to fossa - the authentication window persisted at the top left of my screen throughout - even after entering my credentials in the central authentication window that popped up (and went as normal) -- 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/1870748 Title: Authentication Window Stays Open Status in software-properties package in Ubuntu: New Bug description: I left the Beta of Focal Fossa running overnight and when I logged in this morning, I found an open Authentication window with the message "To change software repository settings, you need to authenticate" (see attached screenshot). I enter my password and the password field grey out. The window stays persistent but is "invisible" to the mouse - i.e. if I click anywhere in it, it actually clicks the thing behind it. The Cancel button does nothing. I had this same issue yesterday when actually running Software & Updates. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:55:33 2020 InstallationDate: Installed on 2020-01-24 (70 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1870748/+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 1870748] [NEW] Authentication Window Stays Open
Public bug reported: I left the Beta of Focal Fossa running overnight and when I logged in this morning, I found an open Authentication window with the message "To change software repository settings, you need to authenticate" (see attached screenshot). I enter my password and the password field grey out. The window stays persistent but is "invisible" to the mouse - i.e. if I click anywhere in it, it actually clicks the thing behind it. The Cancel button does nothing. I had this same issue yesterday when actually running Software & Updates. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:55:33 2020 InstallationDate: Installed on 2020-01-24 (70 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot of persistent Software & Updates authentication window" https://bugs.launchpad.net/bugs/1870748/+attachment/5346150/+files/Screenshot%20from%202020-04-04%2009-58-06.png -- 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/1870748 Title: Authentication Window Stays Open Status in software-properties package in Ubuntu: New Bug description: I left the Beta of Focal Fossa running overnight and when I logged in this morning, I found an open Authentication window with the message "To change software repository settings, you need to authenticate" (see attached screenshot). I enter my password and the password field grey out. The window stays persistent but is "invisible" to the mouse - i.e. if I click anywhere in it, it actually clicks the thing behind it. The Cancel button does nothing. I had this same issue yesterday when actually running Software & Updates. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:55:33 2020 InstallationDate: Installed on 2020-01-24 (70 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1870748/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1868706] Re: Snapd postinst script hangs
Pawel, this is great debugging, thank you. Agree it's an edge case. Mark -- 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/1868706 Title: Snapd postinst script hangs Status in snapd: Triaged Status in dpkg package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: On a machine which has been tracking upgrades for a while, I am unable to install new versions of snapd. The install process stalls indefinitely. Processes running suggest this is a hang in the postinst: ~$ ps ax | grep dpkg 2388 pts/1Ss+0:00 /usr/bin/dpkg --status-fd 25 --configure --pending 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2875 pts/2S+ 0:00 grep --color=auto dpkg ~$ pstree 2388 dpkg───snapd.postinst───systemctl───systemd-tty-ask ~$ ps ax | grep snapd 732 ?Ssl0:00 /usr/lib/snapd/snapd 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2452 pts/1S+ 0:00 /bin/systemctl start snapd.autoimport.service snapd.core-fixup.service snapd.recovery-chooser-trigger.service snapd.seeded.service snapd.service snapd.snap-repair.timer snapd.socket snapd.system-shutdown.service 2880 pts/2S+ 0:00 grep --color=auto snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1868706/+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 1868706] Re: Snapd postinst script hangs
OK, so *now* the situation has cleared on that machine. And there are no snaps installed :/ -- 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/1868706 Title: Snapd postinst script hangs Status in snapd: Triaged Status in dpkg package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: On a machine which has been tracking upgrades for a while, I am unable to install new versions of snapd. The install process stalls indefinitely. Processes running suggest this is a hang in the postinst: ~$ ps ax | grep dpkg 2388 pts/1Ss+0:00 /usr/bin/dpkg --status-fd 25 --configure --pending 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2875 pts/2S+ 0:00 grep --color=auto dpkg ~$ pstree 2388 dpkg───snapd.postinst───systemctl───systemd-tty-ask ~$ ps ax | grep snapd 732 ?Ssl0:00 /usr/lib/snapd/snapd 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2452 pts/1S+ 0:00 /bin/systemctl start snapd.autoimport.service snapd.core-fixup.service snapd.recovery-chooser-trigger.service snapd.seeded.service snapd.service snapd.snap-repair.timer snapd.socket snapd.system-shutdown.service 2880 pts/2S+ 0:00 grep --color=auto snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1868706/+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 1869035] Re: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1869035 Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 Status in pulseaudio package in Ubuntu: New Bug description: i wanted to install wine 5.0 and there is errors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpulse0 (not installed) ProcVersionSignature: Ubuntu 4.15.0-91.92~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.22 Architecture: amd64 Date: Wed Mar 25 16:57:57 2020 DuplicateSignature: package:libpulse0:(not installed) Unpacking libpulse0:i386 (1:8.0-0ubuntu3.10) ... dpkg: error processing archive /var/cache/apt/archives/libpulse0_1%3a8.0-0ubuntu3.10_i386.deb (--unpack): trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 InstallationDate: Installed on 2017-09-28 (908 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: pulseaudio Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1869035/+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 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
The problem exists on my system: Ubuntu 18.04LTS with Gnome Classic Desktop ASUS N3050M-E M/B with the Intel N3050 (Braswell) CPU VGA video connector (not HDMI) -- 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/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+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 1849156] Re: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed
Got bit by this as well, recall fixing it a few years ago but must have clobbered my changes on upgrade bionic -> eoan? Having VirtualBox installed broke it, fix was to comment out this line in /lib/systemdd/system/systemd-timesyncd.service.d and restart systemd: ConditionFileIsExecutable=!/usr/sbin/VBoxService Don't recall being asked about a config file change during upgrade although maybe it did and didn't remember. Further info here: https://askubuntu.com/questions/940311/time-in-ubuntu-16-04-not- updating-from-internet#1005355 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1849156 Title: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed Status in ntp package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in ntp source package in Eoan: Confirmed Status in systemd source package in Eoan: Confirmed Status in ntp source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Bug description: Ubuntu 19.10's systemd package introduced /lib/systemd/system/systemd- timesyncd.service.d/disable-with-time-daemon.conf. This prevents systemd-timesyncd.service from starting if the ntp package has been installed. However, ntp.service has a Conflicts directive for systemd-timesyncd.service. If both services are enabled, neither will start on boot. This breaks upgrades from < 19.10 to 19.10 for systems that have both ntp and systemd installed. Possible workarounds: - Uninstall ntp - Disable systemd-timesyncd.service % lsb_release -rd Description:Ubuntu 19.10 Release:19.10 % apt-cache policy systemd systemd: Installed: 242-7ubuntu3 Candidate: 242-7ubuntu3 Version table: *** 242-7ubuntu3 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status % apt-cache policy ntp ntp: Installed: 1:4.2.8p12+dfsg-3ubuntu2 Candidate: 1:4.2.8p12+dfsg-3ubuntu2 Version table: *** 1:4.2.8p12+dfsg-3ubuntu2 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status % dpkg -S /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf systemd: /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf % sudo systemctl status ntp ● ntp.service - Network Time Service Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: man:ntpd(8) % sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-timesyncd.service.d └─disable-with-time-daemon.conf Active: inactive (dead) Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago Docs: man:systemd-timesyncd.service(8) Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network Time Synchronization being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1849156/+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 1860929] Re: Should include a /usr/bin/python symlink unless..
Is this a written policy / guidance or just something you came up with on the fly? https://blogs.gnome.org/mcatanzaro/2018/02/16/on-python-shebangs/ has a good discussion of this issue and even suggests using python2.7 (as opposed to python2) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1860929 Title: Should include a /usr/bin/python symlink unless.. Status in python2.7 package in Ubuntu: Invalid Bug description: Unless there is some plan to reuse /usr/bin/python for python3.x If not or if not in 20.04 then this package should also include a /usr/bin/python symlink to either /usr/bin/python2 or /usr/bin/python2.7 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python2.7-minimal 2.7.17-1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 26 12:52:07 2020 InstallationDate: Installed on 2020-01-13 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: python2.7 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1860929/+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 1852922] Re: Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285
Please find the attached dumpfile ** Attachment added: "RtHDDump.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852922/+attachment/5306147/+files/RtHDDump.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1852922 Title: Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285 Status in alsa-driver package in Ubuntu: New Bug description: I have just installed Ubuntu 19.10 with Kernel 5.3 on my HP Envy 13. Everything works just fine except the microphone which is not being detected at all. My alsa-info output: http://alsa- project.org/db/?f=1d22f0563bc25ea1ebe609a8482e5f39081abdc2 System info: Description: Ubuntu 19.10 Release: 19.10 Alsa version: alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://pl.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852922/+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 1852922] Re: Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285
Yes, the internal microphone works perfectly fine in Windows 10 and is being detected as Intel Smart Sound -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1852922 Title: Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285 Status in alsa-driver package in Ubuntu: New Bug description: I have just installed Ubuntu 19.10 with Kernel 5.3 on my HP Envy 13. Everything works just fine except the microphone which is not being detected at all. My alsa-info output: http://alsa- project.org/db/?f=1d22f0563bc25ea1ebe609a8482e5f39081abdc2 System info: Description: Ubuntu 19.10 Release: 19.10 Alsa version: alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://pl.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852922/+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 1852922] [NEW] Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285
Public bug reported: I have just installed Ubuntu 19.10 with Kernel 5.3 on my HP Envy 13. Everything works just fine except the microphone which is not being detected at all. My alsa-info output: http://alsa- project.org/db/?f=1d22f0563bc25ea1ebe609a8482e5f39081abdc2 System info: Description:Ubuntu 19.10 Release:19.10 Alsa version: alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://pl.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1852922 Title: Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285 Status in alsa-driver package in Ubuntu: New Bug description: I have just installed Ubuntu 19.10 with Kernel 5.3 on my HP Envy 13. Everything works just fine except the microphone which is not being detected at all. My alsa-info output: http://alsa- project.org/db/?f=1d22f0563bc25ea1ebe609a8482e5f39081abdc2 System info: Description: Ubuntu 19.10 Release: 19.10 Alsa version: alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://pl.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852922/+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 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)
Has this been fixed? I'm using Ubuntu 18.04 with gnome desktop and the ctrl alt print screen is not always reliable. I'm using Shutter as a work around for the mean while. -- 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/1732612 Title: Alt+Printscreen not working (doesn't generate keypress event) Status in systemd package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on my computer. I'm using Unity DE, with default settings. The problem is not about taking screnshots. xev recognizes when I press down the alt key, but nothing happens when I press Print Screen with alt being pressed (it does when PrintScreen is pressed by itself) Here is evtest output when I press Alt+Printscreen: # Alt pressed down: Event: time 1510817663.883489, -- SYN_REPORT Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.923476, -- SYN_REPORT Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.963479, -- SYN_REPORT Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046 # Print screen pressed Event: time 1510817663.993036, -- SYN_REPORT Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 # Alt released Event: time 1510817664.945032, -- SYN_REPORT Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1 Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1 Event: time 1510817664.945086, -- SYN_REPORT Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0 Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 Event: time 1510817664.945097, -- SYN_REPORT ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules Date: Thu Nov 16 08:29:46 2017 InstallationDate: Installed on 2017-03-26 (234 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732612/+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