[Touch-packages] [Bug 1785363] [NEW] Error in Booting
Public bug reported: When i change my default graphics driver as Nvidia then it's not start . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Aug 4 09:59:11 2018 DistUpgraded: 2018-06-18 22:25:36,929 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-23-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:397d] NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF119M [GeForce GT 520M] [17aa:397d] MachineType: LENOVO HuronRiver Platform ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=976f64eb-604f-4770-b36c-2efb3dae6ef1 ro quiet splash acpi_backlight=none vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-06-18 (46 days ago) dmi.bios.date: 10/21/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN38WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr45CN38WW:bd10/21/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: HuronRiver Platform dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 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 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Mon Jun 18 23:25:54 2018 xserver.configfile: default xserver.errors: Failed to initialize GLX extension (Compatible NVIDIA X driver not found) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16560 vendor LEN xserver.version: 2:1.19.6-1ubuntu4 ** 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/1785363 Title: Error in Booting Status in xorg package in Ubuntu: New Bug description: When i change my default graphics driver as Nvidia then it's not start . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Aug 4 09:59:11 2018 DistUpgraded: 2018-06-18 22:25:36,929 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-23-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:397d] NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller])
[Touch-packages] [Bug 1774859] Re: package netcat-openbsd 1.187-1ubuntu0.1 failed to install/upgrade: installed netcat-openbsd package post-installation script subprocess returned error exit status 2
[Expired for netcat-openbsd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: netcat-openbsd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1774859 Title: package netcat-openbsd 1.187-1ubuntu0.1 failed to install/upgrade: installed netcat-openbsd package post-installation script subprocess returned error exit status 2 Status in netcat-openbsd package in Ubuntu: Expired Bug description: was just using "sudo apt-get upgrade" after update, and returned with error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: netcat-openbsd 1.187-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 Date: Sun Jun 3 08:33:04 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libbsd0 0.8.7-1 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DuplicateSignature: package:netcat-openbsd:1.187-1ubuntu0.1 Setting up netcat-openbsd (1.187-1ubuntu0.1) ... update-alternatives: error: cannot stat file '/usr/bin/nodejs': Too many levels of symbolic links dpkg: error processing package netcat-openbsd (--configure): installed netcat-openbsd package post-installation script subprocess returned error exit status 2 ErrorMessage: installed netcat-openbsd package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2018-05-27 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: netcat-openbsd Title: package netcat-openbsd 1.187-1ubuntu0.1 failed to install/upgrade: installed netcat-openbsd package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1774859/+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 1785350] Re: package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of packag
** Tags removed: need-duplicate-check -- 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/1785350 Title: package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 Status in mesa package in Ubuntu: New Bug description: First appeared after system upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-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.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Fri Aug 3 20:32:48 2018 DistUpgraded: 2018-05-18 02:00:49,256 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-24-generic, x86_64: installed nvidia, 390.77, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-24-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed DuplicateSignature: package:libgl1-mesa-dri:18.0.5-0ubuntu0~18.04.1 Unpacking libgl1-mesa-dri:amd64 (18.0.5-0ubuntu0~18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-BSmI2b/074-libgl1-mesa-dri_18.0.5-0ubuntu0~18.04.1_amd64.deb (--unpack): trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701] InstallationDate: Installed on 2017-03-23 (499 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=54d26cb9-e0f9-41d1-a593-869de12e6c28 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, 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 apt 1.6.3 SourcePackage: mesa Title: package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 UpgradeStatus: Upgraded to bionic on 2018-05-18 (77 days ago) dmi.bios.date: 06/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1902 dmi.board.asset.tag: Default string dmi.board.name: Z170-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1902:bd06/27/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1785350/+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 1785351] Re: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1785351 Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: I'm not sure why I received this error, but it could be because I'm running btrfs-tools v4.17. (I'm running btrfs on imsm mdadm raid1.) The btrfs hooks script has this line in it: copy_exec /bin/btrfs-zero-log but this program isn't a part of btrfs-progs anymore, replaced by "btrfs rescue zero-log" Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.17.4-041704-generic E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/initrd.img-4.17.4-041704-generic with 1. dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.23-0ubuntu10) ... Processing triggers for menu (2.1.47ubuntu1.16.04.1) ... Errors were encountered while processing: initramfs-tools ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.11 Uname: Linux 4.17.4-041704-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Aug 3 20:52:17 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-05-30 (795 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: subprocess installed post-installation script 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/1785351/+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 1785351] [NEW] package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I'm not sure why I received this error, but it could be because I'm running btrfs-tools v4.17. (I'm running btrfs on imsm mdadm raid1.) The btrfs hooks script has this line in it: copy_exec /bin/btrfs-zero-log but this program isn't a part of btrfs-progs anymore, replaced by "btrfs rescue zero-log" Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.17.4-041704-generic E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/initrd.img-4.17.4-041704-generic with 1. dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.23-0ubuntu10) ... Processing triggers for menu (2.1.47ubuntu1.16.04.1) ... Errors were encountered while processing: initramfs-tools ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.11 Uname: Linux 4.17.4-041704-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Aug 3 20:52:17 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-05-30 (795 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: subprocess installed post-installation script 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 xenial -- 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/1785351 Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: I'm not sure why I received this error, but it could be because I'm running btrfs-tools v4.17. (I'm running btrfs on imsm mdadm raid1.) The btrfs hooks script has this line in it: copy_exec /bin/btrfs-zero-log but this program isn't a part of btrfs-progs anymore, replaced by "btrfs rescue zero-log" Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.17.4-041704-generic E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/initrd.img-4.17.4-041704-generic with 1. dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.23-0ubuntu10) ... Processing triggers for menu (2.1.47ubuntu1.16.04.1) ... Errors were encountered while processing: initramfs-tools ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.11 Uname: Linux 4.17.4-041704-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Aug 3 20:52:17 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-05-30 (795 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: subprocess installed post-installation script 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/1785351/+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 1785350] [NEW] package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of pack
Public bug reported: First appeared after system upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-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.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Fri Aug 3 20:32:48 2018 DistUpgraded: 2018-05-18 02:00:49,256 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-24-generic, x86_64: installed nvidia, 390.77, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-24-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed DuplicateSignature: package:libgl1-mesa-dri:18.0.5-0ubuntu0~18.04.1 Unpacking libgl1-mesa-dri:amd64 (18.0.5-0ubuntu0~18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-BSmI2b/074-libgl1-mesa-dri_18.0.5-0ubuntu0~18.04.1_amd64.deb (--unpack): trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701] InstallationDate: Installed on 2017-03-23 (499 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=54d26cb9-e0f9-41d1-a593-869de12e6c28 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, 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 apt 1.6.3 SourcePackage: mesa Title: package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 UpgradeStatus: Upgraded to bionic on 2018-05-18 (77 days ago) dmi.bios.date: 06/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1902 dmi.board.asset.tag: Default string dmi.board.name: Z170-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1902:bd06/27/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict ubuntu -- 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/1785350 Title: package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 Status in mesa package in Ubuntu: New Bug description: First appeared after system upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-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'
[Touch-packages] [Bug 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie
When is the apport-autoreport.path service started? I was testing this and noticed that when switching the mode to automatic in g-c-c the file /var/lib/apport/autoreport is created but apport-autoreport.path does not seem to be started so crash reports would sit around until the next reboot when apport-autoreport.path is restarted. I don't think is a deal breaker for this SRU but it should be fixed in cosmic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1778694 Title: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Bug description: [ Impact ] * The goal for autoreporting via whoopsie is to have a silent mode where whoopsie automatically reports crashes. However, this one requires apport-noui to be installed, which we don't by default. apport-noui is just a set of systemd unit starting whoopsie-upload-all (part of apport binary package). We should move the unit to apport package itself. [ Test Case ] * Install the new apport package from proposed * Set in g-c-c, privacy panel, to report bugs automatically * Make one program dumping a core dump * Wait for a while, you should have a .upload and .uploaded files in addition to the .crash one in /var/crash [ Regression potential ] The systemd units were in apport-noui previously, we moved them and made them conditional to whoopsie being installed. apport-noui is still useful by turning autoreport on, so people upgrading shouldn't have any impact or difference. The units have been renamed to make sense and avoid package files overwrite. - There are 2 possible solutions: - promoting apport-noui to main, and seeding it. - or considering there is no reason anymore to have a separate apport-noui pacakge (no more phone factor), and so move the systemd units to apport, having a conditional file on whoopsie installed (no more dependency) and autoreport enabled, shipping those units binary package shipping those units (renamed to apport-autoreport.*) directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1778694/+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 1778497] Re: Add a remember option to whoopsie so that users can diminish crash interactions
I tried this again and it looks the setting was set to "never". I now see the send and don't send buttons with the version in bionic-proposed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1778497 Title: Add a remember option to whoopsie so that users can diminish crash interactions Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Bug description: [ Impact ] A lot of users are bother by the number of whoopsie dialog. We introduced on "G-C-C privacy option don't allow sending manual report" bug (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a way for users to change from always reporting manually (prompting an UI) to auto reporting or never reporting, via a "Remember this in future". This only impacts the apport gtk UI, still offering the underlying capability to other UIs type without changing them. This was a goal for 18.04, but due to a lack of time, we want to introduce this in 18.04.1 [ Test Case ] * There are multiples dialog forms (a good 20 of them), but they are all covered by unit tests which have been updates. One use case would be: * Install the new version and trigger a crash * Check that the dialog has a "Remember this in future" option, check it, and click send. * Check in g-c-c UI, privacy option, that the crash reporting is now in auto mode, always send. * Revert in g-c-c to manual * Create another crash, check "Remember this…" and click don't send * Check in g-c-c UI that crash reporting is now disabled. [ Regression potential ] * The impacted code is both UI and fileutils. It's covered by an extensive testsuite, and checking under KDE has also been done to not trigger a crash. We introduce 5 new strings to translate: "Can't remember send report status settings" "Saving crash reporting state failed. Can't set auto or never reporting mode." "Remember this in future" "Relaunch this application" "Don't send" We are reusing an existing transalted string "Send problem report to the developers?" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1778497/+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 1785236] Re: "dm-tool add-nested-seat" doesn't work normally
** Description changed: Hello, - since I've installed Xubuntu 18-04 (on 15 july 2018). The command "dm-tool add-nested-seat" doesn't work normally. I have a blank screen instead of a login screen. Maybe the problem is due to greeter cause when I set autologin for an user, then everything seems to work normally. The login screen is just skipped. + since I installed Xubuntu 18-04 (on 15 july 2018). The command "dm-tool add-nested-seat" hasn't worked normally. I have a blank screen instead of a login screen. Maybe the problem is due to greeter cause when I set autologin for an user, then everything seems to work normally. The login screen is just skipped. [Impact] "dm-tool add-nested-seat" doesn't work (excepted when autologin-user is set). [Test Case] 1. Log in 2. From a terminal run "dm-tool add-nested-seat" [Expected result] A window opens with a login screen [Observed result] A window opens with a complete black screen if autologin-user isn't set in /etc/lightdm/lightdm.conf No error in the terminal. If autologin is set in /etc/lightdm/lightdm.conf, then it works normally. [used distribution] Xubuntu 18-04, up to date. I didn't have this trouble in may 2018 while I was under Xubuntu 17-10. [related trouble] maybe it's related to this bug: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1529454 But I don't exactly have the same trouble. So I thought I should open a new one. Sorry if I was wrong. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1785236 Title: "dm-tool add-nested-seat" doesn't work normally Status in lightdm package in Ubuntu: New Bug description: Hello, since I installed Xubuntu 18-04 (on 15 july 2018). The command "dm-tool add-nested-seat" hasn't worked normally. I have a blank screen instead of a login screen. Maybe the problem is due to greeter cause when I set autologin for an user, then everything seems to work normally. The login screen is just skipped. [Impact] "dm-tool add-nested-seat" doesn't work (excepted when autologin-user is set). [Test Case] 1. Log in 2. From a terminal run "dm-tool add-nested-seat" [Expected result] A window opens with a login screen [Observed result] A window opens with a complete black screen if autologin-user isn't set in /etc/lightdm/lightdm.conf No error in the terminal. If autologin is set in /etc/lightdm/lightdm.conf, then it works normally. [used distribution] Xubuntu 18-04, up to date. I didn't have this trouble in may 2018 while I was under Xubuntu 17-10. [related trouble] maybe it's related to this bug: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1529454 But I don't exactly have the same trouble. So I thought I should open a new one. Sorry if I was wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1785236/+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 1785324] Re: error popups when I login to my account
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1785324 Title: error popups when I login to my account Status in console-setup package in Ubuntu: New Bug description: error popups when I login to my account ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jul 26 15:35:16 2018 ErrorMessage: installed console-setup package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2017-06-15 (414 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, 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 apt 1.6.3 SourcePackage: console-setup Title: package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1785324/+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 1785324] [NEW] error popups when I login to my account
Public bug reported: error popups when I login to my account ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jul 26 15:35:16 2018 ErrorMessage: installed console-setup package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2017-06-15 (414 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, 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 apt 1.6.3 SourcePackage: console-setup Title: package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (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 console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1785324 Title: error popups when I login to my account Status in console-setup package in Ubuntu: New Bug description: error popups when I login to my account ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jul 26 15:35:16 2018 ErrorMessage: installed console-setup package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2017-06-15 (414 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, 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 apt 1.6.3 SourcePackage: console-setup Title: package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1785324/+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 1777070] Re: firefox plugin libwidevinecdm.so crashes due to apparmor denial
I think we're going to need more information on how this plugin got in
there in the first place. Being able to map a library in a user-writable
directory doesn't sound terribly safe...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1777070
Title:
firefox plugin libwidevinecdm.so crashes due to apparmor denial
Status in apparmor package in Ubuntu:
New
Status in firefox package in Ubuntu:
New
Bug description:
Ubuntu 18.04, Firefox 60.0.1+build2-0ubuntu0.18.04.1
Running firefix, then going to netflix.com and attempting to play a
movie. The widevinecdm plugin crashes, the following is found in
syslog:
Jun 15 19:13:22 xplt kernel: [301351.553043] audit: type=1400
audit(1529046802.585:246): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16118 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:22 xplt kernel: [301351.553236] audit: type=1400
audit(1529046802.585:247): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
Jun 15 19:13:22 xplt kernel: [301351.553259] plugin-containe[16118]: segfault
at 0 ip 7fcdfdaa76af sp 7ffc1ff03e28 error 6 in
libxul.so[7fcdfb77a000+6111000]
Jun 15 19:13:22 xplt snmpd[2334]: error on subcontainer 'ia_addr' insert (-1)
Jun 15 19:13:22 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!!
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
Jun 15 19:13:24 xplt kernel: [301353.960182] audit: type=1400
audit(1529046804.994:248): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16135 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:24 xplt kernel: [301353.960373] audit: type=1400
audit(1529046804.994:249): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
Jun 15 19:13:24 xplt kernel: [301353.960398] plugin-containe[16135]: segfault
at 0 ip 7fe3b57f46af sp 7ffe6dc0b488 error 6 in
libxul.so[7fe3b34c7000+6111000]
Jun 15 19:13:28 xplt kernel: [301357.859177] audit: type=1400
audit(1529046808.895:250): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16139 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:28 xplt kernel: [301357.859328] audit: type=1400
audit(1529046808.895:251): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
Jun 15 19:13:28 xplt kernel: [301357.859349] plugin-containe[16139]: segfault
at 0 ip 7fcf32ae06af sp 7ffeb8a136c8 error 6 in
libxul.so[7fcf307b3000+6111000]
Jun 15 19:13:25 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!!
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
Jun 15 19:13:29 xplt /usr/lib/gdm3/gdm-x-session[6549]: ERROR block_reap:328:
[hamster] bad exit code 1
Jun 15 19:13:29 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!!
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
Jun 15 19:13:29 xplt kernel: [301358.227635] audit: type=1400
audit(1529046809.263:252): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16188 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:29 xplt kernel: [301358.227811] audit: type=1400
audit(1529046809.263:253): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
Jun 15 19:13:29 xplt kernel: [301358.227844] plugin-containe[16188]: segfault
at 0 ip 7fe5667c66af sp 7fffe8cc0da8 error 6 in
libxul.so[7fe564499000+6111000]
Jun 15 19:13:31 xplt kernel: [301360.574177] audit: type=1400
audit(1529046811.608:254): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
[Touch-packages] [Bug 1575438] Re: usr.sbin.nscd needs r/w access to nslcd socket
An update to the "ldapclient" abstraction has been merged upstream:
https://gitlab.com/apparmor/apparmor/merge_requests/153/diffs?commit_id=ac1d0545f458b11728f2bcb4a7de0567538fa94a
** Changed in: apparmor
Status: New => Fix Committed
** Changed in: apparmor (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1575438
Title:
usr.sbin.nscd needs r/w access to nslcd socket
Status in AppArmor:
Fix Committed
Status in apparmor package in Ubuntu:
Fix Committed
Bug description:
I am usinc nscd with nslcd (LDAP lookup daemon) for NSS services via
LDAP.
It is typical to configure nslcd to connect to the actual LDAP server,
and then set up /etc/ldap.conf (which is what NSS/nscd uses for "ldap"
type lookups in /etc/nsswitch.conf) with a server URI of
ldapi:///var/run/nslcd/socket . This way, only nslcd needs to talk
with the LDAP server, rather than every application that wants to do
getpwent() et al.
Unfortunately, the usr.sbin.nscd profile in apparmor-profiles
2.10.95-0ubuntu2 (Xenial) makes no mention of the nslcd socket, which
results in NSS LDAP lookups not working when the profile is enforced
in this configuration.
This is the new line that is needed:
/{,var/}run/nslcd/socket rw,
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1575438/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
@hnasarat, can I set up two DNS servers this way? -- 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/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: [Triage Notes] Apparently fixed on Ubuntu 17.04, nobody caring about LTS versions. Please see wall of text on comment 50 for a long excuse. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594
Apologies for double-posting. Some additional info that may be helpful.
Paste from /var/crash/_usr_bin_compiz.1000.crash:
//BEGIN CODE PASTE//
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Thu Jul 26 22:13:47 2018
DistroRelease: Ubuntu 16.04
ExecutablePath: /usr/bin/compiz
SegvAnalysis:
Segfault happened at: 0x7f19500522c9:movdqu (%r8,%rbx,1),%xmm9
PC (0x7f19500522c9) ok
source "(%r8,%rbx,1)" (0x0320) not located in a known VMA region (needed
readable region)!
destination "%xmm9" ok
SegvReason: reading NULL VMA
SourcePackage: compiz
Stacktrace:
#0 0x7f19500522c9 in ?? ()
No symbol table info available.
#1 0x in ?? ()
No symbol table info available.
StacktraceTop:
?? ()
?? ()
Tags: xenial xenial ubuntu compiz-0.9
ThreadStacktrace:
.
Thread 6 (Thread 0x7f19297bc700 (LWP 2252)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f1956c7dcfa in g_cond_wait_until () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7f1956c0d999 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3 0x7f1956c0dfbb in g_async_queue_timeout_pop () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f1956c6060a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0x7f1956c5fbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#6 0x7f19565ca6ba in start_thread (arg=0x7f19297bc700) at
pthread_create.c:333
__res =
pd = 0x7f19297bc700
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139746046887680,
2698625152003350009, 0, 140732259479199, 139746046888384, 139746491836624,
-2647795865437594119, -2647591021518381575}, mask_was_saved = 0}}, priv = {pad
= {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
pagesize_m1 =
sp =
freesize =
__PRETTY_FUNCTION__ = "start_thread"
#7 0x7f195841641d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
No locals.
.
Thread 5 (Thread 0x7f1942859700 (LWP 2244)):
#0 pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
No locals.
#1 0x7f194343670b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
No symbol table info available.
#2 0x7f1943436427 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
No symbol table info available.
#3 0x7f19565ca6ba in start_thread (arg=0x7f1942859700) at
pthread_create.c:333
__res =
pd = 0x7f1942859700
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139746466961152,
2698625152003350009, 0, 140732259485039, 139746466961856, 0,
-2647566498614731271, -2647591021518381575}, mask_was_saved = 0}}, priv = {pad
= {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
pagesize_m1 =
sp =
freesize =
//END CODE PASTE//
(Log continues, but it more-or-less repeats itself.)
Paste from /var/log/syslog (starting from first instance of the segfault):
//BEGIN CODE PASTE//
Jul 27 18:30:19 HAPPY kernel: [ 669.687946] compiz[2543]: segfault at 738 ip
7f813c01c2c9 sp 7fff02f61ea0 error 4
Jul 27 18:30:20 HAPPY gnome-session[2156]: (unity-fallback-mount-helper:2488):
GLib-GIO-CRITICAL **: g_dbus_proxy_call_finish_internal: assertion
'G_IS_DBUS_PROXY (proxy)' failed
Jul 27 18:30:20 HAPPY gnome-session[2156]: (unity-fallback-mount-helper:2488):
GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed
Jul 27 18:30:20 HAPPY gnome-session[2156]: (unity-fallback-mount-helper:2488):
GLib-CRITICAL **: g_variant_unref: assertion 'value != NULL' failed
Jul 27 18:30:20 HAPPY gnome-session[2156]: **
(unity-fallback-mount-helper:2488): WARNING **: Can't call IsLocked() on the
Unity.Session object: Cannot invoke method; proxy is for a well-known name
without an owner and proxy was constructed with the
G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Jul 27 18:30:21 HAPPY org.gnome.zeitgeist.Engine[2019]: **
(zeitgeist-datahub:2766): WARNING **: zeitgeist-datahub.vala:229: Unable to get
name "org.gnome.zeitgeist.datahub" on the bus!
Jul 27 18:30:23 HAPPY kernel: [ 673.386286] compiz[2740]: segfault at 328 ip
7fbb600272c9 sp 7ffc75bf8da0 error 4
Jul 27 18:30:23 HAPPY gnome-session[2156]: **
(unity-fallback-mount-helper:2488): WARNING **: Can't call IsLocked() on the
Unity.Session object: Cannot invoke method; proxy is for a well-known name
without an owner and proxy was constructed with the
G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
//END CODE PASTE//
--
You received this bug notification because you are a member of Ubuntu
[Touch-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 I can confirm I have what I believe to be this bug in 16.04. All packages updated to current. Have also downloaded latest 16.04 LTS release .iso and run it off a USB drive. Same symptoms. Originally, the issue was confined to Firefox, which crashed on many websites. The error related to "r300_dri.so". I disabled WebGL and this fixed the problem. However, as of mid-July, I have the same problems as other users (flashing icons at login, etc.). My logs tell me I installed a mesa update on 15/07/18. Acer 5100 Ubuntu 16.04 (64-bit) Graphics card: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] I have tried to force a version downgrade of libgl1-mesa-dri in Synaptic, but the only option it gives me is a really old version - I just want to roll back to, say, February. Newbie, so don't want to play around too much and break stuff. Many thanks to the developers - hopefully you can help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in Mesa: New Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental:
[Touch-packages] [Bug 1785301] [NEW] background
Public bug reported: Why did you change the perfect and different Deskback background colours and picture adaptility of 16.04. This way in 18.04 i can't use my pictures and walpapers on Deskback. Which way can i go? best wishes werner ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Aug 3 20:34:30 2018 DistUpgraded: 2018-07-31 12:22:21,445 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF119 [GeForce GT 610] [10de:0915] InstallationDate: Installed on 2016-11-03 (638 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ECT To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=0de38eb8-8ba1-46ef-8ccb-e03e1a3e4305 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-07-31 (3 days ago) dmi.bios.date: 06/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd06/15/2012:svnECT:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: ECT version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 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 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Tue Jul 31 11:28:25 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: nouveau ** 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/1785301 Title: background Status in xorg package in Ubuntu: New Bug description: Why did you change the perfect and different Deskback background colours and picture adaptility of 16.04. This way in 18.04 i can't use my pictures and walpapers on Deskback. Which way can i go? best wishes werner ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Aug 3 20:34:30 2018 DistUpgraded: 2018-07-31 12:22:21,445 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF119 [GeForce GT 610] [10de:0915] InstallationDate: Installed on 2016-11-03 (638 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ECT To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic
[Touch-packages] [Bug 1785302] [NEW] rsync -a should imply -X
Public bug reported:
As discussed at https://lists.ubuntu.com/archives/ubuntu-
devel/2018-August/040407.html ff, as of Ubuntu 18.04 an Ubuntu root
filesystem uses xattrs for storing filesystem capabilities. We should
therefore have defaults for our rsync that preserve these attributes
without needing to pass additional commandline options.
Currently the rsync -a ("archive") option is documented as preserving
symlinks (-l), permissions (-p), modification times (-t), groups (-g),
owners (-u), and special files (-D); but not hardlinks (-H), acls (-A),
or xattrs (-X). I haven't looked into the reasoning, but I expect it's
because the first set of options can be assumed supported on a target
POSIX-ish filesystem, and the latter are not guaranteed to be supported
on all POSIX-ish filesystems (although POSIX does require hardlink
support). On Ubuntu, and on modern Linux generally, it should be safe
to assume that any POSIX filesystem currently in use that supports Unix
permissions and special files also supports acls and xattrs. (Linux
filesystems known to support them: ext4, xfs, jfs, zfs, btrfs.)
Without having looked closely at the implementation, I think a sensible
approach on Ubuntu would be:
- rsync when sending should interpret '-a' to include '-A' and '-X' and send
acls and xattrs as part of the stream.
- if sending to a remote server that doesn't negotiate a protocol high
enough to handle acls and xattrs, do not consider this an error.
- rsync when receiving xattrs and acls appears to already ignore failures to
set them, so no changes would be required for compatibility.
** Affects: rsync (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1785302
Title:
rsync -a should imply -X
Status in rsync package in Ubuntu:
New
Bug description:
As discussed at https://lists.ubuntu.com/archives/ubuntu-
devel/2018-August/040407.html ff, as of Ubuntu 18.04 an Ubuntu root
filesystem uses xattrs for storing filesystem capabilities. We should
therefore have defaults for our rsync that preserve these attributes
without needing to pass additional commandline options.
Currently the rsync -a ("archive") option is documented as preserving
symlinks (-l), permissions (-p), modification times (-t), groups (-g),
owners (-u), and special files (-D); but not hardlinks (-H), acls
(-A), or xattrs (-X). I haven't looked into the reasoning, but I
expect it's because the first set of options can be assumed supported
on a target POSIX-ish filesystem, and the latter are not guaranteed to
be supported on all POSIX-ish filesystems (although POSIX does require
hardlink support). On Ubuntu, and on modern Linux generally, it
should be safe to assume that any POSIX filesystem currently in use
that supports Unix permissions and special files also supports acls
and xattrs. (Linux filesystems known to support them: ext4, xfs, jfs,
zfs, btrfs.)
Without having looked closely at the implementation, I think a
sensible approach on Ubuntu would be:
- rsync when sending should interpret '-a' to include '-A' and '-X' and send
acls and xattrs as part of the stream.
- if sending to a remote server that doesn't negotiate a protocol high
enough to handle acls and xattrs, do not consider this an error.
- rsync when receiving xattrs and acls appears to already ignore failures to
set them, so no changes would be required for compatibility.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1785302/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
** Tags added: trusty xenial ** Tags added: bionic ** Tags added: cosmic -- 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/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: [Triage Notes] Apparently fixed on Ubuntu 17.04, nobody caring about LTS versions. Please see wall of text on comment 50 for a long excuse. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1785296] Re: package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1785296 Title: package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: No further information available. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.20 ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-24-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Aug 3 12:24:15 2018 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-16 (259 days ago) InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed post-installation script 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/1785296/+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 1785296] [NEW] package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: No further information available. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.20 ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-24-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Aug 3 12:24:15 2018 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-16 (259 days ago) InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed post-installation script 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 xenial -- 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/1785296 Title: package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: No further information available. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.20 ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-24-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Aug 3 12:24:15 2018 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-16 (259 days ago) InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed post-installation script 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/1785296/+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 1785052] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1785052 Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: Confirmed Bug description: The error appeared on reboot after update from 16.04 to 18.04 During the version update something went wrong. A message about systemd-sysv 237-3ubuntu10.3 appeared, with the additional info that the system could be instable and that the tool will run a "dpkgsomethingelse -a". I launched the update software and i see a notification that asserts that is not possible to install all updates and invite to run a partial update. Partial version update -> 1 package is going to be removed -> systemd-shim - shim for systemd Then: Could not install 'systemd-shim' The upgrade will continue but the 'systemd-shim' package may not be in a working state. Please consider submitting a bug report about it. installed systemd-shim package post-removal script subprocess returned error exit status 2 FIX THAT WORKED FOR ME: -- cd /usr/share/dbus-1/system-services/ sudo mv org.freedesktop.systemd1.service org.freedesktop.systemd1.service.bak Then Run Update -> Run Partial Upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Aug 2 11:21:11 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2013-11-09 (1726 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, 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 apt 1.6.3 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-08-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1785052/+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 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in apparmor source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in apparmor source package in Bionic: Invalid Status in linux source package in Bionic: Fix Committed Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+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 1785291] [NEW] tar --xattr and --xattr-include=* should be defaults
Public bug reported: As discussed at https://lists.ubuntu.com/archives/ubuntu- devel/2018-August/040407.html ff, as of Ubuntu 18.04 an Ubuntu root filesystem uses xattrs for storing filesystem capabilities. We should therefore have defaults for our tar that preserve these attributes without needing to pass additional commandline options. Currently when creating a tarball you must pass the non-default option --xattrs and when extracting a tarball you must pass the non-default option --xattrs-include=*. The latter is particularly awkward, and Colin Watson found some version of tar documentation that suggests --xattrs-include=* should never be needed, only --xattrs. But that doesn't appear in the version of tar(1) in bionic, and in practice --xattrs-include=* is definitely required. Ideally we want this changed in upstream tar as well since we can't rely on users using the Ubuntu build of tar to unpack their Ubuntu filesystems; but even without this we should change the default in Ubuntu to take the sharp edges off for our users where possible. ** Affects: tar (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1785291 Title: tar --xattr and --xattr-include=* should be defaults Status in tar package in Ubuntu: New Bug description: As discussed at https://lists.ubuntu.com/archives/ubuntu- devel/2018-August/040407.html ff, as of Ubuntu 18.04 an Ubuntu root filesystem uses xattrs for storing filesystem capabilities. We should therefore have defaults for our tar that preserve these attributes without needing to pass additional commandline options. Currently when creating a tarball you must pass the non-default option --xattrs and when extracting a tarball you must pass the non-default option --xattrs-include=*. The latter is particularly awkward, and Colin Watson found some version of tar documentation that suggests --xattrs-include=* should never be needed, only --xattrs. But that doesn't appear in the version of tar(1) in bionic, and in practice --xattrs-include=* is definitely required. Ideally we want this changed in upstream tar as well since we can't rely on users using the Ubuntu build of tar to unpack their Ubuntu filesystems; but even without this we should change the default in Ubuntu to take the sharp edges off for our users where possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1785291/+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 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
I just did a clean install of Xubuntu 18.04.1 and then installed gdebi and its frontend. The interface crashes for me so it hasn't been fixed. The back-end might work from the command line but the gui is broken. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1756238 Title: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags Status in gdebi package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Bionic: Fix Released Bug description: When using gdebi-gtk to install a .deb the install fails with the message:- dpkg: error: unable to read filedescriptor flags for : Bad file descriptor This only occurs via the gdebi-gtk GUI front end, packages install perfectly if done via the CLI with: sudo gdebi /path/to/packagename.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1756238/+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 1780996] Re: Convert triggers to noawait
Hello Julian, or anyone else affected, Accepted libreoffice into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:5.1.6~rc2-0ubuntu1~xenial4 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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! ** Changed in: libreoffice (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in django-countries package in Ubuntu: Fix Released Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: Fix Released Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: Won't Fix Status in guile-2.0 package in Ubuntu: Fix Released Status in guile-2.2 package in Ubuntu: Fix Released Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: Triaged Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: Fix Released Status in neurodebian package in Ubuntu: Fix Released Status in nevow package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: Fix Released Status in pike8.0 package in Ubuntu: Fix Released Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: Won't Fix Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: Fix Released Status in bumblebee source package in Xenial: Fix Released Status in clutter-imcontext source package in Xenial: Won't Fix Status in django-countries source package in Xenial: Fix Released Status in dochelp source package in Xenial: Fix Released Status in dovecot source package in Xenial: Fix Released Status in fusiondirectory source package in Xenial: Fix Released Status in gdk-pixbuf source package in Xenial: Fix Released Status in glib2.0 source package in Xenial: Fix Released Status in gosa source package in Xenial: Won't Fix Status in guile-2.0 source package in Xenial: Fix Released Status in hicolor-icon-theme source package in Xenial: Fix Released Status in libomxil-bellagio source package in Xenial: Triaged Status in libreoffice source package in Xenial: Fix Committed Status in ltsp source package in Xenial: Fix Released Status in mate-icon-theme source package in Xenial: Fix Released Status in maxima source package in Xenial: Fix Committed Status in neurodebian source package in Xenial: Fix Released Status in nevow source package in Xenial: Fix Released Status in octave source package in Xenial: Fix Released Status in packagekit source package in Xenial: Fix Released Status in pike7.8 source package in Xenial: Fix Released Status in pike8.0 source package in Xenial: Fix Released Status in postgresql-common source package in Xenial: Fix Released Status in qgis source package in Xenial: Fix Released Status in reconf-inetd source package in Xenial: Won't Fix Status in shared-mime-info source package in Xenial: Fix Released Status in sphinx source package in Xenial: Fix Released Status in syslog-ng-incubator source package in Xenial: Fix
[Touch-packages] [Bug 1622730] Re: No sound on headphones after suspend
Did you try the workaround posted on 2016-12-19? You may have to add modules i2c_dev and i2c_i801 before running init-headphone: sudo modprobe --first-time i2c_dev sudo modprobe --first-time i2c_i801 -- 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/1622730 Title: No sound on headphones after suspend Status in alsa-driver package in Ubuntu: Confirmed Bug description: This seems to be a common problem on XMG Clevo W230SS there is no output on the headphone jack after suspend. The headphones are detected and the speakers are muted, but there is no output to the headphones. Init-headphones does not help: sudo init-headphone WARNING:root:Kernel parameter is missing: acpi_enforce_resources=lax WARNING:root:Module is not loaded: i2c_dev ERROR:root:Can't find i2c bus ERROR:root:Operation failed Any workaround beside reboot? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: pia 23276 F pulseaudio /dev/snd/controlC0: pia 23276 F pulseaudio CurrentDesktop: GNOME-Classic:GNOME Date: Mon Sep 12 21:56:08 2016 InstallationDate: Installed on 2015-11-05 (312 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-02-15T00:43:38.504815 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1622730/+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 1618870] Re: package gpgv 1.4.20-1ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnupg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1618870 Title: package gpgv 1.4.20-1ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gnupg package in Ubuntu: Confirmed Bug description: ... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gpgv 1.4.20-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: gpgv: Configure gnupg: Install gnupg: Configure NULL: ConfigurePending Architecture: amd64 Date: Wed Aug 24 22:11:19 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libbz2-1.0 1.0.6-8 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 zlib1g 1:1.2.8.dfsg-2ubuntu4 DpkgTerminalLog: dpkg: error processing package gpgv (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-08-12 (19 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: gnupg Title: package gpgv 1.4.20-1ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1618870/+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 1785273] [NEW] Problem installing Intel drivers
Public bug reported: I'm trying to install intel drivers in ubuntu and and that error shows up ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Aug 3 16:40:50 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07e1] Subsystem: Dell Device [1028:07e1] InstallationDate: Installed on 2018-08-03 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Dell Inc. Inspiron 5577 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=e78f51c6-fb02-4b78-b42a-e180057b2edc ro nomodeset vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.9 dmi.board.name: 090HMC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.9:bd01/25/2018:svnDellInc.:pnInspiron5577:pvr1.0.9:rvnDellInc.:rn090HMC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.version: 1.0.9 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Aug 3 16:33:27 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4~16.04.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1785273 Title: Problem installing Intel drivers Status in xorg package in Ubuntu: New Bug description: I'm trying to install intel drivers in ubuntu and and that error shows up ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Aug 3 16:40:50 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07e1] Subsystem: Dell Device [1028:07e1] InstallationDate: Installed on 2018-08-03 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Dell Inc. Inspiron 5577 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=e78f51c6-fb02-4b78-b42a-e180057b2edc ro nomodeset vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.9 dmi.board.name: 090HMC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias:
[Touch-packages] [Bug 1667725] Re: [feature request] make full ppa signing public key available over https
** Changed in: software-properties (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1667725
Title:
[feature request] make full ppa signing public key available over
https
Status in Launchpad itself:
Fix Released
Status in software-properties package in Ubuntu:
In Progress
Bug description:
Currently, for a ppa, launchpad makes the long key fingerprint
available over https. I'd like to request that it also make the full
public key available over https.
Many people use add-apt-repository extensively for using ppas ('add-
apt-repository -y smoser/archive')
As I understand it, that basically does:
a. request the 'archive urls', 'description' and long key fingerprint over
https from launchpad.net
b. does gpg --recv from
hkp://keyserver.ubuntu.com:80/ (or the --keyserver argument)
c. adds the result of 'b' to apt using 'apt-key'
Since launchpad is the owner of the signing key for the ppa, why not
have it just give us the full public key over the same api that it
provides the other bits of information?
My experience is that gpg servers are less reliable than we'd like,
and even if they were as reliable as launchpad, any use of a ppa now
effectively depends on 2 external systems when 1 could suffice.
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1667725/+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 1667725] Re: [feature request] make full ppa signing public key available over https
** Branch linked: lp:software-properties
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1667725
Title:
[feature request] make full ppa signing public key available over
https
Status in Launchpad itself:
Fix Released
Status in software-properties package in Ubuntu:
In Progress
Bug description:
Currently, for a ppa, launchpad makes the long key fingerprint
available over https. I'd like to request that it also make the full
public key available over https.
Many people use add-apt-repository extensively for using ppas ('add-
apt-repository -y smoser/archive')
As I understand it, that basically does:
a. request the 'archive urls', 'description' and long key fingerprint over
https from launchpad.net
b. does gpg --recv from
hkp://keyserver.ubuntu.com:80/ (or the --keyserver argument)
c. adds the result of 'b' to apt using 'apt-key'
Since launchpad is the owner of the signing key for the ppa, why not
have it just give us the full public key over the same api that it
provides the other bits of information?
My experience is that gpg servers are less reliable than we'd like,
and even if they were as reliable as launchpad, any use of a ppa now
effectively depends on 2 external systems when 1 could suffice.
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1667725/+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 1785259] Re: Graphics card hangs after suspend
I will also note this issue is present regardless of ubuntu based distro. -- 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/1785259 Title: Graphics card hangs after suspend Status in xorg package in Ubuntu: New Bug description: OS: pop!_OS 18.04 LTS x86_64 Kernal: 4.15.0-29-generic DE/WM: Gnome CPU: Ryzen 7 GPU: RX580 also issue exists when I use my 1070 Memory; 32GB My system hangs after suspending either I will have to pull the HDMI and put it back in to resolve the issue or reboot the system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1785259/+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 1785259] [NEW] Graphics card hangs after suspend
Public bug reported: OS: pop!_OS 18.04 LTS x86_64 Kernal: 4.15.0-29-generic DE/WM: Gnome CPU: Ryzen 7 GPU: RX580 also issue exists when I use my 1070 Memory; 32GB My system hangs after suspending either I will have to pull the HDMI and put it back in to resolve the issue or reboot the system. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1785259 Title: Graphics card hangs after suspend Status in xorg package in Ubuntu: New Bug description: OS: pop!_OS 18.04 LTS x86_64 Kernal: 4.15.0-29-generic DE/WM: Gnome CPU: Ryzen 7 GPU: RX580 also issue exists when I use my 1070 Memory; 32GB My system hangs after suspending either I will have to pull the HDMI and put it back in to resolve the issue or reboot the system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1785259/+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 1759271] Re: Xorg freeze
** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1759271 Title: Xorg freeze Status in xorg package in Ubuntu: Invalid Bug description: Hello, I already had a freezing problem whith my computer that i resolved this way: Ubuntu 16&17 don't stop. Toshiba C50 B 19H [SOLVED] but, now i just had another freeze will the computer working (not during shutdown). I hope you can fix the problem or help me, Thanks, Thomas. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Mar 27 15:13:35 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1179:f910] InstallationDate: Installed on 2018-03-26 (1 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: TOSHIBA SATELLITE C50-B ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=385e28ce-7be5-4689-b130-a0b80a6af38c ro quiet splash intel_idle.max_cstate=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: 5.10 dmi.board.asset.tag: * dmi.board.name: ZBWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr5.10:bd08/10/2015:svnTOSHIBA:pnSATELLITEC50-B:pvrPSCMLE-09100FFR:rvnTOSHIBA:rnZBWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: SATELLITE C50-B dmi.product.version: PSCMLE-09100FFR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Mar 27 15:09:36 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1759271/+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 1771353] Re: Server feature level is now lower than when we began our transaction. Restarting with new ID
On 3 August 2018 at 14:22, Steve Dodd <1771...@bugs.launchpad.net> wrote: > @xnox: > > Yes, on further investigation it looks like these might well be > different bugs - OTOH the repeated issuance of queries to the upstream > server, and the confusion about the server capabilities is very similar, > which suggests a problem in the same code path may be being triggered. I > will create a new bug once I am sure they are different. > Yeah, a lot of those debug output from resolved is just that debug output, and it looks very similar for even regular normal operations. E.g. the dns server on router is crap and I have transactions restarting, lowering the supported level, then later it attempts to up the supported level again only go back down again... So restarting of transactions and changing ids is "normal" as it's simply "verbose". > Re. libnss-resolve, the man page still says: > > "it is strongly recommended that local programs use the glibc NSS or bus > APIs instead [of the stub resolver]" > That sounds like it predates implementation of stub-resolv.conf generator with search stanzas and other improvements to the local stub listener for large query sizes. > But I do understand there are potential issues - might be nice to have > the Ubuntu "position" documented (top of resolv.conf, perhaps). > I'm working on a blog post series / wiki page, and a talk for FOSDEM about it. But it has been going slow... > Simon Kelley is looking at the dnsmasq issues. > cool! -- Regards, Dimitri. -- 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/1771353 Title: Server feature level is now lower than when we began our transaction. Restarting with new ID Status in systemd package in Ubuntu: Confirmed Bug description: systemd 237-3ubuntu10 from bionic There is no /etc/netplan/* file. I'm getting some sort of a loop when systemd-resolved tries to resolve the hostname of my canonistack instance: ubuntu@bip:~$ systemd-resolve bip.lcy02.canonistack bip.lcy02.canonistack: resolve call failed: All attempts to contact name servers or networks failed systemd-resolved debug output loops over like this: Transaction 36341 is now 19121. Cache miss for bip.lcy02.canonistack IN A Transaction 19121 for scope dns on */*. Using feature level UDP+EDNS0 for transaction 19121. Sending query packet with id 19121. Processing incoming packet on transaction 19121. (rcode=SUCCESS) Server feature level is now lower than when we began our transaction. Restarting with new ID. Transaction 19121 is now 17157. Cache miss for bip.lcy02.canonistack IN A Transaction 17157 for scope dns on */*. Using feature level UDP+EDNS0 for transaction 17157. Sending query packet with id 17157. Processing incoming packet on transaction 17157. (rcode=SUCCESS) Server feature level is now lower than when we began our transaction. Restarting with new ID. ... Packet capture shows a loop like this: 13:38:32.293524 IP 10.55.32.54.53786 > 10.55.32.1.53: 46096+ [1au] A? bip.lcy02.canonistack. (50) 13:38:32.293753 IP 10.55.32.1.53 > 10.55.32.54.53786: 46096* 1/0/0 A 10.55.32.54 (55) 13:38:32.294026 IP 10.55.32.54.53786 > 10.55.32.1.53: 64494+ [1au] A? bip.lcy02.canonistack. (50) 13:38:32.294249 IP 10.55.32.1.53 > 10.55.32.54.53786: 64494* 1/0/0 A 10.55.32.54 (55) I'm going to attach the full debug output, and the pcap file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771353/+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 879902] Re: Increase the number of inotify watches
I am still affected by this in 2018. Any plans to increase the number? It is 8192 in Ubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/879902 Title: Increase the number of inotify watches Status in procps package in Ubuntu: Confirmed Bug description: Many of the problems I encountered seem to be related to a single issue : the maximum number of watches inotify is able to handle. I have found that the default maximum number of watches is way to low too handle every feature using inotify, a default Ubuntu uses a great number of watches out of the box and in Natty and Oneiric it starts to become a real problem. Possible effects are : - Ubuntu One not syncing correctly - Nautilus not updating itself when a file is created or deleted. - Audio players not updating music libraries - tail -f or other programs using inotify show a cryptic message about no space being left on the device (while there's plenty of space) I have found that simply doubling the maximum of watches *is not enough* for a normal use, and if I believe this comment : https://bugs.launchpad.net/ubuntu/+source/beagle/+bug/115801/comments/4 there is no problem to setting the number of watches to a high value. My current setting is 524288, which is 64 times the default value, It may be too high for a default value but I believe that 65536 or 131072 should be enough for almost everyone. If Precise Pangolin wants to be predictable, this issues *has* to be addressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/879902/+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 1775018] Re: Fix for openssl 1.0.2 backport
yeah -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1775018 Title: Fix for openssl 1.0.2 backport Status in Ubuntu on IBM z Systems: Triaged Status in openssl package in Ubuntu: New Bug description: This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and upstream code are not affected ). Original LP ticket : https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775018/+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 1771353] Re: Server feature level is now lower than when we began our transaction. Restarting with new ID
@xnox: Yes, on further investigation it looks like these might well be different bugs - OTOH the repeated issuance of queries to the upstream server, and the confusion about the server capabilities is very similar, which suggests a problem in the same code path may be being triggered. I will create a new bug once I am sure they are different. Re. libnss-resolve, the man page still says: "it is strongly recommended that local programs use the glibc NSS or bus APIs instead [of the stub resolver]" But I do understand there are potential issues - might be nice to have the Ubuntu "position" documented (top of resolv.conf, perhaps). Simon Kelley is looking at the dnsmasq issues. -- 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/1771353 Title: Server feature level is now lower than when we began our transaction. Restarting with new ID Status in systemd package in Ubuntu: Confirmed Bug description: systemd 237-3ubuntu10 from bionic There is no /etc/netplan/* file. I'm getting some sort of a loop when systemd-resolved tries to resolve the hostname of my canonistack instance: ubuntu@bip:~$ systemd-resolve bip.lcy02.canonistack bip.lcy02.canonistack: resolve call failed: All attempts to contact name servers or networks failed systemd-resolved debug output loops over like this: Transaction 36341 is now 19121. Cache miss for bip.lcy02.canonistack IN A Transaction 19121 for scope dns on */*. Using feature level UDP+EDNS0 for transaction 19121. Sending query packet with id 19121. Processing incoming packet on transaction 19121. (rcode=SUCCESS) Server feature level is now lower than when we began our transaction. Restarting with new ID. Transaction 19121 is now 17157. Cache miss for bip.lcy02.canonistack IN A Transaction 17157 for scope dns on */*. Using feature level UDP+EDNS0 for transaction 17157. Sending query packet with id 17157. Processing incoming packet on transaction 17157. (rcode=SUCCESS) Server feature level is now lower than when we began our transaction. Restarting with new ID. ... Packet capture shows a loop like this: 13:38:32.293524 IP 10.55.32.54.53786 > 10.55.32.1.53: 46096+ [1au] A? bip.lcy02.canonistack. (50) 13:38:32.293753 IP 10.55.32.1.53 > 10.55.32.54.53786: 46096* 1/0/0 A 10.55.32.54 (55) 13:38:32.294026 IP 10.55.32.54.53786 > 10.55.32.1.53: 64494+ [1au] A? bip.lcy02.canonistack. (50) 13:38:32.294249 IP 10.55.32.1.53 > 10.55.32.54.53786: 64494* 1/0/0 A 10.55.32.54 (55) I'm going to attach the full debug output, and the pcap file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771353/+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 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck
Thank you for working on this. I agree with your approach. The debdiff
looks good.
I think that though it's clear that the bug is in the host command,
given that we haven't been able to figure out the fix (I spent some time
on it too), it's reasonable to add the timeout command as in your patch
as a workaround. No need for the problem to persist when the workaround
is so clean and clear. I also approve the timeout workaround for SRU in
principle. We can leave a bug task open for bind, but consider a
separate bug task resolved in avahi packaging once this workaround is
applied.
A couple of comments from your current debdiff:
Please leave a comment above the timeout line explaining why it is there
("Workaround for LP: #1752411" is sufficient). For the SRU, I would
prefer a version string of "0.7-3.1ubuntu1.1" ("0.7-3.1ubuntu2" is
technically OK but doesn't convey that it is an SRU so well).
Please could you prepare a debdiff for Cosmic so that we can fix it
there first? Then follow
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure and attach an
updated debdiff for the SRU to Bionic. I'll be happy to sponsor both,
but will then need review from another SRU team member to accept it from
the queue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1752411
Title:
bind9-host, avahi-daemon-check-dns.sh hang forever causes network
connections to get stuck
Status in avahi package in Ubuntu:
Confirmed
Status in bind9 package in Ubuntu:
Confirmed
Status in openconnect package in Ubuntu:
Invalid
Status in avahi package in Debian:
New
Bug description:
On 18.04 Openconnect connects successfully to any of multiple VPN
concentrators but network traffic does not flow across the VPN tunnel
connection. When testing on 16.04 this works flawlessly. This also
worked on this system when it was on 17.10.
I have tried reducing the mtu of the tun0 network device but this has
not resulted in me being able to successfully ping the IP address.
Example showing ping attempt to the IP of DNS server:
~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 172.29.88.11
nameserver 127.0.0.53
liam@liam-lat:~$ netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG0 0 0
wlp2s0
105.27.198.106 192.168.1.1 255.255.255.255 UGH 0 0 0
wlp2s0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
docker0
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0
docker0
172.29.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0
172.29.88.110.0.0.0 255.255.255.255 UH0 0 0 tun0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
wlp2s0
liam@liam-lat:~$ ping 172.29.88.11
PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data.
^C
--- 172.29.88.11 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3054ms
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: openconnect 7.08-3
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 28 22:11:33 2018
InstallationDate: Installed on 2017-06-15 (258 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
SourcePackage: openconnect
UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+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 1785154] Re: libsystemd-dev dependencies not satisfied
that would work too! -- 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/1785154 Title: libsystemd-dev dependencies not satisfied Status in systemd package in Ubuntu: Invalid Bug description: "Following packages lacks these dependencies: libsystemd-dev : Depends: libsystemd0 (= 237-3ubuntu10) but version 237-3ubuntu10.3 is going to be installed" ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libsystemd-dev (not installed) Uname: Linux 4.18.0-999-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 3 03:02:02 2018 InstallationDate: Installed on 2017-01-12 (567 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-07-24 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1785154/+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 1302192] Re: capabilities not preserved on installation
** Tags added: id-5b61e0dfee899a8671484afe -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1302192 Title: capabilities not preserved on installation Status in attr package in Ubuntu: Fix Released Status in iputils package in Ubuntu: Confirmed Status in live-installer package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: New Status in ubiquity package in Ubuntu: Fix Released Status in attr source package in Trusty: Fix Released Status in iputils source package in Trusty: Confirmed Status in live-installer source package in Trusty: Fix Released Status in ubiquity source package in Trusty: Fix Released Bug description: Ping is not longer setuid root and I have to ping as root: [~]$ ping kubuntu.org ping: icmp open socket: Operation not permitted [~]$ sudo ping kubuntu.org PING kubuntu.org (91.189.94.156) 56(84) bytes of data. 64 bytes from vostok.canonical.com (91.189.94.156): icmp_seq=1 ttl=51 time=52.2 ms --- kubuntu.org ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 52.231/52.231/52.231/0.000 ms [~]$ Related bugs: bug 1313550: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/attr/+bug/1302192/+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 1771353] Re: Server feature level is now lower than when we began our transaction. Restarting with new ID
@Steve Dodd libnss-resolve is not the upstream recommendation any more, and it doesn't work without dbus, with non-nss based applications or containers. by default, recent ubuntu releases use a local stub-resolver which does work more universally. See http://manpages.ubuntu.com/manpages/bionic/en/man8/systemd- resolved.8.html /etc/resolv.conf section the four modes of handling /etc/resolv.conf of which Ubuntu uses the first (default / recommended one) It seems to me, your issues is different to the original bug reporter, as the original bug reporter cannot resolve via $ systemd-resolve tool either, which is equivalnt to libnss-resolve. Please do not reuse somebody elses bug report for similar, but potentially different issues. And instead open a new bug report. Bug reports are cheap. -- 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/1771353 Title: Server feature level is now lower than when we began our transaction. Restarting with new ID Status in systemd package in Ubuntu: Confirmed Bug description: systemd 237-3ubuntu10 from bionic There is no /etc/netplan/* file. I'm getting some sort of a loop when systemd-resolved tries to resolve the hostname of my canonistack instance: ubuntu@bip:~$ systemd-resolve bip.lcy02.canonistack bip.lcy02.canonistack: resolve call failed: All attempts to contact name servers or networks failed systemd-resolved debug output loops over like this: Transaction 36341 is now 19121. Cache miss for bip.lcy02.canonistack IN A Transaction 19121 for scope dns on */*. Using feature level UDP+EDNS0 for transaction 19121. Sending query packet with id 19121. Processing incoming packet on transaction 19121. (rcode=SUCCESS) Server feature level is now lower than when we began our transaction. Restarting with new ID. Transaction 19121 is now 17157. Cache miss for bip.lcy02.canonistack IN A Transaction 17157 for scope dns on */*. Using feature level UDP+EDNS0 for transaction 17157. Sending query packet with id 17157. Processing incoming packet on transaction 17157. (rcode=SUCCESS) Server feature level is now lower than when we began our transaction. Restarting with new ID. ... Packet capture shows a loop like this: 13:38:32.293524 IP 10.55.32.54.53786 > 10.55.32.1.53: 46096+ [1au] A? bip.lcy02.canonistack. (50) 13:38:32.293753 IP 10.55.32.1.53 > 10.55.32.54.53786: 46096* 1/0/0 A 10.55.32.54 (55) 13:38:32.294026 IP 10.55.32.54.53786 > 10.55.32.1.53: 64494+ [1au] A? bip.lcy02.canonistack. (50) 13:38:32.294249 IP 10.55.32.1.53 > 10.55.32.54.53786: 64494* 1/0/0 A 10.55.32.54 (55) I'm going to attach the full debug output, and the pcap file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771353/+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 1781242] Re: as segfault with invalid -march= option
** Also affects: binutils (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 binutils in Ubuntu. https://bugs.launchpad.net/bugs/1781242 Title: as segfault with invalid -march= option Status in Ubuntu on IBM z Systems: Triaged Status in binutils package in Ubuntu: New Status in binutils source package in Xenial: New Bug description: The GNU assembler segfaults with an invalid -march= option Contact Information = n/a ---uname output--- n/a Machine Type = n/a ---Debugger--- A debugger is not configured ---Steps to Reproduce--- $ as -march=foo Segmentation fault Userspace tool common name: as The userspace tool has the following bit modes: 64 Userspace rpm: binutils-2.26.1-1ubuntu1~16.04.6 Userspace tool obtained from project website: na *Additional Instructions for n/a: -Attach ltrace and strace of userspace application. The problem is not critical since usually 'as' is invoked through the gcc driver which itself errors out for wrong -march= options. It will only be a problem if somebody builds a more recent GCC from source and uses an -march= option for a machine not supported by the default binutils. Please consider integrating the attached patch into 16.04 binutils. The problem has been fixed in later binutils already. Ubuntu 18.04 does not appear to be affected. --> Package has to set corectly by Canonical To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781242/+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 1780996] Re: Convert triggers to noawait
** Changed in: libreoffice (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in django-countries package in Ubuntu: Fix Released Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: Fix Released Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: Won't Fix Status in guile-2.0 package in Ubuntu: Fix Released Status in guile-2.2 package in Ubuntu: Fix Released Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: Triaged Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: Fix Released Status in neurodebian package in Ubuntu: Fix Released Status in nevow package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: Fix Released Status in pike8.0 package in Ubuntu: Fix Released Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: Won't Fix Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: Fix Released Status in bumblebee source package in Xenial: Fix Released Status in clutter-imcontext source package in Xenial: Won't Fix Status in django-countries source package in Xenial: Fix Released Status in dochelp source package in Xenial: Fix Released Status in dovecot source package in Xenial: Fix Released Status in fusiondirectory source package in Xenial: Fix Released Status in gdk-pixbuf source package in Xenial: Fix Released Status in glib2.0 source package in Xenial: Fix Released Status in gosa source package in Xenial: Won't Fix Status in guile-2.0 source package in Xenial: Fix Released Status in hicolor-icon-theme source package in Xenial: Fix Released Status in libomxil-bellagio source package in Xenial: Triaged Status in libreoffice source package in Xenial: In Progress Status in ltsp source package in Xenial: Fix Released Status in mate-icon-theme source package in Xenial: Fix Released Status in maxima source package in Xenial: Fix Committed Status in neurodebian source package in Xenial: Fix Released Status in nevow source package in Xenial: Fix Released Status in octave source package in Xenial: Fix Released Status in packagekit source package in Xenial: Fix Released Status in pike7.8 source package in Xenial: Fix Released Status in pike8.0 source package in Xenial: Fix Released Status in postgresql-common source package in Xenial: Fix Released Status in qgis source package in Xenial: Fix Released Status in reconf-inetd source package in Xenial: Won't Fix Status in shared-mime-info source package in Xenial: Fix Released Status in sphinx source package in Xenial: Fix Released Status in syslog-ng-incubator source package in Xenial: Fix Released Status in tex-common source package in Xenial: Fix Released Status in wokkel source package in Xenial: Fix Released Status in xpdf source package in Xenial: Fix Released Status in yorick source package in Xenial: Fix Released Status in appstream source package in Bionic: Fix Released Status in bumblebee source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in django-countries source package in Bionic: Fix Released Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in Bionic: Fix Released Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: Won't Fix Status in guile-2.0 source package in Bionic: Fix Released Status in guile-2.2 source package in Bionic: Fix Released Status in hicolor-icon-theme source package in Bionic: Fix Released
[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged
I face the same issue > # dpkg -l systemd > ... > ||/ Name VersionArchitectureDescription > +++-==-==-===-== > ii systemd237-3ubuntu10.3amd64 system and service manager > # networkctl > IDX LINK TYPE OPERATIONAL SETUP > 1 lo loopback carrier unmanaged > 2 ens3 ether routableconfiguring > 3 ens4 ether routableunmanaged > Aug 03 14:00:53 test-vm systemd-networkd-wait-online[4273]: Event loop failed: Connection timed out -- 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/1728181 Title: systemd-networkd-wait-online waits when devices are unmanaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: I started a system with cloud-init disabled, etc. and a single real network interface (ens3) that could be configured. That VM has no configuration whatsoever for systemd-networkd, as that would have to have been written by netplan, and cloud-init did not generate netplan config (because it was disabled). So: root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route d-networkd-wait-online --ignore=lo ignoring: lo Event loop failed: Connection timed out root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether off unmanaged 3 sit0 sitoff unmanaged 3 links listed. root@ubuntu:/etc/systemd/system/network-online.target.wants# The system took 120 seconds to complete boot, because wait-online had to finish; and running wait-online from the system afterwards also waits 120 seconds (its default timeout). If there is no configuration for an interface, it's unmanaged (as shown by networkctl), so wait-online should not wait, and simply report that all interfaces are unmanaged, possibly returning an error so we don't reach network-online. FWIW, having wait-online look up configuration might later be useful also to figure out if an interface was configured, but marked as optional (such that it is explicitly not required to be up at boot), or if we want to configure network devices but specify that networkd should *not* bring them online (like "administratively disabled" interfaces in Cisco world using the "shutdown" command). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+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 1785236] [NEW] "dm-tool add-nested-seat" doesn't work normally
Public bug reported: Hello, since I've installed Xubuntu 18-04 (on 15 july 2018). The command "dm-tool add-nested-seat" doesn't work normally. I have a blank screen instead of a login screen. Maybe the problem is due to greeter cause when I set autologin for an user, then everything seems to work normally. The login screen is just skipped. [Impact] "dm-tool add-nested-seat" doesn't work (excepted when autologin-user is set). [Test Case] 1. Log in 2. From a terminal run "dm-tool add-nested-seat" [Expected result] A window opens with a login screen [Observed result] A window opens with a complete black screen if autologin-user isn't set in /etc/lightdm/lightdm.conf No error in the terminal. If autologin is set in /etc/lightdm/lightdm.conf, then it works normally. [used distribution] Xubuntu 18-04, up to date. I didn't have this trouble in may 2018 while I was under Xubuntu 17-10. [related trouble] maybe it's related to this bug: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1529454 But I don't exactly have the same trouble. So I thought I should open a new one. Sorry if I was wrong. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: dm-tool lighdm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1785236 Title: "dm-tool add-nested-seat" doesn't work normally Status in lightdm package in Ubuntu: New Bug description: Hello, since I've installed Xubuntu 18-04 (on 15 july 2018). The command "dm-tool add-nested-seat" doesn't work normally. I have a blank screen instead of a login screen. Maybe the problem is due to greeter cause when I set autologin for an user, then everything seems to work normally. The login screen is just skipped. [Impact] "dm-tool add-nested-seat" doesn't work (excepted when autologin-user is set). [Test Case] 1. Log in 2. From a terminal run "dm-tool add-nested-seat" [Expected result] A window opens with a login screen [Observed result] A window opens with a complete black screen if autologin-user isn't set in /etc/lightdm/lightdm.conf No error in the terminal. If autologin is set in /etc/lightdm/lightdm.conf, then it works normally. [used distribution] Xubuntu 18-04, up to date. I didn't have this trouble in may 2018 while I was under Xubuntu 17-10. [related trouble] maybe it's related to this bug: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1529454 But I don't exactly have the same trouble. So I thought I should open a new one. Sorry if I was wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1785236/+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 1785154] Re: libsystemd-dev dependencies not satisfied
I rebuilt the package changing its dependencies to the available packages and everything worked fine. -- 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/1785154 Title: libsystemd-dev dependencies not satisfied Status in systemd package in Ubuntu: Invalid Bug description: "Following packages lacks these dependencies: libsystemd-dev : Depends: libsystemd0 (= 237-3ubuntu10) but version 237-3ubuntu10.3 is going to be installed" ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libsystemd-dev (not installed) Uname: Linux 4.18.0-999-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 3 03:02:02 2018 InstallationDate: Installed on 2017-01-12 (567 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-07-24 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1785154/+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 1771353] Re: Server feature level is now lower than when we began our transaction. Restarting with new ID
Installing libss-resolve works around the problem for me - is there a reason this is not installed by default on Ubuntu, per upstream's recommendations? -- 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/1771353 Title: Server feature level is now lower than when we began our transaction. Restarting with new ID Status in systemd package in Ubuntu: Confirmed Bug description: systemd 237-3ubuntu10 from bionic There is no /etc/netplan/* file. I'm getting some sort of a loop when systemd-resolved tries to resolve the hostname of my canonistack instance: ubuntu@bip:~$ systemd-resolve bip.lcy02.canonistack bip.lcy02.canonistack: resolve call failed: All attempts to contact name servers or networks failed systemd-resolved debug output loops over like this: Transaction 36341 is now 19121. Cache miss for bip.lcy02.canonistack IN A Transaction 19121 for scope dns on */*. Using feature level UDP+EDNS0 for transaction 19121. Sending query packet with id 19121. Processing incoming packet on transaction 19121. (rcode=SUCCESS) Server feature level is now lower than when we began our transaction. Restarting with new ID. Transaction 19121 is now 17157. Cache miss for bip.lcy02.canonistack IN A Transaction 17157 for scope dns on */*. Using feature level UDP+EDNS0 for transaction 17157. Sending query packet with id 17157. Processing incoming packet on transaction 17157. (rcode=SUCCESS) Server feature level is now lower than when we began our transaction. Restarting with new ID. ... Packet capture shows a loop like this: 13:38:32.293524 IP 10.55.32.54.53786 > 10.55.32.1.53: 46096+ [1au] A? bip.lcy02.canonistack. (50) 13:38:32.293753 IP 10.55.32.1.53 > 10.55.32.54.53786: 46096* 1/0/0 A 10.55.32.54 (55) 13:38:32.294026 IP 10.55.32.54.53786 > 10.55.32.1.53: 64494+ [1au] A? bip.lcy02.canonistack. (50) 13:38:32.294249 IP 10.55.32.1.53 > 10.55.32.54.53786: 64494* 1/0/0 A 10.55.32.54 (55) I'm going to attach the full debug output, and the pcap file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771353/+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 1771353] Re: Server feature level is now lower than when we began our transaction. Restarting with new ID
Hmm, my case seems to be caused by a dnsmasq bug - if there are no answers, it doesn't return an EDNS0 OPT record even if there was one in the query. This seems to be confusing systemd-resolved. Not sure what is causing @ahasenack's issue - the pcap shows the upstream DNS consistently not returning OPT records, which is expected if it doesn't support EDNS0 at all. So different causes but both apparently tickling some issue in resolved's logic. -- 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/1771353 Title: Server feature level is now lower than when we began our transaction. Restarting with new ID Status in systemd package in Ubuntu: Confirmed Bug description: systemd 237-3ubuntu10 from bionic There is no /etc/netplan/* file. I'm getting some sort of a loop when systemd-resolved tries to resolve the hostname of my canonistack instance: ubuntu@bip:~$ systemd-resolve bip.lcy02.canonistack bip.lcy02.canonistack: resolve call failed: All attempts to contact name servers or networks failed systemd-resolved debug output loops over like this: Transaction 36341 is now 19121. Cache miss for bip.lcy02.canonistack IN A Transaction 19121 for scope dns on */*. Using feature level UDP+EDNS0 for transaction 19121. Sending query packet with id 19121. Processing incoming packet on transaction 19121. (rcode=SUCCESS) Server feature level is now lower than when we began our transaction. Restarting with new ID. Transaction 19121 is now 17157. Cache miss for bip.lcy02.canonistack IN A Transaction 17157 for scope dns on */*. Using feature level UDP+EDNS0 for transaction 17157. Sending query packet with id 17157. Processing incoming packet on transaction 17157. (rcode=SUCCESS) Server feature level is now lower than when we began our transaction. Restarting with new ID. ... Packet capture shows a loop like this: 13:38:32.293524 IP 10.55.32.54.53786 > 10.55.32.1.53: 46096+ [1au] A? bip.lcy02.canonistack. (50) 13:38:32.293753 IP 10.55.32.1.53 > 10.55.32.54.53786: 46096* 1/0/0 A 10.55.32.54 (55) 13:38:32.294026 IP 10.55.32.54.53786 > 10.55.32.1.53: 64494+ [1au] A? bip.lcy02.canonistack. (50) 13:38:32.294249 IP 10.55.32.1.53 > 10.55.32.54.53786: 64494* 1/0/0 A 10.55.32.54 (55) I'm going to attach the full debug output, and the pcap file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771353/+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 1785083] Re: Weird behavior of the VM shutdown dropdown
This one is fine, if you look at the top I added a task for it. This is a thing Launchpad does really well - avoid the proliferation and confusion of bugs affecting or being discussed in multiple packages. -- 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/1785083 Title: Weird behavior of the VM shutdown dropdown Status in ubuntu-themes package in Ubuntu: New Status in virt-manager package in Ubuntu: Incomplete Bug description: The VM window includes a shutdown button with a dropdown button next to it. I've noticed two weird things about it that seem like simple GTK bugs: - The dropdown doesn't close just by clicking the dropdown button again - All the items in the dropdown are greyed out as if they're not functional, but pressing any of them still works ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: virt-manager 1:1.5.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 2 16:58:28 2018 InstallationDate: Installed on 2018-05-31 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1785083/+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 1785154] Re: libsystemd-dev dependencies not satisfied
** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1785154 Title: libsystemd-dev dependencies not satisfied Status in systemd package in Ubuntu: Invalid Bug description: "Following packages lacks these dependencies: libsystemd-dev : Depends: libsystemd0 (= 237-3ubuntu10) but version 237-3ubuntu10.3 is going to be installed" ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libsystemd-dev (not installed) Uname: Linux 4.18.0-999-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 3 03:02:02 2018 InstallationDate: Installed on 2017-01-12 (567 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-07-24 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1785154/+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 1767322] Re: "Activation of network connection failed" popup shows incessantly
Same issue on my Dell XPS 12 9Q33 after upgrading to Ubuntu 18.04. -- 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/1767322 Title: "Activation of network connection failed" popup shows incessantly Status in network-manager package in Ubuntu: Confirmed Bug description: All network connections work normally, however the popup "Activation of network connection failed" keeps showing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:04:56 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 600 192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1767322/+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 1785083] Re: Weird behavior of the VM shutdown dropdown
So you need me to open a new bug or is this one enough to track the ubuntu-themes issue? -- 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/1785083 Title: Weird behavior of the VM shutdown dropdown Status in ubuntu-themes package in Ubuntu: New Status in virt-manager package in Ubuntu: Incomplete Bug description: The VM window includes a shutdown button with a dropdown button next to it. I've noticed two weird things about it that seem like simple GTK bugs: - The dropdown doesn't close just by clicking the dropdown button again - All the items in the dropdown are greyed out as if they're not functional, but pressing any of them still works ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: virt-manager 1:1.5.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 2 16:58:28 2018 InstallationDate: Installed on 2018-05-31 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1785083/+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 1785154] Re: libsystemd-dev dependencies not satisfied
your options are 1) downgrade packages to =237-3ubuntu10, eg. apt install libsystemd0=237-3ubuntu10 2) enable bionic-updates (!) and then everything should be available 3) enable cosmic-proposed (!!!) and upgrade systemd only to v239 & disable cosmic-proposed Basically, v239 is not ready yet, and stuck in cosmic-proposed that is not to be used by humans, cause it has known critical integration issues. Whilst Bionic had a few post-18.04.0 fixes already shipped as SRUs that did not make it into cosmic yet. -- 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/1785154 Title: libsystemd-dev dependencies not satisfied Status in systemd package in Ubuntu: New Bug description: "Following packages lacks these dependencies: libsystemd-dev : Depends: libsystemd0 (= 237-3ubuntu10) but version 237-3ubuntu10.3 is going to be installed" ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libsystemd-dev (not installed) Uname: Linux 4.18.0-999-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 3 03:02:02 2018 InstallationDate: Installed on 2017-01-12 (567 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-07-24 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1785154/+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 1785083] Re: Weird behavior of the VM shutdown dropdown
So what do we know: - Working in KDE + Breeze theme - Broken in Gnome + Ambiance theme I tried Gnome + Adwaita theme and it works fine then. For the Desktop team steps to reproduce: 1. qemu-img create -f qcow2 /var/lib/libvirt/images/test.img 10M 2. apt install virt-manager libvirt-daemon-system 3. (relogin or "su -" to pick up group) 4. start virt-manager 5. define a guest based on existing image (the one created above) 6. start the guest Now you'll see the dropdown showing these issues. As mentioned, when switching to Adwaita the issue is gone. ** Also affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New -- 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/1785083 Title: Weird behavior of the VM shutdown dropdown Status in ubuntu-themes package in Ubuntu: New Status in virt-manager package in Ubuntu: Incomplete Bug description: The VM window includes a shutdown button with a dropdown button next to it. I've noticed two weird things about it that seem like simple GTK bugs: - The dropdown doesn't close just by clicking the dropdown button again - All the items in the dropdown are greyed out as if they're not functional, but pressing any of them still works ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: virt-manager 1:1.5.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 2 16:58:28 2018 InstallationDate: Installed on 2018-05-31 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1785083/+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 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile
one test needed trigger with new openmpi, done now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1771011 Title: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Fix Released Bug description: If environment variable name defined in AuthorizedKeysFile contains underscore character (environment="FOO_BAR=1" ...), sshd refuses connection and throws following error: authorized_keys:1: bad key options: invalid environment string To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1771011/+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 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile
This bug was fixed in the package openssh - 1:7.7p1-3 --- openssh (1:7.7p1-3) unstable; urgency=medium [ Colin Watson ] * Adjust git-dpm tagging configuration. * Remove no-longer-used Lintian overrides from openssh-server and ssh. * Add Documentation keys to ssh-agent.service, ssh.service, and ssh@.service. [ Juri Grabowski ] * Add rescue.target with ssh support. [ Christian Ehrhardt ] * Fix unintentional restriction of authorized keys environment options to be alphanumeric (closes: #903474, LP: #1771011). -- Colin Watson Tue, 10 Jul 2018 16:07:16 +0100 ** Changed in: openssh (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1771011 Title: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Fix Released Bug description: If environment variable name defined in AuthorizedKeysFile contains underscore character (environment="FOO_BAR=1" ...), sshd refuses connection and throws following error: authorized_keys:1: bad key options: invalid environment string To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1771011/+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 1429474] Re: Kubuntu Vivid 1 Beta 15.04: Missing german translation
** Package changed: xorg (Ubuntu) => konsole (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/1429474 Title: Kubuntu Vivid 1 Beta 15.04: Missing german translation Status in konsole package in Ubuntu: New Bug description: When opening a konsole window it first displays the message: "To run a command as administrator (user: root), user "sudo https://bugs.launchpad.net/ubuntu/+source/konsole/+bug/1429474/+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 1759050] Re: Ubuntu 16&17 don't stop. Toshiba C50 B 19H [SOLVED]
arcane, thank you for marking your bug report SOLVED. Marking this report "Invalid" in order to close. ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1759050 Title: Ubuntu 16&17 don't stop. Toshiba C50 B 19H [SOLVED] Status in xorg package in Ubuntu: Invalid Bug description: Hello, I am not sure I talking about the good package (xorg). Since I change my hard drive (for a transcend 370s) when using ubuntu 16 (same version as before) my computer don't want to stop (I have been waiting for 10 mn) so that I've done strong shut down and affected my Hard drive boot (I think have to use boot-repaire). I would be great full if you could fix the probleme or tell me more and how to fix. I am using ubuntu for many years now and love your works, Thank you, Thomas. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Mar 27 00:00:38 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1179:f910] InstallationDate: Installed on 2018-03-26 (0 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: TOSHIBA SATELLITE C50-B ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=385e28ce-7be5-4689-b130-a0b80a6af38c ro quiet splash intel_idle.max_cstate=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: 5.10 dmi.board.asset.tag: * dmi.board.name: ZBWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr5.10:bd08/10/2015:svnTOSHIBA:pnSATELLITEC50-B:pvrPSCMLE-09100FFR:rvnTOSHIBA:rnZBWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: SATELLITE C50-B dmi.product.version: PSCMLE-09100FFR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Mar 26 23:54:25 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1759050/+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 1785176] Re: GnuPG 1.4.23 released on 2018-06-11, addresses CVE-2017-7526
Thanks for reporting this - FYI you can see the status of each CVE via the CVE tracker http://people.canonical.com/~ubuntu-security/cve/ ie. https://people.canonical.com/~ubuntu- security/cve/2017/CVE-2017-7526.html This CVE was triaged against libgrypt only - not against gnupg1 - and all the upstream CVE trackers only seem to reference this CVE against libgcrypt. I can see the mention of CVE-2017-7526 on their homepage for GnuPG 1.4.23, however looking at the changes for 1.4.23 I can see no commits that appear relevant to this CVE: https://git.gnupg.org/cgi- bin/gitweb.cgi?p=gnupg.git;a=shortlog;h=refs/heads/STABLE-BRANCH-1-4 However, if we look at the changes that went into 1.4.22 then there are a bunch of changes which look analogous to the ones for libgrypt for CVE-2017-7526: https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=b38f4489f75e6e435886aa885807738a22c7ff60 https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=12029f83fd0ab3e8ad524f6c9135854662fddfd1 https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=554ded4854758bf6ca268432fa087f946932a409 https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=8fd9f72e1b2e578e45c98c978cab4f6d47683d2c Also I can't see any release annoucements for 1.4.22 or 1.4.23 in gnupg- announce either which is unfortunate. I will retriage this against gnupg1 as well and this will be fixed soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1785176 Title: GnuPG 1.4.23 released on 2018-06-11, addresses CVE-2017-7526 Status in gnupg package in Ubuntu: New Bug description: According to the information at the GnuPG Web site (https://www.gnupg.org/), GnuPG 1.4.23 was released on 2018-06-11 "to address the critical security bug CVE-2017-7526." https://www.gnupg.org/ https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7526 In addition, according to the information on the GnuPG news page (https://www.gnupg.org/news.html) GnuPG 1.4.22 was released on 2017-07-19 "to address the recently published local side channel attack CVE-2017-7526." https://www.gnupg.org/news.html https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7526 On the same page, it is mentioned that GnuPG 1.4.21 was released around 2016-08-17 to address the issue in CVE-2016-6313. https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000395.html (Note that the CVE id in the message is not correct) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6313 The changelog for the gnupg package version 1.4.20-1ubuntu3.2 mentions fixes for CVE-2018-12020 and CVE-2016-6313. There is no mention of CVE-2017-7526. http://changelogs.ubuntu.com/changelogs/pool/main/g/gnupg/gnupg_1.4.20-1ubuntu3.2/changelog Your attention to this issue is appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1785176/+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 1785176] Re: GnuPG 1.4.23 released on 2018-06-11, addresses CVE-2017-7526
Thank you for your attention to detail. CVE-2017-7526 was fixed in USN-3347-1 and -2 by patching the libgcrypt20 and libgcrypt11 source packages: https://usn.ubuntu.com/3347-1/ https://usn.ubuntu.com/3347-2/ You can track our work per-cve on https://people.canonical.com/~ubuntu- security/cve/2017/CVE-2017-7526.html and similar pages, which will show the source packages that may be affected by any given CVE. Thanks ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-7526 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1785176 Title: GnuPG 1.4.23 released on 2018-06-11, addresses CVE-2017-7526 Status in gnupg package in Ubuntu: New Bug description: According to the information at the GnuPG Web site (https://www.gnupg.org/), GnuPG 1.4.23 was released on 2018-06-11 "to address the critical security bug CVE-2017-7526." https://www.gnupg.org/ https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7526 In addition, according to the information on the GnuPG news page (https://www.gnupg.org/news.html) GnuPG 1.4.22 was released on 2017-07-19 "to address the recently published local side channel attack CVE-2017-7526." https://www.gnupg.org/news.html https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7526 On the same page, it is mentioned that GnuPG 1.4.21 was released around 2016-08-17 to address the issue in CVE-2016-6313. https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000395.html (Note that the CVE id in the message is not correct) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6313 The changelog for the gnupg package version 1.4.20-1ubuntu3.2 mentions fixes for CVE-2018-12020 and CVE-2016-6313. There is no mention of CVE-2017-7526. http://changelogs.ubuntu.com/changelogs/pool/main/g/gnupg/gnupg_1.4.20-1ubuntu3.2/changelog Your attention to this issue is appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1785176/+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
