[Touch-packages] [Bug 1877505] Re: Intel VGA Driver
The attached logs don't show any major problems other than the resolution is limited to 1024x768. Is that what you mean, or are you trying to report some other issue? ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1877505 Title: Intel VGA Driver Status in xorg-server package in Ubuntu: Incomplete Bug description: intel VGA driver not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 허가 거부: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 13:37:18 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1458:d000] InstallationDate: Installed on 2020-05-07 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ko_KR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=90d59d88-1dd5-47c9-aba6-431170fc5f32 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Fce dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-S2PV REV 2.2 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.:bvrFce:bd03/03/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S2PVREV2.2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1877505/+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 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1874257 Title: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS Status in linux package in Ubuntu: Invalid Status in openssh package in Ubuntu: Incomplete Status in openvpn package in Ubuntu: Incomplete Bug description: Hello Team, SSH timeout issue, once connect to VPN. Environment == Dell XPS 9570 Ubuntu 16.04.6 Xenial Xerus) kernel - 4.15.0-55-generic $dpkg -l | grep -i openssh ii openssh-client 1:7.2p2-4ubuntu2.8 --> ii openssh-server 1:7.2p2-4ubuntu2.8 ii openssh-sftp-server 1:7.2p2-4ubuntu2.8 VPN tunnel info vpn0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:IP P-t-P:xx Mask:255.255.252.0 inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1406 Metric:1 RX packets:962 errors:0 dropped:0 overruns:0 frame:0 TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:87839 (87.8 KB) TX bytes:238740 (238.7 KB) Issue Unable to connect to any host via ssh or sftp after VPN connection Tried = Reinstalled the openssh-client package and still no luck. May I know why the default cipher is not taking/hanging? Please let me know . There were no recent changes. Workaround === Able to connect to ssh / sftp $ssh -c aes128-ctr user@IP Below is the debug ssh client logs === == $ssh -vvv user@ip OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g 1 Mar 2016 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: resolving "IP" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to IP [IP] port 22. debug1: Connection established. debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to IP:22 as 'user' debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c debug2: host key algorithms: ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa debug2: ciphers ctos: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc debug2: ciphers stoc: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc debug2: MACs ctos: umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc:
[Touch-packages] [Bug 1877505] [NEW] Intel VGA Driver
Public bug reported: intel VGA driver not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 허가 거부: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 13:37:18 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1458:d000] InstallationDate: Installed on 2020-05-07 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ko_KR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=90d59d88-1dd5-47c9-aba6-431170fc5f32 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Fce dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-S2PV REV 2.2 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.:bvrFce:bd03/03/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S2PVREV2.2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.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 -- 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/1877505 Title: Intel VGA Driver Status in xorg package in Ubuntu: New Bug description: intel VGA driver not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 허가 거부: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 13:37:18 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1458:d000] InstallationDate: Installed on 2020-05-07 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M /: Bus 01.Port 1: Dev 1,
[Touch-packages] [Bug 1877473] Re: Upgrading from 18.04 to 20.04 encrypted installation with LUKS and LVM makes it unbootable without manual intervention
** Summary changed: - Upgrading from 18.04 to 20.04 encrypted installation with LUKS and LVM unbootable without manual intervention + Upgrading from 18.04 to 20.04 encrypted installation with LUKS and LVM makes it unbootable without manual intervention -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1877473 Title: Upgrading from 18.04 to 20.04 encrypted installation with LUKS and LVM makes it unbootable without manual intervention Status in lvm2 package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Volume Group metadata had to be upgraded manually with vgck --updatemetadata yourvgname The VG name was somehow changed from lvm-name to just name and I had to edit /etc/crypttab and update-initramfs -u -k all Also cryptsetup-initramfs package was deleted for some reason, had to re-install it in chroot. Maybe it happened because I have disabled installing recommended and suggested packages or maybe because none of *buntu-desktop packages are installed on my system. Not sure if I have to report it as a separate problem, please advise. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri May 8 01:35:04 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1877473/+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 1877502] [NEW] package cups-core-drivers 2.2.12-2ubuntu1.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado
Public bug reported: I don't know to tell you about the fail. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: cups-core-drivers 2.2.12-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Fri May 8 01:15:08 2020 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2019-11-19 (170 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Inspiron 5437 Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=d3150b7f-3c9a-4bc8-ac65-8e341339d22b ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=d3150b7f-3c9a-4bc8-ac65-8e341339d22b ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: cups Title: package cups-core-drivers 2.2.12-2ubuntu1.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 01PN4H dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/09/2019:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn01PN4H:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5437 dmi.product.sku: Inspiron 5437 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- 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/1877502 Title: package cups-core-drivers 2.2.12-2ubuntu1.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado Status in cups package in Ubuntu: New Bug description: I don't know to tell you about the fail. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: cups-core-drivers 2.2.12-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Fri May 8 01:15:08 2020 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2019-11-19 (170 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Inspiron 5437 Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=d3150b7f-3c9a-4bc8-ac65-8e341339d22b ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=d3150b7f-3c9a-4bc8-ac65-8e341339d22b ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: cups Title: package cups-core-drivers 2.2.12-2ubuntu1.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 01PN4H dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/09/2019:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn01PN4H:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5437 dmi.product.sku: Inspiron 5437 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1877502/+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.
This is even more important now, with many people working/learning from home... -- 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. Status in PulseAudio: New Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed 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 1871185] Re: urls in ubuntu-bugs dialog not really clickable
This bug was fixed in the package apport - 2.20.11-0ubuntu33 --- apport (2.20.11-0ubuntu33) groovy; urgency=medium [ Olivier Tilloy ] * gtk/apport-gtk: upgrade regular expression used to match URLs in free text (LP: #1871185) -- Brian Murray Thu, 07 May 2020 14:54:20 -0700 ** Changed in: apport (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1871185 Title: urls in ubuntu-bugs dialog not really clickable Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Triaged Bug description: when ubuntu-bug report suggests filing a bug report directly in launchpad for snap packages, the displayed url is clickable but the url stops at the first + symbol. see attachment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.8 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashReports: 640:1000:124:8919925:2020-03-29 20:16:13.456640958 +0200:2020-03-29 20:16:14.456640958 +0200:/var/crash/_usr_bin_python3.7.1000.crash CurrentDesktop: XFCE Date: Mon Apr 6 19:50:16 2020 InstallationDate: Installed on 2020-03-18 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1871185/+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 1876230] Re: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED
Sorry to jump in, I wrote the membarrier syscall LTP interface test (https://github.com/linux-test- project/ltp/blob/master/testcases/kernel/syscalls/membarrier/membarrier01.c) when I was at Linaro and felt attracted to reading all this during my bug triage day =). So, for MEMBARRIER_CMD_PRIVATE_EXPEDITED, you said at the description: " It only targets threads which share the same mm as the thread calling the membarrier syscall " And it occurred to me right away: "Are there any dependencies using liburcu and Shared Mem IPC" ? Mainly because the private expedited only guarantees the barrier - for the RCU graceful period - among sibling tasks sharing the same address space and thread id (which share the same mm) -> of course this explains why it is much faster, specially in an OS containing tons of running tasks.. or even worse: in a VM with tons of running tasks PLUS vcpus coming in and out the real ones. So, I think my message here, specially for the SRU team, as this is changing the behavior of librcu library for a LTS version, is: - apart from feedback given by @mruffell, to also check if any of librcu consumers are depending on a full membarrier - driven by kernel - for ** shared pages among different processes ** before accepting this as a SRU. Or else we're changing synchronization primitives of all dependencies and this would not be good =o). I think this criteria may also help in the SRU acceptance ^ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to liburcu in Ubuntu. https://bugs.launchpad.net/bugs/1876230 Title: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED Status in liburcu package in Ubuntu: Fix Released Status in liburcu source package in Bionic: In Progress Bug description: [Impact] In Linux 4.3, a new syscall was defined, called "membarrier". This systemcall was defined specifically for use in userspace-rcu (liburcu) to speed up the fast path / reader side of the library. The original implementation in Linux 4.3 only supported the MEMBARRIER_CMD_SHARED subcommand of the membarrier syscall. MEMBARRIER_CMD_SHARED executes a memory barrier on all threads from all processes running on the system. When it exits, the userspace thread which called it is guaranteed that all running threads share the same world view in regards to userspace addresses which are consumed by readers and writers. The problem with MEMBARRIER_CMD_SHARED is system calls made in this fashion can block, since it deploys a barrier across all threads in a system, and some other threads can be waiting on blocking operations, and take time to reach the barrier. In Linux 4.14, this was addressed by adding the MEMBARRIER_CMD_PRIVATE_EXPEDITED command to the membarrier syscall. It only targets threads which share the same mm as the thread calling the membarrier syscall, aka, threads in the current process, and not all threads / processes in the system. Calls to membarrier with the MEMBARRIER_CMD_PRIVATE_EXPEDITED command are guaranteed non-blocking, due to using inter-processor interrupts to implement memory barriers. Because of this, membarrier calls that use MEMBARRIER_CMD_PRIVATE_EXPEDITED are much faster than those that use MEMBARRIER_CMD_SHARED. Since Bionic uses a 4.15 kernel, all kernel requirements are met, and this SRU is to enable support for MEMBARRIER_CMD_PRIVATE_EXPEDITED in the liburcu package. This brings the performance of the liburcu library back in line to where it was in Trusty, as this particular user has performance problems upon upgrading from Trusty to Bionic. [Test] Testing performance is heavily dependant on the application which links against liburcu, and the workload which it executes. A test package is available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf276198-test For the sake of testing, we can use the benchmarks provided in the liburcu source code. Download a copy of the source code for liburcu either from the repos or from github: $ pull-lp-source liburcu bionic # OR $ git clone https://github.com/urcu/userspace-rcu.git $ git checkout v0.10.1 # version in bionic Build the code: $ ./bootstrap $ ./configure $ make Go into the tests/benchmark directory $ cd tests/benchmark From there, you can run benchmarks for the four main usages of liburcu: urcu, urcu-bp, urcu-signal and urcu-mb. On a 8 core machine, 6 threads for readers and 2 threads for writers, with a 10 second runtime, execute: $ ./test_urcu 6 2 10 $ ./test_urcu_bp 6 2 10 $ ./test_urcu_signal 6 2 10 $ ./test_urcu_mb 6 2 10 Results: ./test_urcu 6 2 10 0.10.1-1: 17612527667 reads, 268 writes, 17612527935 ops 0.10.1-1ubuntu1: 14988437247 reads, 810069 writes, 14989247316 ops $ ./test_urcu_bp 6 2 10 0.10.1-1: 1177891079
[Touch-packages] [Bug 1838577] Re: Default audio device changes on reboot; audio still outputs using my previously-selected device
*** This bug is a duplicate of bug 1877194 *** https://bugs.launchpad.net/bugs/1877194 I think bug 1877194 is actually tracking this now. So let's use that (?). ** This bug is no longer a duplicate of bug 1866194 External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. ** This bug has been marked a duplicate of bug 1877194 switch-on-connect mistakes startup for USB hotplug -- 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/1838577 Title: Default audio device changes on reboot; audio still outputs using my previously-selected device Status in pulseaudio package in Ubuntu: New Bug description: This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It was not present in Ubuntu 16.04. I have a USB microphone which also appears to pulse as a speaker. Pulse keeps picking it as the default audio device. I can switch audio devices to my analog line out, which works as expected until I reboot. After reboot, my audio device switches back to the USB "speaker", and Gnome shell / Gnome settings volume control adjusts the USB speaker volume. Despite seeing the USB device as the current output device, I still hear sound from my line-out. In the interest of narrowing down this bug, I have found that disabling "module-switch-on-connect" fixes the problem (my line-out stays as the default audio device and I hear sound). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 31 17:39:38 2019 InstallationDate: Installed on 2019-07-31 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4207 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838577/+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 1877269] Re: Ubuntu crashes multiple time due to pulse audio. (alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large)
Please try using 'apport-cli' instead of 'ubuntu-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/1877269 Title: Ubuntu crashes multiple time due to pulse audio. (alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Description: Ubuntu 18.04.4 LTS Release: 18.04 pulseaudio: Installé : 1:11.1-1ubuntu7.5 Candidat : 1:11.1-1ubuntu7.5 Table de version : *** 1:11.1-1ubuntu7.5 500 500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages The OS freezes when using in normal conditions, usually VS Code, Discord app and Spotify in browser. When it does, I need to hard reboot by holding power button. I checked journalctl to confirm it was due to pulseaudio. alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large The above line is always the last to prompt in the boot journal. It does not freeze instantly, it progressively freezes down, but sometime Mozilla Firefox crashes and it freezes no more. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.5 Uname: Linux 5.1.15-surface-linux-surface x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: saravanane 2071 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 7 11:00:37 2020 InstallationDate: Installed on 2019-10-01 (218 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 108.2706.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr108.2706.768:bd04/18/2019:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B09F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.sku: Surface_Pro_4 dmi.product.version: D:0B:09F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877269/+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 1877496] [NEW] focal sshd snubs VX Connectbot
Public bug reported: what is the subtle change to sshd such that now VX Connectbot no longer gets any response? VX Connectbot can connect to the bionic sshd just fine, even if it's running on the focal kernel. but gets no response from the focal sshd. what's up with that? yes meanwhile it works fine to connect to the focal sshd from elsewhere eg from the bionic ssh client. so what's the subtle snub to VX Connectbot? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 7 21:21:26 2020 InstallationDate: Installed on 2020-03-15 (53 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal regression-release -- 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/1877496 Title: focal sshd snubs VX Connectbot Status in openssh package in Ubuntu: New Bug description: what is the subtle change to sshd such that now VX Connectbot no longer gets any response? VX Connectbot can connect to the bionic sshd just fine, even if it's running on the focal kernel. but gets no response from the focal sshd. what's up with that? yes meanwhile it works fine to connect to the focal sshd from elsewhere eg from the bionic ssh client. so what's the subtle snub to VX Connectbot? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 7 21:21:26 2020 InstallationDate: Installed on 2020-03-15 (53 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1877496/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
@Jamie, just want to highlight that there is an urgent fix in Bionic to an OEM platform which is waiting for this update to be done before we can land it. It'd be very much appreciated if we can somehow speed up the process. Thank you. -- 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/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1877194] Re: switch-on-connect mistakes startup for USB hotplug
** Also affects: pulseaudio via https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/886 Importance: Unknown Status: Unknown -- 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/1877194 Title: switch-on-connect mistakes startup for USB hotplug Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Triaged Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
please install a higher version kernel like 5.4.0-28/29 first, boot with the new kernel, then sudo dpkg -r --force-all linux-image- unsigned-5.4.0-26-generic, install the v4 testing kernel to do the test. I installed the v4 testing kernel on my machine, there is no errors: hwang4@hwang4-Vostro-5390:/tmp$ sudo dpkg -i *.deb [sudo] password for hwang4: Selecting previously unselected package linux-image-unsigned-5.4.0-26-generic. (Reading database ... 393690 files and directories currently installed.) Preparing to unpack linux-image-unsigned-5.4.0-26-generic_5.4.0-26.30+skipv4_amd64.deb ... Unpacking linux-image-unsigned-5.4.0-26-generic (5.4.0-26.30+skipv4) ... Selecting previously unselected package linux-modules-5.4.0-26-generic. Preparing to unpack linux-modules-5.4.0-26-generic_5.4.0-26.30+skipv4_amd64.deb ... Unpacking linux-modules-5.4.0-26-generic (5.4.0-26.30+skipv4) ... Selecting previously unselected package linux-modules-extra-5.4.0-26-generic. Preparing to unpack linux-modules-extra-5.4.0-26-generic_5.4.0-26.30+skipv4_amd64.deb ... Unpacking linux-modules-extra-5.4.0-26-generic (5.4.0-26.30+skipv4) ... Setting up linux-modules-5.4.0-26-generic (5.4.0-26.30+skipv4) ... Setting up linux-image-unsigned-5.4.0-26-generic (5.4.0-26.30+skipv4) ... I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.3.0-46-generic I: /initrd.img.old is now a symlink to boot/initrd.img-5.3.0-46-generic I: /vmlinuz is now a symlink to boot/vmlinuz-5.4.0-26-generic I: /initrd.img is now a symlink to boot/initrd.img-5.4.0-26-generic Setting up linux-modules-extra-5.4.0-26-generic (5.4.0-26.30+skipv4) ... Processing triggers for linux-image-unsigned-5.4.0-26-generic (5.4.0-26.30+skipv4) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.4.0-26-generic Error! Your kernel headers for kernel 5.4.0-26-generic cannot be found. Please install the linux-headers-5.4.0-26-generic package, or use the --kernelsourcedir option to tell DKMS where it's located Error! The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. This indicates that it should not be built. ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-26-generic /etc/kernel/postinst.d/zz-update-grub: Sourcing file `/etc/default/grub' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.4.0-26-generic Found initrd image: /boot/initrd.img-5.4.0-26-generic Found linux image: /boot/vmlinuz-5.3.0-46-generic Found initrd image: /boot/initrd.img-5.3.0-46-generic Found linux image: /boot/vmlinuz-5.0.0-1042-oem-osp1 Found initrd image: /boot/initrd.img-5.0.0-1042-oem-osp1 Found linux image: /boot/vmlinuz-5.0.0-1037-oem-osp1 Found initrd image: /boot/initrd.img-5.0.0-1037-oem-osp1 Found linux image: /boot/vmlinuz-5.0.0-1034-oem-osp1 Found initrd image: /boot/initrd.img-5.0.0-1034-oem-osp1 Adding boot menu entry for EFI firmware configuration done -- 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/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 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 failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600
[Touch-packages] [Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update
Hi! I have an Asus Zenbook UX331 with Linux Mint 19.3 Kernel version 5.3.0-51 and dual-boot with Windows 10. This laptop has the same audio device (ALC 294) as this thread is about. My problem is that the audio speakers sound kind of clunky and distorted after dual-booting from Windows to Linux. A fully shutting down and then booting in linux solves the issue but I need to boot on W10 first as I use Asus Battery Health Charging to cap my battery percentage on 60 so I can keep my laptop plugged in. I've tried many workarounds and possible fixes but the only way I could fix this was uninstalling Realtek Audio Device and High Audio Definition Device on Windows 10. Altough this is not a permanent fix as it sometimes doesn't work (probably because windows reinstall this drivers when it detect they aren't installed) and I have no sound in Windows without this drivers. I would be more than happy to provide further info about my system in order to know what is really happening. -- 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/1742852 Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a windows update I lost all the sound on my ubuntu machine. It's the second time that this happends. My sound is unmuted and at a loud level and nothing is comming out of my speakers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer CurrentDesktop: Unity Date: Thu Jan 11 22:21:23 2018 InstallationDate: Installed on 2017-11-29 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+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 1764172] Re: Unable to change hostname from the one specified during Bionic server installation
This got fixed quite a while ago I think, apologies for the lack of updates. ** Changed in: subiquity Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hostname in Ubuntu. https://bugs.launchpad.net/bugs/1764172 Title: Unable to change hostname from the one specified during Bionic server installation Status in subiquity: Fix Released Status in Release Notes for Ubuntu: New Status in hostname package in Ubuntu: Confirmed Bug description: In Bionic Beta 2 I am not able on a host or in a guest VM to change the hostname of a Bionic Beta 2 installation by changing /etc/hostname. The name in the file can be changed but it always reverts to the hostname configured during installation. In the following thread on the topic it is suggested to remove a number of cloud packages. When doing this in a VM install I could change the hostname again via /etc/hostname. https://ubuntuforums.org/showthread.php?t=2389098=2 To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1764172/+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 1876987] Re: Option to show submitting URL instead of opening it in the default browser
Workarounded it with a custom URL dispatcher https://github.com/int- ua/openbydomain -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1876987 Title: Option to show submitting URL instead of opening it in the default browser Status in apport package in Ubuntu: New Bug description: It's currently quite hard to open link in non-default browser because it gets redirected to login page. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 600:0:130:360439:2020-05-05 20:24:23.870903500 +0300:2020-05-05 20:24:23.858903500 +0300:/var/crash/initramfs-tools.0.crash 640:0:130:24515:2020-05-05 18:19:14.458007423 +0300:2020-05-05 18:19:14.458007423 +0300:/var/crash/_usr_share_apport_package_hook.0.crash 640:0:130:686494:2020-05-05 18:19:13.117986838 +0300:2020-05-05 18:19:13.097986531 +0300:/var/crash/desktop-base.0.crash 640:1000:130:656729:2020-05-05 18:37:26.329201185 +0300:2020-05-05 18:37:26.257200250 +0300:/var/crash/_usr_bin_kglobalaccel5.1000.crash CurrentDesktop: KDE Date: Tue May 5 23:54:48 2020 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1876987/+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 1877473] Re: Upgrading from 18.04 to 20.04 installation requires manual intervention for system with LUKS and LVM to be bootable
** Summary changed: - Upgrading from 18.04 to 20.04 installation requires manual intervention for system to be bootable + Upgrading from 18.04 to 20.04 installation requires manual intervention for system with LUKS and LVM to be bootable ** Summary changed: - Upgrading from 18.04 to 20.04 installation requires manual intervention for system with LUKS and LVM to be bootable + Upgrading from 18.04 to 20.04 encrypted installation with LUKS and LVM unbootable without manual intervention -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1877473 Title: Upgrading from 18.04 to 20.04 encrypted installation with LUKS and LVM unbootable without manual intervention Status in lvm2 package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Volume Group metadata had to be upgraded manually with vgck --updatemetadata yourvgname The VG name was somehow changed from lvm-name to just name and I had to edit /etc/crypttab and update-initramfs -u -k all Also cryptsetup-initramfs package was deleted for some reason, had to re-install it in chroot. Maybe it happened because I have disabled installing recommended and suggested packages or maybe because none of *buntu-desktop packages are installed on my system. Not sure if I have to report it as a separate problem, please advise. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri May 8 01:35:04 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1877473/+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 1871185] Re: urls in ubuntu-bugs dialog not really clickable
** Changed in: apport (Ubuntu Focal) Milestone: None => ubuntu-20.04.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1871185 Title: urls in ubuntu-bugs dialog not really clickable Status in apport package in Ubuntu: In Progress Status in apport source package in Focal: Triaged Bug description: when ubuntu-bug report suggests filing a bug report directly in launchpad for snap packages, the displayed url is clickable but the url stops at the first + symbol. see attachment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.8 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashReports: 640:1000:124:8919925:2020-03-29 20:16:13.456640958 +0200:2020-03-29 20:16:14.456640958 +0200:/var/crash/_usr_bin_python3.7.1000.crash CurrentDesktop: XFCE Date: Mon Apr 6 19:50:16 2020 InstallationDate: Installed on 2020-03-18 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1871185/+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 1877473] [NEW] Upgrading from 18.04 to 20.04 installation requires manual intervention for system with LUKS and LVM to be bootable
Public bug reported: Volume Group metadata had to be upgraded manually with vgck --updatemetadata yourvgname The VG name was somehow changed from lvm-name to just name and I had to edit /etc/crypttab and update-initramfs -u -k all Also cryptsetup-initramfs package was deleted for some reason, had to re-install it in chroot. Maybe it happened because I have disabled installing recommended and suggested packages or maybe because none of *buntu-desktop packages are installed on my system. Not sure if I have to report it as a separate problem, please advise. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri May 8 01:35:04 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1877473 Title: Upgrading from 18.04 to 20.04 installation requires manual intervention for system with LUKS and LVM to be bootable Status in lvm2 package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Volume Group metadata had to be upgraded manually with vgck --updatemetadata yourvgname The VG name was somehow changed from lvm-name to just name and I had to edit /etc/crypttab and update-initramfs -u -k all Also cryptsetup-initramfs package was deleted for some reason, had to re-install it in chroot. Maybe it happened because I have disabled installing recommended and suggested packages or maybe because none of *buntu-desktop packages are installed on my system. Not sure if I have to report it as a separate problem, please advise. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri May 8 01:35:04 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1877473/+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 1862846] Re: Crash and failure installing focal
** Changed in: subiquity Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1862846 Title: Crash and failure installing focal Status in subiquity: Fix Released Status in curtin package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Fix Released Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: Fix Released Status in curtin source package in Focal: Fix Released Status in util-linux source package in Focal: Fix Released Status in util-linux package in Debian: Fix Released Bug description: [Impact] * lsblk no longer prints a partition's parent kernel device name (the wholedisk). (i.e., 'lsblk -no PKNAME /dev/partition') * Another impact is the 'removable media' check always return zero for partitions. (i.e., 'lsblk -no RM /dev/partition') * The regression was introduced on v2.34, only Eoan (v2.34) and later are affected. Disco (v2.33) and earlier are not affected. * The regression is fixed in v2.35, in commit e3bb9bfb76c1 ("lsblk: force to print PKNAME for partition"); fixes RM for partition too. [Test Case] * $ lsblk -no PKNAME /dev/vda1 # partition * Expected output: vda # wholedisk * Current output: (nothing) * $ lsblk -no RM /dev/sdb1 # partition in removable disk * Expected output: 1 # removable media * Current output: 0 # not removable media [Regression Potential] * Columns that depend on a partition device's parent device (i.e., seen as 'wholedisk') could in theory show incorrect values if another bug is present in v2.34 for that. * Other usages of 'parent' pointer in the function have been examined and reported (e.g. issue w/ removable media column), and others found to not have issues (e.g. --merge option, to group multiple parents of a device, as in RAID.) [Other Info] * The impacts to the curtin source package have been addressed in other way, it no longer requires util-linux, comment #14. * util-linux github issue: https://github.com/karelzak/util-linux/issues/813 [Original Bug Description] During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+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 1871185] Re: urls in ubuntu-bugs dialog not really clickable
** Also affects: apport (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Focal) Status: New => Triaged ** Changed in: apport (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1871185 Title: urls in ubuntu-bugs dialog not really clickable Status in apport package in Ubuntu: In Progress Status in apport source package in Focal: Triaged Bug description: when ubuntu-bug report suggests filing a bug report directly in launchpad for snap packages, the displayed url is clickable but the url stops at the first + symbol. see attachment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.8 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashReports: 640:1000:124:8919925:2020-03-29 20:16:13.456640958 +0200:2020-03-29 20:16:14.456640958 +0200:/var/crash/_usr_bin_python3.7.1000.crash CurrentDesktop: XFCE Date: Mon Apr 6 19:50:16 2020 InstallationDate: Installed on 2020-03-18 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1871185/+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 1877458] [NEW] cd ../gcc in a directory ajacent to gcc causes the page to go to gcc/gcc
Public bug reported: This happened in the ~/Downloads directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 7 17:28:53 2020 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1877458 Title: cd ../gcc in a directory ajacent to gcc causes the page to go to gcc/gcc Status in bash package in Ubuntu: New Bug description: This happened in the ~/Downloads directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 7 17:28:53 2020 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1877458/+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 1869155] Re: When installing with subiquity, the generated network config uses the macaddress keyword on s390x (where MAC addresses are not necessarily stable across reboots)
** Changed in: subiquity Status: New => Fix Released ** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-z-systems Status: New => Fix Released ** Changed in: cloud-init Status: Incomplete => Invalid -- 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/1869155 Title: When installing with subiquity, the generated network config uses the macaddress keyword on s390x (where MAC addresses are not necessarily stable across reboots) Status in cloud-init: Invalid Status in subiquity: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Bug description: While performing a subiquity focal installation on an s390x LPAR (where the LPAR is connected to a VLAN trunk) I saw a section like this: match: macaddress: 02:28:0b:00:00:53 So the macaddress keyword is used, but on several s390x machine generation MAC addresses are not necessarily stable and uniquie across reboots. (z14 GA2 and newer system have in between a modified firmware that ensures that MAC addresses are stable and uniquire across reboots, but for z14 GA 1 and older systems, incl. the z13 that I used this is not the case - and a backport of the firmware modification is very unlikely) The configuration that I found is this: $ cat /etc/netplan/50-cloud-init.yaml # This file is generated from information provided by the datasource. Changes # to it will not persist across an instance reboot. To disable cloud-init's # network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} network: ethernets: enc600: addresses: - 10.245.236.26/24 gateway4: 10.245.236.1 match: macaddress: 02:28:0b:00:00:53 nameservers: addresses: - 10.245.236.1 set-name: enc600 version: 2 (This is a spin-off of ticket LP 1868246.) It's understood that the initial idea for the MAC addresses was to have a unique identifier, but I think with the right tooling (ip, ifconfig, ethtool or even the network-manager UI) you can even change MAC addresses today on other platforms. Nowadays interface names are based on their underlying physical device/address (here in this case '600' or to be precise '0600' - leading '0' are removed), which makes the interface and it's name already quite unique - since it is not possible to have two devices (in one system) with the exact same address. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1869155/+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 1870408] Re: casper-md5check should leave a breadcrumb which apport, ubiquity, subiquity could use
(was fixed in subiquity for release) ** Changed in: subiquity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1870408 Title: casper-md5check should leave a breadcrumb which apport, ubiquity, subiquity could use Status in subiquity: Fix Released Status in apport package in Ubuntu: Fix Released Status in casper package in Ubuntu: In Progress Status in ubiquity package in Ubuntu: New Bug description: casper-md5check should leave a breadcrumb which apport & ubiquity can pick up. (subiquity too) There will be a file called: /run/casper-md5check.json If it does not exist, or is empty the check did not run enough to validate anything. Treat as skip. If it has content it will have: { "checksum_missmatch" : [ "./pics/red-upperleft.png", "./pics/red-lowerleft.png" ], "result" : "fail" } optional checksum_missmatch key, which will have a list of strings that are files that failed md5sum. result key, which can have string values "pass" "fail" "skip". One can use python's json or yaml safe_load to parse the file into a dictionary. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1870408/+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 1871439] Re: subiquity should detect when apport crashes collecting crash report
I'm not sure what this bug is asking for any more. ** Changed in: subiquity Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1871439 Title: subiquity should detect when apport crashes collecting crash report Status in subiquity: Incomplete Status in apport package in Ubuntu: New Bug description: apport i think needs a crash handler, to stop apport crashes, when it crahes during crash collection. not sure if subiquity can detect that. see https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1871434 To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1871439/+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 1877181] Re: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1877181 Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Happening while trying to upgrade from 18.04 to 20.04. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 6 14:26:11 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-03-10 (2249 days ago) InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1877181/+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 1877456] Re: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1877181 *** https://bugs.launchpad.net/bugs/1877181 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1877181, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1877181 package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools 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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1877456 Title: package initramfs-tools 0.136ubuntu6 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: Error occured during update from Ubuntu 1804 LTS to Ubuntu 2004 LTS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 7 23:13:16 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-01-25 (1929 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1877456/+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 1877454] Re: openssh-server hangs with AuthorizedKeysCommand
Also see: https://bugzilla.mindrot.org/show_bug.cgi?id=2655 ** Bug watch added: OpenSSH Portable Bugzilla #2655 https://bugzilla.mindrot.org/show_bug.cgi?id=2655 -- 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/1877454 Title: openssh-server hangs with AuthorizedKeysCommand Status in openssh package in Ubuntu: New Bug description: Please consider applying this change to openssh-server distributed in Xenial (16.04). Without it, sshd can sporadically hang when making use of the `AuthorizedKeysCommand` option. https://github.com/openssh/openssh- portable/commit/ddd3d34e5c7979ca6f4a3a98a7d219a4ed3d98c2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1877454/+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 1877456] [NEW] package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: Error occured during update from Ubuntu 1804 LTS to Ubuntu 2004 LTS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 7 23:13:16 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-01-25 (1929 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-07 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal 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/1877456 Title: package initramfs-tools 0.136ubuntu6 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: Error occured during update from Ubuntu 1804 LTS to Ubuntu 2004 LTS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 7 23:13:16 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-01-25 (1929 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1877456/+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 1877454] Re: openssh-server hangs with AuthorizedKeysCommand
Additional discussion of this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1496467 https://bugzilla.mindrot.org/show_bug.cgi?id=2496 https://discourse.phabricator-community.org/t/newly-added-ssh-keys-not- working/992 ** Bug watch added: Red Hat Bugzilla #1496467 https://bugzilla.redhat.com/show_bug.cgi?id=1496467 ** Bug watch added: OpenSSH Portable Bugzilla #2496 https://bugzilla.mindrot.org/show_bug.cgi?id=2496 -- 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/1877454 Title: openssh-server hangs with AuthorizedKeysCommand Status in openssh package in Ubuntu: New Bug description: Please consider applying this change to openssh-server distributed in Xenial (16.04). Without it, sshd can sporadically hang when making use of the `AuthorizedKeysCommand` option. https://github.com/openssh/openssh- portable/commit/ddd3d34e5c7979ca6f4a3a98a7d219a4ed3d98c2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1877454/+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 1877454] [NEW] openssh-server hangs with AuthorizedKeysCommand
Public bug reported: Please consider applying this change to openssh-server distributed in Xenial (16.04). Without it, sshd can sporadically hang when making use of the `AuthorizedKeysCommand` option. https://github.com/openssh/openssh- portable/commit/ddd3d34e5c7979ca6f4a3a98a7d219a4ed3d98c2 ** 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/1877454 Title: openssh-server hangs with AuthorizedKeysCommand Status in openssh package in Ubuntu: New Bug description: Please consider applying this change to openssh-server distributed in Xenial (16.04). Without it, sshd can sporadically hang when making use of the `AuthorizedKeysCommand` option. https://github.com/openssh/openssh- portable/commit/ddd3d34e5c7979ca6f4a3a98a7d219a4ed3d98c2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1877454/+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 1877450] [NEW] Executing "sudo apport-bug /var/crash/some-path.crash" leads to "ERROR: Cannot update /var/crash/some-path.crash: [Errno 13] Permission denied" very often
Public bug reported: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Get some crash file of crashed application (in my example it was /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash ) 3. Try to send this crash file to launchpad using `sudo apport-bug /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash` Expected results: * apport opened window about sending the crash report and then opened Firefox allowing user to login to Launchoad and then to fill some details about the bug-report Actual results: * apport opened window about sending the crash, but Firefox is not opened; instead shows the error in the terminal ``` $ sudo apport-bug /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash [sudo] password for mate: ERROR: Cannot update /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash: [Errno 13] Permission denied: '/var/crash/_usr_lib_mate-panel_clock-applet.1000.crash' ``` Note: what is interesting in this case the upload was successful: ``` $ ls -alt /var/crash/ total 5252 -rw--- 1 whoopsie whoopsie 37 May 7 23:19 _usr_lib_mate-panel_clock-applet.1000.uploaded drwxrwsrwt 2 root whoopsie4096 May 7 23:19 . -rw-r--r-- 1 root whoopsie 0 May 7 23:19 _usr_lib_mate-panel_clock-applet.1000.upload -rw-r- 1 mate whoopsie 5364223 May 7 23:12 _usr_lib_mate-panel_clock-applet.1000.crash drwxr-xr-x 14 root root4096 Apr 23 10:48 .. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportLog: ERROR: apport (pid 2675) Thu May 7 23:10:51 2020: called for pid 2659, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2675) Thu May 7 23:10:51 2020: executable: /usr/lib/mate-panel/clock-applet (command line "/usr/lib/mate-panel/clock-applet") ERROR: apport (pid 2675) Thu May 7 23:10:51 2020: debug: session gdbus call: (true,) ERROR: apport (pid 2675) Thu May 7 23:10:54 2020: wrote report /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 600:121:127:37:2020-05-07 23:19:38.692947366 +0300:2020-05-07 23:11:44.888143341 +0300:/var/crash/_usr_lib_mate-panel_clock-applet.1000.uploaded 644:0:127:0:2020-05-07 23:19:37.976589335 +0300:2020-05-07 23:19:37.976589335 +0300:/var/crash/_usr_lib_mate-panel_clock-applet.1000.upload 640:1000:127:5364223:2020-05-07 23:12:22.348865032 +0300:2020-05-07 23:19:44.571885615 +0300:/var/crash/_usr_lib_mate-panel_clock-applet.1000.crash CurrentDesktop: MATE Date: Thu May 7 23:20:20 2020 InstallationDate: Installed on 2020-04-23 (14 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Get some crash file of crashed application (in my example it was /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash ) - 3. Try to report send this crash file to launchpad and then fill some info about the bug in the browser using `sudo apport-bug /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash` + 3. Try to send this crash file to launchpad using `sudo apport-bug /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash` Expected results: * apport opened window about sending the crash report and then opened Firefox allowing user to login to Launchoad and then to fill some details about the bug-report Actual results: * apport opened window about sending the crash, but Firefox is not opened; instead shows the error in the terminal ``` $ sudo apport-bug /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash [sudo] password for mate: ERROR: Cannot update /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash: [Errno 13] Permission denied: '/var/crash/_usr_lib_mate-panel_clock-applet.1000.crash' ``` Note: what is interesting in this case the upload was successful: ``` - $ ls -alt /var/crash/ + $ ls -alt /var/crash/ total 5252 -rw--- 1 whoopsie whoopsie 37 May 7 23:19 _usr_lib_mate-panel_clock-applet.1000.uploaded drwxrwsrwt 2 root whoopsie4096 May 7 23:19 . -rw-r--r-- 1 root whoopsie 0 May 7 23:19 _usr_lib_mate-panel_clock-applet.1000.upload -rw-r- 1 mate whoopsie 5364223 May 7 23:12 _usr_lib_mate-panel_clock-applet.1000.crash drwxr-xr-x 14 root root4096 Apr 23 10:48 .. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportLog: - ERROR: apport (pid 2675) Thu May 7
[Touch-packages] [Bug 1025388] Re: Internal mic stops working when plugging in headphones
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
Sorry. How should I start installing the v4 kernel? I just downloaded and did "sudo dpkg -i *.deb". But I got "errors encountered installing.. (the kernel)". Do I have to do " sudo dpkg -r --force-all (something here)" first? Also what will happen to the original -26 kernel? -- 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/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 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 failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+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 1025388] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1025388/+attachment/5367985/+files/WifiSyslog.txt -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1025388] Re: Internal mic stops working when plugging in headphones
I've run the apport command because the bug seemed abandoned, but I exhibit the exact same symptoms. This is a Lenovo E490, my headphones use a TRS plug, but the system detects it as TRRS (i.e. believes it also has a microphone). To confirm, I've also checked: * Headphones with a TRRS cable behave correctly on this machine (their microphone is used) * My same TRS headphones (no microphone), on a Chromebook, have the plug detected correctly as TRS, and the Chromebook uses its internal microphone while sending audio to the headphones. There does not appear to be a way, in Linux, to configure the system to use the internal microphone while anything is plugged into the headphone jack. -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1025388] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1025388/+attachment/5367975/+files/Dependencies.txt -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1025388] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1025388/+attachment/5367984/+files/UdevDb.txt -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1025388] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1025388/+attachment/5367983/+files/RfKill.txt -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1025388] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1025388/+attachment/5367982/+files/PulseList.txt -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1025388] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1025388/+attachment/5367976/+files/IwConfig.txt -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1025388] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1025388/+attachment/5367980/+files/ProcInterrupts.txt -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1025388] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1025388/+attachment/5367981/+files/ProcModules.txt -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1025388] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1025388/+attachment/5367979/+files/ProcEnviron.txt -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1025388] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1025388/+attachment/5367978/+files/ProcCpuinfoMinimal.txt -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1025388] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1025388/+attachment/5367977/+files/Lspci.txt -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1025388] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1025388/+attachment/5367974/+files/CurrentDmesg.txt -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1025388] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1025388/+attachment/5367972/+files/AlsaInfo.txt -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1025388] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1025388/+attachment/5367973/+files/CRDA.txt -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1025388] Re: Internal mic stops working when plugging in headphones
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ohad 1755 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-25 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 003: ID 5986:2113 Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20N8000RUK Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-52-lowlatency root=UUID=ac66b098-a06a-4d2e-afac-fcc015944c52 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-52.46-lowlatency 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-52-lowlatency N/A linux-backports-modules-5.3.0-52-lowlatency N/A linux-firmware 1.183.5 Tags: wayland-session eoan wayland-session Uname: Linux 5.3.0-52-lowlatency x86_64 UpgradeStatus: Upgraded to eoan on 2020-05-02 (5 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET27W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8000RUK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET27W(1.10):bd01/22/2019:svnLENOVO:pn20N8000RUK:pvrThinkPadE490:rvnLENOVO:rn20N8000RUK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8000RUK dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO ** Tags added: apport-collected eoan wayland-session -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+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 1875944] Re: Lenovo Ideapad 130-15AST 20.04 distorted and unusable
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: libdrm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1875944 Title: Lenovo Ideapad 130-15AST 20.04 distorted and unusable Status in Ubuntu MATE: New Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Output of lshw here: https://pastebin.com/NMBigV4G Screenshot of the desktop here in the community forum: https://ubuntu-mate.community/t/lenovo-ideapad-20-04-upgrade-distorted-and-unusable/21617 I'm not all that experienced at filing bug reports here so I have included the attachment of the photo found at the forum link. The picture in the community forum link is what the MATE 20.04 live USB boots to. I first upgraded from 18.04 using do-release-upgrade. The result looked like the photo as well. Then I reinstalled 18.04, upgraded to 19.10, which looked and performed normally. I then upgraded the 19.10 install to 20.04 with the same result as the photo. I also tried with a different flash drive just to rule that out. Then I made the live USB of the 20.04 image and booted it to what you see in the forum post. I made a live USB of both Stock Ubuntu and Kubuntu 20.04 and both worked just fine. Until I tried the other two flavors I was thinking it was system specific, but after they worked normally it seems to be a MATE specific issue with this system. It appears to be only a display problem. The DE is completely unusable with the mouse, but I can launch a terminal and run commands, although the terminal is just as distorted as the photo above, so you can't see what you are typing or the resulting output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1875944/+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 1875944] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1875944 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1875944 Title: Lenovo Ideapad 130-15AST 20.04 distorted and unusable Status in Ubuntu MATE: New Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Output of lshw here: https://pastebin.com/NMBigV4G Screenshot of the desktop here in the community forum: https://ubuntu-mate.community/t/lenovo-ideapad-20-04-upgrade-distorted-and-unusable/21617 I'm not all that experienced at filing bug reports here so I have included the attachment of the photo found at the forum link. The picture in the community forum link is what the MATE 20.04 live USB boots to. I first upgraded from 18.04 using do-release-upgrade. The result looked like the photo as well. Then I reinstalled 18.04, upgraded to 19.10, which looked and performed normally. I then upgraded the 19.10 install to 20.04 with the same result as the photo. I also tried with a different flash drive just to rule that out. Then I made the live USB of the 20.04 image and booted it to what you see in the forum post. I made a live USB of both Stock Ubuntu and Kubuntu 20.04 and both worked just fine. Until I tried the other two flavors I was thinking it was system specific, but after they worked normally it seems to be a MATE specific issue with this system. It appears to be only a display problem. The DE is completely unusable with the mouse, but I can launch a terminal and run commands, although the terminal is just as distorted as the photo above, so you can't see what you are typing or the resulting output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1875944/+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 1876065] Re: After unplug headphones and plug them again no sound can be heard
Hi, I tested the package contained in the proposed repo (v13.99.1). I plugged and unplugged the jack several times. It worked well. Worked fine also after reboot. I am now again a happy user of my headset :D Thanks, Roman -- 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/1876065 Title: After unplug headphones and plug them again no sound can be heard Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Bug description: * Impact Sound isn't automatically redirected to headphones when those are connected to a jack interface * Test case Disconnect the headsets Start your webbrowser/music player/video player and play some sound Connect the headsets to the jack interface -> the sound should be directly redirected to the plugged headsets * Regression potential Check that audio routing when connecting/disconnecting devices to the hack entry is working correctly After startup with headset plugged in they play sound nicely - no issue. When they are unplugged, the sound is switched to the speaker (laptop) - all good. However, when I plug the headset back there is no sound. I see the app on pavucontrol, the volume is fine - everything looks fine except there is no sound. I dumped output of "pactl list" command on startup (headset plugged), after unplugging the headset, and when it is plugged back. From the comparison of these outputs, it looks like the source has got muted after the headset is plugged. Source #1 State: RUNNING Name: alsa_input.pci-_00_1f.3.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: yes Attached three outputs: headset-in.txt - after startup with headset plugged - all fine. headset-out.txt - after unplugged headset - sound through the speaker - all fine. headset-back.txt - after plugged headset back - no sound. Any help greatly appreciated. Regards, Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1874723] Re: MATE battery icon disappears when deselect "Show Time in Menu Bar"
Can reproduce this on Ubuntu MATE 20.04 LTS with all updates. ** Changed in: ubuntu-mate Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1874723 Title: MATE battery icon disappears when deselect "Show Time in Menu Bar" Status in Ubuntu MATE: Confirmed Status in indicator-power package in Ubuntu: Confirmed Bug description: In the new Ubuntu MATE 20.04, with the default installation, right clicking on the battery icon in the upper right on the panel, and select either (or both) "Show Time in Menu Bar" or "Show Percentage in Menu Bar". Then, deselect the option, and the entire battery icon (not just the time or percentage) disappears from the tray/panel and can not be replaced. Or, I can not figure out how to replace it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1874723/+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 1874723] Re: MATE battery icon disappears when deselect "Show Time in Menu Bar"
** Also affects: indicator-power (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1874723 Title: MATE battery icon disappears when deselect "Show Time in Menu Bar" Status in Ubuntu MATE: Confirmed Status in indicator-power package in Ubuntu: Confirmed Bug description: In the new Ubuntu MATE 20.04, with the default installation, right clicking on the battery icon in the upper right on the panel, and select either (or both) "Show Time in Menu Bar" or "Show Percentage in Menu Bar". Then, deselect the option, and the entire battery icon (not just the time or percentage) disappears from the tray/panel and can not be replaced. Or, I can not figure out how to replace it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1874723/+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 1874723] Re: MATE battery icon disappears when deselect "Show Time in Menu Bar"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-power (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1874723 Title: MATE battery icon disappears when deselect "Show Time in Menu Bar" Status in Ubuntu MATE: Confirmed Status in indicator-power package in Ubuntu: Confirmed Bug description: In the new Ubuntu MATE 20.04, with the default installation, right clicking on the battery icon in the upper right on the panel, and select either (or both) "Show Time in Menu Bar" or "Show Percentage in Menu Bar". Then, deselect the option, and the entire battery icon (not just the time or percentage) disappears from the tray/panel and can not be replaced. Or, I can not figure out how to replace it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1874723/+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 1874689] Re: alsa force-reload needed to fix my sound after upgrade to 20.04
** Also 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/1874689 Title: alsa force-reload needed to fix my sound after upgrade to 20.04 Status in Ubuntu MATE: New Status in alsa-driver package in Ubuntu: New Bug description: After upgrading from Ubuntu Mate 18.04 LTS to Ubuntu Mate 20.04 LTS "sudo alsa force-reload" is needed to fix my sound. I upgraded yesterday (23rd) before the official announcements of 20.04 LTS. Using "do-release-upgrade -d". I'm not sure yet how often I have to run "sudo alsa force-reload". When I have no sound a reboot is not a guranteed fix although it worked once. Booting into a Ubuntu Desktop 20.04 LTS gets working sounds each time I tried. Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-26-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1874689/+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 1877219] Re: dozens of empty grilo-plugin-cache folders polluting /tmp
** Bug watch added: gitlab.gnome.org/GNOME/grilo-plugins/-/issues #70 https://gitlab.gnome.org/GNOME/grilo-plugins/-/issues/70 ** Also affects: grilo-plugins via https://gitlab.gnome.org/GNOME/grilo-plugins/-/issues/70 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1877219 Title: dozens of empty grilo-plugin-cache folders polluting /tmp Status in Grilo Plugins: Unknown Status in grilo-plugins package in Ubuntu: New Bug description: My /tmp folder has dozens of empty folders with names like grilo- plugin-cache-ABCDEF. I don't know anything about grilo-plugins, but surely they can do their job without leaving endless garbage directories behind when they're done? $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan $ dpkg-query --show grilo-plugins-0.3-base grilo-plugins-0.3-base:amd64 0.3.9-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/grilo-plugins/+bug/1877219/+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 1877440] [NEW] /lib/NetworkManager/conf.d values in wrong section
Public bug reported: $ g ^VER /etc/os-release VERSION="20.10 (Groovy Gorilla)" VERSION_ID="20.10" VERSION_CODENAME=groovy $ apt-cache policy network-manager network-manager: Installed: 1.22.10-1ubuntu3 Candidate: 1.22.10-1ubuntu3 Version table: *** 1.22.10-1ubuntu3 500 500 http://ch.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status $ cat /lib/NetworkManager/conf.d/no-mac-addr-change.conf # Certain drivers are known not to support changing the MAC address. # Disable touching the MAC address on such devices. # # See man NetworkManager.conf # # https://bugzilla.gnome.org/show_bug.cgi?id=777523 [device-mac-addr-change-wifi] match-device=driver:rtl8723bs,driver:rtl8189es,driver:r8188eu,driver:8188eu,driver:eagle_sdio,driver:wl wifi.scan-rand-mac-address=no wifi.cloned-mac-address=preserve ethernet.cloned-mac-address=preserve "wifi.cloned-mac-address" and "ethernet.cloned-mac-address=preserve" should be in a "[connection]" section. ** 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/1877440 Title: /lib/NetworkManager/conf.d values in wrong section Status in network-manager package in Ubuntu: New Bug description: $ g ^VER /etc/os-release VERSION="20.10 (Groovy Gorilla)" VERSION_ID="20.10" VERSION_CODENAME=groovy $ apt-cache policy network-manager network-manager: Installed: 1.22.10-1ubuntu3 Candidate: 1.22.10-1ubuntu3 Version table: *** 1.22.10-1ubuntu3 500 500 http://ch.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status $ cat /lib/NetworkManager/conf.d/no-mac-addr-change.conf # Certain drivers are known not to support changing the MAC address. # Disable touching the MAC address on such devices. # # See man NetworkManager.conf # # https://bugzilla.gnome.org/show_bug.cgi?id=777523 [device-mac-addr-change-wifi] match-device=driver:rtl8723bs,driver:rtl8189es,driver:r8188eu,driver:8188eu,driver:eagle_sdio,driver:wl wifi.scan-rand-mac-address=no wifi.cloned-mac-address=preserve ethernet.cloned-mac-address=preserve "wifi.cloned-mac-address" and "ethernet.cloned-mac-address=preserve" should be in a "[connection]" section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1877440/+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 1875091] Re: opencl fails with "pipe_radeonsi.so: undefined symbol: amdgpu_cs_query_reset_state2"
Fresh re-install of amdgpu (and related things) made the problem go away. I suppose it was most likely something I'd done pre-upgrade in the course of getting the old drivers working. ** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1875091 Title: opencl fails with "pipe_radeonsi.so: undefined symbol: amdgpu_cs_query_reset_state2" Status in mesa package in Ubuntu: Invalid Bug description: Both luxmark and leelaz, the two OpenCL applications I have, fail at runtime with the same error, looking for "amdgpu_cs_query_reset_state2" in /usr/lib/x86_64-linux-gnu/gallium- pipe/pipe_radeonsi.so This is on a system with a relatively new AMD GPU, freshly upgraded from 18.04. Leela zero worked correctly in 18.04, and I've tried various compiler options, openCL config and such with no success. I don't know about luxmark but installed it to test. Since it reports the same error, I think it's a bug to report here. Platform Name Clover Device Name AMD Radeon (TM) RX Graphics (POLARIS11, DRM 3.36.0, 5.6.7-050607-generic, LLVM 9.0.1) Device Name AMD RAVEN (DRM 3.36.0, 5.6.7-050607-generic, LLVM 9.0.1) 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] (rev c0) 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1875091/+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 1871176] Re: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lvm2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1871176 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: Confirmed Bug description: hayden@t470s:~$ sudo apt-get install gnome-boxes [sudo] password for hayden: Reading package lists... Done Building dependency tree Reading state information... Done gnome-boxes is already the newest version (3.36.2-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up lvm2 (2.03.07-1ubuntu1) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked. invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed. ● lvm2-lvmpolld.service - LVM2 poll daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; vendor preset: enabled) Active: active (exited) since Mon 2020-04-06 09:33:50 EDT; 4h 10min ago Docs: man:lvmpolld(8) Tasks: 0 (limit: 23811) Memory: 0B CGroup: /system.slice/lvm2-lvmpolld.service Apr 06 09:33:50 t470s systemd[1]: Starting LSB: LVM2 poll daemon... Apr 06 09:33:50 t470s systemd[1]: Started LSB: LVM2 poll daemon. dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.136ubuntu2) ... update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 Date: Mon Apr 6 13:38:10 2020 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1 SourcePackage: lvm2 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871176/+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 1866681] Re: [HP Pavilion dv9000] Mute toggles on/off while plugged into the headphone/speaker jack (19.04+)
So, after some rather tedious testing (across Ubuntu, Xubuntu, Kubuntu, and Lubuntu), I found the exact iteration where the audio went wrong. Everything works perfectly fine up until and including 18.04.2, and then beginning as of 18.04.3 (of course, including 18.04.4), the audio does the auto-mute thing.I don't know enough about programming to read through the Pulseaudio and/or ALSA source code, and I know it's Debian-based, because again, Kali does it, too, yet Manjaro, CentOS, Fedora, etc. don't. On Thu, Apr 23, 2020 at 11:25 PM Kuroš Taheri-Golværzi wrote: > > I've just tried installing 20.04 LTS, and the audio issue still > persists. I've tried reinstalling both pulseaudio and ALSA, and > nothing works. I'm out of ideas. What do I do? How should I go about > fixing the problem? > > On Tue, Mar 17, 2020 at 11:04 AM Kuroš Taheri-Golværzi > wrote: > > > > Alrighty, so, I installed Xubuntu 16.04. `uname -or` outputs: > > 4.4.0-21-generic GNU/Linux > > and `pulseaudio --version` outputs: > > pulseaudio 8.0 > > In AlsaMixer, "Auto-Mute Mode" is set to "Enabled", and the audio > > works perfectly exactly as expected. > > > > This is definitely something that started happening in the 19.04 versions. > > > > On 3/12/20, Kai-Heng Feng wrote: > > > Can you please test older kernels like 4.15? > > > > > > -- > > > You received this bug notification because you are subscribed to the bug > > > report. > > > https://bugs.launchpad.net/bugs/1866681 > > > > > > Title: > > > [HP Pavilion dv9000] Mute toggles on/off while plugged into the > > > headphone/speaker jack (19.04+) > > > > > > Status in alsa-driver package in Ubuntu: > > > New > > > Status in linux package in Ubuntu: > > > Confirmed > > > Status in pulseaudio package in Ubuntu: > > > New > > > > > > Bug description: > > > I'm on an HP Pavilion dv9000 (https://www.cnet.com/products/hp- > > > pavilion-dv9000/specs/) built many years ago. > > > > > > > > > Whenever I'm using any distro that's based on Ubuntu which was published > > > from Version 19.04 onwards, I've been having a major issue with the mute > > > button toggling on and off whenever I have something plugged into the > > > audio > > > out jack. I know that it's not the fault of XFCE, because I also use the > > > latest version of Manjaro with XFCE on this same computer, and it works > > > fine. I also know it's not any Red Hat-based distro, because I use Stella > > > (which is a remix of CentOS 6) also on this exact same computer, and it > > > also > > > works fine. Qubes, Mageia, and Fedora 31 also work perfectly fine and > > > don't > > > have this issue. > > > > > > My "lsb-release" is: > > > DISTRIB_ID=Ubuntu > > > DISTRIB_RELEASE=19.10 > > > DISTRIB_CODENAME=eoan > > > DISTRIB_DESCRIPTION="Ubuntu 19.10" > > > > > > and "apt-cache policy pulseaudio" outputs: > > > pulseaudio: > > > Installed: 1:13.0-1ubuntu1.1 > > > Candidate: 1:13.0-1ubuntu1.1 > > > Version table: > > >*** 1:13.0-1ubuntu1.1 500 > > > 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 > > > Packages > > > 100 /var/lib/dpkg/status > > >1:13.0-1ubuntu1 500 > > > 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages > > > > > > I've uploaded a short video of the problem that I recorded with my phone > > > here: > > > https://www.youtube.com/watch?v=GXaHXQA-5uQ > > > > > > > > > The problem appears with Kali 2019 and 2020, Peppermint 19.04, Lubuntu > > > 19.04, Xubuntu 19.04, and Sparky 5.10 and 2020.02. > > > > > > > > > I've checked pretty much everything I can think of. There's a log for my > > > ALSA help diagnostics results on my current computer (which works properly > > > with 18.04) at: > > > http://alsa-project.org/db/?f=4859b85cd7fc32e7f01f8df63591b5a43dbf6829 > > > > > > > > > the result output of lspci is: > > > [code]00:00.0 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2) > > > 00:00.1 RAM memory: NVIDIA Corporation C51 Memory Controller 0 (rev a2) > > > 00:00.2 RAM memory: NVIDIA Corporation C51 Memory Controller 1 (rev a2) > > > 00:00.3 RAM memory: NVIDIA Corporation C51 Memory Controller 5 (rev a2) > > > 00:00.4 RAM memory: NVIDIA Corporation C51 Memory Controller 4 (rev a2) > > > 00:00.5 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2) > > > 00:00.6 RAM memory: NVIDIA Corporation C51 Memory Controller 3 (rev a2) > > > 00:00.7 RAM memory: NVIDIA Corporation C51 Memory Controller 2 (rev a2) > > > 00:02.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) > > > 00:03.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) > > > 00:04.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) > > > 00:09.0 RAM memory: NVIDIA Corporation MCP51 Host Bridge (rev a2) > > > 00:0a.0 ISA bridge: NVIDIA Corporation MCP51 LPC Bridge (rev a3) > > > 00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3) > > > 00:0a.3 Co-processor:
[Touch-packages] [Bug 1838329] Re: Cryptswap periodically fails to mount at boot due to missing a udev notification
** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Status: New => Triaged ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => High ** Changed in: systemd (Ubuntu Focal) Milestone: None => ubuntu-20.04.1 ** Tags removed: rls-ff-incoming -- 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/1838329 Title: Cryptswap periodically fails to mount at boot due to missing a udev notification Status in systemd: New Status in systemd package in Ubuntu: Triaged Status in systemd source package in Focal: Triaged Bug description: On some systems, cryptsetup-based encrypted swap partitions cause systemd to get stuck at boot. This is a timing-sensitive Heisenbug, so the rate of occurrence varies from one system to another. Some hardware will not experience the issue at all, others will only occasionally experience the issue, and then there are the unlucky who are unable to boot at all, no matter how many times they restart. The workaround is for the cryptsetup-generator to generate cryptswap service entries that call `udevadm trigger` after `mkswap`. This will ensure that the udev event is triggered, so that systemd is notified that the encrypt swap partition is ready to activate. This patch has already been submitted upstream to systemd, but it was not accepted because it is a workaround for the side effect of systemd not seeing the udev event upon creating the swap partition. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1838329/+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 1813339] Re: Apparmor is denying evince from running vivaldi
That is a very suboptimal solution. for the average user, it just does not work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1813339 Title: Apparmor is denying evince from running vivaldi Status in apparmor package in Ubuntu: Won't Fix Bug description: It's similar to this bug https://bugs.launchpad.net/bugs/1432126 or discussed here; https://forum.vivaldi.net/topic/33591/vivaldi-opening- from-a-link-in-a-pdf-file/7 Apparmor is denying evince from running vivaldi by clicking on a http link kernel: [ 3271.799807] audit: type=1400 audit(1548434352.941:114): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/opt/vivaldi/vivaldi" pid=6795 comm="exo-helper-1" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 Description: Ubuntu 18.04.1 LTS Release: 18.04 vivaldi-stable: 2.2.1388.37-1 apparmor: 2.12-4ubuntu5.1 evince: 3.28.4-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1813339/+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 1876957] Re: Symbolic link 'pyvenv' is bloken
I have the same problem on aarch64 20.04. # dpkg --list | grep venv ii python3-venv 3.8.2-0ubuntu2 arm64pyvenv-3 binary for python3 (default python3 version) ii python3.8-venv 3.8.2-1ubuntu1.1 arm64Interactive high-level object-oriented language (pyvenv binary, version 3.8) # file /usr/bin/pyvenv /usr/bin/pyvenv: broken symbolic link to pyvenv-3.8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1876957 Title: Symbolic link 'pyvenv' is bloken Status in python3-defaults package in Ubuntu: Confirmed Bug description: I installed package 'python3-venv', however, I cannot use command 'pyvenv' because it is a bloken symbolic link. ## OS Version $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" ## Package information $ dpkg -l python3-venv 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 VersionArchitecture Description +++-==-==--> ii python3-venv 3.8.2-0ubuntu2 amd64pyvenv-3 binary for python3 (default python3 ver> lines 1-6/6 (END) ## The symbolic link is bloken $ ls -l /usr/bin/pyvenv lrwxrwxrwx 1 root root 10 3月 13 21:20 /usr/bin/pyvenv -> pyvenv-3.8 $ file /usr/bin/pyvenv /usr/bin/pyvenv: broken symbolic link to pyvenv-3.8 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3-venv 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 01:33:25 2020 InstallationDate: Installed on 2020-05-05 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1876957/+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 1876957] Re: Symbolic link 'pyvenv' is bloken
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python3-defaults (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1876957 Title: Symbolic link 'pyvenv' is bloken Status in python3-defaults package in Ubuntu: Confirmed Bug description: I installed package 'python3-venv', however, I cannot use command 'pyvenv' because it is a bloken symbolic link. ## OS Version $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" ## Package information $ dpkg -l python3-venv 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 VersionArchitecture Description +++-==-==--> ii python3-venv 3.8.2-0ubuntu2 amd64pyvenv-3 binary for python3 (default python3 ver> lines 1-6/6 (END) ## The symbolic link is bloken $ ls -l /usr/bin/pyvenv lrwxrwxrwx 1 root root 10 3月 13 21:20 /usr/bin/pyvenv -> pyvenv-3.8 $ file /usr/bin/pyvenv /usr/bin/pyvenv: broken symbolic link to pyvenv-3.8 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3-venv 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 01:33:25 2020 InstallationDate: Installed on 2020-05-05 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1876957/+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 1877194] Re: switch-on-connect mistakes startup for USB hotplug
Seems reasonable. Created an issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/886 Thank you for the help. ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #886 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/886 -- 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/1877194 Title: switch-on-connect mistakes startup for USB hotplug Status in pulseaudio package in Ubuntu: Triaged Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877194/+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 1867799] Re: Focal: sudo: setrlimit(RLIMIT_CORE): Operation not permitted
Just spun up a Focal LXD container and this is still an issue in containers: bladernr@focal-builder:~/development/kernels-ubuntu/focal$ sudo vim /etc/apt/sources.list sudo: setrlimit(RLIMIT_CORE): Operation not permitted ** Also affects: sudo (Ubuntu) Importance: Undecided Status: New ** Changed in: sudo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1867799 Title: Focal: sudo: setrlimit(RLIMIT_CORE): Operation not permitted Status in juju: Invalid Status in sudo package in Ubuntu: Confirmed Bug description: When bootstrapping to focal and using debug output, we get the following outputted to the stderr. sudo: setrlimit(RLIMIT_CORE): Operation not permitted I'm unsure what it's attempting to do at that point, but others have also run into this with a suggested workaround. https://gitlab.alpinelinux.org/alpine/aports/issues/11122 https://bugzilla.redhat.com/show_bug.cgi?id=1773148 To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1867799/+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 1838577] Re: Default audio device changes on reboot; audio still outputs using my previously-selected device
*** This bug is a duplicate of bug 1866194 *** https://bugs.launchpad.net/bugs/1866194 After looking through the posted bug and comments I'm not sure that the issues are related. It seems more like, in this case, GNOME is just out of sync with pulse about what the default device is thanks to pulse changing it out during login. Changing the selected device fixes the issue (until the next login). -- 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/1838577 Title: Default audio device changes on reboot; audio still outputs using my previously-selected device Status in pulseaudio package in Ubuntu: New Bug description: This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It was not present in Ubuntu 16.04. I have a USB microphone which also appears to pulse as a speaker. Pulse keeps picking it as the default audio device. I can switch audio devices to my analog line out, which works as expected until I reboot. After reboot, my audio device switches back to the USB "speaker", and Gnome shell / Gnome settings volume control adjusts the USB speaker volume. Despite seeing the USB device as the current output device, I still hear sound from my line-out. In the interest of narrowing down this bug, I have found that disabling "module-switch-on-connect" fixes the problem (my line-out stays as the default audio device and I hear sound). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 31 17:39:38 2019 InstallationDate: Installed on 2019-07-31 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4207 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838577/+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 1873785] Re: Root can't modify files of other users in directories with sticky bit anymore
Since you've identified a fix for your use case that doesn't require changing the sysctl setting, I am marking this 'wontfix'. It can be reopened if someone identifies other cases that warrant revisiting the question of reverting this setting. ** Changed in: procps (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1873785 Title: Root can't modify files of other users in directories with sticky bit anymore Status in procps package in Ubuntu: Won't Fix Bug description: Hello, in Focal the behaviour has changed when a program running as root tries to modify a file which belongs to a user/group other than root in a directory with sticky bit set. I'm not sure if this is a bug or the behaviour is intentional (for certain security reasons). Steps to reproduce: - Boot current Focal daily iso - Open terminal - Create a directory with sticky bit set (chmod o+t; or use an existing directory with sticky bit, e.g. /var/crash ) - Create an empty file with user:group set to anything different than root (e.g. ubuntu:ubuntu, ubuntu:whoopsie, ...) - Open the file with nano running as root (sudo nano testfile.txt), write something in it, and try to save it. This won't work and gives a "permission denied" error message. This behaviour is different than in previous Ubuntu versions. In Eoan it is possible to modify the file as root in the scenario described above. I discovered this because after changing my main installation to Eoan I noticed that I got weird error messages from rsync when backing up my root subvolume. In my backup script rsync runs as root, and can't update backed up contents of /var/crash or /var/spool/cups/tmp anymore because it isn't allowed to modify the respective files anymore. For me personally this is a regression compared to previous Ubuntu versions where I never saw such errors during backup. Whether PAM is the appropriate package to report this bug against I'm not sure, so please feel free to assign it to the correct package. If this is intentional, does anybody have a clue how to work around this for use cases like backup with rsync? Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-runtime 1.3.1-5ubuntu4 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 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 20 12:11:32 2020 InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) PackageArchitecture: all SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1873785/+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 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
it looks like your dhcp lease is expiring, which causes networkd to drop your dhcp configuration, including resetting your mtu back to its original value. That's done asynchronously by netlink, and networkd sets a flag "setting_mtu" while the netlink request to change the mtu is pending. However, immediately after your lease is lost, you regain it, and networkd begins setting up the interface with the dhcp info, including the mtu. Unfortunately, since the mtu reset hasn't completed yet, "setting_mtu" flag is still set, and the call to link_set_mtu() returns silently without actually changing the mtu. At least that's what seems like is happening in your case. It's unusual to lose your dhcp lease before renewing it, so you may be able to look at why that's happening to avoid this (hopefully that's not a separate bug in systemd...), but re: the failure to set mtu, I believe that's going to be a problem that still exists upstream, so resolving this bug will need fixing upstream first. If you (or anyone else) has time to open a bug upstream for this (preferably, after testing with upstream systemd to verify it's still a bug upstream), please add a note to this bug. -- 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/1874661 Title: networkd sometimes doesn't set mtu received by dhcp Status in systemd package in Ubuntu: Confirmed Bug description: I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 242-7ubuntu3.7. GCE has mtu 1460, set by dhcp. After having networking issues, I figured out that the mtu on the interface was sometimes incorrectly set to 1500. I manually changed it to 1420 to have a working system again and enabled debugging for systemd-networkd. Log (filtered for ens4, some columns removed for better readability): 09:51:00 ens4: New device has no master, continuing without 09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST 09:51:00 ens4: Link 2 added 09:51:00 ens4: udev initialized link 09:51:00 ens4: Saved original MTU: 1420 09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) 09:51:00 ens4: Gained IPv6LL 09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Link state is up-to-date 09:51:00 ens4: found matching network '/run/systemd/network/10-netplan-ens4.network' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0' 09:51:00 ens4: Started LLDP. 09:51:00 ens4: Setting address genmode for link 09:51:00 ens4: Setting address genmode done. 09:51:00 ens4: Removing address 10.164.0.2 09:51:00 ens4: Acquiring DHCPv4 lease 09:51:00 ens4: Discovering IPv6 routers 09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 09:51:00 ens4: Setting MTU: 1460 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 09:51:00 ens4: IPv6 successfully enabled 09:51:00 ens4: Setting MTU done. 09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d) 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Configured 21:50:59 ens4: DHCP lease lost 21:50:59 ens4: Removing address 10.164.0.2 21:50:59 ens4: Setting MTU: 1420 21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 21:50:59 ens4: IPv6 successfully enabled 21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s) 21:50:59 ens4: Removing route: dst:
[Touch-packages] [Bug 1861082] Re: ubuntu-bug doesn't know how to file bugs against snaps
** Tags removed: champagne -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1861082 Title: ubuntu-bug doesn't know how to file bugs against snaps Status in Snapcraft: New Status in snapd: Triaged Status in Snap Store: New Status in apport package in Ubuntu: Triaged Status in apport source package in Focal: Triaged Bug description: Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1861082/+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 1874353] Re: there is no linux-raspi apport package hook
*** This bug is a duplicate of bug 1876952 *** https://bugs.launchpad.net/bugs/1876952 ** Tags removed: rls-ff-incoming ** This bug has been marked a duplicate of bug 1876952 missing a package hook for linux-raspi and linux-raspi2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1874353 Title: there is no linux-raspi apport package hook Status in apport package in Ubuntu: New Bug description: ubuntu@ubuntu:~$ ls /usr/share/apport/package-hooks/ | grep linux source_linux-5.4.py source_linux-meta-oem-osp1.py source_linux-meta-oem.py source_linux-meta.py source_linux-oem-5.4.py source_linux-oem-osp1.py source_linux-oem.py source_linux-signed-5.4.py source_linux-signed-oem-5.4.py source_linux-signed-oem-osp1.py source_linux-signed-oem.py source_linux-signed.py source_linux.py On a Raspberry Pi this is my kernel image. ii linux-raspi5.4.0.1008.8 arm64 Complete Raspberry Pi Linux kernel and headers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1874353/+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 1872902] Re: Upgrade to Focal now removes chrony
This bug was fixed in the package ubuntu-release-upgrader - 1:20.04.19 --- ubuntu-release-upgrader (1:20.04.19) focal; urgency=medium [ Dimitri John Ledkov ] * DistUpgradeCache: Ignore BaseMetaPkgs' & obsolete tasks during server upgrade (LP: #1872902) [ Brian Murray ] * data/mirrors.cfg: update as some mirrors have been removed as they do not mirror Ubuntu 20.04 LTS. * data/demoted.bionic.cfg: updated for packages that were removed nearer the release date. -- Brian Murray Tue, 05 May 2020 15:26:02 -0700 ** Changed in: ubuntu-release-upgrader (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1872902 Title: Upgrade to Focal now removes chrony Status in Release Notes for Ubuntu: New Status in apt package in Ubuntu: Invalid Status in chrony package in Ubuntu: Invalid Status in germinate package in Ubuntu: New Status in ntp package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Focal: Invalid Status in chrony source package in Focal: Invalid Status in germinate source package in Focal: New Status in ntp source package in Focal: Invalid Status in systemd source package in Focal: Invalid Status in ubuntu-release-upgrader source package in Focal: Fix Released Bug description: Due to changes in systemd for bug 1849156 this issue now happens. On an upgrade for people that had chrony installed on a do-release upgrade it now will: Calculating the changes MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > FU=1 Removing: chrony MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0 That isn't what users want, those who had chrony installed would want to get chrony upgraded and systemd-timesyncd (which now is a separate pacakge) not installed. Test Case - 1) On a system running Ubuntu 19.10 or Ubuntu 18.04 LTS install the package chrony 2) Run do-release-upgrade with the appropriate switches 3) Observe that chrony is marked for deletion With the version of dist-upgrader from -proposed (accessed with the -p switch) chrony is no longer marked for deletion. Regression Potential Given that Dimitri's change is now ignoring the tasks minimal and standard (which are handled by _keepBaseMetaPkgsInstalled) we should still be cautious and test desktop upgrades and ensure that packages in those tasks are not marked for removal. Regression Test --- 1) Run do-release-upgrade on an Ubuntu 19.10 or Ubuntu 18.04 LTS system 2) Record the list of packages marked for removal Compare the list of packages marked for removal with the release- upgrader from -proposed from Focal. Original Description I'd ask you to revise the dependencies that got changes in systemd 245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays installed as that was an opt-in chances are quite high people would want to keep it that way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1872902] Update Released
The verification of the Stable Release Update for ubuntu-release- upgrader has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1872902 Title: Upgrade to Focal now removes chrony Status in Release Notes for Ubuntu: New Status in apt package in Ubuntu: Invalid Status in chrony package in Ubuntu: Invalid Status in germinate package in Ubuntu: New Status in ntp package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Focal: Invalid Status in chrony source package in Focal: Invalid Status in germinate source package in Focal: New Status in ntp source package in Focal: Invalid Status in systemd source package in Focal: Invalid Status in ubuntu-release-upgrader source package in Focal: Fix Released Bug description: Due to changes in systemd for bug 1849156 this issue now happens. On an upgrade for people that had chrony installed on a do-release upgrade it now will: Calculating the changes MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > FU=1 Removing: chrony MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0 That isn't what users want, those who had chrony installed would want to get chrony upgraded and systemd-timesyncd (which now is a separate pacakge) not installed. Test Case - 1) On a system running Ubuntu 19.10 or Ubuntu 18.04 LTS install the package chrony 2) Run do-release-upgrade with the appropriate switches 3) Observe that chrony is marked for deletion With the version of dist-upgrader from -proposed (accessed with the -p switch) chrony is no longer marked for deletion. Regression Potential Given that Dimitri's change is now ignoring the tasks minimal and standard (which are handled by _keepBaseMetaPkgsInstalled) we should still be cautious and test desktop upgrades and ensure that packages in those tasks are not marked for removal. Regression Test --- 1) Run do-release-upgrade on an Ubuntu 19.10 or Ubuntu 18.04 LTS system 2) Record the list of packages marked for removal Compare the list of packages marked for removal with the release- upgrader from -proposed from Focal. Original Description I'd ask you to revise the dependencies that got changes in systemd 245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays installed as that was an opt-in chances are quite high people would want to keep it that way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
** Description changed: + SRU Justification + + Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the + lowlatency kernel since we expected most RT users to use that kernel. + However we are getting RT regressions with the generic kernel. Digging + deeper into this option, it seems to be pretty specialized and to + require quite a bit of workload-specific configuration/tuning to be + useful, so it doesn't really seem to make sense for a general-purpose + kernel. + + Fix: Turn this option back off. + + Test Case: See comment #4. + + Regression Potential: This was turned on to support some docker + functionality, so this functionality will no longer be available. We've + had this option off for all releases prior to focal, so this seems + acceptable. + + --- + These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: - TERM=tmux-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=tmux-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in linux package in Ubuntu: Confirmed Status in rtkit package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in rtkit source package in Focal: New Bug description: SRU Justification Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the lowlatency kernel since we expected most RT users to use that kernel. However we are getting RT regressions with the generic kernel. Digging deeper into this option, it seems to be pretty specialized and to require quite a bit of workload-specific configuration/tuning to be useful, so it doesn't really seem to make sense for a general-purpose kernel. Fix: Turn this option back off. Test Case: See comment #4. Regression Potential: This was turned on to support some docker functionality, so this functionality will no longer be available. We've had this option off for all releases prior to focal, so this seems acceptable. --- These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665/+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 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Using Ubuntu 18.04 LTS on my desktop. From my journalctl -b: wpa_supplicant[6756]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property= wpa_supplicant[6756]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none wpa_supplicant[6756]: dbus: Failed to construct signal wpa_supplicant[6756]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property= -- 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/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' Status in network-manager package in Ubuntu: Confirmed Bug description: The Wifi network can't connect after the wake up from suspend. Xubuntu 15.04 I'll post more useful details (journalctl log) as a comment to this bug report. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu5 Uname: Linux 4.0.0-04rc5-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 2 18:18:56 2015 InstallationDate: Installed on 2015-03-27 (5 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+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 1872902] Re: Upgrade to Focal now removes chrony
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1872902 Title: Upgrade to Focal now removes chrony Status in Release Notes for Ubuntu: New Status in apt package in Ubuntu: Invalid Status in chrony package in Ubuntu: Invalid Status in germinate package in Ubuntu: New Status in ntp package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Focal: Invalid Status in chrony source package in Focal: Invalid Status in germinate source package in Focal: New Status in ntp source package in Focal: Invalid Status in systemd source package in Focal: Invalid Status in ubuntu-release-upgrader source package in Focal: Fix Committed Bug description: Due to changes in systemd for bug 1849156 this issue now happens. On an upgrade for people that had chrony installed on a do-release upgrade it now will: Calculating the changes MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > FU=1 Removing: chrony MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0 That isn't what users want, those who had chrony installed would want to get chrony upgraded and systemd-timesyncd (which now is a separate pacakge) not installed. Test Case - 1) On a system running Ubuntu 19.10 or Ubuntu 18.04 LTS install the package chrony 2) Run do-release-upgrade with the appropriate switches 3) Observe that chrony is marked for deletion With the version of dist-upgrader from -proposed (accessed with the -p switch) chrony is no longer marked for deletion. Regression Potential Given that Dimitri's change is now ignoring the tasks minimal and standard (which are handled by _keepBaseMetaPkgsInstalled) we should still be cautious and test desktop upgrades and ensure that packages in those tasks are not marked for removal. Regression Test --- 1) Run do-release-upgrade on an Ubuntu 19.10 or Ubuntu 18.04 LTS system 2) Record the list of packages marked for removal Compare the list of packages marked for removal with the release- upgrader from -proposed from Focal. Original Description I'd ask you to revise the dependencies that got changes in systemd 245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays installed as that was an opt-in chances are quite high people would want to keep it that way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1876886] Re: chrony autopkgtest fails on armhf (groovy)
Of course now it had to work :-/ I'm suggesting enhanced debug to Debian in https://salsa.debian.org/debian/chrony/-/merge_requests/4 And consider this done for now. ** Changed in: libcap2 (Ubuntu) Status: Confirmed => Invalid ** Changed in: chrony (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1876886 Title: chrony autopkgtest fails on armhf (groovy) Status in chrony package in Ubuntu: Invalid Status in libcap2 package in Ubuntu: Invalid Bug description: Test fails on armhf only: running chronyc makestepERROR checking chronyc output OK running chronyc trimrtc ERROR checking chronyc output OK running chronyc writertcERROR This might be a new twist on https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1863590 as it is libcap2 again. This reproduces through a bunch of retries http://autopkgtest.ubuntu.com/packages/c/chrony/groovy/armhf But as I said is armfh only: http://autopkgtest.ubuntu.com/packages/chrony Flagging update-excuse, but I won't be able to get to it immediately ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1876886/+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 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
Fixed in ubuntu/245.5-2ubuntu1 in Groovy. ** Changed in: systemd (Ubuntu Groovy) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: Fix Released Bug description: [impact] during systemctl daemon-reload, systemd sometimes segfaults while serializing a service. [test case] problem is intermittent, but the upstream bug suggests a reproducer. Also see original description. [regression potential] this adjusts serialization, so any regression would likely occur during serialization/deserialization, e.g. at daemon-reload. [scope] This is needed for Bionic and later. this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41 which is included starting in v234. The commit to fix it is e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in any release. The PR to fix this is https://github.com/systemd/systemd/pull/15546 [other info] there is an additional PR that further avoids the error, but has not yet been accepted, and may not be accepted as it may not be necessary. https://github.com/systemd/systemd/pull/15370 [original description] Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output lines suppressed due to ratelimiting Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.7 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 18:09:06 2020 InstallationDate: Installed on 2019-11-01 (169 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date:
[Touch-packages] [Bug 1806458] Re: Intel I219-V ethernet connection lost
*** This bug is a duplicate of bug 1785171 *** https://bugs.launchpad.net/bugs/1785171 ** This bug has been marked a duplicate of bug 1785171 Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: Confirmed Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 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:
[Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
** Description changed: + [impact] + + during systemctl daemon-reload, systemd sometimes segfaults while + serializing a service. + + [test case] + + problem is intermittent, but the upstream bug suggests a reproducer. + Also see original description. + + [regression potential] + + this adjusts serialization, so any regression would likely occur during + serialization/deserialization, e.g. at daemon-reload. + + [scope] + + This is needed for Bionic and later. + + this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41 + which is included starting in v234. The commit to fix it is + e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in + any release. + + The PR to fix this is https://github.com/systemd/systemd/pull/15546 + + [other info] + + there is an additional PR that further avoids the error, but has not yet been accepted, and may not be accepted as it may not be necessary. + https://github.com/systemd/systemd/pull/15370 + + [original description] + Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output lines suppressed due to ratelimiting Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.7 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 18:09:06 2020 InstallationDate: Installed on 2019-11-01 (169 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub - Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub - Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: - SHELL=/bin/bash - LANG=en_US.UTF-8 - TERM=xterm-256color - XDG_RUNTIME_DIR= - PATH=(custom, no user) + SHELL=/bin/bash + LANG=en_US.UTF-8 + TERM=xterm-256color + XDG_RUNTIME_DIR= + PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-cosmic dmi.modalias:
[Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: Fix Released ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Groovy) Status: Fix Released => New -- 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/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd: Fix Released Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: New Bug description: [impact] during systemctl daemon-reload, systemd sometimes segfaults while serializing a service. [test case] problem is intermittent, but the upstream bug suggests a reproducer. Also see original description. [regression potential] this adjusts serialization, so any regression would likely occur during serialization/deserialization, e.g. at daemon-reload. [scope] This is needed for Bionic and later. this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41 which is included starting in v234. The commit to fix it is e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in any release. The PR to fix this is https://github.com/systemd/systemd/pull/15546 [other info] there is an additional PR that further avoids the error, but has not yet been accepted, and may not be accepted as it may not be necessary. https://github.com/systemd/systemd/pull/15370 [original description] Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output lines suppressed due to ratelimiting Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.7 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 18:09:06 2020 InstallationDate: Installed on 2019-11-01 (169 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 001:
[Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd: Fix Released Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: New Bug description: [impact] during systemctl daemon-reload, systemd sometimes segfaults while serializing a service. [test case] problem is intermittent, but the upstream bug suggests a reproducer. Also see original description. [regression potential] this adjusts serialization, so any regression would likely occur during serialization/deserialization, e.g. at daemon-reload. [scope] This is needed for Bionic and later. this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41 which is included starting in v234. The commit to fix it is e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in any release. The PR to fix this is https://github.com/systemd/systemd/pull/15546 [other info] there is an additional PR that further avoids the error, but has not yet been accepted, and may not be accepted as it may not be necessary. https://github.com/systemd/systemd/pull/15370 [original description] Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output lines suppressed due to ratelimiting Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.7 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 18:09:06 2020 InstallationDate: Installed on 2019-11-01 (169 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1
[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
Oh wow, there are multiple bugs, and I thought this bug was about the actual crash: pk-client-error-quark: could not do untrusted question as no klass support (8) but it is about the handling of the crash: TypeError: could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1829401 Title: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support Status in packagekit package in Ubuntu: Triaged Status in packagekit source package in Eoan: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.98.2, the problem page at https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. [Back trace] Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", line 86, in on_pktask_finish results = self._pktask.generic_finish(result) gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support (8) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", line 89, in on_pktask_finish Gtk.ButtonsType.CANCEL, _("Error while refreshing cache")) File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init return super_init_func(self, **new_kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in __init__ self._init(*args, **new_kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init return super_init_func(self, **new_kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in __init__ _window_init(self, *args, **kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init return super_init_func(self, **new_kwargs) TypeError: could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
Seems like this kernel config change should be reverted for now. We can consider turning it back on later if rtkit receives changes to work better with this option. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: rtkit (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in linux package in Ubuntu: Confirmed Status in rtkit package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in rtkit source package in Focal: New Bug description: These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665/+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 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
** Bug watch added: github.com/systemd/systemd/issues #15356 https://github.com/systemd/systemd/issues/15356 ** Also affects: systemd via https://github.com/systemd/systemd/issues/15356 Importance: Unknown Status: Unknown ** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: systemd (Ubuntu Eoan) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Eoan) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Eoan: In Progress Bug description: Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output lines suppressed due to ratelimiting Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.7 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 18:09:06 2020 InstallationDate: Installed on 2019-11-01 (169 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-cosmic dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-cosmic:cvnQEMU:ct1:cvrpc-i440fx-cosmic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-cosmic dmi.sys.vendor: QEMU mtime.conffile..etc.systemd.resolved.conf: 2020-04-18T10:41:34.662328 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1873607/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
Thanks! upstream still hasn't decided on the patch, but I'll upload to focal anyway since this has a serious impact on users. Hopefully upstream will accept the patch later. -- 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/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [regression potential] Any regression would likely involve incorrectly configured network after an interface carrier gain/loss. [scope] This is needed for Focal, Eoan, and Bionic. While this only reproduces at boot for Focal, the general loss of configuration on carrier loss even when ConfigureWithoutCarrier=true is reproducable on all releases except Xenial, which does not have the ConfigureWithoutCarrier= parameter. [original description] Freshly installed Ubuntu 20.04 fully patched to days date with static IP address works fine and survives a reboot network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] however when converted to a bridged network for kvm network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] will not survive a reboot and required systemd-network to be restarted or @reboot /usr/sbin/netplan apply added to the crontab after a reboot the network can not b eaccseed and a systemctl status systemd-networkd produces systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 979 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 57662) Memory: 4.1M CGroup: /system.slice/systemd-networkd.service └─979 /lib/systemd/systemd-networkd Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for link '5' we don't know about, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring. systemctl restart systemd-networkd resolved the issue and a systemctl status systemd-network
[Touch-packages] [Bug 1866347] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_ad
workaround which worked for me: cd /tmp git clone https://git.launchpad.net/ubuntu/+source/apport sudo cp apport/apport/report.py /usr/lib/python3/dist-packages/apport/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1866347 Title: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport /whoopsie-upload- all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_address_to_offset:_build_proc_maps_cache Status in apport package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu17, the problem page at https://errors.ubuntu.com/problem/5cc81a1cde2a921ad2adcc00e2f8d13f2c9f76e8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866347/+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 1877294] [NEW] graphic problem and no internet connection
Public bug reported: every time I start my personal computer there is an error on the graphics module and I have to restart the service network manager in the terminal. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu May 7 13:53:42 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [104d:90ab] InstallationDate: Installed on 2020-05-01 (5 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: Sony Corporation SVE1511F1EW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=c4e39bf2-5485-4178-b290-aa431b8a172b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0180E5 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:bvnInsydeCorp.:bvrR0180E5:bd04/24/2012:svnSonyCorporation:pnSVE1511F1EW:pvrC107K8GJ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVE1511F1EW dmi.product.version: C107K8GJ dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 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 xserver.bootTime: Thu May 7 13:44:28 2020 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- 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/1877294 Title: graphic problem and no internet connection Status in xorg package in Ubuntu: New Bug description: every time I start my personal computer there is an error on the graphics module and I have to restart the service network manager in the terminal. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu May 7 13:53:42 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [104d:90ab] InstallationDate: Installed on 2020-05-01 (5 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: Sony Corporation SVE1511F1EW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=c4e39bf2-5485-4178-b290-aa431b8a172b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0180E5 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:
[Touch-packages] [Bug 1877159] Re: netlink: 'systemd-network': attribute type 5 has an invalid length.
Here is a strace of systemd-networkd when it was consuming 100% CPU: https://paste.ubuntu.com/p/2XwxWwW99q/ -- 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/1877159 Title: netlink: 'systemd-network': attribute type 5 has an invalid length. Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: This morning, our 2 Bionic machine configured with the wireguard's PPA and using systemd-networkd to configure the wireguard tunnel started misbehaving. Why this started just now is unclear ATM but their dmesg was filled with this: validate_nla: 100 callbacks suppressed netlink: 'systemd-network': attribute type 5 has an invalid length. netlink: 'systemd-network': attribute type 5 has an invalid length. netlink: 'systemd-network': attribute type 5 has an invalid length. netlink: 'systemd-network': attribute type 5 has an invalid length. netlink: 'systemd-network': attribute type 5 has an invalid length. netlink: 'systemd-network': attribute type 5 has an invalid length. netlink: 'systemd-network': attribute type 5 has an invalid length. netlink: 'systemd-network': attribute type 5 has an invalid length. netlink: 'systemd-network': attribute type 5 has an invalid length. netlink: 'systemd-network': attribute type 5 has an invalid length. Folks in #systemd mentioned https://github.com/systemd/systemd/issues/11575 which points to 2 commits missing from Bionic's systemd version: https://github.com/systemd/systemd/commit/7d0b26a027118ca063780421cb31c74e9d2664ee https://github.com/systemd/systemd/commit/624a47694cad4c87b2e807c32db656f3e9d679c5 Focal's systemd have the above commits. Would it be possible to backport those 2 commits to Bionic? Additional information: # uname -a Linux noc-eu1 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux # apt-cache policy systemd wireguard{,-tools,-dkms} systemd: Installed: 237-3ubuntu10.39 Candidate: 237-3ubuntu10.39 Version table: *** 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages wireguard: Installed: 1.0.20200319-1ubuntu1~18.04 Candidate: 1.0.20200319-1ubuntu1~18.04 Version table: *** 1.0.20200319-1ubuntu1~18.04 500 500 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic/main amd64 Packages 500 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status wireguard-tools: Installed: 1.0.20200319-1ubuntu1~18.04 Candidate: 1.0.20200319-1ubuntu1~18.04 Version table: *** 1.0.20200319-1ubuntu1~18.04 500 500 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status wireguard-dkms: Installed: 1.0.20200429-2~18.04 Candidate: 1.0.20200429-2~18.04 Version table: *** 1.0.20200429-2~18.04 500 500 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic/main amd64 Packages 500 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877159/+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 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
@ddstreet the previous upload finally landed in groovy, now I'm testing the next upload with this fix in in https://bileto.ubuntu.com/#/ticket/3801 . ** Changed in: systemd (Ubuntu Groovy) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: systemd (Ubuntu Groovy) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [regression potential] Any regression would likely involve incorrectly configured network after an interface carrier gain/loss. [scope] This is needed for Focal, Eoan, and Bionic. While this only reproduces at boot for Focal, the general loss of configuration on carrier loss even when ConfigureWithoutCarrier=true is reproducable on all releases except Xenial, which does not have the ConfigureWithoutCarrier= parameter. [original description] Freshly installed Ubuntu 20.04 fully patched to days date with static IP address works fine and survives a reboot network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] however when converted to a bridged network for kvm network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] will not survive a reboot and required systemd-network to be restarted or @reboot /usr/sbin/netplan apply added to the crontab after a reboot the network can not b eaccseed and a systemctl status systemd-networkd produces systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 979 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 57662) Memory: 4.1M CGroup: /system.slice/systemd-networkd.service └─979 /lib/systemd/systemd-networkd Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for link '5' we don't know about, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an address we don't remember:
[Touch-packages] [Bug 1866347] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_ad
How can I find 2.20.11-0ubuntu19 ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1866347 Title: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport /whoopsie-upload- all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_address_to_offset:_build_proc_maps_cache Status in apport package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu17, the problem page at https://errors.ubuntu.com/problem/5cc81a1cde2a921ad2adcc00e2f8d13f2c9f76e8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866347/+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 1866347] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_ad
Installed apport 2.20.11-0ubuntu8.8 in bionic, still same problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1866347 Title: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport /whoopsie-upload- all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_address_to_offset:_build_proc_maps_cache Status in apport package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu17, the problem page at https://errors.ubuntu.com/problem/5cc81a1cde2a921ad2adcc00e2f8d13f2c9f76e8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866347/+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 1866347] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_ad
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1866347 Title: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport /whoopsie-upload- all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_address_to_offset:_build_proc_maps_cache Status in apport package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu17, the problem page at https://errors.ubuntu.com/problem/5cc81a1cde2a921ad2adcc00e2f8d13f2c9f76e8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866347/+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 1876726] Re: software-properties-gtk crashes: dbus.proxies error
** Tags added: dbus ** Tags added: python ** Tags removed: dbus -- 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/1876726 Title: software-properties-gtk crashes: dbus.proxies error Status in software-properties package in Ubuntu: New Bug description: Expected: software-properties-gtk should launch properly; instead it crashes and doesn't launch. Out of the blue, I couldn't open Software so I checked the output of software-properties-gtk which is: ``` WARNING:root:system-image-cli failed, using defaults: [Errno 13] Permission denied: 'system-ima WARNING:root:system-image-cli failed, using defaults: [Errno 13] Permission denied: 'system-ima ERROR:dbus.proxies:Introspect error on :1.159:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 172, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.159 was not provided by any .service files ``` If I launch it with sudo I get circa the same output: ``` ERROR:dbus.proxies:Introspect error on :1.167:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 172, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.167 was not provided by any .service files ``` Additional info: $ uname -r `5.3.0-51-generic` $ dpkg -l software-properties-gtk | grep ii ``` ii software-properties-gtk 0.96.24.32.12 all manage the repositories that you install software from (gtk) ``` $ apt-cache policy software-properties-gtk ``` software-properties-gtk: Installed: 0.96.24.32.12 Candidate: 0.96.24.32.12 Version table: *** 0.96.24.32.12 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.96.24.32.1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu bionic/main i386 Packages ``` Release: Ubuntu 18.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1876726/+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 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
Few more things for my case (Dell Precision 7510). AUX headphones' sound seems to be connected to active input device: switching input devices (headphone mic, built-in mic, dock mic (unplugged)) causes sound to appear in the headphones. Although heavily distorted by noise. But the distortion is not like in Adam's (krychek) case. Although, getting headphones to work (w/ the distortion) and then logging in and out removes the noise. But touching input device settings in pavucontrol brings the noise (or the original issue) back. -- 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/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in gnome-control-center: Unknown Status in PulseAudio: New Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: Invalid Status in pulseaudio source package in Focal: In Progress Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+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 1868892] Re: initramfs-tools/hooks/udev for network *.link really sucks
This bug was fixed in the package systemd - 245.5-2ubuntu1 --- systemd (245.5-2ubuntu1) groovy; urgency=medium * Merge to Ubuntu from Debian unstable - Dropped changes: none systemd (245.5-2) unstable; urgency=medium * Cherry-pick various fixes from upstream master - network: add a flag to ignore gateway provided by DHCP server - userdb: when doing client-side NSS look-ups optionally avoid shadow look-ups - nss-systemd: don't synthesize root/nobody when iterating - core: make sure we don't get confused when setting TERM for a tty fd - core: make sure to restore the control command id, too * Install 60-block.rules in udev-udeb and initramfs-tools. The block device rules were split out from 60-persistent-storage.rules into its own rules file in v220. Those rules ensure that change events are emitted and the udev db is updated after metadata changes. Thanks to Pascal Hambourg (Closes: #958397) systemd (245.5-1ubuntu1) groovy; urgency=medium * Merge to Ubuntu from Debian unstable - Dropped changes: none systemd (245.5-1) unstable; urgency=medium [ Michael Biebl ] * New upstream version 245.5 * Rebase patches [ Dan Streetman ] * Follow symlinks when finding link files to copy into initramfs. If the /{etc,lib}/systemd/network directory itself is a symlink, the find command will not actually find any of the files in the dir it links to. Use the find -L param to follow symlinks. (LP: #1868892) * Remove Ubuntu-specific ondemand.service. New processors handle scaling/throttling in internal firmware (e.g. intel_pstate), and do not require OS config. Additionally, nobody else does this, not even Debian. -- Balint Reczey Tue, 28 Apr 2020 13:20:31 +0200 ** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1868892 Title: initramfs-tools/hooks/udev for network *.link really sucks Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: In Progress Bug description: [impact] If the /{etc,lib}/systemd/network directory itself is a symlink, the find command will not actually find any of the files in the dir it links to. [test case] $ sudo touch /etc/systemd/network/lp1868892.link $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic ... $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892 usr/lib/systemd/network/lp1868892.link $ sudo mv /etc/systemd/network /etc/systemd/network.abc $ sudo ln -s network.abc /etc/systemd/network $ sudo update-initramfs -u $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892 $ [regression potential] this adjusts how link files are included in the initramfs, so regressions would likely occur when creating new initramfs, such as failure to create initramfs at all, or failure to properly copy link files into the initramfs, causing network setup failure. [scope] this is a Debian/Ubuntu specific file, and the Debian MR was just opened, so this is needed for Debian and all releases of Ubuntu. [other info] This bug likely has a very limited impact, as it is uncommon to symlink either the /lib/systemd/network or /etc/systemd/network dirs. [original description] If one creates e.g. /etc/systemd/network.cu and /etc/systemd/network.fc and symlinks /etc/systemd/network to one of them, network setup will fail on reboot, because /usr/share/initramfs- tools/hooks/udev does a very poor job: it simply checks for a directory instead of the link files and therefore skips copying required files to the ram image. Another poor job is done when copying the files to the ram image: instead of following symlinks it copies them as which in turn makes them useless, because it does not copy the related dirs and thus the symlinks point to nothing. So keeping the system in an consistent state which such poor scripts is very hard, asking for trouble. Suggested fix is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1868892/+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 1877269] Re: Ubuntu crashes multiple time due to pulse audio. (alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large)
Thank you for your quick answer. There is a .crash file of pulseaudio dated on May 5th but I don't have enough memory to send it to you (see screenshot attached). As for reports there is one from March 2020 about Discord, here is the link. https://errors.ubuntu.com/oops/e8e9010a-702a-11ea-aad2-fa163e983629 Thank you again for your concern. Le jeu. 7 mai 2020 à 11:35, Daniel van Vugt a écrit : > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It sounds like some part of the system has crashed. To > help us find the cause of the crash please follow these steps: > > 1. Look in /var/crash for crash files and if found run: > ubuntu-bug YOURFILE.crash > Then tell us the ID of the newly-created bug. > > 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. > Do you find any links to recent problems on that page? If so then please > send the links to us. > > 3. If step 2 also failed then apply the workaround from bug 994921, > reboot, reproduce the crash, and retry step 1. > > Please take care to avoid attaching .crash files to bugs as we are > unable to process them as file attachments. It would also be a security > risk for yourself. > > > ** Changed in: pulseaudio (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1877269 > > Title: > Ubuntu crashes multiple time due to pulse audio. (alsa-util.c: > snd_pcm_delay() returned a value that is exceptionally large) > > Status in pulseaudio package in Ubuntu: > Incomplete > > Bug description: > Description: Ubuntu 18.04.4 LTS > Release: 18.04 > > pulseaudio: > Installé : 1:11.1-1ubuntu7.5 > Candidat : 1:11.1-1ubuntu7.5 >Table de version : >*** 1:11.1-1ubuntu7.5 500 > 500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main > amd64 Packages > 100 /var/lib/dpkg/status >1:11.1-1ubuntu7 500 > 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 > Packages > > > The OS freezes when using in normal conditions, usually VS Code, Discord > app and Spotify in browser. > When it does, I need to hard reboot by holding power button. > > I checked journalctl to confirm it was due to pulseaudio. > > alsa-util.c: snd_pcm_delay() returned a value that is exceptionally > large > > The above line is always the last to prompt in the boot journal. > It does not freeze instantly, it progressively freezes down, but > sometime Mozilla Firefox crashes and it freezes no more. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: pulseaudio 1:11.1-1ubuntu7.5 > Uname: Linux 5.1.15-surface-linux-surface x86_64 > ApportVersion: 2.20.9-0ubuntu7.14 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: saravanane 2071 F pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Thu May 7 11:00:37 2020 > InstallationDate: Installed on 2019-10-01 (218 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=fr_FR.UTF-8 >SHELL=/bin/bash > SourcePackage: pulseaudio > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/18/2019 > dmi.bios.vendor: Microsoft Corporation > dmi.bios.version: 108.2706.768 > dmi.board.name: Surface Pro 4 > dmi.board.vendor: Microsoft Corporation > dmi.chassis.type: 9 > dmi.chassis.vendor: Microsoft Corporation > dmi.modalias: > dmi:bvnMicrosoftCorporation:bvr108.2706.768:bd04/18/2019:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B09F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: > dmi.product.family: Surface > dmi.product.name: Surface Pro 4 > dmi.product.sku: Surface_Pro_4 > dmi.product.version: D:0B:09F:1C:03P:38 > dmi.sys.vendor: Microsoft Corporation > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877269/+subscriptions > ** Attachment added: "ubuntu-bug_cannot_send.png" https://bugs.launchpad.net/bugs/1877269/+attachment/5367717/+files/ubuntu-bug_cannot_send.png -- 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/1877269 Title: Ubuntu crashes multiple time due to pulse audio. (alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Description: Ubuntu 18.04.4 LTS Release: 18.04 pulseaudio: Installé : 1:11.1-1ubuntu7.5 Candidat : 1:11.1-1ubuntu7.5 Table de version : *** 1:11.1-1ubuntu7.5 500 500