[Touch-packages] [Bug 1804159] [NEW] package udev 237-3ubuntu10.9 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1
Public bug reported: machine was connected to VPN. apt dist-upgrade failed with udev error in the bug report errors seen: Setting up udev (237-3ubuntu10.9) ... Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Failed to retrieve unit state: Connection timed out Failed to restart udev.service: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) See system logs and 'systemctl status udev.service' for details. invoke-rc.d: initscript udev, action "restart" failed. Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) dpkg: error processing package udev (--configure): installed udev package post-installation script subprocess returned error exit status 1 ... Processing triggers for dbus (1.12.2-1ubuntu1) ... Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ... Errors were encountered while processing: udev E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.9 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CustomUdevRuleFiles: 50-hid.rules 60-vboxdrv.rules Date: Tue Nov 20 08:20:46 2018 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-10-06 (44 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Precision 7820 Tower ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: systemd Title: package udev 237-3ubuntu10.9 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-10-23 (28 days ago) dmi.bios.date: 09/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05WNJ2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd09/04/2018:svnDellInc.:pnPrecision7820Tower:pvr:rvnDellInc.:rn05WNJ2:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision 7820 Tower dmi.sys.vendor: Dell Inc. ** 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/1804159 Title: package udev 237-3ubuntu10.9 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: machine was connected to VPN. apt dist-upgrade failed with udev error in the bug report errors seen: Setting up udev (237-3ubuntu10.9) ... Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Failed to retrieve unit state: Connection timed out Failed to restart udev.service: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) See system logs and 'systemctl status udev.service' for details. invoke-rc.d: initscript udev, action "restart" failed. Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) dpkg: error processing package udev (--configure): installed udev package post-installation script subprocess returned error exit status 1 ... Processing triggers for dbus (1.12.2-1ubuntu1) ... Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ... Errors were encountered while processing: udev E: Sub-process /usr/bin/dpkg returned an error code (1)
[Touch-packages] [Bug 1804157] [NEW] Python3 and python3-minimal when apt upgrade
Public bug reported: I tried to do daily upgrade of packages but then i encountered this missmatch with python packages versions. Found an workaround but it should be solved natively. sudo apt install python3 Reading package lists... Done Building dependency tree Reading state information... Done python3 is already the newest version (3.6.5-3ubuntu1). You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: python3 : PreDepends: python3-minimal (= 3.6.5-3ubuntu1) but 3.6.7-1~18.04 is to be installed apt policy python3 python3: Installed: 3.6.5-3ubuntu1 Candidate: 3.6.5-3ubuntu1 Version table: *** 3.6.5-3ubuntu1 100 100 /var/lib/dpkg/status 3.6.5-3 500 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages apt policy python3-minimal python3-minimal:
[Touch-packages] [Bug 1804130] [NEW] package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: This happened on a near-fresh install of 18.04 on a new computer. I was having trouble getting the NVIDIA proprietary drivers working. So I did quite a bit of install/uninstall cycles, failing to get the NVIDIA drivers working. I couldn't seem to get the NVIDIA drivers to work. I just recently discovered the reason -- I had the UEFI secure boot setup. So I disabled UEFI using the mokutil --disable-validation command. This crash occured on a system reboot. I imagine I can fix my setup from here. I'll update the thread, regardless of the outcome. I think perhaps Ubuntu would benefit from a warning, during the installation process that UEFI secure boot can cause problems such as this. Also, when installing NVIDIA drivers with the "Software and Updates" GUI, there should be some indication of the problems if the UEFI secure boot is enabled. Perhaps users should be blocked from attempting the install, and pointed towards mokutil. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.5 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Nov 19 20:24:14 2018 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-11-16 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** 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/1804130 Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: This happened on a near-fresh install of 18.04 on a new computer. I was having trouble getting the NVIDIA proprietary drivers working. So I did quite a bit of install/uninstall cycles, failing to get the NVIDIA drivers working. I couldn't seem to get the NVIDIA drivers to work. I just recently discovered the reason -- I had the UEFI secure boot setup. So I disabled UEFI using the mokutil --disable-validation command. This crash occured on a system reboot. I imagine I can fix my setup from here. I'll update the thread, regardless of the outcome. I think perhaps Ubuntu would benefit from a warning, during the installation process that UEFI secure boot can cause problems such as this. Also, when installing NVIDIA drivers with the "Software and Updates" GUI, there should be some indication of the problems if the UEFI secure boot is enabled. Perhaps users should be blocked from attempting the install, and pointed towards mokutil. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.5 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Nov 19 20:24:14 2018 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-11-16 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1804130/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1804036] Re: package apt 1.6.1 failed to install/upgrade: unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: apt (Ubuntu) Importance: Undecided => Low ** Changed in: apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1804036 Title: package apt 1.6.1 failed to install/upgrade: unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error Status in apt package in Ubuntu: Invalid Bug description: All info has been provided in the report ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apt 1.6.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Mon Nov 19 09:27:23 2018 DpkgTerminalLog: Preparing to unpack .../archives/apt_1.6.6_amd64.deb ... Unpacking apt (1.6.6) over (1.6.1) ... dpkg: error processing archive /var/cache/apt/archives/apt_1.6.6_amd64.deb (--unpack): unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error DuplicateSignature: package:apt:1.6.1 Unpacking apt (1.6.6) over (1.6.1) ... dpkg: error processing archive /var/cache/apt/archives/apt_1.6.6_amd64.deb (--unpack): unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error ErrorMessage: unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error InstallationDate: Installed on 2018-11-11 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.1 SourcePackage: apt Title: package apt 1.6.1 failed to install/upgrade: unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1804036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804076] Re: Xorg freeze
You may need to contact Sophos for support. Thanks -- 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/1804076 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: i recently installed OVPN(2) from gnome extentions because the OVPN(1) was not working correctly, after that when ever i use my system's Wifi i'm getting system freeze for few minutes and again it works fine,having this issue on ubuntu but Ubuntu on wayland is working perfect. I also used Bleachbit for cleaning junk files and backup from my system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 20 03:53:18 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3670] [1002:9593] (prog-if 00 [VGA controller]) Subsystem: Dell RV635/M86 [Mobility Radeon HD 3670] [1028:0272] InstallationDate: Installed on 2018-10-23 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Studio XPS 1640 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=493c5373-ab6c-4136-a868-f324e0358b9c ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0U785D dmi.board.vendor: Dell Inc. dmi.board.version: A15 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A15 dmi.modalias: dmi:bvnDellInc.:bvrA15:bd04/09/2011:svnDellInc.:pnStudioXPS1640:pvrA153:rvnDellInc.:rn0U785D:rvrA15:cvnDellInc.:ct8:cvrA15: dmi.product.name: Studio XPS 1640 dmi.product.version: A153 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1804076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803849] Re: libgl1-mesa-dri:i386 can not be installed
WTF??? Does this mean you want to get rid of the problem without solving it? There is definitely a dependency problem either in libgl1-mesa-dri:i386 or in libllvm7:i386. == $ apt policy Package files: 100 /var/lib/dpkg/status release a=now 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main i386 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=main,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=main,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/multiverse i386 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=multiverse,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/multiverse amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=multiverse,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/universe i386 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=universe,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/universe amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=universe,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/multiverse i386 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=multiverse,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/multiverse amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=multiverse,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/universe i386 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=universe,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/universe amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=universe,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/main i386 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=main,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/main amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=main,b=amd64 origin archive.ubuntu.com 500 http://archive.canonical.com/ubuntu cosmic/partner i386 Packages release v=18.10,o=Canonical,a=cosmic,n=cosmic,l=Partner archive,c=partner,b=i386 origin archive.canonical.com 500 http://archive.canonical.com/ubuntu cosmic/partner amd64 Packages release v=18.10,o=Canonical,a=cosmic,n=cosmic,l=Partner archive,c=partner,b=amd64 origin archive.canonical.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/multiverse i386 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=multiverse,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/multiverse amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=multiverse,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/universe i386 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=universe,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/universe amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=universe,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main i386 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=main,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=main,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic/multiverse i386 Packages release v=18.10,o=Ubuntu,a=cosmic,n=cosmic,l=Ubuntu,c=multiverse,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic/multiverse amd64 Packages release v=18.10,o=Ubuntu,a=cosmic,n=cosmic,l=Ubuntu,c=multiverse,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic/universe i386 Packages release v=18.10,o=Ubuntu,a=cosmic,n=cosmic,l=Ubuntu,c=universe,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages release v=18.10,o=Ubuntu,a=cosmic,n=cosmic,l=Ubuntu,c=universe,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic/restricted i386 Packages release
[Touch-packages] [Bug 1804076] Re: Xorg freeze
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1804076 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: i recently installed OVPN(2) from gnome extentions because the OVPN(1) was not working correctly, after that when ever i use my system's Wifi i'm getting system freeze for few minutes and again it works fine,having this issue on ubuntu but Ubuntu on wayland is working perfect. I also used Bleachbit for cleaning junk files and backup from my system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 20 03:53:18 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3670] [1002:9593] (prog-if 00 [VGA controller]) Subsystem: Dell RV635/M86 [Mobility Radeon HD 3670] [1028:0272] InstallationDate: Installed on 2018-10-23 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Studio XPS 1640 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=493c5373-ab6c-4136-a868-f324e0358b9c ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0U785D dmi.board.vendor: Dell Inc. dmi.board.version: A15 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A15 dmi.modalias: dmi:bvnDellInc.:bvrA15:bd04/09/2011:svnDellInc.:pnStudioXPS1640:pvrA153:rvnDellInc.:rn0U785D:rvrA15:cvnDellInc.:ct8:cvrA15: dmi.product.name: Studio XPS 1640 dmi.product.version: A153 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1804076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803915] Re: nose
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1803915 Title: nose Status in xorg package in Ubuntu: New Bug description: erro de video ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompositorRunning: None Date: Sun Nov 18 23:01:57 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Core Processor Integrated Graphics Controller [1462:1039] InstallationDate: Installed on 2018-11-08 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-1454 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=c1a50982-6add-41a3-aacc-6bbf1417cd04 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1454IIA.11C dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1454 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MS-1454 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1454IIA.11C:bd02/10/2011:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-1454:pvrREV1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-1454:rvrREV1.0:cvnMS-1454:ct10:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-1454 dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1803915/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803840] Re: color calibration with huey pro greenish
Thanks! Your feedback sounds like the missing piece to this puzzle. Until now the greenish problem had only been reported by people who didn't have a colorimeter so we just blamed the default profiles. However your comments now make me think it might have been a miscalculation in colord (or such) that is exaggerating the green channel most visibly. The previous existing bug 1785764 mentions the greenish issue but isn't really about it. Let's make this bug 1803840 about the green problem. ** Package changed: xorg-server (Ubuntu) => colord (Ubuntu) ** Changed in: colord (Ubuntu) Status: Incomplete => Confirmed ** Changed in: colord (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1803840 Title: color calibration with huey pro greenish Status in colord package in Ubuntu: Confirmed Bug description: First of all: Congratulations, after an absence due to bad configurability of my rig I came back to ubuntu and was very positively surprisedthere is one thing that bothers me: after using the calibration feature for my screens this leads to greenish displays, even a icc profile made with the same hardware under windows10 (where configurability decreased since my update to v10) makes the same effect used with ubuntu 16.04...am I not aware of some more setting or is this a bug? Please let me know what more information you need from me besides I am using a hp envy dv6 and a wacom cintiq 13 hd, the nvidia graphics card is turned off for displays, I am using it just for Blenders Cycles renderer. I am a left-handed CG enthusiast who needs the wacom buttons on the right-hand side... Thank you, Michael ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 17 23:43:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-38-generic, x86_64: installed nvidia, 390.77, 4.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:181b] NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GF108M [GeForce GT 635M] [103c:181b] InstallationDate: Installed on 2018-11-11 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ENVY dv6 Notebook PC ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=befbe944-5e8a-4bfc-b541-c8ad84809dde ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181B dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd11/02/2012:svnHewlett-Packard:pnHPENVYdv6NotebookPC:pvr088A1230591620100:rvnHewlett-Packard:rn181B:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY dv6 Notebook PC dmi.product.version: 088A1230591620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1803840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1785764] Re: Chrome/Chromium and Image Viewer distort colours if a colour profile is enabled.
The greenish problem is now being tracked separately, in bug 1803840. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1785764 Title: Chrome/Chromium and Image Viewer distort colours if a colour profile is enabled. Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Using Ubuntu 18.04.1 LTS Running on an i7-6700k with a GTX 1080 Reproducible with nvidia-driver-396 or xserver-xorg-video-nouveau and a single 4K screen (TV) connected via HDMI. The issue: Any dark content displayed by an effected application (e.g. a very dark image or dark themed web page) is much darker than intended making it almost unusable. This only effects applications that are launched when the 4K screen is connected. If i disconnect the 4K screen, launch the app via a different 1080p monitor then reconnect the 4K screen the app remains unaffected. The only apps i have found so far that are effected by this are Google Chrome and Image Viewer. That said this is only noticeable when the app is displaying dark contend so if other apps are affected it may be impossible to tell. The attached screenshot uses a black to white gradient image to clearly demonstrate the issue. Is seems like it may be an issue with colour depth as bellow a certain brightness it just goes strait to black. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1785764/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803840] [NEW] color calibration with huey pro greenish
You have been subscribed to a public bug: First of all: Congratulations, after an absence due to bad configurability of my rig I came back to ubuntu and was very positively surprisedthere is one thing that bothers me: after using the calibration feature for my screens this leads to greenish displays, even a icc profile made with the same hardware under windows10 (where configurability decreased since my update to v10) makes the same effect used with ubuntu 16.04...am I not aware of some more setting or is this a bug? Please let me know what more information you need from me besides I am using a hp envy dv6 and a wacom cintiq 13 hd, the nvidia graphics card is turned off for displays, I am using it just for Blenders Cycles renderer. I am a left-handed CG enthusiast who needs the wacom buttons on the right-hand side... Thank you, Michael ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 17 23:43:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-38-generic, x86_64: installed nvidia, 390.77, 4.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:181b] NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GF108M [GeForce GT 635M] [103c:181b] InstallationDate: Installed on 2018-11-11 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ENVY dv6 Notebook PC ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=befbe944-5e8a-4bfc-b541-c8ad84809dde ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181B dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd11/02/2012:svnHewlett-Packard:pnHPENVYdv6NotebookPC:pvr088A1230591620100:rvnHewlett-Packard:rn181B:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY dv6 Notebook PC dmi.product.version: 088A1230591620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: colord (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic ubuntu -- color calibration with huey pro greenish https://bugs.launchpad.net/bugs/1803840 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785775] Re: New 2.42 version
https://launchpad.net/ubuntu/+source/librsvg/2.44.8-3 ** Changed in: librsvg (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1785775 Title: New 2.42 version Status in librsvg package in Ubuntu: Fix Released Bug description: There is a new upstream version available but it depends on a new toolchain which we don't want yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1785775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803992] Re: Lock screen, notifications panel crashes
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu-mate-meta (Ubuntu) ** Changed in: ubuntu-mate-meta (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1803992 Title: Lock screen, notifications panel crashes Status in ubuntu-mate-meta package in Ubuntu: Incomplete Bug description: Multiple issues: 1) Lock screen crashes revealing the desktop after sleep/wake 2) Notification panel crashes constantly (with ubuntu-mate) 3) Ability to send report fails for whatever reason Pics attached here: https://imgur.com/a/dtUaXQF Happy to work with anyone to get this resolved. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: MATE Date: Mon Nov 19 08:40:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.15.0-38-generic, x86_64: installed nvidia, 390.87, 4.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 6GB] [3842:6161] LightdmLog: [+119931.86s] DEBUG: Seat seat0 changes active session to [+119934.82s] DEBUG: Seat seat0 changes active session to c2 [+119934.82s] DEBUG: Session c2 is already active MachineType: Gigabyte Technology Co., Ltd. Z170X-Designare ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=/dev/mapper/hostname--vg-root ro initrd=initrd.gz text SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23g dmi.board.asset.tag: Default string dmi.board.name: Z170X-Designare-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23g:bd03/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Designare:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Designare-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170X-Designare dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1803992/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1803149] Re: Update to 2.2.9
But the autopkgtest fails in the new version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1803149 Title: Update to 2.2.9 Status in cups package in Ubuntu: Fix Released Bug description: There is a new 2.2.9 version available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1803149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803149] Re: Update to 2.2.9
https://launchpad.net/ubuntu/+source/cups/2.2.9-1 ** Changed in: cups (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1803149 Title: Update to 2.2.9 Status in cups package in Ubuntu: Fix Released Bug description: There is a new 2.2.9 version available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1803149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804079] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1804079 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: I recently reported but now im having this issue on wayland as well ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 20 04:41:56 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3670] [1002:9593] (prog-if 00 [VGA controller]) Subsystem: Dell RV635/M86 [Mobility Radeon HD 3670] [1028:0272] InstallationDate: Installed on 2018-10-23 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Studio XPS 1640 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=493c5373-ab6c-4136-a868-f324e0358b9c ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0U785D dmi.board.vendor: Dell Inc. dmi.board.version: A15 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A15 dmi.modalias: dmi:bvnDellInc.:bvrA15:bd04/09/2011:svnDellInc.:pnStudioXPS1640:pvrA153:rvnDellInc.:rn0U785D:rvrA15:cvnDellInc.:ct8:cvrA15: dmi.product.name: Studio XPS 1640 dmi.product.version: A153 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1804079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804083] [NEW] Could not install '/tmp/apt-dpkg-install-lC31RI/0-systemd-sysv_237-3ubuntu10.9_i386.deb'
Public bug reported: Could not install '/tmp/apt-dpkg-install-lC31RI/0-systemd- sysv_237-3ubuntu10.9_i386.deb' ** Affects: systemd-shim (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-shim in Ubuntu. https://bugs.launchpad.net/bugs/1804083 Title: Could not install '/tmp/apt-dpkg-install-lC31RI/0-systemd- sysv_237-3ubuntu10.9_i386.deb' Status in systemd-shim package in Ubuntu: New Bug description: Could not install '/tmp/apt-dpkg-install-lC31RI/0-systemd- sysv_237-3ubuntu10.9_i386.deb' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1804083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798073] Re: [SRU] Provide 2018 archive signing key on stable releases
Setting up ubuntu-keyring (2018.09.18.1~18.04.0) ... # apt-key list ... /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg -- pub rsa4096 2018-09-17 [SC] F6EC B376 2474 EDA9 D21B 7022 8719 20D1 991B C93C uid [ unknown] Ubuntu Archive Automatic Signing Key (2018) all is good for bionic. Prior releases should only probably ship this key in the ubuntu-keyring.gpg, but not as a trusted.gpg.d key snippet. As we do not anticipate to use 2018 key to sign the bionic archive. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1798073 Title: [SRU] Provide 2018 archive signing key on stable releases Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: Fix Committed Bug description: [Impact] * For LTS releases to be able to bootstrap dual and single signed future releases, and validate all signatures, 2018 archive signing key should be SRUed back * Also build process has improved documentation and vague validation that all key snippets are signed correctly [Test Case] * $ apt-key list ... /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg -- pub rsa4096 2018-09-17 [SC] F6EC B376 2474 EDA9 D21B 7022 8719 20D1 991B C93C uid [ unknown] Ubuntu Archive Automatic Signing Key (2018) ... apt-key list should contain the 2018 archive key. [Regression Potential] * Build-process, key algo, and key size, and file format are the same as previous key snippets thus supported by all of gpg1 gpg2 gpgv1 gpgv2. [Other Info] * 2018 key is to be used for dual-signing in DD series and up * Bileto PPA is built against security pocket only, suitable to be released into both -security and -updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1798073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804079] [NEW] Xorg freeze
Public bug reported: I recently reported but now im having this issue on wayland as well ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 20 04:41:56 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3670] [1002:9593] (prog-if 00 [VGA controller]) Subsystem: Dell RV635/M86 [Mobility Radeon HD 3670] [1028:0272] InstallationDate: Installed on 2018-10-23 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Studio XPS 1640 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=493c5373-ab6c-4136-a868-f324e0358b9c ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0U785D dmi.board.vendor: Dell Inc. dmi.board.version: A15 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A15 dmi.modalias: dmi:bvnDellInc.:bvrA15:bd04/09/2011:svnDellInc.:pnStudioXPS1640:pvrA153:rvnDellInc.:rn0U785D:rvrA15:cvnDellInc.:ct8:cvrA15: dmi.product.name: Studio XPS 1640 dmi.product.version: A153 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze 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/1804079 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I recently reported but now im having this issue on wayland as well ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 20 04:41:56 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3670] [1002:9593] (prog-if 00 [VGA controller]) Subsystem: Dell RV635/M86 [Mobility Radeon HD 3670] [1028:0272] InstallationDate: Installed on 2018-10-23 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Studio XPS 1640 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=493c5373-ab6c-4136-a868-f324e0358b9c ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0U785D dmi.board.vendor: Dell Inc. dmi.board.version: A15 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A15 dmi.modalias: dmi:bvnDellInc.:bvrA15:bd04/09/2011:svnDellInc.:pnStudioXPS1640:pvrA153:rvnDellInc.:rn0U785D:rvrA15:cvnDellInc.:ct8:cvrA15: dmi.product.name: Studio XPS 1640 dmi.product.version: A153 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri
[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
Should better be this patch. ** Patch added: "0001-debian-udev.postinst-Don-t-always-trigger-systemctl-.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1803391/+attachment/5214307/+files/0001-debian-udev.postinst-Don-t-always-trigger-systemctl-.patch -- 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/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Committed Bug description: [Impact] * Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. [Regression Potential] * The daemons, shipped in deb:systemd, are not attempted to be restarted because despite package installation the system is in the middle of shutting down. This means that currently running daemons may be helding up open files on the filesystem, however all process are being stopped and killed as part of shutdown. Hence the worst possible regression from this, is an unclean shutdown, but even that shouldn't happen with this update. [Test Case] Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] root@uu-systemd-onshutdown:~# reboot Session terminated, terminating shell...Terminated root@uu-systemd- rbalint@yogi:~$ rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# tail /var/log/unattended-upgrades/unattended-upgrades-dpkg.log Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ... Setting up libsystemd0:amd64 (237-3ubuntu10.6) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Setting up systemd (237-3ubuntu10.6)
[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
The upgrade on Xenial fails in udev.postint, the attached patch should fix that. (Under test) -- 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/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Committed Bug description: [Impact] * Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. [Regression Potential] * The daemons, shipped in deb:systemd, are not attempted to be restarted because despite package installation the system is in the middle of shutting down. This means that currently running daemons may be helding up open files on the filesystem, however all process are being stopped and killed as part of shutdown. Hence the worst possible regression from this, is an unclean shutdown, but even that shouldn't happen with this update. [Test Case] Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] root@uu-systemd-onshutdown:~# reboot Session terminated, terminating shell...Terminated root@uu-systemd- rbalint@yogi:~$ rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# tail /var/log/unattended-upgrades/unattended-upgrades-dpkg.log Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ... Setting up libsystemd0:amd64 (237-3ubuntu10.6) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Setting up systemd (237-3ubuntu10.6) ... Failed to try-restart systemd-networkd.service: Transaction is destructive. See system logs and 'systemctl status systemd-networkd.service' for details. Failed to
[Touch-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually
The problem didn't go away after doing a fresh installation of Ubuntu 18.10. I have to first disconnect and then connect my Sony MDR-1000x to get the A2DP profile to work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1724919 Title: Bluetooth headphones only use A2DP when connected manually Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Issue with Sony MDR-1ABT Bluetooth headphones: Once paired, the headphones will be connected automatically whenever they are switched on. However when connected this way, only the HSP/HFP profile will work and trying to change to A2DP in sound settings does nothing. If the headphones are then manually disconnected and reconnected from Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in sound settings will successfully make them use A2DP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neil 1443 F pulseaudio /dev/snd/pcmC0D0c: neil 1443 F...m pulseaudio /dev/snd/controlC0: neil 1443 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 19:12:59 2017 InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: MDR-1ABT Symptom_Type: None of the above Title: [MDR-1ABT, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z270N-WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z270N-WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803749] Re: apt.Cache.clear() may set apt.Package.is_auto_removable to False
I'm fixing the issue here in u-u: https://github.com/mvo5/unattended-upgrades/pull/156 However I believe ActionGroup may need at least better documentation to clearly state when ActionGroups should be reset. ** Changed in: unattended-upgrades (Ubuntu) Status: New => In Progress ** Changed in: unattended-upgrades (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: unattended-upgrades (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1803749 Title: apt.Cache.clear() may set apt.Package.is_auto_removable to False Status in unattended-upgrades package in Ubuntu: In Progress Bug description: While triaging LP: #1803587 I found that originally autoremovable packages were handled as newly autoremovable ones by unattended- upgrades due to not finding all of them at the beginning of u-u's run. The root cause seems to be cache.clear() resetting pkg.is_auto_removable to False under some circumstances I haven't fully narrowed down. The reproduction is as follows: Set up a Bionic (or later) system with autoremovable packages, packages upgradable from -security and blacklist at least one upgradable package and apply the following patch to u-u: root@bb-1803587:~# diff -Naur /usr/bin/unattended-upgrade.orig /usr/bin/unattended-upgrade --- /usr/bin/unattended-upgrade.orig 2018-11-16 16:17:58.522583254 + +++ /usr/bin/unattended-upgrade 2018-11-16 16:36:12.226675870 + @@ -948,7 +948,9 @@ def rewind_cache(cache, pkgs_to_upgrade): # type: (apt.Cache, List[apt.Package]) -> None """ set the cache back to the state with packages_to_upgrade """ +print([pkg.name for pkg in cache if pkg.is_auto_removable]) cache.clear() +print([pkg.name for pkg in cache if pkg.is_auto_removable]) for pkg2 in pkgs_to_upgrade: pkg2.mark_install(from_user=not pkg2.is_auto_installed) if cache.broken_count > 0: Run u-u to observe cache.clear() resetting the list of autoremovable packages: ~# /usr/bin/unattended-upgrade --dry-run --verbose --debug Initial blacklisted packages: systemd Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic Using (^linux-image|^linux-headers|^linux-image-extra|^linux-modules|^linux-modules-extra|^linux-signed-image|^kfreebsd-image|^kfreebsd-headers|^gnumach-image|^.*-modules|^.*-kernel|^linux-backports-modules-.*|^linux-modules-.*|^linux-tools|^linux-cloud-tools) regexp to find kernel packages Using (^linux-image.*4.15.0-38-generic|^linux-headers.*4.15.0-38-generic|^linux-image-extra.*4.15.0-38-generic|^linux-modules.*4.15.0-38-generic|^linux-modules-extra.*4.15.0-38-generic|^linux-signed-image.*4.15.0-38-generic|^kfreebsd-image.*4.15.0-38-generic|^kfreebsd-headers.*4.15.0-38-generic|^gnumach-image.*4.15.0-38-generic|4.15.0-38-generic.*-modules|4.15.0-38-generic.*-kernel|^linux-backports-modules-.*.*4.15.0-38-generic|^linux-modules-.*.*4.15.0-38-generic|^linux-tools.*4.15.0-38-generic|^linux-cloud-tools.*4.15.0-38-generic) regexp to find running kernel packages Checking: apport ([]) adjusting candidate version: apport=2.20.9-0ubuntu7.1 ... Checking: libnss-systemd ([, ]) skipping blacklisted package systemd pkg systemd package has been blacklisted sanity check failed ['libfreetype6'] [] ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1803749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
The fix was backported to the upstream 1.10 series. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Confirmed Bug description: In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803849] Re: libgl1-mesa-dri:i386 can not be installed
seems like you've enabled an external ppa, and that's causing the issue ** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1803849 Title: libgl1-mesa-dri:i386 can not be installed Status in mesa package in Ubuntu: Invalid Bug description: Steam client tries to install a set of i386 libraries. One of them is libgl1-mesa-dri:i386. But since upgrade to Ubuntu 18.10 this package got broken dependency and thus installation fails. >The following packages have unmet dependencies: > libgl1-mesa-dri:i386 : Depends: libllvm7:i386 (>= 1:7~svn298832-1~) but it is not going to be installed ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgl1-mesa-dri:i386 (not installed) Uname: Linux 4.19.2-041902-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 18 09:54:04 2018 DistUpgraded: 2018-10-19 13:34:56,068 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: exfat, 1.2.10, 4.18.0-11-generic, x86_64: installed exfat, 1.2.10, 4.18.0-12-generic, x86_64: installed exfat, 1.2.10, 4.19.1-041901-generic, x86_64: installed exfat, 1.2.10, 4.19.2-041902-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2018-03-27 (235 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.2-041902-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: Upgraded to cosmic on 2018-10-19 (29 days ago) dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1803849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
CONFIRM: @digitalcircuit's 2018-06-10 recommendation works to complete do-release-upgrade from 16.04.5 to 18.04.1, after addressing exim4 issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Fix Committed Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial, ie. lxc launch ubuntu-daily:xenial test-shim-upgrade lxc exec test-shim-upgrade apt update apt install systemd-shim wget https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb apt install ./systemd-shim_10-3_amd64.deb sed 's/xenial/bionic/' -i /etc/apt/sources.list apt update apt install systemd this currently passes, however, systemd-shim remains installed. It should be removed instead. Apt install systemd should have lines like this: The following packages will be REMOVED: systemd-shim ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' ... [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
** Description changed: [Impact] - * Some systems fail to upgrade due to conflicts between systemd and the + * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. - * Instead of trying to work out what's the problem in ordering / + * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] - * monitor drop-off of upgrades with below reported problem + * monitor drop-off of upgrades with below reported problem - * Check that it is possible to upgrade to bionic's libpam-systemd from - xenial with systemd-shim installed on xenial. + * Check that it is possible to upgrade to bionic's libpam-systemd from + xenial with systemd-shim installed on xenial, ie. + + lxc launch ubuntu-daily:xenial test-shim-upgrade + lxc exec test-shim-upgrade + apt update + apt install systemd-shim + wget https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb + apt install ./systemd-shim_10-3_amd64.deb + sed 's/xenial/bionic/' -i /etc/apt/sources.list + apt update + apt install systemd + + this currently passes, however, systemd-shim remains installed. It + should be removed instead. Apt install systemd should have lines like + this: + + The following packages will be REMOVED: + systemd-shim + ... + Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' + ... + [Regression Potential] - * systemd-shim/upstart are both removed and not supported in bionic, + * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] - - * original bug report + * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Fix Committed Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial, ie. lxc launch ubuntu-daily:xenial test-shim-upgrade lxc exec test-shim-upgrade apt update apt install systemd-shim wget https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb apt install ./systemd-shim_10-3_amd64.deb sed 's/xenial/bionic/' -i /etc/apt/sources.list apt update apt install systemd this currently passes, however, systemd-shim remains installed. It
[Touch-packages] [Bug 1798073] Re: [SRU] Provide 2018 archive signing key on stable releases
It might be nice to provide this on older LTS releases too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1798073 Title: [SRU] Provide 2018 archive signing key on stable releases Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: Fix Committed Bug description: [Impact] * For LTS releases to be able to bootstrap dual and single signed future releases, and validate all signatures, 2018 archive signing key should be SRUed back * Also build process has improved documentation and vague validation that all key snippets are signed correctly [Test Case] * $ apt-key list ... /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg -- pub rsa4096 2018-09-17 [SC] F6EC B376 2474 EDA9 D21B 7022 8719 20D1 991B C93C uid [ unknown] Ubuntu Archive Automatic Signing Key (2018) ... apt-key list should contain the 2018 archive key. [Regression Potential] * Build-process, key algo, and key size, and file format are the same as previous key snippets thus supported by all of gpg1 gpg2 gpgv1 gpgv2. [Other Info] * 2018 key is to be used for dual-signing in DD series and up * Bileto PPA is built against security pocket only, suitable to be released into both -security and -updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1798073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804036] Re: package apt 1.6.1 failed to install/upgrade: unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1804036 Title: package apt 1.6.1 failed to install/upgrade: unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error Status in apt package in Ubuntu: New Bug description: All info has been provided in the report ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apt 1.6.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Mon Nov 19 09:27:23 2018 DpkgTerminalLog: Preparing to unpack .../archives/apt_1.6.6_amd64.deb ... Unpacking apt (1.6.6) over (1.6.1) ... dpkg: error processing archive /var/cache/apt/archives/apt_1.6.6_amd64.deb (--unpack): unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error DuplicateSignature: package:apt:1.6.1 Unpacking apt (1.6.6) over (1.6.1) ... dpkg: error processing archive /var/cache/apt/archives/apt_1.6.6_amd64.deb (--unpack): unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error ErrorMessage: unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error InstallationDate: Installed on 2018-11-11 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.1 SourcePackage: apt Title: package apt 1.6.1 failed to install/upgrade: unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1804036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804036] [NEW] package apt 1.6.1 failed to install/upgrade: unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error
Public bug reported: All info has been provided in the report ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apt 1.6.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Mon Nov 19 09:27:23 2018 DpkgTerminalLog: Preparing to unpack .../archives/apt_1.6.6_amd64.deb ... Unpacking apt (1.6.6) over (1.6.1) ... dpkg: error processing archive /var/cache/apt/archives/apt_1.6.6_amd64.deb (--unpack): unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error DuplicateSignature: package:apt:1.6.1 Unpacking apt (1.6.6) over (1.6.1) ... dpkg: error processing archive /var/cache/apt/archives/apt_1.6.6_amd64.deb (--unpack): unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error ErrorMessage: unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error InstallationDate: Installed on 2018-11-11 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.1 SourcePackage: apt Title: package apt 1.6.1 failed to install/upgrade: unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1804036 Title: package apt 1.6.1 failed to install/upgrade: unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error Status in apt package in Ubuntu: New Bug description: All info has been provided in the report ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apt 1.6.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Mon Nov 19 09:27:23 2018 DpkgTerminalLog: Preparing to unpack .../archives/apt_1.6.6_amd64.deb ... Unpacking apt (1.6.6) over (1.6.1) ... dpkg: error processing archive /var/cache/apt/archives/apt_1.6.6_amd64.deb (--unpack): unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error DuplicateSignature: package:apt:1.6.1 Unpacking apt (1.6.6) over (1.6.1) ... dpkg: error processing archive /var/cache/apt/archives/apt_1.6.6_amd64.deb (--unpack): unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error ErrorMessage: unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error InstallationDate: Installed on 2018-11-11 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.1 SourcePackage: apt Title: package apt 1.6.1 failed to install/upgrade: unable to stat './usr/share/bash-completion/completions/apt' (which I was about to install): Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1804036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
I solved problem sttoping services and erasing systemd-shim upon console. After I could updating my pc, also, from console Kind regards El mié., 17 oct. 2018 23:11, Brian Murray escribió: > ** Tags added: bugpattern-written > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1792241). > https://bugs.launchpad.net/bugs/1773859 > > Title: > upgrades to 18.04 fail > > Status in systemd package in Ubuntu: > Fix Released > Status in systemd-shim package in Ubuntu: > Won't Fix > Status in systemd source package in Bionic: > In Progress > Status in systemd-shim source package in Bionic: > Won't Fix > Status in systemd source package in Cosmic: > Fix Released > Status in systemd-shim source package in Cosmic: > Won't Fix > > Bug description: > [Impact] > >* Some systems fail to upgrade due to conflicts between systemd and > the (now removed from the archive) systemd-shim / upstart. > >* Instead of trying to work out what's the problem in ordering / > removal of diverts, ensure that systemd is never unpacked whilst > systemd-shim/upstart are still on disk. Thus declare conflicts against > systemd-shim/upstart packages in systemd package. > > [Test Case] > >* monitor drop-off of upgrades with below reported problem > >* Check that it is possible to upgrade to bionic's libpam-systemd > from xenial with systemd-shim installed on xenial. > > [Regression Potential] > >* systemd-shim/upstart are both removed and not supported in bionic, > thus forcing their removal via conflicts should bring the system into > an expected state. > > [Other Info] > >* original bug report > > > $ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be REMOVED: > systemd-shim > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 71.7 kB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 63 files and directories currently installed.) > Removing systemd-shim (9-1bzr4ubuntu1) ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > dpkg-divert: error: rename involves overwriting > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with > different file > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', > not allowed > dpkg: error processing package systemd-shim (--remove): >subprocess installed post-removal script returned error exit status 2 > Errors were encountered while processing: >systemd-shim > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Commenting out the dpkg-divert in systemd-shim's postrm solved this > for me and I was about to continue the upgrade. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions > -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Fix Committed Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial. [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you
[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Similar experience on a DO instance. Initial do-release-upgrade failure due to bug #1793932: exim4 deprecated conffile issue. Now recovery is systemd-shim (9-1bzr4ubuntu1) blocked. @digitalcircuit's 2018-06-10 suggestion above did not work for me. Will restore 16.04 and try again later. Details: $ sudo apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: cgmanager libcryptsetup4 rename Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: debconf debconf-i18n exim4-base exim4-daemon-heavy libapparmor-perl libgdbm-compat4 libgdbm5 libhtml-parser-perl liblocale-gettext-perl libmailutils5 libnet-ssleay-perl libpam-systemd libperl5.26 libreadline7 libsocket6-perl libssl1.1 libtext-charwidth-perl libtext-iconv-perl networkd-dispatcher perl perl-base perl-modules-5.26 perl-openssl-defaults systemd Suggested packages: debconf-doc debconf-utils libterm-readline-gnu-perl libgtk3-perl libnet-ldap-perl libqtgui4-perl libqtcore4-perl eximon4 exim4-doc-html | exim4-doc-info spf-tools-perl swaks gdbm-l10n libdata-dump-perl perl-doc libterm-readline-gnu-perl | libterm-readline-perl-perl systemd-container policykit-1 The following packages will be REMOVED: libperl5.22 perl-modules-5.22 systemd-shim The following NEW packages will be installed: libgdbm-compat4 libgdbm5 libmailutils5 libperl5.26 libreadline7 libssl1.1 networkd-dispatcher perl-modules-5.26 perl-openssl-defaults The following packages will be upgraded: debconf debconf-i18n exim4-base exim4-daemon-heavy libapparmor-perl libhtml-parser-perl liblocale-gettext-perl libnet-ssleay-perl libpam-systemd libsocket6-perl libtext-charwidth-perl libtext-iconv-perl perl perl-base systemd 15 upgraded, 9 newly installed, 3 to remove and 389 not upgraded. 3 not fully installed or removed. Need to get 0 B/14.9 MB of archives. After this operation, 3,000 kB of additional disk space will be used. Do you want to continue? [Y/n] Preconfiguring packages ... (Reading database ... 97832 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Fix Committed Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial. [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Thanks a lot for your help. I resolved my problem erasing systemd-shim and updating. I'll try new solution in another pc. Kind regards El lun., 19 nov. 2018 15:11, Łukasz Zemczak <1773...@bugs.launchpad.net> escribió: > Hello Kees, or anyone else affected, > > Accepted systemd into bionic-proposed. The package will build now and be > available at > https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few > hours, and then in the -proposed repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how > to enable and use -proposed. Your feedback will aid us getting this > update out to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested and change the tag from > verification-needed-bionic to verification-done-bionic. If it does not > fix the bug for you, please add a comment stating that, and change the > tag to verification-failed-bionic. In either case, without details of > your testing we will not be able to proceed. > > Further information regarding the verification process can be found at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > advance for helping! > > N.B. The updated package will be released to -updates after the bug(s) > fixed by this package have been verified and the package has been in > -proposed for a minimum of 7 days. > > ** Changed in: systemd (Ubuntu Bionic) >Status: In Progress => Fix Committed > > ** Tags added: verification-needed verification-needed-bionic > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1792241). > https://bugs.launchpad.net/bugs/1773859 > > Title: > upgrades to 18.04 fail > > Status in systemd package in Ubuntu: > Fix Released > Status in systemd-shim package in Ubuntu: > Won't Fix > Status in systemd source package in Bionic: > Fix Committed > Status in systemd-shim source package in Bionic: > Won't Fix > Status in systemd source package in Cosmic: > Fix Released > Status in systemd-shim source package in Cosmic: > Won't Fix > > Bug description: > [Impact] > >* Some systems fail to upgrade due to conflicts between systemd and > the (now removed from the archive) systemd-shim / upstart. > >* Instead of trying to work out what's the problem in ordering / > removal of diverts, ensure that systemd is never unpacked whilst > systemd-shim/upstart are still on disk. Thus declare conflicts against > systemd-shim/upstart packages in systemd package. > > [Test Case] > >* monitor drop-off of upgrades with below reported problem > >* Check that it is possible to upgrade to bionic's libpam-systemd > from xenial with systemd-shim installed on xenial. > > [Regression Potential] > >* systemd-shim/upstart are both removed and not supported in bionic, > thus forcing their removal via conflicts should bring the system into > an expected state. > > [Other Info] > >* original bug report > > > $ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be REMOVED: > systemd-shim > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 71.7 kB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 63 files and directories currently installed.) > Removing systemd-shim (9-1bzr4ubuntu1) ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > dpkg-divert: error: rename involves overwriting > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with > different file > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', > not allowed > dpkg: error processing package systemd-shim (--remove): >subprocess installed post-removal script returned error exit status 2 > Errors were encountered while processing: >systemd-shim > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Commenting out the dpkg-divert in systemd-shim's postrm solved this > for me and I was about to continue the upgrade. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions > -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Fix Committed Status in
[Touch-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic
Launchpad has imported 1 comments from the remote bug at https://bugs.documentfoundation.org/show_bug.cgi?id=120663. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-10-17T15:57:39+00:00 Sergio Callegari wrote: Description: The fault seems to be on the Libreoffice application running on the computer, not on the android impress remote app. Running libreoffice, the computer reports a bluetoothd error on syslog, namely bluetoothd[1491]: RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) After that the remote handset cannot connect via bluetooth to LibO even if the the bluetooth adapters in the computer and the handset are paired. The issue appears in the bug trackers of both Ubuntu and Fedora and regards Ubuntu 18.04 and Fedora 27. I am 100% sure that in the past the impress remote was working via bluetooth on the same hardware (both computer and handset). It is unclear to me if the issue is with the bluetooth stack of recent linux distros (bluez? kernel?) or if something has changed in it and LibO is trying to still use it in some old way that is now wrong. The issue is now present using any LibO version from 5.4 to 6.1. See https://bugzilla.redhat.com/show_bug.cgi?id=1581879 and https://bugs.launchpad.net/bugs/1798400 Steps to Reproduce: See description Actual Results: See description Expected Results: See description Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: StartModule [Information guessed from browser] OS: Linux (All) OS is 64bit: yes Reply at: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400/comments/4 ** Changed in: df-libreoffice Status: Unknown => New ** Changed in: df-libreoffice Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5
[Touch-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported
Edit: This terminal ouput is from a Surface Go. Also there is a guide how to port it to Linux https://developer.qualcomm.com/download/qca9377/wlan-bluetooth-linux- porting-guide.pdf Also there have been some updates in the upstream linux-firmware repo. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=a87eb5f7bac0f70ade57da57d9126d14eee12336 and https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0 but they also do not help to get the wifi card working. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported Status in HWE Next: Fix Released Status in HWE Next wily series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Invalid Status in linux source package in Wily: Fix Released Status in linux-firmware source package in Wily: Fix Released Bug description: = CURRENT STATUS: Wily(15.10) could not work with and don't need Adam's dkms package 1.0 or 1.1 Wily(15.10) has already fixed the driver part, and the firmware part is in progress. For now, you guys could use 15.10(purge the ath10k-dkms if you tried installing it), and make a copy of https://git.kernel.org/cgit/linux/kernel/git/firmware/linux- firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/ 15.10 will work in a week by a simple `apt upgrade` Distros before 15.10(lower than 4.2 kernel) please keep using the dkms(which will be relocated soon) = Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. Qualcomm Atheros Device [168c:003e] (rev 20) mainline commit d63955b33b3bee45d784ffdfafeb93076c765660 [6.221281] ath10k_pci :02:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0 [6.417386] ath10k_pci :02:00.0: Direct firmware load for ath10k/cal-pci-:02:00.0.bin failed with error -2 [6.417404] ath10k_pci :02:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/board-pci-168c:003e:17aa:3044.bin failed with error -2 [6.417407] ath10k_pci :02:00.0: failed to load spec board file, falling back to generic: -2 [6.417416] ath10k_pci :02:00.0: Direct firmware load for
[Touch-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported
Still an issue even four years later. On Ubuntu 18.10 dmesg outputs: "[4.242132] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 168c:3370 [4.242138] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [4.243006] ath10k_pci :01:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [4.308059] ath10k_pci :01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370 from ath10k/QCA6174/hw3.0/board-2.bin [4.309354] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 ed5f849a" There is a board.bin available directly from the vendor http://www.killernetworking.com/support/K1535_Debian/board.bin The only thing which is missing is getting this added to https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles . My problem is that I dont know how to read the board files and modify them because I do not know the encoding they use. Any ideas how to get this solved? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported Status in HWE Next: Fix Released Status in HWE Next wily series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Invalid Status in linux source package in Wily: Fix Released Status in linux-firmware source package in Wily: Fix Released Bug description: = CURRENT STATUS: Wily(15.10) could not work with and don't need Adam's dkms package 1.0 or 1.1 Wily(15.10) has already fixed the driver part, and the firmware part is in progress. For now, you guys could use 15.10(purge the ath10k-dkms if you tried installing it), and make a copy of https://git.kernel.org/cgit/linux/kernel/git/firmware/linux- firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/ 15.10 will work in a week by a simple `apt upgrade` Distros before 15.10(lower than 4.2 kernel) please keep using the dkms(which will be relocated soon) = Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. Qualcomm Atheros Device [168c:003e] (rev 20) mainline commit
[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
This bug was fixed in the package systemd - 239-7ubuntu10.4 --- systemd (239-7ubuntu10.4) cosmic-security; urgency=medium [ Chris Coulson ] * SECURITY UPDATE: symlink mishandling in systemd-tmpfiles - debian/patches/CVE-2018-6954_2.patch: backport the remaining patches to resolve this completely - CVE-2018-6954 [ Balint Reczey ] * Fix LP: #1803391 - Skip daemon-reexec and try-restarts during shutdown - update debian/systemd.postinst -- Chris Coulson Thu, 15 Nov 2018 20:42:32 + ** Changed in: systemd (Ubuntu Cosmic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Committed Bug description: [Impact] * Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. [Regression Potential] * The daemons, shipped in deb:systemd, are not attempted to be restarted because despite package installation the system is in the middle of shutting down. This means that currently running daemons may be helding up open files on the filesystem, however all process are being stopped and killed as part of shutdown. Hence the worst possible regression from this, is an unclean shutdown, but even that shouldn't happen with this update. [Test Case] Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] root@uu-systemd-onshutdown:~# reboot Session terminated, terminating shell...Terminated root@uu-systemd- rbalint@yogi:~$ rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# tail /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
[Touch-packages] [Bug 1804027] Re: dbus-daemon sigsegv, apport cannot report it: expected core size ...
** Attachment added: "core dump file" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1804027/+attachment/5214227/+files/apport_core_0k2jxx4e -- 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/1804027 Title: dbus-daemon sigsegv, apport cannot report it: expected core size ... Status in dbus package in Ubuntu: New Bug description: At almost every boot and login after a while I get a "Ubuntu 18.10 has experienced an internal error" window. However it says, coredump size is too small (see attached screenshot). Also no idea if it is related but touchpad of the notebook does not work only external mouse. This is a fresh 18.10 install on this new Lenovo L580 notebook, live version of ubuntu worked fine with touchpad and there was no window on dbus like that. However after the install it worked only once, then not anymore, regardless of reboot, powering off and on etc, and usually the mentioned internal error window is shown. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: dbus 1.12.10-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 19 17:24:50 2018 InstallationDate: Installed on 2018-11-15 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1804027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804027] Re: dbus-daemon sigsegv, apport cannot report it: expected core size ...
** Attachment added: "crash file from /var/crash" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1804027/+attachment/5214228/+files/_usr_bin_dbus-daemon.1000.crash -- 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/1804027 Title: dbus-daemon sigsegv, apport cannot report it: expected core size ... Status in dbus package in Ubuntu: New Bug description: At almost every boot and login after a while I get a "Ubuntu 18.10 has experienced an internal error" window. However it says, coredump size is too small (see attached screenshot). Also no idea if it is related but touchpad of the notebook does not work only external mouse. This is a fresh 18.10 install on this new Lenovo L580 notebook, live version of ubuntu worked fine with touchpad and there was no window on dbus like that. However after the install it worked only once, then not anymore, regardless of reboot, powering off and on etc, and usually the mentioned internal error window is shown. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: dbus 1.12.10-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 19 17:24:50 2018 InstallationDate: Installed on 2018-11-15 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1804027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804027] [NEW] dbus-daemon sigsegv, apport cannot report it: expected core size ...
Public bug reported: At almost every boot and login after a while I get a "Ubuntu 18.10 has experienced an internal error" window. However it says, coredump size is too small (see attached screenshot). Also no idea if it is related but touchpad of the notebook does not work only external mouse. This is a fresh 18.10 install on this new Lenovo L580 notebook, live version of ubuntu worked fine with touchpad and there was no window on dbus like that. However after the install it worked only once, then not anymore, regardless of reboot, powering off and on etc, and usually the mentioned internal error window is shown. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: dbus 1.12.10-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 19 17:24:50 2018 InstallationDate: Installed on 2018-11-15 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1804027/+attachment/5214223/+files/Screenshot%20from%202018-11-19%2017-32-17.png -- 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/1804027 Title: dbus-daemon sigsegv, apport cannot report it: expected core size ... Status in dbus package in Ubuntu: New Bug description: At almost every boot and login after a while I get a "Ubuntu 18.10 has experienced an internal error" window. However it says, coredump size is too small (see attached screenshot). Also no idea if it is related but touchpad of the notebook does not work only external mouse. This is a fresh 18.10 install on this new Lenovo L580 notebook, live version of ubuntu worked fine with touchpad and there was no window on dbus like that. However after the install it worked only once, then not anymore, regardless of reboot, powering off and on etc, and usually the mentioned internal error window is shown. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: dbus 1.12.10-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 19 17:24:50 2018 InstallationDate: Installed on 2018-11-15 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1804027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
This bug was fixed in the package systemd - 237-3ubuntu10.9 --- systemd (237-3ubuntu10.9) bionic-security; urgency=medium [ Chris Coulson ] * SECURITY UPDATE: symlink mishandling in systemd-tmpfiles - debian/patches/CVE-2018-6954_2.patch: backport the remaining patches to resolve this completely - CVE-2018-6954 [ Balint Reczey ] * Fix LP: #1803391 - Skip daemon-reexec and try-restarts during shutdown - update debian/systemd.postinst -- Chris Coulson Thu, 15 Nov 2018 20:45:11 + ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6954 -- 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/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Committed Bug description: [Impact] * Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. [Regression Potential] * The daemons, shipped in deb:systemd, are not attempted to be restarted because despite package installation the system is in the middle of shutting down. This means that currently running daemons may be helding up open files on the filesystem, however all process are being stopped and killed as part of shutdown. Hence the worst possible regression from this, is an unclean shutdown, but even that shouldn't happen with this update. [Test Case] Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] root@uu-systemd-onshutdown:~# reboot Session terminated, terminating shell...Terminated root@uu-systemd- rbalint@yogi:~$ rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device
[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
Another possibly related issue: bug #1762726 (Context menu does not show on passwords fields). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in ibus package in Ubuntu: Confirmed Bug description: tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic
** Bug watch added: Document Foundation Bugzilla #120663 https://bugs.documentfoundation.org/show_bug.cgi?id=120663 ** Also affects: df-libreoffice via https://bugs.documentfoundation.org/show_bug.cgi?id=120663 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Unknown Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU 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:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997217] Update Released
The verification of the Stable Release Update for cyrus-sasl2 has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/997217
Title:
salsauthd maxes cpu
Status in cyrus-sasl2 package in Ubuntu:
Fix Released
Status in cyrus-sasl2 source package in Precise:
Won't Fix
Status in cyrus-sasl2 source package in Trusty:
Invalid
Status in cyrus-sasl2 source package in Xenial:
Fix Released
Bug description:
[Impact]
The rimap authentication mechanism in saslauthd can hit a condition
where it will start spinning and using all available CPU. This
condition can be easily encountered when an authentication is
happening and the imap service is being restarted.
Furthermore, the saslauthd child process that picked up that
authentication request and that is spinning now won't be reaped nor
can it service further requests. If all children are left in this
state, the authentication service as a whole won't be working anymore.
[Test Case]
This test can be performed in a LXD or VM.
* install the needed packages. mail-stack-delivery is used to have an
imap server available on localhost that needs no further
configuration. Accept the defaults for all debconf prompts:
sudo apt update
sudo apt install sasl2-bin mail-stack-delivery
* set the password "ubuntu" for the ubuntu user
echo ubuntu:ubuntu | sudo chpasswd
* start saslauthd like this, with just one child:
sudo /usr/sbin/saslauthd -a rimap -O localhost -r -n 1
* restart dovecot
sudo service dovecot restart
* test saslauthd authentication:
$ sudo testsaslauthd -u ubuntu -p ubuntu
0: OK "Success."
* Now let's break it. In one terminal watch the output of top:
top
* in another terminal, run the following:
sudo testsaslauthd -u ubuntu -p ubuntu & sleep 1; sudo service dovecot stop
* observe in the "top" terminal that saslauthd is consuming a lot of
cpu. If that's not happening, try starting dovecot again and adjusting
the sleep value in the previous test command, but 1s was enough in all
my runs.
* start dovecot and repeat the authentication request. Since the only
saslauthd child is now spinning, this will block:
sudo service dovecot start
$ sudo testsaslauthd -u ubuntu -p ubuntu
[Regression Potential]
This fix relies on read(2) returning zero bytes when the connection is
dropped, and that is clearly documented in its manpage:
"On success, the number of bytes read is returned (zero indicates
end of file),"
The select manpage also documents such a case being a valid case to
indicate that a socket is ready to be read from, and that it won't
block:
"The file descriptors listed in readfds will be watched to see if
characters become available for reading (more precisely, to see if a
read will not block; in particular, a file descriptor is also
ready on end-of-file)"
This patch is what was used upstream, and is also present in bionic.
I can't think of regressions specific to this change, other than the
usual risk of rebuilding a widely used library (sasl2) in an
environment different from the one from when xenial was released,
i.e., different libraries available, maybe different system-wide build
options, etc.
[Other Info]
Trusty is still not accounting for read() returning zero being an end-of-file
case, but the loop there has a counter and it eventually exits, not leading to
a perpetual spin or high cpu usage (see comment #17 for a brief history on how
this fix was dropped in the xenial package).
The fix is simple and could be applied there as well, if the SRU team
prefers.
[Original Description]
sasl2-bin version 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu contains a
bug that causes heavy cpu utilization, impacting normal operation of
one of our mail servers following an upgrade to Ubuntu 12.04.
We are running the daemon with the following options:
/usr/sbin/saslauthd -a rimap -O our.imap.server -r -m
/var/spool/postfix/var/run/saslauthd -n 5
We noticed that users were unable to send mail and that the saslauthd
processes were using approximately 100% of each cpu core. An strace of
one of the runaway process showed that it was stuck in the following
behaviour:
select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0})
read(8, "", 940)= 0
select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0})
read(8, "", 940)
[Touch-packages] [Bug 1776626] Re: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part
** Changed in: ubuntu-z-systems Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1776626 Title: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part Status in Ubuntu on IBM z Systems: In Progress Status in cryptsetup package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in cryptsetup source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Bug description: [Impact] * cryptsetup in bionic supports creating luks volumes with a non- standard sector-size option, and thus this option also needs to be used when activating the LUKS volumes. Add sector-size= option support to /etc/crypttab. [Test Case] * Create a plain LUKS volume with sector-size 4096 * Specify sector-size=4096 option in /etc/crypttab * reload systemd, start systemd-cryptsetup@.service for that volume * check the journal, to ensure that `sector-size` option was recognized and is active. (i.e. there is not error messages about unrecognized option `sector-size` from systemd-cryptsetup) [Regression Potential] * This is an optional argument, not used by default. Currently custom sector-size crypttab does not work correctly, and thus cannot regress. [Other Info] * Original bug report Support fast clear key dm-crypt with 4k support Extend /etc/crypttab to enable 4k sector support in plain mode The proposed enhancements are posted on github, see https://github.com/systemd/systemd/issues/8881 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776626/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997217] Re: salsauthd maxes cpu
This bug was fixed in the package cyrus-sasl2 - 2.1.26.dfsg1-14ubuntu0.1
---
cyrus-sasl2 (2.1.26.dfsg1-14ubuntu0.1) xenial; urgency=medium
* d/p/dont_hang_when_imap_closes.patch: Don't hang when IMAP
server closes connection. (LP: #997217)
-- Andreas Hasenack Wed, 24 Oct 2018 14:51:00
-0300
** Changed in: cyrus-sasl2 (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/997217
Title:
salsauthd maxes cpu
Status in cyrus-sasl2 package in Ubuntu:
Fix Released
Status in cyrus-sasl2 source package in Precise:
Won't Fix
Status in cyrus-sasl2 source package in Trusty:
Invalid
Status in cyrus-sasl2 source package in Xenial:
Fix Released
Bug description:
[Impact]
The rimap authentication mechanism in saslauthd can hit a condition
where it will start spinning and using all available CPU. This
condition can be easily encountered when an authentication is
happening and the imap service is being restarted.
Furthermore, the saslauthd child process that picked up that
authentication request and that is spinning now won't be reaped nor
can it service further requests. If all children are left in this
state, the authentication service as a whole won't be working anymore.
[Test Case]
This test can be performed in a LXD or VM.
* install the needed packages. mail-stack-delivery is used to have an
imap server available on localhost that needs no further
configuration. Accept the defaults for all debconf prompts:
sudo apt update
sudo apt install sasl2-bin mail-stack-delivery
* set the password "ubuntu" for the ubuntu user
echo ubuntu:ubuntu | sudo chpasswd
* start saslauthd like this, with just one child:
sudo /usr/sbin/saslauthd -a rimap -O localhost -r -n 1
* restart dovecot
sudo service dovecot restart
* test saslauthd authentication:
$ sudo testsaslauthd -u ubuntu -p ubuntu
0: OK "Success."
* Now let's break it. In one terminal watch the output of top:
top
* in another terminal, run the following:
sudo testsaslauthd -u ubuntu -p ubuntu & sleep 1; sudo service dovecot stop
* observe in the "top" terminal that saslauthd is consuming a lot of
cpu. If that's not happening, try starting dovecot again and adjusting
the sleep value in the previous test command, but 1s was enough in all
my runs.
* start dovecot and repeat the authentication request. Since the only
saslauthd child is now spinning, this will block:
sudo service dovecot start
$ sudo testsaslauthd -u ubuntu -p ubuntu
[Regression Potential]
This fix relies on read(2) returning zero bytes when the connection is
dropped, and that is clearly documented in its manpage:
"On success, the number of bytes read is returned (zero indicates
end of file),"
The select manpage also documents such a case being a valid case to
indicate that a socket is ready to be read from, and that it won't
block:
"The file descriptors listed in readfds will be watched to see if
characters become available for reading (more precisely, to see if a
read will not block; in particular, a file descriptor is also
ready on end-of-file)"
This patch is what was used upstream, and is also present in bionic.
I can't think of regressions specific to this change, other than the
usual risk of rebuilding a widely used library (sasl2) in an
environment different from the one from when xenial was released,
i.e., different libraries available, maybe different system-wide build
options, etc.
[Other Info]
Trusty is still not accounting for read() returning zero being an end-of-file
case, but the loop there has a counter and it eventually exits, not leading to
a perpetual spin or high cpu usage (see comment #17 for a brief history on how
this fix was dropped in the xenial package).
The fix is simple and could be applied there as well, if the SRU team
prefers.
[Original Description]
sasl2-bin version 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu contains a
bug that causes heavy cpu utilization, impacting normal operation of
one of our mail servers following an upgrade to Ubuntu 12.04.
We are running the daemon with the following options:
/usr/sbin/saslauthd -a rimap -O our.imap.server -r -m
/var/spool/postfix/var/run/saslauthd -n 5
We noticed that users were unable to send mail and that the saslauthd
processes were using approximately 100% of each cpu core. An strace of
one of the runaway process showed that it was stuck in the following
behaviour:
select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0})
read(8, "", 940)= 0
select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0})
read(8, "", 940)= 0
select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8],
[Touch-packages] [Bug 1800877] Re: iproute2/xenial: Add support for the VF Trust setting (fix IPv6 multicast under SR-IOV on Mellanox adapters)
This bug was fixed in the package iproute2 - 4.3.0-1ubuntu3.16.04.4
---
iproute2 (4.3.0-1ubuntu3.16.04.4) xenial; urgency=medium
* Add support for VF Trust (LP: #1800877)
- d/p/1008-vf_trust_dddf1b44126e.patch: netlink attribute
- d/p/1009-vf_trust_b6d77d9ee312.patch: set it for kernel
- d/p/1010-vf_trust_fe9322781e63.patch: print it for user
-- Mauricio Faria de Oliveira Tue, 18 Sep 2018
12:21:44 -0300
** Changed in: iproute2 (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1800877
Title:
iproute2/xenial: Add support for the VF Trust setting (fix IPv6
multicast under SR-IOV on Mellanox adapters)
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
Fix Released
Bug description:
[Impact]
* An VM's VF cannot receive IPv6 multicast traffic
from other VMs' VFs in the same Mellanox adapter
_if_ its VF trust setting is not enabled, and on
Xenial currently iproute2 _cannot_ enable it.
* This breaks IPv6 NDP (Neighbor Discovery Protocol)
in that scenario.
* This upload adds three iproute2 upstream commits
to enable/disable the VF setting, which resolves
that problem/limitation.
[Test Case]
* Check 'ip link help' for the 'trust' option:
Before:
# ip link help 2>&1 | grep trust
After:
# ip link help 2>&1 | grep trust
[ trust { on | off} ] ]
* Check 'ip link show dev PF' for 'trust on|off' field in VFs.
Before: (trust field _is not_ present)
# ip link show dev ens1f0
...
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
After: (trust field _is_ present)
# ip link show dev ens1f0
...
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
* Set the VF trust on/off and check it:
Set VF 0 trust on:
# ip link set ens1f0 vf 0 trust on
# ip link show dev ens1f0 | grep trust
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust on
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
Set VF 0 trust off:
# ip link set ens1f0 vf 0 trust off
# ip link show dev ens1f0 | grep trust
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
[Regression Potential]
* Regression potential is low because the commits just add the
netlink attribute for the userspace-kernel interface and the
ways to set/clear it, and show the current value to the user.
* Regressions could happen _if_ the user turns the setting on
(it's disabled by default) and there's a problem/bug likely
in _other_ component that depends on that setting (which is
something to fix on such component).
[Other Info]
* The users that reported this problem have verified
the test package with these changes, and confirmed
that it now works correctly for IPv6 NDP/multicast.
* Upstream commits:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=dddf1b44126e
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=fe9322781e63
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=b6d77d9ee312
* Only affect Xenial release :
# rmadison iproute2
iproute2 | 4.3.0-1ubuntu3.16.04.3 | xenial-updates
iproute2 | 4.15.0-2ubuntu1| bionic
iproute2 | 4.18.0-1ubuntu2| cosmic
iproute2 | 4.18.0-1ubuntu2| disco
# iproute2 upstream vcs
$ git describe --contains dddf1b44126e
v4.4.0~67
$ git describe --contains b6d77d9ee312
v4.5.0~47
$ git describe --contains fe9322781e63
v4.6.0~32
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1800877/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800877] Update Released
The verification of the Stable Release Update for iproute2 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1800877
Title:
iproute2/xenial: Add support for the VF Trust setting (fix IPv6
multicast under SR-IOV on Mellanox adapters)
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
Fix Released
Bug description:
[Impact]
* An VM's VF cannot receive IPv6 multicast traffic
from other VMs' VFs in the same Mellanox adapter
_if_ its VF trust setting is not enabled, and on
Xenial currently iproute2 _cannot_ enable it.
* This breaks IPv6 NDP (Neighbor Discovery Protocol)
in that scenario.
* This upload adds three iproute2 upstream commits
to enable/disable the VF setting, which resolves
that problem/limitation.
[Test Case]
* Check 'ip link help' for the 'trust' option:
Before:
# ip link help 2>&1 | grep trust
After:
# ip link help 2>&1 | grep trust
[ trust { on | off} ] ]
* Check 'ip link show dev PF' for 'trust on|off' field in VFs.
Before: (trust field _is not_ present)
# ip link show dev ens1f0
...
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
After: (trust field _is_ present)
# ip link show dev ens1f0
...
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
* Set the VF trust on/off and check it:
Set VF 0 trust on:
# ip link set ens1f0 vf 0 trust on
# ip link show dev ens1f0 | grep trust
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust on
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
Set VF 0 trust off:
# ip link set ens1f0 vf 0 trust off
# ip link show dev ens1f0 | grep trust
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
[Regression Potential]
* Regression potential is low because the commits just add the
netlink attribute for the userspace-kernel interface and the
ways to set/clear it, and show the current value to the user.
* Regressions could happen _if_ the user turns the setting on
(it's disabled by default) and there's a problem/bug likely
in _other_ component that depends on that setting (which is
something to fix on such component).
[Other Info]
* The users that reported this problem have verified
the test package with these changes, and confirmed
that it now works correctly for IPv6 NDP/multicast.
* Upstream commits:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=dddf1b44126e
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=fe9322781e63
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=b6d77d9ee312
* Only affect Xenial release :
# rmadison iproute2
iproute2 | 4.3.0-1ubuntu3.16.04.3 | xenial-updates
iproute2 | 4.15.0-2ubuntu1| bionic
iproute2 | 4.18.0-1ubuntu2| cosmic
iproute2 | 4.18.0-1ubuntu2| disco
# iproute2 upstream vcs
$ git describe --contains dddf1b44126e
v4.4.0~67
$ git describe --contains b6d77d9ee312
v4.5.0~47
$ git describe --contains fe9322781e63
v4.6.0~32
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1800877/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
Hello Dan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-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/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Confirmed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate
Hello errors.ubuntu.com, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-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/1773148 Title: /lib/systemd/systemd- journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * systemd aborts journald, upon watchdog expiry and generates lots of crash reports * it appears that journald is simply stuck in fsync * it has been agreed to disable watchdog timer on journald [Test Case] * watch drop-off of errors w.r.t. watchdog timer [Regression Potential] * Potentially journald does get stuck, and thus is no longer automatically restarted with a sigabrt crash. However, so far, it is not known to do that. [Other Info] * Original bug report The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1773148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
Hello Damiön, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in landscape-client source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
Hello Frank, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-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/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image Status in Ubuntu on IBM z Systems: Fix Released Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC image on a z/VM guest leads to a kernel panic: /lib/debian-installer/start-udev: line 15: can't create /sys/module/scsi_mod/par ameters/scan: Permission denied ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ exitcode=0x00 000100 ¬0.845071| ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic #157-Ubun tu ¬0.845077|7d107c20 7d107cb0 0002 000 0 7d107d50 7d107cc8 7d107cc8 00114732 008b 009a304c 009f11d0 000b 7d107d10 7d107cb0 040001cdf800 00114732 7d107cb0 7d107d10 ¬0.845089| Call Trace: ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) ¬0.845095| ¬<001146e2>| show_stack+0x72/0xf8 ¬0.845099| ¬<00555752>| dump_stack+0x82/0xb8 ¬0.845101| ¬<00286390>| panic+0x108/0x250 ¬0.845104| ¬<00166228>| do_exit+0xac0/0xba0 ¬0.845106| ¬<001663c8>| do_group_exit+0x50/0xe0 ¬0.845108| ¬<00166488>| __wake_up_parent+0x0/0x28 ¬0.845111| ¬<007eadda>| system_call+0xee/0x28c ¬0.845113| ¬<03ff8953983a>| 0x3ff8953983a 00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0010F8CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776626] Re: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part
Hello bugproxy, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-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/1776626 Title: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part Status in Ubuntu on IBM z Systems: Fix Released Status in cryptsetup package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in cryptsetup source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Bug description: [Impact] * cryptsetup in bionic supports creating luks volumes with a non- standard sector-size option, and thus this option also needs to be used when activating the LUKS volumes. Add sector-size= option support to /etc/crypttab. [Test Case] * Create a plain LUKS volume with sector-size 4096 * Specify sector-size=4096 option in /etc/crypttab * reload systemd, start systemd-cryptsetup@.service for that volume * check the journal, to ensure that `sector-size` option was recognized and is active. (i.e. there is not error messages about unrecognized option `sector-size` from systemd-cryptsetup) [Regression Potential] * This is an optional argument, not used by default. Currently custom sector-size crypttab does not work correctly, and thus cannot regress. [Other Info] * Original bug report Support fast clear key dm-crypt with 4k support Extend /etc/crypttab to enable 4k sector support in plain mode The proposed enhancements are posted on github, see https://github.com/systemd/systemd/issues/8881 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776626/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU
Hello Ryan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-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/1671951 Title: networkd should allow configuring IPV6 MTU Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Status in cloud-init source package in Bionic: Confirmed Status in netplan.io source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Bug description: = systemd = [Impact] * IPv6 traffic failing to send/receive due to incompatible/low MTU setting. Specifically, IPv6 traffic may have higher MTU requirements than IPv4 traffic and thus may need to be overridden and/or set to a higher value than IPv6 traffic. [Test Case] * Use IPv6MTUBytes= setting in a .network unit * Restart systemd-network * Check that there no error messages / warnings about not-recognizing this option * Check that MTU bytes, is at least IPv6MTUBytes on the interface [Regression Potential] * This is a future compatible backport of an additional keyword not used by default. It may result in MTU change to a higher value, which should not cause loss of connectivity. [Other Info] * Original bug report below = end of systemd = 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this configuration to the interface. Upstream has discussed this issue here: https://github.com/systemd/systemd/pull/1533 But it's been closed in favor of only setting via RA. However, we know of multiple use-case which are currently supported in ifdupdown where we want to retain control over IPV6 MTU values outside of PMTU Discovery configurations. Some context from those discussions >> Client systems that route their ipv6 packets to a 6in4 router also >> have to have their ipv6 mtu lowered. They could lower their link mtu, >> so their ipv6 packets are small enough, but that reduces performance >> of their ipv4 network. Yes. Anything that creates a PMTUD black hole can result in situations where the higher header overhead of IPv6 will cause IPv4 to pass but IPv6 traffic to be dropped. One example here is egress from an ipsec tunnel wherein the next hop MTU is too low for IPv6 datagrams to pass. Another is VM -> whatever -> host bridge -> tunnel ingress. If the datagram cannot enter the tunnel due to size, it is dropped, and an ICMP response uses the tunnel address as a source, which may not be routable back to the origin. This one is an issue with IPv4 as well, and is one case where manually setting the IPv6 MTU lower than the (also manually set) device MTU is of benefit. In essence, any of these sort of cases that require an explicit setting of the device MTU will likely require a setting of the IPv6 mtu as well to account for its larger header overhead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
Hello Balint, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-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/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Committed Bug description: [Impact] * Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. [Regression Potential] * The daemons, shipped in deb:systemd, are not attempted to be restarted because despite package installation the system is in the middle of shutting down. This means that currently running daemons may be helding up open files on the filesystem, however all process are being stopped and killed as part of shutdown. Hence the worst possible regression from this, is an unclean shutdown, but even that shouldn't happen with this update. [Test Case] Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all
[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Hello Kees, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Fix Committed Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial. [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch
Hello Michael, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-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/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * core18 systems fail to update hostname * this happens due to /etc/hostname actually being a symlink to a file under /etc/writable/, adjust hostnamed to take that into account when trying to update /etc/hostname [Test Case] * run a core18 system, check that dhcp acquire hostname is correctly updated in /etc/writable/hostname [Regression Potential] * This is cherrypick of code that has gone missing since xenial. * There is no change of behaviour for the classic systems. * Currently, core18 systems simply fail to update hostname/machine-info files, thus the worst case is that they will still fail to do so. [Other Info] * original bug report The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
** Description changed: - Installation of latest systemd update in -security hangs with current + + [Impact] + + * Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. + + + [Regression Potential] + + * The daemons, shipped in deb:systemd, are not attempted to be + restarted because despite package installation the system is in the + middle of shutting down. This means that currently running daemons may + be helding up open files on the filesystem, however all process are + being stopped and killed as part of shutdown. Hence the worst possible + regression from this, is an unclean shutdown, but even that shouldn't + happen with this update. + + [Test Case] Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown - rbalint@yogi:~$ lxc shell uu-systemd-onshutdown + rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] root@uu-systemd-onshutdown:~# reboot Session terminated, terminating shell...Terminated root@uu-systemd- - rbalint@yogi:~$ - rbalint@yogi:~$ lxc shell uu-systemd-onshutdown + rbalint@yogi:~$ + rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# tail /var/log/unattended-upgrades/unattended-upgrades-dpkg.log Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ... Setting up libsystemd0:amd64 (237-3ubuntu10.6) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Setting up systemd (237-3ubuntu10.6) ... Failed to try-restart systemd-networkd.service: Transaction is destructive. See system logs and 'systemctl status systemd-networkd.service' for details. Failed to try-restart systemd-resolved.service: Transaction is destructive. See system logs and 'systemctl status systemd-resolved.service' for details. root@uu-systemd-onshutdown:~# ps -ef | cat UIDPID PPID C STIME TTY TIME CMD root 1 0 0 15:34 ?00:00:00 /lib/systemd/systemd --system --deserialize 22 root53 1 0 15:34 ?00:00:00 /lib/systemd/systemd-journald systemd+
[Touch-packages] [Bug 1803992] [NEW] Lock screen, notifications panel crashes
Public bug reported: Multiple issues: 1) Lock screen crashes revealing the desktop after sleep/wake 2) Notification panel crashes constantly (with ubuntu-mate) 3) Ability to send report fails for whatever reason Pics attached here: https://imgur.com/a/dtUaXQF Happy to work with anyone to get this resolved. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: MATE Date: Mon Nov 19 08:40:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.15.0-38-generic, x86_64: installed nvidia, 390.87, 4.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 6GB] [3842:6161] LightdmLog: [+119931.86s] DEBUG: Seat seat0 changes active session to [+119934.82s] DEBUG: Seat seat0 changes active session to c2 [+119934.82s] DEBUG: Session c2 is already active MachineType: Gigabyte Technology Co., Ltd. Z170X-Designare ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=/dev/mapper/hostname--vg-root ro initrd=initrd.gz text SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23g dmi.board.asset.tag: Default string dmi.board.name: Z170X-Designare-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23g:bd03/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Designare:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Designare-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170X-Designare dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1803992 Title: Lock screen, notifications panel crashes Status in xorg package in Ubuntu: New Bug description: Multiple issues: 1) Lock screen crashes revealing the desktop after sleep/wake 2) Notification panel crashes constantly (with ubuntu-mate) 3) Ability to send report fails for whatever reason Pics attached here: https://imgur.com/a/dtUaXQF Happy to work with anyone to get this resolved. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: MATE Date: Mon Nov 19 08:40:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.15.0-38-generic, x86_64: installed nvidia, 390.87, 4.15.0-39-generic,
[Touch-packages] [Bug 1803707] Re: merge nss 2:3.39-1 from Debian unstable
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/nss/+git/nss/+merge/358921 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1803707 Title: merge nss 2:3.39-1 from Debian unstable Status in nss package in Ubuntu: In Progress Bug description: please merge newer nss for disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1803707/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803749] Re: apt.Cache.clear() may set apt.Package.is_auto_removable to False
This is caused by unattended-upgrades having an ActionGroup during the clear. So, UnattendedUpgrades cache should likely overwrite clear() and make it reset the action group, for example (after making actiongroup global): def clear(self): global actiongroup actiongroup.release() # pyflakes apt.Cache.clear(self) actiongroup = apt_pkg.ActionGroup(cache._depcache) ** Package changed: python-apt (Ubuntu) => unattended-upgrades (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1803749 Title: apt.Cache.clear() may set apt.Package.is_auto_removable to False Status in unattended-upgrades package in Ubuntu: New Bug description: While triaging LP: #1803587 I found that originally autoremovable packages were handled as newly autoremovable ones by unattended- upgrades due to not finding all of them at the beginning of u-u's run. The root cause seems to be cache.clear() resetting pkg.is_auto_removable to False under some circumstances I haven't fully narrowed down. The reproduction is as follows: Set up a Bionic (or later) system with autoremovable packages, packages upgradable from -security and blacklist at least one upgradable package and apply the following patch to u-u: root@bb-1803587:~# diff -Naur /usr/bin/unattended-upgrade.orig /usr/bin/unattended-upgrade --- /usr/bin/unattended-upgrade.orig 2018-11-16 16:17:58.522583254 + +++ /usr/bin/unattended-upgrade 2018-11-16 16:36:12.226675870 + @@ -948,7 +948,9 @@ def rewind_cache(cache, pkgs_to_upgrade): # type: (apt.Cache, List[apt.Package]) -> None """ set the cache back to the state with packages_to_upgrade """ +print([pkg.name for pkg in cache if pkg.is_auto_removable]) cache.clear() +print([pkg.name for pkg in cache if pkg.is_auto_removable]) for pkg2 in pkgs_to_upgrade: pkg2.mark_install(from_user=not pkg2.is_auto_installed) if cache.broken_count > 0: Run u-u to observe cache.clear() resetting the list of autoremovable packages: ~# /usr/bin/unattended-upgrade --dry-run --verbose --debug Initial blacklisted packages: systemd Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic Using (^linux-image|^linux-headers|^linux-image-extra|^linux-modules|^linux-modules-extra|^linux-signed-image|^kfreebsd-image|^kfreebsd-headers|^gnumach-image|^.*-modules|^.*-kernel|^linux-backports-modules-.*|^linux-modules-.*|^linux-tools|^linux-cloud-tools) regexp to find kernel packages Using (^linux-image.*4.15.0-38-generic|^linux-headers.*4.15.0-38-generic|^linux-image-extra.*4.15.0-38-generic|^linux-modules.*4.15.0-38-generic|^linux-modules-extra.*4.15.0-38-generic|^linux-signed-image.*4.15.0-38-generic|^kfreebsd-image.*4.15.0-38-generic|^kfreebsd-headers.*4.15.0-38-generic|^gnumach-image.*4.15.0-38-generic|4.15.0-38-generic.*-modules|4.15.0-38-generic.*-kernel|^linux-backports-modules-.*.*4.15.0-38-generic|^linux-modules-.*.*4.15.0-38-generic|^linux-tools.*4.15.0-38-generic|^linux-cloud-tools.*4.15.0-38-generic) regexp to find running kernel packages Checking: apport ([]) adjusting candidate version: apport=2.20.9-0ubuntu7.1 ... Checking: libnss-systemd ([, ]) skipping blacklisted package systemd pkg systemd package has been blacklisted sanity check failed ['libfreetype6'] [] ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1803749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801338] Re: apt fails to properly handle server-side connection closure
Yes, exactly, that's why it was removed from disco-proposed and I quickly reverted it in the followup upload. Though, the problem only seems to happen with apache based servers, if you put a squid in front of them, you're fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1801338 Title: apt fails to properly handle server-side connection closure Status in apt package in Ubuntu: Triaged Status in apt source package in Xenial: New Status in apt source package in Bionic: Triaged Status in apt source package in Cosmic: Triaged Bug description: [Impact] In some cases, apt does not correctly handle server-side connection closure after a pipeline, and aborts the file being downloaded with an "Undetermined Error" when the connection has been closed. [Test case] This could be seen by running apt build-dep evince on cosmic with a recent apt with the pipelining fix (such as 1.6.6) against a local mirror running apache from trusty. It remains to be seen whether this is easily reproducible for anyone. [Regression potential] N/A yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799202] Re: SRU: update Python 3.7 to the 3.7.1 release
This bug was fixed in the package python3-stdlib-extensions - 3.6.7-1~18.04 --- python3-stdlib-extensions (3.6.7-1~18.04) bionic-proposed; urgency=medium * SRU: LP: #1799202. * Update 3.6 extensions and modules to 3.6.7. * Update 3.7 extensions and modules to 3.7.1. -- Matthias Klose Mon, 22 Oct 2018 13:15:03 +0200 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1799202 Title: SRU: update Python 3.7 to the 3.7.1 release Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Fix Committed Status in python3.7 package in Ubuntu: Fix Committed Status in python3-defaults source package in Bionic: New Status in python3-stdlib-extensions source package in Bionic: Fix Released Status in python3.7 source package in Bionic: Fix Released Status in python3-defaults source package in Cosmic: Fix Released Status in python3-stdlib-extensions source package in Cosmic: Fix Released Status in python3.7 source package in Cosmic: Fix Released Bug description: SRU: update Python 3.7 to the 3.7.1 release. 3.7.1 is the first maintenance release, update both 18.04 LTS and 18.10 to the release. For 18.10 it's just one bug fix compared to the release candidate 2. python3-stdlib-extensions also updates the modules to the 3.6.7 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799206] Re: SRU: update python3.6 to the new minor release 3.6.7
Thanks for the verification! I also double-checked python-asdf and it's indeed busted in release as well. I think we can proceed with releasing of the packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1799206 Title: SRU: update python3.6 to the new minor release 3.6.7 Status in python3-defaults package in Ubuntu: Fix Committed Status in python3.6 package in Ubuntu: Fix Committed Status in python3-defaults source package in Bionic: Fix Released Status in python3.6 source package in Bionic: Fix Released Status in python3-defaults source package in Cosmic: Fix Released Status in python3.6 source package in Cosmic: Fix Released Bug description: SRU: update python3.6 to the new minor release 3.6.7 See LP: #1792143 for the rationale, going one minor release ahead (and planning to do 3.6.8 in January, the last source release from the 3.6 branch). [Impact] Provide the branch updates for the stable 3.6 branch in the LTS release. [Regression Potential] There is regression potential, but this version is in use in 18.10, which didn't show regressions. [Test Case] No regressions in the Python 3.6 test suite, no regressions in the autopkg tests Failing autopkg tests: - http://autopkgtest.ubuntu.com/packages/p/python-asdf/bionic/armhf failed before, flaky autopkg tests history, now passes in disco. - snapcraft: amd64 and i386 try to download some rust installation, which then fails to build some downloaded code. This doesn't look like a reliable test. - python-mechanicalsoup: unrelated, fails in both 2.7 and 3.6. Fixed in cosmic, filed LP: #1802835 for a fix anyway. - http://autopkgtest.ubuntu.com/packages/l/lxd/bionic/arm64 doesn't look like a regression in the autopkg test history. pinged the lxd maintainers, but no response yet. LP: #1803344 lxd now passes after giving back several times - ocrmypdf has a hint: adconrad:unblock ocrmypdf/6.1.2-1ubuntu1 This does not seem to be a regression, although fixed in disco via a new upstream version 6.2.5. And now fixed by another SRU ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799206/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799206] Re: SRU: update python3.6 to the new minor release 3.6.7
This bug was fixed in the package python3-defaults - 3.6.7-1~18.04 --- python3-defaults (3.6.7-1~18.04) bionic-proposed; urgency=medium * SRU: LP: #1799206. * Drop python3.7 as a supported python3 version for the bionic SRU. python3-defaults (3.6.7-1) unstable; urgency=high * Really ship the policy in the python3 package, and update from the last version found in the python package. Closes: #910113. * Bump version to 3.6.7. python3-defaults (3.6.6-1) unstable; urgency=medium [ Matthias Klose ] * Fix the idle desktop file. Closes: #901096. * Install the policy files in the python3 package. Closes: #901486. * python3-minimal: Pre-Depend on python3.6-minimal. Closes: #901001. * Bump version to 3.6.6. [ Scott Kitterman ] * Remove myself from uploaders -- Matthias Klose Thu, 25 Oct 2018 13:11:00 +0200 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1799206 Title: SRU: update python3.6 to the new minor release 3.6.7 Status in python3-defaults package in Ubuntu: Fix Committed Status in python3.6 package in Ubuntu: Fix Committed Status in python3-defaults source package in Bionic: Fix Released Status in python3.6 source package in Bionic: Fix Released Status in python3-defaults source package in Cosmic: Fix Released Status in python3.6 source package in Cosmic: Fix Released Bug description: SRU: update python3.6 to the new minor release 3.6.7 See LP: #1792143 for the rationale, going one minor release ahead (and planning to do 3.6.8 in January, the last source release from the 3.6 branch). [Impact] Provide the branch updates for the stable 3.6 branch in the LTS release. [Regression Potential] There is regression potential, but this version is in use in 18.10, which didn't show regressions. [Test Case] No regressions in the Python 3.6 test suite, no regressions in the autopkg tests Failing autopkg tests: - http://autopkgtest.ubuntu.com/packages/p/python-asdf/bionic/armhf failed before, flaky autopkg tests history, now passes in disco. - snapcraft: amd64 and i386 try to download some rust installation, which then fails to build some downloaded code. This doesn't look like a reliable test. - python-mechanicalsoup: unrelated, fails in both 2.7 and 3.6. Fixed in cosmic, filed LP: #1802835 for a fix anyway. - http://autopkgtest.ubuntu.com/packages/l/lxd/bionic/arm64 doesn't look like a regression in the autopkg test history. pinged the lxd maintainers, but no response yet. LP: #1803344 lxd now passes after giving back several times - ocrmypdf has a hint: adconrad:unblock ocrmypdf/6.1.2-1ubuntu1 This does not seem to be a regression, although fixed in disco via a new upstream version 6.2.5. And now fixed by another SRU ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799206/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799202] Re: SRU: update Python 3.7 to the 3.7.1 release
This bug was fixed in the package python3.7 - 3.7.1-1~18.04 --- python3.7 (3.7.1-1~18.04) bionic-proposed; urgency=medium * SRU: LP: #1799202. python3.7 (3.7.1-1) unstable; urgency=medium * Python 3.7.1 release. python3.7 (3.7.1~rc2-1) unstable; urgency=medium * Python 3.7.1 release candidate 2. python3.7 (3.7.1~rc1-1) unstable; urgency=medium * Python 3.7.1 release candidate 1. python3.7 (3.7.0-7) unstable; urgency=medium * Update to 20180925 from the 3.7 branch. * Don't run OpenSSL related tests during the build. Hanging on some buildds. python3.7 (3.7.0-6) unstable; urgency=medium * Update to 20180901 from the 3.7 branch. - Fixes the build with OpenSSL 1.1.1. Closes: #907031. * Don't run the test_ftplib and test_ssl autopkg tests, not yet ready for OpenSSL 1.1.1. python3.7 (3.7.0-5) unstable; urgency=medium * Update to 20180820 from the 3.7 branch. * Avoid usage of distutils in the platform module. See issue #26544. * Fix some issues on architectures from the computer museum (Jason Duerstock). Closes: #905536. - Disable -O3 on ia64 (see PR rtl-optimization/85412). - Remove the -O2 override on m68k (see Debian #326903). - Remove the -mieee and -O2 overrides for DEC Alpha (see Debian #212912). * Add more breaks for packages not compatible with Python 3.7: - python3-aiomeasures. See #906159. - python3-motor (updated). See #903527. * Again close the RC issue about the syntax errors triggered by Python 3.7. Closes: #902788. * Update symbols files. python3.7 (3.7.0-4) unstable; urgency=medium * Update to 20180802 from the 3.7 branch. * Add more breaks for packages not compatible with Python 3.7: - python3-pyatspi. See #902989. * Move test/__main__.py into libpython3.7-stdlib. python3.7 (3.7.0-3) unstable; urgency=medium * Update to 20180730 from the 3.7 branch. * Add more breaks for packages not compatible with Python 3.7: - python3-trollius. See #903888. - python3-sleekxmpp. See #904453. - voltron. See #904657. - visidata. See #904656. - salt-common. See #903654. - python3-yowsup. See #904653. - python3-websockets. See #904650. - python3-txfixtures. See #904649. - python3-tweepy. See #904648. - python3-slixmpp. See #904644. - python3-signaller. See #904642. - python3-rpyc. See #904615. - python3-protorpc-standalone. See #904603. - python3-nova. See #904587. - python3-murano. See #904581. - python3-mastodon. See #904579. - python3-hug. See #904576. - python3-async. See #904492. - python3-pylama. See #904491. - python3-exabgp. See #904390. - python3-glance. See #904389. - python3-gbulb. See #904388. - python3-engineio. See #904383. - python3-doublex. See #904382. - python3-dns. See #904381. - python3-opcua. See #904373. - openscap-daemon. See #904. - oca-core. See #904370. - patroni. See #904369. - python3-panoramisk. See #904368. - linux-show-player-. See #904367. - python3-cs. See #904365. - python3-azure. See #904364. - python3-applicationinsights. See #904363. - python3-aiopg. See #904361. - python3-aiozmq. See #904358. - python3-pysnmp4. See #904357. - python3-astroquery. See #904351. - snakemake. See #904350. - fail2ban. See #902817. - python3-morse-simulator. See #904343. - python3-tango. See #904298. - python3-pycuda. See #903826. - python3-pycsw. See #903784. - gnome3-builder. See #903558. * Close the RC issue about the syntax errors triggered by Python 3.7, now that all the breaks are in place. Closes: #902788. * Mark the lib2to3 and site tests as succeeding again, mark the tcl test as failing (issue #34178). python3.7 (3.7.0-2) unstable; urgency=medium * Update to 20180720 from the 3.7 branch. * Add breaks for packages not compatible with Python 3.7: - python3-twisted. See #902766. - python3-pexpect. See #902646. - python3-cxx-dev. See #902673. - libboost-python1.62.0. See #902702. - python3-psycopg2. See #902715. - python3-maxminddb. See #902756. - python3-blist. See #902757. - python3-django. See #902761. - diffoscope. See #902650. - gpodder. See #902704. - python3-http-parser. See: #902759. - python3-celery. See #902900. - python3-astroid. See #902631. - python3-ubjson. See #902762. - python3-protobuf. See #902597. - python3-opengl. See #903218. - python3-ws4py. See #903529. - python3-dropbox. See #903525. - python3-pycuda. See #903826. - python3-libcloud. See #903388. - python3-motor. See #903527. - python3-jira. See #903526. -- Matthias Klose Mon, 22 Oct 2018 13:21:55 +0200 ** Changed in: python3.7 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: python3-stdlib-extensions (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification
[Touch-packages] [Bug 1799206] Re: SRU: update python3.6 to the new minor release 3.6.7
This bug was fixed in the package python3.6 - 3.6.7-1~18.04
---
python3.6 (3.6.7-1~18.04) bionic-proposed; urgency=medium
* SRU: LP: #1799206.
python3.6 (3.6.7-1) unstable; urgency=medium
* Python 3.6.7 release.
python3.6 (3.6.7~rc2-1) unstable; urgency=medium
* Python 3.6.7 release candidate 2.
python3.6 (3.6.7~rc1-1) unstable; urgency=medium
* Python 3.6.7 release candidate 1.
python3.6 (3.6.6-4) unstable; urgency=medium
* Update to 20180901 from the 3.6 branch.
* Add idle-python3.6 to the autopkg test depends.
python3.6 (3.6.6-3) unstable; urgency=medium
* Update to 20180828 from the 3.6 branch.
* Disable running some tests which are not ready for Debian's OpenSSL
defaults (test_{asyncio,ftplib,httplib,imaplib,nntplib,poplib,ssl}).
Closes: #907215.
python3.6 (3.6.6-2) unstable; urgency=medium
* Update to 20180820 from the 3.6 branch.
* Avoid usage of distutils in the platform module. See issue #26544.
* Move test/__main__.py into libpython3.6-stdlib.
* Pass the list of the pyFPE breaks as a parameter into dpkg-gencontrol
instead of hard-coding them in the control file.
-- Matthias Klose Mon, 22 Oct 2018 13:32:17 +0200
** Changed in: python3.6 (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: python3-defaults (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1799206
Title:
SRU: update python3.6 to the new minor release 3.6.7
Status in python3-defaults package in Ubuntu:
Fix Committed
Status in python3.6 package in Ubuntu:
Fix Committed
Status in python3-defaults source package in Bionic:
Fix Released
Status in python3.6 source package in Bionic:
Fix Released
Status in python3-defaults source package in Cosmic:
Fix Released
Status in python3.6 source package in Cosmic:
Fix Released
Bug description:
SRU: update python3.6 to the new minor release 3.6.7
See LP: #1792143 for the rationale, going one minor release ahead (and
planning to do 3.6.8 in January, the last source release from the 3.6
branch).
[Impact]
Provide the branch updates for the stable 3.6 branch in the LTS release.
[Regression Potential]
There is regression potential, but this version is in use in 18.10, which
didn't show regressions.
[Test Case]
No regressions in the Python 3.6 test suite, no regressions in the autopkg
tests
Failing autopkg tests:
- http://autopkgtest.ubuntu.com/packages/p/python-asdf/bionic/armhf
failed before, flaky autopkg tests history, now passes in disco.
- snapcraft: amd64 and i386 try to download some rust installation,
which then fails to build some downloaded code. This doesn't look
like a reliable test.
- python-mechanicalsoup: unrelated, fails in both 2.7 and 3.6.
Fixed in cosmic, filed LP: #1802835 for a fix anyway.
- http://autopkgtest.ubuntu.com/packages/l/lxd/bionic/arm64
doesn't look like a regression in the autopkg test history.
pinged the lxd maintainers, but no response yet. LP: #1803344
lxd now passes after giving back several times
- ocrmypdf has a hint: adconrad:unblock ocrmypdf/6.1.2-1ubuntu1
This does not seem to be a regression, although fixed in disco via
a new upstream version 6.2.5.
And now fixed by another SRU ...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799206/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1739931] Update Released
The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1739931 Title: Separator lines in shell popup menus are too faint to see Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in ubuntu-themes package in Ubuntu: Won't Fix Status in gnome-shell source package in Bionic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Bionic: Won't Fix Status in ubuntu-themes source package in Bionic: Won't Fix Bug description: [ Impact ] Separators in gnome-shell menuitems are not visible [ Test case ] 1. Right - Click on a dock icon 2. Separators between menu items should be visible [ Regression potential ] Nothing known when I click on the dock icons, some of the lines in the popup menus are blank and some of them appear to be incorrect. see top left of attached screenshot. ProblemType: BugDistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-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.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 23 22:24:40 2017 InstallationDate: Installed on 2016-08-18 (492 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1739931] Re: Separator lines in shell popup menus are too faint to see
This bug was fixed in the package gnome-shell - 3.28.3-0ubuntu0.18.04.3 --- gnome-shell (3.28.3-0ubuntu0.18.04.3) bionic; urgency=medium * debian/ubuntu.css: - use defined color for menu separators (LP: #1739931) - set StEntry minimun height to work properly with Ubuntu font (LP: #1743058) * debian/patches/st-button-Ignore-pointer-emulated-touch-events.patch: - Don't emit two click events on touch under X11 (LP: #1745888) * d/p/st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch, d/p/st-scroll-view-Remove-scrollbars-references-on-dispose.patch: - Handle NULL scroll bars in st-scroll-view (LP: #1725312) -- Marco Trevisan (Treviño) Tue, 06 Nov 2018 17:49:17 + ** Changed in: gnome-shell (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1739931 Title: Separator lines in shell popup menus are too faint to see Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in ubuntu-themes package in Ubuntu: Won't Fix Status in gnome-shell source package in Bionic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Bionic: Won't Fix Status in ubuntu-themes source package in Bionic: Won't Fix Bug description: [ Impact ] Separators in gnome-shell menuitems are not visible [ Test case ] 1. Right - Click on a dock icon 2. Separators between menu items should be visible [ Regression potential ] Nothing known when I click on the dock icons, some of the lines in the popup menus are blank and some of them appear to be incorrect. see top left of attached screenshot. ProblemType: BugDistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-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.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 23 22:24:40 2017 InstallationDate: Installed on 2016-08-18 (492 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798700] Update Released
The verification of the Stable Release Update for elfutils has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to elfutils in Ubuntu. https://bugs.launchpad.net/bugs/1798700 Title: ftbfs on arm64 Status in elfutils package in Ubuntu: Fix Released Status in elfutils source package in Cosmic: Fix Released Bug description: [impact] elfutils ftbfs on sid on arm64 currently: FAIL: run-backtrace-dwarf.sh 0xb3c5373craise 0xb3c418e8abort /<>/tests/backtrace-dwarf: dwfl_thread_getframes: (null) dwarf: no main FAIL run-backtrace-dwarf.sh (exit status: 1) FAIL: run-deleted.sh PID 19405 - process TID 19405: #0 0x81e7f3e0 __nanosleep #1 0x81e7f2c0 sleep /<>/src/stack: dwfl_thread_getframes tid 19405 at 0x81e7f2bf in /lib/aarch64-linux-gnu/libc-2.28.so: (null) FAIL run-deleted.sh (exit status: 1) Current git passes, and git bisect and logic point to the following upstream commit as fixing it: commit f881459ffc95b6fad51aa055a158ee14814073aa Author: Mark Wielaard Date: Wed Apr 11 10:37:45 2018 +0200 aarch64: Add default cfi rule to restore SP from CFA address. The CFA is set by default to the stack pointer of the previous frame. So that is also how we can always restore the SP. This default aarch64 CFI rule is necessary on Fedora 28 with GCC8 to make the run-deleted.sh and run-backtrace-dwarf.sh testcases work. Signed-off-by: Mark Wielaard Debugging the test failure made it clear that the libdw1 in the archive will not be able to successfully walk the stack of processes built by gcc-8, i.e. this is a regression in runtime functionality. I don't know if any of the revdeps of libdw1 depend on this but it seems at least possible and the patch to fix all this is pretty simple so my inclination is that this meets the threshold for an SRU. [test case] Build the package on arm64. [regression potential] The patch is small, fairly (given the general level of hairiness around here) simple and only affects the functionality that is currently broken. There's always the chance that building with a new toolchain will introduce new problems, but there's not much we can do about that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1798700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798700] Re: ftbfs on arm64
This bug was fixed in the package elfutils - 0.170-0.5.0ubuntu1 --- elfutils (0.170-0.5.0ubuntu1) cosmic; urgency=medium * Add d/patches/0001-aarch64-Add-default-cfi-rule-to-restore-SP-from-CFA-.patch to fix walking the stack of arm64 binaries compiled with GCC 8. (LP: #1798700) -- Michael Hudson-Doyle Thu, 18 Oct 2018 20:06:01 +1300 ** Changed in: elfutils (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to elfutils in Ubuntu. https://bugs.launchpad.net/bugs/1798700 Title: ftbfs on arm64 Status in elfutils package in Ubuntu: Fix Released Status in elfutils source package in Cosmic: Fix Released Bug description: [impact] elfutils ftbfs on sid on arm64 currently: FAIL: run-backtrace-dwarf.sh 0xb3c5373craise 0xb3c418e8abort /<>/tests/backtrace-dwarf: dwfl_thread_getframes: (null) dwarf: no main FAIL run-backtrace-dwarf.sh (exit status: 1) FAIL: run-deleted.sh PID 19405 - process TID 19405: #0 0x81e7f3e0 __nanosleep #1 0x81e7f2c0 sleep /<>/src/stack: dwfl_thread_getframes tid 19405 at 0x81e7f2bf in /lib/aarch64-linux-gnu/libc-2.28.so: (null) FAIL run-deleted.sh (exit status: 1) Current git passes, and git bisect and logic point to the following upstream commit as fixing it: commit f881459ffc95b6fad51aa055a158ee14814073aa Author: Mark Wielaard Date: Wed Apr 11 10:37:45 2018 +0200 aarch64: Add default cfi rule to restore SP from CFA address. The CFA is set by default to the stack pointer of the previous frame. So that is also how we can always restore the SP. This default aarch64 CFI rule is necessary on Fedora 28 with GCC8 to make the run-deleted.sh and run-backtrace-dwarf.sh testcases work. Signed-off-by: Mark Wielaard Debugging the test failure made it clear that the libdw1 in the archive will not be able to successfully walk the stack of processes built by gcc-8, i.e. this is a regression in runtime functionality. I don't know if any of the revdeps of libdw1 depend on this but it seems at least possible and the patch to fix all this is pretty simple so my inclination is that this meets the threshold for an SRU. [test case] Build the package on arm64. [regression potential] The patch is small, fairly (given the general level of hairiness around here) simple and only affects the functionality that is currently broken. There's always the chance that building with a new toolchain will introduce new problems, but there's not much we can do about that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1798700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801338] Re: apt fails to properly handle server-side connection closure
And it made multiple buildds hang for days :-(. I just only noticed it now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1801338 Title: apt fails to properly handle server-side connection closure Status in apt package in Ubuntu: Triaged Status in apt source package in Xenial: New Status in apt source package in Bionic: Triaged Status in apt source package in Cosmic: Triaged Bug description: [Impact] In some cases, apt does not correctly handle server-side connection closure after a pipeline, and aborts the file being downloaded with an "Undetermined Error" when the connection has been closed. [Test case] This could be seen by running apt build-dep evince on cosmic with a recent apt with the pipelining fix (such as 1.6.6) against a local mirror running apache from trusty. It remains to be seen whether this is easily reproducible for anyone. [Regression potential] N/A yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
Similar issue (itself with duplicate reports): bug #1803631. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in ibus package in Ubuntu: Confirmed Bug description: tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
** Also affects: systemd (Ubuntu Xenial) 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/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Committed Bug description: Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] root@uu-systemd-onshutdown:~# reboot Session terminated, terminating shell...Terminated root@uu-systemd- rbalint@yogi:~$ rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# tail /var/log/unattended-upgrades/unattended-upgrades-dpkg.log Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ... Setting up libsystemd0:amd64 (237-3ubuntu10.6) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Setting up systemd (237-3ubuntu10.6) ... Failed to try-restart systemd-networkd.service: Transaction is destructive. See system logs and 'systemctl status systemd-networkd.service' for details. Failed to try-restart systemd-resolved.service: Transaction is destructive. See system logs and 'systemctl status systemd-resolved.service' for details. root@uu-systemd-onshutdown:~# ps -ef | cat UIDPID PPID C STIME TTY TIME CMD root 1 0 0 15:34 ?00:00:00 /lib/systemd/systemd --system --deserialize 22 root53 1 0 15:34 ?00:00:00 /lib/systemd/systemd-journald systemd+ 153 1 0 15:34 ?00:00:00 /lib/systemd/systemd-networkd systemd+ 154 1 0
[Touch-packages] [Bug 1803967] Re: package network-manager 1.10.6-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a remova
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1803967 Title: package network-manager 1.10.6-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in network-manager package in Ubuntu: New Bug description: Removed Network manager due to errors, and attempted re-install from downloaded files. it gave the error. but networking is operating now.. could be due to some errors with TorGuard VPN software. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic i686 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 Date: Mon Nov 19 02:42:21 2018 DuplicateSignature: package:network-manager:1.10.6-2ubuntu1.1 Removing network-manager-gnome (1.8.10-2ubuntu1) ... dpkg: error processing package network-manager (--remove): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal IfupdownConfig: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp IpRoute: default via 192.168.11.1 dev eth0 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.11.0/24 dev eth0 proto kernel scope link src 192.168.11.50 IwConfig: eth0 no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 RfKill: SourcePackage: network-manager Title: package network-manager 1.10.6-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: Upgraded to bionic on 2018-05-30 (173 days ago) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started unknown enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1803967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803967] [NEW] package network-manager 1.10.6-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a remo
Public bug reported: Removed Network manager due to errors, and attempted re-install from downloaded files. it gave the error. but networking is operating now.. could be due to some errors with TorGuard VPN software. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic i686 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 Date: Mon Nov 19 02:42:21 2018 DuplicateSignature: package:network-manager:1.10.6-2ubuntu1.1 Removing network-manager-gnome (1.8.10-2ubuntu1) ... dpkg: error processing package network-manager (--remove): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal IfupdownConfig: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp IpRoute: default via 192.168.11.1 dev eth0 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.11.0/24 dev eth0 proto kernel scope link src 192.168.11.50 IwConfig: eth0 no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 RfKill: SourcePackage: network-manager Title: package network-manager 1.10.6-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: Upgraded to bionic on 2018-05-30 (173 days ago) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started unknown enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1803967 Title: package network-manager 1.10.6-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in network-manager package in Ubuntu: New Bug description: Removed Network manager due to errors, and attempted re-install from downloaded files. it gave the error. but networking is operating now.. could be due to some errors with TorGuard VPN software. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic i686 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 Date: Mon Nov 19 02:42:21 2018 DuplicateSignature: package:network-manager:1.10.6-2ubuntu1.1 Removing network-manager-gnome (1.8.10-2ubuntu1) ... dpkg: error processing package network-manager (--remove): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal IfupdownConfig: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp IpRoute: default via 192.168.11.1 dev eth0 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.11.0/24 dev eth0 proto kernel scope link src 192.168.11.50 IwConfig: eth0 no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 RfKill: SourcePackage: network-manager Title: package network-manager 1.10.6-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: Upgraded to bionic on 2018-05-30 (173 days ago) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE
[Touch-packages] [Bug 1803706] Re: long application menus overflowing when screen too small
Launchpad has imported 3 comments from the remote bug at https://bugs.documentfoundation.org/show_bug.cgi?id=121495. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-11-18T18:14:44+00:00 Sandor wrote: Description: Hi I am not a developer, only a user. In 18.10 Cosmic with new Yaru theme: any application with long menus are overflowing and covering the menubar making impossible to slide mouse to the next menu. It affects long sub-menus too (this might be intended as it is same with other applications). It also affects Bionic Ubuntu with original ubuntu theme. When the menu is not wider than the available vertical area of the screen than they show up nicely aligned under the menu toolbar but when it is too large: it might even run edge to edge vertically. It happens when screen is too small or the window is too small. If you want: see pics from launchpad bug 1803706. Steps to Reproduce: 1.open any long menu, like format or edit on small screen; or size window small and open any menu that is longer than vertical length needed. 2. 3. Actual Results: Menu is covering menubar and other menus, even first submenu is usually higher and not aligned well. Expected Results: Menu should open under menubar and stay there. However if submenu is too long that can run edge to edge. That is true for other (not libreoffice) app too. However other apps open long menus nicely. Reproducible: Always User Profile Reset: No Additional Info: It affects others too as I have tried to report it to launchpad (bug 1803706) and another person sent similar pictures, affected Cosmic and Bionic both original Bionic and new Yaru theme. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1803706/comments/12 On 2018-11-18T18:17:16+00:00 Sandor wrote: Created attachment 146722 LibreOffice overflowing menu in Yaru Not just in Yaru, though. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1803706/comments/13 On 2018-11-18T18:19:51+00:00 Sandor wrote: Created attachment 146723 This is from launchpad Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1803706/comments/14 ** Changed in: df-libreoffice Status: Unknown => New ** Changed in: df-libreoffice Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1803706 Title: long application menus overflowing when screen too small Status in LibreOffice: New Status in gtk+3.0 package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: Hi I am not a developer, only a user. In 18.10 Cosmic with new Yaru theme: any application with long menus are overflowing and covering the menubar making impossible to slide mouse to the next menu. It affects long sub-menus too. It mainly affects LibreOffice as it has got quite large menus but it is also present in CherryTree app and I guess in any other. When the menu is not wider than the available vertical area of the screen than they show up nicely aligned under the menu toolbar but when it is too large: it might even run edge to edge vertically. (As for Design: probably a slightly different colour at the end of these long menus would make them more visible where the arrows are.) Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803706] Re: long application menus overflowing when screen too small
Terminal menu does an interesting thing too when it is resized to small window and pulled down to the edge of screen therefore restricting space underneath for menu. when it is in the middle of the screen then menu opens normally but runs out of app window, I guess that is normal, though. ** Attachment added: "Terminal menu 1" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1803706/+attachment/5214116/+files/Terminal-menu-1.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1803706 Title: long application menus overflowing when screen too small Status in LibreOffice: New Status in gtk+3.0 package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: Hi I am not a developer, only a user. In 18.10 Cosmic with new Yaru theme: any application with long menus are overflowing and covering the menubar making impossible to slide mouse to the next menu. It affects long sub-menus too. It mainly affects LibreOffice as it has got quite large menus but it is also present in CherryTree app and I guess in any other. When the menu is not wider than the available vertical area of the screen than they show up nicely aligned under the menu toolbar but when it is too large: it might even run edge to edge vertically. (As for Design: probably a slightly different colour at the end of these long menus would make them more visible where the arrows are.) Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803706] Re: long application menus overflowing when screen too small
I can confirm shotwell does it too on my laptop. ** Attachment added: "Shotwell overflowing menu hiding menubar 1" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1803706/+attachment/5214114/+files/Shotwell-menu-overflowing-1.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1803706 Title: long application menus overflowing when screen too small Status in LibreOffice: Unknown Status in gtk+3.0 package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: Hi I am not a developer, only a user. In 18.10 Cosmic with new Yaru theme: any application with long menus are overflowing and covering the menubar making impossible to slide mouse to the next menu. It affects long sub-menus too. It mainly affects LibreOffice as it has got quite large menus but it is also present in CherryTree app and I guess in any other. When the menu is not wider than the available vertical area of the screen than they show up nicely aligned under the menu toolbar but when it is too large: it might even run edge to edge vertically. (As for Design: probably a slightly different colour at the end of these long menus would make them more visible where the arrows are.) Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803706] Re: long application menus overflowing when screen too small
installed inxi, here is the output. For the link to bugzilla, olivier has already copied it above. Bug 121495 I have 1366x768 display, 15 inch screen, hp laptop elitbook 8560p. inxi -Fx System: Host: sanyi-HP Kernel: 4.18.0-11-generic x86_64 bits: 64 compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.1 Distro: Ubuntu 18.10 (Cosmic Cuttlefish) Machine: Type: Laptop System: Hewlett-Packard product: HP EliteBook 8560p v: A0001D02 serial: Mobo: Hewlett-Packard model: 1618 v: KBC Version 97.4E serial: BIOS: Hewlett-Packard v: 68SCF Ver. F.65 date: 04/06/2017 Battery: ID-1: BAT0 charge: 52.0 Wh condition: 53.8/53.8 Wh (100%) model: Hewlett-Packard Primary status: Unknown CPU: Topology: Dual Core model: Intel Core i5-2520M bits: 64 type: MT MCP arch: Sandy Bridge rev: 7 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19953 Speed: 798 MHz min/max: 800/3200 MHz Core speeds (MHz): 1: 798 2: 799 3: 800 4: 797 Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.1 driver: i915 resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.2.2 direct render: Yes Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k4.18.0-11-generic Network: Device-1: Intel 82579LM Gigabit Network driver: e1000e v: 3.2.6-k port: 4060 bus ID: 00:19.0 IF: enp0s25 state: down mac: b4:b5:2f:2d:d8:58 Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel bus ID: 24:00.0 IF: wlo1 state: up mac: 8c:70:5a:fc:5a:78 IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A Drives: Local Storage: total: 465.76 GiB used: 222.72 GiB (47.8%) ID-1: /dev/sda vendor: Western Digital model: WD5000LPVX-08V0TT5 size: 465.76 GiB temp: 32 C Partition: ID-1: / size: 56.41 GiB used: 47.00 GiB (83.3%) fs: ext4 dev: /dev/sda5 Sensors: System Temperatures: cpu: 39.0 C mobo: 0.0 C Fan Speeds (RPM): N/A Info: Processes: 269 Uptime: 1h 45m Memory: 7.70 GiB used: 2.48 GiB (32.2%) Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 clang: 7.0.0-3 Shell: bash v: 4.4.19 inxi: 3.0.24 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1803706 Title: long application menus overflowing when screen too small Status in LibreOffice: Unknown Status in gtk+3.0 package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: Hi I am not a developer, only a user. In 18.10 Cosmic with new Yaru theme: any application with long menus are overflowing and covering the menubar making impossible to slide mouse to the next menu. It affects long sub-menus too. It mainly affects LibreOffice as it has got quite large menus but it is also present in CherryTree app and I guess in any other. When the menu is not wider than the available vertical area of the screen than they show up nicely aligned under the menu toolbar but when it is too large: it might even run edge to edge vertically. (As for Design: probably a slightly different colour at the end of these long menus would make them more visible where the arrows are.) Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile
I don't like that the sponsorship queue says my name is on this. Removing sponsors. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1750947 Title: pulseaudio print lots of error when selecting unavailable profile Status in HWE Next: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Confirmed Bug description: SRU Document: [Impact] A HDMI audio device usually has several output ports, each port represents a profile in pulseaudio, without this patch, the puseaudio always choose the first profile no matter it is active or not. [Test Case] connect each port of HDMI device, and check if the profile of that port is active or not. [Regression Potential] The patch will check all ports under each profile, if a profile only contains unavailable ports, this profile will be set to unavailable as well. Without this patch, all profiles are always available, then if a profile includes a unusable hdmi-output, and pulseaudio select this profile to be active (since its priority is the highest), the kernel audio driver will crash. I think this patch will not introduce regression: 1) It is a correct logic to set a profile to be unavailable if it only contains unavailable ports. 2) pulseaudio-artful and pulseaudio-bionic already include this patch, they work very well 3) I tested this patch on 1 lenovo laptop, 1 lenovo desktop, 1 dell laptop and 1 dell desktop, all worked well as before 4) tested this patch on two dell machines (LOAD5-DVT2-A2 and Dawson-JC-C without analogue audio) which have unusable hdmi-output profile on them, the kernel driver did not crash anymore and audio function worked very well. [Other Info] Only pulseaudio-xenial has this problem. we need to backport this commit to pulseaudio-xenial. https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4 After printing out the error logs, the kernel crashes and system hangs. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1750947/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803706] Re: long application menus overflowing when screen too small
LibreOffice does make menus scrollable like Gimp does when their contents are too tall, however the y coordinate of the menu is offset, hiding the menu bar. This also affects Shotwell and Transmission, so it's probably a GTK bug. ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1803706 Title: long application menus overflowing when screen too small Status in LibreOffice: Unknown Status in gtk+3.0 package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: Hi I am not a developer, only a user. In 18.10 Cosmic with new Yaru theme: any application with long menus are overflowing and covering the menubar making impossible to slide mouse to the next menu. It affects long sub-menus too. It mainly affects LibreOffice as it has got quite large menus but it is also present in CherryTree app and I guess in any other. When the menu is not wider than the available vertical area of the screen than they show up nicely aligned under the menu toolbar but when it is too large: it might even run edge to edge vertically. (As for Design: probably a slightly different colour at the end of these long menus would make them more visible where the arrows are.) Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
