[Touch-packages] [Bug 1699694] [NEW] package click-apparmor 0.3.18 failed to install/upgrade: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 1
Public bug reported: r ProblemType: Package DistroRelease: Ubuntu 17.04 Package: click-apparmor 0.3.18 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Thu Jun 22 08:59:52 2017 ErrorMessage: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2017-01-24 (148 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: click-apparmor Title: package click-apparmor 0.3.18 failed to install/upgrade: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to zesty on 2017-04-14 (68 days ago) ** Affects: click-apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1699694 Title: package click-apparmor 0.3.18 failed to install/upgrade: le sous- processus script pre-removal installé a retourné une erreur de sortie d'état 1 Status in click-apparmor package in Ubuntu: New Bug description: r ProblemType: Package DistroRelease: Ubuntu 17.04 Package: click-apparmor 0.3.18 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Thu Jun 22 08:59:52 2017 ErrorMessage: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2017-01-24 (148 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: click-apparmor Title: package click-apparmor 0.3.18 failed to install/upgrade: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to zesty on 2017-04-14 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1699694/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693155] Re: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0)
Design says: "For now please revert to Gnome standard, we first want to get to a workable theme and once everything is converted to Gnome we can look at improving the icons (this might be an 18.04 timeframe)." ** Changed in: ubuntu-themes Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: ubuntu-themes Status: Confirmed => In Progress ** Changed in: ubuntu-ux Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693155 Title: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0) Status in Ubuntu theme: In Progress Status in Ubuntu UX: Fix Committed Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1693155/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699698] [NEW] apt removes package when packagename ends with -
Public bug reported: It turns out that if you mess up (like in your system automation setup) - and ask for installing a package named perl-byacc- (where you wanted to install perl-byacc-subname) - apt just chooses to remove perl-byacc.. even if perl-byacc is not installed - it returns 0 - meaning everything seems okay :( # apt install perl-byacc Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.4.0-64 linux-headers-4.4.0-64-generic linux-headers-4.4.0-67 linux-headers-4.4.0-67-generic linux-image-4.4.0-64-generic linux-image-4.4.0-67-generic linux-image-extra-4.4.0-64-generic linux-image-extra-4.4.0-67-generic Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: perl-byacc 0 upgraded, 1 newly installed, 0 to remove and 34 not upgraded. Need to get 105 kB of archives. After this operation, 203 kB of additional disk space will be used. Get:1 http://repo01.nms.tdc.net/ubuntu xenial/universe amd64 perl-byacc amd64 2.0-7 [105 kB] Fetched 105 kB in 0s (2.537 kB/s) Selecting previously unselected package perl-byacc. (Reading database ... 221007 files and directories currently installed.) Preparing to unpack .../perl-byacc_2.0-7_amd64.deb ... Unpacking perl-byacc (2.0-7) ... Processing triggers for man-db (2.7.5-1) ... Setting up perl-byacc (2.0-7) ... update-alternatives: using /usr/bin/pbyacc to provide /usr/bin/yacc (yacc) in auto mode # apt install perl-byacc- Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.4.0-64 linux-headers-4.4.0-64-generic linux-headers-4.4.0-67 linux-headers-4.4.0-67-generic linux-image-4.4.0-64-generic linux-image-4.4.0-67-generic linux-image-extra-4.4.0-64-generic linux-image-extra-4.4.0-67-generic Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: perl-byacc 0 upgraded, 0 newly installed, 1 to remove and 34 not upgraded. After this operation, 203 kB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 221041 files and directories currently installed.) Removing perl-byacc (2.0-7) ... Processing triggers for man-db (2.7.5-1) ... ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- 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/1699698 Title: apt removes package when packagename ends with - Status in apt package in Ubuntu: New Bug description: It turns out that if you mess up (like in your system automation setup) - and ask for installing a package named perl-byacc- (where you wanted to install perl-byacc-subname) - apt just chooses to remove perl-byacc.. even if perl-byacc is not installed - it returns 0 - meaning everything seems okay :( # apt install perl-byacc Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.4.0-64 linux-headers-4.4.0-64-generic linux-headers-4.4.0-67 linux-headers-4.4.0-67-generic linux-image-4.4.0-64-generic linux-image-4.4.0-67-generic linux-image-extra-4.4.0-64-generic linux-image-extra-4.4.0-67-generic Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: perl-byacc 0 upgraded, 1 newly installed, 0 to remove and 34 not upgraded. Need to get 105 kB of archives. After this operation, 203 kB of additional disk space will be used. Get:1 http://repo01.nms.tdc.net/ubuntu xenial/universe amd64 perl-byacc amd64 2.0-7 [105 kB] Fetched 105 kB in 0s (2.537 kB/s) Selecting previously unselected package perl-byacc. (Reading database ... 221007 files and directories currently installed.) Preparing to unpack .../perl-byacc_2.0-7_amd64.deb ... Unpacking perl-byacc (2.0-7) ... Processing triggers for man-db (2.7.5-1) ... Setting up perl-byacc (2.0-7) ... update-alternatives: using /usr/bin/pbyacc to provide /usr/bin/yacc (yacc) in auto mode # apt install perl-byacc- Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.4.0-64 linux-headers-4.4.0-64-generic linux-headers-4.4.0-67 linux-headers-4.4.0-67-generic linux-image-4.4.0-64-generic linux-image-4.4.0-67-generic linux-image-extra-4.4.0-64-generic linux-image-extra-4.4.0-67-generic Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: perl-byacc 0 upgraded, 0 newly installed, 1 to remove and 34 not upgraded. After this operation, 203 kB disk space will be
[Touch-packages] [Bug 1693155] Re: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0)
Although it appears tricky to just remove gnome-shell-related battery icon symlinks without causing the same changes to occur in Unity7 and unity-greeter. Needs more time and consideration than I have right now. ** Changed in: ubuntu-themes Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: ubuntu-themes Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693155 Title: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0) Status in Ubuntu theme: Confirmed Status in Ubuntu UX: Fix Committed Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1693155/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699698] Re: apt removes package when packagename ends with -
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1699698 Title: apt removes package when packagename ends with - Status in apt package in Ubuntu: Confirmed Bug description: It turns out that if you mess up (like in your system automation setup) - and ask for installing a package named perl-byacc- (where you wanted to install perl-byacc-subname) - apt just chooses to remove perl-byacc.. even if perl-byacc is not installed - it returns 0 - meaning everything seems okay :( # apt install perl-byacc Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.4.0-64 linux-headers-4.4.0-64-generic linux-headers-4.4.0-67 linux-headers-4.4.0-67-generic linux-image-4.4.0-64-generic linux-image-4.4.0-67-generic linux-image-extra-4.4.0-64-generic linux-image-extra-4.4.0-67-generic Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: perl-byacc 0 upgraded, 1 newly installed, 0 to remove and 34 not upgraded. Need to get 105 kB of archives. After this operation, 203 kB of additional disk space will be used. Get:1 http://repo01.nms.tdc.net/ubuntu xenial/universe amd64 perl-byacc amd64 2.0-7 [105 kB] Fetched 105 kB in 0s (2.537 kB/s) Selecting previously unselected package perl-byacc. (Reading database ... 221007 files and directories currently installed.) Preparing to unpack .../perl-byacc_2.0-7_amd64.deb ... Unpacking perl-byacc (2.0-7) ... Processing triggers for man-db (2.7.5-1) ... Setting up perl-byacc (2.0-7) ... update-alternatives: using /usr/bin/pbyacc to provide /usr/bin/yacc (yacc) in auto mode # apt install perl-byacc- Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.4.0-64 linux-headers-4.4.0-64-generic linux-headers-4.4.0-67 linux-headers-4.4.0-67-generic linux-image-4.4.0-64-generic linux-image-4.4.0-67-generic linux-image-extra-4.4.0-64-generic linux-image-extra-4.4.0-67-generic Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: perl-byacc 0 upgraded, 0 newly installed, 1 to remove and 34 not upgraded. After this operation, 203 kB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 221041 files and directories currently installed.) Removing perl-byacc (2.0-7) ... Processing triggers for man-db (2.7.5-1) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1699698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop
Just wanted to chime in to report I have the exact same problem (using Ubuntu 16.04), with the same GPU, GTX 1060 (in an MSI Apache Pro). No matter what I do, I cannot get the HDMI sound device to show up... One thing that changed things for me is if I restart the PC with the HDMI cable plugged in, I do get the HDMI device - but unfortunately it completely messes up the screens (it somehow thinks the external TV is my main monitor, laptop screen becomes unclickable... it really is a mess). Could this be connected to the graphics card drivers? I'm using the latest from the Ubuntu packages, 375. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1377653 Title: HDMI sound output not detected / NVIDIA optimus laptop Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Hi, not sure if this is an alsa or nvidia/nouveau bug. HDMI audio output doesn't appear in sound settings output panel. Audio works well on internal speakers, but it seems there is no way to make it output to hdmi... The laptop has optimus NVIDIA+Intel. The behaviour is the same with nouveau or nvidia proprietary driver. Please let me know if further testing is required ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam2295 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun Oct 5 17:05:35 2014 InstallationDate: Installed on 2014-04-21 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.215 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1283003 Title: Bluetooth headset/speakers listed but not selectable in Sound settings Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Invalid Status in gnome-bluetooth package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in blueman source package in Xenial: New Status in gnome-bluetooth source package in Xenial: New Status in pulseaudio source package in Xenial: Fix Committed Bug description: [Impact] Bluetooth headset/speakers are listed but not selectable in Sound settings (the correct device's options don't appear in the right pane). Hence no Bluetooth audio is unusable. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and try to select the device. Expected: The Bluetooth audio device is selectable (its options appear in the right pane when clicked and the selection stays on that device). [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://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 1699698] Re: apt removes package when packagename ends with -
It even says so in the apt(8) man page itself: The requested action can be overridden for specific packages by append a plus (+) to the package name to install this package or a minus (-) to remove it. -- 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/1699698 Title: apt removes package when packagename ends with - Status in apt package in Ubuntu: Invalid Bug description: It turns out that if you mess up (like in your system automation setup) - and ask for installing a package named perl-byacc- (where you wanted to install perl-byacc-subname) - apt just chooses to remove perl-byacc.. even if perl-byacc is not installed - it returns 0 - meaning everything seems okay :( # apt install perl-byacc Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.4.0-64 linux-headers-4.4.0-64-generic linux-headers-4.4.0-67 linux-headers-4.4.0-67-generic linux-image-4.4.0-64-generic linux-image-4.4.0-67-generic linux-image-extra-4.4.0-64-generic linux-image-extra-4.4.0-67-generic Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: perl-byacc 0 upgraded, 1 newly installed, 0 to remove and 34 not upgraded. Need to get 105 kB of archives. After this operation, 203 kB of additional disk space will be used. Get:1 http://repo01.nms.tdc.net/ubuntu xenial/universe amd64 perl-byacc amd64 2.0-7 [105 kB] Fetched 105 kB in 0s (2.537 kB/s) Selecting previously unselected package perl-byacc. (Reading database ... 221007 files and directories currently installed.) Preparing to unpack .../perl-byacc_2.0-7_amd64.deb ... Unpacking perl-byacc (2.0-7) ... Processing triggers for man-db (2.7.5-1) ... Setting up perl-byacc (2.0-7) ... update-alternatives: using /usr/bin/pbyacc to provide /usr/bin/yacc (yacc) in auto mode # apt install perl-byacc- Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.4.0-64 linux-headers-4.4.0-64-generic linux-headers-4.4.0-67 linux-headers-4.4.0-67-generic linux-image-4.4.0-64-generic linux-image-4.4.0-67-generic linux-image-extra-4.4.0-64-generic linux-image-extra-4.4.0-67-generic Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: perl-byacc 0 upgraded, 0 newly installed, 1 to remove and 34 not upgraded. After this operation, 203 kB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 221041 files and directories currently installed.) Removing perl-byacc (2.0-7) ... Processing triggers for man-db (2.7.5-1) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1699698/+subscriptions -- Mailing list: https://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 1699698] Re: apt removes package when packagename ends with -
Of course it does that. Just like specifying + at the end of a package name to remove means install. These are package modifiers, as documented in the apt-get manpage (and - is incredibly useful for packages not already installed, to prevent them from being installed). ** Changed in: apt (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1699698 Title: apt removes package when packagename ends with - Status in apt package in Ubuntu: Invalid Bug description: It turns out that if you mess up (like in your system automation setup) - and ask for installing a package named perl-byacc- (where you wanted to install perl-byacc-subname) - apt just chooses to remove perl-byacc.. even if perl-byacc is not installed - it returns 0 - meaning everything seems okay :( # apt install perl-byacc Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.4.0-64 linux-headers-4.4.0-64-generic linux-headers-4.4.0-67 linux-headers-4.4.0-67-generic linux-image-4.4.0-64-generic linux-image-4.4.0-67-generic linux-image-extra-4.4.0-64-generic linux-image-extra-4.4.0-67-generic Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: perl-byacc 0 upgraded, 1 newly installed, 0 to remove and 34 not upgraded. Need to get 105 kB of archives. After this operation, 203 kB of additional disk space will be used. Get:1 http://repo01.nms.tdc.net/ubuntu xenial/universe amd64 perl-byacc amd64 2.0-7 [105 kB] Fetched 105 kB in 0s (2.537 kB/s) Selecting previously unselected package perl-byacc. (Reading database ... 221007 files and directories currently installed.) Preparing to unpack .../perl-byacc_2.0-7_amd64.deb ... Unpacking perl-byacc (2.0-7) ... Processing triggers for man-db (2.7.5-1) ... Setting up perl-byacc (2.0-7) ... update-alternatives: using /usr/bin/pbyacc to provide /usr/bin/yacc (yacc) in auto mode # apt install perl-byacc- Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.4.0-64 linux-headers-4.4.0-64-generic linux-headers-4.4.0-67 linux-headers-4.4.0-67-generic linux-image-4.4.0-64-generic linux-image-4.4.0-67-generic linux-image-extra-4.4.0-64-generic linux-image-extra-4.4.0-67-generic Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: perl-byacc 0 upgraded, 0 newly installed, 1 to remove and 34 not upgraded. After this operation, 203 kB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 221041 files and directories currently installed.) Removing perl-byacc (2.0-7) ... Processing triggers for man-db (2.7.5-1) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1699698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
Also verified again by me using the proposed packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Committed Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Verify in Sound settings you have it set to A2DP mode. 3. Turn off and then on the Bluetooth device. 4. Verify the device has reconnected and if not, force it to in the Bluetooth indicator menu. 5. Open Sound settings again, select the device and verify it's reappeared in A2DP mode. 6. Click 'Test Sound'. Expected: Sound can be heard from the Bluetooth device. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1438510. Possibly others too. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1582213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~to
[Touch-packages] [Bug 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)
Verified. Using the proposed packages bluetooth audio no longer randomly refuses to use A2DP mode. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Status in pulseaudio source package in Xenial: Fix Committed Bug description: [Impact] Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and check the device's current "Mode". 3. If the current Mode is not yet A2DP then try to set it to A2DP Expected: The mode is either A2DP by default or can be set to it. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions -- Mailing list: https://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 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings
Verified. Using the proposed packages my bluetooth audio device is no longer randomly unselectable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1283003 Title: Bluetooth headset/speakers listed but not selectable in Sound settings Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Invalid Status in gnome-bluetooth package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in blueman source package in Xenial: New Status in gnome-bluetooth source package in Xenial: New Status in pulseaudio source package in Xenial: Fix Committed Bug description: [Impact] Bluetooth headset/speakers are listed but not selectable in Sound settings (the correct device's options don't appear in the right pane). Hence no Bluetooth audio is unusable. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and try to select the device. Expected: The Bluetooth audio device is selectable (its options appear in the right pane when clicked and the selection stays on that device). [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://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 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)
Although after some reboots and reconnects I found I could encounter similar bugs, the proposed packages are still much better than what's in xenial at present. It took a lot more effort to confuse and break the bluetooth audio mode than it usually does :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Status in pulseaudio source package in Xenial: Fix Committed Bug description: [Impact] Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and check the device's current "Mode". 3. If the current Mode is not yet A2DP then try to set it to A2DP Expected: The mode is either A2DP by default or can be set to it. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions -- Mailing list: https://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 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss
Unfortunately that did not work. I can confirm that http://people.canonical.com/~khfeng/lp1654448-artful/ does now remove the 'Headphone Mic Boost' option. However the headphone audio hiss remains, and now we have no workaround... -- 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/1654448 Title: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss Status in Dell Sputnik: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions -- Mailing list: https://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 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss
At a guess the cause of the problem may be some kind of headphone volume boost option that's turned on by default, and weirdly turned off by "'Headphone Mic Boost',0 1". This may not be avoidable interference as much as just excessive volume boost turned on by default. -- 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/1654448 Title: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss Status in Dell Sputnik: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions -- Mailing list: https://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 1576193] Re: software-properties-gtk complains about Gdk being imported without a version
Thanks for the fix @Miloš Pavlović!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1576193
Title:
software-properties-gtk complains about Gdk being imported without a
version
Status in software-properties package in Ubuntu:
Triaged
Bug description:
jik@jik5:~$ software-properties-gtk &
[1] 6387
jik@jik5:~$
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py:40:
PyGIWarning: Gdk was imported without specifying a version first. Use
gi.require_version('Gdk', '3.0') before import to ensure that the right version
gets loaded.
from gi.repository import GObject, Gdk, Gtk, Gio, GLib
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: software-properties-gtk 0.96.20
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 28 08:42:25 2016
InstallationDate: Installed on 2016-01-16 (103 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: Upgraded to xenial on 2016-04-28 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1576193/+subscriptions
--
Mailing list: https://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 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates
I added more debug messages and reproduced the issue again. Here are logs: lock_file: /var/run/unattended-upgrades.lock 1. xenial (unattended-upgrades-0.90ubuntu0.6): a. /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2017-06-22 03:43:09,028 WARNING - get_lock returned... 2017-06-22 03:43:09,040 WARNING - lock not taken b. $ ls /var/run/una* nothing 2. yakkety (unattended-upgrades-0.92ubuntu1.5): a. /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2017-06-22 03:35:21,038 WARNING - get_lock returned... 2017-06-22 03:35:21,052 WARNING - log_progress... 2017-06-22 03:35:21,066 WARNING - Unattended-upgrade in progress during shutdown, sleeping for 5s Progress: 17.1429 % (libreoffice-math) ... 2017-06-22 03:41:30,797 WARNING - Unattended-upgrade in progress during shutdown, sleeping for 5s Progress: 98.5525 % (initramfs-tools) 2017-06-22 03:41:35,816 WARNING - get_lock returned... 2017-06-22 03:41:35,833 WARNING - lock not taken 2017-06-22 03:41:35,866 INFO - All upgrades installed b. $ ls /var/run/una* /var/run/unattended-upgrades.lock /var/run/unattended-upgrades.progress $ sudo lslocks COMMAND PID TYPE SIZE MODE M STARTEND PATH ... unattended-upgr 3006 POSIX 0B WRITE 0 0 0 /run/unattended-upgrades.lock -- 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/1690980 Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699660] Re: systemd-resolve breaks resolution of local network hostnames
you should be able to opt-into UseDomains by creating /etc/systemd/network/usedomains.network [DNS] UseDomains=true I believe. does above help you resolve things? Can you tar up and attach the tarball of /run/systemd to investigate which links you have available, and what domains they have? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1699660 Title: systemd-resolve breaks resolution of local network hostnames Status in systemd package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 (zesty), resolution of my local network's host names is completely broken. Apparently the upgrade replaced my existing resolver with systemd-resolve, which deliberately refuses to pass "single-label" domain names to my domain name server. That is the server where all my network's host names are kept, so I can no longer resolve any of them. Apparently, this is yet another example of Poettering's upstream decisions causing denial of service to people who have been saddled with his malware. https://github.com/systemd/systemd/issues/2514#issuecomment-179203186 Would someone sensible please put a stop to this forced breakage during upgrade, and advise on how to fix it now that the damage has been done? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699752] [NEW] Indicator menu filled up with ballast/multiplicate entries
Public bug reported: Recently more and more unusable entries showed up in the network manager indicator. The "New mobile broadband connection" entry is listed 4 times -four lines each- and 4 specific GSM phones are listed that are not currently around. Currently I have 24 extra lines that I cant use for anything, they make no use, I already have to scroll down at the bottom edge of the screen to find the actual available connections. (see the screenshot) Release: Ubuntu 14.04.5 LTS network-manager-gnome: 0.9.8.8-0ubuntu4.5 I tried to delete all entries from /etc/NetworkManager/system-connections/ but the culprits show up again after a reboot. I also tried to purge and reinstall everything corresponding to the network manager. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "bazmeg.png" https://bugs.launchpad.net/bugs/1699752/+attachment/4900852/+files/bazmeg.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1699752 Title: Indicator menu filled up with ballast/multiplicate entries Status in network-manager package in Ubuntu: New Bug description: Recently more and more unusable entries showed up in the network manager indicator. The "New mobile broadband connection" entry is listed 4 times -four lines each- and 4 specific GSM phones are listed that are not currently around. Currently I have 24 extra lines that I cant use for anything, they make no use, I already have to scroll down at the bottom edge of the screen to find the actual available connections. (see the screenshot) Release: Ubuntu 14.04.5 LTS network-manager-gnome: 0.9.8.8-0ubuntu4.5 I tried to delete all entries from /etc/NetworkManager/system-connections/ but the culprits show up again after a reboot. I also tried to purge and reinstall everything corresponding to the network manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1699752/+subscriptions -- Mailing list: https://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 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT
The journal restart can be observed on zesty as well. However, the journal is not corrupted, the renaming and replacing took place as a safety measure due to unclean shutdown. $ sudo journalctl --verify --file=/run/log/journal/*/* PASS: /run/log/journal//6ff4e09ca827435bbe1b6efc2236a105/system.journal PASS: /run/log/journal//6ff4e09ca827435bbe1b6efc2236a105/system@00055289b166aebb-17bfde05076f84d2.journal~ PASS: /run/log/journal//6ff4e09ca827435bbe1b6efc2236a105/system@b7f19f66c640442d854033592fdedbb6-00013de4-0005528690181932.journal PASS: /run/log/journal//6ff4e09ca827435bbe1b6efc2236a105/system@b7f19f66c640442d854033592fdedbb6-00013569-000552843559e7e6.journal PASS: /run/log/journal//6ff4e09ca827435bbe1b6efc2236a105/system@b7f19f66c640442d854033592fdedbb6-00012d03-00055282a0e0b31b.journal PASS: /run/log/journal//6ff4e09ca827435bbe1b6efc2236a105/system@b7f19f66c640442d854033592fdedbb6-000124a8-000552806e21938c.journal PASS: /run/log/journal//6ff4e09ca827435bbe1b6efc2236a105/system@b7f19f66c640442d854033592fdedbb6-00011ca8-0005527efc9ec6de.journal PASS: /run/log/journal//6ff4e09ca827435bbe1b6efc2236a105/system@b7f19f66c640442d854033592fdedbb6-000114a4-0005527d2438261c.journal Was the journal corrupted in your case? ** Changed in: systemd (Ubuntu Artful) Status: New => Incomplete -- 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/1696970 Title: softlockup DoS causes systemd-journald.service to abort with SIGABORT Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Artful: Incomplete Bug description: I was running the new stress-ng softlockup stressor and observed that systemd-journald gets killed with an abort and this corrupts the systemd journal. How to reproduce: git clone git://kernel.ubuntu.com/cking/stress-ng cd stress-ng make clean; make sudo ./stress-ng --softlockup 0 -t 360 -v ..and wait for 360 seconds. dmesg shows the following, 100% reproduceable: [ 875.310331] systemd[1]: systemd-timesyncd.service: Watchdog timeout (limit 3min)! [ 875.310740] systemd[1]: systemd-timesyncd.service: Killing process 574 (systemd-timesyn) with signal SIGABRT. [ 875.327289] systemd[1]: systemd-timesyncd.service: Main process exited, code=killed, status=6/ABRT [ 875.327666] systemd[1]: systemd-timesyncd.service: Unit entered failed state. [ 875.327686] systemd[1]: systemd-timesyncd.service: Failed with result 'watchdog'. [ 875.327917] systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart. [ 875.327954] systemd[1]: Stopped Network Time Synchronization. [ 875.328845] systemd[1]: Starting Network Time Synchronization... [ 875.525071] systemd[1]: Started Network Time Synchronization. [ 875.539619] systemd[1]: systemd-journald.service: Main process exited, code=dumped, status=6/ABRT [ 875.544257] systemd-journald[5214]: File /run/log/journal/440e485e550040e3b93b66b2faae8525/system.journal corrupted or uncleanly shut down, renaming and replacing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1696970/+subscriptions -- Mailing list: https://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 1699755] [NEW] ubuntu_lttng_smoke_test failed on Artful: Kernel tracer not available
Public bug reported: Similar to bug 1677126, ubuntu_lttng_smoke_test failed on Artful too. == lttng smoke test list kernel events == Error: Unable to list kernel events: Kernel tracer not available Error: Command error FAILED (lttng list --kernel) FAILED (lttng list --kernel more output expected) == lttng smoke test trace open/close system calls == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-2107-session PASSED (lttng create) Error: Event open: Kernel tracer not available (channel channel0, session test-kernel-session) Error: Event openat: Kernel tracer not available (channel channel0, session test-kernel-session) Error: Event close: Kernel tracer not available (channel channel0, session test-kernel-session) FAILED (lttng enable-event) Session test-kernel-session destroyed == lttng smoke test trace context switches == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-2107-session PASSED (lttng create) Error: Event sched_switch: Kernel tracer not available (channel channel0, session test-kernel-session) FAILED (lttng enable-event) Complete test result: http://pastebin.ubuntu.com/24924042/ ** Affects: linux (Ubuntu) Importance: Medium Assignee: Colin Ian King (colin-king) Status: In Progress ** Package changed: apparmor (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1699755 Title: ubuntu_lttng_smoke_test failed on Artful: Kernel tracer not available Status in linux package in Ubuntu: In Progress Bug description: Similar to bug 1677126, ubuntu_lttng_smoke_test failed on Artful too. == lttng smoke test list kernel events == Error: Unable to list kernel events: Kernel tracer not available Error: Command error FAILED (lttng list --kernel) FAILED (lttng list --kernel more output expected) == lttng smoke test trace open/close system calls == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-2107-session PASSED (lttng create) Error: Event open: Kernel tracer not available (channel channel0, session test-kernel-session) Error: Event openat: Kernel tracer not available (channel channel0, session test-kernel-session) Error: Event close: Kernel tracer not available (channel channel0, session test-kernel-session) FAILED (lttng enable-event) Session test-kernel-session destroyed == lttng smoke test trace context switches == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-2107-session PASSED (lttng create) Error: Event sched_switch: Kernel tracer not available (channel channel0, session test-kernel-session) FAILED (lttng enable-event) Complete test result: http://pastebin.ubuntu.com/24924042/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699755/+subscriptions -- Mailing list: https://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 1699759] [NEW] LXC Alpine template broken on ppc64le
You have been subscribed to a public bug: == Comment: #0 - Breno Leitao - 2017-06-14 07:36:33 == LXC Alpine template is broken on Ubuntu 17.10, since it does not support ppc64le. It shows the following message: # Unknown architecture. == Comment: #1 - Breno Leitao - 2017-06-14 07:37:50 == Patch sent to upstream and accepted already: https://github.com/lxc/lxc/pull/1621#issuecomment-307887344 ** Affects: lxc (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-155728 severity-medium targetmilestone-inin1710 -- LXC Alpine template broken on ppc64le https://bugs.launchpad.net/bugs/1699759 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699759] [NEW] LXC Alpine template broken on ppc64le
Public bug reported: == Comment: #0 - Breno Leitao - 2017-06-14 07:36:33 == LXC Alpine template is broken on Ubuntu 17.10, since it does not support ppc64le. It shows the following message: # Unknown architecture. == Comment: #1 - Breno Leitao - 2017-06-14 07:37:50 == Patch sent to upstream and accepted already: https://github.com/lxc/lxc/pull/1621#issuecomment-307887344 ** Affects: lxc (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-155728 severity-medium targetmilestone-inin1710 ** Tags added: architecture-ppc64le bugnameltc-155728 severity-medium targetmilestone-inin1710 ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1699759 Title: LXC Alpine template broken on ppc64le Status in lxc package in Ubuntu: New Bug description: == Comment: #0 - Breno Leitao - 2017-06-14 07:36:33 == LXC Alpine template is broken on Ubuntu 17.10, since it does not support ppc64le. It shows the following message: # Unknown architecture. == Comment: #1 - Breno Leitao - 2017-06-14 07:37:50 == Patch sent to upstream and accepted already: https://github.com/lxc/lxc/pull/1621#issuecomment-307887344 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1699759/+subscriptions -- Mailing list: https://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 1699759] Re: LXC Alpine template broken on ppc64le
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Server Team (canonical-server) ** Changed in: ubuntu-power-systems Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1699759 Title: LXC Alpine template broken on ppc64le Status in The Ubuntu-power-systems project: New Status in lxc package in Ubuntu: New Bug description: == Comment: #0 - Breno Leitao - 2017-06-14 07:36:33 == LXC Alpine template is broken on Ubuntu 17.10, since it does not support ppc64le. It shows the following message: # Unknown architecture. == Comment: #1 - Breno Leitao - 2017-06-14 07:37:50 == Patch sent to upstream and accepted already: https://github.com/lxc/lxc/pull/1621#issuecomment-307887344 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1699759/+subscriptions -- Mailing list: https://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 1699772] [NEW] linux-image-4.4.0-81-generic Regression: Oracle Java plugin crashes
Public bug reported: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from > /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, > unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from > /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from > /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package > and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Package changed: mesa (Ubuntu) => linux (Ubuntu) ** CVE added: https://cve.mitre.org/cgi- bin/cvename.cgi?name=2017-1000364 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1699772 Title: linux-image-4.4.0-81-generic Regression: Oracle Java plugin crashes Status in linux package in Ubuntu: Confirmed Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server
[Touch-packages] [Bug 1699759] Re: LXC Alpine template broken on ppc64le
** Changed in: lxc (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1699759 Title: LXC Alpine template broken on ppc64le Status in The Ubuntu-power-systems project: New Status in lxc package in Ubuntu: Fix Committed Bug description: == Comment: #0 - Breno Leitao - 2017-06-14 07:36:33 == LXC Alpine template is broken on Ubuntu 17.10, since it does not support ppc64le. It shows the following message: # Unknown architecture. == Comment: #1 - Breno Leitao - 2017-06-14 07:37:50 == Patch sent to upstream and accepted already: https://github.com/lxc/lxc/pull/1621#issuecomment-307887344 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1699759/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699683] Re: package libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 failed to install/upgrade: függőségi hibák - e csomag beállítatlan maradt
Thanks for filing this bug in Ubuntu. Could you please try a few things: a) show us the output of: apt update apt-cache policy libgssapi-krb5-2 libnss3 libk5crypto3 b) Try this: sudo apt update sudo apt -f install c) If that doesn't work, then follow up with this attempt: sudo apt update sudo apt install --reinstall libgssapi-krb5-2 libnss3 libk5crypto3 Please include all output when reporting back. Thanks! ** Changed in: krb5 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1699683 Title: package libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 failed to install/upgrade: függőségi hibák - e csomag beállítatlan maradt Status in krb5 package in Ubuntu: Incomplete Bug description: i have no idea. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: libnss3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Jun 22 09:22:10 2017 ErrorMessage: függőségi hibák - e csomag beállítatlan maradt InstallationDate: Installed on 2017-05-31 (21 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: krb5 Title: package libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 failed to install/upgrade: függőségi hibák - e csomag beállítatlan maradt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1699683/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
I can confirm this bug. Works after wake up from suspend - after reboot: dead. So I've to put my computer into suspend mode and then wake it up in order to get sound in the headphone jack. -- 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 1699759] Re: LXC Alpine template broken on ppc64le
** Changed in: ubuntu-power-systems Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1699759 Title: LXC Alpine template broken on ppc64le Status in The Ubuntu-power-systems project: Fix Committed Status in lxc package in Ubuntu: Fix Committed Bug description: == Comment: #0 - Breno Leitao - 2017-06-14 07:36:33 == LXC Alpine template is broken on Ubuntu 17.10, since it does not support ppc64le. It shows the following message: # Unknown architecture. == Comment: #1 - Breno Leitao - 2017-06-14 07:37:50 == Patch sent to upstream and accepted already: https://github.com/lxc/lxc/pull/1621#issuecomment-307887344 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1699759/+subscriptions -- Mailing list: https://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 1699783] [NEW] package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libpng12-0/ANNOUNCE' partilhado, que é diferente de outras ins
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpng12-0 1.2.50-2+deb8u3 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 09:47:19 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu9 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 ErrorMessage: a tentar sobreescrever '/usr/share/doc/libpng12-0/ANNOUNCE' partilhado, que é diferente de outras instâncias do pacote libpng12-0:amd64 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libpng Title: package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libpng12-0/ANNOUNCE' partilhado, que é diferente de outras instâncias do pacote libpng12-0:amd64 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libpng (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 libpng in Ubuntu. https://bugs.launchpad.net/bugs/1699783 Title: package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libpng12-0/ANNOUNCE' partilhado, que é diferente de outras instâncias do pacote libpng12-0:amd64 Status in libpng package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpng12-0 1.2.50-2+deb8u3 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 09:47:19 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu9 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 ErrorMessage: a tentar sobreescrever '/usr/share/doc/libpng12-0/ANNOUNCE' partilhado, que é diferente de outras instâncias do pacote libpng12-0:amd64 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libpng Title: package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libpng12-0/ANNOUNCE' partilhado, que é diferente de outras instâncias do pacote libpng12-0:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpng/+bug/1699783/+subscriptions -- Mailing list: https://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 1681190] Re: I/O errors on disc from optical drive can block raising the network
Use kernel parameter "systemd.log_level=debug", then attach output of `journalctl -b` here. -- 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/1681190 Title: I/O errors on disc from optical drive can block raising the network Status in systemd package in Ubuntu: New Bug description: I'm using Ubuntu 17.04 dev with systemd 232-21ubuntu2 and I'm using an automounter which does also mount discs in optical drives and on having a damaged disk (from too much overwriting) in /dev/sr0 inserted I'm getting I/O errors as expected (blk_update_request: I/O error, dev sr0, sector 0) but the console shows then "A start job is running for Raise network interfaces" with a maximum time of 5 minutes and 2 seconds which doesn't progress until I'm ejecting the disc in /dev/sr0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1681190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d
** Also affects: rsyslog (Ubuntu Artful) Importance: Wishlist Status: New ** Also affects: rsyslog (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: rsyslog (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: rsyslog (Ubuntu Zesty) Importance: Medium => Wishlist ** Changed in: rsyslog (Ubuntu Trusty) Assignee: (unassigned) => Frode Nordahl (fnordahl) ** Changed in: rsyslog (Ubuntu Xenial) Assignee: (unassigned) => Frode Nordahl (fnordahl) ** Changed in: rsyslog (Ubuntu Yakkety) Assignee: (unassigned) => Frode Nordahl (fnordahl) ** Changed in: rsyslog (Ubuntu Zesty) Assignee: (unassigned) => Frode Nordahl (fnordahl) ** Changed in: rsyslog (Ubuntu Artful) Assignee: (unassigned) => Frode Nordahl (fnordahl) ** Changed in: rsyslog (Ubuntu Trusty) Importance: Wishlist => Low ** Changed in: rsyslog (Ubuntu Xenial) Importance: Wishlist => Low ** Changed in: rsyslog (Ubuntu Yakkety) Importance: Wishlist => Low ** Changed in: rsyslog (Ubuntu Zesty) Importance: Wishlist => Medium ** Changed in: rsyslog (Ubuntu Xenial) Importance: Low => Medium ** Changed in: rsyslog (Ubuntu Trusty) Importance: Low => Medium ** Changed in: rsyslog (Ubuntu Artful) Importance: Wishlist => Medium ** Changed in: rsyslog (Ubuntu Yakkety) Importance: Low => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1668639 Title: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d Status in rsyslog package in Ubuntu: New Status in rsyslog source package in Trusty: New Status in rsyslog source package in Xenial: New Status in rsyslog source package in Yakkety: New Status in rsyslog source package in Zesty: New Status in rsyslog source package in Artful: New Status in rsyslog package in Debian: Fix Released Bug description: [Impact] Servers or cloud instances will not log important messages after initial deployment. Manual reboot or restart of services is necessary to get expected behaviour. [Test Case] 1) Install, enable and start haproxy 2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed 3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT created 4) Restart rsyslog service 5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created 6) Restart haproxy service and observe that log now is filled with entries With the patched deb steps 3,4 and 6 becomes irrelevant and everything works out of the box. [Regression Potential] Minimal. This patch merges a patch from Debian where a trigger is added to the rsyslog package that fires when other debs drop files into /etc/rsyslog.d. [Original Bug Description] rsyslog should reload its configuration when other packages drop configuration in /etc/rsyslog.d https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337 https://anonscm.debian.org/cgit/collab- maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
10:29 bdmurray: opinion on bug 1562308 please? It seems to me that comment 17 is referring to some other bug, with no steps to reproduce provided. OTOH cosmos-door has a reproducer and confirmed it broken without and fixed with proposed, so I think this is OK to release. Do you agree? 6:07 rbasak: I looked for other bugs related to the commenter and found some recent activity from them so maybe they made a mistake? Also I'm looking at other less bugs to see if there is anything like their issue. 16:10 rbasak: I don't see anything similar to comment #17 so I think its fine. I suspect sexxxenator has a different bug, so I'm releasing this one. sexxxenator, please find or file a different bug for your issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Fix Released Status in less source package in Xenial: Fix Released Status in less source package in Yakkety: Fix Released Bug description: [Impact] Currently less doesn't work correctly with UTF-8 encoded Japanese characters, wrapping the lines in an invalid manner, missing or duplicating them (see original description below for exact error cases). For locale like these it breaks the general workflow, making the tool unreliable. [Test Case] 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top and only the first part of the wrapped line should be shown. 5. Type "k", then you will see "001", "002" and "003" at the top. [Regression Potential] Rather low as the fix is present in the beta version of less for over 5 months already, which seems to be enough time for general audience testing. But since the width tables are modified potentially this could lead to other similar breakages related to wide-character handling. [Original Description] When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://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 1562308] Update Released
The verification of the Stable Release Update for less has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Fix Released Status in less source package in Xenial: Fix Released Status in less source package in Yakkety: Fix Released Bug description: [Impact] Currently less doesn't work correctly with UTF-8 encoded Japanese characters, wrapping the lines in an invalid manner, missing or duplicating them (see original description below for exact error cases). For locale like these it breaks the general workflow, making the tool unreliable. [Test Case] 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top and only the first part of the wrapped line should be shown. 5. Type "k", then you will see "001", "002" and "003" at the top. [Regression Potential] Rather low as the fix is present in the beta version of less for over 5 months already, which seems to be enough time for general audience testing. But since the width tables are modified potentially this could lead to other similar breakages related to wide-character handling. [Original Description] When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://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 1416768] Re: Fontconfig error output due to malformed conf file
This doesn't just affect Steam. I see the same error when running Cura (3D printer slicer program). See attached log. ** Attachment added: "Cura-2.6.0.log" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1416768/+attachment/4900919/+files/Cura-2.6.0.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1416768 Title: Fontconfig error output due to malformed conf file Status in One Hundred Papercuts: Confirmed Status in fontconfig package in Ubuntu: Confirmed Bug description: Generating new string page texture 121: 256x256, total string texture memory is 393.22 KB Generating new string page texture 122: 128x256, total string texture memory is 2.79 MB Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 78: saw unknown, expected number Generating new string page texture 136: 2048x256, total string texture memory is 4.88 MB Installing breakpad exception handler for appid(steamwebhelper)/version(20150130171142) Installing breakpad exception handler for appid(steamwebhelper)/version(1422637902) Above output is produced, eg by steam when running a game. The fontconfig error lines can be verified with "fc-cache -v | grep -i err". The offending section is around original lines 70, 78: false 1.0 matrix pixelsizefixupfactor 0 0 pixelsizefixupfactor size pixelsizefixupfactor Note that the element has 2 child elements when it should only have 1. Removal of the second "pixelsizefixupfactor" solves the error. After this removal neither fc-cache nor steam report an "Fontconfig error:". The documentation for fonts.conf, eg http://linux.die.net/man/5/fonts- conf, suggests that the element should hold 4 elements: > > >This element holds the four elements of an affine transformation. But it appears not to produce an error when only 2 elements are present (and does produce an error here when there are 4, for me). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: fontconfig-config 2.11.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 1 00:46:10 2015 InstallationDate: Installed on 2012-11-02 (820 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) PackageArchitecture: all SourcePackage: fontconfig UpgradeStatus: Upgraded to utopic on 2015-01-28 (3 days ago) modified.conffile..etc.fonts.conf.avail.10.scale.bitmap.fonts.conf: [modified] mtime.conffile..etc.fonts.conf.avail.10.scale.bitmap.fonts.conf: 2015-02-01T00:30:44.308962 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1416768/+subscriptions -- Mailing list: https://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 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
This bug was fixed in the package less - 481-2.1ubuntu1.1 --- less (481-2.1ubuntu1.1) yakkety; urgency=medium * debian/patches/lp-1562308-fix_mkutable.patch: - Fix east asian width problem (LP: #1562308) -- Mitsuya Shibata Sat, 25 Mar 2017 03:00:03 +0900 ** Changed in: less (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Fix Released Status in less source package in Xenial: Fix Released Status in less source package in Yakkety: Fix Released Bug description: [Impact] Currently less doesn't work correctly with UTF-8 encoded Japanese characters, wrapping the lines in an invalid manner, missing or duplicating them (see original description below for exact error cases). For locale like these it breaks the general workflow, making the tool unreliable. [Test Case] 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top and only the first part of the wrapped line should be shown. 5. Type "k", then you will see "001", "002" and "003" at the top. [Regression Potential] Rather low as the fix is present in the beta version of less for over 5 months already, which seems to be enough time for general audience testing. But since the width tables are modified potentially this could lead to other similar breakages related to wide-character handling. [Original Description] When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://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 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
This bug was fixed in the package less - 481-2.1ubuntu0.2 --- less (481-2.1ubuntu0.2) xenial; urgency=medium * debian/patches/lp-1562308-fix_mkutable.patch: - Fix east asian width problem (LP: #1562308) -- Mitsuya Shibata Sat, 25 Mar 2017 03:00:03 +0900 ** Changed in: less (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Fix Released Status in less source package in Xenial: Fix Released Status in less source package in Yakkety: Fix Released Bug description: [Impact] Currently less doesn't work correctly with UTF-8 encoded Japanese characters, wrapping the lines in an invalid manner, missing or duplicating them (see original description below for exact error cases). For locale like these it breaks the general workflow, making the tool unreliable. [Test Case] 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top and only the first part of the wrapped line should be shown. 5. Type "k", then you will see "001", "002" and "003" at the top. [Regression Potential] Rather low as the fix is present in the beta version of less for over 5 months already, which seems to be enough time for general audience testing. But since the width tables are modified potentially this could lead to other similar breakages related to wide-character handling. [Original Description] When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://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 1699104] Re: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить
*** This bug is a duplicate of bug 1696865 *** https://bugs.launchpad.net/bugs/1696865 ** This bug has been marked a duplicate of bug 1696865 package grub-common 2.02~beta3-4ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1699104 Title: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить Status in util-linux package in Ubuntu: New Bug description: weird stuff ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue Jun 20 12:56:16 2017 DpkgTerminalLog: dpkg: ошибка при обработке пакета util-linux (--configure): пакет абсолютно неработоспособен; перед настройкой его следует переустановить ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его следует переустановить InstallationDate: Installed on 2016-10-02 (260 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1699104/+subscriptions -- Mailing list: https://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 980519] Re: Random log off in Ubuntu 12.04 LTS
the same issue is reflected in ubuntu 16.04 lts ...Any remedy for this issue? -- 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/980519 Title: Random log off in Ubuntu 12.04 LTS Status in Unity: Fix Released Status in gnome-desktop package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Status in Fedora: New Bug description: I get logged off from Ubuntu sometimes. There is no error message or any indication that it is going to log off. The screen goes black, and after 2-4 seconds, i get presented with the Ubuntu Log On Screen. There is no clear pattern (or at least if have not noticed any). One time i am working with Netbeans, another time i am using firefox. This also means that at present i can not clearly say what package might be causing this behaviour. I am fairly sure the problem lies in 12.04 (or more precise - the combination of 12.04 and the hardware i am using). I do not have the same problem running 11.04 or 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+subscriptions -- Mailing list: https://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 1699826] Re: I get this error on login every time - package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error e
*** 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 Packages that trigger multiple debconf prompts fail to install -- 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/1699826 Title: I get this error on login every time - 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: I get this error on login every time ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Thu Jun 22 15:59:10 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-22 (0 days ago) InstallationMedia: Ubuntu-GNOME 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/1699826/+subscriptions -- Mailing list: https://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 1699826] [NEW] I get this error on login every time - package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: I get this error on login every time ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Thu Jun 22 15:59:10 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-22 (0 days ago) InstallationMedia: Ubuntu-GNOME 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/1699826 Title: I get this error on login every time - 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: I get this error on login every time ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Thu Jun 22 15:59:10 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-22 (0 days ago) InstallationMedia: Ubuntu-GNOME 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/1699826/+subscriptions -- Mailing list: https://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 1624644] Re: Unable to automatically remove packages that become unused in conjunction with updating by other software
** Changed in: unattended-upgrades (Ubuntu Artful) Assignee: (unassigned) => Steve Langasek (vorlon) ** Changed in: unattended-upgrades (Ubuntu Artful) Assignee: Steve Langasek (vorlon) => Canonical Foundations Team (canonical-foundations) -- 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/1624644 Title: Unable to automatically remove packages that become unused in conjunction with updating by other software Status in unattended-upgrades package in Ubuntu: Confirmed Status in unattended-upgrades source package in Artful: Confirmed Bug description: When using default settings for unattended-upgrades i.e. Unattended-Upgrade::Remove-Unused-Dependencies "false"; # default "false" Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; # default "true" in configuration file /etc/apt/apt.conf.d/50unattended-upgrades, U-U is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because U-U compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:28:44 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades 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/1624644/+subscriptions -- Mailing list: https://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 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows
** Changed in: unattended-upgrades (Ubuntu Artful) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: unattended-upgrades (Ubuntu Zesty) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: unattended-upgrades (Ubuntu Yakkety) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: unattended-upgrades (Ubuntu Xenial) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: apt (Ubuntu Artful) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: apt (Ubuntu Zesty) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: apt (Ubuntu Yakkety) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: apt (Ubuntu Xenial) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- 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/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: In Progress Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: In Progress Status in unattended-upgrades source package in Yakkety: Triaged Status in apt source package in Zesty: In Progress Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Released Status in unattended-upgrades source package in Artful: Triaged Status in apt package in Debian: Fix Released Status in unattended-upgrades package in Debian: New Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : htt
[Touch-packages] [Bug 1686803] Re: sudo returns exit code 0 if child is killed with SIGTERM
Updating the bug; let's keep this assigned to Balint; I uploaded the sudo update to artful as well as the SRUs (and subscribed ~ubuntu-sru) ** Tags removed: rls-aa-incoming ** Changed in: sudo (Ubuntu Artful) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: sudo (Ubuntu Zesty) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: sudo (Ubuntu Yakkety) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: sudo (Ubuntu Xenial) Assignee: (unassigned) => Balint Reczey (rbalint) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1686803 Title: sudo returns exit code 0 if child is killed with SIGTERM Status in sudo: Unknown Status in sudo package in Ubuntu: Triaged Status in sudo source package in Xenial: New Status in sudo source package in Yakkety: New Status in sudo source package in Zesty: New Status in sudo source package in Artful: Triaged Bug description: [Impact] * sudo returns exit code 0 if child is killed with signals other than SIGINT * This can break scripts assuming successful execution of the command ran by sudo [Test Case] * Open two separate shells 1. In shell 1. run: ubuntu@tough-calf:~$ sudo sleep 300; echo $? 2. In shell 2. run: root@tough-calf:~# killall -TERM sleep 3. In broken versions shell 1. shows this: ubuntu@tough-calf:~$ sudo sleep 300; echo $? 0 4. Install fixed version 5. Execute steps 1. and 2. 6. In fixed version shell 1. shows this: ubuntu@tough-calf:~$ sudo sleep 300; echo $? Terminated 143 [Regression Potential] * sudo may exit with a different status than expected [Other Info] original bug description: Please backport upstream sudo changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the" to xenial, yakkety, and zesty versions of sudo. This will fix a regression documented by this upstream bug report: https://bugzilla.sudo.ws/show_bug.cgi?id=784 sudo 1.8.15 changeset 10229:153f016db8f1 "When the command sudo is running is killed by a signal, sudo will" introduced a regression where the exit status is always 0 when a command is killed by a signal other than SIGINT. https://www.sudo.ws/repos/sudo/rev/153f016db8f1 This will be fixed in sudo 1.8.20 with changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the". https://www.sudo.ws/repos/sudo/rev/50b988d0c97f trusty sudo is based off sudo 1.8.9 and is not affected. xenial sudo based off sudo 1.8.16, yaketty sudo based off sudo 1.8.16, and zesty sudo based off 1.8.19 need the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/1686803/+subscriptions -- Mailing list: https://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 1687122] Re: /usr/bin/add-apt-repository:OSError:/usr/bin/add-apt-repository@168:add_source_from_shortcut:/usr/bin/add-apt-repository@172
** Tags removed: rls-aa-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1687122 Title: /usr/bin/add-apt-repository:OSError:/usr/bin/add-apt- repository@168:add_source_from_shortcut:/usr/bin/add-apt- repository@172 Status in software-properties package in Ubuntu: New Status in software-properties source package in Artful: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.96.24.13, the problem page at https://errors.ubuntu.com/problem/01a945aed47dfff0cdfea51c5923f51cadeafb00 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1687122/+subscriptions -- Mailing list: https://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 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies
** No longer affects: update-notifier (Ubuntu Artful) ** No longer affects: update-manager (Ubuntu Artful) ** No longer affects: ubuntu-mate-welcome (Ubuntu Artful) ** No longer affects: ubuntu-mate-meta (Ubuntu Artful) ** No longer affects: ubiquity (Ubuntu Artful) ** No longer affects: software-properties (Ubuntu Artful) ** No longer affects: sessioninstaller (Ubuntu Artful) ** No longer affects: mythbuntu-control-centre (Ubuntu Artful) ** No longer affects: lubuntu-software-center (Ubuntu Artful) ** No longer affects: language-selector (Ubuntu Artful) ** No longer affects: aptdaemon (Ubuntu Artful) ** No longer affects: apturl (Ubuntu Artful) ** No longer affects: dell-recovery (Ubuntu Artful) ** No longer affects: gnome-software (Ubuntu Artful) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1673258 Title: Remove aptdaemon and drop or port its reverse-dependencies Status in aptdaemon package in Ubuntu: New Status in apturl package in Ubuntu: New Status in dell-recovery package in Ubuntu: New Status in gnome-software package in Ubuntu: New Status in language-selector package in Ubuntu: New Status in lubuntu-software-center package in Ubuntu: New Status in mythbuntu-control-centre package in Ubuntu: New Status in sessioninstaller package in Ubuntu: New Status in software-properties package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-mate-welcome package in Ubuntu: New Status in update-manager package in Ubuntu: New Status in update-notifier package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: Fix Released Bug description: aptdaemon is abandoned and unmaintained. It has already been dropped from Debian, but there are several reverse dependencies keeping it in Ubuntu. I will add bug tasks for each of those dependencies, which should be ported or dropped themselves. Then we can get rid of aptdaemon too. See this mailing list thread for more details: https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port- from-aptdaemon-to-packagekit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449001] Re: systemd-resolved: please do not use Google public DNS by default
** Tags removed: rls-aa-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1449001 Title: systemd-resolved: please do not use Google public DNS by default Status in systemd: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: New Status in systemd source package in Artful: Fix Committed Status in systemd package in Debian: Fix Released Bug description: systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.) in the absence of other configured DNS servers. systemd-resolved is not enabled by default in Ubuntu 15.04, but it is installed by default and will behave in this way if enabled by the user. $ cat /etc/systemd/resolved.conf (...) # Entries in this file show the compile time defaults. (...) #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844 This raises privacy concerns since in the event of accidental misconfiguration DNS queries will be sent unencrypted across the internet, and potentially also security concerns given systemd- resolved does not perform DNSSEC validation and is not particularly well hardened against malicious responses e.g. from a MITM (http://www.openwall.com/lists/oss-security/2014/11/12/5). I believe that it would be better to fail safe if no DNS server is configured -- i.e. have DNS lookups fail; it's better that the user is aware of their misconfiguration, rather than silently sending their queries to Google. The user can intentionally opt to use Google public DNS if they wish. Steps to reproduce: 1. Remove existing DNS configuration (from /etc/network/interfaces, /etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*) 2. Reboot, or otherwise clear relevant state 3. sudo service systemd-resolved start 4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf 5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by default), observe that DNS lookups probably still work, and queries are being sent to one of Google's servers Possible workaround/bugfix: ship a resolved.conf which clears the FallbackDNS parameter. This issue has been discussed in the Debian BTS (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658). My interpretation of the Debian package maintainer's position is that a user concerned with the privacy implications shouldn't let systemd get into a state where it uses the fallback DNS servers (quoting Marco d'Itri: "Short summary: have a resolv.conf file or use DHCP"). I would argue that it's safest not to have fallback DNS servers configured at all by default. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1449001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449001] Re: systemd-resolved: please do not use Google public DNS by default
** Changed in: systemd (Debian) Status: Unknown => 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/1449001 Title: systemd-resolved: please do not use Google public DNS by default Status in systemd: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: New Status in systemd source package in Artful: Fix Committed Status in systemd package in Debian: Fix Released Bug description: systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.) in the absence of other configured DNS servers. systemd-resolved is not enabled by default in Ubuntu 15.04, but it is installed by default and will behave in this way if enabled by the user. $ cat /etc/systemd/resolved.conf (...) # Entries in this file show the compile time defaults. (...) #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844 This raises privacy concerns since in the event of accidental misconfiguration DNS queries will be sent unencrypted across the internet, and potentially also security concerns given systemd- resolved does not perform DNSSEC validation and is not particularly well hardened against malicious responses e.g. from a MITM (http://www.openwall.com/lists/oss-security/2014/11/12/5). I believe that it would be better to fail safe if no DNS server is configured -- i.e. have DNS lookups fail; it's better that the user is aware of their misconfiguration, rather than silently sending their queries to Google. The user can intentionally opt to use Google public DNS if they wish. Steps to reproduce: 1. Remove existing DNS configuration (from /etc/network/interfaces, /etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*) 2. Reboot, or otherwise clear relevant state 3. sudo service systemd-resolved start 4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf 5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by default), observe that DNS lookups probably still work, and queries are being sent to one of Google's servers Possible workaround/bugfix: ship a resolved.conf which clears the FallbackDNS parameter. This issue has been discussed in the Debian BTS (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658). My interpretation of the Debian package maintainer's position is that a user concerned with the privacy implications shouldn't let systemd get into a state where it uses the fallback DNS servers (quoting Marco d'Itri: "Short summary: have a resolv.conf file or use DHCP"). I would argue that it's safest not to have fallback DNS servers configured at all by default. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1449001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681190] Re: I/O errors on disc from optical drive can block raising the network
I assume I shall do this if this issue appears again with a damaged disc. If I have one again in the future I'm attaching the output in case I don't forget it then. -- 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/1681190 Title: I/O errors on disc from optical drive can block raising the network Status in systemd package in Ubuntu: New Bug description: I'm using Ubuntu 17.04 dev with systemd 232-21ubuntu2 and I'm using an automounter which does also mount discs in optical drives and on having a damaged disk (from too much overwriting) in /dev/sr0 inserted I'm getting I/O errors as expected (blk_update_request: I/O error, dev sr0, sector 0) but the console shows then "A start job is running for Raise network interfaces" with a maximum time of 5 minutes and 2 seconds which doesn't progress until I'm ejecting the disc in /dev/sr0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1681190/+subscriptions -- Mailing list: https://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 1699481] Re: RM: obsolete product
Removing packages from artful: address-book-app 0.2+17.04.20161219-0ubuntu1 in artful address-book-app 0.2+17.04.20161219-0ubuntu1 in artful amd64 address-book-app 0.2+17.04.20161219-0ubuntu1 in artful armhf address-book-app 0.2+17.04.20161219-0ubuntu1 in artful i386 address-book-app-autopilot 0.2+17.04.20161219-0ubuntu1 in artful amd64 address-book-app-autopilot 0.2+17.04.20161219-0ubuntu1 in artful arm64 address-book-app-autopilot 0.2+17.04.20161219-0ubuntu1 in artful armhf address-book-app-autopilot 0.2+17.04.20161219-0ubuntu1 in artful i386 address-book-app-autopilot 0.2+17.04.20161219-0ubuntu1 in artful ppc64el address-book-app-autopilot 0.2+17.04.20161219-0ubuntu1 in artful s390x address-book-app-dbg 0.2+17.04.20161219-0ubuntu1 in artful amd64 address-book-app-dbg 0.2+17.04.20161219-0ubuntu1 in artful armhf address-book-app-dbg 0.2+17.04.20161219-0ubuntu1 in artful i386 qtdeclarative5-ubuntu-addressbook0.1 0.2+17.04.20161219-0ubuntu1 in artful amd64 qtdeclarative5-ubuntu-addressbook0.1 0.2+17.04.20161219-0ubuntu1 in artful arm64 qtdeclarative5-ubuntu-addressbook0.1 0.2+17.04.20161219-0ubuntu1 in artful armhf qtdeclarative5-ubuntu-addressbook0.1 0.2+17.04.20161219-0ubuntu1 in artful i386 qtdeclarative5-ubuntu-addressbook0.1 0.2+17.04.20161219-0ubuntu1 in artful ppc64el qtdeclarative5-ubuntu-addressbook0.1 0.2+17.04.20161219-0ubuntu1 in artful s390x qtdeclarative5-ubuntu-contacts0.1 0.2+17.04.20161219-0ubuntu1 in artful amd64 qtdeclarative5-ubuntu-contacts0.1 0.2+17.04.20161219-0ubuntu1 in artful arm64 qtdeclarative5-ubuntu-contacts0.1 0.2+17.04.20161219-0ubuntu1 in artful armhf qtdeclarative5-ubuntu-contacts0.1 0.2+17.04.20161219-0ubuntu1 in artful i386 qtdeclarative5-ubuntu-contacts0.1 0.2+17.04.20161219-0ubuntu1 in artful ppc64el qtdeclarative5-ubuntu-contacts0.1 0.2+17.04.20161219-0ubuntu1 in artful s390x Comment: Part of Ubuntu Phone, no longer developed; LP: #1699481 1 package successfully removed. ** Changed in: address-book-app (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1699481 Title: RM: obsolete product Status in address-book-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Bug description: dialer-app, messaging-app, address-book-app were components of Ubuntu Phone which are no longer developed. Please remove these from Ubuntu Archive. 1. $ reverse-depends src:dialer-app No reverse dependencies found $ reverse-depends -b src:dialer-app No reverse dependencies found 2. $ reverse-depends src:messaging-app No reverse dependencies found $ reverse-depends -b src:messaging-app No reverse dependencies found 3. $ reverse-depends -b src:address-book-app Reverse-Build-Depends = * dialer-app(for qtdeclarative5-ubuntu-addressbook0.1) * messaging-app (for qtdeclarative5-ubuntu-addressbook0.1) $ reverse-depends src:address-book-app Reverse-Depends === * dialer-app(for qtdeclarative5-ubuntu-addressbook0.1) * dialer-app-autopilot (for address-book-app-autopilot) * messaging-app (for qtdeclarative5-ubuntu-addressbook0.1) * messaging-app-autopilot (for address-book-app-autopilot) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1699481/+subscriptions -- Mailing list: https://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 1699481] Re: RM: obsolete product
Removing packages from artful: dialer-app 0.1+17.04.20161209-0ubuntu1 in artful dialer-app 0.1+17.04.20161209-0ubuntu1 in artful amd64 dialer-app 0.1+17.04.20161209-0ubuntu1 in artful arm64 dialer-app 0.1+17.04.20161209-0ubuntu1 in artful armhf dialer-app 0.1+17.04.20161209-0ubuntu1 in artful i386 dialer-app 0.1+17.04.20161209-0ubuntu1 in artful ppc64el dialer-app 0.1+17.04.20161209-0ubuntu1 in artful s390x dialer-app-autopilot 0.1+17.04.20161209-0ubuntu1 in artful amd64 dialer-app-autopilot 0.1+17.04.20161209-0ubuntu1 in artful arm64 dialer-app-autopilot 0.1+17.04.20161209-0ubuntu1 in artful armhf dialer-app-autopilot 0.1+17.04.20161209-0ubuntu1 in artful i386 dialer-app-autopilot 0.1+17.04.20161209-0ubuntu1 in artful ppc64el dialer-app-autopilot 0.1+17.04.20161209-0ubuntu1 in artful s390x Comment: Part of Ubuntu Phone, no longer developed; LP: #1699481 1 package successfully removed. ** Changed in: dialer-app (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1699481 Title: RM: obsolete product Status in address-book-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Bug description: dialer-app, messaging-app, address-book-app were components of Ubuntu Phone which are no longer developed. Please remove these from Ubuntu Archive. 1. $ reverse-depends src:dialer-app No reverse dependencies found $ reverse-depends -b src:dialer-app No reverse dependencies found 2. $ reverse-depends src:messaging-app No reverse dependencies found $ reverse-depends -b src:messaging-app No reverse dependencies found 3. $ reverse-depends -b src:address-book-app Reverse-Build-Depends = * dialer-app(for qtdeclarative5-ubuntu-addressbook0.1) * messaging-app (for qtdeclarative5-ubuntu-addressbook0.1) $ reverse-depends src:address-book-app Reverse-Depends === * dialer-app(for qtdeclarative5-ubuntu-addressbook0.1) * dialer-app-autopilot (for address-book-app-autopilot) * messaging-app (for qtdeclarative5-ubuntu-addressbook0.1) * messaging-app-autopilot (for address-book-app-autopilot) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1699481/+subscriptions -- Mailing list: https://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 1699481] Re: RM: obsolete product
Removing packages from artful: messaging-app 0.1+17.04.20161130-0ubuntu1 in artful messaging-app 0.1+17.04.20161130-0ubuntu1 in artful amd64 messaging-app 0.1+17.04.20161130-0ubuntu1 in artful arm64 messaging-app 0.1+17.04.20161130-0ubuntu1 in artful armhf messaging-app 0.1+17.04.20161130-0ubuntu1 in artful i386 messaging-app 0.1+17.04.20161130-0ubuntu1 in artful ppc64el messaging-app 0.1+17.04.20161130-0ubuntu1 in artful s390x messaging-app-autopilot 0.1+17.04.20161130-0ubuntu1 in artful amd64 messaging-app-autopilot 0.1+17.04.20161130-0ubuntu1 in artful arm64 messaging-app-autopilot 0.1+17.04.20161130-0ubuntu1 in artful armhf messaging-app-autopilot 0.1+17.04.20161130-0ubuntu1 in artful i386 messaging-app-autopilot 0.1+17.04.20161130-0ubuntu1 in artful ppc64el messaging-app-autopilot 0.1+17.04.20161130-0ubuntu1 in artful s390x Comment: Part of Ubuntu Phone, no longer developed; LP: #1699481 1 package successfully removed. ** Changed in: messaging-app (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1699481 Title: RM: obsolete product Status in address-book-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Bug description: dialer-app, messaging-app, address-book-app were components of Ubuntu Phone which are no longer developed. Please remove these from Ubuntu Archive. 1. $ reverse-depends src:dialer-app No reverse dependencies found $ reverse-depends -b src:dialer-app No reverse dependencies found 2. $ reverse-depends src:messaging-app No reverse dependencies found $ reverse-depends -b src:messaging-app No reverse dependencies found 3. $ reverse-depends -b src:address-book-app Reverse-Build-Depends = * dialer-app(for qtdeclarative5-ubuntu-addressbook0.1) * messaging-app (for qtdeclarative5-ubuntu-addressbook0.1) $ reverse-depends src:address-book-app Reverse-Depends === * dialer-app(for qtdeclarative5-ubuntu-addressbook0.1) * dialer-app-autopilot (for address-book-app-autopilot) * messaging-app (for qtdeclarative5-ubuntu-addressbook0.1) * messaging-app-autopilot (for address-book-app-autopilot) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1699481/+subscriptions -- Mailing list: https://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 1310294] Re: apt is missing build-dep changelog and source commands.
Was fixed some time ago ** Changed in: apt (Ubuntu) Status: New => Fix Released -- 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/1310294 Title: apt is missing build-dep changelog and source commands. Status in apt package in Ubuntu: Fix Released Bug description: I like that there is now single command to do what previously needed multiple different commands unless you used aptitude. I aliased those commands to apt when apt exists and noticed that three commands are missing. ``` # 100 LC_ALL=C apt build-dep E: Invalid operation build-dep ``` build-dep is important command to me, I use it often. And now that apt has process bar, it would be even nicer to have. ``` # 100 LC_ALL=C apt source E: Invalid operation source # 100 LC_ALL=C apt changelog E: Invalid operation changelog ``` I don't use source and changelog so often, but sometimes I need them too. I know that I can use \aptitude build-dep, but that is missing the process bar. I hope to see these three commands and those that I didn't notice missing, but which are important in future version. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: LXDE Date: Sun Apr 20 17:40:40 2014 InstallationDate: Installed on 2014-02-01 (78 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1310294/+subscriptions -- Mailing list: https://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 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
> bdmurray Thanks, uploading! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Fix Released Status in less source package in Xenial: Fix Released Status in less source package in Yakkety: Fix Released Bug description: [Impact] Currently less doesn't work correctly with UTF-8 encoded Japanese characters, wrapping the lines in an invalid manner, missing or duplicating them (see original description below for exact error cases). For locale like these it breaks the general workflow, making the tool unreliable. [Test Case] 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top and only the first part of the wrapped line should be shown. 5. Type "k", then you will see "001", "002" and "003" at the top. [Regression Potential] Rather low as the fix is present in the beta version of less for over 5 months already, which seems to be enough time for general audience testing. But since the width tables are modified potentially this could lead to other similar breakages related to wide-character handling. [Original Description] When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://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 1699850] [NEW] Reliable network connectivity for apt-daily
Public bug reported: [Impact] apt-daily.service is launched by a timer that depends on network- online.target (after the fixes for bug 1686470 are in everywhere) At boot that is mostly sufficient for it to have network online, but it does not seem to work all the time, and we might be disagreeing with network-manager and friends what online state means. At resume time, network-online.target is still active, so the service is started as soon as possible when it tries to catch up. Depending on the timing, the network connectivity might not be there yet, and it will fail and only retry 12 hours later. [Proposed solution] Introduce a new apt-helper wait-online that tries to connect() to remote hosts specified in sources.list until one connection works or a TIMEOUT is reached. The proposed algorithm looks something like this: while (time elapsed < TIMEOUT): for each entry: host = gethostbyname() if host failed: continue fd = connect to it if fd is invalid: continue all fds += fd if poll(all fds, 100 ms timeout) finds a connected one: exit(0) exit(42) # timeout There are two things to consider: * gethostbyname() and connect() may fail if network is not up yet, so we need to retry (we might need to sleep somewhere) * If poll() fails, we likely sleep enough, so no extra sleep needed. I believe the time out should be something like 30s. On the systemd service side, we add: ExecStartPre=/usr/lib/apt/apt-helper wait-online RestartForceExitStatus=42 RestartSec=15m To retry the service after 15 minutes. [Test case] * Start apt-daily.service after turning off network -> It should wait (in ExecStartPre) * Turn on network -> apt-daily.service should start [Regression potential] There might be increased I/O activity after resume, if that did not work before. ** Affects: apt (Ubuntu) Importance: High Assignee: Julian Andres Klode (juliank) Status: Triaged ** Changed in: apt (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Description changed: [Impact] apt-daily.service is launched by a timer that depends on network- online.target (after the fixes for 1686470 are in everywhere) At boot that is mostly sufficient for it to have network online, but it does not seem to work all the time, and we might be disagreeing with network-manager and friends what online state means. At resume time, network-online.target is still active, so the service is started as soon as possible when it tries to catch up. Depending on the timing, the network connectivity might not be there yet, and it will fail and only retry 12 hours later. [Proposed solution] Introduce a new apt-helper wait-online that tries to connect() to remote hosts specified in sources.list until one connection works or a TIMEOUT is reached. The proposed algorithm looks something like this: while (time elapsed < TIMEOUT): - for each entry: - host = gethostbyname() - if host failed: - continue - fd = connect to it - if fd is invalid: - continue + for each entry: + host = gethostbyname() + if host failed: + continue + fd = connect to it + if fd is invalid: + continue - all fds += fd - - if poll(all fds, 100 ms timeout) finds a connected one: - exit(0) + all fds += fd + + if poll(all fds, 100 ms timeout) finds a connected one: + exit(0) exit(42) # timeout There are two things to consider: * gethostbyname() and connect() may fail if network is not up yet, so we need to retry (we might need to sleep somewhere) * If poll() fails, we likely sleep enough, so no extra sleep needed. I believe the time out should be something like 30s. On the systemd service side, we add: - RestartForceExitStatus=42 - RestartSec=15m + ExecStartPre=/usr/lib/apt/apt-helper wait-online + RestartForceExitStatus=42 + RestartSec=15m To retry the service after 15 minutes. + + [Test case] + * Start apt-daily.service after turning off network -> It should wait (in ExecStartPre) + * Turn on network -> apt-daily.service should start + + [Regression potential] + There might be increased I/O activity after resume, if that did not work before. ** Changed in: apt (Ubuntu) Status: New => Triaged ** Changed in: apt (Ubuntu) Importance: Undecided => High ** Description changed: [Impact] apt-daily.service is launched by a timer that depends on network- - online.target (after the fixes for 1686470 are in everywhere) + online.target (after the fixes for bug 1686470 are in everywhere) At boot that is mostly sufficient for it to have network online, but it does not seem to work all the time, and we might be disagreeing with network-manager and friends what online state means. At resume time, network-online.target is still active, so the service is started as soon as possible when it tries to catch up.
[Touch-packages] [Bug 1699493] Re: RM: obsolete product
Removing packages from artful: bluetooth-touch 0.3.3+16.04.20160201-0ubuntu1 in artful bluetooth-touch 0.3.3+16.04.20160201-0ubuntu1 in artful amd64 bluetooth-touch 0.3.3+16.04.20160201-0ubuntu1 in artful arm64 bluetooth-touch 0.3.3+16.04.20160201-0ubuntu1 in artful armhf bluetooth-touch 0.3.3+16.04.20160201-0ubuntu1 in artful i386 bluetooth-touch 0.3.3+16.04.20160201-0ubuntu1 in artful ppc64el bluetooth-touch 0.3.3+16.04.20160201-0ubuntu1 in artful s390x Comment: Part of Ubuntu Phone, no longer developed; LP: #1699493 1 package successfully removed. ** Changed in: bluetooth-touch (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluetooth-touch in Ubuntu. https://bugs.launchpad.net/bugs/1699493 Title: RM: obsolete product Status in bluetooth-touch package in Ubuntu: Fix Released Bug description: bluetooth-touch was a components of Ubuntu Phone which is no longer developed. Please remove bluetooth-touch from the Ubuntu Archive $ reverse-depends -b src:bluetooth-touch No reverse dependencies found $ reverse-depends src:bluetooth-touch No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1699493/+subscriptions -- Mailing list: https://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 1699850] Re: Reliable network connectivity for apt-daily
** Description changed: [Impact] apt-daily.service is launched by a timer that depends on network- online.target (after the fixes for bug 1686470 are in everywhere) At boot that is mostly sufficient for it to have network online, but it does not seem to work all the time, and we might be disagreeing with network-manager and friends what online state means. At resume time, network-online.target is still active, so the service is started as soon as possible when it tries to catch up. Depending on the timing, the network connectivity might not be there yet, and it will fail and only retry 12 hours later. [Proposed solution] Introduce a new apt-helper wait-online that tries to connect() to remote hosts specified in sources.list until one connection works or a TIMEOUT is reached. The proposed algorithm looks something like this: while (time elapsed < TIMEOUT): for each entry: - host = gethostbyname() + host = getaddrinfo() if host failed: continue fd = connect to it if fd is invalid: continue all fds += fd if poll(all fds, 100 ms timeout) finds a connected one: exit(0) exit(42) # timeout There are two things to consider: - * gethostbyname() and connect() may fail if network is not up yet, so we need to retry (we might need to sleep somewhere) + * getaddrinfo() and connect() may fail if network is not up yet, so we need to retry (we might need to sleep somewhere) * If poll() fails, we likely sleep enough, so no extra sleep needed. I believe the time out should be something like 30s. On the systemd service side, we add: ExecStartPre=/usr/lib/apt/apt-helper wait-online RestartForceExitStatus=42 RestartSec=15m To retry the service after 15 minutes. [Test case] * Start apt-daily.service after turning off network -> It should wait (in ExecStartPre) * Turn on network -> apt-daily.service should start [Regression potential] There might be increased I/O activity after resume, if that did not work before. -- 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/1699850 Title: Reliable network connectivity for apt-daily Status in apt package in Ubuntu: Triaged Bug description: [Impact] apt-daily.service is launched by a timer that depends on network- online.target (after the fixes for bug 1686470 are in everywhere) At boot that is mostly sufficient for it to have network online, but it does not seem to work all the time, and we might be disagreeing with network-manager and friends what online state means. At resume time, network-online.target is still active, so the service is started as soon as possible when it tries to catch up. Depending on the timing, the network connectivity might not be there yet, and it will fail and only retry 12 hours later. [Proposed solution] Introduce a new apt-helper wait-online that tries to connect() to remote hosts specified in sources.list until one connection works or a TIMEOUT is reached. The proposed algorithm looks something like this: while (time elapsed < TIMEOUT): for each entry: host = getaddrinfo() if host failed: continue fd = connect to it if fd is invalid: continue all fds += fd if poll(all fds, 100 ms timeout) finds a connected one: exit(0) exit(42) # timeout There are two things to consider: * getaddrinfo() and connect() may fail if network is not up yet, so we need to retry (we might need to sleep somewhere) * If poll() fails, we likely sleep enough, so no extra sleep needed. I believe the time out should be something like 30s. On the systemd service side, we add: ExecStartPre=/usr/lib/apt/apt-helper wait-online RestartForceExitStatus=42 RestartSec=15m To retry the service after 15 minutes. [Test case] * Start apt-daily.service after turning off network -> It should wait (in ExecStartPre) * Turn on network -> apt-daily.service should start [Regression potential] There might be increased I/O activity after resume, if that did not work before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1699850/+subscriptions -- Mailing list: https://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 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings
Can we get an update for Zesty? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1283003 Title: Bluetooth headset/speakers listed but not selectable in Sound settings Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Invalid Status in gnome-bluetooth package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in blueman source package in Xenial: New Status in gnome-bluetooth source package in Xenial: New Status in pulseaudio source package in Xenial: Fix Committed Bug description: [Impact] Bluetooth headset/speakers are listed but not selectable in Sound settings (the correct device's options don't appear in the right pane). Hence no Bluetooth audio is unusable. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and try to select the device. Expected: The Bluetooth audio device is selectable (its options appear in the right pane when clicked and the selection stays on that device). [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://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 1682154] Re: loginctl ignoring user given sessions IDs at command-line
This bug was fixed in the package systemd - 233-8ubuntu1 --- systemd (233-8ubuntu1) artful; urgency=medium Merge from experimental. Existing Ubuntu cherry-picks: * TEST-12: cherry-pick upstream fix for compat with new netcat-openbsd. * networkd: cherry-pick support for setting bridge port's priority. This is a useful feature/bugfix to improve feature parity of networkd with ifupdown. This matches netplan's expectations to be able to set bridge port's priorities via networked. This featue is to be used by netplan/MAAS/OpenStack. * Cherrypick upstream commit to enable system use kernel maximum limit for RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. * debian/tests/root-unittests: disable execute and seccomp tests on arm test-seccomp and test-execute fail on arm64 kernels. Marking both tests as expected failures. An upstream bug report is filed to resolve these. * Cherrypick upstream patch for vio predictable interface names. * Cherrypick upstream patch for platform predictable interface names. Ubuntu cherry-picks, now also applied in Debian: * resolved: fix null pointer dereference crash Remaining Ubuntu delta: * ubuntu: udev.postinst preserve virtio interfaces names on upgrades, on s390x. New udev generates stable interface names on s390x kvm instances, however, upon upgrades existing ethX names should be preserved to prevent breaking networking and software configurations. This patch only affects Ubuntu systems. * 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. New Ubuntu cherry-picks: * loginctl: Chrerry-pick upstream fix to not ignore multiple session ids. (LP: #1682154) -- Dimitri John Ledkov Mon, 19 Jun 2017 15:24:30 +0100 ** Changed in: systemd (Ubuntu) Status: Triaged => 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/1682154 Title: loginctl ignoring user given sessions IDs at command-line Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Zesty: Triaged Bug description: Kubuntu zesty, 232-21ubuntu2 See upstream bug https://github.com/systemd/systemd/issues/5733 with patch attached. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1682154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699660] Re: systemd-resolve breaks resolution of local network hostnames
According to the systemd documentation, UseDomains only affects systems that get their network setup from DHCP, which is not the case at my site. Furthermore, it is documented as a way to add a DNS search domain, which would not help resolve hosts that have no domains. So far, the only way I have found to fix the breakage is to manually disable systemd-resolve and configure a resolver that actually works properly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1699660 Title: systemd-resolve breaks resolution of local network hostnames Status in systemd package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 (zesty), resolution of my local network's host names is completely broken. Apparently the upgrade replaced my existing resolver with systemd-resolve, which deliberately refuses to pass "single-label" domain names to my domain name server. That is the server where all my network's host names are kept, so I can no longer resolve any of them. Apparently, this is yet another example of Poettering's upstream decisions causing denial of service to people who have been saddled with his malware. https://github.com/systemd/systemd/issues/2514#issuecomment-179203186 Would someone sensible please put a stop to this forced breakage during upgrade, and advise on how to fix it now that the damage has been done? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604010] Re: sntp missing
This bug was fixed in the package ntp - 1:4.2.8p10+dfsg-5ubuntu1 --- ntp (1:4.2.8p10+dfsg-5ubuntu1) artful; urgency=medium * Merge with Debian unstable (LP: #1604010). Remaining changes: - d/ntp.conf, d/ntpdate.default: Change default server to ntp.ubuntu.com. - Add PPS support (LP 1512980): + debian/README.Debian: Add a PPS section to the README.Debian, removed all PPSkit one. + debian/ntp.conf: Add some configuration examples from the offical documentation. * Drop Changes (contribs accepted in Debian): - Apparmor bits not yet accepted in Debian + d/apparmor-profile add samba winbindd pipe (LP 1582767) - Fix ntpdate-debian to be able to parse new config of ntp (LP 1576698) - d/rules: enable debugging - d/rules, d/ntp.dirs, d/source_ntp.py: Add apport hook. + d/source_ntp.py: includes a filter on AppArmor profile names to prevent false positives from denials originating in other packages -- Christian Ehrhardt Wed, 21 Jun 2017 16:17:38 +0200 ** Changed in: ntp (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1604010 Title: sntp missing Status in Ubuntu Server Guide: New Status in ntp package in Ubuntu: Fix Released Status in ntp package in Debian: Fix Released Bug description: In Ubuntu 16.04, the binary file /usr/bin/sntp is missing from the package ntp. The associated man page /usr/share/man/man1/sntp.1.gz is still included. How to reproduce: $ sudo apt-get install ntp $ dpkg-query -L ntp | grep sntp /usr/share/man/man1/sntp.1.gz Expected result: /usr/bin/sntp was included in Ubuntu 14.04: $ dpkg-query -L ntp | grep sntp /usr/bin/sntp /usr/share/man/man1/sntp.1.gz The sntp program remains a very useful tool for interactively testing on the command line the offset of the local clock to a remote NTP server (like "ntpdate -qu [ntp-server]" previously). It should be included in the same package as its man page. To manage notifications about this bug go to: https://bugs.launchpad.net/serverguide/+bug/1604010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692543] Re: Regression tests cannot write to apparmor path_max module parameter in artful/4.11
What if the test was changed to check writability of path_max? Just changing the the check for the sysfs path to -w won't work for root, but maybe something like this (perhaps there's a simpler way to do the check though): if [[ -f /sys/module/apparmor/parameters/path_max && $(stat -c "%a" /sys/module/apparmor/parameters/path_max) == "600" ]] ; then buf_max=2048#standard x86 page size/2 old_max=`cat /sys/module/apparmor/parameters/path_max` echo $buf_max > /sys/module/apparmor/parameters/path_max else echo "WARNING: This version of AppArmor does not support changing buffer size." fi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1692543 Title: Regression tests cannot write to apparmor path_max module parameter in artful/4.11 Status in apparmor package in Ubuntu: New Bug description: The longpath regression tests tries to write to /sys/module/apparmor/parameters/path_max, but this is read-only in artful/4.11: commit cdc8e09e16bb7eb7d23fcbdbe416aa91770fb4d6 Author: John Johansen Date: Thu Apr 6 05:14:20 2017 -0700 apparmor: Make path_max parameter readonly This is causing ADT to fail. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful-canonical-kernel-team- ppa/artful/amd64/l/linux/20170519_170900_9130b@/log.gz running longpath longpath.sh: line 53: /sys/module/apparmor/parameters/path_max: Permission denied Fatal Error (longpath): Unexpected shell error. Run with -x to debug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1692543/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699604] Re: package linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Attachment removed: "DuplicateSignature.txt" https://bugs.launchpad.net/bugs/1699604/+attachment/4900532/+files/DuplicateSignature.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1699604 Title: package linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: The laptop does not resume on suspend. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Thu Jun 22 00:35:28 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2017-05-14 (38 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: initramfs-tools Title: package linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1699604/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699604] DuplicateSignature.txt
Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise! ** Attachment added: "DuplicateSignature.txt" https://bugs.launchpad.net/bugs/1699604/+attachment/4901126/+files/DuplicateSignature.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1699604 Title: package linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: The laptop does not resume on suspend. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Thu Jun 22 00:35:28 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2017-05-14 (38 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: initramfs-tools Title: package linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1699604/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699784] Re: package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libpng12-0/ANNOUNCE' partilhado, que é diferente de outras instâ
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpng in Ubuntu. https://bugs.launchpad.net/bugs/1699784 Title: package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libpng12-0/ANNOUNCE' partilhado, que é diferente de outras instâncias do pacote libpng12-0:amd64 Status in libpng package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpng12-0 1.2.50-2+deb8u3 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 09:47:19 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu9 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 ErrorMessage: a tentar sobreescrever '/usr/share/doc/libpng12-0/ANNOUNCE' partilhado, que é diferente de outras instâncias do pacote libpng12-0:amd64 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libpng Title: package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libpng12-0/ANNOUNCE' partilhado, que é diferente de outras instâncias do pacote libpng12-0:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpng/+bug/1699784/+subscriptions -- Mailing list: https://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 1692543] Re: Regression tests cannot write to apparmor path_max module parameter in artful/4.11
yes something like this should work. However 600 will not be the correct check, as in some cases the owner may differ, especially in the virtualized case because vfs doesn't let us virtualize the file's owner. Currently this file isn't virtualized to the poilicy namespace, and that is why the restriction was put in place to keep containers from doing things they shouldn't with other policy namespaces. It will be virtualized by 4.14, we can land that change in Ubuntu for 17.10 and SRU. We have no plans to require/use bind mounts to get around owner virtualization, but with the 4.13 we added the ability for securityfs to do magic symlinks, which allows a virtualization like nsfs is doing. We could make this a magic symlink to a file owned by the correct user if need be, in which case 600 would be sufficient. I think for now the test needs to be for any possible write, 222, so we will need to do some masking on the returned value. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1692543 Title: Regression tests cannot write to apparmor path_max module parameter in artful/4.11 Status in apparmor package in Ubuntu: New Bug description: The longpath regression tests tries to write to /sys/module/apparmor/parameters/path_max, but this is read-only in artful/4.11: commit cdc8e09e16bb7eb7d23fcbdbe416aa91770fb4d6 Author: John Johansen Date: Thu Apr 6 05:14:20 2017 -0700 apparmor: Make path_max parameter readonly This is causing ADT to fail. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful-canonical-kernel-team- ppa/artful/amd64/l/linux/20170519_170900_9130b@/log.gz running longpath longpath.sh: line 53: /sys/module/apparmor/parameters/path_max: Permission denied Fatal Error (longpath): Unexpected shell error. Run with -x to debug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1692543/+subscriptions -- Mailing list: https://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 1698967] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed')
** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1698967/+attachment/4898872/+files/JournalErrors.txt ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1698967 Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') Status in util-linux package in Ubuntu: New Bug description: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bsdutils 1:2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: bsdutils:amd64: Configure axel:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Jun 18 17:43:58 2017 DpkgTerminalLog: dpkg: error processing package bsdutils (--configure): package bsdutils is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-06-15 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils 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/util-linux/+bug/1698967/+subscriptions -- Mailing list: https://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 1698639] Re: graphic dont work
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1698639 Title: graphic dont work Status in xorg package in Ubuntu: New Bug description: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. cat: /var/log/lightdm/x-0-greeter.log: Nie ma takiego pliku ani katalogu cat: /var/log/lightdm/x-0-greeter.log.old: Nie ma takiego pliku ani katalogu Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 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: Sun Jun 18 13:06:42 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-54-generic, x86_64: installed nvidia-381, 381.22, 4.8.0-54-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:397d] InstallationDate: Installed on 2017-06-15 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO HuronRiver Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic root=UUID=223aa3e7-2866-4e97-adde-818a33f681ad ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN47WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr45CN47WW:bd02/15/2012:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: HuronRiver Platform dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Jun 17 16:52:14 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1698639/+subscriptions -- Mailing list: https://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 1699903] [NEW] lxc-sshd won't start with 2.0.8
Public bug reported: On a xenial system after an update to lxc, starting a container created with the lxc-sshd template fails consistently. This does not occur with 2.0.7. root@xenial:~# lxc-create -n mysshd -t /usr/share/lxc/templates/lxc-sshd Generating public/private rsa key pair. Your identification has been saved in /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_rsa_key. Your public key has been saved in /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_rsa_key.pub. The key fingerprint is: SHA256:eR4Kv8JpWxe+RvIudD8LTuOYSGmLdnmX1CgB3Y/IHP4 root@xenial The key's randomart image is: +---[RSA 2048]+ | . . | | . o . | | = o o | |*.. .| | . So+o | | ++=Eo.| | .+++BBo | |.+B+oO=+o| | ..o+++== .o | +[SHA256]-+ Generating public/private dsa key pair. Your identification has been saved in /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_dsa_key. Your public key has been saved in /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_dsa_key.pub. The key fingerprint is: SHA256:Jmet2LLZMtolKBhfDQ/Za4i3yr0/993umj4Hq0D8Qyg root@xenial The key's randomart image is: +---[DSA 1024]+ | | | o | |+ . | | . * o o | |. . + E S o | | + o + X + .| |. o o + = o o | | . + .+B.. ooo. | | o ++==..oo=*+ | +[SHA256]-+ root@xenial:~# lxc-start -n mysshd --logfile mysshd.log lxc-start: tools/lxc_start.c: main: 366 The container failed to start. lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode. lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options. root@xenial:~# cat mysshd.log lxc-start 20170622214710.829 ERRORlxc_conf - conf.c:lxc_setup_dev_console:1473 - Read-only file system - error unlinking /usr/lib/x86_64-linux-gnu/lxc/dev/console lxc-start 20170622214710.829 ERRORlxc_conf - conf.c:lxc_setup:4055 - failed to setup the console for 'mysshd' lxc-start 20170622214710.829 ERRORlxc_start - start.c:do_start:811 - Failed to setup container "mysshd". lxc-start 20170622214710.829 ERRORlxc_sync - sync.c:__sync_wait:57 - An error occurred in another process (expected sequence number 3) lxc-start 20170622214710.868 ERRORlxc_start - start.c:__lxc_start:1358 - Failed to spawn container "mysshd". lxc-start 20170622214715.901 ERRORlxc_start_ui - tools/lxc_start.c:main:366 - The container failed to start. lxc-start 20170622214715.901 ERRORlxc_start_ui - tools/lxc_start.c:main:368 - To get more details, run the container in foreground mode. lxc-start 20170622214715.901 ERRORlxc_start_ui - tools/lxc_start.c:main:370 - Additional information can be obtained by setting the --logfile and --logpriority options. root@xenial:~# dpkg -l '*lxc*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== un liblxc0 (no description available) ii liblxc12.0.8-0ubuntu1~16.04.2 amd64 Linux Containers userspace tools (library) ii lxc2.0.8-0ubuntu1~16.04.2 all Transitional package for lxc1 ii lxc-common 2.0.8-0ubuntu1~16.04.2 amd64 Linux Containers userspace tools (common tools) ii lxc-templates 2.0.8-0ubuntu1~16.04.2 amd64 Linux Containers userspace tools (templates) ii lxc1 2.0.8-0ubuntu1~16.04.2 amd64 Linux Containers userspace tools ii lxcfs 2.0.6-0ubuntu1~16.04.1 amd64 FUSE based filesystem for LXC un lxctl (no description available) ii python3-lxc2.0.8-0ubuntu1~16.04.2 amd64 Linux Containers userspace tools (Python 3.x bindings) Removing the addition of the bind-mount for /dev to the config from the template seems to move the start along, yet implications of doing this are unknown. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1699903 Title: lxc-sshd won't start with 2.0.8 St
[Touch-packages] [Bug 1699903] Re: lxc-sshd won't start with 2.0.8
Hi Miroslav, Yes, we've been hardening the console handling code quite a bit prior to this release. It seems that you are on a read-only file system which prevents LXC from removing the underlying "/dev/console" file that already exists. LXC wants to remove this file since it wants to prevent bind-mounting over a possible malicious file. Is the read-only filesystem intentional? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1699903 Title: lxc-sshd won't start with 2.0.8 Status in lxc package in Ubuntu: New Bug description: On a xenial system after an update to lxc, starting a container created with the lxc-sshd template fails consistently. This does not occur with 2.0.7. root@xenial:~# lxc-create -n mysshd -t /usr/share/lxc/templates/lxc-sshd Generating public/private rsa key pair. Your identification has been saved in /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_rsa_key. Your public key has been saved in /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_rsa_key.pub. The key fingerprint is: SHA256:eR4Kv8JpWxe+RvIudD8LTuOYSGmLdnmX1CgB3Y/IHP4 root@xenial The key's randomart image is: +---[RSA 2048]+ | . . | | . o . | | = o o | |*.. .| | . So+o | | ++=Eo.| | .+++BBo | |.+B+oO=+o| | ..o+++== .o | +[SHA256]-+ Generating public/private dsa key pair. Your identification has been saved in /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_dsa_key. Your public key has been saved in /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_dsa_key.pub. The key fingerprint is: SHA256:Jmet2LLZMtolKBhfDQ/Za4i3yr0/993umj4Hq0D8Qyg root@xenial The key's randomart image is: +---[DSA 1024]+ | | | o | |+ . | | . * o o | |. . + E S o | | + o + X + .| |. o o + = o o | | . + .+B.. ooo. | | o ++==..oo=*+ | +[SHA256]-+ root@xenial:~# lxc-start -n mysshd --logfile mysshd.log lxc-start: tools/lxc_start.c: main: 366 The container failed to start. lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode. lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options. root@xenial:~# cat mysshd.log lxc-start 20170622214710.829 ERRORlxc_conf - conf.c:lxc_setup_dev_console:1473 - Read-only file system - error unlinking /usr/lib/x86_64-linux-gnu/lxc/dev/console lxc-start 20170622214710.829 ERRORlxc_conf - conf.c:lxc_setup:4055 - failed to setup the console for 'mysshd' lxc-start 20170622214710.829 ERRORlxc_start - start.c:do_start:811 - Failed to setup container "mysshd". lxc-start 20170622214710.829 ERRORlxc_sync - sync.c:__sync_wait:57 - An error occurred in another process (expected sequence number 3) lxc-start 20170622214710.868 ERRORlxc_start - start.c:__lxc_start:1358 - Failed to spawn container "mysshd". lxc-start 20170622214715.901 ERRORlxc_start_ui - tools/lxc_start.c:main:366 - The container failed to start. lxc-start 20170622214715.901 ERRORlxc_start_ui - tools/lxc_start.c:main:368 - To get more details, run the container in foreground mode. lxc-start 20170622214715.901 ERRORlxc_start_ui - tools/lxc_start.c:main:370 - Additional information can be obtained by setting the --logfile and --logpriority options. root@xenial:~# dpkg -l '*lxc*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== un liblxc0 (no description available) ii liblxc12.0.8-0ubuntu1~16.04.2 amd64 Linux Containers userspace tools (library) ii lxc2.0.8-0ubuntu1~16.04.2 all Transitional package for lxc1 ii lxc-common 2.0.8-0ubuntu1~16.04.2 amd64 Linux Containers userspace tools (common tools) ii lxc-templates 2.0.8-0ubuntu1~16.04.2 amd64 Linux Containers userspace tools (templates) ii lxc1 2.0.8-0ubuntu1~16.04.2 amd64 Linux Containers userspace tools ii lxcfs 2.0.6-0ubuntu1~16.04
[Touch-packages] [Bug 1699903] Re: lxc-sshd won't start with 2.0.8
Our actual templates are based on the lxc-sshd template example that comes with lxc-templates. There, basically all the lxc is is bind-mounts for necessary paths from the host, obviously read-only: # grep mount.entry /usr/share/lxc/templates/lxc-sshd lxc.mount.entry = /dev dev none ro,bind 0 0 lxc.mount.entry = /lib lib none ro,bind 0 0 lxc.mount.entry = /bin bin none ro,bind 0 0 lxc.mount.entry = /usr usr none ro,bind 0 0 lxc.mount.entry = /sbin sbin none ro,bind 0 0 lxc.mount.entry = tmpfs run/sshd tmpfs mode=0644 0 0 lxc.mount.entry = /usr/share/lxc/templates/lxc-sshd $init_path none ro,bind 0 0 lxc.mount.entry = /etc/init.d etc/init.d none ro,bind 0 0 lxc.mount.entry = /etc/sysconfig/network-scripts etc/sysconfig/network-scripts none ro,bind 0 0 lxc.mount.entry = /etc/rc.d etc/rc.d none ro,bind 0 0 lxc.mount.entry = /lib64 lib64 none ro,bind 0 0 Perhaps bind-mounting /dev isn't needed anymore, though then I'd like to know why the example does that, and what the implications are of leaving the /dev entry out. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1699903 Title: lxc-sshd won't start with 2.0.8 Status in lxc package in Ubuntu: New Bug description: On a xenial system after an update to lxc, starting a container created with the lxc-sshd template fails consistently. This does not occur with 2.0.7. root@xenial:~# lxc-create -n mysshd -t /usr/share/lxc/templates/lxc-sshd Generating public/private rsa key pair. Your identification has been saved in /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_rsa_key. Your public key has been saved in /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_rsa_key.pub. The key fingerprint is: SHA256:eR4Kv8JpWxe+RvIudD8LTuOYSGmLdnmX1CgB3Y/IHP4 root@xenial The key's randomart image is: +---[RSA 2048]+ | . . | | . o . | | = o o | |*.. .| | . So+o | | ++=Eo.| | .+++BBo | |.+B+oO=+o| | ..o+++== .o | +[SHA256]-+ Generating public/private dsa key pair. Your identification has been saved in /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_dsa_key. Your public key has been saved in /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_dsa_key.pub. The key fingerprint is: SHA256:Jmet2LLZMtolKBhfDQ/Za4i3yr0/993umj4Hq0D8Qyg root@xenial The key's randomart image is: +---[DSA 1024]+ | | | o | |+ . | | . * o o | |. . + E S o | | + o + X + .| |. o o + = o o | | . + .+B.. ooo. | | o ++==..oo=*+ | +[SHA256]-+ root@xenial:~# lxc-start -n mysshd --logfile mysshd.log lxc-start: tools/lxc_start.c: main: 366 The container failed to start. lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode. lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options. root@xenial:~# cat mysshd.log lxc-start 20170622214710.829 ERRORlxc_conf - conf.c:lxc_setup_dev_console:1473 - Read-only file system - error unlinking /usr/lib/x86_64-linux-gnu/lxc/dev/console lxc-start 20170622214710.829 ERRORlxc_conf - conf.c:lxc_setup:4055 - failed to setup the console for 'mysshd' lxc-start 20170622214710.829 ERRORlxc_start - start.c:do_start:811 - Failed to setup container "mysshd". lxc-start 20170622214710.829 ERRORlxc_sync - sync.c:__sync_wait:57 - An error occurred in another process (expected sequence number 3) lxc-start 20170622214710.868 ERRORlxc_start - start.c:__lxc_start:1358 - Failed to spawn container "mysshd". lxc-start 20170622214715.901 ERRORlxc_start_ui - tools/lxc_start.c:main:366 - The container failed to start. lxc-start 20170622214715.901 ERRORlxc_start_ui - tools/lxc_start.c:main:368 - To get more details, run the container in foreground mode. lxc-start 20170622214715.901 ERRORlxc_start_ui - tools/lxc_start.c:main:370 - Additional information can be obtained by setting the --logfile and --logpriority options. root@xenial:~# dpkg -l '*lxc*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== un liblxc0 (no description available) ii liblxc12.0.8-0ubuntu1~16.04.2 amd64
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
Hello Timo, or anyone else affected, Accepted vulkan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/vulkan/1.0.42.0+dfsg1-1ubuntu1~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: vulkan (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: libdrm (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: New Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in libinput source package in Xenial: New Status in libwacom source package in Xenial: Fix Committed Status in libxfont source package in Xenial: Fix Committed Status in libxfont2 source package in Xenial: Fix Committed Status in llvm-toolchain-4.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in vulkan source package in Xenial: Fix Committed Status in wayland source package in Xenial: Fix Committed Status in x11proto-core source package in Xenial: Fix Committed Status in xfonts-utils source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://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 1687981] Please test proposed package
Hello Timo, or anyone else affected, Accepted libdrm into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.76-1~ubuntu16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: New Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in libinput source package in Xenial: New Status in libwacom source package in Xenial: Fix Committed Status in libxfont source package in Xenial: Fix Committed Status in libxfont2 source package in Xenial: Fix Committed Status in llvm-toolchain-4.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in vulkan source package in Xenial: Fix Committed Status in wayland source package in Xenial: Fix Committed Status in x11proto-core source package in Xenial: Fix Committed Status in xfonts-utils source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://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 1687981] Please test proposed package
Hello Timo, or anyone else affected, Accepted xfonts-utils into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xfonts- utils/1:7.7+3ubuntu0.16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libclc (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: New Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in libinput source package in Xenial: New Status in libwacom source package in Xenial: Fix Committed Status in libxfont source package in Xenial: Fix Committed Status in libxfont2 source package in Xenial: Fix Committed Status in llvm-toolchain-4.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in vulkan source package in Xenial: Fix Committed Status in wayland source package in Xenial: Fix Committed Status in x11proto-core source package in Xenial: Fix Committed Status in xfonts-utils source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://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 1687981] Please test proposed package
Hello Timo, or anyone else affected, Accepted libclc into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libclc/0.2.0+git20170213-1~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: New Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in libinput source package in Xenial: New Status in libwacom source package in Xenial: Fix Committed Status in libxfont source package in Xenial: Fix Committed Status in libxfont2 source package in Xenial: Fix Committed Status in llvm-toolchain-4.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in vulkan source package in Xenial: Fix Committed Status in wayland source package in Xenial: Fix Committed Status in x11proto-core source package in Xenial: Fix Committed Status in xfonts-utils source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://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 1687981] Re: Backport packages for 16.04.3 HWE stack
Hello Timo, or anyone else affected, Accepted libwacom into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libwacom/0.22-1~ubuntu16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libwacom (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: xfonts-utils (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: New Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in libinput source package in Xenial: New Status in libwacom source package in Xenial: Fix Committed Status in libxfont source package in Xenial: Fix Committed Status in libxfont2 source package in Xenial: Fix Committed Status in llvm-toolchain-4.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in vulkan source package in Xenial: Fix Committed Status in wayland source package in Xenial: Fix Committed Status in x11proto-core source package in Xenial: Fix Committed Status in xfonts-utils source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://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 1270348] Re: failure when starting with expect stop doesn't respawn, but logs it will
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 upstart in Ubuntu. https://bugs.launchpad.net/bugs/1270348 Title: failure when starting with expect stop doesn't respawn, but logs it will Status in upstart : New Status in upstart package in Ubuntu: Confirmed Bug description: Consider this job (also attached): script sleep 10 exit 1 end script expect stop respawn If started this will pause for 10 seconds, then print "started/running" state: $ sudo initctl start bug bug start/running However, it is recorded as failed in syslog: Jan 17 19:20:26 localhost kernel: [276823.832916] init: bug main process (11410) terminated with status 1 Jan 17 19:20:26 localhost kernel: [276823.832930] init: bug main process ended, respawning But it isn't running, didn't actually respawn, and never does. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1270348/+subscriptions -- Mailing list: https://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 1699914] [NEW] oooooooooooooooooooooo
Public bug reported: 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 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jun 23 04:06:36 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-31-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-72-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-75-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-78-generic, x86_64: installed GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] InstallationDate: Installed on 2017-04-19 (64 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20023 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=02e0e1d1-578e-4a7a-9f63-f0cc470a2454 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 18CN45WW(V2.54) dmi.board.name: NITU1 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr18CN45WW(V2.54):bd05/05/2010:svnLENOVO:pn20023:pvrLenovoG550:rvnLENOVO:rnNITU1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 20023 dmi.product.version: Lenovo G550 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 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.3-1ubuntu2.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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Jun 22 22:34:54 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 560 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages 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/1699914 Title: oo Status in xorg package in Ubuntu: New Bug description: 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 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jun 23 04:06:36 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-31-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-72-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-75-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-78-generic, x86_64: installed GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] InstallationDate: Installed on 2017-04-19 (64 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20023 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4
Re: [Touch-packages] [Bug 1699903] Re: lxc-sshd won't start with 2.0.8
On Thu, Jun 22, 2017 at 11:11:59PM -, Miroslav Los wrote: > Our actual templates are based on the lxc-sshd template example that > comes with lxc-templates. There, basically all the lxc is is bind-mounts > for necessary paths from the host, obviously read-only: The /dev bind-mount is definitely not needed anymore since LXC will populate dev internally on its own. So you can remove this from your template and - if you want - you can send a PR against LXC master to remove this bind-mount from the template. We can however, make the code a little smarter in handling the /dev/console case by making it ignore unlink() failures. > > # grep mount.entry /usr/share/lxc/templates/lxc-sshd > lxc.mount.entry = /dev dev none ro,bind 0 0 > lxc.mount.entry = /lib lib none ro,bind 0 0 > lxc.mount.entry = /bin bin none ro,bind 0 0 > lxc.mount.entry = /usr usr none ro,bind 0 0 > lxc.mount.entry = /sbin sbin none ro,bind 0 0 > lxc.mount.entry = tmpfs run/sshd tmpfs mode=0644 0 0 > lxc.mount.entry = /usr/share/lxc/templates/lxc-sshd $init_path none ro,bind 0 > 0 > lxc.mount.entry = /etc/init.d etc/init.d none ro,bind 0 0 > lxc.mount.entry = /etc/sysconfig/network-scripts > etc/sysconfig/network-scripts none ro,bind 0 0 > lxc.mount.entry = /etc/rc.d etc/rc.d none ro,bind 0 0 > lxc.mount.entry = /lib64 lib64 none ro,bind 0 0 > > > Perhaps bind-mounting /dev isn't needed anymore, though then I'd like to know > why the example does that, and what the implications are of leaving the /dev > entry out. > > -- > You received this bug notification because you are a member of Ubuntu > containers team, which is subscribed to lxc in Ubuntu. > Matching subscriptions: lxc > https://bugs.launchpad.net/bugs/1699903 > > Title: > lxc-sshd won't start with 2.0.8 > > Status in lxc package in Ubuntu: > New > > Bug description: > On a xenial system after an update to lxc, starting a container > created with the lxc-sshd template fails consistently. This does not > occur with 2.0.7. > > root@xenial:~# lxc-create -n mysshd -t /usr/share/lxc/templates/lxc-sshd > Generating public/private rsa key pair. > Your identification has been saved in > /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_rsa_key. > Your public key has been saved in > /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_rsa_key.pub. > The key fingerprint is: > SHA256:eR4Kv8JpWxe+RvIudD8LTuOYSGmLdnmX1CgB3Y/IHP4 root@xenial > The key's randomart image is: > +---[RSA 2048]+ > | . . | > | . o . | > | = o o | > |*.. .| > | . So+o | > | ++=Eo.| > | .+++BBo | > |.+B+oO=+o| > | ..o+++== .o | > +[SHA256]-+ > Generating public/private dsa key pair. > Your identification has been saved in > /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_dsa_key. > Your public key has been saved in > /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_dsa_key.pub. > The key fingerprint is: > SHA256:Jmet2LLZMtolKBhfDQ/Za4i3yr0/993umj4Hq0D8Qyg root@xenial > The key's randomart image is: > +---[DSA 1024]+ > | | > | o | > |+ . | > | . * o o | > |. . + E S o | > | + o + X + .| > |. o o + = o o | > | . + .+B.. ooo. | > | o ++==..oo=*+ | > +[SHA256]-+ > > > root@xenial:~# lxc-start -n mysshd --logfile mysshd.log > lxc-start: tools/lxc_start.c: main: 366 The container failed to start. > lxc-start: tools/lxc_start.c: main: 368 To get more details, run the > container in foreground mode. > lxc-start: tools/lxc_start.c: main: 370 Additional information can be > obtained by setting the --logfile and --logpriority options. > > > root@xenial:~# cat mysshd.log > lxc-start 20170622214710.829 ERRORlxc_conf - > conf.c:lxc_setup_dev_console:1473 - Read-only file system - error unlinking > /usr/lib/x86_64-linux-gnu/lxc/dev/console > lxc-start 20170622214710.829 ERRORlxc_conf - > conf.c:lxc_setup:4055 - failed to setup the console for 'mysshd' > lxc-start 20170622214710.829 ERRORlxc_start - > start.c:do_start:811 - Failed to setup container "mysshd". > lxc-start 20170622214710.829 ERRORlxc_sync - > sync.c:__sync_wait:57 - An error occurred in another process (expected > sequence number 3) > lxc-start 20170622214710.868 ERRORlxc_start - > start.c:__lxc_start:1358 - Failed to spawn container "mysshd". > lxc-start 20170622214715.901 ERRORlxc_start_ui - > tools/lxc_start.c:main:366 - The container failed to start. > lxc-start 20170622214715.901 ERRORlxc_start_ui - > tools/lxc_start.c:main:368 - To get more details, run the container in > foreground mode. > lxc-start 20170622214715.901 ERRORlxc_start_ui - > tools/lxc_start.c:main:370 - Additional information can be obtained by > setting the --logfile and --logpriority options. > > > root@xenial:~# dpkg -l
[Touch-packages] [Bug 1699919] [NEW] lxc copy between hosts preserves original uid/gid
Public bug reported: I tried to copy an lxc container between two hosts. All worked as expected, but when I looked at the underlying filesystem I realised that the container that has been copied onto the new machine retained its original uid/gid (running unprivileged): root@ii:/var/lib/lxd/containers# ls -al total 24 drwx--x--x 1 root root 58 Jun 23 12:01 . drwxr-xr-x 1 root root182 Jun 23 12:04 .. drwxr-xr-x+ 1 10 10 56 Jun 23 10:38 backend -rw-r--r-- 1 root root 4446 Jun 23 12:04 lxc-monitord.log drwxr-xr-x+ 1 10 10 56 Jun 23 12:01 putils (putils has been copied from a different host). I'd expect a new uid/gid to be allocated for the copied host. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1699919 Title: lxc copy between hosts preserves original uid/gid Status in lxc package in Ubuntu: New Bug description: I tried to copy an lxc container between two hosts. All worked as expected, but when I looked at the underlying filesystem I realised that the container that has been copied onto the new machine retained its original uid/gid (running unprivileged): root@ii:/var/lib/lxd/containers# ls -al total 24 drwx--x--x 1 root root 58 Jun 23 12:01 . drwxr-xr-x 1 root root182 Jun 23 12:04 .. drwxr-xr-x+ 1 10 10 56 Jun 23 10:38 backend -rw-r--r-- 1 root root 4446 Jun 23 12:04 lxc-monitord.log drwxr-xr-x+ 1 10 10 56 Jun 23 12:01 putils (putils has been copied from a different host). I'd expect a new uid/gid to be allocated for the copied host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1699919/+subscriptions -- Mailing list: https://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 1699928] [NEW] Please delete obsolete android binaries
Public bug reported: Since Canonical's Ubuntu phone project is ending and no one has stepped up to maintain Ubuntu's android-tools fork, we are syncing the Android stack from Debian. This benefits users by allowing them to use the latest adb and fastboot instead of an old copy. There are a few obsolete binaries that need to be removed to make this happen, because Debian's android-tools is only built for a limited set of supported architectures (not ppc64el or s390x). Please delete these binaries: android-tools-fsutils for ppc64el and s390x ubuntu-device-do for ppc64el ubuntu-device-flash for ppc64el These are listed on update_excuses.html or update_output.txt ** Affects: android-tools (Ubuntu) Importance: Undecided Status: New ** Affects: goget-ubuntu-touch (Ubuntu) Importance: Undecided Status: New ** Also affects: goget-ubuntu-touch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1699928 Title: Please delete obsolete android binaries Status in android-tools package in Ubuntu: New Status in goget-ubuntu-touch package in Ubuntu: New Bug description: Since Canonical's Ubuntu phone project is ending and no one has stepped up to maintain Ubuntu's android-tools fork, we are syncing the Android stack from Debian. This benefits users by allowing them to use the latest adb and fastboot instead of an old copy. There are a few obsolete binaries that need to be removed to make this happen, because Debian's android-tools is only built for a limited set of supported architectures (not ppc64el or s390x). Please delete these binaries: android-tools-fsutils for ppc64el and s390x ubuntu-device-do for ppc64el ubuntu-device-flash for ppc64el These are listed on update_excuses.html or update_output.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1699928/+subscriptions -- Mailing list: https://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 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)
** Changed in: glib Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1691908 Title: fstab binds appear as mounts (x-gvfs-hide is being ignored) Status in GLib: Incomplete Status in glib2.0 package in Ubuntu: Triaged Bug description: glib2 version 2.52.2+1+gb8bd46bc8-1 (possibly the version before it as well, I haven't tested) causes fstab binds to appear as mounts in Nautilus (and in Deepin Dock - Deepin is based on Gnome). Downgrading to glib2 and glib2-docs 2.52.0-1 resolves this behaviour. I first noted this bug behaviour here: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/452049 Details of my particular system and issue with what I tried to resolve it can be found here: https://bbs.archlinux.org/viewtopic.php?pid=1712030#p1712030 1. Not using Ubuntu. Deepin Desktop 15.4 (Gnome based) on Arch Linux. OS: Arch Linux Kernel: x86_64 Linux 4.10.13-1-ARCH Shell: bash 4.4.12 Resolution: 1920x1200 DE: Deepin 15.4 WM: Deepin WM WM Theme: Arc-Darker GTK Theme: Arc-Darker [GTK2/3] Icon Theme: deepin Font: Noto Sans 11 CPU: Intel Core i5-6500 @ 4x 3.6GHz [27.8°C] GPU: GeForce GTX 950 RAM: 2598MiB / 15990MiB 2. 2.52.2+1+gb8bd46bc8-1 (downgrading to 2.52.0-1 removed the problem). 3. Nautilus to list internal physical drives (my SSD and 1TB HDD) only. 4. Nautilus listed my system disk (as expected) but also listed all of my fstab binds as removable drives (Downloads, Music, Pictures, Videos and Documents although this was not listed as "Documents" but instead listed as the HDD label "Farsight"). Adding x-gvfs-hide did not hide those drives. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1691908/+subscriptions -- Mailing list: https://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 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings
Zesty already contains the latest release (and all fixes): https://launchpad.net/ubuntu/+source/pulseaudio So if you have a problem with zesty, please log a new bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1283003 Title: Bluetooth headset/speakers listed but not selectable in Sound settings Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Invalid Status in gnome-bluetooth package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in blueman source package in Xenial: New Status in gnome-bluetooth source package in Xenial: New Status in pulseaudio source package in Xenial: Fix Committed Bug description: [Impact] Bluetooth headset/speakers are listed but not selectable in Sound settings (the correct device's options don't appear in the right pane). Hence no Bluetooth audio is unusable. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and try to select the device. Expected: The Bluetooth audio device is selectable (its options appear in the right pane when clicked and the selection stays on that device). [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://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 1663157] Re: Guest session processes are not confined in 16.10 and newer releases
** No longer affects: apparmor (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1663157 Title: Guest session processes are not confined in 16.10 and newer releases Status in Light Display Manager: New Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Yakkety: Fix Released Status in lightdm source package in Zesty: Fix Released Status in lightdm source package in Artful: Fix Released Bug description: Processes launched under a lightdm guest session are not confined by the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu 16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The processes are unconfined. The simple test case is to log into a guest session, launch a terminal with ctrl-alt-t, and run the following command: $ cat /proc/self/attr/current Expected output, as seen in Ubuntu 16.04 LTS, is: /usr/lib/lightdm/lightdm-guest-session (enforce) Running the command inside of an Ubuntu 16.10 and newer guest session results in: unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1663157/+subscriptions -- Mailing list: https://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 1699942] [NEW] network-manager fails to deprecate addresses
Public bug reported: network manager does not properly deprecate autoconfigured temporary IP addresses when ValidLifetime for a prefix is 0 in router advertisements. This behaviour is non-compliant with RFC 4861 § 6.3.4, which reads: If the prefix is already present in the host's Prefix List as the result of a previously received advertisement, reset its invalidation timer to the Valid Lifetime value in the Prefix Information option. If the new Lifetime value is zero, time-out the prefix immediately. The hosts instead continued to use temporary addresses configured until they reached their timeout, rather than immediately dropping the addresses. It further appears that it is generating new temporary addresses when the previous ones expire, but I have not been monitoring hosts closely enough to tell for sure---I will update on this when I have further information. This problem was discovered on Ubuntu Studio 16.04.2; it is not present on Ubuntu Server (which uses Debian networking scripts). Additional Info: $ lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 $ apt-cache policy network-manager network-manager: Installed: 1.2.6-0ubuntu0.16.04.1 Candidate: 1.2.6-0ubuntu0.16.04.1 Version table: *** 1.2.6-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu0.16.04.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1699942 Title: network-manager fails to deprecate addresses Status in network-manager package in Ubuntu: New Bug description: network manager does not properly deprecate autoconfigured temporary IP addresses when ValidLifetime for a prefix is 0 in router advertisements. This behaviour is non-compliant with RFC 4861 § 6.3.4, which reads: If the prefix is already present in the host's Prefix List as the result of a previously received advertisement, reset its invalidation timer to the Valid Lifetime value in the Prefix Information option. If the new Lifetime value is zero, time-out the prefix immediately. The hosts instead continued to use temporary addresses configured until they reached their timeout, rather than immediately dropping the addresses. It further appears that it is generating new temporary addresses when the previous ones expire, but I have not been monitoring hosts closely enough to tell for sure---I will update on this when I have further information. This problem was discovered on Ubuntu Studio 16.04.2; it is not present on Ubuntu Server (which uses Debian networking scripts). Additional Info: $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ apt-cache policy network-manager network-manager: Installed: 1.2.6-0ubuntu0.16.04.1 Candidate: 1.2.6-0ubuntu0.16.04.1 Version table: *** 1.2.6-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu0.16.04.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1699942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
FYI, just found out the hard way that "Device" needs to be lower case!... $ sudo nano /etc/NetworkManager/NetworkManager.conf # Append... - - - - - - - - - - - - - - - - - - - - [device] wifi.scan-rand-mac-address=no - - - - - - - - - - - - - - - - - - - - $ sudo service network-manager restart -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1681513 Title: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue) Status in network-manager package in Ubuntu: Confirmed Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672499] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf
This bug was fixed in the package systemd - 232-21ubuntu4 --- systemd (232-21ubuntu4) zesty; urgency=medium * Cherrypick upstream commit to enable system use kernel maximum limit for RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361) * debian/tests/root-unittests: disable execute and seccomp tests on arm test-seccomp and test-execute fail on arm64 kernels. Marking both tests as expected failures. An upstream bug report is filed to resolve these. (LP: #1672499) * Cherrypick upstream patch for platform predictable interface names. (LP: #1686784) * resolved: fix null pointer dereference crash (LP: #1621396) * Cherrypick core/timer downgrade message about random time addition (LP: #1692136) -- Dimitri John Ledkov Wed, 24 May 2017 16:26:16 +0100 ** Changed in: systemd (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1672499 Title: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Zesty: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] * ADT test superfluously fails, resulting in SRU / proposed-migration delays [Test Case] * Check that systemd ADT tests pass [Regression Potential] * No change to the binary packages, this is a change in ADT test- suite only. [Original Bug Report] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/armhf/s/systemd/20170310_221057_b5cf9@/log.gz root-unittests fails: -> Unit a.service: Description: a.service Instance: n/a Unit Load State: not-found Unit Active State: inactive State Change Timestamp: n/a Inactive Exit Timestamp: n/a Active Enter Timestamp: n/a Activeerror: org.freedesktop.systemd1.NoSuchUnit: Unit c.service not found. Assertion 'r == 0' failed at ../src/test/test-engine.c:62, function main(). Aborting. Exit Timestamp: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672499/+subscriptions -- Mailing list: https://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 1686361] Re: systemd does not respect nofile ulimit when running in container
This bug was fixed in the package systemd - 232-21ubuntu4 --- systemd (232-21ubuntu4) zesty; urgency=medium * Cherrypick upstream commit to enable system use kernel maximum limit for RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361) * debian/tests/root-unittests: disable execute and seccomp tests on arm test-seccomp and test-execute fail on arm64 kernels. Marking both tests as expected failures. An upstream bug report is filed to resolve these. (LP: #1672499) * Cherrypick upstream patch for platform predictable interface names. (LP: #1686784) * resolved: fix null pointer dereference crash (LP: #1621396) * Cherrypick core/timer downgrade message about random time addition (LP: #1692136) -- Dimitri John Ledkov Wed, 24 May 2017 16:26:16 +0100 ** Changed in: systemd (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1686361 Title: systemd does not respect nofile ulimit when running in container Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] * Containers cannot use maximum RLIMIT_NOFILE, because systemd sets an arbitrary cap. [Test Case] * Start container with high RLIMIT_NOFILE (e.g. 100 000) * Check that RLIMIT_NOFILE on the container is more than 65536 [Regression Potential] * This is a feature / change of behaviour. Some users may be relying on the lower RLIMIT_NOFILE cap, but it should not have a negative impact on the host (as in creating too many file descriptors/denial of service). [Original Bug Report] When systemd currently starts in a container that has RLIMIT_NOFILE set to e.g. 10 systemd will lower it to 65536 since this value is hard-coded into systemd. I've pushed a patch to systemd upstream that will try to set the nofile limit to the allowed kernel maximum. If this fails, it will compute the minimum of the current set value (the limit that is set on the container) and the maximum value as soft limit and the currently set maximum value as the maximum value. This way it retains the limit set on the container. It would be great if we could backport this patch to have system adhere to nofile limits set for the container. This is especially important since user namespaces will allow you to lower the limit but not raise it back up afterwards. The upstream patch is appended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1686361/+subscriptions -- Mailing list: https://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 1692136] Re: Backport "core/timer: downgrade message about random time addition (#5229)".
This bug was fixed in the package systemd - 232-21ubuntu4 --- systemd (232-21ubuntu4) zesty; urgency=medium * Cherrypick upstream commit to enable system use kernel maximum limit for RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361) * debian/tests/root-unittests: disable execute and seccomp tests on arm test-seccomp and test-execute fail on arm64 kernels. Marking both tests as expected failures. An upstream bug report is filed to resolve these. (LP: #1672499) * Cherrypick upstream patch for platform predictable interface names. (LP: #1686784) * resolved: fix null pointer dereference crash (LP: #1621396) * Cherrypick core/timer downgrade message about random time addition (LP: #1692136) -- Dimitri John Ledkov Wed, 24 May 2017 16:26:16 +0100 ** Changed in: systemd (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1692136 Title: Backport "core/timer: downgrade message about random time addition (#5229)". Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Triaged Status in systemd source package in Yakkety: Triaged Status in systemd source package in Zesty: Fix Released Bug description: [Impact] * Systemd spams logs too much with pointless messages [Test Case] * Boot system and observe no pointless messages of scheduling random timers for things at a given offset [Regression Potential] * Low, this patch simply changes the priority of the message from info to debug. [Original bug report] Please backport upstream systemd v233 commit 382852fd581efe3cc0ae11154102ab9f435adea1 "core/timer: downgrade message about random time addition (#5229)". https://github.com/systemd/systemd/commit/382852fd581efe3cc0ae11154102ab9f435adea1 This removes "random time" messages flooding dmesg. The spew was introduced with v229 commit "core: add new RandomSec= setting for time units". https://github.com/systemd/systemd/commit/744c7693751830149ae78fdaf95c6c6f99d59f07 trusty based off v204 is not affected. xenial based off v229, yakkety based off v231, and zesty based off v232 need this fix. artful based off v233 has the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1692136/+subscriptions -- Mailing list: https://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 1686784] Re: no predictable names for platform (non-PCI) NICs
This bug was fixed in the package systemd - 232-21ubuntu4 --- systemd (232-21ubuntu4) zesty; urgency=medium * Cherrypick upstream commit to enable system use kernel maximum limit for RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361) * debian/tests/root-unittests: disable execute and seccomp tests on arm test-seccomp and test-execute fail on arm64 kernels. Marking both tests as expected failures. An upstream bug report is filed to resolve these. (LP: #1672499) * Cherrypick upstream patch for platform predictable interface names. (LP: #1686784) * resolved: fix null pointer dereference crash (LP: #1621396) * Cherrypick core/timer downgrade message about random time addition (LP: #1692136) -- Dimitri John Ledkov Wed, 24 May 2017 16:26:16 +0100 ** Changed in: systemd (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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: Fix Released 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] Unless one fixed the names locally with .netlink / .rules files the interface names will change for the ACPI/platform bus network interfaces, from random ethX names to stable names named like enaVENDORMODELiX. Thus we should check that this update doesn't negatively break certified ARM64 platforms with: ARM, NVIDIA, HISILICON platform bus ethernet devices. 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 1686361] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1686361 Title: systemd does not respect nofile ulimit when running in container Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] * Containers cannot use maximum RLIMIT_NOFILE, because systemd sets an arbitrary cap. [Test Case] * Start container with high RLIMIT_NOFILE (e.g. 100 000) * Check that RLIMIT_NOFILE on the container is more than 65536 [Regression Potential] * This is a feature / change of behaviour. Some users may be relying on the lower RLIMIT_NOFILE cap, but it should not have a negative impact on the host (as in creating too many file descriptors/denial of service). [Original Bug Report] When systemd currently starts in a container that has RLIMIT_NOFILE set to e.g. 10 systemd will lower it to 65536 since this value is hard-coded into systemd. I've pushed a patch to systemd upstream that will try to set the nofile limit to the allowed kernel maximum. If this fails, it will compute the minimum of the current set value (the limit that is set on the container) and the maximum value as soft limit and the currently set maximum value as the maximum value. This way it retains the limit set on the container. It would be great if we could backport this patch to have system adhere to nofile limits set for the container. This is especially important since user namespaces will allow you to lower the limit but not raise it back up afterwards. The upstream patch is appended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1686361/+subscriptions -- Mailing list: https://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 1672499] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1672499 Title: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Zesty: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] * ADT test superfluously fails, resulting in SRU / proposed-migration delays [Test Case] * Check that systemd ADT tests pass [Regression Potential] * No change to the binary packages, this is a change in ADT test- suite only. [Original Bug Report] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/armhf/s/systemd/20170310_221057_b5cf9@/log.gz root-unittests fails: -> Unit a.service: Description: a.service Instance: n/a Unit Load State: not-found Unit Active State: inactive State Change Timestamp: n/a Inactive Exit Timestamp: n/a Active Enter Timestamp: n/a Activeerror: org.freedesktop.systemd1.NoSuchUnit: Unit c.service not found. Assertion 'r == 0' failed at ../src/test/test-engine.c:62, function main(). Aborting. Exit Timestamp: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672499/+subscriptions -- Mailing list: https://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 1692136] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1692136 Title: Backport "core/timer: downgrade message about random time addition (#5229)". Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Triaged Status in systemd source package in Yakkety: Triaged Status in systemd source package in Zesty: Fix Released Bug description: [Impact] * Systemd spams logs too much with pointless messages [Test Case] * Boot system and observe no pointless messages of scheduling random timers for things at a given offset [Regression Potential] * Low, this patch simply changes the priority of the message from info to debug. [Original bug report] Please backport upstream systemd v233 commit 382852fd581efe3cc0ae11154102ab9f435adea1 "core/timer: downgrade message about random time addition (#5229)". https://github.com/systemd/systemd/commit/382852fd581efe3cc0ae11154102ab9f435adea1 This removes "random time" messages flooding dmesg. The spew was introduced with v229 commit "core: add new RandomSec= setting for time units". https://github.com/systemd/systemd/commit/744c7693751830149ae78fdaf95c6c6f99d59f07 trusty based off v204 is not affected. xenial based off v229, yakkety based off v231, and zesty based off v232 need this fix. artful based off v233 has the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1692136/+subscriptions -- Mailing list: https://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 1686784] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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: Fix Released 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] Unless one fixed the names locally with .netlink / .rules files the interface names will change for the ACPI/platform bus network interfaces, from random ethX names to stable names named like enaVENDORMODELiX. Thus we should check that this update doesn't negatively break certified ARM64 platforms with: ARM, NVIDIA, HISILICON platform bus ethernet devices. 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 1621396] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Yakkety: Confirmed Status in systemd source package in Zesty: Fix Released Bug description: [Impact] * Null-pointer dereference in resolved, results in resolved crash and reports on launchpad and errors. [Test Case] * Unknown steps to reproduce * Monitor the drop off in crashes on errors.ubuntu.com: https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 [Regression Potential] * The behavior is similar, instead of crashing resolved it returns an error in the relevant function. Whilst this may not result in correct dns resolution for the affected dns packets, it should not result in resolved crashes. [Original Bug Report] This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 233-6ubuntu2, the problem page at https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()
This bug was fixed in the package systemd - 232-21ubuntu4 --- systemd (232-21ubuntu4) zesty; urgency=medium * Cherrypick upstream commit to enable system use kernel maximum limit for RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361) * debian/tests/root-unittests: disable execute and seccomp tests on arm test-seccomp and test-execute fail on arm64 kernels. Marking both tests as expected failures. An upstream bug report is filed to resolve these. (LP: #1672499) * Cherrypick upstream patch for platform predictable interface names. (LP: #1686784) * resolved: fix null pointer dereference crash (LP: #1621396) * Cherrypick core/timer downgrade message about random time addition (LP: #1692136) -- Dimitri John Ledkov Wed, 24 May 2017 16:26:16 +0100 ** Changed in: systemd (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Yakkety: Confirmed Status in systemd source package in Zesty: Fix Released Bug description: [Impact] * Null-pointer dereference in resolved, results in resolved crash and reports on launchpad and errors. [Test Case] * Unknown steps to reproduce * Monitor the drop off in crashes on errors.ubuntu.com: https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 [Regression Potential] * The behavior is similar, instead of crashing resolved it returns an error in the relevant function. Whilst this may not result in correct dns resolution for the affected dns packets, it should not result in resolved crashes. [Original Bug Report] This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 233-6ubuntu2, the problem page at https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699952] [NEW] [Aspire 5750Z, Realtek ALC269VB, Speaker, Internal] Background noise or low volume
Public bug reported: High crackling/popping sound with low volume from laptop speakers when playing any audio video file. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ankit 1866 F pulseaudio CurrentDesktop: Unity Date: Fri Jun 23 08:55:10 2017 InstallationDate: Installed on 2016-07-14 (343 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 successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [Aspire 5750Z, Realtek ALC269VB, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE50_HR dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.modalias: dmi:bvnAcer:bvrV1.12:bd07/11/2011:svnAcer:pnAspire5750Z:pvrV1.12:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.12: dmi.product.name: Aspire 5750Z dmi.product.version: V1.12 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- 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/1699952 Title: [Aspire 5750Z, Realtek ALC269VB, Speaker, Internal] Background noise or low volume Status in alsa-driver package in Ubuntu: New Bug description: High crackling/popping sound with low volume from laptop speakers when playing any audio video file. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ankit 1866 F pulseaudio CurrentDesktop: Unity Date: Fri Jun 23 08:55:10 2017 InstallationDate: Installed on 2016-07-14 (343 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 successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [Aspire 5750Z, Realtek ALC269VB, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE50_HR dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.modalias: dmi:bvnAcer:bvrV1.12:bd07/11/2011:svnAcer:pnAspire5750Z:pvrV1.12:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.12: dmi.product.name: Aspire 5750Z dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1699952/+subscriptions -- Mailing list: https://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 1699928] Re: Please delete obsolete android binaries
Removing packages from artful: android-tools-fsutils 5.1.1r36+git20160322-0ubuntu5 in artful ppc64el android-tools-fsutils 5.1.1r36+git20160322-0ubuntu5 in artful s390x Comment: ANAIS 2 packages successfully removed. ** Changed in: android-tools (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1699928 Title: Please delete obsolete android binaries Status in android-tools package in Ubuntu: Fix Released Status in goget-ubuntu-touch package in Ubuntu: New Bug description: Since Canonical's Ubuntu phone project is ending and no one has stepped up to maintain Ubuntu's android-tools fork, we are syncing the Android stack from Debian. This benefits users by allowing them to use the latest adb and fastboot instead of an old copy. There are a few obsolete binaries that need to be removed to make this happen, because Debian's android-tools is only built for a limited set of supported architectures (not ppc64el or s390x). Please delete these binaries: android-tools-fsutils for ppc64el and s390x ubuntu-device-do for ppc64el ubuntu-device-flash for ppc64el These are listed on update_excuses.html or update_output.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1699928/+subscriptions -- Mailing list: https://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 1514508] Re: cant install libopencv-objdetect-dev
[Expired for opencv (Ubuntu) because there has been no activity for 60 days.] ** Changed in: opencv (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1514508 Title: cant install libopencv-objdetect-dev Status in opencv package in Ubuntu: Expired Bug description: im trying to install libopencv-objdetect-dev but, i got the next message Los siguientes paquetes tienen dependencias incumplidas: libopencv-objdetect-dev : Depende: libopencv-highgui-dev (= 2.4.9+dfsg-1ubuntu6) pero no va a instalarse E: No se pudieron corregir los problemas, usted ha retenido paquetes rotos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1514508/+subscriptions -- Mailing list: https://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 1699928] Re: Please delete obsolete android binaries
** Description changed: - Since Canonical's Ubuntu phone project is ending and no one has stepped - up to maintain Ubuntu's android-tools fork, we are syncing the Android - stack from Debian. + New Request + === + Please remove phablet-tools and goget-ubuntu-touch and all their binaries from artful. goget-ubuntu-touch does not build in zesty or artful and I don't think anyone is interested in maintaining it in Ubuntu at this time. It can be re-added later if someone volunteers. + + phablet-tools also fails to build (pep8) but I don't think it's very + useful without ubuntu-device-do and ubuntu-device-flash. + + Background + == + Since Canonical's Ubuntu phone project is ending and no one has stepped up to maintain Ubuntu's android-tools fork, we are syncing the Android stack from Debian. This benefits users by allowing them to use the latest adb and fastboot instead of an old copy. There are a few obsolete binaries that need to be removed to make this happen, because Debian's android-tools is only built for a limited set of supported architectures (not ppc64el or s390x). + + Original Report + === Please delete these binaries: android-tools-fsutils for ppc64el and s390x ubuntu-device-do for ppc64el ubuntu-device-flash for ppc64el These are listed on update_excuses.html or update_output.txt ** Also affects: phablet-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 android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1699928 Title: Please delete obsolete android binaries Status in android-tools package in Ubuntu: Fix Released Status in goget-ubuntu-touch package in Ubuntu: New Status in phablet-tools package in Ubuntu: New Bug description: New Request === Please remove phablet-tools and goget-ubuntu-touch and all their binaries from artful. goget-ubuntu-touch does not build in zesty or artful and I don't think anyone is interested in maintaining it in Ubuntu at this time. It can be re-added later if someone volunteers. phablet-tools also fails to build (pep8) but I don't think it's very useful without ubuntu-device-do and ubuntu-device-flash. Background == Since Canonical's Ubuntu phone project is ending and no one has stepped up to maintain Ubuntu's android-tools fork, we are syncing the Android stack from Debian. This benefits users by allowing them to use the latest adb and fastboot instead of an old copy. There are a few obsolete binaries that need to be removed to make this happen, because Debian's android-tools is only built for a limited set of supported architectures (not ppc64el or s390x). Original Report === Please delete these binaries: android-tools-fsutils for ppc64el and s390x ubuntu-device-do for ppc64el ubuntu-device-flash for ppc64el These are listed on update_excuses.html or update_output.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1699928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
