[Touch-packages] [Bug 1699310] Re: Unmet dependancies on 16.04
On ubuntu 16.10 sudo apt install python3-click-package=0.4.45.1+16.10.20160916-0ubuntu1 gir1.2-click-0.4=0.4.45.1+16.10.20160916-0ubuntu1 libclick-0.4-0=0.4.45.1+16.10.20160916-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1699310 Title: Unmet dependancies on 16.04 Status in click package in Ubuntu: Confirmed Bug description: SInce today I can not install anything in 16.04 due to unmet dependencies with click. I'd like to remove it, but that fails: --- The following packages will be REMOVED click* 0 to upgrade, 0 to newly install, 1 to remove and 0 not to upgrade. 3 not fully installed or removed. After this operation, 88.1 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 590359 files and directories currently installed.) Removing click (0.4.43+16.04.20160203-0ubuntu2) ... Traceback (most recent call last): File "/usr/bin/click", line 37, in import click ImportError: No module named 'click' dpkg: error processing package click (--purge): subprocess installed pre-removal script returned error exit status 1 Job for click-system-hooks.service failed because the control process exited with error code. See "systemctl status click-system-hooks.service" and "journalctl -xe" for details. click-system-hooks.service couldn't start. Errors were encountered while processing: click E: Sub-process /usr/bin/dpkg returned an error code (1) --- I also often get the following error: --- The following packages have unmet dependencies. click : Depends: python3-click-package (= 0.4.43+16.04.20160203-0ubuntu2) but 0.4.43+16.04.20170613-0ubuntu1 is to be installed --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1699310/+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 1698050] Re: Disabled arrow buttons in Nautilus header bar are too dark
Looking at xenial by comparison, it appears not that the disabled colour has changed, but that the disabled buttons are now placed on a lighter background. In xenial they're below the titlebar, where the grey background is darker. In artful they're in the titlebar where the grey is lighter. So the increased contrast now looks odd. -- 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/1698050 Title: Disabled arrow buttons in Nautilus header bar are too dark Status in ubuntu-themes package in Ubuntu: New Bug description: Disabled arrow buttons in Nautilus header bar are too dark, under Gnome Shell. They don't look disabled as much as they look like a rendering bug, or look like depressed buttons. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 11:41:54 2017 InstallationDate: Installed on 2017-05-03 (42 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1698050/+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 1699683] [NEW] package libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 failed to install/upgrade: függőségi hibák - e csomag beállítatlan maradt
Public bug reported: i have no idea. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: libnss3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Jun 22 09:22:10 2017 ErrorMessage: függőségi hibák - e csomag beállítatlan maradt InstallationDate: Installed on 2017-05-31 (21 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: krb5 Title: package libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 failed to install/upgrade: függőségi hibák - e csomag beállítatlan maradt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1699683 Title: package libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 failed to install/upgrade: függőségi hibák - e csomag beállítatlan maradt Status in krb5 package in Ubuntu: New Bug description: i have no idea. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: libnss3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Jun 22 09:22:10 2017 ErrorMessage: függőségi hibák - e csomag beállítatlan maradt InstallationDate: Installed on 2017-05-31 (21 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: krb5 Title: package libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 failed to install/upgrade: függőségi hibák - e csomag beállítatlan maradt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1699683/+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 1693155] Re: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0)
"New icons" might not be strictly required. If someone can edit: /usr/share/icons/ubuntu-mono-dark/status/{22,24}/battery*.svg and change them to actual squares of the correct dimensions (22x22, 24x24) then I think that would be a proper fix. It does require editing (recentering) the curves though, and not just changing the canvas dimensions. So you would need a proper vector graphics editor. -- 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/1693155 Title: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0) Status in Ubuntu theme: Confirmed Status in Ubuntu UX: New Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1693155/+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 1699672] Re: systemctl status Failed to read server status: Connection timed out
And I have systemd-logind[505]: Failed to abandon session scope: Connection timed out in log -- 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/1699672 Title: systemctl status Failed to read server status: Connection timed out Status in systemd package in Ubuntu: New Bug description: I run 5 Ubuntu 16.04 as kvm VMs on centos 7. Yesterday, after installing updates, I can't reboot them, because systemd connection timeout. After reboot systemctl status worked fine, but today I get on one of these servers: systemctl status Failed to read server status: Connection timed out I guess after some time I'll have this on all of them. Looks like bug. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699672/+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 1699675] [NEW] Routine check
Public bug reported: See details sent. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 BootLog: [[0;32m OK [0m] Started Raise network interfaces. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jun 22 06:55:48 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:30db] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:30db] InstallationDate: Installed on 2017-06-20 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP EliteBook 6930p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic root=UUID=3e3fb406-1314-469f-b398-ce0337c6d0ee ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PCU Ver. F.13 dmi.board.name: 30DB dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 87.28 dmi.chassis.asset.tag: CZC9411L52 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PCUVer.F.13:bd09/11/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.13:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.28:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 6930p dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Jun 22 01:17:26 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset ** 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/1699675 Title: Routine check Status in xorg package in Ubuntu: New Bug description: See details sent. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 BootLog: [[0;32m OK [0m] Started Raise network interfaces. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jun 22 06:55:48 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:30db] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:30db] InstallationDate: Installed on 2017-06-20 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP EliteBook 6930p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic root=UUID=3e3fb40
[Touch-packages] [Bug 1699676] [NEW] package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: auto ProblemType: Package DistroRelease: Ubuntu 17.04 Package: click 0.4.45.1+16.10.20160916-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Thu Jun 22 12:00:59 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-28 (86 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: click Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: click (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1699676 Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in click package in Ubuntu: New Bug description: auto ProblemType: Package DistroRelease: Ubuntu 17.04 Package: click 0.4.45.1+16.10.20160916-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Thu Jun 22 12:00:59 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-28 (86 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: click Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: subprocess new pre-removal 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/click/+bug/1699676/+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 1699672] Re: systemctl status Failed to read server status: Connection timed out
btw, solution mentioned here https://github.com/systemd/systemd/issues/1961 to remove session dirs doesnt help ** Bug watch added: github.com/systemd/systemd/issues #1961 https://github.com/systemd/systemd/issues/1961 -- 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/1699672 Title: systemctl status Failed to read server status: Connection timed out Status in systemd package in Ubuntu: New Bug description: I run 5 Ubuntu 16.04 as kvm VMs on centos 7. Yesterday, after installing updates, I can't reboot them, because systemd connection timeout. After reboot systemctl status worked fine, but today I get on one of these servers: systemctl status Failed to read server status: Connection timed out I guess after some time I'll have this on all of them. Looks like bug. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699672/+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 1693155] Re: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0)
Nope, comment #14 won't really work adequately either. As a proof of concept, here's something that demonstrates what the outcome would be: https://code.launchpad.net/~vanvugt/ubuntu-themes/fix-1693155/+merge/326127 ** Changed in: ubuntu-themes Status: In Progress => Confirmed ** Changed in: ubuntu-themes Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- 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/1693155 Title: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0) Status in Ubuntu theme: Confirmed Status in Ubuntu UX: New Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1693155/+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 1693155] Re: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0)
** Also affects: ubuntu-ux Importance: Undecided Status: New ** Also affects: ubuntu-themes Importance: Undecided Status: New ** Changed in: ubuntu-themes Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: ubuntu-themes Status: New => In Progress -- 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/1693155 Title: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0) Status in Ubuntu theme: In Progress Status in Ubuntu UX: New Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1693155/+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 1699672] [NEW] systemctl status Failed to read server status: Connection timed out
Public bug reported: I run 5 Ubuntu 16.04 as kvm VMs on centos 7. Yesterday, after installing updates, I can't reboot them, because systemd connection timeout. After reboot systemctl status worked fine, but today I get on one of these servers: systemctl status Failed to read server status: Connection timed out I guess after some time I'll have this on all of them. Looks like bug. Thank you! ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1699672 Title: systemctl status Failed to read server status: Connection timed out Status in systemd package in Ubuntu: New Bug description: I run 5 Ubuntu 16.04 as kvm VMs on centos 7. Yesterday, after installing updates, I can't reboot them, because systemd connection timeout. After reboot systemctl status worked fine, but today I get on one of these servers: systemctl status Failed to read server status: Connection timed out I guess after some time I'll have this on all of them. Looks like bug. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699672/+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 1693155] Re: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0)
** Branch linked: lp:~vanvugt/ubuntu-themes/fix-1693155 -- 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/1693155 Title: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0) Status in Ubuntu theme: In Progress Status in Ubuntu UX: New Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1693155/+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 1699664] Re: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1699664 Title: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libnl3 package in Ubuntu: New Bug description: issue in installing packages. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 01:06:06 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libnl-3-200:amd64:3.2.27-1ubuntu0.16.04.1 Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ... dpkg: error processing package libnl-3-200:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-08 (74 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libnl3 Title: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.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/libnl3/+bug/1699664/+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 1699664] [NEW] package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin
Public bug reported: issue in installing packages. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 01:06:06 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libnl-3-200:amd64:3.2.27-1ubuntu0.16.04.1 Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ... dpkg: error processing package libnl-3-200:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-08 (74 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libnl3 Title: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.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) ** Affects: libnl3 (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 libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1699664 Title: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libnl3 package in Ubuntu: New Bug description: issue in installing packages. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 01:06:06 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libnl-3-200:amd64:3.2.27-1ubuntu0.16.04.1 Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ... dpkg: error processing package libnl-3-200:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-08 (74 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libnl3 Title: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.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/libnl3/+bug/1699664/+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 1699660] [NEW] systemd-resolve breaks resolution of local network hostnames
Public bug reported: After upgrading to Ubuntu 17.04 (zesty), resolution of my local network's host names is completely broken. Apparently the upgrade replaced my existing resolver with systemd-resolve, which deliberately refuses to pass "single-label" domain names to my domain name server. That is the server where all my network's host names are kept, so I can no longer resolve any of them. Apparently, this is yet another example of Poettering's upstream decisions causing denial of service to people who have been saddled with his malware. https://github.com/systemd/systemd/issues/2514#issuecomment-179203186 Would someone sensible please put a stop to this forced breakage during upgrade, and advise on how to fix it now that the damage has been done? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1699660 Title: systemd-resolve breaks resolution of local network hostnames Status in systemd package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 (zesty), resolution of my local network's host names is completely broken. Apparently the upgrade replaced my existing resolver with systemd-resolve, which deliberately refuses to pass "single-label" domain names to my domain name server. That is the server where all my network's host names are kept, so I can no longer resolve any of them. Apparently, this is yet another example of Poettering's upstream decisions causing denial of service to people who have been saddled with his malware. https://github.com/systemd/systemd/issues/2514#issuecomment-179203186 Would someone sensible please put a stop to this forced breakage during upgrade, and advise on how to fix it now that the damage has been done? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699660/+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 1693155] Re: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0)
and 3. Keep the SVGs as proper SVGs. Don't accidentally rasterize them like I did. -- 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/1693155 Title: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0) Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693155/+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 1693155] Re: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0)
Actually, this might work (and I apologise to design for troubling them if it does): 1. Ensure we use the SVGs from "22": /usr/share/icons/ubuntu-mono- dark/status/22/ 2. Fix gnome-shell to add square padding, avoiding distortion. The battery icons in 22/ have a narrower width (26x22 px) so should render to gnome-shell more clearly than 16/ (32x16px) or 24/ (32x24px) that would both pad out to 32x32 and then get scaled down too much to be readable. -- 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/1693155 Title: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0) Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693155/+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 1693155] Re: Squashed blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0)
** Summary changed: - Squashed blurry battery indicator in gnome-shell (using ubuntu-mono icons) + Squashed blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0) ** Summary changed: - Squashed blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0) + Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0) -- 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/1693155 Title: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0) Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693155/+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 1693155] Re: Squashed blurry battery indicator in gnome-shell (using ubuntu-mono icons)
** Tags added: gnome-17.10 -- 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/1693155 Title: Squashed blurry battery indicator in gnome-shell (using ubuntu-mono icons) Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693155/+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 1699647] Re: package account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1699647 Title: package account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 Status in account-plugins package in Ubuntu: New Bug description: i was making updates for packages on virtualmin and i faced and the updating failled so i tried it from terminal with apt-get update but also the process failed i tried some solutions from ask ubuntu forum like apt-get clean , dpkg --configure -a,ps -aux | grep 'apt-get',sudo kill -9 process id,apt-get -f install but all solutions didn't work ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 06:51:51 2017 DuplicateSignature: package:account-plugin-flickr:0.12+16.04.20160126-0ubuntu1 Removing g++ (4:5.3.1-1ubuntu1) ... dpkg (subprocess): unable to execute installed pre-removal script (/var/lib/dpkg/info/g++.prerm): Permission denied dpkg: error processing package g++ (--purge): subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2017-06-18 (3 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: account-plugins Title: package account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script 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/account-plugins/+bug/1699647/+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 1699647] [NEW] package account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2
Public bug reported: i was making updates for packages on virtualmin and i faced and the updating failled so i tried it from terminal with apt-get update but also the process failed i tried some solutions from ask ubuntu forum like apt-get clean , dpkg --configure -a,ps -aux | grep 'apt-get',sudo kill -9 process id,apt-get -f install but all solutions didn't work ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 06:51:51 2017 DuplicateSignature: package:account-plugin-flickr:0.12+16.04.20160126-0ubuntu1 Removing g++ (4:5.3.1-1ubuntu1) ... dpkg (subprocess): unable to execute installed pre-removal script (/var/lib/dpkg/info/g++.prerm): Permission denied dpkg: error processing package g++ (--purge): subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2017-06-18 (3 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: account-plugins Title: package account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: account-plugins (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 account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1699647 Title: package account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 Status in account-plugins package in Ubuntu: New Bug description: i was making updates for packages on virtualmin and i faced and the updating failled so i tried it from terminal with apt-get update but also the process failed i tried some solutions from ask ubuntu forum like apt-get clean , dpkg --configure -a,ps -aux | grep 'apt-get',sudo kill -9 process id,apt-get -f install but all solutions didn't work ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 06:51:51 2017 DuplicateSignature: package:account-plugin-flickr:0.12+16.04.20160126-0ubuntu1 Removing g++ (4:5.3.1-1ubuntu1) ... dpkg (subprocess): unable to execute installed pre-removal script (/var/lib/dpkg/info/g++.prerm): Permission denied dpkg: error processing package g++ (--purge): subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2017-06-18 (3 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: account-plugins Title: package account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script 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/account-plugins/+bug/1699647/+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 1699646] Re: package language-pack-en 1:16.04+20161009 failed to install/upgrade: package language-pack-en is already installed and configured
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en in Ubuntu. https://bugs.launchpad.net/bugs/1699646 Title: package language-pack-en 1:16.04+20161009 failed to install/upgrade: package language-pack-en is already installed and configured Status in language-pack-en package in Ubuntu: New Bug description: clean install on new hardware ProblemType: Package DistroRelease: Ubuntu 16.04 Package: language-pack-en 1:16.04+20161009 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Wed Jun 21 17:38:32 2017 DuplicateSignature: package:language-pack-en:1:16.04+20161009 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package language-pack-en-base (--configure): package language-pack-en-base is already installed and configured ErrorMessage: package language-pack-en is already installed and configured InstallationDate: Installed on 2017-06-21 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: language-pack-en Title: package language-pack-en 1:16.04+20161009 failed to install/upgrade: package language-pack-en is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en/+bug/1699646/+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 1699646] [NEW] package language-pack-en 1:16.04+20161009 failed to install/upgrade: package language-pack-en is already installed and configured
Public bug reported: clean install on new hardware ProblemType: Package DistroRelease: Ubuntu 16.04 Package: language-pack-en 1:16.04+20161009 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Wed Jun 21 17:38:32 2017 DuplicateSignature: package:language-pack-en:1:16.04+20161009 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package language-pack-en-base (--configure): package language-pack-en-base is already installed and configured ErrorMessage: package language-pack-en is already installed and configured InstallationDate: Installed on 2017-06-21 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: language-pack-en Title: package language-pack-en 1:16.04+20161009 failed to install/upgrade: package language-pack-en is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: language-pack-en (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en in Ubuntu. https://bugs.launchpad.net/bugs/1699646 Title: package language-pack-en 1:16.04+20161009 failed to install/upgrade: package language-pack-en is already installed and configured Status in language-pack-en package in Ubuntu: New Bug description: clean install on new hardware ProblemType: Package DistroRelease: Ubuntu 16.04 Package: language-pack-en 1:16.04+20161009 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Wed Jun 21 17:38:32 2017 DuplicateSignature: package:language-pack-en:1:16.04+20161009 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package language-pack-en-base (--configure): package language-pack-en-base is already installed and configured ErrorMessage: package language-pack-en is already installed and configured InstallationDate: Installed on 2017-06-21 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: language-pack-en Title: package language-pack-en 1:16.04+20161009 failed to install/upgrade: package language-pack-en is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en/+bug/1699646/+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 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
I forgot to add, my wi-fi adapter info is: $ lsusb | grep Wireless Bus 001 Device 002: ID 050d:825b Belkin Components F5D8055 N+ Wireless Adapter v2000 [Ralink RT3072] And I believe it is using the following driver/module: $ lsmod rt2x00usb 20480 1 rt2800usb Located at... /lib/modules/4.10.0-22-generic/kernel/drivers/net/wireless/ralink/rt2x00/rt2800usb.ko -- 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/1681513 Title: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue) Status in network-manager package in Ubuntu: Confirmed Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+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 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
In my logs, I see the message: "...aborting authentication ...by local choice (Reason: 3=DEAUTH_LEAVING)" (I've listed below the relevant portion of the log file, since the logs above do not include this particular error). The solution posted in comment #1 (https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1681513/comments/1) worked for me... $ sudo nano /etc/NetworkManager/NetworkManager.conf # Append... - - - - - - - - - - - - - - - - - - - - [Device] wifi.scan-rand-mac-address=no - - - - - - - - - - - - - - - - - - - - $ sudo service network-manager restart I did not need to install dnsmasq-base, as suggested in comment #24 (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/comments/24). What is the purpose of installing this? - - - - - - - - - - - - - - - - - - - - SYSTEM INFO - - - - - - - - - - - - - - - - - - - - Linux RS001 4.10.0-22-generic #24-Ubuntu SMP Mon May 22 17:43:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - LOG - - - - - - - - - - - - - - - - - - - - Jun 19 19:20:42 MY_COMPUTER NetworkManager[724]: [1497914442.1301] device (wlx00227540404a): supplicant interface state: disconnected -> scanning Jun 19 19:20:43 MY_COMPUTER wpa_supplicant[855]: wlx00227540404a: SME: Trying to authenticate with b4:75:0e:69:96:af (SSID='MY_WIFI' freq=2462 MHz) Jun 19 19:20:43 MY_COMPUTER kernel: [ 3001.130115] wlx00227540404a: authenticate with b4:75:0e:69:96:af Jun 19 19:20:43 MY_COMPUTER kernel: [ 3001.209885] wlx00227540404a: send auth to b4:75:0e:69:96:af (try 1/3) Jun 19 19:20:43 MY_COMPUTER NetworkManager[724]: [1497914443.7071] device (wlx00227540404a): supplicant interface state: scanning -> authenticating Jun 19 19:20:43 MY_COMPUTER kernel: [ 3001.231002] wlx00227540404a: authenticated Jun 19 19:20:45 MY_COMPUTER kernel: [ 3003.003601] wlx00227540404a: aborting authentication with b4:75:0e:69:96:af by local choice (Reason: 3=DEAUTH_LEAVING) Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.4980] device (wlx00227540404a): Activation: (wifi) association took too long, failing activation Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.4980] device (wlx00227540404a): state change: config -> failed (reason 'ssid-not-found') [50 120 53] Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.4984] manager: NetworkManager state is now DISCONNECTED Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.5053] device (wlx00227540404a): Activation: failed for connection 'MY_WIFI 1' Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.5111] device (wlx00227540404a): state change: failed -> disconnected (reason 'none') [120 30 0] Jun 19 19:20:45 MY_COMPUTER wpa_supplicant[855]: wlx00227540404a: CTRL-EVENT-DISCONNECTED bssid=b4:75:0e:69:96:af reason=3 locally_generated=1 Jun 19 19:20:45 MY_COMPUTER kernel: [ 3003.063699] IPv6: ADDRCONF(NETDEV_UP): wlx00227540404a: link is not ready Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.9519] device (wlx00227540404a): set-hw-addr: set MAC address to XX:XX:XX:XX:XX:XX (scanning) Jun 19 19:20:46 MY_COMPUTER kernel: [ 3003.775904] IPv6: ADDRCONF(NETDEV_UP): wlx00227540404a: link is not ready Jun 19 19:20:46 MY_COMPUTER NetworkManager[724]: [1497914446.2947] sup-iface[0x558e6b4676e0,wlx00227540404a]: connection disconnected (reason -3) Jun 19 19:20:46 MY_COMPUTER NetworkManager[724]: [1497914446.2958] device (wlx00227540404a): supplicant interface state: authenticating -> disconnected - - - - - - - - - - - - - - - - - - - - -- 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/1681513 Title: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue) Status in network-manager package in Ubuntu: Confirmed Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. Th
[Touch-packages] [Bug 1461834] Re: 1024-bit signing keys should be deprecated
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnupg2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1461834 Title: 1024-bit signing keys should be deprecated Status in Launchpad itself: New Status in apt package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: Confirmed Bug description: 1024-bit RSA was deprecated years ago by NIST[1], Microsoft[2] and more recently by others[3]. 1024-bit signing keys are insufficient to guarantee the authenticity of software distributed from Launchpad.net including PPAs. There should be a mechanism to refuse signing keys below a minimum key length based on key type. 1024-bit signing keys should be deprecated and removed from Launchpad.net itself ASAP. Future projects and PPAs should be disallowed from using 1024-bit signing keys. 1. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf 2. http://blogs.technet.com/b/pki/archive/2012/06/12/rsa-keys-under-1024-bits-are-blocked.aspx 3. https://threatpost.com/mozilla-1024-bit-cert-deprecation-leaves-107000-sites-untrusted/108114 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1461834/+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 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
Yes, it's exactly the same in code. Only the changelog text was modified. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Committed Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Verify in Sound settings you have it set to A2DP mode. 3. Turn off and then on the Bluetooth device. 4. Verify the device has reconnected and if not, force it to in the Bluetooth indicator menu. 5. Open Sound settings again, select the device and verify it's reappeared in A2DP mode. 6. Click 'Test Sound'. Expected: Sound can be heard from the Bluetooth device. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1438510. Possibly others too. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI 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.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1582213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages P
[Touch-packages] [Bug 613412] Re: packagekit in maverick causes error in apt operations
Same here, I was experiencing this problem (on 16.04 xenial) each time I ran 'sudo apt update' or any apt commands. Fixed by installing 'packagekit'. Not even sure what that does, but it must have done something because the error is gone now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/613412 Title: packagekit in maverick causes error in apt operations Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Maverick: Fix Released Bug description: Binary package hint: packagekit i upgraded in maverick today and suddenly i got these errors at the end of all apt operations (e.g. apt-get update etc.) Hit http://archive.ubuntu.com maverick-updates/restricted i386 Packages Error org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1 Reading package lists... Done removing packagkit and the apt backend for it, fixed it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/613412/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
After setting the ipv4.dns-priority of the VPN connection to a negative number and patching the source or installing the conveniently packaged .deb below, you should not experience DNS leaks over NM-VPN. (Output from extended test at https://dnsleaktest.com ) Test complete Query round Progress... Servers found 1 .. 1 2 .. 1 3 .. 1 4 .. 1 5 .. 1 6 .. 1 IP HostnameISP Country 173.239.226.69 ip-69-226-239-173.east.us.northamericancoax.com LogicWeb Inc United States To install the .deb package, simply use: cd ~/Downloads && sudo dpkg -i network-manager_1.4.4-1ubuntu4_amd64.deb NOTE: make sure apt does not replace the package with: sudo apt-mark hold network-manager Make sure to stop all network services and restart the network manager using: sudo service network-manager stop sudo service networking restart sudo service network-manager start To build the source and apply the patch yourself, use the following steps: sudo apt-get build-dep network-manager cd ~/Downloads && mkdir nm-patch && cd nm-patch apt-get source network-manager cd network-manager-1.4.4 cp ~/Downloads/systemd-resolved-dns-priority-fix.patch . patch -p1 < systemd-resolved-dns-priority-fix.patch rm systemd-resolved-dns-priority-fix.patch dpkg-buildpackage -us -uc -b (wait a while, it will take some time to compile) Then install the generated network-manager_1.4.4-1ubuntu .deb package using: cd ../ && sudo dpkg -i ** Attachment added: "network-manager_1.4.4-1ubuntu4_amd64.deb" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4900613/+files/network-manager_1.4.4-1ubuntu4_amd64.deb -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in network-manager source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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 1699630] Re: package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur
*** This bug is a duplicate of bug 1692981 *** https://bugs.launchpad.net/bugs/1692981 ** This bug has been marked a duplicate of bug 1692981 package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1699630 Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in isc-dhcp package in Ubuntu: New Bug description: ? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: isc-dhcp-common 4.3.3-5ubuntu12.7 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue Jun 20 04:56:26 2017 Dependencies: debianutils 4.7 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 sensible-utils 0.0.9 DuplicateSignature: package:isc-dhcp-common:4.3.3-5ubuntu12.7 Unpacking linux-headers-generic-hwe-16.04 (4.8.0.56.27) over (4.8.0.54.25) ... dpkg: error processing package isc-dhcp-common (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-23 (59 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: isc-dhcp Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 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/isc-dhcp/+bug/1699630/+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 1689825] Re: gnome-keyring not unlocked on boot
Maybe a clearer capture of something amiss... logging in and out and in repeatedly causes the keyring daemon process to be started again and again (as lightdm and as the user). Please see attached. ** Attachment added: "log_in_and_out.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+attachment/4900608/+files/log_in_and_out.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in chromium-browser package in Ubuntu: Invalid Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
I have successfully backported Thomas Haller's excellent upstream solution as detailed in https://bugzilla.gnome.org/show_bug.cgi?id=783569 This took some time as things have changed quite a bit upstream, but the patch works on the current zesty 17.04 1.4.4-1ubuntu3.1 network-manager! This is a much better fix than the stopgap SetLinkDomains "." bus call based on link type I included in the previous patch. It should be reviewed for current application/submission to the package maintainers as it is basically a direct backport of Haller's fix merged upstream. NOTE: You MUST set the ipv4.dns-priority to a negative number for the network-manager to unseat DNS configurations for other non-VPN interfaces. This patch allows for correct behavior with negative ipv4 .dns-priority: "Negative values have the special effect of excluding other configurations with a greater priority value; so in presence of at least a negative priority, only DNS servers from connections with the lowest priority value will be used." Usage of a negative dns-priority disables DNS configuration for all other interfaces, ensuring there are no DNS leaks over a VPN connection using systemd-resolved. Before Haller's bugfix, this feature did not work with systemd-resolved. To set the ipv4.dns-priority, open the VPN connection profile you have configured through NM like so: sudo nano /etc/NetworkManager/system-connections/ and adding the line (value of -42 recommended by Haller) "dns-priority=-42" so that the file contains something like: [ipv4] dns-priority=-42 dns-search= method=auto Alternatively, use the command sudo nmcli connection modify "" ipv4.dns-priority -42 And you should see that the config file for that connection contains the same line as shown above. After doing so and patching/installing the patched network manager, you should not experience DNS leaks. When I am connected to PIA's servers through network-manager-openvpn using the patched network manager and a negative ipv4.dns-priority set for my VPN connection, the output of systemd-resolved looks like this (notice that the Verizon ISP DNS server was 'unseated' and is absent for the primary wireless link wlo1): Global DNSSEC NTA: 10.in-addr.arpa ...(long list of NTAs omitted)... test Link 4 (tun0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 209.222.18.222 209.222.18.218 Link 2 (wlo1) Current Scopes: LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no If anyone is curious about support for the routing-only domain in NM, see the following bug https://bugzilla.gnome.org/show_bug.cgi?id=746422 which is about adding support for routing-only domains for systemd- resolved (still work in progress). ** Bug watch added: GNOME Bug Tracker #746422 https://bugzilla.gnome.org/show_bug.cgi?id=746422 ** Patch added: "systemd-resolved-dns-priority-fix.patch" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4900587/+files/systemd-resolved-dns-priority-fix.patch -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in network-manager source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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 1699630] Re: package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1699630 Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in isc-dhcp package in Ubuntu: New Bug description: ? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: isc-dhcp-common 4.3.3-5ubuntu12.7 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue Jun 20 04:56:26 2017 Dependencies: debianutils 4.7 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 sensible-utils 0.0.9 DuplicateSignature: package:isc-dhcp-common:4.3.3-5ubuntu12.7 Unpacking linux-headers-generic-hwe-16.04 (4.8.0.56.27) over (4.8.0.54.25) ... dpkg: error processing package isc-dhcp-common (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-23 (59 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: isc-dhcp Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 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/isc-dhcp/+bug/1699630/+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 1699630] [NEW] package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config
Public bug reported: ? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: isc-dhcp-common 4.3.3-5ubuntu12.7 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue Jun 20 04:56:26 2017 Dependencies: debianutils 4.7 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 sensible-utils 0.0.9 DuplicateSignature: package:isc-dhcp-common:4.3.3-5ubuntu12.7 Unpacking linux-headers-generic-hwe-16.04 (4.8.0.56.27) over (4.8.0.54.25) ... dpkg: error processing package isc-dhcp-common (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-23 (59 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: isc-dhcp Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 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) ** Affects: isc-dhcp (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 isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1699630 Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in isc-dhcp package in Ubuntu: New Bug description: ? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: isc-dhcp-common 4.3.3-5ubuntu12.7 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue Jun 20 04:56:26 2017 Dependencies: debianutils 4.7 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 sensible-utils 0.0.9 DuplicateSignature: package:isc-dhcp-common:4.3.3-5ubuntu12.7 Unpacking linux-headers-generic-hwe-16.04 (4.8.0.56.27) over (4.8.0.54.25) ... dpkg: error processing package isc-dhcp-common (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-23 (59 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: isc-dhcp Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 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/isc-dhcp/+bug/1699630/+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 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
This bug was fixed in the package gnome-session - 3.24.1-0ubuntu5 --- gnome-session (3.24.1-0ubuntu5) artful; urgency=medium * Backport patches from 3.25.3 to kill D-Bus clients on log out. This works around GNOME Online Accounts not working correctly after logging out (LP: #1610944) - 0001-manager-add-bus-daemon-dbus-api-xml-file.patch - 0002-system-add-api-for-detecting-if-this-is-the-last-ses.patch - 0003-manager-kill-off-bus-clients-at-log-out.patch -- Jeremy Bicha Wed, 21 Jun 2017 18:57:12 -0400 ** Changed in: gnome-session (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 gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) Status in gnome-online-accounts: Confirmed Status in Ubuntu GNOME: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Yakkety: Triaged Status in gnome-session source package in Yakkety: Triaged Status in gnome-online-accounts source package in Zesty: Triaged Status in gnome-session source package in Zesty: Triaged Bug description: Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+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 1449001] Re: systemd-resolved: please do not use Google public DNS by default
** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658 Importance: Unknown Status: Unknown ** Changed in: systemd Importance: Unknown => Undecided ** Changed in: systemd Status: Fix Released => New ** Changed in: systemd Remote watch: Debian Bug tracker #761658 => None -- 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/1449001 Title: systemd-resolved: please do not use Google public DNS by default Status in systemd: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: New Status in systemd source package in Artful: Fix Committed Status in systemd package in Debian: Unknown Bug description: systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.) in the absence of other configured DNS servers. systemd-resolved is not enabled by default in Ubuntu 15.04, but it is installed by default and will behave in this way if enabled by the user. $ cat /etc/systemd/resolved.conf (...) # Entries in this file show the compile time defaults. (...) #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844 This raises privacy concerns since in the event of accidental misconfiguration DNS queries will be sent unencrypted across the internet, and potentially also security concerns given systemd- resolved does not perform DNSSEC validation and is not particularly well hardened against malicious responses e.g. from a MITM (http://www.openwall.com/lists/oss-security/2014/11/12/5). I believe that it would be better to fail safe if no DNS server is configured -- i.e. have DNS lookups fail; it's better that the user is aware of their misconfiguration, rather than silently sending their queries to Google. The user can intentionally opt to use Google public DNS if they wish. Steps to reproduce: 1. Remove existing DNS configuration (from /etc/network/interfaces, /etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*) 2. Reboot, or otherwise clear relevant state 3. sudo service systemd-resolved start 4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf 5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by default), observe that DNS lookups probably still work, and queries are being sent to one of Google's servers Possible workaround/bugfix: ship a resolved.conf which clears the FallbackDNS parameter. This issue has been discussed in the Debian BTS (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658). My interpretation of the Debian package maintainer's position is that a user concerned with the privacy implications shouldn't let systemd get into a state where it uses the fallback DNS servers (quoting Marco d'Itri: "Short summary: have a resolv.conf file or use DHCP"). I would argue that it's safest not to have fallback DNS servers configured at all by default. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1449001/+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 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-session (Ubuntu) Importance: Undecided => High ** Changed in: gnome-session (Ubuntu) Status: New => Triaged ** Changed in: gnome-session (Ubuntu) Status: Triaged => Fix Committed ** Also affects: gnome-session (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: gnome-online-accounts (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: gnome-session (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: gnome-online-accounts (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: gnome-session (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: gnome-session (Ubuntu Yakkety) Status: New => Triaged ** Changed in: gnome-session (Ubuntu Zesty) Importance: Undecided => High ** Changed in: gnome-session (Ubuntu Zesty) Status: New => Triaged ** Changed in: gnome-online-accounts (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: gnome-online-accounts (Ubuntu Yakkety) Status: New => Triaged ** Changed in: gnome-online-accounts (Ubuntu Zesty) Importance: Undecided => High ** Changed in: gnome-online-accounts (Ubuntu Zesty) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) Status in gnome-online-accounts: Confirmed Status in Ubuntu GNOME: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Fix Committed Status in gnome-online-accounts source package in Yakkety: Triaged Status in gnome-session source package in Yakkety: Triaged Status in gnome-online-accounts source package in Zesty: Triaged Status in gnome-session source package in Zesty: Triaged Bug description: Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+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 1689825] Re: gnome-keyring not unlocked on boot
I uncovered another problematic side effect but I am unsure of the significance; perhaps this will trigger an idea for someone There are three user accounts on my box. Here's a flow: 1) Reboot box 2) Sign in as user 1 3) Examine running processes (as MikeD mentioned in #33) and observe two keyring processes 4) Log out as user 1 5) Log in as user 2 6) Observe that Unity (via upper-right corner power icon thing) shows two checkmarks indicating that both user 1 and user 2 are signed in -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in chromium-browser package in Ubuntu: Invalid Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1699604] [NEW] package linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: The laptop does not resume on suspend. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Thu Jun 22 00:35:28 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2017-05-14 (38 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: initramfs-tools Title: package linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages 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/1699604 Title: package linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: The laptop does not resume on suspend. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Thu Jun 22 00:35:28 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2017-05-14 (38 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: initramfs-tools Title: package linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1699604/+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 1699604] Re: package linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 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/1699604 Title: package linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: The laptop does not resume on suspend. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Thu Jun 22 00:35:28 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2017-05-14 (38 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: initramfs-tools Title: package linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1699604/+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 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)
Unfortunately I'm experiencing the same problem but with 17.04. The only difference to the previous reports that volume adjustment is happening in almost every second and the notification popup is visible constantly (it is flickering when the volume adjustment happens). So it is quite annoying. When I remove my headphones from the front audio jack, the autonomous volume adjusting stops. Interestingly i have never had similar problems with any of the previous versions of Ubuntu (starting from 12.04). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1585084 Title: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner) Status in pulseaudio package in Ubuntu: Fix Released Bug description: I upgraded to Ubuntu 16.04 yesterday, I did a clean install while preserving the home directory which is mounted in a separate partition. Even during the installation I had constant volume notification bubble appearing on the top-right corner of my screen, it would come and go about twice every minute. I just thought it was due to installing hardware drivers or something but the problem persisted even when I booted into the freshly installed system. I did some searching and two users reported the exact problem. And one more suggested this happens because constant disconnect and reconnect of the sound card which makes sense as the sound settings flashes briefly during every popup. Someone on IRC suggested to kill pulseaudio and thus restart it, that does not fix the issue. I also tried the Live environment thinking it might be due to some old config files in home partition (which was preserved during upgrade), but this problem happens in the live environment as well, which makes sense because it was present during installation as well. Users with the same issue: http://ubuntuforums.org/showthread.php?t=2323815 http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04 http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sidd 1651 F pulseaudio /dev/snd/controlC0: sidd 1651 F pulseaudio /dev/snd/controlC1: sidd 1651 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 12:31:12 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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 1677363] Re: does auditd work on armhf on precise?
Thanks for the reminder to upgrade this old system. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1677363 Title: does auditd work on armhf on precise? Status in audit package in Ubuntu: Incomplete Bug description: $ sudo /etc/init.d/auditd restart * Restarting audit daemon auditd Error sending add rule data request (Invalid argument) There was an error in line 17 of /etc/audit/audit.rules [ OK ] The non-comment lines before this were: -D -b 328 -w /etc/localtime -p wa -k time-change ... The watch rule on /etc/localtime is the first 'real' rule and it caused the error. The default rules file does almost nothing but seems to work okay. I'm guessing this is in part due to being on an armhf (armv7l) system. Thanks ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: auditd 1.7.18-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-1497.124-omap4 3.2.79 Uname: Linux 3.2.0-1497-omap4 armv7l ApportVersion: 2.0.1-0ubuntu17.15 Architecture: armhf Date: Wed Mar 29 12:20:43 2017 MarkForUpload: True ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: audit UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.audit.audit.rules: [modified] mtime.conffile..etc.audit.audit.rules: 2017-03-29T12:19:33.699968 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1677363/+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 1699592] Re: lxc-create fails for debian jessie armhf
Whoops not quite addressing the issue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1699592 Title: lxc-create fails for debian jessie armhf Status in lxc package in Ubuntu: New Bug description: I: Extracting zlib1g... W: Failure trying to run: chroot /var/cache/lxc/debian/partial-jessie-armhf mount -t proc proc /proc W: See /var/cache/lxc/debian/partial-jessie-armhf/debootstrap/debootstrap.log for details Failed to download the rootfs, aborting. Failed to download 'debian base' failed to install debian lxc-create: lxccontainer.c: create_run_template: 1295 container creation template for jessie-armhf failed lxc-create: tools/lxc_create.c: main: 318 Error creating container jessie-armhf root@finfin-ubuntuvm:~# cat /etc/debian_version stretch/sid root@finfin-ubuntuvm:~# do-release-upgrade Checking for a new Ubuntu release No new release found root@finfin-ubuntuvm:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty root@finfin-ubuntuvm:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1699592/+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 1699592] Re: lxc-create fails for debian jessie armhf
https://wiki.debian.org/LXC#Debian_8_.22Jessie.22 Found it finally. Wish there was a message or error pointing to this URL -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1699592 Title: lxc-create fails for debian jessie armhf Status in lxc package in Ubuntu: New Bug description: I: Extracting zlib1g... W: Failure trying to run: chroot /var/cache/lxc/debian/partial-jessie-armhf mount -t proc proc /proc W: See /var/cache/lxc/debian/partial-jessie-armhf/debootstrap/debootstrap.log for details Failed to download the rootfs, aborting. Failed to download 'debian base' failed to install debian lxc-create: lxccontainer.c: create_run_template: 1295 container creation template for jessie-armhf failed lxc-create: tools/lxc_create.c: main: 318 Error creating container jessie-armhf root@finfin-ubuntuvm:~# cat /etc/debian_version stretch/sid root@finfin-ubuntuvm:~# do-release-upgrade Checking for a new Ubuntu release No new release found root@finfin-ubuntuvm:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty root@finfin-ubuntuvm:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1699592/+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 1692870] Re: gzip compression broken in UniFi (built-in tomcat)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zlib (Ubuntu Zesty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1692870 Title: gzip compression broken in UniFi (built-in tomcat) Status in zlib package in Ubuntu: Confirmed Status in zlib source package in Zesty: Confirmed Bug description: [Impact] Since I upgraded from Ubuntu 16.10 to 17.04, my Guest portal for my UniFi system was broken (https://www.ubnt.com/download/unifi/). Curl gave me the following response: # curl - --compress localhost:8880/guest/s/default/ * Trying ::1... * TCP_NODELAY set * Connected to localhost (::1) port 8880 (#0) > GET /guest/s/default/ HTTP/1.1 > Host: localhost:8880 > User-Agent: curl/7.52.1 > Accept: */* > Accept-Encoding: deflate, gzip > < HTTP/1.1 200 OK < Server: Apache-Coyote/1.1 < Content-Type: text/html;charset=utf-8 < Transfer-Encoding: chunked < Content-Encoding: gzip < Vary: Accept-Encoding < Date: Tue, 23 May 2017 11:19:22 GMT < * Error while processing content unencoding: invalid code lengths set * Failed writing data * Curl_http_done: called premature == 1 * Closing connection 0 curl: (23) Error while processing content unencoding: invalid code lengths set [Test Case] - Install UniFi controller on Ubuntu 17.04 (http://dl.ubnt.com/unifi/5.4.16/unifi_sysvinit_all.deb) - Go to https://:8443/manage/site/default/settings/guestcontrol - Or do: curl - --compress :8880/guest/s/default/ When compression is enabled, its broken. When disabling compression in curl, it works fine. After some debugging, I found out that downgrading to zlib 1:1.2.8 .dfsg-2ubuntu5.1 was a workaround. Now after digging into the issue some more, I found the following upstream patch (unreleased version), fixes the issue: https://github.com/madler/zlib/commit/f9694097dd69354b03cb8af959094c7f260db0a1 [Regression Potential] Everybody upgrading from 16.10 (or previous) to 17.04 will be affected by this. The patch is taken from upstream, so this isn't a change we will need to keep different from upstream. I've already created a new package (see debdiff) that fixes the issue. [Other Info] Now as the UniFi controller is just some Tomcat, which relies on Java (OpenJDK), which uses zlib for its built-in Compression/Decompression. I guess even more java related tools can be broken. But I didn't have time to test this. At least some other people using UniFi have the same issue, see: https://community.ubnt.com/t5/UniFi-Wireless/ERR-CONTENT-DECODING-FAILED-on-guest-portal-customisation/td-p/1903419 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1692870/+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 1699592] Re: lxc-create fails for debian jessie armhf
Looks related to bug 1671990 but it's marked as invalid. However, I'm not running lxc-create inside another container. It is under qemu-user- static though. Any help with this would be appreciated -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1699592 Title: lxc-create fails for debian jessie armhf Status in lxc package in Ubuntu: New Bug description: I: Extracting zlib1g... W: Failure trying to run: chroot /var/cache/lxc/debian/partial-jessie-armhf mount -t proc proc /proc W: See /var/cache/lxc/debian/partial-jessie-armhf/debootstrap/debootstrap.log for details Failed to download the rootfs, aborting. Failed to download 'debian base' failed to install debian lxc-create: lxccontainer.c: create_run_template: 1295 container creation template for jessie-armhf failed lxc-create: tools/lxc_create.c: main: 318 Error creating container jessie-armhf root@finfin-ubuntuvm:~# cat /etc/debian_version stretch/sid root@finfin-ubuntuvm:~# do-release-upgrade Checking for a new Ubuntu release No new release found root@finfin-ubuntuvm:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty root@finfin-ubuntuvm:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1699592/+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 1689825] Re: gnome-keyring not unlocked on boot
The only "permanent" (well, it still asks for the password once when opening google-chrome after login) workaround I found was creating a startup item as described here: https://askubuntu.com/a/911896. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in chromium-browser package in Ubuntu: Invalid Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1699592] Re: lxc-create fails for debian jessie armhf
It's under zesty lxc-create -name jessie-armhf -t debian -- -a armhf -r jessie while the same architecture under Ubuntu using zesty creates without errors. Might be related to another bug that was marked invalid but I don't know how this differs from using the Ubuntu versus the Debian templates ** Package changed: ubuntu => lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1699592 Title: lxc-create fails for debian jessie armhf Status in lxc package in Ubuntu: New Bug description: I: Extracting zlib1g... W: Failure trying to run: chroot /var/cache/lxc/debian/partial-jessie-armhf mount -t proc proc /proc W: See /var/cache/lxc/debian/partial-jessie-armhf/debootstrap/debootstrap.log for details Failed to download the rootfs, aborting. Failed to download 'debian base' failed to install debian lxc-create: lxccontainer.c: create_run_template: 1295 container creation template for jessie-armhf failed lxc-create: tools/lxc_create.c: main: 318 Error creating container jessie-armhf root@finfin-ubuntuvm:~# cat /etc/debian_version stretch/sid root@finfin-ubuntuvm:~# do-release-upgrade Checking for a new Ubuntu release No new release found root@finfin-ubuntuvm:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty root@finfin-ubuntuvm:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1699592/+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 1699592] [NEW] lxc-create fails for debian jessie armhf
You have been subscribed to a public bug: I: Extracting zlib1g... W: Failure trying to run: chroot /var/cache/lxc/debian/partial-jessie-armhf mount -t proc proc /proc W: See /var/cache/lxc/debian/partial-jessie-armhf/debootstrap/debootstrap.log for details Failed to download the rootfs, aborting. Failed to download 'debian base' failed to install debian lxc-create: lxccontainer.c: create_run_template: 1295 container creation template for jessie-armhf failed lxc-create: tools/lxc_create.c: main: 318 Error creating container jessie-armhf root@finfin-ubuntuvm:~# cat /etc/debian_version stretch/sid root@finfin-ubuntuvm:~# do-release-upgrade Checking for a new Ubuntu release No new release found root@finfin-ubuntuvm:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty root@finfin-ubuntuvm:~# ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment zesty -- lxc-create fails for debian jessie armhf https://bugs.launchpad.net/bugs/1699592 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1697353] Re: package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyb
*** This bug is a duplicate of bug 1588998 *** https://bugs.launchpad.net/bugs/1588998 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1588998, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1588998 [master] package console-setup-linux 1.108ubuntu15 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15 -- 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/1697353 Title: package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.3 Status in console-setup package in Ubuntu: Confirmed Bug description: ubuntu 16.04 LTS, try to use kali linux in ubuntu but get this bug. ProblemType: Package DistroRelease: Kali 2017.1 Package: console-setup-linux 1.108ubuntu15.3 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 Date: Mon Jun 12 05:36:54 2017 ErrorMessage: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.3 InstallationDate: Installed on 2016-07-22 (324 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.23kali1 apt 1.2.20 SourcePackage: console-setup Title: package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.3 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/1697353/+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 1699478] Re: package console-setup-linux 1.164 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-confi
*** This bug is a duplicate of bug 1588998 *** https://bugs.launchpad.net/bugs/1588998 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1588998, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1588998 [master] package console-setup-linux 1.108ubuntu15 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15 -- 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/1699478 Title: package console-setup-linux 1.164 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.3 Status in console-setup package in Ubuntu: New Bug description: apt-get upgrade is not working ProblemType: Package DistroRelease: Kali 2017.1 Package: console-setup-linux 1.164 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Jun 21 16:11:36 2017 ErrorMessage: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.3 InstallationDate: Installed on 2017-06-20 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.23kali1 apt 1.2.19 SourcePackage: console-setup Title: package console-setup-linux 1.164 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.3 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/1699478/+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 1646015] Re: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Hi Laurent, the issue is from this line: invoke-rc.d: policy-rc.d denied execution of start. Until the work from https://bugzilla.redhat.com/show_bug.cgi?id=893751 lands it doesn't make sense to run multiple auditds on one kernel. Someone needs to do the work to see how much we're missing. So far I don't think anyone has offered to undertake the research to enable this. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1646015 Title: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Status in audit package in Ubuntu: Confirmed Bug description: HI I have the docker image for ubuntu 16.04 and 16.10 . In both I was tried to install the auditd but getting the following error. apt-get install auditdReading package lists... Done Building dependency tree... Done The following additional packages will be installed: libauparse0 Suggested packages: audispd-plugins The following NEW packages will be installed: auditd libauparse0 0 upgraded, 2 newly installed, 0 to remove and 21 not upgraded. Need to get 224 kB of archives. After this operation, 753 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu yakkety/main amd64 libauparse0 amd64 1:2.6.6-1ubuntu1 [38.6 kB] Get:2 http://archive.ubuntu.com/ubuntu yakkety/main amd64 auditd amd64 1:2.6.6-1ubuntu1 [186 kB] Fetched 224 kB in 0s (409 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package libauparse0:amd64. (Reading database ... 6501 files and directories currently installed.) Preparing to unpack .../0-libauparse0_1%3a2.6.6-1ubuntu1_amd64.deb ... Unpacking libauparse0:amd64 (1:2.6.6-1ubuntu1) ... Selecting previously unselected package auditd. Preparing to unpack .../1-auditd_1%3a2.6.6-1ubuntu1_amd64.deb ... Unpacking auditd (1:2.6.6-1ubuntu1) ... Setting up libauparse0:amd64 (1:2.6.6-1ubuntu1) ... Setting up auditd (1:2.6.6-1ubuntu1) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults invoke-rc.d: could not determine current runlevel invoke-rc.d: policy-rc.d denied execution of start. Processing triggers for libc-bin (2.24-0ubuntu1) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1646015/+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 1689825] Re: gnome-keyring not unlocked on boot
I am experiencing the same issue on one of my two machines. The 'Password and Keys' padlock icon next to 'Login' remains locked even with the correct password, and I'm unable to use Chrome, access e-mail etc.. I'm no expert but, in case it helps, these are two differences between the two machines I'm aware of... - the machine with the problem has an encrypted installation and the other not. Otherwise both installations are similar (basic 16.04 and not much else) - if I enter "ps aux | grep keyring" I get two 'gnome-keyring-daemon' processes listed on the problem machine (one for user 'lightdm' and one for myself), and only one on the machine without the problem (user is myself) The machine with the problem is almost useless for the moment - would be great to get a solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in chromium-browser package in Ubuntu: Invalid Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1699310] Re: Unmet dependancies on 16.04
Resolved it with: sudo apt install python3-click-package=0.4.43+16.04.20160203-0ubuntu2 gir1.2-click-0.4=0.4.43+16.04.20160203-0ubuntu2 libclick-0.4-0=0.4.43+16.04.20160203-0ubuntu2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1699310 Title: Unmet dependancies on 16.04 Status in click package in Ubuntu: Confirmed Bug description: SInce today I can not install anything in 16.04 due to unmet dependencies with click. I'd like to remove it, but that fails: --- The following packages will be REMOVED click* 0 to upgrade, 0 to newly install, 1 to remove and 0 not to upgrade. 3 not fully installed or removed. After this operation, 88.1 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 590359 files and directories currently installed.) Removing click (0.4.43+16.04.20160203-0ubuntu2) ... Traceback (most recent call last): File "/usr/bin/click", line 37, in import click ImportError: No module named 'click' dpkg: error processing package click (--purge): subprocess installed pre-removal script returned error exit status 1 Job for click-system-hooks.service failed because the control process exited with error code. See "systemctl status click-system-hooks.service" and "journalctl -xe" for details. click-system-hooks.service couldn't start. Errors were encountered while processing: click E: Sub-process /usr/bin/dpkg returned an error code (1) --- I also often get the following error: --- The following packages have unmet dependencies. click : Depends: python3-click-package (= 0.4.43+16.04.20160203-0ubuntu2) but 0.4.43+16.04.20170613-0ubuntu1 is to be installed --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1699310/+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 1668724] [cgroup-lite/precise] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for precise for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cgroup-lite in Ubuntu. https://bugs.launchpad.net/bugs/1668724 Title: fails to mount cgroupfs inside containers running on 16.04 Status in cgroup-lite package in Ubuntu: Fix Released Status in cgroup-lite source package in Precise: Fix Committed Status in cgroup-lite source package in Trusty: New Status in cgroup-lite source package in Xenial: Fix Committed Status in cgroup-lite source package in Yakkety: Fix Committed Bug description: I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts, and have noticed that the cgroups-mount script for mounting the cgroups inside the containers has stopped working. This is because systemd now comounts multiple controllers on a single hierarchy, which prevents mounting them individually inside the container. === SRU Justification Impact: nested containers fail to start Reproduce: create a root owned container; install lxc and cgroup-lite; create a container, and try to start it. Starting will fail if cgroup-lite is running in the first level container without this patch. Regression potential: should be low, it's possible that the regexp is simply wrong for some cases. === To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+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 1670036] Re: Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG compressed files
** Changed in: libtiff Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1670036 Title: Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG compressed files Status in LibTIFF: Fix Released Status in tiff package in Ubuntu: Invalid Status in tiff source package in Trusty: Fix Released Status in tiff source package in Xenial: Fix Released Status in tiff source package in Yakkety: Fix Released Bug description: The patches applied to libtiff 4.0.6 in 4.0.6-2ubuntu01 seem to break JPEG tiff read and write. To reproduce: $ tiffcp -c jpeg k2a.tif x.tif (where k2a.tif is a simple uncompressed RGB strip tiff) appears to work. However, x.tif, the output, will now not read without warnings: $ tiffcp x.tif y.tif TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in null byte. Forcing it to be null. JPEGLib: Warning, Premature end of JPEG file. This was working fine until a couple of days ago, so I guess it's one of the most recent patches. Some packages using libtiff seem to be broken too. For example, openslide, which uses libtiff to load jp2k-compressed slide images, is no longer working: $ openslide-write-png CMU-1-Small-Region.svs 0 0 0 100 100 x.png TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in null byte. Forcing it to be null. TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in null byte. Forcing it ... repeats 8 more times openslide-write-png: Premature end of JPEG file and x.png is not a valid PNG image. The test .svs image may be downloaded here: http://openslide.cs.cmu.edu/download/openslide-testdata/Aperio/ To manage notifications about this bug go to: https://bugs.launchpad.net/libtiff/+bug/1670036/+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 1699572] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: underprosessen installerte pre-removal-skript returnerte feilstatus 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 avahi in Ubuntu. https://bugs.launchpad.net/bugs/1699572 Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: underprosessen installerte pre-removal-skript returnerte feilstatus 1 Status in avahi package in Ubuntu: New Bug description: i was looking for additional drivers. then this error did appear. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sun Jun 18 18:51:04 2017 DpkgTerminalLog: Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ... Job for avahi-daemon.socket canceled. dpkg: error processing package avahi-dnsconfd (--purge): underprosessen installerte pre-removal-skript returnerte feilstatus 1 DuplicateSignature: package:avahi-dnsconfd:0.6.32~rc+dfsg-1ubuntu2 Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ... Job for avahi-daemon.socket canceled. dpkg: error processing package avahi-dnsconfd (--purge): underprosessen installerte pre-removal-skript returnerte feilstatus 1 ErrorMessage: underprosessen installerte pre-removal-skript returnerte feilstatus 1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: avahi Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: underprosessen installerte pre-removal-skript returnerte feilstatus 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1699572/+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 1699572] [NEW] package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: underprosessen installerte pre-removal-skript returnerte feilstatus 1
Public bug reported: i was looking for additional drivers. then this error did appear. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sun Jun 18 18:51:04 2017 DpkgTerminalLog: Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ... Job for avahi-daemon.socket canceled. dpkg: error processing package avahi-dnsconfd (--purge): underprosessen installerte pre-removal-skript returnerte feilstatus 1 DuplicateSignature: package:avahi-dnsconfd:0.6.32~rc+dfsg-1ubuntu2 Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ... Job for avahi-daemon.socket canceled. dpkg: error processing package avahi-dnsconfd (--purge): underprosessen installerte pre-removal-skript returnerte feilstatus 1 ErrorMessage: underprosessen installerte pre-removal-skript returnerte feilstatus 1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: avahi Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: underprosessen installerte pre-removal-skript returnerte feilstatus 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: avahi (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 avahi in Ubuntu. https://bugs.launchpad.net/bugs/1699572 Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: underprosessen installerte pre-removal-skript returnerte feilstatus 1 Status in avahi package in Ubuntu: New Bug description: i was looking for additional drivers. then this error did appear. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sun Jun 18 18:51:04 2017 DpkgTerminalLog: Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ... Job for avahi-daemon.socket canceled. dpkg: error processing package avahi-dnsconfd (--purge): underprosessen installerte pre-removal-skript returnerte feilstatus 1 DuplicateSignature: package:avahi-dnsconfd:0.6.32~rc+dfsg-1ubuntu2 Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ... Job for avahi-daemon.socket canceled. dpkg: error processing package avahi-dnsconfd (--purge): underprosessen installerte pre-removal-skript returnerte feilstatus 1 ErrorMessage: underprosessen installerte pre-removal-skript returnerte feilstatus 1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: avahi Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: underprosessen installerte pre-removal-skript returnerte feilstatus 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1699572/+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 1691911] Re: SRU of LXC 2.0.8
** Changed in: lxc (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1691911 Title: SRU of LXC 2.0.8 Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: New Status in lxc source package in Xenial: Fix Released Status in lxc source package in Yakkety: Fix Released Status in lxc source package in Zesty: Fix Released Status in lxc source package in Artful: Fix Released Bug description: LXC upstream released LXC 2.0.8 as a bugfix release with following changelog: - Security fix for CVE-2017-5985 (previously fixed in Ubuntu) - All templates have been updated to not set default passwords anymore, instead requiring lxc-attach be used to configure users. This may affect some automated environments that were relying on our default (very much insecure) users. - Make lxc-start-ephemeral Python 3.2-compatible - Fix typo - Allow build without sys/capability.h - lxc-opensuse: fix default value for release code - util: always malloc for setproctitle - util: update setproctitle comments - confile: clear lxc.network..ipv{4,6} when empty - lxc_setup_tios(): Ignore SIGTTOU and SIGTTIN signals - Make lxc-net return non-zero on failure - seccomp: allow x32 guests on amd64 hosts. - Add HAVE_LIBCAP - c/r: only supply --ext-mount-map for bind mounts - Added 'mkdir -p' functionality in create_or_remove_cgroup - Use LXC_ROOTFS_MOUNT in clonehostname hook - squeeze is not a supported release anymore, drop the key - start: dumb down SIGCHLD from WARN() to NOTICE() - log: fix lxc_unix_epoch_to_utc() - cgfsng: make trim() safer - seccomp: set SCMP_FLTATR_ATL_TSKIP if available - lxc-user-nic: re-order #includes - lxc-user-nic: improve + bugfix - lxc-user-nic: delete link on failure - conf: only try to delete veth when privileged - Fix lxc-containers to support multiple bridges - Fix mixed tab/spaces in previous patch - lxc-alpine: use dl-cdn.a.o as default mirror instead of random one - lxc-checkconfig: verify new[ug]idmap are setuid-root - [templates] archlinux: resolve conflicting files - [templates] archlinux: noneed default_timezone variable - python3: Deal with potential NULL char* - lxc-download.in / allow setting keyserver from env - lxc-download.in / Document keyserver change in help - Change variable check to match existing style - tree-wide: include directly - conf/ile: make sure buffer is large enough - tree-wide: include directly - tests: Support running on IPv6 networks - tests: Kill containers (don't wait for shutdown) - Fix opening wrong file in suggest_default_idmap - do not set the root password in the debian template - do not set insecure passwords - don't set a default password for altlinux, gentoo, openmandriva and pld - tools: exit with return code of lxc_execute() - Keep veth.pair.name on network shutdown - Makefile: fix static clang init.lxc build - Avoid waiting for bridge interface if disabled in sysconfig/lxc - Increased buffer length in print_stats() - avoid assigning to a variable which is not POSIX shell proof (bug #1498) - remove obsolete note about api stability - conf: less error prone pointer access - conf: lxc_map_ids() non-functional changes - caps: add lxc_{proc,file}_cap_is_set() - conf: check for {filecaps,setuid} on new{g,u}idmap - conf: improve log when mounting rootfs - ls: simplify the judgment condition when list active containers - fix typo introduced in #1509 - attach|unshare: fix the wrong comment - caps: skip file capability checks on android - autotools: check for cap_get_file - caps: return false if caps are not supported - conf: non-functional changes to setup_pts() - conf: use bind-mount for /dev/ptmx - conf: non-functional changes - utils: use loop device helpers from LXD - create ISSUE_TEMPLATE.md - cgroups: improve cgfsng debugging - issue template: fix typo - conf: close fd in lxc_setup_devpts() - conf: non-functional changes - utils: tweak lxc_mount_proc_if_needed() - Change sshd template to work with Ubuntu 17.04 - conf: order mount options - conf: add MS_LAZYTIME to mount options - monitor: report errno on exec() error - af unix: allow for maximum socket name - commands: avoid NULL pointer dereference - commands: non-functional changes - lxccontainer: avoid NULL pointer dereference - monitor: simplify abstract socket logic - precise is not the
[Touch-packages] [Bug 1693002] Re: SRU of LXC 1.0.10 (upstream bugfix release)
All tests passed, manual testing looks good and we haven't heard of any negative feedback about 1.0.10. Releasing. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1693002 Title: SRU of LXC 1.0.10 (upstream bugfix release) Status in lxc package in Ubuntu: Invalid Status in lxc source package in Trusty: Fix Released Bug description: LXC upstream released LXC 1.0.10 as a bugfix release with following changelog: - Security fix for CVE-2016-10124 - Security fix for CVE-2017-5985 - attach: simplify lsm_openat() - commands: improve logging - utils: add macro __LXC_NUMSTRLEN - tests; Don't cause test failures on cleanup errors - conf: clearly report to either use drop or keep - attach: close lsm label file descriptor - conf, attach: save errno across call to close - templates/lxc-debian.in: Fix typo in calling dpkg with --print-foreign-architectures option - templates/lxc-debian.in: handle ppc hostarch -> powerpc - Fix regression in errno handling cherry-pick - don't try to get stuff from /usr/lib/systemd on the host - lxc-opensuse: rm poweroff.target -> sigpwr.target copy - Add --enable-gnutls option - tests: skip unpriv tests on broken overlay module - Use AC_HEADER_MAJOR to detect major()/minor()/makedev() - Make lxc-start-ephemeral Python 3.2-compatible - systemd: enable delegate in service file - confile: clear lxc.network..ipv{4,6} when empty - seccomp: allow x32 guests on amd64 hosts. - squeeze is not a supported release anymore, drop the key - seccomp: set SCMP_FLTATR_ATL_TSKIP if available - lxc-checkconfig: verify new[ug]idmap are setuid-root - python3: Deal with potential NULL char* - lxc-download.in / allow setting keyserver from env - lxc-download.in / Document keyserver change in help - Change variable check to match existing style - tests: Support running on IPv6 networks - tests: Kill containers (don't wait for shutdown) - Fix opening wrong file in suggest_default_idmap - lxc_setup_tios(): Ignore SIGTTOU and SIGTTIN signals - Increased buffer length in print_stats() - remove obsolete note about api stability - conf: less error prone pointer access - create ISSUE_TEMPLATE.md - issue template: fix typo - conf: order mount options - commands: avoid NULL pointer dereference - commands: non-functional changes - lxccontainer: avoid NULL pointer dereference Just like Ubuntu itself, upstream releases long term support releases, as is 1.0 and then periodic point releases including all the accumulated bugfixes. Only the latest upstream release gets full support from the upstream developers, everyone else is expected to first update to it before receiving any kind of support. This should qualify under the minor upstream bugfix release allowance of the SRU policy, letting us SRU this without paperwork for every single change included in this upstream release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1693002/+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 1691911] Re: SRU of LXC 2.0.8
This has been in the development release and our PPA for a while now without any report of regressions. Releasing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1691911 Title: SRU of LXC 2.0.8 Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: New Status in lxc source package in Xenial: Fix Released Status in lxc source package in Yakkety: Fix Released Status in lxc source package in Zesty: Fix Released Status in lxc source package in Artful: Fix Released Bug description: LXC upstream released LXC 2.0.8 as a bugfix release with following changelog: - Security fix for CVE-2017-5985 (previously fixed in Ubuntu) - All templates have been updated to not set default passwords anymore, instead requiring lxc-attach be used to configure users. This may affect some automated environments that were relying on our default (very much insecure) users. - Make lxc-start-ephemeral Python 3.2-compatible - Fix typo - Allow build without sys/capability.h - lxc-opensuse: fix default value for release code - util: always malloc for setproctitle - util: update setproctitle comments - confile: clear lxc.network..ipv{4,6} when empty - lxc_setup_tios(): Ignore SIGTTOU and SIGTTIN signals - Make lxc-net return non-zero on failure - seccomp: allow x32 guests on amd64 hosts. - Add HAVE_LIBCAP - c/r: only supply --ext-mount-map for bind mounts - Added 'mkdir -p' functionality in create_or_remove_cgroup - Use LXC_ROOTFS_MOUNT in clonehostname hook - squeeze is not a supported release anymore, drop the key - start: dumb down SIGCHLD from WARN() to NOTICE() - log: fix lxc_unix_epoch_to_utc() - cgfsng: make trim() safer - seccomp: set SCMP_FLTATR_ATL_TSKIP if available - lxc-user-nic: re-order #includes - lxc-user-nic: improve + bugfix - lxc-user-nic: delete link on failure - conf: only try to delete veth when privileged - Fix lxc-containers to support multiple bridges - Fix mixed tab/spaces in previous patch - lxc-alpine: use dl-cdn.a.o as default mirror instead of random one - lxc-checkconfig: verify new[ug]idmap are setuid-root - [templates] archlinux: resolve conflicting files - [templates] archlinux: noneed default_timezone variable - python3: Deal with potential NULL char* - lxc-download.in / allow setting keyserver from env - lxc-download.in / Document keyserver change in help - Change variable check to match existing style - tree-wide: include directly - conf/ile: make sure buffer is large enough - tree-wide: include directly - tests: Support running on IPv6 networks - tests: Kill containers (don't wait for shutdown) - Fix opening wrong file in suggest_default_idmap - do not set the root password in the debian template - do not set insecure passwords - don't set a default password for altlinux, gentoo, openmandriva and pld - tools: exit with return code of lxc_execute() - Keep veth.pair.name on network shutdown - Makefile: fix static clang init.lxc build - Avoid waiting for bridge interface if disabled in sysconfig/lxc - Increased buffer length in print_stats() - avoid assigning to a variable which is not POSIX shell proof (bug #1498) - remove obsolete note about api stability - conf: less error prone pointer access - conf: lxc_map_ids() non-functional changes - caps: add lxc_{proc,file}_cap_is_set() - conf: check for {filecaps,setuid} on new{g,u}idmap - conf: improve log when mounting rootfs - ls: simplify the judgment condition when list active containers - fix typo introduced in #1509 - attach|unshare: fix the wrong comment - caps: skip file capability checks on android - autotools: check for cap_get_file - caps: return false if caps are not supported - conf: non-functional changes to setup_pts() - conf: use bind-mount for /dev/ptmx - conf: non-functional changes - utils: use loop device helpers from LXD - create ISSUE_TEMPLATE.md - cgroups: improve cgfsng debugging - issue template: fix typo - conf: close fd in lxc_setup_devpts() - conf: non-functional changes - utils: tweak lxc_mount_proc_if_needed() - Change sshd template to work with Ubuntu 17.04 - conf: order mount options - conf: add MS_LAZYTIME to mount options - monitor: report errno on exec() error - af unix: allow for maximum socket name - commands: avoid NULL pointer dereference - commands: non-functional changes - lxccontainer: avoid NULL pointer dereference - monitor: simplify abstract soc
[Touch-packages] [Bug 1691911] Re: SRU of LXC 2.0.8
This bug was fixed in the package lxc - 2.0.8-0ubuntu1~16.10.2 --- lxc (2.0.8-0ubuntu1~16.10.2) yakkety; urgency=medium * Cherry-pick upstream workaround for ppc64el failure: - 0011-utils-fix-ppc64le-builds.patch -- Stéphane Graber Mon, 29 May 2017 14:39:52 -0400 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1691911 Title: SRU of LXC 2.0.8 Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: New Status in lxc source package in Xenial: Fix Released Status in lxc source package in Yakkety: Fix Released Status in lxc source package in Zesty: Fix Released Status in lxc source package in Artful: Fix Released Bug description: LXC upstream released LXC 2.0.8 as a bugfix release with following changelog: - Security fix for CVE-2017-5985 (previously fixed in Ubuntu) - All templates have been updated to not set default passwords anymore, instead requiring lxc-attach be used to configure users. This may affect some automated environments that were relying on our default (very much insecure) users. - Make lxc-start-ephemeral Python 3.2-compatible - Fix typo - Allow build without sys/capability.h - lxc-opensuse: fix default value for release code - util: always malloc for setproctitle - util: update setproctitle comments - confile: clear lxc.network..ipv{4,6} when empty - lxc_setup_tios(): Ignore SIGTTOU and SIGTTIN signals - Make lxc-net return non-zero on failure - seccomp: allow x32 guests on amd64 hosts. - Add HAVE_LIBCAP - c/r: only supply --ext-mount-map for bind mounts - Added 'mkdir -p' functionality in create_or_remove_cgroup - Use LXC_ROOTFS_MOUNT in clonehostname hook - squeeze is not a supported release anymore, drop the key - start: dumb down SIGCHLD from WARN() to NOTICE() - log: fix lxc_unix_epoch_to_utc() - cgfsng: make trim() safer - seccomp: set SCMP_FLTATR_ATL_TSKIP if available - lxc-user-nic: re-order #includes - lxc-user-nic: improve + bugfix - lxc-user-nic: delete link on failure - conf: only try to delete veth when privileged - Fix lxc-containers to support multiple bridges - Fix mixed tab/spaces in previous patch - lxc-alpine: use dl-cdn.a.o as default mirror instead of random one - lxc-checkconfig: verify new[ug]idmap are setuid-root - [templates] archlinux: resolve conflicting files - [templates] archlinux: noneed default_timezone variable - python3: Deal with potential NULL char* - lxc-download.in / allow setting keyserver from env - lxc-download.in / Document keyserver change in help - Change variable check to match existing style - tree-wide: include directly - conf/ile: make sure buffer is large enough - tree-wide: include directly - tests: Support running on IPv6 networks - tests: Kill containers (don't wait for shutdown) - Fix opening wrong file in suggest_default_idmap - do not set the root password in the debian template - do not set insecure passwords - don't set a default password for altlinux, gentoo, openmandriva and pld - tools: exit with return code of lxc_execute() - Keep veth.pair.name on network shutdown - Makefile: fix static clang init.lxc build - Avoid waiting for bridge interface if disabled in sysconfig/lxc - Increased buffer length in print_stats() - avoid assigning to a variable which is not POSIX shell proof (bug #1498) - remove obsolete note about api stability - conf: less error prone pointer access - conf: lxc_map_ids() non-functional changes - caps: add lxc_{proc,file}_cap_is_set() - conf: check for {filecaps,setuid} on new{g,u}idmap - conf: improve log when mounting rootfs - ls: simplify the judgment condition when list active containers - fix typo introduced in #1509 - attach|unshare: fix the wrong comment - caps: skip file capability checks on android - autotools: check for cap_get_file - caps: return false if caps are not supported - conf: non-functional changes to setup_pts() - conf: use bind-mount for /dev/ptmx - conf: non-functional changes - utils: use loop device helpers from LXD - create ISSUE_TEMPLATE.md - cgroups: improve cgfsng debugging - issue template: fix typo - conf: close fd in lxc_setup_devpts() - conf: non-functional changes - utils: tweak lxc_mount_proc_if_needed() - Change sshd template to work with Ubuntu 17.04 - conf: order mount options - conf: add MS_LAZYTIME to mount options - monitor: report errno on exec() error - af unix: allow for maximum socket name -
[Touch-packages] [Bug 1691911] Re: SRU of LXC 2.0.8
This bug was fixed in the package lxc - 2.0.8-0ubuntu1~16.04.2 --- lxc (2.0.8-0ubuntu1~16.04.2) xenial; urgency=medium * Cherry-pick upstream workaround for ppc64el failure: - 0011-utils-fix-ppc64le-builds.patch -- Stéphane Graber Mon, 29 May 2017 14:37:15 -0400 ** Changed in: lxc (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: lxc (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1691911 Title: SRU of LXC 2.0.8 Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: New Status in lxc source package in Xenial: Fix Released Status in lxc source package in Yakkety: Fix Released Status in lxc source package in Zesty: Fix Released Status in lxc source package in Artful: Fix Released Bug description: LXC upstream released LXC 2.0.8 as a bugfix release with following changelog: - Security fix for CVE-2017-5985 (previously fixed in Ubuntu) - All templates have been updated to not set default passwords anymore, instead requiring lxc-attach be used to configure users. This may affect some automated environments that were relying on our default (very much insecure) users. - Make lxc-start-ephemeral Python 3.2-compatible - Fix typo - Allow build without sys/capability.h - lxc-opensuse: fix default value for release code - util: always malloc for setproctitle - util: update setproctitle comments - confile: clear lxc.network..ipv{4,6} when empty - lxc_setup_tios(): Ignore SIGTTOU and SIGTTIN signals - Make lxc-net return non-zero on failure - seccomp: allow x32 guests on amd64 hosts. - Add HAVE_LIBCAP - c/r: only supply --ext-mount-map for bind mounts - Added 'mkdir -p' functionality in create_or_remove_cgroup - Use LXC_ROOTFS_MOUNT in clonehostname hook - squeeze is not a supported release anymore, drop the key - start: dumb down SIGCHLD from WARN() to NOTICE() - log: fix lxc_unix_epoch_to_utc() - cgfsng: make trim() safer - seccomp: set SCMP_FLTATR_ATL_TSKIP if available - lxc-user-nic: re-order #includes - lxc-user-nic: improve + bugfix - lxc-user-nic: delete link on failure - conf: only try to delete veth when privileged - Fix lxc-containers to support multiple bridges - Fix mixed tab/spaces in previous patch - lxc-alpine: use dl-cdn.a.o as default mirror instead of random one - lxc-checkconfig: verify new[ug]idmap are setuid-root - [templates] archlinux: resolve conflicting files - [templates] archlinux: noneed default_timezone variable - python3: Deal with potential NULL char* - lxc-download.in / allow setting keyserver from env - lxc-download.in / Document keyserver change in help - Change variable check to match existing style - tree-wide: include directly - conf/ile: make sure buffer is large enough - tree-wide: include directly - tests: Support running on IPv6 networks - tests: Kill containers (don't wait for shutdown) - Fix opening wrong file in suggest_default_idmap - do not set the root password in the debian template - do not set insecure passwords - don't set a default password for altlinux, gentoo, openmandriva and pld - tools: exit with return code of lxc_execute() - Keep veth.pair.name on network shutdown - Makefile: fix static clang init.lxc build - Avoid waiting for bridge interface if disabled in sysconfig/lxc - Increased buffer length in print_stats() - avoid assigning to a variable which is not POSIX shell proof (bug #1498) - remove obsolete note about api stability - conf: less error prone pointer access - conf: lxc_map_ids() non-functional changes - caps: add lxc_{proc,file}_cap_is_set() - conf: check for {filecaps,setuid} on new{g,u}idmap - conf: improve log when mounting rootfs - ls: simplify the judgment condition when list active containers - fix typo introduced in #1509 - attach|unshare: fix the wrong comment - caps: skip file capability checks on android - autotools: check for cap_get_file - caps: return false if caps are not supported - conf: non-functional changes to setup_pts() - conf: use bind-mount for /dev/ptmx - conf: non-functional changes - utils: use loop device helpers from LXD - create ISSUE_TEMPLATE.md - cgroups: improve cgfsng debugging - issue template: fix typo - conf: close fd in lxc_setup_devpts() - conf: non-functional changes - utils: tweak lxc_mount_proc_if_needed() - Change sshd template to work with Ubuntu 17.04 - conf: order
[Touch-packages] [Bug 1693002] Update Released
The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1693002 Title: SRU of LXC 1.0.10 (upstream bugfix release) Status in lxc package in Ubuntu: Invalid Status in lxc source package in Trusty: Fix Released Bug description: LXC upstream released LXC 1.0.10 as a bugfix release with following changelog: - Security fix for CVE-2016-10124 - Security fix for CVE-2017-5985 - attach: simplify lsm_openat() - commands: improve logging - utils: add macro __LXC_NUMSTRLEN - tests; Don't cause test failures on cleanup errors - conf: clearly report to either use drop or keep - attach: close lsm label file descriptor - conf, attach: save errno across call to close - templates/lxc-debian.in: Fix typo in calling dpkg with --print-foreign-architectures option - templates/lxc-debian.in: handle ppc hostarch -> powerpc - Fix regression in errno handling cherry-pick - don't try to get stuff from /usr/lib/systemd on the host - lxc-opensuse: rm poweroff.target -> sigpwr.target copy - Add --enable-gnutls option - tests: skip unpriv tests on broken overlay module - Use AC_HEADER_MAJOR to detect major()/minor()/makedev() - Make lxc-start-ephemeral Python 3.2-compatible - systemd: enable delegate in service file - confile: clear lxc.network..ipv{4,6} when empty - seccomp: allow x32 guests on amd64 hosts. - squeeze is not a supported release anymore, drop the key - seccomp: set SCMP_FLTATR_ATL_TSKIP if available - lxc-checkconfig: verify new[ug]idmap are setuid-root - python3: Deal with potential NULL char* - lxc-download.in / allow setting keyserver from env - lxc-download.in / Document keyserver change in help - Change variable check to match existing style - tests: Support running on IPv6 networks - tests: Kill containers (don't wait for shutdown) - Fix opening wrong file in suggest_default_idmap - lxc_setup_tios(): Ignore SIGTTOU and SIGTTIN signals - Increased buffer length in print_stats() - remove obsolete note about api stability - conf: less error prone pointer access - create ISSUE_TEMPLATE.md - issue template: fix typo - conf: order mount options - commands: avoid NULL pointer dereference - commands: non-functional changes - lxccontainer: avoid NULL pointer dereference Just like Ubuntu itself, upstream releases long term support releases, as is 1.0 and then periodic point releases including all the accumulated bugfixes. Only the latest upstream release gets full support from the upstream developers, everyone else is expected to first update to it before receiving any kind of support. This should qualify under the minor upstream bugfix release allowance of the SRU policy, letting us SRU this without paperwork for every single change included in this upstream release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1693002/+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 1693002] Re: SRU of LXC 1.0.10 (upstream bugfix release)
This bug was fixed in the package lxc - 1.0.10-0ubuntu1 --- lxc (1.0.10-0ubuntu1) trusty; urgency=medium * New upstream bugfix release. (LP: #1693002) - Security fix for CVE-2016-10124 - Security fix for CVE-2017-5985 - attach: simplify lsm_openat() - commands: improve logging - utils: add macro __LXC_NUMSTRLEN - tests; Don't cause test failures on cleanup errors - conf: clearly report to either use drop or keep - attach: close lsm label file descriptor - conf, attach: save errno across call to close - templates/lxc-debian.in: Fix typo in calling dpkg with --print-foreign-architectures option - templates/lxc-debian.in: handle ppc hostarch -> powerpc - Fix regression in errno handling cherry-pick - don't try to get stuff from /usr/lib/systemd on the host - lxc-opensuse: rm poweroff.target -> sigpwr.target copy - Add --enable-gnutls option - tests: skip unpriv tests on broken overlay module - Use AC_HEADER_MAJOR to detect major()/minor()/makedev() - Make lxc-start-ephemeral Python 3.2-compatible - systemd: enable delegate in service file - confile: clear lxc.network..ipv{4,6} when empty - seccomp: allow x32 guests on amd64 hosts. - squeeze is not a supported release anymore, drop the key - seccomp: set SCMP_FLTATR_ATL_TSKIP if available - lxc-checkconfig: verify new[ug]idmap are setuid-root - python3: Deal with potential NULL char* - lxc-download.in / allow setting keyserver from env - lxc-download.in / Document keyserver change in help - Change variable check to match existing style - tests: Support running on IPv6 networks - tests: Kill containers (don't wait for shutdown) - Fix opening wrong file in suggest_default_idmap - lxc_setup_tios(): Ignore SIGTTOU and SIGTTIN signals - Increased buffer length in print_stats() - remove obsolete note about api stability - conf: less error prone pointer access - create ISSUE_TEMPLATE.md - issue template: fix typo - conf: order mount options - commands: avoid NULL pointer dereference - commands: non-functional changes - lxccontainer: avoid NULL pointer dereference -- Stéphane Graber Tue, 23 May 2017 14:44:34 -0400 ** Changed in: lxc (Ubuntu Trusty) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-10124 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5985 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1693002 Title: SRU of LXC 1.0.10 (upstream bugfix release) Status in lxc package in Ubuntu: Invalid Status in lxc source package in Trusty: Fix Released Bug description: LXC upstream released LXC 1.0.10 as a bugfix release with following changelog: - Security fix for CVE-2016-10124 - Security fix for CVE-2017-5985 - attach: simplify lsm_openat() - commands: improve logging - utils: add macro __LXC_NUMSTRLEN - tests; Don't cause test failures on cleanup errors - conf: clearly report to either use drop or keep - attach: close lsm label file descriptor - conf, attach: save errno across call to close - templates/lxc-debian.in: Fix typo in calling dpkg with --print-foreign-architectures option - templates/lxc-debian.in: handle ppc hostarch -> powerpc - Fix regression in errno handling cherry-pick - don't try to get stuff from /usr/lib/systemd on the host - lxc-opensuse: rm poweroff.target -> sigpwr.target copy - Add --enable-gnutls option - tests: skip unpriv tests on broken overlay module - Use AC_HEADER_MAJOR to detect major()/minor()/makedev() - Make lxc-start-ephemeral Python 3.2-compatible - systemd: enable delegate in service file - confile: clear lxc.network..ipv{4,6} when empty - seccomp: allow x32 guests on amd64 hosts. - squeeze is not a supported release anymore, drop the key - seccomp: set SCMP_FLTATR_ATL_TSKIP if available - lxc-checkconfig: verify new[ug]idmap are setuid-root - python3: Deal with potential NULL char* - lxc-download.in / allow setting keyserver from env - lxc-download.in / Document keyserver change in help - Change variable check to match existing style - tests: Support running on IPv6 networks - tests: Kill containers (don't wait for shutdown) - Fix opening wrong file in suggest_default_idmap - lxc_setup_tios(): Ignore SIGTTOU and SIGTTIN signals - Increased buffer length in print_stats() - remove obsolete note about api stability - conf: less error prone pointer access - create ISSUE_TEMPLATE.md - issue template: fix typo - conf: order mount options - commands: avoid NULL pointer dereference - commands:
[Touch-packages] [Bug 1657646] Re: Missing thin-provisioning-tools prevents VG with thin pool LV from being (de)activated, but not its creation
** Bug watch added: Debian Bug tracker #865463 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865463 ** Also affects: lvm2 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865463 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1657646 Title: Missing thin-provisioning-tools prevents VG with thin pool LV from being (de)activated, but not its creation Status in lvm2 package in Ubuntu: New Status in lvm2 package in Debian: Unknown Bug description: Creating a thin pool LV is allowed even when thin-provisioning-tools is not installed. But deactivating or activating that VG fails. Since deactivating the VG usually only happens at reboot, the user might fail to notice this big problem until then. I think the lvconvert tool, used to combine the two "thin LVs" into a thin pool LV, should refuse to run if thin-provisioning-tools, or the needed scripts, aren't installed. Steps to reproduce: root@15-89:~# vgcreate vg /dev/vdb1 Volume group "vg" successfully created root@15-89:~# vgs VG #PV #LV #SN Attr VSize VFree vg 1 0 0 wz--n- 40.00g 40.00g root@15-89:~# lvcreate -n pool0 -l 90%VG vg Logical volume "pool0" created. root@15-89:~# lvcreate -n pool0meta -l 5%VG vg Logical volume "pool0meta" created. root@15-89:~# lvs LVVG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert pool0 vg -wi-a- 36.00g pool0meta vg -wi-a- 2.00g root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 100 Jun 21 14:15 ./ drwxr-xr-x 20 root root3820 Jun 21 14:15 ../ crw--- 1 root root 10, 236 Jun 21 13:15 control lrwxrwxrwx 1 root root 7 Jun 21 14:14 vg-pool0 -> ../dm-0 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0meta -> ../dm-1 root@15-89:~# lvconvert --type thin-pool --poolmetadata vg/pool0meta vg/pool0 WARNING: Converting logical volume vg/pool0 and vg/pool0meta to pool's data and metadata volumes. THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.) Do you really want to convert vg/pool0 and vg/pool0meta? [y/n]: y Converted vg/pool0 to thin pool. root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 120 Jun 21 14:15 ./ drwxr-xr-x 20 root root3840 Jun 21 14:15 ../ crw--- 1 root root 10, 236 Jun 21 13:15 control lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0_tdata -> ../dm-1 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0_tmeta -> ../dm-0 root@15-89:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%S ync Convert [lvol0_pmspare] vg ewi--- 2.00g pool0 vg twi-a-tz-- 36.00g 0.00 0.01 [pool0_tdata] vg Twi-ao 36.00g [pool0_tmeta] vg ewi-ao 2.00g If you now reboot the system, all that is gone: root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 60 Jun 21 14:28 ./ drwxr-xr-x 19 root root3760 Jun 21 14:28 ../ crw--- 1 root root 10, 236 Jun 21 14:28 control The same happens if you deactivate the VG (which the reboot undoubtedly triggers). It fails because of a missing /usr/sbin/thin_check which is provided by the thin-provisioning-tools package: root@15-89:~# vgchange -a n /usr/sbin/thin_check: execvp failed: No such file or directory WARNING: Integrity check of metadata for pool vg/pool0 failed. 0 logical volume(s) in volume group "vg" now active root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 60 Jun 21 14:29 ./ drwxr-xr-x 19 root root3760 Jun 21 14:29 ../ crw--- 1 root root 10, 236 Jun 21 14:28 control To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1657646/+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 1699559] Re: webbrowser-app crashed with SIGABRT in __run_exit_handlers()
*** This bug is a duplicate of bug 1560994 *** https://bugs.launchpad.net/bugs/1560994 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1560994, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1699559/+attachment/4900388/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1699559/+attachment/4900390/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1699559/+attachment/4900394/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1699559/+attachment/4900395/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1699559/+attachment/4900396/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1699559/+attachment/4900397/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1699559/+attachment/4900398/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1560994 webbrowser-app crashed with SIGABRT in oxide::BrowserProcessMainImpl::~BrowserProcessMainImpl ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1699559 Title: webbrowser-app crashed with SIGABRT in __run_exit_handlers() Status in webbrowser-app package in Ubuntu: New Bug description: whats problem? ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: webbrowser-app 0.23+17.04.20170321-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-8.13-generic 4.11.6 Uname: Linux 4.11.0-8-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: MATE Date: Wed Jun 21 22:55:55 2017 ExecutablePath: /usr/bin/webbrowser-app InstallationDate: Installed on 2017-05-05 (47 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: webbrowser-app /home/username/Downloads/Age\ Verification.html Signal: 6 SourcePackage: webbrowser-app StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 __run_exit_handlers (status=1, listp=0x7f9815b295d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:83 __GI_exit (status=) at exit.c:105 Title: webbrowser-app crashed with SIGABRT in __run_exit_handlers() UpgradeStatus: Upgraded to artful on 2017-05-09 (42 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1699559/+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 1697146] Re: Unable to use apport to report any bugs prior to the first software update
Another way to recreate this bug report is to remove everything in '/var/lib/apt/lists/*'. -- 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/1697146 Title: Unable to use apport to report any bugs prior to the first software update Status in apport package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Running `ubuntu-bug gnome-shell` from within an installed artful system claims that it is not an official ubuntu package. Running it from the live CD session works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1697146/+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 1636564] Re: Segfault from libX11.so.6.3.0
I have the same problem. See the attached syslog. The x-server almost crashes, and if I wait for a long time I might manage to get back to the login screen. The problem seems to occur mainly in my case when using the Google Chrome browswer. I have an Nvidia card using KMS and Nouveau, and my network connection is via WiFi. I can confirm the problem is distro-inpependent, I use Gentoo Linux. ** Attachment added: "Syslog" https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1636564/+attachment/4900387/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1636564 Title: Segfault from libX11.so.6.3.0 Status in libx11 package in Ubuntu: Confirmed Bug description: Something went wrong with my Ubuntu 16.04 LTS desktop today. When I got back to the system Mattermost and a Chrome were indicating that the network was not working. I started to look about and it seemed that my main ethernet network connection had lost its IPv4 address somehow. ifconfig and the GUI network manager confirmed this. To try and resolve this I physically removed the connector and the plugged it back in. Shortly after I did this my GUI seemed to die out and I ended up back at the login screen. Once everything had calmed down I logged back in. After some digging about in the logs I noticed the following in /var/log/kern.log Oct 25 13:01:09 thorne-ul-dt kernel: [694321.877561] Mattermost[744]: segfault at 968 ip 7f8a9e257643 sp 7ffe72a3b510 error 4 in libX11.so.6.3.0[7f8a9e22f000+135000] Oct 25 13:01:09 thorne-ul-dt kernel: [694322.029362] chrome[745]: segfault at 968 ip 7fd4b5c73643 sp 7fff94f78d90 error 4 in libX11.so.6.3.0[7fd4b5c4b000+135000] That seemed to be the correct time for the problem I noticed. What exactly caused it I am not sure. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libx11-6 2:1.6.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 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 Oct 25 17:07:28 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2015-03-12 (592 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: libx11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V 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.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Oct 25 13:01:04 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id
[Touch-packages] [Bug 1677363] Re: does auditd work on armhf on precise?
Hi, audit in precise is quite old. Did you retry with a more recent version of ubuntu/audit? ** Changed in: audit (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1677363 Title: does auditd work on armhf on precise? Status in audit package in Ubuntu: Incomplete Bug description: $ sudo /etc/init.d/auditd restart * Restarting audit daemon auditd Error sending add rule data request (Invalid argument) There was an error in line 17 of /etc/audit/audit.rules [ OK ] The non-comment lines before this were: -D -b 328 -w /etc/localtime -p wa -k time-change ... The watch rule on /etc/localtime is the first 'real' rule and it caused the error. The default rules file does almost nothing but seems to work okay. I'm guessing this is in part due to being on an armhf (armv7l) system. Thanks ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: auditd 1.7.18-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-1497.124-omap4 3.2.79 Uname: Linux 3.2.0-1497-omap4 armv7l ApportVersion: 2.0.1-0ubuntu17.15 Architecture: armhf Date: Wed Mar 29 12:20:43 2017 MarkForUpload: True ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: audit UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.audit.audit.rules: [modified] mtime.conffile..etc.audit.audit.rules: 2017-03-29T12:19:33.699968 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1677363/+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 1449001] Re: systemd-resolved: please do not use Google public DNS by default
** Changed in: systemd (Ubuntu Artful) Status: Triaged => Fix Committed -- 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/1449001 Title: systemd-resolved: please do not use Google public DNS by default Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: New Status in systemd source package in Artful: Fix Committed Bug description: systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.) in the absence of other configured DNS servers. systemd-resolved is not enabled by default in Ubuntu 15.04, but it is installed by default and will behave in this way if enabled by the user. $ cat /etc/systemd/resolved.conf (...) # Entries in this file show the compile time defaults. (...) #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844 This raises privacy concerns since in the event of accidental misconfiguration DNS queries will be sent unencrypted across the internet, and potentially also security concerns given systemd- resolved does not perform DNSSEC validation and is not particularly well hardened against malicious responses e.g. from a MITM (http://www.openwall.com/lists/oss-security/2014/11/12/5). I believe that it would be better to fail safe if no DNS server is configured -- i.e. have DNS lookups fail; it's better that the user is aware of their misconfiguration, rather than silently sending their queries to Google. The user can intentionally opt to use Google public DNS if they wish. Steps to reproduce: 1. Remove existing DNS configuration (from /etc/network/interfaces, /etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*) 2. Reboot, or otherwise clear relevant state 3. sudo service systemd-resolved start 4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf 5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by default), observe that DNS lookups probably still work, and queries are being sent to one of Google's servers Possible workaround/bugfix: ship a resolved.conf which clears the FallbackDNS parameter. This issue has been discussed in the Debian BTS (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658). My interpretation of the Debian package maintainer's position is that a user concerned with the privacy implications shouldn't let systemd get into a state where it uses the fallback DNS servers (quoting Marco d'Itri: "Short summary: have a resolv.conf file or use DHCP"). I would argue that it's safest not to have fallback DNS servers configured at all by default. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1449001/+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 1666980] Re: cannot install click, missing python files
I believe the new version of click in yakkety-updates should no longer cause this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1666980 Title: cannot install click, missing python files Status in click package in Ubuntu: Incomplete Bug description: When I try to install click package, I get the following error: dpkg: click: dependency problems, but removing anyway as you requested: ubuntu-system-settings depends on click | ubuntu-snappy-cli; however: Package click is to be removed. Package ubuntu-snappy-cli is not installed. (Reading database ... 255714 files and directories currently installed.) Removing click (0.4.45.1+16.10.20160916-0ubuntu1) ... Traceback (most recent call last): File "/usr/bin/click", line 37, in import click ImportError: No module named 'click' dpkg: error processing package click (--remove): subprocess installed pre-removal script returned error exit status 1 Job for click-system-hooks.service failed because the control process exited with error code. See "systemctl status click-system-hooks.service" and "journalctl -xe" for details. click-system-hooks.service couldn't start. Errors were encountered while processing: click Script /usr/bin/click tries to import python module click, but it is missing. I suppose that this module should be included in *.deb package, but I cannot find it there. It seems that source code of required module is located here: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/vivid/click/vivid/files/head:/click/ as it contains submodule "commands" Ubuntu 16.10 click 0.4.45.1+16.10.20160916-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1666980/+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 1698734] Re: systemd-resolved spams syslog whenever I'm disconnected
** Changed in: systemd (Ubuntu Artful) Status: Confirmed => Fix Committed -- 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/1698734 Title: systemd-resolved spams syslog whenever I'm disconnected Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: New Status in systemd source package in Artful: Fix Committed Bug description: Every time I suspend my laptop and resume in a situation where I don't have connectivity I get big syslog spam from systemd-resolved. See for instance yesterday when I went out: Jun 18 18:48:16 chiron systemd[1]: Starting Suspend... Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS server 8.8.8.8. Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS server 8.8.4.4. Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS server 2001:4860:4860::. Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS server 2001:4860:4860::8844. ... And the last messages of the "episode": Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS server 8.8.8.8. Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS server 8.8.4.4. Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS server 2001:4860:4860::. Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS server 2001:4860:4860::8844. Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS server 8.8.8.8. Jun 18 20:13:28 chiron NetworkManager[30674]: [1497809608.0889] device (wlp2s0): supplicant interface state: associ ated -> 4-way handshake So this correspond to roughly 85 minutes of disconnection, during which I got... $ grep "fallback DNS" /var/log/syslog.1 | wc -l 444066 This correspond to 5224 messages/minute, 87 messages/second I had a few other episodes in the last week, including a 4h train roundtrip: $ zgrep "fallback DNS" /var/log/syslog* | wc -l 1964217 I noticed the bug during the trip, when the SSD activity was slowing my machine in a clearly noticeable way. I'm running: $ lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 $ apt-cache policy $(dpkg-query -S $(which systemd-resolve ) | awk '{print $1}') systemd: Installed: 232-21ubuntu3 Candidate: 232-21ubuntu3 Version table: *** 232-21ubuntu3 500 500 http://es.archive.ubuntu.com/ubuntu zesty-updates/main amd64 Packages 100 /var/lib/dpkg/status 232-21ubuntu2 500 500 http://es.archive.ubuntu.com/ubuntu zesty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1698734/+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 1646015] Re: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
I'm wondering what is the issue here. The "update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults" warning is completely harmless. Is anything broken in addition to this warning? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1646015 Title: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Status in audit package in Ubuntu: Confirmed Bug description: HI I have the docker image for ubuntu 16.04 and 16.10 . In both I was tried to install the auditd but getting the following error. apt-get install auditdReading package lists... Done Building dependency tree... Done The following additional packages will be installed: libauparse0 Suggested packages: audispd-plugins The following NEW packages will be installed: auditd libauparse0 0 upgraded, 2 newly installed, 0 to remove and 21 not upgraded. Need to get 224 kB of archives. After this operation, 753 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu yakkety/main amd64 libauparse0 amd64 1:2.6.6-1ubuntu1 [38.6 kB] Get:2 http://archive.ubuntu.com/ubuntu yakkety/main amd64 auditd amd64 1:2.6.6-1ubuntu1 [186 kB] Fetched 224 kB in 0s (409 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package libauparse0:amd64. (Reading database ... 6501 files and directories currently installed.) Preparing to unpack .../0-libauparse0_1%3a2.6.6-1ubuntu1_amd64.deb ... Unpacking libauparse0:amd64 (1:2.6.6-1ubuntu1) ... Selecting previously unselected package auditd. Preparing to unpack .../1-auditd_1%3a2.6.6-1ubuntu1_amd64.deb ... Unpacking auditd (1:2.6.6-1ubuntu1) ... Setting up libauparse0:amd64 (1:2.6.6-1ubuntu1) ... Setting up auditd (1:2.6.6-1ubuntu1) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults invoke-rc.d: could not determine current runlevel invoke-rc.d: policy-rc.d denied execution of start. Processing triggers for libc-bin (2.24-0ubuntu1) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1646015/+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 1689033] Re: A few missing icons in version 2.4.3
** Changed in: gdk-pixbuf Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1689033 Title: A few missing icons in version 2.4.3 Status in gdk-pixbuf: Incomplete Status in easytag package in Ubuntu: Confirmed Status in gdk-pixbuf package in Ubuntu: New Bug description: A few icons are missing in version 2.4.3 for zesty (and probably artful), see https://i.imgur.com/Cl4o36Sr.png To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1689033/+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 1376329] Re: readarray doesn't work with pipes
** Changed in: bash (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1376329 Title: readarray doesn't work with pipes Status in bash package in Ubuntu: Invalid Bug description: (echo one 1 ; echo two 2 ; echo three 3) > /tmp/foo #works readarray blah < /tmp/foo echo "${blah[@]}" # doesn't work: unset blah cat /tmp/foo | readarray blah echo "${blah[@]}" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1376329/+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 1621396] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1621396/+attachment/4900345/+files/ThreadStacktrace.txt ** Tags removed: apport-request-retrace -- 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/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Yakkety: Confirmed Status in systemd source package in Zesty: Fix Committed Bug description: [Impact] * Null-pointer dereference in resolved, results in resolved crash and reports on launchpad and errors. [Test Case] * Unknown steps to reproduce * Monitor the drop off in crashes on errors.ubuntu.com: https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 [Regression Potential] * The behavior is similar, instead of crashing resolved it returns an error in the relevant function. Whilst this may not result in correct dns resolution for the affected dns packets, it should not result in resolved crashes. [Original Bug Report] This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 233-6ubuntu2, the problem page at https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1604010] Re: sntp missing
Added a serverguide task to clean up the the mentioned section. Both should stay but split more clearly. Also FYI the merge of latest ntp is on the way which will bring sntp back as it should be for Artful and later. It is part of a new package there - not sure if this qualifies as an SRU or if we instead want to do different (or not). But lets finish the merge for the development release first. ** Also affects: serverguide Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1604010 Title: sntp missing Status in Ubuntu Server Guide: New Status in ntp package in Ubuntu: Triaged Status in ntp package in Debian: Fix Released Bug description: In Ubuntu 16.04, the binary file /usr/bin/sntp is missing from the package ntp. The associated man page /usr/share/man/man1/sntp.1.gz is still included. How to reproduce: $ sudo apt-get install ntp $ dpkg-query -L ntp | grep sntp /usr/share/man/man1/sntp.1.gz Expected result: /usr/bin/sntp was included in Ubuntu 14.04: $ dpkg-query -L ntp | grep sntp /usr/bin/sntp /usr/share/man/man1/sntp.1.gz The sntp program remains a very useful tool for interactively testing on the command line the offset of the local clock to a remote NTP server (like "ntpdate -qu [ntp-server]" previously). It should be included in the same package as its man page. To manage notifications about this bug go to: https://bugs.launchpad.net/serverguide/+bug/1604010/+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 1621396] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1621396/+attachment/4900344/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Yakkety: Confirmed Status in systemd source package in Zesty: Fix Committed Bug description: [Impact] * Null-pointer dereference in resolved, results in resolved crash and reports on launchpad and errors. [Test Case] * Unknown steps to reproduce * Monitor the drop off in crashes on errors.ubuntu.com: https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 [Regression Potential] * The behavior is similar, instead of crashing resolved it returns an error in the relevant function. Whilst this may not result in correct dns resolution for the affected dns packets, it should not result in resolved crashes. [Original Bug Report] This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 233-6ubuntu2, the problem page at https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1621396] Dependencies.txt
** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1621396/+attachment/4900342/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Yakkety: Confirmed Status in systemd source package in Zesty: Fix Committed Bug description: [Impact] * Null-pointer dereference in resolved, results in resolved crash and reports on launchpad and errors. [Test Case] * Unknown steps to reproduce * Monitor the drop off in crashes on errors.ubuntu.com: https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 [Regression Potential] * The behavior is similar, instead of crashing resolved it returns an error in the relevant function. Whilst this may not result in correct dns resolution for the affected dns packets, it should not result in resolved crashes. [Original Bug Report] This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 233-6ubuntu2, the problem page at https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1621396] ProcMaps.txt
** Attachment added: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1621396/+attachment/4900343/+files/ProcMaps.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Yakkety: Confirmed Status in systemd source package in Zesty: Fix Committed Bug description: [Impact] * Null-pointer dereference in resolved, results in resolved crash and reports on launchpad and errors. [Test Case] * Unknown steps to reproduce * Monitor the drop off in crashes on errors.ubuntu.com: https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 [Regression Potential] * The behavior is similar, instead of crashing resolved it returns an error in the relevant function. Whilst this may not result in correct dns resolution for the affected dns packets, it should not result in resolved crashes. [Original Bug Report] This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 233-6ubuntu2, the problem page at https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1200296] Re: [MIR] spice-vdagent
Please also make sure to update ubuntu-meta / seed; if nothing brings in the package, it won't stay in main. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1200296 Title: [MIR] spice-vdagent Status in spice-vdagent package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Availability Built for all supported architectures. In sync with Debian except for one cherry-picked patch to hide spice- vdagent from Startup Applications. Rationale = "spice-vdagent adds some nice features to guest systems running over SPICE: copy and paste between guest and host, arbitrary resolution support, ... It's also very tiny (40kB compressed, less than 200kB installed) and won't startup when not running in a SPICE guest. Shipping it on the desktop ISOs will improve the user experience when using SPICE (eg in GNOME Boxes), and will have no impact on other use cases, so it would be really nice to add this package to the ISO." Ubuntu GNOME 16.10 and 17.04 included it in the default install. Security No known open security vulnerabilities. https://rhn.redhat.com/errata/RHSA-2013-0924.html (CVE-2013-2152) Quality assurance = Bug subscriber: Ubuntu Desktop Bugs? or Ubuntu Server since they watch other spice packages? https://bugs.launchpad.net/ubuntu/+source/spice-vdagent https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=spice-vdagent https://bugs.freedesktop.org/buglist.cgi?bug_status=__open__&component=unix agent&product=Spice No tests. Dependencies check-mir reports all other binary dependencies are in main Standards compliance 3.9.8 Maintenance === - Actively developed upstream https://cgit.freedesktop.org/spice/linux/vd_agent/log/ https://anonscm.debian.org/git/collab-maint/spice-vdagent.git - Maintained in Debian by the same Debian Developer who maintains the other Spice packages. short dh7 style rules, dh compat 10 Background information == N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1200296/+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 1200296] Re: [MIR] spice-vdagent
The package in general looks fine, properly maintained in Debian, and low effort to maintain in Ubuntu; so this part looks fine for the MIR. However, spice-vdagent is missing a team subscriber; please fix this. Finally, given the use of spice-vdagent to capture mouse and such, its tight integration with ConsoleKit for session handling, its clipboard capture, and mucking with X, randr, etc., this will require a review by the Security Team. ** Changed in: spice-vdagent (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1200296 Title: [MIR] spice-vdagent Status in spice-vdagent package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Availability Built for all supported architectures. In sync with Debian except for one cherry-picked patch to hide spice- vdagent from Startup Applications. Rationale = "spice-vdagent adds some nice features to guest systems running over SPICE: copy and paste between guest and host, arbitrary resolution support, ... It's also very tiny (40kB compressed, less than 200kB installed) and won't startup when not running in a SPICE guest. Shipping it on the desktop ISOs will improve the user experience when using SPICE (eg in GNOME Boxes), and will have no impact on other use cases, so it would be really nice to add this package to the ISO." Ubuntu GNOME 16.10 and 17.04 included it in the default install. Security No known open security vulnerabilities. https://rhn.redhat.com/errata/RHSA-2013-0924.html (CVE-2013-2152) Quality assurance = Bug subscriber: Ubuntu Desktop Bugs? or Ubuntu Server since they watch other spice packages? https://bugs.launchpad.net/ubuntu/+source/spice-vdagent https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=spice-vdagent https://bugs.freedesktop.org/buglist.cgi?bug_status=__open__&component=unix agent&product=Spice No tests. Dependencies check-mir reports all other binary dependencies are in main Standards compliance 3.9.8 Maintenance === - Actively developed upstream https://cgit.freedesktop.org/spice/linux/vd_agent/log/ https://anonscm.debian.org/git/collab-maint/spice-vdagent.git - Maintained in Debian by the same Debian Developer who maintains the other Spice packages. short dh7 style rules, dh compat 10 Background information == N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1200296/+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 1408092] Re: sysconfig.get_path('purelib') points to site-packages directory
In fact looking at /usr/lib/python3.4/distutils/sysconfig.py, it appears the fix is quite easy. In get_python_inc(), the variable `python_dir = python_dir = 'python' + get_python_version() + build_flags` is used to build the path. However, in get_python_lib(), "python3" is a hard-coded string: `return os.path.join(prefix, "lib", "python3", "dist-packages")` This is a special case for the value of prefix if it's something like /usr/local.. Currently to get around this I am forced to provide a fake argument to `prefix` and then doing a string replace for /usr/local, which is just silly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1408092 Title: sysconfig.get_path('purelib') points to site-packages directory Status in python3-defaults package in Ubuntu: Confirmed Status in python3.5 package in Ubuntu: Confirmed Bug description: purelib and platlib paths in Python 3 sysconfig module point to site- packages directory: $ python3 -m sysconfig Platform: "linux-x86_64" Python version: "3.4" Current installation scheme: "posix_prefix" Paths: data = "/usr" include = "/usr/include/python3.4m" platinclude = "/usr/include/python3.4m" platlib = "/usr/lib/python3.4/site-packages" platstdlib = "/usr/lib/python3.4" purelib = "/usr/lib/python3.4/site-packages" scripts = "/usr/bin" stdlib = "/usr/lib/python3.4" ... whereas Python 2 points to dist-packages: Platform: "linux-x86_64" Python version: "2.7" Current installation scheme: "posix_local" Paths: data = "/usr/local" include = "/usr/local/include/python2.7" platinclude = "/usr/local/include/python2.7" platlib = "/usr/local/lib/python2.7/dist-packages" platstdlib = "/usr/lib/python2.7" purelib = "/usr/local/lib/python2.7/dist-packages" scripts = "/usr/local/bin" stdlib = "/usr/lib/python2.7" ... One severe consequence of this is that automake is installing Python modules to a location which is not in sys.path, namely site-packages directory. When one uses automake to create a Makefile that installs a Python module to the system, it is installed into /usr/local/lib/python3.4 /site-packages since automake/aclocal uses sysconfig to determine where the package will be installed. From /usr/share/aclocal-1.14/python.m4 file: AC_CACHE_CHECK([for $am_display_PYTHON script directory], [am_cv_python_pythondir], [if test "x$prefix" = xNONE then am_py_prefix=$ac_default_prefix else am_py_prefix=$prefix fi am_cv_python_pythondir=`$PYTHON -c " $am_python_setup_sysconfig if can_use_sysconfig: sitedir = sysconfig.get_path('purelib', vars={'base':'$am_py_prefix'}) <--- else: from distutils import sysconfig ... Here, it can be seen that automake uses purelib path defined by the sysconfig module of Python. However, since this path is not included in sys.path, and thus the installed package cannot be used: $ python3 -c "import sys; print(sys.path)" ['', '/usr/lib/python3.4', '/usr/lib/python3.4/plat-x86_64-linux-gnu', '/usr/lib/python3.4/lib-dynload', '/usr/local/lib/python3.4/dist-packages', '/usr/lib/python3/dist-packages'] Ubuntu version:14.10 $ apt-cache policy python3-minimal python3-minimal: Installed: 3.4.2-1 Candidate: 3.4.2-1 Version table: *** 3.4.2-1 0 500 http://mirror.23media.de/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1408092/+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 1621396] Updated stack trace from duplicate bug 1699527
Package: systemd 232-21ubuntu3 ProcCmdline: /lib/systemd/systemd-resolved -- 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/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Yakkety: Confirmed Status in systemd source package in Zesty: Fix Committed Bug description: [Impact] * Null-pointer dereference in resolved, results in resolved crash and reports on launchpad and errors. [Test Case] * Unknown steps to reproduce * Monitor the drop off in crashes on errors.ubuntu.com: https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 [Regression Potential] * The behavior is similar, instead of crashing resolved it returns an error in the relevant function. Whilst this may not result in correct dns resolution for the affected dns packets, it should not result in resolved crashes. [Original Bug Report] This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 233-6ubuntu2, the problem page at https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1699527] Re: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
*** This bug is a duplicate of bug 1621396 *** https://bugs.launchpad.net/bugs/1621396 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1621396, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1699527/+attachment/4900322/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1699527/+attachment/4900325/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1699527/+attachment/4900332/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1699527/+attachment/4900334/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1699527/+attachment/4900335/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1699527/+attachment/4900337/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1699527/+attachment/4900340/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1621396 systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1699527 Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() Status in systemd package in Ubuntu: New Bug description: Not sure what happened. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed Jun 21 08:55:28 2017 ExecutablePath: /lib/systemd/systemd-resolved MachineType: System76, Inc. Galago UltraPro ProcCmdline: /lib/systemd/systemd-resolved ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic root=UUID=9a35e457-d298-41c4-9274-a5e8eb9f78c5 ro i915.disable_power_well=0 quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-232.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-232.so sd_event_run () from /lib/systemd/libsystemd-shared-232.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to zesty on 2017-04-18 (63 days ago) UserGroups: dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699527/+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 1408092] Re: sysconfig.get_path('purelib') points to site-packages directory
Hello, yes this last issue (distutils.sysconfig) is causing a problem on a project I work on, so I'd like to confirm as well. It appears to have been previously brought up here without reply: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2016-October/017005.html I am seeing the issue on Ubuntu 17.04 so it seems this bug has not been fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1408092 Title: sysconfig.get_path('purelib') points to site-packages directory Status in python3-defaults package in Ubuntu: Confirmed Status in python3.5 package in Ubuntu: Confirmed Bug description: purelib and platlib paths in Python 3 sysconfig module point to site- packages directory: $ python3 -m sysconfig Platform: "linux-x86_64" Python version: "3.4" Current installation scheme: "posix_prefix" Paths: data = "/usr" include = "/usr/include/python3.4m" platinclude = "/usr/include/python3.4m" platlib = "/usr/lib/python3.4/site-packages" platstdlib = "/usr/lib/python3.4" purelib = "/usr/lib/python3.4/site-packages" scripts = "/usr/bin" stdlib = "/usr/lib/python3.4" ... whereas Python 2 points to dist-packages: Platform: "linux-x86_64" Python version: "2.7" Current installation scheme: "posix_local" Paths: data = "/usr/local" include = "/usr/local/include/python2.7" platinclude = "/usr/local/include/python2.7" platlib = "/usr/local/lib/python2.7/dist-packages" platstdlib = "/usr/lib/python2.7" purelib = "/usr/local/lib/python2.7/dist-packages" scripts = "/usr/local/bin" stdlib = "/usr/lib/python2.7" ... One severe consequence of this is that automake is installing Python modules to a location which is not in sys.path, namely site-packages directory. When one uses automake to create a Makefile that installs a Python module to the system, it is installed into /usr/local/lib/python3.4 /site-packages since automake/aclocal uses sysconfig to determine where the package will be installed. From /usr/share/aclocal-1.14/python.m4 file: AC_CACHE_CHECK([for $am_display_PYTHON script directory], [am_cv_python_pythondir], [if test "x$prefix" = xNONE then am_py_prefix=$ac_default_prefix else am_py_prefix=$prefix fi am_cv_python_pythondir=`$PYTHON -c " $am_python_setup_sysconfig if can_use_sysconfig: sitedir = sysconfig.get_path('purelib', vars={'base':'$am_py_prefix'}) <--- else: from distutils import sysconfig ... Here, it can be seen that automake uses purelib path defined by the sysconfig module of Python. However, since this path is not included in sys.path, and thus the installed package cannot be used: $ python3 -c "import sys; print(sys.path)" ['', '/usr/lib/python3.4', '/usr/lib/python3.4/plat-x86_64-linux-gnu', '/usr/lib/python3.4/lib-dynload', '/usr/local/lib/python3.4/dist-packages', '/usr/lib/python3/dist-packages'] Ubuntu version:14.10 $ apt-cache policy python3-minimal python3-minimal: Installed: 3.4.2-1 Candidate: 3.4.2-1 Version table: *** 3.4.2-1 0 500 http://mirror.23media.de/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1408092/+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 1657646] Re: Missing thin-provisioning-tools prevents VG with thin pool LV from being (de)activated, but not its creation
I'm marking this bug as "new" again because of the package change (from docker.io to lvm2), to allow it to be triaged again in this new context. ** Changed in: lvm2 (Ubuntu) Status: Triaged => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1657646 Title: Missing thin-provisioning-tools prevents VG with thin pool LV from being (de)activated, but not its creation Status in lvm2 package in Ubuntu: New Bug description: Creating a thin pool LV is allowed even when thin-provisioning-tools is not installed. But deactivating or activating that VG fails. Since deactivating the VG usually only happens at reboot, the user might fail to notice this big problem until then. I think the lvconvert tool, used to combine the two "thin LVs" into a thin pool LV, should refuse to run if thin-provisioning-tools, or the needed scripts, aren't installed. Steps to reproduce: root@15-89:~# vgcreate vg /dev/vdb1 Volume group "vg" successfully created root@15-89:~# vgs VG #PV #LV #SN Attr VSize VFree vg 1 0 0 wz--n- 40.00g 40.00g root@15-89:~# lvcreate -n pool0 -l 90%VG vg Logical volume "pool0" created. root@15-89:~# lvcreate -n pool0meta -l 5%VG vg Logical volume "pool0meta" created. root@15-89:~# lvs LVVG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert pool0 vg -wi-a- 36.00g pool0meta vg -wi-a- 2.00g root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 100 Jun 21 14:15 ./ drwxr-xr-x 20 root root3820 Jun 21 14:15 ../ crw--- 1 root root 10, 236 Jun 21 13:15 control lrwxrwxrwx 1 root root 7 Jun 21 14:14 vg-pool0 -> ../dm-0 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0meta -> ../dm-1 root@15-89:~# lvconvert --type thin-pool --poolmetadata vg/pool0meta vg/pool0 WARNING: Converting logical volume vg/pool0 and vg/pool0meta to pool's data and metadata volumes. THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.) Do you really want to convert vg/pool0 and vg/pool0meta? [y/n]: y Converted vg/pool0 to thin pool. root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 120 Jun 21 14:15 ./ drwxr-xr-x 20 root root3840 Jun 21 14:15 ../ crw--- 1 root root 10, 236 Jun 21 13:15 control lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0_tdata -> ../dm-1 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0_tmeta -> ../dm-0 root@15-89:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%S ync Convert [lvol0_pmspare] vg ewi--- 2.00g pool0 vg twi-a-tz-- 36.00g 0.00 0.01 [pool0_tdata] vg Twi-ao 36.00g [pool0_tmeta] vg ewi-ao 2.00g If you now reboot the system, all that is gone: root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 60 Jun 21 14:28 ./ drwxr-xr-x 19 root root3760 Jun 21 14:28 ../ crw--- 1 root root 10, 236 Jun 21 14:28 control The same happens if you deactivate the VG (which the reboot undoubtedly triggers). It fails because of a missing /usr/sbin/thin_check which is provided by the thin-provisioning-tools package: root@15-89:~# vgchange -a n /usr/sbin/thin_check: execvp failed: No such file or directory WARNING: Integrity check of metadata for pool vg/pool0 failed. 0 logical volume(s) in volume group "vg" now active root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 60 Jun 21 14:29 ./ drwxr-xr-x 19 root root3760 Jun 21 14:29 ../ crw--- 1 root root 10, 236 Jun 21 14:28 control To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1657646/+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 1657646] Re: Missing thin-provisioning-tools prevent VG from being (de)activated
** Summary changed: - Missing thin-provisioning-tools prevent VG from being activated + Missing thin-provisioning-tools prevent VG from being (de)activated ** Description changed: - I had configured thin-pool storage driver for docker on one of the PowerVM lapr. And had created containers. - These containers were running STAF tests. I had to reboot the partition. After reboot, i see the docker daemon failed to come up. Below are the details, + Creating a thin pool LV is allowed even when thin-provisioning-tools is + not installed. But deactivating, or activating, the VG fails. - Steps - - 1. Instal 16.04.02 on a vm partition. - 2. Install docker.io - 3. Configure a thin-pool storage driver for docker daemon. - 4. Create some sample containers. - 5. Reboot the vm partition. + I think the lvconvert tool, used to combine the two "thin LVs" into a + thin pool LV, should refuse to run if thin-provisioning-tools isn't + installed. - Docker daemon fails to come up. + Steps to reproduce: + root@15-89:~# vgcreate vg /dev/vdb1 + Volume group "vg" successfully created - Logs - - Machine details - - Kernel Build: 4.4.0-53-generic - System Name : bamlp4 - Model/Type : 8247-22L - Platform: powerpc64le + root@15-89:~# vgs + VG #PV #LV #SN Attr VSize VFree + vg 1 0 0 wz--n- 40.00g 40.00g - uname -a - Linux bamlp4 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:36 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux + root@15-89:~# lvcreate -n pool0 -l 90%VG vg + Logical volume "pool0" created. - Docker details- - root@bamlp4:~# docker info - Containers: 4 - Running: 3 - Paused: 0 - Stopped: 1 - Images: 4 - Server Version: 1.12.1 - Storage Driver: devicemapper - Pool Name: docker--storage-thinpool - Pool Blocksize: 65.54 kB - Base Device Size: 10.74 GB - Backing Filesystem: xfs - Data file: - Metadata file: - Data Space Used: 12.02 GB - Data Space Total: 20.4 GB - Data Space Available: 8.373 GB - Metadata Space Used: 9.466 MB - Metadata Space Total: 213.9 MB - Metadata Space Available: 204.4 MB - Thin Pool Minimum Free Space: 2.04 GB - Udev Sync Supported: true - Deferred Removal Enabled: false - Deferred Deletion Enabled: false - Deferred Deleted Device Count: 0 - Library Version: 1.02.110 (2015-10-30) - Logging Driver: json-file - Cgroup Driver: cgroupfs - Plugins: - Volume: local - Network: null bridge host overlay - Swarm: inactive - Runtimes: runc - Default Runtime: runc - Security Options: apparmor - Kernel Version: 4.4.0-53-generic - Operating System: Ubuntu 16.04.1 LTS - OSType: linux - Architecture: ppc64le - CPUs: 36 - Total Memory: 90.91 GiB - Name: bamlp4 - ID: BS55:FI5I:4KNB:33H7:ZUAC:AXIU:AOQ4:2PST:22Y7:TNW7:GYT6:WX7A - Docker Root Dir: /var/lib/docker - Debug Mode (client): false - Debug Mode (server): false - Registry: https://index.docker.io/v1/ - WARNING: No swap limit support - Insecure Registries: - 127.0.0.0/8 - root@bamlp4:~# + root@15-89:~# lvcreate -n pool0meta -l 5%VG vg + Logical volume "pool0meta" created. - docker info |grep Udev - Udev Sync Supported: true - WARNING: No swap limit support + root@15-89:~# lvs + LVVG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert + pool0 vg -wi-a- 36.00g + pool0meta vg -wi-a- 2.00g + + root@15-89:~# ll /dev/mapper/ + total 0 + drwxr-xr-x 2 root root 100 Jun 21 14:15 ./ + drwxr-xr-x 20 root root3820 Jun 21 14:15 ../ + crw--- 1 root root 10, 236 Jun 21 13:15 control + lrwxrwxrwx 1 root root 7 Jun 21 14:14 vg-pool0 -> ../dm-0 + lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0meta -> ../dm-1 + + root@15-89:~# lvconvert --type thin-pool --poolmetadata vg/pool0meta vg/pool0 + WARNING: Converting logical volume vg/pool0 and vg/pool0meta to pool's data and metadata volumes. + THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.) + Do you really want to convert vg/pool0 and vg/pool0meta? [y/n]: y + Converted vg/pool0 to thin pool. + + root@15-89:~# ll /dev/mapper/ + total 0 + drwxr-xr-x 2 root root 120 Jun 21 14:15 ./ + drwxr-xr-x 20 root root3840 Jun 21 14:15 ../ + crw--- 1 root root 10, 236 Jun 21 13:15 control + lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0 -> ../dm-2 + lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0_tdata -> ../dm-1 + lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0_tmeta -> ../dm-0 + root@15-89:~# lvs -a + LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert + [lvol0_pmspare] vg ewi--- 2.00g + pool0 vg twi-a-tz-- 36.00g 0.00 0.01 + [pool0_tdata] vg Twi-ao 36.00g + [pool0_tmeta] vg ewi-ao 2.00g
[Touch-packages] [Bug 1686344] Re: Mesa 17.0.x stable release
tested to be fine on Intel Kabylake GT3 and AMD R7 260X (Bonaire) -- 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/1686344 Title: Mesa 17.0.x stable release Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Zesty: Fix Committed Bug description: [Impact] Mesa stable release for zesty & backport to xenial. Xenial needs newer libdrm from zesty. These are part of the hwe-16.04 stack refresh. [Test case] Install, run desktop session, test xonotic. the important hw drivers to test: - i965 (Intel) - radeonsi (AMD) [Regression potential] Spec compliance test suites are already run by Intel and others, so feature regressions should not be possible. GLESv1 support has been dropped from the packaging though, but packages that depend on libgles1-mesa have been pushed to proposed to drop the dependency, see bug 1676845 (applies to xenial). 17.0.x has been available for xenial and yakkety users for a while, and so far no-one has complained about driver regressions. [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1686344/+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 1697891] Re: SSH X11 forwarding broken on Zesty
*** This bug is a duplicate of bug 882878 *** https://bugs.launchpad.net/bugs/882878 ** Changed in: openssh (Ubuntu) Status: Invalid => New ** Summary changed: - SSH X11 forwarding broken on Zesty + SSH X11 forwarding broken on Xenial When IPv6 is disabled ** This bug has been marked a duplicate of bug 882878 With IPv6 disabled, openssh will not forward X connections -- 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/1697891 Title: SSH X11 forwarding broken on Xenial When IPv6 is disabled Status in openssh package in Ubuntu: New Bug description: ouroumov@Edge:~$ ssh -X ouroumov@10.42.0.1 pluma ouroumov@10.42.0.1's password: X11 forwarding request failed on channel 0 (pluma:30718): Gtk-WARNING **: cannot open display: ouroumov@Edge:~$ This used to work in 16.04. This is problematic because among other things, it prevents one from using x2x. Note: in this experiment, the ssh command is executed on a Zesty client, and the target is a Xenial Server ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ssh 1:7.4p1-10 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed Jun 14 10:39:17 2017 InstallationDate: Installed on 2017-04-05 (70 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1697891/+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 1699519] Re: package linux-image-extra-4.4.0-79-generic 4.4.0-79.100 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 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/1699519 Title: package linux-image-extra-4.4.0-79-generic 4.4.0-79.100 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Just had notification about system problem with no details. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-79-generic 4.4.0-79.100 ProcVersionSignature: Ubuntu 4.4.0-82.105-generic 4.4.70 Uname: Linux 4.4.0-82-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.7 AptOrdering: linux-headers-4.4.0-79-generic: Remove linux-headers-4.4.0-79: Remove linux-image-extra-4.4.0-79-generic: Remove linux-image-4.4.0-79-generic: Remove NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wayne 1870 F pulseaudio Date: Wed Jun 21 10:21:25 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=7fc64e3c-6cfa-4c1f-9988-fb544d761dac InstallationDate: Installed on 2016-12-17 (185 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire 5733Z ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-82-generic root=UUID=56c8a1ca-2097-4f05-ac45-97f85b1480c9 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-79-generic 4.4.0-79.100 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5733Z dmi.board.vendor: Acer dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnAcer:bvrV1.07:bd11/07/2011:svnAcer:pnAspire5733Z:pvrV1.07:rvnAcer:rnAspire5733Z:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.name: Aspire 5733Z dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1699519/+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 1699519] [NEW] package linux-image-extra-4.4.0-79-generic 4.4.0-79.100 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Just had notification about system problem with no details. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-79-generic 4.4.0-79.100 ProcVersionSignature: Ubuntu 4.4.0-82.105-generic 4.4.70 Uname: Linux 4.4.0-82-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.7 AptOrdering: linux-headers-4.4.0-79-generic: Remove linux-headers-4.4.0-79: Remove linux-image-extra-4.4.0-79-generic: Remove linux-image-4.4.0-79-generic: Remove NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wayne 1870 F pulseaudio Date: Wed Jun 21 10:21:25 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=7fc64e3c-6cfa-4c1f-9988-fb544d761dac InstallationDate: Installed on 2016-12-17 (185 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire 5733Z ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-82-generic root=UUID=56c8a1ca-2097-4f05-ac45-97f85b1480c9 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-79-generic 4.4.0-79.100 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5733Z dmi.board.vendor: Acer dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnAcer:bvrV1.07:bd11/07/2011:svnAcer:pnAspire5733Z:pvrV1.07:rvnAcer:rnAspire5733Z:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.name: Aspire 5733Z dmi.product.version: V1.07 dmi.sys.vendor: Acer ** 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/1699519 Title: package linux-image-extra-4.4.0-79-generic 4.4.0-79.100 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Just had notification about system problem with no details. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-79-generic 4.4.0-79.100 ProcVersionSignature: Ubuntu 4.4.0-82.105-generic 4.4.70 Uname: Linux 4.4.0-82-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.7 AptOrdering: linux-headers-4.4.0-79-generic: Remove linux-headers-4.4.0-79: Remove linux-image-extra-4.4.0-79-generic: Remove linux-image-4.4.0-79-generic: Remove NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wayne 1870 F pulseaudio Date: Wed Jun 21 10:21:25 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=7fc64e3c-6cfa-4c1f-9988-fb544d761dac InstallationDate: Installed on 2016-12-17 (185 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire 5733Z ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-82-generic root=UUID=56c8a1ca-2097-4f05-ac45-97f85b1480c9 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-79-generic 4.4.0-79.100 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5733Z dmi.board.vendor: Acer dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnAcer:bvrV1.07:bd11/07/2011:svnAcer:pnAspire5733Z:pvrV1.07:rvnAcer:rnAspire5733Z:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.name: Aspire 5733Z dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1699519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages
[Touch-packages] [Bug 882878] Re: With IPv6 disabled, openssh will not forward X connections
I'm affected by this on Xenial. ** Tags added: xenial -- 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/882878 Title: With IPv6 disabled, openssh will not forward X connections Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Status in openssh package in openSUSE: Confirmed Bug description: If you disable IPv6 in /etc/sysctl.conf sshd will not forward X11. It logs the failue in /var/log/auth.log Oct 27 18:49:26 uscps002 sshd[14722]: Accepted password for root from 172.20.10.50 port 60322 ssh2 Oct 27 18:49:26 uscps002 sshd[14722]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 27 18:49:27 uscps002 sshd[14722]: error: Failed to allocate internet-domain X11 display socket. Aparently the compiled sshd version will not try an ipv4 localhost if an ipv6 localhost does not exist. Placing the following line in /etc/ssh/sshd_config fixes the issue X11UseLocalHost no root@uscps002:/var/log# lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 root@uscps002:/var/log# root@uscps002:/var/log# uname -a Linux uscps002 3.0.0-12-server #20-Ubuntu SMP Fri Oct 7 16:36:30 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/882878/+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 1657646] [NEW] Missing thin-provisioning-tools prevent VG from being (de)activated
You have been subscribed to a public bug: Creating a thin pool LV is allowed even when thin-provisioning-tools is not installed. But deactivating, or activating, the VG fails. I think the lvconvert tool, used to combine the two "thin LVs" into a thin pool LV, should refuse to run if thin-provisioning-tools isn't installed. Steps to reproduce: root@15-89:~# vgcreate vg /dev/vdb1 Volume group "vg" successfully created root@15-89:~# vgs VG #PV #LV #SN Attr VSize VFree vg 1 0 0 wz--n- 40.00g 40.00g root@15-89:~# lvcreate -n pool0 -l 90%VG vg Logical volume "pool0" created. root@15-89:~# lvcreate -n pool0meta -l 5%VG vg Logical volume "pool0meta" created. root@15-89:~# lvs LVVG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert pool0 vg -wi-a- 36.00g pool0meta vg -wi-a- 2.00g root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 100 Jun 21 14:15 ./ drwxr-xr-x 20 root root3820 Jun 21 14:15 ../ crw--- 1 root root 10, 236 Jun 21 13:15 control lrwxrwxrwx 1 root root 7 Jun 21 14:14 vg-pool0 -> ../dm-0 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0meta -> ../dm-1 root@15-89:~# lvconvert --type thin-pool --poolmetadata vg/pool0meta vg/pool0 WARNING: Converting logical volume vg/pool0 and vg/pool0meta to pool's data and metadata volumes. THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.) Do you really want to convert vg/pool0 and vg/pool0meta? [y/n]: y Converted vg/pool0 to thin pool. root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 120 Jun 21 14:15 ./ drwxr-xr-x 20 root root3840 Jun 21 14:15 ../ crw--- 1 root root 10, 236 Jun 21 13:15 control lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0_tdata -> ../dm-1 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0_tmeta -> ../dm-0 root@15-89:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert [lvol0_pmspare] vg ewi--- 2.00g pool0 vg twi-a-tz-- 36.00g 0.00 0.01 [pool0_tdata] vg Twi-ao 36.00g [pool0_tmeta] vg ewi-ao 2.00g If you now reboot the system, all that is gone: root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 60 Jun 21 14:28 ./ drwxr-xr-x 19 root root3760 Jun 21 14:28 ../ crw--- 1 root root 10, 236 Jun 21 14:28 control The same happens if you deactivate the VG (which the reboot undoubtedly triggers). It fails because of a missing /usr/sbin/thin_check which is provided by the thin-provisioning-tools package: root@15-89:~# vgchange -a n /usr/sbin/thin_check: execvp failed: No such file or directory WARNING: Integrity check of metadata for pool vg/pool0 failed. 0 logical volume(s) in volume group "vg" now active root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 60 Jun 21 14:29 ./ drwxr-xr-x 19 root root3760 Jun 21 14:29 ../ crw--- 1 root root 10, 236 Jun 21 14:28 control ** Affects: lvm2 (Ubuntu) Importance: High Status: Triaged ** Tags: architecture-ppc64le bugnameltc-150003 severity-high targetmilestone-inin16042 -- Missing thin-provisioning-tools prevent VG from being (de)activated https://bugs.launchpad.net/bugs/1657646 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d
** Patch added: "rsyslog-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900273/+files/rsyslog-xenial.debdiff ** Tags removed: sts-sponsor ** Tags added: sts-sru-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1668639 Title: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d Status in rsyslog package in Ubuntu: New Status in rsyslog source package in Trusty: New Status in rsyslog source package in Xenial: New Status in rsyslog source package in Yakkety: New Status in rsyslog package in Debian: Fix Released Bug description: [Impact] Servers or cloud instances will not log important messages after initial deployment. Manual reboot or restart of services is necessary to get expected behaviour. [Test Case] 1) Install, enable and start haproxy 2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed 3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT created 4) Restart rsyslog service 5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created 6) Restart haproxy service and observe that log now is filled with entries With the patched deb steps 3,4 and 6 becomes irrelevant and everything works out of the box. [Regression Potential] Minimal. This patch merges a patch from Debian where a trigger is added to the rsyslog package that fires when other debs drop files into /etc/rsyslog.d. [Original Bug Description] rsyslog should reload its configuration when other packages drop configuration in /etc/rsyslog.d https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337 https://anonscm.debian.org/cgit/collab- maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+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 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d
** Patch added: "rsyslog-zesty.debdiff" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900271/+files/rsyslog-zesty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1668639 Title: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d Status in rsyslog package in Ubuntu: New Status in rsyslog source package in Trusty: New Status in rsyslog source package in Xenial: New Status in rsyslog source package in Yakkety: New Status in rsyslog package in Debian: Fix Released Bug description: [Impact] Servers or cloud instances will not log important messages after initial deployment. Manual reboot or restart of services is necessary to get expected behaviour. [Test Case] 1) Install, enable and start haproxy 2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed 3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT created 4) Restart rsyslog service 5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created 6) Restart haproxy service and observe that log now is filled with entries With the patched deb steps 3,4 and 6 becomes irrelevant and everything works out of the box. [Regression Potential] Minimal. This patch merges a patch from Debian where a trigger is added to the rsyslog package that fires when other debs drop files into /etc/rsyslog.d. [Original Bug Description] rsyslog should reload its configuration when other packages drop configuration in /etc/rsyslog.d https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337 https://anonscm.debian.org/cgit/collab- maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+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 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d
** Patch added: "rsyslog-yakkety.debdiff" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900272/+files/rsyslog-yakkety.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1668639 Title: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d Status in rsyslog package in Ubuntu: New Status in rsyslog source package in Trusty: New Status in rsyslog source package in Xenial: New Status in rsyslog source package in Yakkety: New Status in rsyslog package in Debian: Fix Released Bug description: [Impact] Servers or cloud instances will not log important messages after initial deployment. Manual reboot or restart of services is necessary to get expected behaviour. [Test Case] 1) Install, enable and start haproxy 2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed 3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT created 4) Restart rsyslog service 5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created 6) Restart haproxy service and observe that log now is filled with entries With the patched deb steps 3,4 and 6 becomes irrelevant and everything works out of the box. [Regression Potential] Minimal. This patch merges a patch from Debian where a trigger is added to the rsyslog package that fires when other debs drop files into /etc/rsyslog.d. [Original Bug Description] rsyslog should reload its configuration when other packages drop configuration in /etc/rsyslog.d https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337 https://anonscm.debian.org/cgit/collab- maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+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 1695403] Re: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: hicolor-icon-theme (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1695403 Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in hicolor-icon-theme package in Ubuntu: Confirmed Bug description: no more info ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 Date: Fri Jun 2 19:08:58 2017 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-05-10 (754 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2017-06-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1695403/+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 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop
Have a similar issue with my HP Pavilion DV6 Laptop under both Ubuntu 16.04 and Ubuntu Mate 16.04 using pulse audio. Video still displays out of HDMI port to TV but Audio hardware device disappears from sound applet (in my case "mate-volume-control-applet"). Curiously the HDMI device is visible at some level to aplay $ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: 92HD81B1X5 Analog [92HD81B1X5 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 Work-Around (temporarily SOLVES issue ... until the next time) --- I have developed the following work-around (for Mate ... but you can adapt it to standard Ubuntu) that recovers the HDMI sound (perhaps it may help users get by and/or some smart developer to track down the root cause):- Step 0: Open your terminal ... Step 1: Kill the (non-detecting) volume control process $ kill -9 $(ps aux |grep -v 'sudo\|grep' |grep -e "mate-volume-control-applet"| awk {'print $2'}) Step 2: Relaunch the volume-control process $ sudo mate-volume-control-applet Step 3: Then at the blinking terminal type ^Z Step 4: Now complete the manual terminal tty disassociation by typing $ bg Step 5: Now when you right click on your "mate-volume-control-applet" go to > Sound Preferences > Hardware Tab > Profile Drop Down ... should now show all the available sound devices including the HDMI output to the TV. --- The volume control applet just seems to forget about the sound hardware, never refreshes nor updates even with the HDMI lead being disconnected and reconnected. -- 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/1377653 Title: HDMI sound output not detected / NVIDIA optimus laptop Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Hi, not sure if this is an alsa or nvidia/nouveau bug. HDMI audio output doesn't appear in sound settings output panel. Audio works well on internal speakers, but it seems there is no way to make it output to hdmi... The laptop has optimus NVIDIA+Intel. The behaviour is the same with nouveau or nvidia proprietary driver. Please let me know if further testing is required ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam2295 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun Oct 5 17:05:35 2014 InstallationDate: Installed on 2014-04-21 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.215 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+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