[Touch-packages] [Bug 1743572] Re: package linux-image-4.13.0-25-generic 4.13.0-25.29 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 143
The fault occurred in the version that was reported on software listed in bug report. No issue in the current version on Ubuntu. Close as resolved in future version of software. -- 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/1743572 Title: package linux-image-4.13.0-25-generic 4.13.0-25.29 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 143 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: update-initramfs fails to finish update process and hang apt indefinitely. In other order to continue process must be killed. Then apt and dpkg goes into unusable state. Only way to resolve is to hard shutdown system and reboot in different kernel. Issues follows the linux-image-extra package. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7 Uname: Linux 4.14.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1495 F pulseaudio drew 3119 F pulseaudio /dev/snd/controlC0: gdm1495 F pulseaudio drew 3119 F pulseaudio Date: Tue Jan 16 07:26:55 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 143 HibernationDevice: RESUME=UUID=fb9ec1e3-951d-44bd-9ca5-a0ede4624487 InstallationDate: Installed on 2016-11-01 (441 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Hewlett-Packard HP Z420 Workstation ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.0-13-generic.efi.signed root=UUID=836402c4-db45-4f3c-adf2-0a1cfe22af77 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: grub-pc 2.02-2ubuntu2 RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.13.0-25-generic 4.13.0-25.29 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 143 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.91 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.91:bd10/17/2016:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1743572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735088] Re: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
The issue was on the exact versions listed in the bug report and was resolved long ago. The bug should have been confirmed, documented, and closed. -- 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/1735088 Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) Status in initramfs-tools package in Ubuntu: Incomplete Bug description: running update-initramfs -u never completes. Any package install that that attempts to update initramfs sit and hangs. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Tue Nov 28 23:51:18 2017 ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2016-11-01 (393 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all 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: initramfs-tools Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1735088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2049238] [NEW] Video does not output to second monitor
Public bug reported: I have a 2-display setup (laptop screen with second monitor). When I am booted into Linux kernel 6.5.0-14-generic, my laptop screen works fine, however my second monitor doesn't get any video input at all. This problem does not occur on previous Linux kernel versions. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Fri Jan 12 17:32:15 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 6.2.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Lenovo Wani [Radeon R5/R6/R7 Graphics] [17aa:39ff] InstallationDate: Installed on 2023-10-03 (101 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) MachineType: LENOVO 80XS ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: 5QCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15ABR dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr5QCN24WW:bd07/29/2019:br1.24:efr1.24:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:skuLENOVO_MT_80XS_BU_idea_FM_ideapad320-15ABR: dmi.product.family: ideapad 320-15ABR dmi.product.name: 80XS dmi.product.sku: LENOVO_MT_80XS_BU_idea_FM_ideapad 320-15ABR dmi.product.version: Lenovo ideapad 320-15ABR dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kubuntu 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/2049238 Title: Video does not output to second monitor Status in xorg package in Ubuntu: New Bug description: I have a 2-display setup (laptop screen with second monitor). When I am booted into Linux kernel 6.5.0-14-generic, my laptop screen works fine, however my second monitor doesn't get any video input at all. This problem does not occur on previous Linux kernel versions. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Fri Jan 12 17:32:15 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 6.2.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Lenovo Wani [Radeon R5/R6/R7 Graphics] [17aa:39ff] InstallationDate: Installed on 2023-10-03 (101 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) MachineType: LENOVO 80XS ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: 5QCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi
[Touch-packages] [Bug 2039743] [NEW] Intermittent DHCP startup failure during boot due to potential race condition in interface renaming
Public bug reported: The server fails to start its network with DHCP seemingly randomly. It can take a few reboots to bring up the network. This causes issues where automated updates that trigger a reboot cause the server to go offline. I've attached syslog examples of both success and failure. My assumption is that the cause of this bug is a race condition where systemd is not waiting on the interface renaming. Notably, when it boots properly, it says: "Interface is under renaming, pending initialization." That message is not logged when it fails. The server uses cloud-init, and the cloud image provided by Ubuntu. Another possible explanation is the netplan configuration at /etc/netplan/50-cloud-init.yaml is: network: version: 2 ethernets: eth0: dhcp4: true match: macaddress: 92:00:00:00:43:6a set-name: eth0 Maybe set-name is redundant here, but it's the default configuration generated by cloud-init. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.21 ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 Uname: Linux 5.4.0-164-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Oct 18 16:22:57 2023 Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: Slicie.com Slicie Cloud Server ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-164-generic root=UUID=f849f569-82f8-4fc0-9ac6-d4f7f7ef9609 ro console=tty1 console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.1 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnSlicie.com:pnSlicieCloudServer:pvr1.0.0:cvnQEMU:ct1:cvrpc-i440fx-2.1: dmi.product.name: Slicie Cloud Server dmi.product.version: 1.0.0 dmi.sys.vendor: Slicie.com ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages uec-images ** Attachment added: "Relevant syslog lines for success and failure" https://bugs.launchpad.net/bugs/2039743/+attachment/5710951/+files/syslog.txt -- 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/2039743 Title: Intermittent DHCP startup failure during boot due to potential race condition in interface renaming Status in systemd package in Ubuntu: New Bug description: The server fails to start its network with DHCP seemingly randomly. It can take a few reboots to bring up the network. This causes issues where automated updates that trigger a reboot cause the server to go offline. I've attached syslog examples of both success and failure. My assumption is that the cause of this bug is a race condition where systemd is not waiting on the interface renaming. Notably, when it boots properly, it says: "Interface is under renaming, pending initialization." That message is not logged when it fails. The server uses cloud-init, and the cloud image provided by Ubuntu. Another possible explanation is the netplan configuration at /etc/netplan/50-cloud-init.yaml is: network: version: 2 ethernets: eth0: dhcp4: true match: macaddress: 92:00:00:00:43:6a set-name: eth0 Maybe set-name is redundant here, but it's the default configuration generated by cloud-init. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.21 ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 Uname: Linux 5.4.0-164-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Oct 18 16:22:57 2023 Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: Slicie.com Slicie Cloud Server ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-164-generic root=UUID=f849f569-82f8-4fc0-9ac6-d4f7f7ef9609 ro console=tty1 console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.1 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnSlicie.com:pnSlicieCloudServer:pvr1.
[Touch-packages] [Bug 2012980] [NEW] package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: This happened when I upgraded the kernel with "sudo apt upgrade". ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-69-generic 5.15.0-69.76 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: drew 1508 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Mar 27 16:28:39 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-12-22 (460 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 80XS ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/vgubuntu-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: 5QCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15ABR dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr5QCN24WW:bd07/29/2019:br1.24:efr1.24:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:skuLENOVO_MT_80XS_BU_idea_FM_ideapad320-15ABR: dmi.product.family: ideapad 320-15ABR dmi.product.name: 80XS dmi.product.sku: LENOVO_MT_80XS_BU_idea_FM_ideapad 320-15ABR dmi.product.version: Lenovo ideapad 320-15ABR dmi.sys.vendor: LENOVO ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2012980 Title: package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: This happened when I upgraded the kernel with "sudo apt upgrade". ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-69-generic 5.15.0-69.76 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: drew 1508 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Mar 27 16:28:39 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-12-22 (460 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 80XS ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/vgubuntu-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: 5QCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15ABR dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr5QCN24WW:bd07/29/2019:br1.24:efr1.24:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:skuLENOVO_MT_80XS_BU_idea_FM_id
[Touch-packages] [Bug 1942623] [NEW] [Wishlist] systemctl CLI UI should allow glob expansion throughout the service name
Public bug reported: When attempting to craft a command to query and/or restart all services with name 'something-*-else', such as 'neutron-*-agent' to match [neutron-l3-agent, neutron-openvswitch-agent, and neutron-dhcp-agent], I've found that no services are returned from globs in the middle of the string. The only supported glob seems to be a * at the end of the service name. Also, single character globbing with ? is not honored (as in the last example). To provide an example, I expect each of these commands to return the dbus.socket and dbus.service, but only 'systemctl status dbu*' shows the proper return. drew@grimoire:~$ systemctl status dbus ● dbus.service - D-Bus System Message Bus Loaded: loaded (/lib/systemd/system/dbus.service; static) Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) Main PID: 1357 (dbus-daemon) Tasks: 1 (limit: 57290) Memory: 4.9M CGroup: /system.slice/dbus.service └─1357 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only Warning: some journal files were not opened due to insufficient permissions. drew@grimoire:~$ systemctl status *bus drew@grimoire:~$ systemctl status '*bus' drew@grimoire:~$ systemctl status 'dbu*' ● dbus.service - D-Bus System Message Bus Loaded: loaded (/lib/systemd/system/dbus.service; static) Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) Main PID: 1357 (dbus-daemon) Tasks: 1 (limit: 57290) Memory: 5.0M CGroup: /system.slice/dbus.service └─1357 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only Warning: some journal files were not opened due to insufficient permissions. ● dbus.socket - D-Bus System Message Bus Socket Loaded: loaded (/lib/systemd/system/dbus.socket; static) Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago Triggers: ● dbus.service Listen: /run/dbus/system_bus_socket (Stream) drew@grimoire:~$ systemctl status 'db*s' drew@grimoire:~$ systemctl status 'dbu?' ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1942623 Title: [Wishlist] systemctl CLI UI should allow glob expansion throughout the service name Status in systemd package in Ubuntu: New Bug description: When attempting to craft a command to query and/or restart all services with name 'something-*-else', such as 'neutron-*-agent' to match [neutron-l3-agent, neutron-openvswitch-agent, and neutron-dhcp- agent], I've found that no services are returned from globs in the middle of the string. The only supported glob seems to be a * at the end of the service name. Also, single character globbing with ? is not honored (as in the last example). To provide an example, I expect each of these commands to return the dbus.socket and dbus.service, but only 'systemctl status dbu*' shows the proper return. drew@grimoire:~$ systemctl status dbus ● dbus.service - D-Bus System Message Bus Loaded: loaded (/lib/systemd/system/dbus.service; static) Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) Main PID: 1357 (dbus-daemon) Tasks: 1 (limit: 57290) Memory: 4.9M CGroup: /system.slice/dbus.service └─1357 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only Warning: some journal files were not opened due to insufficient permissions. drew@grimoire:~$ systemctl status *bus drew@grimoire:~$ systemctl status '*bus' drew@grimoire:~$ systemctl status 'dbu*' ● dbus.service - D-Bus System Message Bus Loaded: loaded (/lib/systemd/system/dbus.service; static) Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) Main PID: 1357 (dbus-daemon) Tasks: 1 (limit: 57290) Memory: 5.0M CGroup: /system.slice/dbus.service └─1357 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only Warning: some journal files were not opened due to insufficient permissions. ● dbus.socket - D-Bus System Message Bus Socket Loaded: loaded (/lib/systemd/system/dbus.socket; static) Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago Triggers: ● dbus.service Listen: /run/dbus/system_bus_socket
[Touch-packages] [Bug 1939941] [NEW] Drop down menu issues
Public bug reported: I found that about a month or so ago that I was having problems with dropdown menus in Thunderbird where they would not respond when I clicked on them. I managed to get around this by using the arrow keys but I would also have issues with the thunderbird icon in the icon tray not responding if I suspended the computer with Thunderbird still open. Now I find that the drop down application menu in Firefox also doesn't work and when I click on it the menu flashes up very quickly but then disappears. Also sometimes drop down menus that I have opened continue to persist in the display even after I have shut down the program, so I don't think it is a problem just in Mozilla products. I have reported the bug to Mozilla however just in case. Thanks. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 14 13:19:47 2021 DistUpgraded: 2021-05-17 16:32:46,967 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05bd] Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [1028:05bd] InstallationDate: Installed on 2021-03-06 (160 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. Latitude E6440 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i3o8fa@/vmlinuz-5.11.0-25-generic root=ZFS=rpool/ROOT/ubuntu_i3o8fa ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-05-17 (88 days ago) dmi.bios.date: 06/13/2019 dmi.bios.release: 65.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd06/13/2019:br65.24:svnDellInc.:pnLatitudeE6440:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6440 dmi.product.sku: 05BD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu wayland-session -- 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/1939941 Title: Drop down menu issues Status in xorg package in Ubuntu: New Bug description: I found that about a month or so ago that I was having problems with dropdown menus in Thunderbird where they would not respond when I clicked on them. I managed to get around this by using the arrow keys but I would also have issues with the thunderbird icon in the icon tray not responding if I suspended the computer with Thunderbird still open. Now I find that the drop down application menu in Firefox also doesn't work and when I click on it the menu flashes up very quickly but then disappears. Also sometimes drop down menus that I have opened continue to persist in the display even after I have shut down the program, so I don't think it is a problem just in Mozilla products. I have reported the bug to Mozilla however just in case. Thanks. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 14 13:19:47 2021 DistUpgraded: 2021-05-17 16:32:46,967 DEBUG Running PostInsta
[Touch-packages] [Bug 1928470] [NEW] Duplicate image of Icons on Desktop
Public bug reported: After I upgraded to Hirsute Hippo the first time I opened the desktop I noticed that the desktop icons looked blurry. I tried to move them and then I realised that there was an image underneath the icon which replicated the icon image. These images could not be moved or deleted even if the desktop background was changed. Also on restarting they appeared under with new location of the icons. I deleted all the icons I could on the desktop via files and was just left with the default trash and home icons but the same problem still happened although the other icons were now completely gone. Thanks for your help. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 14:19:56 2021 DistUpgraded: 2021-05-14 12:54:25,361 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: No such file or directory (1)) DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05bd] Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [1028:05bd] InstallationDate: Installed on 2021-03-06 (68 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. Latitude E6440 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_wzumu3@/vmlinuz-5.11.0-17-generic root=ZFS=rpool/ROOT/ubuntu_wzumu3 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-05-14 (0 days ago) dmi.bios.date: 06/13/2019 dmi.bios.release: 65.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd06/13/2019:br65.24:svnDellInc.:pnLatitudeE6440:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6440 dmi.product.sku: 05BD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105+git2105101700.cfbea7~oibaf~g version.libgl1-mesa-dri: libgl1-mesa-dri 21.2~git2105121014.7db79f~oibaf~g version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages ubuntu wayland-session -- 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/1928470 Title: Duplicate image of Icons on Desktop Status in xorg package in Ubuntu: New Bug description: After I upgraded to Hirsute Hippo the first time I opened the desktop I noticed that the desktop icons looked blurry. I tried to move them and then I realised that there was an image underneath the icon which replicated the icon image. These images could not be moved or deleted even if the desktop background was changed. Also on restarting they appeared under with new location of the icons. I deleted all the icons I could on the desktop via files and was just left with the default trash and home icons but the same problem still happened although the other icons were now completely gone. Thanks for your help. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 14:19:56 2021 DistUpgraded: 2021-05-14 12:54:25,361 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_p
[Touch-packages] [Bug 1922823] Re: Please remove poppler-qml-plugin from Ubuntu
** Changed in: poppler-qml-plugin (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler-qml-plugin in Ubuntu. https://bugs.launchpad.net/bugs/1922823 Title: Please remove poppler-qml-plugin from Ubuntu Status in poppler-qml-plugin package in Ubuntu: Opinion Bug description: Unmaintained Ubuntu-only package that is part of the obsolete Ubuntu Touch stack. FTBFS on rebuild and has no rdeps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler-qml-plugin/+bug/1922823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922822] Re: Please remove qtpowerd from Ubuntu
** Changed in: qtpowerd (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpowerd in Ubuntu. https://bugs.launchpad.net/bugs/1922822 Title: Please remove qtpowerd from Ubuntu Status in qtpowerd package in Ubuntu: Opinion Bug description: Unmaintained Ubuntu-only package that is part of the obsolete Ubuntu Touch stack. FTBFS on rebuild and has no rdeps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtpowerd/+bug/1922822/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 50093] Re: Some sysctls are ignored on boot
Still seeing this in bionic 18.04.3 with the following kernel and procps package. ii procps 2:3.3.12-3ubuntu1.2 amd64/proc file system utilities kernel 5.4.0-62-generic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctls are ignored on boot Status in procps package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: New Bug description: Binary package hint: procps /etc/init.d/procps.sh comes too early in the boot process to apply a lot of sysctl's. As it runs before networking modules are loaded and filesystems are mounted, there are quite a lot of commonly-used sysctl's which are simply ignored on boot and produce errors to the console. Simply renaming the symlink from S17 to > S40 probably isn't a great solution, as there are probably folk who want and expect some sysctl's to be applied before filesystems are mounted and so on. However, simply ugnoring something as important as sysctl settings isn't really on. Administrators expect the settings in /etc/sysctl.conf to take effect. One sto-gap solution would be to run sysctl -p twice; once at S17 and once at S41. There may still be some warnings and errors, but everything would be applied. A different, more complex approach might be to re-architect the sysctl configuration into something like; /etc/sysctl.d/$modulename and have the userland module-loading binaries take care of applying them after modules are loaded. Though this may take care of explicitly loaded modules only, I'm not sure. Incidentally, /etc/sysctl.conf still refers to /etc/networking/options, but hasn't that been deprecated? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855350] Re: Will not logout or shutdown from guest-session
I don't have much to add other than to say I am also experiencing this issue or one similar to it. I am running xfce on ubuntu 20.04 in a kvm virtual machine. The system was configured to boot to a command prompt with “systemctl set-default multi-user.target”, so when I want to run xfce this is done with "startxfce4". (problem description) if you log in to xfce then immediately log out it will fail with one of these errors: session manager must be in idle state when requesting a shutdown gdbus.error:org.freedesktop.dbus.error.invalidargs: type of message, "(yb)", does not match expected type "(b)" - example scenarios: reach the desktop, wait 45 seconds or more, try to log out, it works normally reach the desktop, try to log out immediately, get an error, try a second time, sometimes it will work reach the desktop, try to log out immediately, get an error, sit there doing nothing for a few seconds, sometimes it will log out - I tried playing around with the file 50-guest-wrapper.conf as others had mentioned, but I did not notice any difference. I also have an identically-configured centos 8 vm and it does not have this issue. (uninformed guess) When reaching the desktop something related to lightdm or xfce is failing in the background, once a timeout is reached, things work as expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1855350 Title: Will not logout or shutdown from guest-session Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: This is in Xubuntu 19.10, a regression from 18.04. xfce4-session 4.14.0-0ubuntu1. I enabled guest-session and logged in that. But there I can not log out or even shut down using the graphical way at least unless put Action Buttons on the panel and choose Switch User. If I run "xfce4-session-logout -l" I get error dialog saying: Received error while trying to log out GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs:Type of message, "(yb)", does not match expected type"(b)" And in standard output there is: "Received error while trying to log out, error was GDBus.Error:org.xfce.SessionManager.Error.Failed: Session manager must be in idle state when requesting a shutdown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1855350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1226855] Re: Cannot use open-iscsi inside LXC container
Adding Bootstack to watch this bug, as we are taking ownership of charm- iscsi-connector which would be ideal to test within lxd confinement, but requires VM or metal for functional tests. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1226855 Title: Cannot use open-iscsi inside LXC container Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: Trying to use open-iscsi from within an LXC container, but the iscsi netlink socket does not support multiple namespaces, causing: "iscsid: sendmsg: bug? ctrl_fd 6" error and failure. Command attempted: iscsiadm -m node -p $ip:$port -T $target --login Results in: Exit code: 18 Stdout: 'Logging in to [iface: default, target: $target, portal: $ip,$port] (multiple)' Stderr: 'iscsiadm: got read error (0/0), daemon died? iscsiadm: Could not login to [iface: default, target: $target, portal: $ip,$port]. iscsiadm: initiator reported error (18 - could not communicate to iscsid) iscsiadm: Could not log into all portals' ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 17 14:38:08 2013 InstallationDate: Installed on 2013-01-15 (245 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2013-05-16 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888571] [NEW] Screen flickering and glitching after install
Public bug reported: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 15:41:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] InstallationDate: Installed on 2020-07-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY Laptop 13-ba0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 875A dmi.board.vendor: HP dmi.board.version: 07.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ba0xxx dmi.product.sku: 8KD13AV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** 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/1888571 Title: Screen flickering and glitching after install Status in xorg package in Ubuntu: New Bug description: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 15:41:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] InstallationDate: Installed on 2020-07-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY Laptop 13-ba0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 875A dmi.board.vendor: HP dmi.board.version: 07.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ba0xxx dmi.product.sku: 8KD13AV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.
[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
I'm having similar issues to this bug and those described by Dmitrii in https://bugs.launchpad.net/charm-ceph-osd/+bug/1883585 specifically comment #2 and the last comment. It appears that if I run 'udevadm trigger --subsystem-match=block', I get my by-dname devices for bcaches, but if I run udevadm trigger w/out a subsystem match, something is triggering later than the block subsystem that is removing the links. Here are the runs with --verbose to show what appears to be getting probed on each run: https://pastebin.ubuntu.com/p/VPvSKRfGt4/ This is with 5.3.0-62 kernel on Bionic. I also have core and canonical-livepatch snaps installed as did the environment where Dmitrii has run into this. -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: New Status in linux source package in Bionic: New Status in linux-signed source package in Bionic: New Status in systemd source package in Bionic: New Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Triaged Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
Relevant package revisions for comment #50: bcache-tools 1.0.8-2build1 snapd2.45.1+18.04.2 systemd 237-3ubuntu10.41 udev 237-3ubuntu10.41 and snaps: Name VersionRev Tracking Publisher Notes canonical-livepatch 9.5.5 95latest/stable canonical✓ - core 16-2.45.2 9665 latest/stable canonical✓ core -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: New Status in linux source package in Bionic: New Status in linux-signed source package in Bionic: New Status in systemd source package in Bionic: New Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Triaged Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831221] Re: do-release-upgrade fails due to package libpam0g:amd64 1.1.8-3.2ubuntu2.1
Ah, that was the piece I was missing. Somehow after adding the debian- installer repo in order to play with d-i creation, either I accidentally installed cdebconf-udeb, or some other package took it on as a dependency and I didn't even notice it (for a few years I might add). I'm honestly surprised this hadn't caused issues before. It certainly wreaked havoc on my system during this attempted upgrade. I was eventually able to brute-force the removal of cdebconf and reconfigure debconf and fix my broken system. This is resolved, and was not an issue with libpam but rather my own misfortune and cdebconf being _almost good enough_ to fool me. -- 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/1831221 Title: do-release-upgrade fails due to package libpam0g:amd64 1.1.8-3.2ubuntu2.1 Status in pam package in Ubuntu: Incomplete Bug description: While performing a release upgrade from 14.04 to 16.04, the do- release-upgrade process crashes, apparently due to a failure installing or upgrading the package libpam0g:amd64 1.1.8-3.2ubuntu2.1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpam0g:amd64 1.1.8-3.2ubuntu2.1 ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39 Uname: Linux 3.13.0-165-generic x86_64 NonfreeKernelModules: rr232x ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Fri May 31 04:35:26 2019 DuplicateSignature: package:libpam0g:amd64:1.1.8-3.2ubuntu2.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: pam Title: package libpam0g:amd64 1.1.8-3.2ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-05-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1831221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831221] [NEW] do-release-upgrade fails due to package libpam0g:amd64 1.1.8-3.2ubuntu2.1
Public bug reported: While performing a release upgrade from 14.04 to 16.04, the do-release- upgrade process crashes, apparently due to a failure installing or upgrading the package libpam0g:amd64 1.1.8-3.2ubuntu2.1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpam0g:amd64 1.1.8-3.2ubuntu2.1 ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39 Uname: Linux 3.13.0-165-generic x86_64 NonfreeKernelModules: rr232x ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Fri May 31 04:35:26 2019 DuplicateSignature: package:libpam0g:amd64:1.1.8-3.2ubuntu2.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: pam Title: package libpam0g:amd64 1.1.8-3.2ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-05-31 (0 days ago) ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1831221 Title: do-release-upgrade fails due to package libpam0g:amd64 1.1.8-3.2ubuntu2.1 Status in pam package in Ubuntu: New Bug description: While performing a release upgrade from 14.04 to 16.04, the do- release-upgrade process crashes, apparently due to a failure installing or upgrading the package libpam0g:amd64 1.1.8-3.2ubuntu2.1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpam0g:amd64 1.1.8-3.2ubuntu2.1 ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39 Uname: Linux 3.13.0-165-generic x86_64 NonfreeKernelModules: rr232x ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Fri May 31 04:35:26 2019 DuplicateSignature: package:libpam0g:amd64:1.1.8-3.2ubuntu2.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: pam Title: package libpam0g:amd64 1.1.8-3.2ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-05-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1831221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668771] Re: systemd-resolved negative caching for extended period of time
This affects bionic openstack cloud environments when os-*-hostname is configured for keystone, and the keystone entry is deleted temporarily from upstream dns, or the upstream dns fails providing no record for the lookup of keystone.endpoint.domain.com. We have to then flush all caches across the cloud once DNS issue is resolved, rather than auto-healing at 60 seconds as if we were running nscd with negative-ttl set to 60 seconds. Ultimately, a negative TTL that is settable would be ideal, or the ability to not cache negative hits would also be useful. Only workaround now is to not use caches or to operationally flush caches as needed. -- 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/1668771 Title: systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: 231-9ubuntu3 If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd-resolved to have the negative caching purged. After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
February 4th, 2019: Lost a day to this bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Confirmed Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764848] Re: Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found
perhaps a proper fix is for ubuntu-sso-client to release a new python- ubuntu-sso-client package in bionic that doesn't include this UbuntuOne- Go_Daddy_Class_2_CA.pem now that ca-certificates package has the CA. However, I'd still like to see duplicate certs not causing ca- certificates.crt to be deleted. ** Also affects: ubuntu-sso-client Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1764848 Title: Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found Status in Ubuntu Single Sign On Client: New Status in ca-certificates package in Ubuntu: New Bug description: The certificate /usr/share/ca- certificates/mozilla/Go_Daddy_Class_2_CA.crt in package ca- certificates is conflicting with /etc/ssl/certs/UbuntuOne- Go_Daddy_Class_2_CA.pem from package python-ubuntu-sso-client. This results in the postinst trigger for ca-certificates to remove the /etc/ssl/certs/ca-certificates.crt file. This happens because the postinst trigger runs update-ca-certificates --fresh. If I run update-ca-certificates without the --fresh flag, the conflict is a non-issue and the ca-certificates.crt file is restored. If I understand some of the postinst code correctly, --fresh should only be run if called directly or if upgrading from a ca-certificates version older than 2011. Running bionic with daily -updates channel and ran into this this morning due to the release of ca-certificates version 20180409. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-sso-client/+bug/1764848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764848] [NEW] Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found
Public bug reported: The certificate /usr/share/ca- certificates/mozilla/Go_Daddy_Class_2_CA.crt in package ca-certificates is conflicting with /etc/ssl/certs/UbuntuOne-Go_Daddy_Class_2_CA.pem from package python-ubuntu-sso-client. This results in the postinst trigger for ca-certificates to remove the /etc/ssl/certs/ca-certificates.crt file. This happens because the postinst trigger runs update-ca-certificates --fresh. If I run update-ca-certificates without the --fresh flag, the conflict is a non-issue and the ca-certificates.crt file is restored. If I understand some of the postinst code correctly, --fresh should only be run if called directly or if upgrading from a ca-certificates version older than 2011. Running bionic with daily -updates channel and ran into this this morning due to the release of ca-certificates version 20180409. ** Affects: ubuntu-sso-client Importance: Undecided Status: New ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1764848 Title: Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found Status in Ubuntu Single Sign On Client: New Status in ca-certificates package in Ubuntu: New Bug description: The certificate /usr/share/ca- certificates/mozilla/Go_Daddy_Class_2_CA.crt in package ca- certificates is conflicting with /etc/ssl/certs/UbuntuOne- Go_Daddy_Class_2_CA.pem from package python-ubuntu-sso-client. This results in the postinst trigger for ca-certificates to remove the /etc/ssl/certs/ca-certificates.crt file. This happens because the postinst trigger runs update-ca-certificates --fresh. If I run update-ca-certificates without the --fresh flag, the conflict is a non-issue and the ca-certificates.crt file is restored. If I understand some of the postinst code correctly, --fresh should only be run if called directly or if upgrading from a ca-certificates version older than 2011. Running bionic with daily -updates channel and ran into this this morning due to the release of ca-certificates version 20180409. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-sso-client/+bug/1764848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1743572] [NEW] package linux-image-4.13.0-25-generic 4.13.0-25.29 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 143
Public bug reported: update-initramfs fails to finish update process and hang apt indefinitely. In other order to continue process must be killed. Then apt and dpkg goes into unusable state. Only way to resolve is to hard shutdown system and reboot in different kernel. Issues follows the linux-image-extra package. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7 Uname: Linux 4.14.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1495 F pulseaudio drew 3119 F pulseaudio /dev/snd/controlC0: gdm1495 F pulseaudio drew 3119 F pulseaudio Date: Tue Jan 16 07:26:55 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 143 HibernationDevice: RESUME=UUID=fb9ec1e3-951d-44bd-9ca5-a0ede4624487 InstallationDate: Installed on 2016-11-01 (441 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Hewlett-Packard HP Z420 Workstation ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.0-13-generic.efi.signed root=UUID=836402c4-db45-4f3c-adf2-0a1cfe22af77 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: grub-pc 2.02-2ubuntu2 RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.13.0-25-generic 4.13.0-25.29 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 143 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.91 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.91:bd10/17/2016:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.sys.vendor: Hewlett-Packard ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1743572 Title: package linux-image-4.13.0-25-generic 4.13.0-25.29 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 143 Status in initramfs-tools package in Ubuntu: New Bug description: update-initramfs fails to finish update process and hang apt indefinitely. In other order to continue process must be killed. Then apt and dpkg goes into unusable state. Only way to resolve is to hard shutdown system and reboot in different kernel. Issues follows the linux-image-extra package. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7 Uname: Linux 4.14.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1495 F pulseaudio drew 3119 F pulseaudio /dev/snd/controlC0: gdm1495 F pulseaudio drew 3119 F pulseaudio Date: Tue Jan 16 07:26:55 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 143 HibernationDevice: RESUME=UUID=fb9ec1e3-951d-44bd-9ca5-a0ede4624487 InstallationDate: Installed on 2016-11-01 (441 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Hewlett-Packard HP Z420 Workstation ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.0-13-generic.efi.signed root=UUID=836402c4-db45-4f3c-adf2-0a1cfe22af77 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
[Touch-packages] [Bug 1740997] [NEW] package systemd 235-3ubuntu2 failed to install/upgrade: triggers looping, abandoned
Public bug reported: systemd and dpkg crashed during dist-upgrade from artful to bionic ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu2 ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3 Uname: Linux 4.14.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 Date: Tue Jan 2 20:00:27 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-11-01 (428 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Z420 Workstation ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.0-11-generic root=UUID=836402c4-db45-4f3c-adf2-0a1cfe22af77 ro quiet splash crashkernel=384M-:128M vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. Title: package systemd 235-3ubuntu2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.91 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.91:bd10/17/2016:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.sys.vendor: Hewlett-Packard ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1740997 Title: package systemd 235-3ubuntu2 failed to install/upgrade: triggers looping, abandoned Status in systemd package in Ubuntu: New Bug description: systemd and dpkg crashed during dist-upgrade from artful to bionic ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu2 ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3 Uname: Linux 4.14.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 Date: Tue Jan 2 20:00:27 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-11-01 (428 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Z420 Workstation ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.0-11-generic root=UUID=836402c4-db45-4f3c-adf2-0a1cfe22af77 ro quiet splash crashkernel=384M-:128M vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. Title: package systemd 235-3ubuntu2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.91 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.91:bd10/17/2016:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1740997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1735088] Re: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
Had to boot to 4.10.0.42 or 4.14.0-11 to get command to run. Issue seen on both 4.13.0-17-generic and 4.13.0-19-generic. Another issue that accompanied this issue was that after updating to 17.10 PC would no longer reboot or shutdown. Updating kernel manually to 4.14.0-11 and manually booting to 4.14.0-11 linux-image resolved issue. I was then able to install software needed, update-initramfs, boot, and reboot normally. Currently running with 17.10 package set and newer kernel. -- 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/1735088 Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) Status in initramfs-tools package in Ubuntu: New Bug description: running update-initramfs -u never completes. Any package install that that attempts to update initramfs sit and hangs. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Tue Nov 28 23:51:18 2017 ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2016-11-01 (393 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all 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: initramfs-tools Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1735088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735088] [NEW] package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
Public bug reported: running update-initramfs -u never completes. Any package install that that attempts to update initramfs sit and hangs. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Tue Nov 28 23:51:18 2017 ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2016-11-01 (393 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all 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: initramfs-tools Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- 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/1735088 Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) Status in initramfs-tools package in Ubuntu: New Bug description: running update-initramfs -u never completes. Any package install that that attempts to update initramfs sit and hangs. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Tue Nov 28 23:51:18 2017 ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2016-11-01 (393 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all 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: initramfs-tools Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1735088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant
Can confirm this bug while using JavaFX in IntelliJ IDEA 2017.2.5 with Oracle JDK 9.0.1... /usr/share/themes/Radiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1723422 Title: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant Status in ubuntu-themes package in Ubuntu: In Progress Bug description: [Impact] Get that error now with each random package upgrade: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant Looks like related to that change: * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP: #961679) -- Marco Trevisan (Treviño) Thu, 12 Oct 2017 05:19:32 + That installation is a default Ubuntu , no Mate installed, and Ambiance is set for 'applications' into tweaks [Test case] 1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal 2. App has to run without any error [Possible regression] Different scrollbars in gtk2 apps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20171012.1-0ubuntu1 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 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 13 14:52:43 2017 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1723422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
>From a high level, it appears that invoke-rc.d script used for compatibility falls back to checking for /etc/rcX.d symlinks for a "policy" check if there is no $POLICYHELPER installed. Perhaps the actual shortcoming is not having the policy-rc.d installed to prefer systemd over init.d on Xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1727063 Title: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage Status in OpenStack hacluster charm: Invalid Status in init-system-helpers package in Ubuntu: Confirmed Status in pacemaker package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: Confirmed Status in pacemaker source package in Xenial: Fix Released Status in init-system-helpers source package in Zesty: Confirmed Status in pacemaker source package in Zesty: Fix Released Status in init-system-helpers source package in Artful: Confirmed Status in pacemaker source package in Artful: Fix Released Status in init-system-helpers source package in Bionic: Confirmed Status in pacemaker source package in Bionic: Fix Released Bug description: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] Minimal, earlier and later versions provide the defaults in the lsb header. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
re: init-system-helpers, I noticed the oddity of the init script on a systemd system as well and found that there's a systemd hack in /lib/lsb /init-functions.d/40-systemd that allows for multi-startup compatibility. I believe invoke-rc.d should check systemd "enabled/disabled" state instead of just the S/K links in /etc/rcX.d. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1727063 Title: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage Status in OpenStack hacluster charm: Invalid Status in init-system-helpers package in Ubuntu: New Status in pacemaker package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: New Status in pacemaker source package in Xenial: Fix Released Status in init-system-helpers source package in Zesty: New Status in pacemaker source package in Zesty: Fix Released Status in init-system-helpers source package in Artful: New Status in pacemaker source package in Artful: Fix Released Status in init-system-helpers source package in Bionic: New Status in pacemaker source package in Bionic: Fix Released Bug description: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] Minimal, earlier and later versions provide the defaults in the lsb header. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay
Trusty versions of packages affected (I see there is a systemd update 229-4ubuntu19. Does this include the backported fixes from v230/v231 mentioned in comment #4?): ii dbus 1.10.6-1ubuntu3.1 amd64simple interprocess messaging system (daemon and utilities) ii libdbus-1-3:amd641.10.6-1ubuntu3.1 amd64simple interprocess messaging system (library) ii libdbus-glib-1-2:amd64 0.106-1 amd64simple interprocess messaging system (GLib-based shared library) ii python3-dbus 1.2.0-3 amd64simple interprocess messaging system (Python 3 interface) ii libpam-systemd:amd64 229-4ubuntu12 amd64system and service manager - PAM module ii libsystemd0:amd64229-4ubuntu12 amd64systemd utility library ii python3-systemd 231-2build1 amd64Python 3 bindings for systemd ii systemd 229-4ubuntu12 amd64system and service manager ii systemd-sysv 229-4ubuntu12 amd64system and service manager - SysV links -- 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/1591411 Title: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay Status in D-Bus: Fix Released Status in systemd: Unknown Status in dbus package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Xenial: Fix Released Status in systemd source package in Xenial: Invalid Status in dbus source package in Yakkety: Won't Fix Status in systemd source package in Yakkety: Invalid Bug description: [Impact] The bug affects multiple users and introduces an user visible delay (~25 seconds) on SSH connections after a large number of sessions have been processed. This has a serious impact on big systems and servers running our software. The currently proposed fix is actually a safe workaround for the bug as proposed by the dbus upstream. The workaround makes uid 0 immune to the pending_fd_timeout limit that kicks in and causes the original issue. [Test Case] lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done Then checking the log file if there are any ssh sessions that are taking 25+ seconds to complete. Multiple instances of the same script can be used at the same time. [Regression Potential] The fix has a rather low regression potential as the workaround is a very small change only affecting one particular case - handling of uid 0. The fix has been tested by multiple users and has been around in zesty for a while, with multiple people involved in reviewing the change. It's also a change that has been proposed by upstream. [Original Description] I noticed on a system that accepts large numbers of SSH connections that after awhile, SSH sessions were taking ~25 seconds to complete. Looking in /var/log/auth.log, systemd-logind starts failing with the following: Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for user ubuntu by (uid=0) Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu. Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: Transport endpoint is not connected Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create session: Message recipient disconnected from message bus without replying I reproduced this in an LXD container by doing something like: lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done In my case, after 1052 logins, the 1053rd and thereafter were taking 25+ seconds to complete. Here are some snippets from the log file: $ cat log | grep 0m0 | wc -l 1052 $ cat log | grep 0m25 | wc -l 4 $ tail -5 log real 0m0.222s real 0m25.232s real 0m25.235s real 0m25.236s real 0m25.239s ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Jun 11 00:09:34 2016 MachineType: Notebook W230SS ProcEnviron: TERM=xterm-256color
[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay
** Tags added: canonical-bootstack canonical-is -- 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/1591411 Title: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay Status in D-Bus: Fix Released Status in systemd: Unknown Status in dbus package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Xenial: Fix Released Status in systemd source package in Xenial: Invalid Status in dbus source package in Yakkety: Won't Fix Status in systemd source package in Yakkety: Invalid Bug description: [Impact] The bug affects multiple users and introduces an user visible delay (~25 seconds) on SSH connections after a large number of sessions have been processed. This has a serious impact on big systems and servers running our software. The currently proposed fix is actually a safe workaround for the bug as proposed by the dbus upstream. The workaround makes uid 0 immune to the pending_fd_timeout limit that kicks in and causes the original issue. [Test Case] lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done Then checking the log file if there are any ssh sessions that are taking 25+ seconds to complete. Multiple instances of the same script can be used at the same time. [Regression Potential] The fix has a rather low regression potential as the workaround is a very small change only affecting one particular case - handling of uid 0. The fix has been tested by multiple users and has been around in zesty for a while, with multiple people involved in reviewing the change. It's also a change that has been proposed by upstream. [Original Description] I noticed on a system that accepts large numbers of SSH connections that after awhile, SSH sessions were taking ~25 seconds to complete. Looking in /var/log/auth.log, systemd-logind starts failing with the following: Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for user ubuntu by (uid=0) Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu. Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: Transport endpoint is not connected Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create session: Message recipient disconnected from message bus without replying I reproduced this in an LXD container by doing something like: lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done In my case, after 1052 logins, the 1053rd and thereafter were taking 25+ seconds to complete. Here are some snippets from the log file: $ cat log | grep 0m0 | wc -l 1052 $ cat log | grep 0m25 | wc -l 4 $ tail -5 log real 0m0.222s real 0m25.232s real 0m25.235s real 0m25.236s real 0m25.239s ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Jun 11 00:09:34 2016 MachineType: Notebook W230SS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1591411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscrib
[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay
Can we get this backported to trusty? -- 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/1591411 Title: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay Status in D-Bus: Fix Released Status in systemd: Unknown Status in dbus package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Xenial: Fix Released Status in systemd source package in Xenial: Invalid Status in dbus source package in Yakkety: Won't Fix Status in systemd source package in Yakkety: Invalid Bug description: [Impact] The bug affects multiple users and introduces an user visible delay (~25 seconds) on SSH connections after a large number of sessions have been processed. This has a serious impact on big systems and servers running our software. The currently proposed fix is actually a safe workaround for the bug as proposed by the dbus upstream. The workaround makes uid 0 immune to the pending_fd_timeout limit that kicks in and causes the original issue. [Test Case] lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done Then checking the log file if there are any ssh sessions that are taking 25+ seconds to complete. Multiple instances of the same script can be used at the same time. [Regression Potential] The fix has a rather low regression potential as the workaround is a very small change only affecting one particular case - handling of uid 0. The fix has been tested by multiple users and has been around in zesty for a while, with multiple people involved in reviewing the change. It's also a change that has been proposed by upstream. [Original Description] I noticed on a system that accepts large numbers of SSH connections that after awhile, SSH sessions were taking ~25 seconds to complete. Looking in /var/log/auth.log, systemd-logind starts failing with the following: Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for user ubuntu by (uid=0) Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu. Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: Transport endpoint is not connected Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create session: Message recipient disconnected from message bus without replying I reproduced this in an LXD container by doing something like: lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done In my case, after 1052 logins, the 1053rd and thereafter were taking 25+ seconds to complete. Here are some snippets from the log file: $ cat log | grep 0m0 | wc -l 1052 $ cat log | grep 0m25 | wc -l 4 $ tail -5 log real 0m0.222s real 0m25.232s real 0m25.235s real 0m25.236s real 0m25.239s ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Jun 11 00:09:34 2016 MachineType: Notebook W230SS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1591411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://l
[Touch-packages] [Bug 1615702] [NEW] I have intel integrated graphics 3rd Gen and I am having issues with the brightness not working, its very dim
Public bug reported: running linux mint 18 sarah ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Aug 22 11:30:26 2016 InstallationDate: Installed on 2016-08-18 (3 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug sarah -- 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/1615702 Title: I have intel integrated graphics 3rd Gen and I am having issues with the brightness not working, its very dim Status in xorg package in Ubuntu: New Bug description: running linux mint 18 sarah ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Aug 22 11:30:26 2016 InstallationDate: Installed on 2016-08-18 (3 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1615702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1581302] Re: Monitor remains blanked with Intel Graphics
For anyone running xfce4 with this bug driving them nuts, it may pertain to a known bug in xfsettingsd. Check out the patch noted here: https://bugzilla.xfce.org/show_bug.cgi?id=11107#c53 Download the xfce4-settings source, apply the patch, increment with a non-maintainer version number (for no future apt-get conflicts once this gets an official fix), and reinstall your patched xfce4-settings. The aforementioned screen blank patch fixed this bug that has been driving me nuts for weeks. I would lose my entire X session every single day as soon as the screen blanked... quite troublesome when you're trying to make linux work as your daily drive, haha. I had to learn how to patch a .deb file properly in the process, but that was worth it too. -- Hardware/Software -- GPU: GTX 970 over DisplayPort 1.2 Monitor: Dell P2715 (4K@60Hz, hardware rev A03) OS: Xubuntu Xenial (16.04 LTS) Manually patched xfce4-settings version: 4.12.0-2ubuntu1 Useful links on patching .deb's: https://help.ubuntu.com/community/UpdatingADeb http://www.cyberciti.biz/faq/appy-patch-file-using-patch-command/ ** Bug watch added: Xfce Bugzilla #11107 https://bugzilla.xfce.org/show_bug.cgi?id=11107 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1581302 Title: Monitor remains blanked with Intel Graphics Status in lightdm package in Ubuntu: Confirmed Status in xfce4-settings package in Ubuntu: Confirmed Bug description: Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port or HDMI Running Xubuntu 16.04 - latest all current patches Sometimes the monitor remains blanked even when the session has reactivated. I have been able to reproduce this problem by letting the monitor remain in the 'blanked' state for > 60 minutes, or powering off the monitor. When the monitor is powered back on and the session is woken up with mouse or keyboard input, it does wake up but the monitor remains blanked. I was able to prove to myself the session was awake by leaving it with terminal opened to full screen with VIM running on an NFS mounted file system. I could type and save at the black monitor screen and see that the file got updates from a different system. So the session is "live" but the computer has forgotten to re-establish the DisplayPort link. An error appears in the lightdm logs about setting a CRTC, if you activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr --output DP1 --auto` it also registers that CRTC error. HOWEVER, if you ssh in from a different machine, tell bash to export DISPLAY=:0 (set $DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the screen turns on again! This also happens on a Gigabyte BRIX system (same NUC reference design but in that case a core i3 rather than a Core i7). To reproduce, turn off the monitor, wait an hour, and turn it on again. You can also kill HUP the lightdm process and that will restart a new session (but open windows in the previous session are lost). So interesting questions, why does typing xrandr "locally" give you the error but running it from an ssh session work? Since xrandr and restarting the session can both "fix" the problem, the driver seems to know how to turn the display on if told correctly. How can I find out where the code is getting the CRTC error? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu May 12 20:33:01 2016 InstallationDate: Installed on 2016-05-08 (4 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch LightdmLog: [+80180.09s] DEBUG: Seat seat0 changes active session to [+80189.53s] DEBUG: Seat seat0 changes active session to 64 [+80222.67s] DEBUG: Seat seat0 changes active session to c4 [+80222.67s] DEBUG: Session c4 is already active SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1581302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp