[Touch-packages] [Bug 1688689] Re: Owner and group of few files and folders from Bind directory visible as nobody/nogroup within nspawn container
https://github.com/systemd/systemd/issues/5900#issuecomment-300362005 ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1688689 Title: Owner and group of few files and folders from Bind directory visible as nobody/nogroup within nspawn container Status in systemd: New Status in systemd package in Ubuntu: Invalid Bug description: Owner and group of few files and folders from Bind directory visible as nobody/nogroup when I check permission from within nspawn container. Create testing.nspawn: [Files] Bind=/patch/to/folder Use some folder with many subfolders, to expand the test coverage. Check if owners of all subfolders and files in Bind directory inside container is the same as on host. Issue is reproducible in Ubuntu Server 17.04 (systemd 232) and Ubuntu Server 17.10 (systemd 233). To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1688689/+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 1692188] [NEW] journalctl --vacuum* ignores --quiet
Public bug reported: I am clearing the journal per cron using `journalctl --vacuum-time=1d --quiet`. Unfortunately the `--quiet` is ignored, and the journalctl always outputs something like `Vacuuming done…`. This results in cron sending me an email, and I don’t like that. I think that `--quiet` should suppress normal output of `journalctl --vacuum-time=1d`. ** 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/1692188 Title: journalctl --vacuum* ignores --quiet Status in systemd package in Ubuntu: New Bug description: I am clearing the journal per cron using `journalctl --vacuum-time=1d --quiet`. Unfortunately the `--quiet` is ignored, and the journalctl always outputs something like `Vacuuming done…`. This results in cron sending me an email, and I don’t like that. I think that `--quiet` should suppress normal output of `journalctl --vacuum-time=1d`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1692188/+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 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
Maybe also dkms may need more space on /boot when updating and backing up initrd.img? -- 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/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full Status in initramfs-tools: New Status in dpkg package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: New Bug description: System calls /etc/kernel/postinst.d/initramfs-tools when purging/removing a linux-image-extra package. That calls "update- initramfs -c" which needs significant amount of additional disk space in /boot temporarily. But there is no space left, if /boot is full. The fix could be to create the new initrg.img file in different partition before replacing the old one by it in update-initramfs. So the update-initramfs script should be fixed. But there may not be such a partition.. Anyway the likely case when space runs out is when there is a separate /boot partition. Alternatively the init script should remove the respective /boot/initrd.img- file when removing/installing the linux-image-extra package. That could also be done by update-initramfs -d -k Related question: http://askubuntu.com/q/898499/21005 The output of 'dpkg --purge' presented there shows that corresponding linux-image package may get successfully removed while the linux-image-extra is left broken. If the linux-image-extra package will be removed later, the post-installation script will create an initrd.img file for a non-installed kernel! Same would happen, if removing would be done by apt-get purge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.7 ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 31 17:42:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (922 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1678187/+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 1692201] [NEW] package bash 4.4-2ubuntu1 failed to install/upgrade: il pacchetto bash non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed
Public bug reported: non so ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bash 4.4-2ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic i686 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: bash:i386: Configure NULL: ConfigurePending Architecture: i386 Date: Sat May 20 11:42:03 2017 DpkgTerminalLog: dpkg: errore nell'elaborare il pacchetto bash (--configure): il pacchetto bash non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") ErrorMessage: il pacchetto bash non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") InstallationDate: Installed on 2017-03-27 (54 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: bash Title: package bash 4.4-2ubuntu1 failed to install/upgrade: il pacchetto bash non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") UpgradeStatus: Upgraded to zesty on 2017-04-16 (33 days ago) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 zesty -- 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/1692201 Title: package bash 4.4-2ubuntu1 failed to install/upgrade: il pacchetto bash non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") Status in bash package in Ubuntu: New Bug description: non so ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bash 4.4-2ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic i686 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: bash:i386: Configure NULL: ConfigurePending Architecture: i386 Date: Sat May 20 11:42:03 2017 DpkgTerminalLog: dpkg: errore nell'elaborare il pacchetto bash (--configure): il pacchetto bash non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") ErrorMessage: il pacchetto bash non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") InstallationDate: Installed on 2017-03-27 (54 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: bash Title: package bash 4.4-2ubuntu1 failed to install/upgrade: il pacchetto bash non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") UpgradeStatus: Upgraded to zesty on 2017-04-16 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1692201/+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 1692202] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: njnjnnn ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sat May 20 16:57:34 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-20 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (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 gconf in Ubuntu. https://bugs.launchpad.net/bugs/1692202 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: njnjnnn ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sat May 20 16:57:34 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-20 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1692202/+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 1692202] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 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 #1688721, 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. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1688721 package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1692202 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: njnjnnn ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sat May 20 16:57:34 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-20 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1692202/+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 1692213] [NEW] black screen
Public bug reported: my system went to black screen and became unresponsive ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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 Date: Sat May 20 14:30:46 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7310] [1002:9809] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Wrestler [Radeon HD 7310] [144d:c0db] InstallationDate: Installed on 2016-12-30 (140 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 355V4C/356V4C/3445VC/3545VC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=c0b388a3-7664-45c6-a50e-24458bdf7bd5 ro splash quiet nopat SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ABG dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP355E5C-A01GR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: BOARD REVISION 00 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ABG:bd02/23/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn355V4C/356V4C/3445VC/3545VC:pvrP05ABG.008.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP355E5C-A01GR:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 355V4C/356V4C/3445VC/3545VC dmi.product.version: P05ABG.008.CP dmi.sys.vendor: SAMSUNG ELECTRONICS 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.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 2:1.18.4-0ubuntu0.2 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat May 20 09:47:23 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon ** 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/1692213 Title: black screen Status in xorg package in Ubuntu: New Bug description: my system went to black screen and became unresponsive ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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 Date: Sat May 20 14:30:46 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7310] [1002:9809] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Wrestler [Radeon HD 7310] [144d:c0db] InstallationDate: Installed on 2016-12-30 (140 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 355V4C/356V4C/3445VC/3545VC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=c0b388a3-7664-45c6-a50e-24458bdf7bd5 ro splash quiet nopat SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ABG dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP355E5C-A01GR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: BOARD REVISION 00 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO.,
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
It would be easier to remove excessive kernels after this issue, if Bug #1678187 was fixed. -- 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/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in Software Updater: New Status in dpkg package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: In Progress Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. See instructions here https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1692217] [NEW] package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-install
Public bug reported: estaba actualisando ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat May 20 07:26:41 2017 ErrorMessage: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed') InstallationDate: Installed on 2017-05-17 (2 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iproute2 (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 iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1692217 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed') Status in iproute2 package in Ubuntu: New Bug description: estaba actualisando ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat May 20 07:26:41 2017 ErrorMessage: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed') InstallationDate: Installed on 2017-05-17 (2 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1692217/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
** Description changed: Binary package hint: initramfs-tools - When generating a new initramfs there is no check for available free - space, subsequently its possible for update-initramfs to fail due to a - lack of free space. This is resulting in package installation failures - for initramfs-tools. For example: + When installing a kernel, /boot may become full during execution of + post-installation script typically when update-initramfs is creating or + updating an initrd.img file. This is resulting in kernel installation + error. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 - WORKAROUND: + Ideal behavior: - Remove unused kernels using computer janitor (not in repositories for - 14.04 or later) or manually free space on your partition containing the - /boot file system. + Give a more helpful error message when this unfortunate situation occurs + so that user can fix the broken system and keep it going. - See instructions here + Workaround: + + As the bug reporting system forwards user to this bug report, such instructions can be given here: https://help.ubuntu.com/community/RemoveOldKernels ** Summary changed: - update-initramfs should produce a more helpful error when there isn't enough free space + update-initramfs should produce a more helpful error message when there isn't enough free space -- 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/798414 Title: update-initramfs should produce a more helpful error message when there isn't enough free space Status in initramfs-tools: Confirmed Status in Software Updater: New Status in dpkg package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: In Progress Bug description: Binary package hint: initramfs-tools When installing a kernel, /boot may become full during execution of post-installation script typically when update-initramfs is creating or updating an initrd.img file. This is resulting in kernel installation error. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Ideal behavior: Give a more helpful error message when this unfortunate situation occurs so that user can fix the broken system and keep it going. Workaround: As the bug reporting system forwards user to this bug report, such instructions can be given here: https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1692218] [NEW] package libicu55:amd64 55.1-7 failed to install/upgrade: package libicu55:amd64 is not ready for configuration cannot configure (current status 'half-installed')
Public bug reported: Hello, I am trying to prepare Openwrt working with image builder. Running statement apt-get install subversion build-essential libncurses5-dev zlib1g-dev gawk git ccache gettext libssl-dev xsltproc wget raised hr error. I am susing a VM on Oracle VrtualBox, 64-bit. Best regards, Cristi ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libicu55:amd64 55.1-7 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: Sat May 20 15:36:39 2017 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.4 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.4 DuplicateSignature: package:libicu55:amd64:55.1-7 Processing triggers for libc-bin (2.23-0ubuntu7) ... dpkg: error processing package libicu55:amd64 (--configure): package libicu55:amd64 is not ready for configuration ErrorMessage: package libicu55:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-02-19 (89 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: icu Title: package libicu55:amd64 55.1-7 failed to install/upgrade: package libicu55:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: icu (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 icu in Ubuntu. https://bugs.launchpad.net/bugs/1692218 Title: package libicu55:amd64 55.1-7 failed to install/upgrade: package libicu55:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in icu package in Ubuntu: New Bug description: Hello, I am trying to prepare Openwrt working with image builder. Running statement apt-get install subversion build-essential libncurses5-dev zlib1g-dev gawk git ccache gettext libssl-dev xsltproc wget raised hr error. I am susing a VM on Oracle VrtualBox, 64-bit. Best regards, Cristi ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libicu55:amd64 55.1-7 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: Sat May 20 15:36:39 2017 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.4 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.4 DuplicateSignature: package:libicu55:amd64:55.1-7 Processing triggers for libc-bin (2.23-0ubuntu7) ... dpkg: error processing package libicu55:amd64 (--configure): package libicu55:amd64 is not ready for configuration ErrorMessage: package libicu55:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-02-19 (89 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: icu Title: package libicu55:amd64 55.1-7 failed to install/upgrade: package libicu55:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1692218/+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 1692218] Re: package libicu55:amd64 55.1-7 failed to install/upgrade: package libicu55:amd64 is not ready for configuration cannot configure (current status 'half-installed')
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1692218 Title: package libicu55:amd64 55.1-7 failed to install/upgrade: package libicu55:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in icu package in Ubuntu: New Bug description: Hello, I am trying to prepare Openwrt working with image builder. Running statement apt-get install subversion build-essential libncurses5-dev zlib1g-dev gawk git ccache gettext libssl-dev xsltproc wget raised hr error. I am susing a VM on Oracle VrtualBox, 64-bit. Best regards, Cristi ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libicu55:amd64 55.1-7 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: Sat May 20 15:36:39 2017 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.4 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.4 DuplicateSignature: package:libicu55:amd64:55.1-7 Processing triggers for libc-bin (2.23-0ubuntu7) ... dpkg: error processing package libicu55:amd64 (--configure): package libicu55:amd64 is not ready for configuration ErrorMessage: package libicu55:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-02-19 (89 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: icu Title: package libicu55:amd64 55.1-7 failed to install/upgrade: package libicu55:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1692218/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
I can also confirm this bug. I have a dell 7560 with ALC3246. I tried 14.04, 16.04, 17.04 and None of them works. -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in alsa-driver package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801/+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 1692222] [NEW] new user so my install sucked
Public bug reported: tried to be all ubuntu cool and erased windows from my moms old dell, now i get all these errors ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.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 Date: Sat May 20 09:44:47 2017 DistUpgraded: 2017-05-20 00:06:17,510 DEBUG icon theme changed, re-reading DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0447] InstallationDate: Installed on 2016-07-18 (305 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron N5010 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic root=/dev/mapper/ubuntu--vg-root ro nopat drm.debug=0xe vesafb.invalid=1 plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-05-20 (0 days ago) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0WXY9J dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn0WXY9J:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.6-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.6-0ubuntu0.17.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu zesty -- 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/169 Title: new user so my install sucked Status in xorg package in Ubuntu: New Bug description: tried to be all ubuntu cool and erased windows from my moms old dell, now i get all these errors ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.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 Date: Sat May 20 09:44:47 2017 DistUpgraded: 2017-05-20 00:06:17,510 DEBUG icon theme changed, re-reading DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0447] InstallationDate: Installed on 2016-07-18 (305 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron N5010 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic root=/dev/mapper/ubuntu--vg-root ro nopat drm.debug=0xe vesafb.invalid=1 plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-05-20 (0 days ago) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0WXY9J dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn0WXY9J:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
[Touch-packages] [Bug 1692225] [NEW] update-initramfs -u fails with random resume UUID
Public bug reported: Ubuntu 16.04 32-bit In fstab I have: UUID=38e6603c-6b17-488a-9613-7341e8e89274 none swapsw 0 0 But I have 2 swap partitions on my hard drive, the other for a 64-bit instance. With this setting, suspend-to-disk (STD) was functional in ~ 50 % of the cases. Then I created /etc/initramfs-tools/conf.d/resume with: RESUME=UUID=38e6603c-6b17-488a-9613-7341e8e89274 and did sudo update-initramfs -u -k all. After this, the STD never worked again. So I extracted /boot/initrd.img-4.4.0-78-generic and saw the surprising content, different from the swap-partitions UUID: RESUME=UUID=93782983-700c-4084-84b1-5e3f8c1e788f Another try of sudo update-initramfs -u -k all created another random UUID, both do not match with any partition UUID on my system. So I recovered my original system back from a backup image and discovered in conf/conf.d/resume from /boot/initrd.img-4.4.0-78-generic: RESUME=UUID=38e6603c-6b17-488a-9613-7341e8e89274 So originally there was the correct UUID, even I never created a /etc/initramfs-tools/conf.d/resume file. Now I do not have any idea, why sudo update-initramfs -u -k all doesn't create correct values to make STD always working reliably. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- 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/1692225 Title: update-initramfs -u fails with random resume UUID Status in initramfs-tools package in Ubuntu: New Bug description: Ubuntu 16.04 32-bit In fstab I have: UUID=38e6603c-6b17-488a-9613-7341e8e89274 none swapsw 0 0 But I have 2 swap partitions on my hard drive, the other for a 64-bit instance. With this setting, suspend-to-disk (STD) was functional in ~ 50 % of the cases. Then I created /etc/initramfs-tools/conf.d/resume with: RESUME=UUID=38e6603c-6b17-488a-9613-7341e8e89274 and did sudo update-initramfs -u -k all. After this, the STD never worked again. So I extracted /boot/initrd.img-4.4.0-78-generic and saw the surprising content, different from the swap-partitions UUID: RESUME=UUID=93782983-700c-4084-84b1-5e3f8c1e788f Another try of sudo update-initramfs -u -k all created another random UUID, both do not match with any partition UUID on my system. So I recovered my original system back from a backup image and discovered in conf/conf.d/resume from /boot/initrd.img-4.4.0-78-generic: RESUME=UUID=38e6603c-6b17-488a-9613-7341e8e89274 So originally there was the correct UUID, even I never created a /etc/initramfs-tools/conf.d/resume file. Now I do not have any idea, why sudo update-initramfs -u -k all doesn't create correct values to make STD always working reliably. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1692225/+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 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()
** Changed in: pulseaudio Status: Confirmed => Fix Released -- 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/1539209 Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg() Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Triaged Bug description: Appears randomly. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:7.1-1ubuntu3 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: potato12883 F...m pulseaudio /dev/snd/controlC0: potato12883 F pulseaudio /dev/snd/controlC1: potato12883 F pulseaudio CurrentDesktop: Unity Date: Thu Jan 28 22:16:03 2016 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-01-17 (11 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=ru_RU.UTF-8 LANGUAGE=ru XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so ?? () from /usr/lib/libpulsecore-7.1.so Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/07/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.11 dmi.board.name: JV71TR dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone: dmi.product.name: Aspire 7540 dmi.product.version: 0100 dmi.sys.vendor: Acer modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1539209/+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 772720] Re: extreme noise with sound
I'm now on Ubuntu 16.04 xenial. VLC now actually plays music, but the UI freezes when I click play/select a file (so the music *is* playing even while the UI is frozen). MPlayer, Clementine et all do just fine on my machine. I'll enter another bug report for that. -- 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/772720 Title: extreme noise with sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: Binary package hint: vlc Since update to Natty, vlc plays with extreme noise. What works: * visual part of video-playing with vlc * sound & video with other players like totem, mplayer, rhythmbox What does not: * audio part of video-playing with vlc * playing soundfiles with vlc In the latter cases, vlc plays the file (everything ok in GUI), while the audio is identifiable, but hardly comprehensible through the noise. I've tested the issue with a number of files in different audio/video formats. Audio hw is: 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) 01:00.1 Audio device: ATI Technologies Inc RV710/730 <-- belongs to the graphics card, I assume, is not used ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: vlc 1.1.9-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Thu Apr 28 23:17:22 2011 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: LANGUAGE=sv_SE:en PATH=(custom, no user) LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: Upgraded to natty on 2011-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/772720/+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 1691798] Re: package linux-image-extra-4.4.0-75-generic 4.4.0-75.96 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1691798 Title: package linux-image-extra-4.4.0-75-generic 4.4.0-75.96 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I tried updating ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-75-generic 4.4.0-75.96 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anon 2001 F pulseaudio /dev/snd/controlC0: anon 2001 F pulseaudio Date: Thu May 18 12:19:22 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=7f0a4815-0f11-4b86-8a42-500b90fa26d1 InstallationDate: Installed on 2016-09-28 (232 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Apple Inc. MacBookAir7,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash pcie_aspm=force i915.i915_enable_rc6=1 i915.lvds_downclock=1 i915.i915_enable_fbc=1 intel_idle.max_cstate=1 acpi_backlight=vendor 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 N/A SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-75-generic 4.4.0-75.96 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: 02/22/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA71.88Z.0166.B12.1602221953 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-937CB26E2E02BB01 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir7,2 dmi.chassis.asset.tag: Chassis Board Asset Tag# dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-937CB26E2E02BB01 dmi.modalias: dmi:bvnAppleInc.:bvrMBA71.88Z.0166.B12.1602221953:bd02/22/2016:svnAppleInc.:pnMacBookAir7,2:pvr1.0:rvnAppleInc.:rnMac-937CB26E2E02BB01:rvrMacBookAir7,2:cvnAppleInc.:ct9:cvrMac-937CB26E2E02BB01: dmi.product.name: MacBookAir7,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1691798/+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 1505220] Re: multiple apps crashing at launch
For me, removing /home/phablet/.cache/QML/Apps/webbrowser-app helped. If I return backup contents, browser crashes again. I could send webbrowser-app.tar.gz for investigation. -- 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/1505220 Title: multiple apps crashing at launch Status in Canonical System Image: Incomplete Status in webbrowser-app package in Ubuntu: New Bug description: os: ubuntu touch 15.04 stable channel r25(OTA6), fully updated, no r/w mode device: BQ 45E(Krillin) bug: starting this morning, I found that my browser (the default ubuntu-touch one) crashes on startup. All i see is the spinning startup wheel. Then nothing. I am again on the apps scope. Then i found that this is also the case for the Liri browser and Dekko (The difference for Dekko being that it doenst crash. But it neither starts. It just keeps spinning the app startup wheel). All other webapps and apps that i have tested continue to work fine. First i tried a reboot but the same behaviour remains. Then I noticed that i was low on diskspace(system-settings said I had about 250 MB left) so cleared out some stuff giving me a gig of free space. Reboot again but still the same apps continue to crash when started. on irc I consulted jgdx. He had me verify that I had indeed enough space with df -h The output for that is here: http://pastebin.com/NbvSKvit Then we looked logfiles for the browser app and unity8. They are here: http://pastebin.com/Bia7qrkm (webbrowser) http://pastebin.com/2UuRuDk6 (unity8) Attached is also the .crash file for the webbrowser from /var/crash Any other info needed, let me know To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505220/+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 1505220] Re: multiple apps crashing at launch
In my case it's E5 with OTA-15. -- 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/1505220 Title: multiple apps crashing at launch Status in Canonical System Image: Incomplete Status in webbrowser-app package in Ubuntu: New Bug description: os: ubuntu touch 15.04 stable channel r25(OTA6), fully updated, no r/w mode device: BQ 45E(Krillin) bug: starting this morning, I found that my browser (the default ubuntu-touch one) crashes on startup. All i see is the spinning startup wheel. Then nothing. I am again on the apps scope. Then i found that this is also the case for the Liri browser and Dekko (The difference for Dekko being that it doenst crash. But it neither starts. It just keeps spinning the app startup wheel). All other webapps and apps that i have tested continue to work fine. First i tried a reboot but the same behaviour remains. Then I noticed that i was low on diskspace(system-settings said I had about 250 MB left) so cleared out some stuff giving me a gig of free space. Reboot again but still the same apps continue to crash when started. on irc I consulted jgdx. He had me verify that I had indeed enough space with df -h The output for that is here: http://pastebin.com/NbvSKvit Then we looked logfiles for the browser app and unity8. They are here: http://pastebin.com/Bia7qrkm (webbrowser) http://pastebin.com/2UuRuDk6 (unity8) Attached is also the .crash file for the webbrowser from /var/crash Any other info needed, let me know To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505220/+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 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
** Description changed: System calls /etc/kernel/postinst.d/initramfs-tools when purging/removing a linux-image-extra package. That calls "update- initramfs -c" which needs significant amount of additional disk space in /boot temporarily. But there is no space left, if /boot is full. + Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u". + The fix could be to create the new initrg.img file in different partition before replacing the old one by it in update-initramfs. So the update-initramfs script should be fixed. But there may not be such a partition.. Anyway the likely case when space runs out is when there is a separate /boot partition. - Alternatively the init script should remove the respective /boot/initrd.img- file when removing/installing the linux-image-extra package. That could also be done by + Alternatively the init scripts should remove the respective /boot/initrd.img- file when removing/installing the linux-image-extra package. That could also be done by update-initramfs -d -k Related question: http://askubuntu.com/q/898499/21005 The output of 'dpkg --purge' presented there shows that corresponding linux-image package may get successfully removed while the linux-image-extra is left broken. If the linux-image-extra package will be removed later, the post-installation script will create an initrd.img file for a non-installed kernel! Same would happen, if removing would be done by apt-get purge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.7 ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 31 17:42:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (922 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full Status in initramfs-tools: New Status in dpkg package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: New Bug description: System calls /etc/kernel/postinst.d/initramfs-tools when purging/removing a linux-image-extra package. That calls "update- initramfs -c" which needs significant amount of additional disk space in /boot temporarily. But there is no space left, if /boot is full. Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u". The fix could be to create the new initrg.img file in different partition before replacing the old one by it in update-initramfs. So the update-initramfs script should be fixed. But there may not be such a partition.. Anyway the likely case when space runs out is when there is a separate /boot partition. Alternatively the init scripts should remove the respective /boot/initrd.img- file when removing/installing the linux-image-extra package. That could also be done by update-initramfs -d -k Related question: http://askubuntu.com/q/898499/21005 The output of 'dpkg --purge' presented there shows that corresponding linux-image package may get successfully removed while the linux-image-extra is left broken. If the linux-image-extra package will be removed later, the post-installation script will create an initrd.img file for a non-installed kernel! Same would happen, if removing would be done by apt-get purge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.7 ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 31 17:42:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (922 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1678187/+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 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting
booting distro kernel 4.8.0-52 with kernel parameter amd_iommu=off: boot time 1 minute and "boot finished" sound - just like upstream kernel 4.12-rc1 without amd_iommu parameter. ** Attachment added: "error and fail lines from dmesg distro kernel" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639517/+attachment/4880375/+files/dmesg_error_distro_iommu.txt -- 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/1639517 Title: [HP Pavilion Notebook - 17-g164ng] black screen when booting Status in xorg package in Ubuntu: Incomplete Bug description: When booting the screen is black – backlight on – off - on. When HDD is inactive - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or Strg + Alt + Del - remote access e.g. using ssh is possible Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10. My notebook is a HP Pavilion 17-g164ng with an AMD A10-8780P APU and 2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz. It seems very similar to that described in #1597079. The bug report was generated from a remote PC. My HP notebook was started without any workaround parameters. This apport doesn't display the second graphic subsystem Topaz R7 as an apport generated with nomodeset xforcevesa. WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver. WORKAROUND: When booting in UEFI mode, use kernel parameters: nomodeset or: nomodeset xforcevesa Resolution without xforcevesa: 800x600 Resolution with xforcevesa: 1600x900 – the optimal resolution ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 5 23:40:19 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:80b6] InstallationDate: Installed on 2016-11-03 (2 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP Pavilion Notebook ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.41 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 80B6 dmi.board.vendor: HP dmi.board.version: 81.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.sys.vendor: HP version.compiz: compiz N/A 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: Sat Nov 5 23:32:11 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.1 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639517/+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 1692256] [NEW] Wacky graphics after sleep
Public bug reported: After resuming from sleep the graphics are wacky. Green frames appear with white and black dots. Can be noticed on open windows. Attached print screen should say all. It has occurred several times, solved after restart and same issue after log out / log in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.39 Tue Jan 31 20:47:00 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 BootLog: 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: Sat May 20 23:19:05 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Palit Microsystems Inc. GK106 [GeForce GTX 660] [1569:11c0] InstallationDate: Installed on 2016-06-07 (347 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) LightdmLog: [+6872.42s] DEBUG: Seat seat0 changes active session to [+6872.44s] DEBUG: Seat seat0 changes active session to c2 [+6872.44s] DEBUG: Session c2 is already active MachineType: MSI MS-7758 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic root=UUID=68b670a7-f823-4c65-89db-055649e143a7 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ZH77A-G41 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd10/29/2013:svnMSI:pnMS-7758:pvr3.0:rvnMSI:rnZH77A-G41(MS-7758):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.name: MS-7758 dmi.product.version: 3.0 dmi.sys.vendor: MSI 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 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: Sat May 20 21:11:15 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Keyboard KEYBOARD, id 8 inputA4Tech USB Mouse MOUSE, id 9 inputLogitech USB Keyboard KEYBOARD, id 10 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial ** Attachment added: "Wacky graphics - VLC gets greenish frame after sleep" https://bugs.launchpad.net/bugs/1692256/+attachment/4880377/+files/wacky%20-%20graphics%202.png -- 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/1692256 Title: Wacky graphics after sleep Status in xorg package in Ubuntu: New Bug description: After resuming from sleep the graphics are wacky. Green frames appear with white and black dots. Can be noticed on open windows. Attached print screen should say all. It has occurred several times, solved after restart and same issue after log out / log in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driv
[Touch-packages] [Bug 1691848] Re: Python not compiled with -fexceptions in ppc64le
is powerpc64le-linux-gnu the only architecture affected? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1691848 Title: Python not compiled with -fexceptions in ppc64le Status in python2.7 package in Ubuntu: New Bug description: Pytorch (https://github.com/pytorch/pytorch) is an application that is written in python, C and C++. There's high interoperalibity between code written in these languages therex. The issue is that there are cases when an exception is thrown by C++ code that subsequentely calls some C code before being caught. In ppc64le builds, without the -fexceptions gcc flag, such exceptions are not caught when the execution returns to C++ code from C code. This makes some Pytorch tests fail. Compiling CPython with -fexceptions seems to solve this issue. This was also reported to Debian: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=862925 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: python2.7 2.7.13-2 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic ppc64le .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform' ApportVersion: 2.20.4-0ubuntu4 Architecture: ppc64el Date: Thu May 18 15:35:54 2017 InstallationDate: Installed on 2015-11-05 (560 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release ppc64el (20150422) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcLoadAvg: 0.07 0.33 0.43 1/348 20166 ProcSwaps: Filename TypeSizeUsed Priority ProcVersion: Linux version 4.10.0-19-generic (buildd@bos01-ppc64el-009) (gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1) ) #21-Ubuntu SMP Thu Apr 6 17:03:05 UTC 2017 SourcePackage: python2.7 UpgradeStatus: Upgraded to zesty on 2017-04-17 (30 days ago) cpu_cores: Number of cores present = 2 cpu_coreson: Number of cores online = 2 cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1691848/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
** Changed in: debconf (Ubuntu) Status: Triaged => Confirmed ** Changed in: aptdaemon (Ubuntu) Status: Triaged => Confirmed ** Changed in: aptdaemon Status: New => Confirmed ** Changed in: ambasa Assignee: (unassigned) => maurizio gamberini (mauriziogamberini1) ** Changed in: aptdaemon Assignee: (unassigned) => maurizio gamberini (mauriziogamberini1) ** Changed in: debconf Assignee: (unassigned) => maurizio gamberini (mauriziogamberini1) ** Changed in: aptdaemon (Ubuntu) Assignee: (unassigned) => maurizio gamberini (mauriziogamberini1) ** Changed in: debconf (Ubuntu) Assignee: (unassigned) => maurizio gamberini (mauriziogamberini1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Ambasa: New Status in Aptdaemon: Confirmed Status in Debconf: New Status in aptdaemon package in Ubuntu: Confirmed Status in debconf package in Ubuntu: Confirmed Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ambasa/+bug/349469/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
** Project changed: ambasa => null-and-void ** Changed in: null-and-void Assignee: maurizio gamberini (mauriziogamberini1) => (unassigned) ** Changed in: aptdaemon (Ubuntu) Status: Confirmed => Triaged ** Changed in: debconf (Ubuntu) Assignee: maurizio gamberini (mauriziogamberini1) => (unassigned) ** Changed in: aptdaemon (Ubuntu) Assignee: maurizio gamberini (mauriziogamberini1) => (unassigned) ** Changed in: debconf Assignee: maurizio gamberini (mauriziogamberini1) => (unassigned) ** Changed in: aptdaemon Assignee: maurizio gamberini (mauriziogamberini1) => (unassigned) ** Changed in: debconf (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Aptdaemon: Confirmed Status in Debconf: New Status in aptdaemon package in Ubuntu: Triaged Status in debconf package in Ubuntu: Triaged Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upstart (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Aptdaemon: Confirmed Status in Debconf: New Status in aptdaemon package in Ubuntu: Triaged Status in debconf package in Ubuntu: Triaged Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
** Project changed: null-and-void => upstart (Ubuntu) ** No longer affects: upstart (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Aptdaemon: Confirmed Status in Debconf: New Status in aptdaemon package in Ubuntu: Triaged Status in debconf package in Ubuntu: Triaged Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/349469/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
Thanks, looks like it answers questions I have not encountered yet as well. So many sites out there, and I had not discovered this one yet. Thanks for taking the time. On Wed, May 17, 2017 at 7:57 PM, Daniel Richard G. wrote: > Hi Luigi, > > This StackExchange posting should answer your question: > > https://unix.stackexchange.com/questions/3586/what-do-the-numbers-in-a > -man-page-mean > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1522675 > > Title: > Warning messages about unsandboxed downloads > > Status in apt package in Ubuntu: > Fix Released > Status in update-notifier package in Ubuntu: > Confirmed > Status in apt package in Debian: > Fix Released > Status in synaptic package in Debian: > New > > Bug description: > Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but > now get that error when installing/upgrading some packages: > > Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... > Processing triggers for libc-bin (2.21-0ubuntu5) ... > W: Can't drop privileges for downloading as file > '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - > pkgAcquire::Run (13: Permission denied) > > From nautilus, i'm seeing a /root/ folder locked (x on its icon) and > the folder is empty (no /.synaptic/ sub-folder or file), so the above > error. > > oem@u64:~$ ls -l .synaptic > total 4 > -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options > -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf > > oem@u64:~$ ls -l /var/lib/apt/lists/ > > -rw-r- 1 root root0 Sep 20 06:36 lock > drwx-- 2 _apt root16384 Sep 24 15:25 partial > .. > > oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ > . > drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial > > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: synaptic 0.82+build1 > ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 > Uname: Linux 4.3.0-1-generic x86_64 > NonfreeKernelModules: nvidia > ApportVersion: 2.19.2-0ubuntu8 > Architecture: amd64 > CurrentDesktop: GNOME > Date: Fri Dec 4 05:23:25 2015 > SourcePackage: synaptic > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions > -- _-_-_ |BricK| [image: 🤓] L P Luigi Espenlaub luigiwrit...@gmail.com "Kuiper Belted" [A Non fantasy science fiction mystery set 150 years in the future.] "A stone cold mystery in space." - Woody Carsky-Wilson, ED: A Few Good Words, a Cincinnati Writers Project Anthology available on Amazon. -- 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/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Confirmed Status in apt package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
Ok, Thanks. Will definitely copy this into my personal command reference. This will help solve a bunch of headaches until I can get Samba's teeth un-clamped from my leg. Thanks again. On Wed, May 17, 2017 at 7:57 PM, Travisgevans <1522...@bugs.launchpad.net> wrote: > The command is lowercase “chown”, without the “(1)”. The general syntax > would be “chown ”. You'll normally need > superuser privileges to change owners on system files and directories, > activated by adding the command “sudo” before the “chown” (separated by > a space). > > The “(1)” refers to which section in the manual pages, or “manpages”, > the command is described in. A common way to get help on a command is to > run “man ”; for instance, you can execute “man chown” to > get the manpage on the chown command. (To exit, type the letter q; more > info here: https://help.ubuntu.com/community/man) The manual pages are > divided into numbered sections by categories. Occasionally, there is > more than one manpage with the same name, and the section number has to > be included in the “man” command to indicate which is desired (for > instance, “man 1 printf” gives the page on the shell command “printf”, > but “man 3 printf” gives the page on the “printf” library call for C > programming). > > You can get a manpage on “man” itself with “man man” (or just read it > online here: > http://manpages.ubuntu.com/manpages/xenial/man1/man.1.html). Under > “DESCRIPTION”, there's a list of the manpage sections and their numbers, > if you're curious. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1522675 > > Title: > Warning messages about unsandboxed downloads > > Status in apt package in Ubuntu: > Fix Released > Status in update-notifier package in Ubuntu: > Confirmed > Status in apt package in Debian: > Fix Released > Status in synaptic package in Debian: > New > > Bug description: > Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but > now get that error when installing/upgrading some packages: > > Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... > Processing triggers for libc-bin (2.21-0ubuntu5) ... > W: Can't drop privileges for downloading as file > '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - > pkgAcquire::Run (13: Permission denied) > > From nautilus, i'm seeing a /root/ folder locked (x on its icon) and > the folder is empty (no /.synaptic/ sub-folder or file), so the above > error. > > oem@u64:~$ ls -l .synaptic > total 4 > -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options > -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf > > oem@u64:~$ ls -l /var/lib/apt/lists/ > > -rw-r- 1 root root0 Sep 20 06:36 lock > drwx-- 2 _apt root16384 Sep 24 15:25 partial > .. > > oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ > . > drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial > > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: synaptic 0.82+build1 > ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 > Uname: Linux 4.3.0-1-generic x86_64 > NonfreeKernelModules: nvidia > ApportVersion: 2.19.2-0ubuntu8 > Architecture: amd64 > CurrentDesktop: GNOME > Date: Fri Dec 4 05:23:25 2015 > SourcePackage: synaptic > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions > -- _-_-_ |BricK| [image: 🤓] L P Luigi Espenlaub luigiwrit...@gmail.com "Kuiper Belted" [A Non fantasy science fiction mystery set 150 years in the future.] "A stone cold mystery in space." - Woody Carsky-Wilson, ED: A Few Good Words, a Cincinnati Writers Project Anthology available on Amazon. -- 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/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Confirmed Status in apt package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synapti
[Touch-packages] [Bug 1692273] [NEW] bug notification
Public bug reported: This was found when I ran a diagnostic. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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 Date: Sat May 20 19:15:24 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:8694] InstallationDate: Installed on 2017-04-13 (37 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=ce8e6a6f-8c36-4bf0-b23c-1a1e71deefcf ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2003 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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 2:1.18.4-0ubuntu0.2 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat May 20 09:42:52 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9412 vendor ACI xserver.version: 2:1.18.4-0ubuntu0.2 ** 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/1692273 Title: bug notification Status in xorg package in Ubuntu: New Bug description: This was found when I ran a diagnostic. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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 Date: Sat May 20 19:15:24 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:8694] InstallationDate: Installed on 2017-04-13 (37 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=ce8e6a6f-8c36-4bf0-b23c-1a1e71deefcf ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2003 dmi.board.asset.tag: Default string dm
[Touch-packages] [Bug 1692275] [NEW] package unattended-upgrades 0.93.1ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: the upgrade was interrupted without any apparent reason. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: unattended-upgrades 0.93.1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: unattended-upgrades:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri May 19 21:18:39 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-28 (22 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.93.1ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unattended-upgrades (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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1692275 Title: package unattended-upgrades 0.93.1ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in unattended-upgrades package in Ubuntu: New Bug description: the upgrade was interrupted without any apparent reason. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: unattended-upgrades 0.93.1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: unattended-upgrades:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri May 19 21:18:39 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-28 (22 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.93.1ubuntu2.1 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/unattended-upgrades/+bug/1692275/+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 1692276] [NEW] package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: just can't install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat May 20 21:53:21 2017 DuplicateSignature: package:iproute2:4.3.0-1ubuntu3 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package iproute2 (--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-05-15 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 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: iproute2 (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 iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1692276 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in iproute2 package in Ubuntu: New Bug description: just can't install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat May 20 21:53:21 2017 DuplicateSignature: package:iproute2:4.3.0-1ubuntu3 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package iproute2 (--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-05-15 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 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/iproute2/+bug/1692276/+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 1692275] Re: package unattended-upgrades 0.93.1ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1692275 Title: package unattended-upgrades 0.93.1ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in unattended-upgrades package in Ubuntu: New Bug description: the upgrade was interrupted without any apparent reason. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: unattended-upgrades 0.93.1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: unattended-upgrades:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri May 19 21:18:39 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-28 (22 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.93.1ubuntu2.1 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/unattended-upgrades/+bug/1692275/+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 1692277] [NEW] New release of alsa-lib
Public bug reported: 1.1.4 -- Cristian ** Affects: alsa-lib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1692277 Title: New release of alsa-lib Status in alsa-lib package in Ubuntu: New Bug description: 1.1.4 -- Cristian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1692277/+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 1692276] Re: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1692276 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in iproute2 package in Ubuntu: New Bug description: just can't install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat May 20 21:53:21 2017 DuplicateSignature: package:iproute2:4.3.0-1ubuntu3 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package iproute2 (--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-05-15 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 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/iproute2/+bug/1692276/+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 366665] Re: find wont use .bashrc alias
The -exec param of find is executed by find, not by the bash, and find
doesn't look into your aliases. This is expected behaviour. Find won't
neither execute bash functions. And it does not allow redirection like
such:
$ find -exec ls {} > /dev/null \;
You have to invoke bash as a login shell (-l) and set the shell option
"expand aliases". Read "man bash", especially section ALIASES, for
further insights.
$ find -type f -name "*.mp3" -exec bash -l -O expand_aliases -c "mp3gainB {}"
";"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
https://bugs.launchpad.net/bugs/35
Title:
find wont use .bashrc alias
Status in findutils:
New
Status in findutils package in Ubuntu:
Invalid
Bug description:
Binary package hint: findutils
i created this alias:
alias mp3gainB='mp3gain -r -k -t -p -s r'
then tried to run
$ find -type f -name "*.mp3" -exec mp3gainB {} \;
but it failed
running
$ find -type f -name "*.mp3" -exec mp3gain -r -k -t -p -s r {} \;
works as expected
ProblemType: Bug
Architecture: amd64
Dependencies:
libgcc1 1:4.3.3-5ubuntu4
gcc-4.3-base 4.3.3-5ubuntu4
findutils 4.4.0-2ubuntu4
libc6 2.9-4ubuntu6
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: findutils 4.4.0-2ubuntu4
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: findutils
Uname: Linux 2.6.28-12-generic x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/findutils/+bug/35/+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 366665] Re: find wont use .bashrc alias
P.S.: Sorry about the failing code-tags, and the missing explanation of
-c parameter:
-c tells the bash, that it shall execute the following commands.
The linebreak was unintendet.
find -type f -name "*.mp3" -exec bash -l -O expand_aliases -c "mp3gainB
{}" ";"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
https://bugs.launchpad.net/bugs/35
Title:
find wont use .bashrc alias
Status in findutils:
New
Status in findutils package in Ubuntu:
Invalid
Bug description:
Binary package hint: findutils
i created this alias:
alias mp3gainB='mp3gain -r -k -t -p -s r'
then tried to run
$ find -type f -name "*.mp3" -exec mp3gainB {} \;
but it failed
running
$ find -type f -name "*.mp3" -exec mp3gain -r -k -t -p -s r {} \;
works as expected
ProblemType: Bug
Architecture: amd64
Dependencies:
libgcc1 1:4.3.3-5ubuntu4
gcc-4.3-base 4.3.3-5ubuntu4
findutils 4.4.0-2ubuntu4
libc6 2.9-4ubuntu6
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: findutils 4.4.0-2ubuntu4
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: findutils
Uname: Linux 2.6.28-12-generic x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/findutils/+bug/35/+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 366665] Re: find wont use .bashrc alias
As described in the comment below, this is not a bug, but intended
behaviour of find. It can be avoided by the right parameter settings.
I suggest this Bug is invalid.
** Changed in: findutils (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
https://bugs.launchpad.net/bugs/35
Title:
find wont use .bashrc alias
Status in findutils:
New
Status in findutils package in Ubuntu:
Invalid
Bug description:
Binary package hint: findutils
i created this alias:
alias mp3gainB='mp3gain -r -k -t -p -s r'
then tried to run
$ find -type f -name "*.mp3" -exec mp3gainB {} \;
but it failed
running
$ find -type f -name "*.mp3" -exec mp3gain -r -k -t -p -s r {} \;
works as expected
ProblemType: Bug
Architecture: amd64
Dependencies:
libgcc1 1:4.3.3-5ubuntu4
gcc-4.3-base 4.3.3-5ubuntu4
findutils 4.4.0-2ubuntu4
libc6 2.9-4ubuntu6
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: findutils 4.4.0-2ubuntu4
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: findutils
Uname: Linux 2.6.28-12-generic x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/findutils/+bug/35/+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 1692281] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: Nothing further to report. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sat May 20 21:25:20 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-21 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (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 gconf in Ubuntu. https://bugs.launchpad.net/bugs/1692281 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: Nothing further to report. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sat May 20 21:25:20 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-21 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1692281/+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 1692281] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 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 #1688721, 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. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1688721 package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1692281 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: Nothing further to report. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sat May 20 21:25:20 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-21 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1692281/+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 585648] Re: find regex does not work properly
Not a bug, see comment #1.
** Changed in: findutils (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
https://bugs.launchpad.net/bugs/585648
Title:
find regex does not work properly
Status in findutils package in Ubuntu:
Invalid
Bug description:
Binary package hint: findutils
I would appear to be a similar bug to #58883
Some have said this isn't a bug at all but here goes.
When in an empty directory using gnome-terminal:
user@ubuntukarmic:~/f/Desktop/test$ touch {A..Z}
user@ubuntukarmic:~/f/Desktop/test$ touch {a..z}
user@ubuntukarmic:~/f/Desktop/test$ ls
a b c d e f g h i j k l m n o p q r s t u v w x y z
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
user@ubuntukarmic:~/f/Desktop/test$ find . \! -regex '.*[A-Z].*' | sort
.
./a
user@ubuntukarmic:~/f/Desktop/test$ env | grep -i lang
LANG=en_US.UTF-8
GDM_LANG=en_US.UTF-8
user@ubuntukarmic:~/f/Desktop/test$ LANG=C
user@ubuntukarmic:~/f/Desktop/test$ find . \! -regex '.*[A-Z].*' | sort
.
./a
./b
./c
./d
./e
./f
./g
./h
./i
./j
./k
./l
./m
./n
./o
./p
./q
./r
./s
./t
./u
./v
./w
./x
./y
./z
user@ubuntukarmic:~/f/Desktop/test$ find -version
find (GNU findutils) 4.4.2
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Eric B. Decker, James Youngman, and Kevin Dalley.
Built using GNU gnulib version e5573b1bad88bfabcda181b9e0125fb0c52b7d3b
Features enabled: D_TYPE O_NOFOLLOW(enabled) LEAF_OPTIMISATION FTS()
CBO(level=0)
This is further discussed at
http://ubuntuforums.org/showthread.php?t=1488843
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/585648/+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 515404] Re: find should understand "size -100K" aswell as "-size -100k"
Sorry, but that's just an opinion, not a bug. A small k is the standardized shorthand for 1000. K is Kelvin. M is Mega while m is meter. ** Changed in: findutils (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to findutils in Ubuntu. https://bugs.launchpad.net/bugs/515404 Title: find should understand "size -100K" aswell as "-size -100k" Status in findutils package in Ubuntu: Opinion Bug description: Binary package hint: findutils You can find files below a certain file size in find with the "-size" option. However to specify (say) 100 KB, you need to enter "100k", find does not understand "100K", i.e. an upper case K instead of lower case. I think find should be able to recognise upper and lower case k (ie k and K) for kilobytes in the file size. ProblemType: Bug Architecture: i386 Date: Mon Feb 1 09:18:54 2010 DistroRelease: Ubuntu 9.10 Package: findutils 4.4.2-1 ProcEnviron: PATH=(custom, user) LANG=en_IE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic SourcePackage: findutils Uname: Linux 2.6.31-17-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/515404/+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 1433097] Re: enhance -exec option documentation of find with extra hint about command tails and counter-example
This is an opinion, not a bug, IMHO.
** Changed in: findutils (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
https://bugs.launchpad.net/bugs/1433097
Title:
enhance -exec option documentation of find with extra hint about
command tails and counter-example
Status in findutils package in Ubuntu:
Opinion
Bug description:
The `-exec` section of the `find` manpages explains kind of cryptic
that there're no command trails supported in `-exec {] +` (the crucial
part is "at the end" which is not too clear and "The command line is
built in much the same way that xargs builds its command lines." which
is annoying for the user to search in the `xargs` manpage). An
explicit statement, like
File names can be appended only in `-exec`'s argument, i.e.
statements like `find . -name '*.ext' -exec mv {} /target/ +` will
fail (use `xargs` or a form of the desired command which allows
appending if available (e.g. `find . -name '*.ext' -exec mv -t /target
{} +`)).
http://stackoverflow.com/questions/5607542/why-does-find-exec-mv-
target-not-work-on-cygwin. Markdown won't be supported by `man`,
I don't know about the conventions/equivalents there.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: findutils 4.4.2-9
Uname: Linux 3.19.1-031901-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 17 14:44:07 2015
Dependencies:
gcc-4.9-base 4.9.1-16ubuntu6
libc6 2.19-10ubuntu2.3
libgcc1 1:4.9.1-16ubuntu6
multiarch-support 2.19-10ubuntu2.3
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-01-26 (49 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: findutils
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1433097/+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 1422453] Re: Enhance feedback of missing argument to -exec
Did you notice, that you need a blank before the plus sign?
$ find . -name pom.xml -exec grep '' {}+
$ find . -name pom.xml -exec grep '' {} +
For example, if find finds the files a/pom.xml and b/pom.xml, it will
try to build the exec part as:
$ grep '' a/pom.xml b/pom.xml+
instead of
$ grep '' a/pom.xml b/pom.xml
leaving the + for find as special option.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
https://bugs.launchpad.net/bugs/1422453
Title:
Enhance feedback of missing argument to -exec
Status in findutils package in Ubuntu:
New
Bug description:
Invoking a wrong `find` command, e.g. `find . -name pom.xml -exec grep
'' {}+` causes the error message `find: missing argument
to `-exec'` which could be more helpful if the error message would
reflect the correct usage, e.g `find: missing argument to `-exec
{}+'`.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: findutils 4.4.2-9
Uname: Linux 3.19.0-031900-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb 16 19:28:45 2015
Dependencies:
gcc-4.9-base 4.9.1-16ubuntu6
libc6 2.19-10ubuntu2.2
libgcc1 1:4.9.1-16ubuntu6
multiarch-support 2.19-10ubuntu2.2
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-01-26 (20 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: findutils
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1422453/+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 1690605] Re: systemd-resolved: no dns resolution after upgrade to Artful
This bug was fixed in the package systemd - 233-6ubuntu2 --- systemd (233-6ubuntu2) artful; urgency=medium [ Michael Biebl ] * basic/journal-importer: Fix unaligned access in get_data_size() (Closes: #862062) [ Dimitri John Ledkov ] * ubuntu: disable dnssec on any ubuntu releases (LP: #1690605) * Cherrypick upstream patch for vio predictable interface names. * Cherrypick upstream patch for platform predictable interface names. (LP: #1686784) [ Balint Reczey ] * Skip starting systemd-remount-fs.service in containers even when /etc/fstab is present. This allows entering fully running state even when /etc/fstab lists / to be mounted from a device which is not present in the container. (LP: #1576341) -- Dimitri John Ledkov Wed, 17 May 2017 19:24:03 +0100 ** Changed in: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1690605 Title: systemd-resolved: no dns resolution after upgrade to Artful Status in systemd package in Ubuntu: Fix Released Bug description: After upgrading to artful systemd-resolved is failing to resolve dns. It seems DNSSEC validation is failing but shouldnt that be disabled by default like it was in zesty? $ systemctl status systemd-resolved.service ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-resolved.service.d └─resolvconf.conf Active: active (running) since Sun 2017-05-14 13:45:27 AEST; 29min ago Docs: man:systemd-resolved.service(8) http://www.freedesktop.org/wiki/Software/systemd/resolved http://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers http://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 12092 ExecStartPost=/bin/sh -c [ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved (code Main PID: 12089 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 4915) CGroup: /system.slice/systemd-resolved.service └─12089 /lib/systemd/systemd-resolved May 14 14:06:42 arapiles2 systemd-resolved[12089]: DNSSEC validation failed for question changelogs.ubuntu.com IN SOA: failed-auxiliary May 14 14:06:42 arapiles2 systemd-resolved[12089]: DNSSEC validation failed for question changelogs.ubuntu.com IN A: failed-auxiliary May 14 14:06:43 arapiles2 systemd-resolved[12089]: DNSSEC validation failed for question changelogs.ubuntu.com IN SOA: failed-auxiliary May 14 14:06:43 arapiles2 systemd-resolved[12089]: DNSSEC validation failed for question changelogs.ubuntu.com IN A: failed-auxiliary May 14 14:09:31 arapiles2 systemd-resolved[12089]: DNSSEC validation failed for question launchpad.net IN SOA: failed-auxiliary May 14 14:09:31 arapiles2 systemd-resolved[12089]: DNSSEC validation failed for question launchpad.net IN A: failed-auxiliary May 14 14:14:27 arapiles2 systemd-resolved[12089]: DNSSEC validation failed for question search.apps.ubuntu.com IN SOA: failed-auxiliary May 14 14:14:27 arapiles2 systemd-resolved[12089]: DNSSEC validation failed for question search.apps.ubuntu.com IN A: failed-auxiliary May 14 14:14:27 arapiles2 systemd-resolved[12089]: DNSSEC validation failed for question search.apps.ubuntu.com IN SOA: failed-auxiliary May 14 14:14:27 arapiles2 systemd-resolved[12089]: DNSSEC validation failed for question search.apps.ubuntu.com IN A: failed-auxiliary $ systemd-resolve --status Link 3 (wlp3s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: allow-downgrade DNSSEC supported: yes DNS Servers: 192.168.15.1 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 14 14:17:46 2017 InstallationDate: Installed on 2016-03-18 (421 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160317) MachineType: LENOVO 2764CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=3664c32a-e900-46b0-bd17-848f08c17bbe ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-05-13 (0 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 2764CTO dmi
[Touch-packages] [Bug 1686784] Re: no predictable names for platform (non-PCI) NICs
This bug was fixed in the package systemd - 233-6ubuntu2 --- systemd (233-6ubuntu2) artful; urgency=medium [ Michael Biebl ] * basic/journal-importer: Fix unaligned access in get_data_size() (Closes: #862062) [ Dimitri John Ledkov ] * ubuntu: disable dnssec on any ubuntu releases (LP: #1690605) * Cherrypick upstream patch for vio predictable interface names. * Cherrypick upstream patch for platform predictable interface names. (LP: #1686784) [ Balint Reczey ] * Skip starting systemd-remount-fs.service in containers even when /etc/fstab is present. This allows entering fully running state even when /etc/fstab lists / to be mounted from a device which is not present in the container. (LP: #1576341) -- Dimitri John Ledkov Wed, 17 May 2017 19:24:03 +0100 ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1686784 Title: no predictable names for platform (non-PCI) NICs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: New Bug description: [Impact] Systems may have NICs attached to the "platform" bus. These are NICs that are onboard, but not attached to a PCI(-like) bus. Rather, they are described by firmware directly. None of the naming policies enabled by Ubuntu by default matches these NICs, so they end up having unpredictable names. In the case where other NICs are attached (e.g. PCIe cards), the ethN enumeration race occurs, making it impossible to have an interface name that is persistent across reboots. That is, if you do a network install over "eth0", on reboot that NIC now maybe "eth3", which causes it to fail to start the network on boot. The HiSilicon D05 boards are an example of this. It has 4 onboard NICs that are described by ACPI directly, and may also have other PCIe NICs plugged in. [Test Case] Boot a system with the characteristics described above, and check to see if any "ethN" interfaces exist. [Regression Risk] TBD - depends on the proposed solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1686784/+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 1576341] Re: systemd in degraded state on startup in LXD containers
This bug was fixed in the package systemd - 233-6ubuntu2 --- systemd (233-6ubuntu2) artful; urgency=medium [ Michael Biebl ] * basic/journal-importer: Fix unaligned access in get_data_size() (Closes: #862062) [ Dimitri John Ledkov ] * ubuntu: disable dnssec on any ubuntu releases (LP: #1690605) * Cherrypick upstream patch for vio predictable interface names. * Cherrypick upstream patch for platform predictable interface names. (LP: #1686784) [ Balint Reczey ] * Skip starting systemd-remount-fs.service in containers even when /etc/fstab is present. This allows entering fully running state even when /etc/fstab lists / to be mounted from a device which is not present in the container. (LP: #1576341) -- Dimitri John Ledkov Wed, 17 May 2017 19:24:03 +0100 ** Changed in: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1576341 Title: systemd in degraded state on startup in LXD containers Status in lvm2 package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Status in open-iscsi package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Bug description: The ubuntu:xenial image shows 'degraded' state in lxd on initial boot. $ lxc launch xenial x1 $ sleep 10 $ lxc file pull x1/etc/cloud/build.info - build_name: server serial: 20160420-145324 $ lxc exec x1 systemctl is-system-running degraded $ lxc exec x1 -- systemctl --state=failed UNIT LOAD ACTIVE SUBDESCRIPTION ● dev-hugepages.mount loaded failed failed Huge Pages File System ● iscsid.serviceloaded failed failed iSCSI initiator daemon (iscsid) ● open-iscsi.serviceloaded failed failed Login to default iSCSI targets ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel File Systems ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables ● lvm2-lvmetad.socket loaded failed failed LVM2 metadata daemon socket ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 7 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 28 17:28:04 2016 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) SourcePackage: open-iscsi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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
