[Touch-packages] [Bug 1906600] 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 1906600 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 ** Tags added: disco -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: New Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook
[Touch-packages] [Bug 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: New Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:
[Touch-packages] [Bug 1906601] Re: Display + HDMI not working properly. I suspect the automatically installed driver.
It appears "UNCLAIMED" in lshw is somewhat common. So I wouldn't take that to be evidence of a problem although it is suspicious. What is evidence of a real problem is the Xorg log shows software rendering is in use: [ 3.872] (II) FBDEV(0): hardware: EFI VGA (video memory: 8100kB) and the correct hardware device node is missing: [ 3.872] (EE) open /dev/dri/card0: No such file or directory This makes me think the kernel version is slightly too old for your GPU. Please try booting Ubuntu 20.10 or 20.04.1: https://ubuntu.com/download/desktop ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - Display + HDMI not working properly. I suspect the automatically installed driver. + FBDEV in use with amdgpu and there is no /dev/dri/card0 ** Summary changed: - FBDEV in use with amdgpu and there is no /dev/dri/card0 + FBDEV in use with amdgpu and there is no /dev/dri/card0 (hardware is AMD/ATI Renoir [1002:1636]) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: amdgpu -- 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/1906601 Title: FBDEV in use with amdgpu and there is no /dev/dri/card0 (hardware is AMD/ATI Renoir [1002:1636]) Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: New bug from: https://bugs.launchpad.net/ubuntu/+bug/1906525. lshw -c video gives same result of unclaimed video. Night light and HDMI still do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 2 22:09:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-56-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-12-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=9f7c4a34-4508-4d48-9c26-c7bf0045826a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA 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.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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/linux/+bug/1906601/+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 1906601] [NEW] Display + HDMI not working properly. I suspect the automatically installed driver.
Public bug reported: New bug from: https://bugs.launchpad.net/ubuntu/+bug/1906525. lshw -c video gives same result of unclaimed video. Night light and HDMI still do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 2 22:09:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-56-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-12-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=9f7c4a34-4508-4d48-9c26-c7bf0045826a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA 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.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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/1906601 Title: Display + HDMI not working properly. I suspect the automatically installed driver. Status in xorg package in Ubuntu: New Bug description: New bug from: https://bugs.launchpad.net/ubuntu/+bug/1906525. lshw -c video gives same result of unclaimed video. Night light and HDMI still do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 2 22:09:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-56-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-12-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=9f7c4a34-4508-4d48-9c26-c7bf0045826a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag
[Touch-packages] [Bug 1896098] Re: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack
@Chi-Wei, OK, got it. thx. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1896098 Title: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack Status in pulseaudio package in Ubuntu: Invalid Bug description: I suspect this is a pulseaudio or alsa bug. Our test team reported this: 1. Prepare Padme-3 machine and Install Ubuntu_20.04 OS . 2. Boot system. 3. Play audio or video file. 4. Open Settings > Sound. 5. Hot attach headset. 6. Notice that headset is selected as output device in sound settings and sound can be heard from headset => EXPECTED 7. While playback, select Internal Speaker as output device => KEYPOINT 9. Notice:SUT havo no sound from Internal Speakers => PROBLEM I was able to confirm this - it seems with the headphones connected that I can't select the system speakers. If I don't have headphones connected I can switch between dock audio and system speakers correctly - so it's just related to the audio jack Thanks Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1896098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1898386] Re: package libpam0g:amd64 1.3.1-5ubuntu4.1 failed to install/upgrade: el paquete libpam0g:amd64 no está listo para configurarse no se puede configurar (estado actual `
[Expired for pam (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pam (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1898386 Title: package libpam0g:amd64 1.3.1-5ubuntu4.1 failed to install/upgrade: el paquete libpam0g:amd64 no está listo para configurarse no se puede configurar (estado actual `half-installed') Status in pam package in Ubuntu: Expired Bug description: package libpam0g:amd64 1.3.1-5ubuntu4.1 failed to install/upgrade: el paquete libpam0g:amd64 no está listo para configurarse no se puede configurar (estado actual `half-installed') ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam0g:amd64 1.3.1-5ubuntu4.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: libpam0g:amd64: Configure NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 3 19:42:12 2020 DpkgHistoryLog: Start-Date: 2020-10-03 19:42:12 Commandline: apt install -f Requested-By: daniel (1000) DpkgTerminalLog: [1mdpkg:[0m error al procesar el paquete libpam0g:amd64 (--configure): el paquete libpam0g:amd64 no está listo para configurarse no se puede configurar (estado actual `half-installed') ErrorMessage: el paquete libpam0g:amd64 no está listo para configurarse no se puede configurar (estado actual `half-installed') InstallationDate: Installed on 2020-06-06 (118 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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.2ubuntu0.1 SourcePackage: pam Title: package libpam0g:amd64 1.3.1-5ubuntu4.1 failed to install/upgrade: el paquete libpam0g:amd64 no está listo para configurarse no se puede configurar (estado actual `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1898386/+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 1906525] Re: Display + HDMI not working properly. I suspect the automatically installed driver.
Thanks for the bug report. Unfortunately you seem to have packages from the "oibaf" PPA installed, which are known to cause a lot of graphics problems. Please remove that PPA from your system using 'ppa-purge' and then if the problems persist open a new bug. Alternatively, just reinstall Ubuntu without PPAs. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/1906525 Title: Display + HDMI not working properly. I suspect the automatically installed driver. Status in Ubuntu: Invalid Bug description: My display is not working properly. Ryzen 7, Radeon graphics ASUS Vivobook laptop. Display night light does not work and the HDMI port does not work as evidence. Furthermore, the display commands seem to signify that there is a driver that is not installed. But it was installed automatically and there is not selection that I can make in the additional drivers tab of the software update program. I reinstalled ubuntu 20.04 LTS to uninstall the graphics driver that had been freezing my computer non-stop in search of a way to get ubuntu bug support (support is not provided when using the driver amd reccomends using). (Screenfreeze bug https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1900777) So, there appears to be a driver installed. However, the display is unclaimed. (see below). I switched from gdm3 to lightdm, as that was recommended in someone’s answer but did me no good. I have not switched back. blaise@blaise-VivoBook2:~$ sudo lshw -c video [sudo] password for blaise: *-display UNCLAIMED description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:03:00.0 version: c2 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: latency=0 resources: memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe70-fe77 xrandr gives failed to get size of gamma for output default. This proves further evidence to me that the incorrect driver is not being used. Furthermore, the night light function and the HDMI functionality does not work. I spent my whole work day googling for a solution and trying various things yesterday, but the vast majority of solutions recommend installing a driver that has previously given me freezes. I can include all the sites that tI have visited to try and solve this problem upon request (Warning this list exceeds 50). All the help is greatly appreciated. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 2 07:18:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-56-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-12-01 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=9f7c4a34-4508-4d48-9c26-c7bf0045826a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA 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.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC.
[Touch-packages] [Bug 1895928] Re: Snap policy module fails to identify snaps if SCM_CREDENTIALS are missing from PA_COMMAND_AUTH request
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1895928 Title: Snap policy module fails to identify snaps if SCM_CREDENTIALS are missing from PA_COMMAND_AUTH request Status in pulseaudio package in Ubuntu: Fix Released Bug description: This bug was discovered while debugging the non-deterministic behaviour of the example program attached to bug 1886854. The snap policy module currently uses the credentials passed in an SCM_CREDENTIALS control message attached to the PA_COMMAND_AUTH request sent by the client. Credentials will only be attached to the message if at least one end of the connection has set the SO_PASSCRED socket option. In normal operation, both the client and server set SO_PASSCRED on their sockets, so this functions normally. The test program on the other bug used an alternative client library that didn't set SO_PASSCRED, which leads to a race between the client sending the PA_COMMAND_AUTH request and the server calling setsockopt(). If the client wins, the server will receive a message with an empty SCM_CREDENTIALS control message (pid=0, uid=65534, gid=65534). When the snap policy module gets these empty credentials, it would try to look up the confinement of pid 0. As there is no such process, the module decides that the client is not a snap. As any lookup via process ID is inherently racy, a better solution would be to use aa_getpeercon() to retrieve the client's security label in pa_native_protocol_connect(), and store it in the pa_client struct. We can then look up this in the policy module when it comes time to do the check. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895928/+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 1835660] Re: initramfs unpacking failed
** Description changed: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. + + [Impact] + + * Decoding failure messages in dmsg with a single lz4 initrd + + * Multiple lz4 compressed initrds cannot be decompressed by kernel, + when loaded by grub + + * Multiple lz4 compressed initrds cannot be decompressed by kernel, + when there is padding between them + + [Test Case] + + * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 + + * Create an lz4 compressed initrd with a single test-file in it with + some content. I.e. echo "second-initrd" > test-file, and then pack that + with cpio hewc owned by root & lz4 -l. + + * Create a combined padded initrd of stock initrd, pad4, and the test- + marker initrd created above. + + * Boot above with "break=top" kernel command line. + + * With broken kernels, there should be dmesg error message that + decoding failed, and one will observe that /test-file does not exist in + the shell. + + * With fixed kernel, /test-file in the initrd shell should exist, and + should have the expected content "second-initrd". + + * The alignment and padding in the above test case depends on the size + of the first initrd => if a given padded initrd does not reproduce the + problem, try varying the size of the first initrd or that of the padding + between 0..4. + + + [Where problems could occur] + + * This changes compatible lz4 decompressor in the kernel, which can + also be used by other kernel modules such as cryptography, squashfs, + zram, f2fs, comprssed kernel image, pstore. For example, previously + rejected files with "bogus" length and extra padding may now be + accepted, whereas they were previously getting rejected by the + decompressor. + + * Ideally kernel should switch to the stable lz4 format which has + better specification of end of stream. ** Patch added: "0001-lib-decompress_unlz4.c-correctly-handle-zero-padding.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+attachment/5440421/+files/0001-lib-decompress_unlz4.c-correctly-handle-zero-padding.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the
[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user
** Description changed: [Impact] The apport-test-crashes package, which is used to test the Error Tracker deployments, fails produce crash files for binary applications since "various security hardening fixes" were included in apport. The problematic change is the dropping of supplemental groups in data/apport. This results in a PermissionError as it is not the root user who is calling /usr/share/apport/apport. [Test Case] The least convulted test case involves using the generate-sigsegv-crash.py script from apport-test-crashes. This ends up using a command similar to '/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < /tmp/20.10-gnome-calculator.core' which then will encounter the Traceback. 1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary as we are not running as root) 2) Put a copy of generate-sigsegv-crash.py on disk. 3) Run 'python3 /tmp/generate-sigsegv-crash.py cat' 4) Observe the following Traceback: Traceback (most recent call last): - File "/tmp/tmpvkt5d266/apport", line 599, in - drop_privileges(True) - File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges - os.setgroups([]) + File "/tmp/tmpvkt5d266/apport", line 599, in + drop_privileges(True) + File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges + os.setgroups([]) PermissionError: [Errno 1] Operation not permitted With the version of apport from -proposed you'll receive no such Traceback. [Regression Potential] If there is an error in the python code we code see a new traceback for any and all crashes being generated, so ensure regular crash generation works too. + + apport-test-crashes code is here: + https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/ -- 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/1906565 Title: traceback when running apport as non-root user Status in apport package in Ubuntu: In Progress Status in apport source package in Xenial: New Status in apport source package in Bionic: New Status in apport source package in Focal: New Status in apport source package in Groovy: New Bug description: [Impact] The apport-test-crashes package, which is used to test the Error Tracker deployments, fails produce crash files for binary applications since "various security hardening fixes" were included in apport. The problematic change is the dropping of supplemental groups in data/apport. This results in a PermissionError as it is not the root user who is calling /usr/share/apport/apport. [Test Case] The least convulted test case involves using the generate-sigsegv-crash.py script from apport-test-crashes. This ends up using a command similar to '/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < /tmp/20.10-gnome-calculator.core' which then will encounter the Traceback. 1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary as we are not running as root) 2) Put a copy of generate-sigsegv-crash.py on disk. 3) Run 'python3 /tmp/generate-sigsegv-crash.py cat' 4) Observe the following Traceback: Traceback (most recent call last): File "/tmp/tmpvkt5d266/apport", line 599, in drop_privileges(True) File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges os.setgroups([]) PermissionError: [Errno 1] Operation not permitted With the version of apport from -proposed you'll receive no such Traceback. [Regression Potential] If there is an error in the python code we code see a new traceback for any and all crashes being generated, so ensure regular crash generation works too. apport-test-crashes code is here: https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1906565/+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 1906565] Re: traceback when running apport as non-root user
** Also affects: apport (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Focal) Importance: Undecided Status: New ** Tags added: fr-978 ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu) Status: New => In Progress ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Changed in: apport (Ubuntu Bionic) Importance: Undecided => High ** Changed in: apport (Ubuntu Xenial) Importance: Undecided => High ** Changed in: apport (Ubuntu Focal) Importance: Undecided => High ** Changed in: apport (Ubuntu Bionic) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu Focal) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu Groovy) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu Groovy) Importance: Undecided => High -- 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/1906565 Title: traceback when running apport as non-root user Status in apport package in Ubuntu: In Progress Status in apport source package in Xenial: New Status in apport source package in Bionic: New Status in apport source package in Focal: New Status in apport source package in Groovy: New Bug description: [Impact] The apport-test-crashes package, which is used to test the Error Tracker deployments, fails produce crash files for binary applications since "various security hardening fixes" were included in apport. The problematic change is the dropping of supplemental groups in data/apport. This results in a PermissionError as it is not the root user who is calling /usr/share/apport/apport. [Test Case] The least convulted test case involves using the generate-sigsegv-crash.py script from apport-test-crashes. This ends up using a command similar to '/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < /tmp/20.10-gnome-calculator.core' which then will encounter the Traceback. 1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary as we are not running as root) 2) Put a copy of generate-sigsegv-crash.py on disk. 3) Run 'python3 /tmp/generate-sigsegv-crash.py cat' 4) Observe the following Traceback: Traceback (most recent call last): File "/tmp/tmpvkt5d266/apport", line 599, in drop_privileges(True) File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges os.setgroups([]) PermissionError: [Errno 1] Operation not permitted With the version of apport from -proposed you'll receive no such Traceback. [Regression Potential] If there is an error in the python code we code see a new traceback for any and all crashes being generated, so ensure regular crash generation works too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1906565/+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 1906565] [NEW] traceback when running apport as non-root user
Public bug reported: [Impact] The apport-test-crashes package, which is used to test the Error Tracker deployments, fails produce crash files for binary applications since "various security hardening fixes" were included in apport. The problematic change is the dropping of supplemental groups in data/apport. This results in a PermissionError as it is not the root user who is calling /usr/share/apport/apport. [Test Case] The least convulted test case involves using the generate-sigsegv-crash.py script from apport-test-crashes. This ends up using a command similar to '/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < /tmp/20.10-gnome-calculator.core' which then will encounter the Traceback. 1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary as we are not running as root) 2) Put a copy of generate-sigsegv-crash.py on disk. 3) Run 'python3 /tmp/generate-sigsegv-crash.py cat' 4) Observe the following Traceback: Traceback (most recent call last): File "/tmp/tmpvkt5d266/apport", line 599, in drop_privileges(True) File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges os.setgroups([]) PermissionError: [Errno 1] Operation not permitted With the version of apport from -proposed you'll receive no such Traceback. [Regression Potential] If there is an error in the python code we code see a new traceback for any and all crashes being generated, so ensure regular crash generation works too. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- 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/1906565 Title: traceback when running apport as non-root user Status in apport package in Ubuntu: New Bug description: [Impact] The apport-test-crashes package, which is used to test the Error Tracker deployments, fails produce crash files for binary applications since "various security hardening fixes" were included in apport. The problematic change is the dropping of supplemental groups in data/apport. This results in a PermissionError as it is not the root user who is calling /usr/share/apport/apport. [Test Case] The least convulted test case involves using the generate-sigsegv-crash.py script from apport-test-crashes. This ends up using a command similar to '/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < /tmp/20.10-gnome-calculator.core' which then will encounter the Traceback. 1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary as we are not running as root) 2) Put a copy of generate-sigsegv-crash.py on disk. 3) Run 'python3 /tmp/generate-sigsegv-crash.py cat' 4) Observe the following Traceback: Traceback (most recent call last): File "/tmp/tmpvkt5d266/apport", line 599, in drop_privileges(True) File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges os.setgroups([]) PermissionError: [Errno 1] Operation not permitted With the version of apport from -proposed you'll receive no such Traceback. [Regression Potential] If there is an error in the python code we code see a new traceback for any and all crashes being generated, so ensure regular crash generation works too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1906565/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
Crash happened on this dell latitude which I am supposed to use for my PhD. Happened at the very end of the installation, when almost completely loaded. Please contact me (josja.vanbe...@gmail.com) for any possible solution. I am desperate. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64
[Touch-packages] [Bug 1906364] Re: unattended-upgrade still restarts blacklisted daemons
This sounds like another dupe of https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1906364 Title: unattended-upgrade still restarts blacklisted daemons Status in containerd package in Ubuntu: Confirmed Status in docker.io package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Won't Fix Bug description: Hello, Today plenty of our systems running ubuntu 20.04 were restarting the docker daemon, even if i blacklisted the docker package. Since docker has an dependency on containerd thats the reason why it was restarted. IMO the blacklist should also check the full tree of dependencies... This should NOT happen! From the log you find: 2020-12-01 06:40:13,881 INFO Starting unattended upgrades script 2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:13,882 INFO Initial whitelist (not strict): 2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils 2020-12-01 06:40:19,140 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2020-12-01 06:40:46,996 INFO All upgrades installed 2020-12-01 06:40:50,732 INFO Starting unattended upgrades script 2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:50,733 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:50,733 INFO Initial whitelist (not strict): Also this happened for us on plenty of our servers almost at the same (why the unattended updates are not spread over time?), which destroyed the second time an production environment. This is not how unattended-upgraded should be, sadly this package lost our trust and we disable it and schedule the 'unattended updates' now on our own. PS: Not to say that on some servers the docker daemon did not even restart.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1906364/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04
** Changed in: hud (Ubuntu Xenial) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/987060 Title: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04 Status in Unity HUD: Confirmed Status in Application Menu Indicator: Confirmed Status in Unity: Won't Fix Status in firefox package in Ubuntu: Incomplete Status in hud package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Status in firefox source package in Xenial: Incomplete Status in hud source package in Xenial: Confirmed Status in unity source package in Xenial: Invalid Bug description: unity-panel-service and hud-service quickly racks up memory and CPU usage until I kill it when invoking the HUD on Firefox. It's taking anywhere from a few minutes to half an hour, but it sometimes makes the system completely unusable. 1. run Firefox 12.0 in the foreground 2. hit Alt to bring up HUD 3. type any text 4. select one proposal from HUD 5. wait for unity-panel-service and hud-service to fill up the remaining RAM and swap space. This is due to a high number of bookmarks in a user profile (hundreds). To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/987060/+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 1759014] Re: Netplan has no way to control DHCP client
The fix for dns override for dhcp4 does not work with network manager. Netplan Generated config: [ipv4] method=auto dns=8.8.8.8;1.1.1.1 What is actually in /var/run/systemd/resolve/resolv.conf : nameserver 192.168.1.254 nameserver 8.8.8.8 nameserver 1.1.1.1 search attlocal.net Required fix for network manager: The line "ignore-auto-dns=true" has to be added by netplan. I have verified that this generates the expected resolv.conf. [ipv4] method=auto ignore-auto-dns=true dns=8.8.8.8;1.1.1.1; -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1759014 Title: Netplan has no way to control DHCP client Status in Default settings and artwork for Baltix OS: New Status in netplan: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in netplan.io source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] DHCP configurations where custom settings (routes, nameservers, etc.) need to be applied. [Test case] 1) Configure netplan for the particulars of the network by configuring an appropriate dhcp{4,6}-override stanza: network: version: 2 ethernets: engreen: dhcp4: true dhcp4-overrides: use-dns: false use-routes: false route-metric: Additionally, if so required, add a custom DNS / routes to the configuration. e.g. nameservers: search: [lab, kitchen] addresses: [8.8.8.8] (See https://netplan.io/reference#dhcp-overrides for the available options) 2) Run 'netplan apply' or reboot to have the configuration applied. 3) Validate that the routes / DNS are properly ignored and/or replaced by the defined values. [Regression potential] Minimal; this adds new values to the configuration generated for networkd or NetworkManager. Existing configurations will remain unchanged, but new configurations using the dhcp{4,6}-overrides fields will benefit from additional flexibility. --- Currently DHCP appears to be an all or nothing boolean, which is insufficient for many network configurations. Ideally all of the DHCP configuration options supported by systemd would also be supported in netplan: https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options As an example, consider the following netplan configuration: network: version: 2 renderer: networkd ethernets: enp0s3: dhcp4: yes nameservers: [8.8.8.8,8.8.4.4] After running netplan apply I check the nameservers with systemd- resolve --status and it shows: DNS Servers: 8.8.8.8 8.8.4.4 192.168.1.1 Here, "192.168.1.1" was provided by my DHCP server. On this particular node, I only want the manually configured DNS servers, but netplan has no way to indicate this. To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1759014/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04
** Changed in: hud (Ubuntu Xenial) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/987060 Title: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04 Status in Unity HUD: Confirmed Status in Application Menu Indicator: Confirmed Status in Unity: Won't Fix Status in firefox package in Ubuntu: Incomplete Status in hud package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Status in firefox source package in Xenial: Incomplete Status in hud source package in Xenial: In Progress Status in unity source package in Xenial: Invalid Bug description: unity-panel-service and hud-service quickly racks up memory and CPU usage until I kill it when invoking the HUD on Firefox. It's taking anywhere from a few minutes to half an hour, but it sometimes makes the system completely unusable. 1. run Firefox 12.0 in the foreground 2. hit Alt to bring up HUD 3. type any text 4. select one proposal from HUD 5. wait for unity-panel-service and hud-service to fill up the remaining RAM and swap space. This is due to a high number of bookmarks in a user profile (hundreds). To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/987060/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Confirm this issue with my Logitech H800 headset and also with Bose Mini II Soundlink. I hear audio successfully on both devices irrespective of A2DP or HSP/HSF. But microphone doesn't work on either mode. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-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-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)
Setting to verification-done for Groovy given that the buckets linked to in the bug description do not contain whoopsie version number 0.2.72.1 and there are no new buckets with similar signatures. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy ** Changed in: whoopsie (Ubuntu Bionic) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: whoopsie (Ubuntu Focal) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: whoopsie (Ubuntu Bionic) Status: New => In Progress ** Changed in: whoopsie (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1899100 Title: whoopsie assert failure: double free or corruption (fasttop) Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Bionic: In Progress Status in whoopsie source package in Focal: In Progress Status in whoopsie source package in Groovy: Fix Committed Bug description: [Impact] whoopsie is crashing somewhat regularly. There are a couple of crashes in the Error Tracker which look similar: https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98 As of yet (2020-11-22) neither crash is happening with whoopsie version 0.2.73. [Test Case] We don't have a manual test case for this crash report but given the number of crashes in the Error Tracker and the number of users of whoopsie the absence of the same crash occurring with the new version of whoopsie should be enough to consider this verified. [Regression Potential] Whoopsie will no longer upload crash reports with duplicate keys but this was not something it should have been doing in the first place. That being said we should also test whoopsie with a sample of crashes (apport-test-crashes) and ensure they are received by the staging version of the Ubuntu Error Tracker. Original Description Apport popped up saying whoopsie had crashed (I assume during a previous crash report upload?) ProblemType: CrashDistroRelease: Ubuntu 20.10 Package: whoopsie 0.2.72 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AssertionMessage: double free or corruption (fasttop) CasperMD5CheckResult: skip CrashCounter: 1 Date: Fri Oct 9 08:08:56 2020 ExecutablePath: /usr/bin/whoopsie InstallationDate: Installed on 2019-11-18 (325 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: /usr/bin/whoopsie -f ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) RelatedPackageVersions: apport-noui N/ASignal: 6SourcePackage: whoopsie StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption (fasttop)") at malloc.c:5389 _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at malloc.c:4298 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: whoopsie assert failure: double free or corruption (fasttop) UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1899100/+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 1906420] Re: Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author)
I also run Desktop Icons NG, and agree that it is superior to the the original Desktop Icons extension. Even if the original version is still supported, my impression is that the NG version is more actively maintained and is the focus of the author's development efforts. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1906420 Title: Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author) Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: By default, Ubuntu installs the Gnome extension "Desktop Icons" [1] (by rastersoft). Unfortunately, this extension is now unmaintained, is problematic, and leads to several bugs, including but not limited to Bug #1901150 and Bug #1813441. The same author has created, and continues to maintain, the far superior "Desktop Icons NG (DING)" [2]. It solves a number of problems including the two aforementioned bugs. It's possible to disable, but not uninstall, "Desktop Icons", and then to install "Desktop Icons NG (DING)". I did this a while ago with great results. If Canonical replaces the former with the latter, not only will Ubuntu be using a better desktop manager, but also it will be able clear all related bugs at a stroke. This is a simple, cheap, quick and effective solution that will let the devs concentrate on more important tasks. Please give this serious consideration. More information: Ubuntu 20.04.1 LTS 64-bit Gnome version 3.36.3 [1] https://extensions.gnome.org/extension/1465/desktop-icons/ [2] https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1906420/+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 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
Hi there. Got the no-compositing with Window Manager Tweaks solution working at the first try. AMD Radeon 535 with 2G. 20.04. Subscribing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in Linux: Unknown Status in libxcb package in Ubuntu: Confirmed Status in xfwm4 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E495 dmi.product.name: 20NECTO1WW dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-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/linux/+bug/1873895/+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 1854314] Re: Legacy directory /var/run in /lib/systemd/system/dbus.socket
Same thing here ... Dec 1 06:42:11 lx-dev3 containerd[845]: time="2020-12-01T06:42:11.225821304-05:00" level=info msg="Stop CRI service" Dec 1 06:42:11 lx-dev3 containerd[845]: time="2020-12-01T06:42:11.242385111-05:00" level=info msg="Stop CRI service" Dec 1 06:42:11 lx-dev3 containerd[845]: time="2020-12-01T06:42:11.253040416-05:00" level=info msg="Event monitor stopped" Dec 1 06:42:11 lx-dev3 containerd[845]: time="2020-12-01T06:42:11.253082773-05:00" level=info msg="Stream server stopped" Dec 1 06:42:11 lx-dev3 systemd[1]: containerd.service: Succeeded. Dec 1 06:42:11 lx-dev3 systemd[1]: Stopped containerd container runtime. Dec 1 06:42:14 lx-dev3 systemd[1]: Reloading. Dec 1 06:42:14 lx-dev3 systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Dec 1 06:42:14 lx-dev3 systemd[1]: /etc/systemd/system/rc-local.service:11: Support for option SysVStartPriority= has been removed and it is ignored Dec 1 06:42:14 lx-dev3 systemd[1]: /lib/systemd/system/docker.socket:6: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file accordingly. Dec 1 06:42:15 lx-dev3 systemd[1]: Reloading. Dec 1 06:42:15 lx-dev3 systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Dec 1 06:42:15 lx-dev3 systemd[1]: /etc/systemd/system/rc-local.service:11: Support for option SysVStartPriority= has been removed and it is ignored Dec 1 06:42:15 lx-dev3 systemd[1]: /lib/systemd/system/docker.socket:6: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file accordingly. Dec 1 06:42:15 lx-dev3 systemd[1]: Starting containerd container runtime... Dec 1 06:42:15 lx-dev3 systemd[1]: Started containerd container runtime. ... And, after that, instead of having a file /var/run/docker I had a file /var/run/docker= -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1854314 Title: Legacy directory /var/run in /lib/systemd/system/dbus.socket Status in D-Bus: New Status in dbus package in Ubuntu: Fix Committed Status in dbus package in Debian: Fix Released Bug description: dbus/focal-proposed,now 1.12.16-2ubuntu1 amd64 Re(o)curring after each new upgrade of dbus, for quite some time and still... $ dmesg|grep accordingly systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Originally: $cat /lib/systemd/system/dbus.socket [Unit] Description=D-Bus System Message Bus Socket [Socket] ListenStream=/var/run/dbus/system_bus_socket After change: $cat /lib/systemd/system/dbus.socket [Unit] Description=D-Bus System Message Bus Socket [Socket] ListenStream=/run/dbus/system_bus_socket To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1854314/+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 1906525] [NEW] Display + HDMI not working properly. I suspect the automatically installed driver.
Public bug reported: My display is not working properly. Ryzen 7, Radeon graphics ASUS Vivobook laptop. Display night light does not work and the HDMI port does not work as evidence. Furthermore, the display commands seem to signify that there is a driver that is not installed. But it was installed automatically and there is not selection that I can make in the additional drivers tab of the software update program. I reinstalled ubuntu 20.04 LTS to uninstall the graphics driver that had been freezing my computer non-stop in search of a way to get ubuntu bug support (support is not provided when using the driver amd reccomends using). (Screenfreeze bug https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1900777) So, there appears to be a driver installed. However, the display is unclaimed. (see below). I switched from gdm3 to lightdm, as that was recommended in someone’s answer but did me no good. I have not switched back. blaise@blaise-VivoBook2:~$ sudo lshw -c video [sudo] password for blaise: *-display UNCLAIMED description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:03:00.0 version: c2 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: latency=0 resources: memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe70-fe77 xrandr gives failed to get size of gamma for output default. This proves further evidence to me that the incorrect driver is not being used. Furthermore, the night light function and the HDMI functionality does not work. I spent my whole work day googling for a solution and trying various things yesterday, but the vast majority of solutions recommend installing a driver that has previously given me freezes. I can include all the sites that tI have visited to try and solve this problem upon request (Warning this list exceeds 50). All the help is greatly appreciated. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 2 07:18:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-56-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-12-01 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=9f7c4a34-4508-4d48-9c26-c7bf0045826a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA 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.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103+git2011061830.fc479e~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.0~git2012010730.688dda~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx 21.0~git2012010730.688dda~oibaf~f version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu ** Description changed: - - - --- + My display is not working properly. Ryzen 7, Radeon graphics ASUS + Vivobook laptop. Display night light
[Touch-packages] [Bug 1903329] Re: SRU the current 2.48.9 stable update
> Should groovy also get the fix for upstream issue 642? I suppose it wouldn't hurt. Adding the rls-gg-incoming tag to consider whether this is worthwhile. ** Tags added: rls-gg-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1903329 Title: SRU the current 2.48.9 stable update Status in librsvg package in Ubuntu: Fix Released Status in librsvg source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, which fixes a number of issues, including a regression[1] since librsvg 2.40.x which was shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant changes between Ubuntu 20.04's current librsvg 2.48.7 (that version was also introduced by an SRU back in July[3]) and the current version 2.48.9. The complete list of changes is available on GNOME GitLab[4]. * Test case The update is part of GNOME stable updates[5]. Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke testing to try and detect SVG rendering issues should be performed. * Notes about this report This is my first SRU request (and at the same time my first launchpad bug report). I'm not really familiar with the whole SRU process which is why I first asked about it on Ubuntu's official discourse forum[6]. Canonical's Sebastien Bacher encouraged me to open this ticket. I've copied over some parts of the last librsvg SRU ticket[3]. I hope this is fine. Thanks for considering this SRU. [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS [3]: https://bugs.launchpad.net/bugs/1884326 [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9 [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [6]: https://discourse.ubuntu.com/t/most-straight-forward-way-to-get- librsvg2-microrelease-update-into-focal-updates/19238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+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 1901609] Re: signond causes qprocess crash
Also uploaded to groovy and focal as 8.59+17.10.20170606-0ubuntu2.20.10.1 and 8.59+17.10.20170606-0ubuntu2.20.04.1 respectively ** Changed in: signon (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: signon (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 signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Fix Released Status in signon source package in Focal: In Progress Status in signon source package in Groovy: In Progress Status in signon source package in Hirsute: Fix Released Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1846334] Re: cupsd assert failure: free(): invalid pointer
Also happening to me for a Samsung CLX-3300 Ubuntu 20.04 LTS -- 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/1846334 Title: cupsd assert failure: free(): invalid pointer Status in cups package in Ubuntu: Confirmed Bug description: Just running in the background, no user action (printing) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: cups-daemon 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: free(): invalid pointer Date: Tue Oct 1 19:41:35 2019 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2019-02-09 (234 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) Lpstat: device for HP_LaserJet_CM1415fn_44A808_: implicitclass://HP_LaserJet_CM1415fn_44A808_/ device for Samsung_C48x_Series_SEC84251900EE44_: implicitclass://Samsung_C48x_Series_SEC84251900EE44_/ MachineType: Dell Inc. Latitude E6530 Papersize: letter PpdFiles: HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at malloc.c:5332 _int_free (av=, p=, have_lock=0) at malloc.c:4173 ?? () from /lib/x86_64-linux-gnu/libcups.so.2 ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2 Title: cupsd assert failure: free(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.sku: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334/+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 1903329] Re: SRU the current 2.48.9 stable update
Hi Brian I've succesfully installed and tested the `librsvg2-*` v2.48.9-1ubuntu0.20.04.1 packages on focal and can confirm that they work as expected for me, meaning i.a. that the bug I suffered from in the previous v2.48.7 is fixed. I've used the CLI `rsvg-convert` as well as the R package rsvg[1] (which uses the C bindings provided by `librsvg2-dev`) to convert SVG images to PDF. Everything was fine, no regression as far as I can tell. Thank you very much, Oliver, Brian and everyone else involved for the SRU work! [1]: https://github.com/jeroen/rsvg#readme ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1903329 Title: SRU the current 2.48.9 stable update Status in librsvg package in Ubuntu: Fix Released Status in librsvg source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, which fixes a number of issues, including a regression[1] since librsvg 2.40.x which was shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant changes between Ubuntu 20.04's current librsvg 2.48.7 (that version was also introduced by an SRU back in July[3]) and the current version 2.48.9. The complete list of changes is available on GNOME GitLab[4]. * Test case The update is part of GNOME stable updates[5]. Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke testing to try and detect SVG rendering issues should be performed. * Notes about this report This is my first SRU request (and at the same time my first launchpad bug report). I'm not really familiar with the whole SRU process which is why I first asked about it on Ubuntu's official discourse forum[6]. Canonical's Sebastien Bacher encouraged me to open this ticket. I've copied over some parts of the last librsvg SRU ticket[3]. I hope this is fine. Thanks for considering this SRU. [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS [3]: https://bugs.launchpad.net/bugs/1884326 [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9 [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [6]: https://discourse.ubuntu.com/t/most-straight-forward-way-to-get- librsvg2-microrelease-update-into-focal-updates/19238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+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 1905735] Re: ubuntu-image autopkgtests failing since python-debian 0.1.38
https://launchpad.net/ubuntu/+source/ubuntu-image/1.10+20.10ubuntu3 ** Changed in: ubuntu-image (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: python-debian (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-debian in Ubuntu. https://bugs.launchpad.net/bugs/1905735 Title: ubuntu-image autopkgtests failing since python-debian 0.1.38 Status in python-debian package in Ubuntu: Fix Committed Status in ubuntu-image package in Ubuntu: Fix Released Status in python-debian package in Debian: Unknown Bug description: In the tests it seems that since some - yet to be found - change ~20th Nov the tests of ubuntu-image fail. Tests all list those three sub-tests as failing: unittests.sh FAIL non-zero exit status 1 qa FAIL non-zero exit status 1 coverage.sh FAIL non-zero exit status 1 Fails all seem to be related to some python/pytest/py* change that might have slipped in without gating on this test. Ubuntu-image itself also isn't new - still the same as in groovy ubuntu-image | 1.10+20.10ubuntu2 | groovy | source, all ubuntu-image | 1.10+20.10ubuntu2 | hirsute| source, all == log start === Obtaining file:///tmp/autopkgtest.ZuL7Da/build.chY/src ERROR: Command errored out with exit status 1: command: /tmp/autopkgtest.ZuL7Da/build.chY/src/.tox/py38-nocov/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/autopkgtest.ZuL7Da/build.chY/src/setup.py'"'"'; __file__='"'"'/tmp/autopkgtest.ZuL7Da/build.chY/src/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-yaplrymq cwd: /tmp/autopkgtest.ZuL7Da/build.chY/src/ Complete output (5 lines): Traceback (most recent call last): File "", line 1, in File "/tmp/autopkgtest.ZuL7Da/build.chY/src/setup.py", line 49, in __version__ = str(Changelog(infp).get_version()) AttributeError: 'Changelog' object has no attribute 'get_version' ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output. === log end The issue reproducible in local KVM-autopkgtest against hirsute-proposed and hirsute-release for me (I mistyped before). Example: sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries --apt-upgrade --apt-pocket=proposed --shell-fail ubuntu-image_1.10+20.10ubuntu2.dsc --testname=qa -- qemu --qemu-options='-cpu host' --ram-size=1536 --cpus 2 ~/work/autopkgtest-hirsute-amd64.img In terms of similar bug signatures I found https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973227 Fixed by: https://gitlab.kitware.com/debian/dh-cmake/-/commit/3337c8e0e9ebd109490d3c40f0bd5c1e367bedc8 Looking for the same issue in ubuntu-image has shown an entry in setup.py setup.py:49:__version__ = str(Changelog(infp).get_version()) And now that we know all that we see https://launchpad.net/ubuntu/+source/python-debian/+publishinghistory New version in since 2020-11-20 02:23:27 CET That is a perfect match to our bug. $ diff -Naur python-debian-0.1.3[78]/lib/debian/changelog.py ... -def get_version(self): -# type: () -> Version +def _get_version(self): +# type: () -> Optional[Version] """Return a Version object for the last version""" -return self._blocks[0].version +return self._blocks[0].version # type: ignore ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1905735/+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 1733159] Re: package wogerman (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 139
** Package changed: hkgerman (Ubuntu) => dictionaries-common (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/1733159 Title: package wogerman (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 139 Status in dictionaries-common package in Ubuntu: New Bug description: don't know hat has happened, and i cannot use my touchpad anymore ProblemType: Package DistroRelease: Ubuntu 17.10 Package: wogerman (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 Date: Sat Nov 18 06:52:26 2017 DuplicateSignature: package:wogerman:(not installed) Removing wogerman (1:2-31) ... Segmentation fault (core dumped) dpkg: error processing package wogerman (--remove): subprocess installed post-removal script returned error exit status 139 ErrorMessage: subprocess installed post-removal script returned error exit status 139 Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: hkgerman Title: package wogerman (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1733159/+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 1870876] Re: docker stopped when containerd updated
*** This bug is a duplicate of bug 1870514 *** https://bugs.launchpad.net/bugs/1870514 As a workaround I opted for using a systemd unit file to create a loose dependency between containerd and dockerd. Here's how: As root: Make the override directory (permission 755) mkdir /etc/systemd/system/containerd.service.d/ Create the override file in the above directory (permissions 644) vi override.conf Add the following to the file [Unit] Before=docker.service Wants=docker.service Restart systemd daemon systemctl daemon-reload Check it works Stop containerd systemctl stop containerd Check dockerd has stopped systemctl status docker Start containerd systemctl start containerd Check dockerd has started systemctl status docker ++ Some links to other documentation on the subject https://www.shellhacks.com/systemd-service-file-example/ https://man7.org/linux/man-pages/man5/systemd.service.5.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+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 1733159] [NEW] package wogerman (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 139
You have been subscribed to a public bug: don't know hat has happened, and i cannot use my touchpad anymore ProblemType: Package DistroRelease: Ubuntu 17.10 Package: wogerman (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 Date: Sat Nov 18 06:52:26 2017 DuplicateSignature: package:wogerman:(not installed) Removing wogerman (1:2-31) ... Segmentation fault (core dumped) dpkg: error processing package wogerman (--remove): subprocess installed post-removal script returned error exit status 139 ErrorMessage: subprocess installed post-removal script returned error exit status 139 Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: hkgerman Title: package wogerman (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dictionaries-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- package wogerman (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 139 https://bugs.launchpad.net/bugs/1733159 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. -- 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 1906493] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Tags removed: 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/1906493 Title: package initramfs-tools 0.136ubuntu6.3 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: Cannot create report: [Errno 17] File exists: '/var/crash/initramfs-tools.0.crash' Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Dec 2 17:30:43 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-05-18 (1658 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.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-12-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1906493/+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 1906493] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/initramfs-tools.0.crash' Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Dec 2 17:30:43 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-05-18 (1658 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.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-12-02 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1906493 Title: package initramfs-tools 0.136ubuntu6.3 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: Cannot create report: [Errno 17] File exists: '/var/crash/initramfs-tools.0.crash' Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Dec 2 17:30:43 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-05-18 (1658 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.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-12-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1906493/+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 1246981] Re: Bluetooth devices fail to re-connect after sleep.
I notice similar behaviour on 20.10, Dell XPS 13 7390 2-in-1, Logitech M590 When I open Settings->Bluetooth, which takes a sec or two, something seems to get triggered and the mouse starts working again. -- 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/1246981 Title: Bluetooth devices fail to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+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