[Group.of.nepali.translators] [Bug 1689093] Re: modify ubuntu-gnome hook to set UnreportableReason for 14.04 and 16.04
This bug was fixed in the package apport - 2.20.4-0ubuntu7 --- apport (2.20.4-0ubuntu7) artful; urgency=medium * data/general/ubuntu-gnome.py: The GNOME3 PPAs are no longer supported for 14.04 or 16.04 so set an UnreportableReason in those reports. (LP: #1689093) -- Brian MurrayWed, 10 May 2017 14:53:46 -0700 ** Changed in: apport (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1689093 Title: modify ubuntu-gnome hook to set UnreportableReason for 14.04 and 16.04 Status in apport package in Ubuntu: Fix Released Status in apport source package in Trusty: Triaged Status in apport source package in Xenial: Triaged Bug description: Impact -- As announced, the GNOME3 PPAs for Ubuntu 16.04 LTS are no longer being maintained as of April 2017. Therefore, the Ubuntu GNOME project would like to stop receiving bugs from packages installed from those PPAs for that version, or for 14.04 LTS which is no longer supported by Ubuntu GNOME. See https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3 Test Case - sudo add-apt-repository ppa:gnome3-team/gnome3 sudo apt update sudo apt upgrade Ubuntu 14.04: ubuntu-bug gnome-system-monitor Ubuntu 16.04: ubuntu-bug nautilus What should happen: After several moments, you should see a popup with The GNOME3 PPA you are using is no longer supported for this Ubuntu release. Please run "ppa-purge ppa:gnome3-team/gnome3". Clean up: sudo apt install ppa-purge sudo ppa-purge ppa:gnome3-team/gnome3 Other Info -- Ubuntu GNOME has always installed ppa-purge by default. Regression Potential People will be unable to report bugs with PPA packages like they used to but they'll be told why. The message unfortunately likely won't be translated right away, but since it will land in the development release, it should eventually be translated for future Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689093/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1673557] Re: /proc/cpuinfo should be collected
** Also affects: apport (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: Fix Released Status in whoopsie package in Ubuntu: Fix Released Status in apport source package in Trusty: New Status in whoopsie source package in Trusty: New Status in apport source package in Xenial: New Status in whoopsie source package in Xenial: New Status in apport source package in Yakkety: New Status in whoopsie source package in Yakkety: New Bug description: apport does not currently collect data from /proc/cpuinfo and this would be useful to determine how many users can only run the i386 version of Ubuntu. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1674892] Re: zend_print_flat_zval_r doesn't consider reference
This bug was fixed in the package php7.0 - 7.0.18-0ubuntu0.17.04.1 --- php7.0 (7.0.18-0ubuntu0.17.04.1) zesty; urgency=medium * New upstream release 7.0.18 - LP: #1686237 - LP: #1674892 - Refresh patches for new upstream release * Drop: - debian/patches/0050-Fix-pdo_pgsql.patch: Fixed #73959 - lastInsertId fails to throw an exception in pdsql. Thanks to andrewnester. Closes LP #1658289. [ Fixed upstream in 7.0.16 ] - SECURITY REGRESSION: large mysql requests broken (LP #1668017) + debian/patches/fix_74021.patch: fix fetch_array with more than MEDIUMBLOB in ext/mysqlnd/mysqlnd_wireprotocol.c, added tests to ext/mysqli/tests/bug73800.phpt, ext/mysqli/tests/bug74021.phpt. [ Fixed upstream in 7.0.17 ] -- Nishanth Aravamudan Wed, 26 Apr 2017 16:59:48 -0700 ** Changed in: php7.0 (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1674892 Title: zend_print_flat_zval_r doesn't consider reference Status in php7.0 package in Ubuntu: Fix Released Status in php7.0 source package in Xenial: Confirmed Status in php7.0 source package in Yakkety: Fix Committed Status in php7.0 source package in Zesty: Fix Released Status in php7.0 source package in Artful: Fix Released Bug description: [Impact] * Users hit an error with PHP7.0 when zend_print_flat_zval_r doesn't consider a reference. The following error may be triggered: PHP Notice: Array to string conversion; Catchable fatal error: Object could not be converted to string. [Test Case] * From the upstream bug: $a = array('a'); class b{}; $b = new b; $test[] =& $a; $test[] =& $b; test($test); function test() { debug_print_backtrace(); } Expected result: #0 test(Array ([0] => Array ([0] => a),[1] => b Object ())) called at [/Users/playcrab/Documents/code/php/test/test7.php:7] Actual result: -- #0 test(Array ([0] => PHP Notice: Array to string conversion in /Users/playcrab/Documents/code/php/test/test7.php on line 9 PHP Stack trace: PHP 1. {main}() /Users/playcrab/Documents/code/php/test/test7.php:0 PHP 2. test() /Users/playcrab/Documents/code/php/test/test7.php:7 PHP 3. debug_print_backtrace() /Users/playcrab/Documents/code/php/test/test7.php:9 PHP Catchable fatal error: Object of class b could not be converted to string in /Users/playcrab/Documents/code/php/test/test7.php on line 9 PHP Stack trace: PHP 1. {main}() /Users/playcrab/Documents/code/php/test/test7.php:0 PHP 2. test() /Users/playcrab/Documents/code/php/test/test7.php:7 PHP 3. debug_print_backtrace() /Users/playcrab/Documents/code/php/test/test7.php:9 Notice: Array to string conversion in /Users/playcrab/Documents/code/php/test/test7.php on line 9 Call Stack: 0.0068 353088 1. {main}() /Users/playcrab/Documents/code/php/test/test7.php:0 0.0080 353928 2. test() /Users/playcrab/Documents/code/php/test/test7.php:7 0.0080 353928 3. debug_print_backtrace() /Users/playcrab/Documents/code/php/test/test7.php:9 Array,[1] => Catchable fatal error: Object of class b could not be converted to string in /Users/playcrab/Documents/code/php/test/test7.php on line 9 Call Stack: 0.0068 353088 1. {main}() /Users/playcrab/Documents/code/php/test/test7.php:0 0.0080 353928 2. test() /Users/playcrab/Documents/code/php/test/test7.php:7 0.0080 353928 3. debug_print_backtrace() /Users/playcrab/Documents/code/php/test/test7.php:9 [Regression Potential] * I believe the regression potential is low to zero for this fix (via 7.0.18 upstream). The reason is that the code as-is in 16.04 does not work and leads to backtraces. The fix introduce upstream resolves the issue. --- https://bugs.php.net/bug.php?id=73916 We've hit this bug in 7.0.15, the current/latest version for Xenial. It was fixed in 7.0.16 by php.net, Feb 16 2017. It would be nice if Xenials packages would be updated to reflect this fix. Patch: http://git.php.net/?p=php- src.git;a=blobdiff;f=Zend/zend.c;h=2a47e9244ba787a2ad35e9220171b04d1a5de634;hp=3f3ca75e382b1dec98fd138307d812f36f02251e;hb=04379bcb1df25a9f9cc1d440f5c12105b9fbaf97;hpb=bd75f9e61375c7632bb55b0d49b470ecd94e8ec7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1674892/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help :
[Group.of.nepali.translators] [Bug 1686237] Re: [SRU] microrelease update of src:php7.0 (7.0.18)
This bug was fixed in the package php7.0 - 7.0.18-0ubuntu0.17.04.1 --- php7.0 (7.0.18-0ubuntu0.17.04.1) zesty; urgency=medium * New upstream release 7.0.18 - LP: #1686237 - LP: #1674892 - Refresh patches for new upstream release * Drop: - debian/patches/0050-Fix-pdo_pgsql.patch: Fixed #73959 - lastInsertId fails to throw an exception in pdsql. Thanks to andrewnester. Closes LP #1658289. [ Fixed upstream in 7.0.16 ] - SECURITY REGRESSION: large mysql requests broken (LP #1668017) + debian/patches/fix_74021.patch: fix fetch_array with more than MEDIUMBLOB in ext/mysqlnd/mysqlnd_wireprotocol.c, added tests to ext/mysqli/tests/bug73800.phpt, ext/mysqli/tests/bug74021.phpt. [ Fixed upstream in 7.0.17 ] -- Nishanth Aravamudan Wed, 26 Apr 2017 16:59:48 -0700 ** Changed in: php7.0 (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1686237 Title: [SRU] microrelease update of src:php7.0 (7.0.18) Status in php7.0 package in Ubuntu: Fix Released Status in php7.0 source package in Xenial: In Progress Status in php7.0 source package in Yakkety: Fix Committed Status in php7.0 source package in Zesty: Fix Released Bug description: There have been a number of microreleases of PHP 7.0 upstream since the last update to Xenial (which corresponded to the merge in Zesty). As we have re-merged again in Artful, it feels appropriate to provide another MRE update to php7.0. A number of critical security and bug- fixes are present in each 7.0.x. Rather than backporting individual patches (e.g., Bug # 1569509), I believe it makes significantly more sense to follow the upstream 7.0.x. Upstream PHP is demonstrating an improved approach of bugfixes only in 7.0.x: - 7.0.18: http://php.net/ChangeLog-7.php#7.0.18 The upstream CI is at: https://travis-ci.org/php/php-src and is run regularly. Our php7.0 source package has autopkgtests for the 4 SAPIs, mod-php, cgi, fpm and cli. We have also updated the packing to run the source tests during the build itself. I do not believe there is a firm statement from upstream on API/ABI stability, but the general approach seems to be a BC-break would result in 7.1.0. Additionally for this SRU, there is (at least) one bug fixed upstream which will be fixed by updating to a newer upstream version: LP: #1674892. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1686237/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22
This bug was fixed in the package linux-firmware - 1.164.1 --- linux-firmware (1.164.1) zesty; urgency=medium * intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22 (LP: #1647826) - UBUNTU: SAUCE: Remove iwlwifi-8000C-22.ucode -- Seth ForsheeFri, 21 Apr 2017 11:36:23 -0500 ** Changed in: linux-firmware (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1647826 Title: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Xenial: Fix Committed Status in linux-firmware source package in Yakkety: Fix Released Status in linux-firmware source package in Zesty: Fix Released Status in linux-firmware source package in Artful: Fix Released Bug description: SRU Justification Impact: The -22 firmware for iwlwifi introduces regressions with some hardware versus earlier firmware versions. As no newer firmware is available, the only fix is to revert back to the older firmware which does work. Test Case: Using the -22 firmware with affected hardware produces the behavior described below. The -21 firmware does not. Regression Potential: Switching back to -21 could cause some regressions with other hardware supported by this firmware. However as -22 causes some hardware to completely fail to work any regressions are almost certain to be less severe than the current problems. --- The -22 microcode for the intel 8260 wifi adapter has compatibility issues with Linux Kernel 4.8 under certain hardware configurations. The iwlwifi module crashes resulting in wifi failing with "device not ready" and kernel errors reported in dmesg. [ 10.691115] iwlwifi :6e:00.0: Microcode SW error detected. Restarting 0x200. Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to fallback to the -21 ucode resolves the issue and wifi begins working normally again. This is an issue with Linux kernel 4.8 on both yakkety and xenial, so the bug doesn't currently affect users on xenial, but will begin to after the 16.04.2 HWE release. Kernel 4.4 is unaffected because it doesn't attempt to use the -22 ucode The failure doesn't necessarily affect all machines of a given model with the 8260, but I can reproduce it on multiple laptops when 64GB of RAM are installed (4x16GB). The RAM itself does not appear to be an issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1610878] Re: pmp-check-unix-memory stopped working because of new output from free
This bug was fixed in the package nagios-plugins-contrib - 16.20151226ubuntu0.16.10.1 --- nagios-plugins-contrib (16.20151226ubuntu0.16.10.1) yakkety; urgency=medium * pmp-check-unix-memory: Consider MemAvailable if available in /proc/meminfo. (LP: #1610878) -- Christian BiamontTue, 28 Feb 2017 10:18:11 -0800 ** Changed in: nagios-plugins-contrib (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1610878 Title: pmp-check-unix-memory stopped working because of new output from free Status in nagios-plugins-contrib package in Ubuntu: Fix Released Status in nagios-plugins-contrib source package in Xenial: Fix Released Status in nagios-plugins-contrib source package in Yakkety: Fix Released Status in nagios-plugins-contrib source package in Zesty: Fix Released Bug description: Hello, Current pmp-check-unix-memory in package nagios-plugins-contrib does not work anymore, from Ubuntu Xenial. It can't fetch free memory and therefor presents it incorrectly. E.g: $ ./pmp-check-unix-memory OK Memory % used | memory_used=0;90;95;0;100 As of version 3.3.10 of package procps, the command "free" uses a different output. See: http://upstream.rosalinux.ru/changelogs/procps- ng/3.3.10/changelog.html How free memory is calculated was changed in kernel here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=34e431b0ae398fc54ea69ff85ec700722c9da773 This problem has been fixed in the percona-monitoring-plugins repo on GitHub: https://github.com/percona/percona-monitoring- plugins/commit/b4636c49f0188d2af1235293d01396abeddacf7f I have ported and tested the fix and it is working, both on a computer with older procps and on a computer running Ubuntu Xenial. Will submit a debdiff with proposed patch shortly. Best regards, Christian Biamont To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins-contrib/+bug/1610878/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1683965] Re: [SRU] package virtualbox-ext-pack 5.0.36-0ubuntu1.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit s
This bug was fixed in the package virtualbox-guest-additions-iso - 5.0.40-0ubuntu1.16.04.1 --- virtualbox-guest-additions-iso (5.0.40-0ubuntu1.16.04.1) xenial; urgency=medium * Update to the latest minor release for xenial (LP: #1683965) - bring new fixes from Debian packaging (5.1.22) - Update copyright and watch files - Update get-orig-source.sh script -- Gianfranco CostamagnaThu, 20 Apr 2017 09:08:54 +0200 ** Changed in: virtualbox-guest-additions-iso (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1683965 Title: [SRU] package virtualbox-ext-pack 5.0.36-0ubuntu1.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 143 Status in virtualbox package in Ubuntu: Fix Committed Status in virtualbox-ext-pack package in Ubuntu: Fix Committed Status in virtualbox-guest-additions-iso package in Ubuntu: Fix Committed Status in virtualbox source package in Xenial: Fix Committed Status in virtualbox-ext-pack source package in Xenial: Fix Committed Status in virtualbox-guest-additions-iso source package in Xenial: Fix Released Status in virtualbox source package in Yakkety: In Progress Status in virtualbox-ext-pack source package in Yakkety: In Progress Status in virtualbox-guest-additions-iso source package in Yakkety: In Progress Status in virtualbox source package in Zesty: Fix Committed Status in virtualbox-ext-pack source package in Zesty: Fix Committed Status in virtualbox-guest-additions-iso source package in Zesty: Fix Committed Bug description: This has been introduced in 5.0.38 and 5.1.20 and leads to failures when using virtualbox-ext-pack with the official virtualbox clients. Backporting the fixes to the stable Ubuntu versions fixes this issue. Fix is upgrade xenial to 5.0.40 and yakkety/zesty to 5.1.22 (or 5.1.20, but 5.1.22 fixes two regressions in audio handling and postinst guest addition installation) [Changelog] VirtualBox 5.0.40 (released 2017-04-28) This is a maintenance release. The following items were fixed and/or added: VMM: fixed software virtualization on Solaris hosts (5.0.38 regression) Storage: fixed a potential hang under rare circumstances (bug #16677) Storage: fixed a potential crash under rare circumstances (asynchronous I/O disabled or during maintenance file operations like merging snapshots) Storage: fixed a potential crash under rare circumstances (no asynchronous I/O or during maintenance file operations like merging snapshots) Linux hosts: make the ALSA backend work again as well as Loading the GL libraries on certain hosts (5.0.38 regression; bugs #16667, #16693) VirtualBox 5.0.38 (released 2017-04-18) This is a maintenance release. The following items were fixed and/or added: GUI: don't crash on restoring defaults in the appliance import dialog several fixes [SRU Template] * virtualbox folks changed how ext-pack gets installed. People using the custom .38 virtualbox from the website won't be able to install the ext pack [Regression potential] Changelog: * GUI: don't crash on restoring defaults in the appliance import dialog * several fixes [Test case] * Virtualbox and the ext pack should install without issues (and work) I installed the latest updates (including kernel) in xenial-proposed and got this crash report. The installation was stuck at "VirtualBox Personal Use and Evaluation License (PUEL)" step. The acceptance question (Do you agree to these license terms and conditions (y/n)?) does not show up and the process is stuck.. Release of Ubuntu: Ubuntu 16.04.2 LTS Version of package: virtualbox-ext-pack: 5.0.36-0ubuntu1.16.04.2 What is expected to happen: The question will be asked and waited for an answer from user What happened instead: The question didnt appear and the process was stuck ProblemType: Package DistroRelease: Ubuntu 16.04 Package: virtualbox-ext-pack 5.0.36-0ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Apr 19 01:31:08 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 143 InstallationDate: Installed on 2016-06-15 (307 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: virtualbox-ext-pack Title: package virtualbox-ext-pack 5.0.36-0ubuntu1.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned
[Group.of.nepali.translators] [Bug 1668093] Re: ssh-keygen -H corrupts already hashed entries
This bug was fixed in the package openssh - 1:7.2p2-4ubuntu2.2 --- openssh (1:7.2p2-4ubuntu2.2) xenial; urgency=medium * Fix ssh-keygen -H accidentally corrupting known_hosts that contained already-hashed entries (LP: #1668093). * Fix ssh-keyscan to correctly hash hosts with a port number (LP: #1670745). -- Christian EhrhardtWed, 15 Mar 2017 13:16:56 +0100 ** Changed in: openssh (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1668093 Title: ssh-keygen -H corrupts already hashed entries Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: Fix Released Status in openssh source package in Yakkety: Fix Released Status in openssh package in Debian: Fix Released Bug description: [Impact] * re-execution of ssh-keygen -H can clobber known-hosts * Due to that users might get spurious re-warnings of known systems. For Automation it might be worse as it might stop to work when re-executed. * This is a regression from Trusty (working) to Xenial (fail) upgrade due to an upstream bug in the versions we merged. * This is a backport of the upstream fix [Test Case] * Pick a Host IP to scan keys from that you can reach and replies with SSH, then run the following trivial loop: $ ssh-keyscan ${IP} > ~/.ssh/known_hosts; for i in $(seq 1 20); do ssh-keygen -H; diff -Naur ~/.ssh/known_hosts.old ~/.ssh/known_hosts; done * Expected: no diff reported, since already hashed entries should be left as-is * Without fix: - diff in the hashes [Regression Potential] * The fix is upstream and soon in Debian as well, so we are not custom diverting here. * The risk should be minimal as this only changes ssh-keygen so despite openssh being really critical this doesn't affect ssh itself at all. [Other Info] * n/a --- xenial @ 1:7.2p2-4ubuntu2.1 on amd64 has this bug. trusty @ 1:6.6p1-2ubuntu2.8 on amd64 does not have this bug. I have not tested any other ssh versions. The following should reproduce the issue: #ssh-keyscan > ~/.ssh/known_hosts # ssh root@X Permission denied (publickey). # ssh-keygen -H /root/.ssh/known_hosts updated. Original contents retained as /root/.ssh/known_hosts.old WARNING: /root/.ssh/known_hosts.old contains unhashed entries Delete this file to ensure privacy of hostnames # ssh root@XX Permission denied (publickey). # ssh-keygen -H /root/.ssh/known_hosts updated. Original contents retained as /root/.ssh/known_hosts.old WARNING: /root/.ssh/known_hosts.old contains unhashed entries Delete this file to ensure privacy of hostnames # ssh root@X The authenticity of host 'XX' can't be established. RSA key fingerprint is XX. Are you sure you want to continue connecting (yes/no)? # diff known_hosts.old known_hosts 1c1 < |1|BoAbRpUE3F5AzyprJcbjdepeDh8=|x/1AcaLxh45FlShmVQnlgx2qjxY= X --- > |1|nTPsoLxCugQyZi3pqOa2pc/cX64=|bUH5qwZlZPp8msMGHdLtslf3Huk= X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1668093/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1670745] Re: ssh-keyscan : bad host signature when using port option
This bug was fixed in the package openssh - 1:7.2p2-4ubuntu2.2 --- openssh (1:7.2p2-4ubuntu2.2) xenial; urgency=medium * Fix ssh-keygen -H accidentally corrupting known_hosts that contained already-hashed entries (LP: #1668093). * Fix ssh-keyscan to correctly hash hosts with a port number (LP: #1670745). -- Christian EhrhardtWed, 15 Mar 2017 13:16:56 +0100 ** Changed in: openssh (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1670745 Title: ssh-keyscan : bad host signature when using port option Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: Fix Released Status in openssh source package in Yakkety: Fix Released Status in openssh package in Debian: Fix Released Bug description: [Impact] * using ssh-keyscan while using the port (-p) option of it will create bad entries. They will contain the port and thereby be invalid for latter use under the purpose of known_hosts. * Fix by backporting upstream fix. [Test Case] * Further evolving from the simplification Josh provided: Testcase: $ release=xenial $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-client $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-server $ lxc exec ${release}-test-ssh-port-scan-server -- sed -i 's/Port 22/Port /' /etc/ssh/sshd_config $ lxc exec ${release}-test-ssh-port-scan-server -- service ssh restart $ IP=$(lxc exec ${release}-test-ssh-port-scan-server -- hostname --ip-address) $ lxc exec ${release}-test-ssh-port-scan-client -- ssh-keyscan -H -p ${IP} # See the port in the Hash still # Install the fixed version in *-client and see the port gone from the output [Regression Potential] * Change is limited to ssh-keyscan (not any touching other parts of openssh) * Fix is from upstream (no "Ubuntu special" change) * Fix is small and "only" changing string creation (11 lines touched) So overall the regression potential should be low. [Other Info] * n/a --- When I use the port option with ssh-keygen, the result is not compatible with ssh known_host file format. UBUNTU VERSION : lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 BAD : :~/.ssh$ cat /etc/issue Ubuntu 16.04.1 LTS \n \l :~/.ssh$ ssh-keyscan -v -p [...port...] -t ecdsa -H [...snip...] debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400 # [...snip...]:[...port...] SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3 debug1: Enabling compatibility mode for protocol 2.0 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha...@libssh.org debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY [|1|BEEwVcggbNPf7fUydgU4O+BDoLg=|9SmWBUxFZkpR70Hqq8uqxLAzXFU=]:[...port...] ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8= ==> we see the port number because it is not hashed ! GOOD : rm ~/.ssh/known_hosts :~/$ ssh -p [...port...] [...snip...] The authenticity of host '[[...snip...]]:[...port...] ([[...snip...]]:[...port...])' can't be established. ECDSA key fingerprint is SHA256:b/Jx+y3fNWFqOqTzFRI3XGrz33DBtAFFLmQaYQYFRnM. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '[[...snip...]]:[...port...],[[...snip...]]:[...port...]' (ECDSA) to the list of known hosts. [...snip...]@[...snip...]'s password: :~/$ !cat cat ~/.ssh/known_hosts |1|qdg91H9/DMHLO7yGOivI17+WFQI=|B+a6SrzF1GBd3XFvmAvQRnJxLWs= ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8= |1|8I/vbrBV04VaUF12JXRwxvAL9So=|ToMf+kRwbSeNertVdUVuG3iLdH8= ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8= ==> we cannot see the port number as it is well hashed ! REMARKS : == Same problem has already reported here (on macOS): https://github.com/ansible/ansible-modules-extras/issues/2651 It seems that ssh-keyscan version and open-ssh version differs : dpkg -l | grep openssh :: ii openssh-client 1:7.2p2-4ubuntu2.1 [...] ssh-keyscan -v
[Group.of.nepali.translators] [Bug 1670745] Re: ssh-keyscan : bad host signature when using port option
This bug was fixed in the package openssh - 1:7.3p1-1ubuntu0.1 --- openssh (1:7.3p1-1ubuntu0.1) yakkety; urgency=medium * Fix ssh-keygen -H accidentally corrupting known_hosts that contained already-hashed entries (LP: #1668093). * Fix ssh-keyscan to correctly hash hosts with a port number (LP: #1670745). -- Christian EhrhardtWed, 15 Mar 2017 14:25:22 +0100 ** Changed in: openssh (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1670745 Title: ssh-keyscan : bad host signature when using port option Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: Fix Committed Status in openssh source package in Yakkety: Fix Released Status in openssh package in Debian: Fix Released Bug description: [Impact] * using ssh-keyscan while using the port (-p) option of it will create bad entries. They will contain the port and thereby be invalid for latter use under the purpose of known_hosts. * Fix by backporting upstream fix. [Test Case] * Further evolving from the simplification Josh provided: Testcase: $ release=xenial $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-client $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-server $ lxc exec ${release}-test-ssh-port-scan-server -- sed -i 's/Port 22/Port /' /etc/ssh/sshd_config $ lxc exec ${release}-test-ssh-port-scan-server -- service ssh restart $ IP=$(lxc exec ${release}-test-ssh-port-scan-server -- hostname --ip-address) $ lxc exec ${release}-test-ssh-port-scan-client -- ssh-keyscan -H -p ${IP} # See the port in the Hash still # Install the fixed version in *-client and see the port gone from the output [Regression Potential] * Change is limited to ssh-keyscan (not any touching other parts of openssh) * Fix is from upstream (no "Ubuntu special" change) * Fix is small and "only" changing string creation (11 lines touched) So overall the regression potential should be low. [Other Info] * n/a --- When I use the port option with ssh-keygen, the result is not compatible with ssh known_host file format. UBUNTU VERSION : lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 BAD : :~/.ssh$ cat /etc/issue Ubuntu 16.04.1 LTS \n \l :~/.ssh$ ssh-keyscan -v -p [...port...] -t ecdsa -H [...snip...] debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400 # [...snip...]:[...port...] SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3 debug1: Enabling compatibility mode for protocol 2.0 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha...@libssh.org debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY [|1|BEEwVcggbNPf7fUydgU4O+BDoLg=|9SmWBUxFZkpR70Hqq8uqxLAzXFU=]:[...port...] ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8= ==> we see the port number because it is not hashed ! GOOD : rm ~/.ssh/known_hosts :~/$ ssh -p [...port...] [...snip...] The authenticity of host '[[...snip...]]:[...port...] ([[...snip...]]:[...port...])' can't be established. ECDSA key fingerprint is SHA256:b/Jx+y3fNWFqOqTzFRI3XGrz33DBtAFFLmQaYQYFRnM. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '[[...snip...]]:[...port...],[[...snip...]]:[...port...]' (ECDSA) to the list of known hosts. [...snip...]@[...snip...]'s password: :~/$ !cat cat ~/.ssh/known_hosts |1|qdg91H9/DMHLO7yGOivI17+WFQI=|B+a6SrzF1GBd3XFvmAvQRnJxLWs= ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8= |1|8I/vbrBV04VaUF12JXRwxvAL9So=|ToMf+kRwbSeNertVdUVuG3iLdH8= ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8= ==> we cannot see the port number as it is well hashed ! REMARKS : == Same problem has already reported here (on macOS): https://github.com/ansible/ansible-modules-extras/issues/2651 It seems that ssh-keyscan version and open-ssh version differs : dpkg -l | grep openssh :: ii openssh-client 1:7.2p2-4ubuntu2.1 [...] ssh-keyscan -v
[Group.of.nepali.translators] [Bug 1668093] Re: ssh-keygen -H corrupts already hashed entries
This bug was fixed in the package openssh - 1:7.3p1-1ubuntu0.1 --- openssh (1:7.3p1-1ubuntu0.1) yakkety; urgency=medium * Fix ssh-keygen -H accidentally corrupting known_hosts that contained already-hashed entries (LP: #1668093). * Fix ssh-keyscan to correctly hash hosts with a port number (LP: #1670745). -- Christian EhrhardtWed, 15 Mar 2017 14:25:22 +0100 ** Changed in: openssh (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1668093 Title: ssh-keygen -H corrupts already hashed entries Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: Fix Committed Status in openssh source package in Yakkety: Fix Released Status in openssh package in Debian: Fix Released Bug description: [Impact] * re-execution of ssh-keygen -H can clobber known-hosts * Due to that users might get spurious re-warnings of known systems. For Automation it might be worse as it might stop to work when re-executed. * This is a regression from Trusty (working) to Xenial (fail) upgrade due to an upstream bug in the versions we merged. * This is a backport of the upstream fix [Test Case] * Pick a Host IP to scan keys from that you can reach and replies with SSH, then run the following trivial loop: $ ssh-keyscan ${IP} > ~/.ssh/known_hosts; for i in $(seq 1 20); do ssh-keygen -H; diff -Naur ~/.ssh/known_hosts.old ~/.ssh/known_hosts; done * Expected: no diff reported, since already hashed entries should be left as-is * Without fix: - diff in the hashes [Regression Potential] * The fix is upstream and soon in Debian as well, so we are not custom diverting here. * The risk should be minimal as this only changes ssh-keygen so despite openssh being really critical this doesn't affect ssh itself at all. [Other Info] * n/a --- xenial @ 1:7.2p2-4ubuntu2.1 on amd64 has this bug. trusty @ 1:6.6p1-2ubuntu2.8 on amd64 does not have this bug. I have not tested any other ssh versions. The following should reproduce the issue: #ssh-keyscan > ~/.ssh/known_hosts # ssh root@X Permission denied (publickey). # ssh-keygen -H /root/.ssh/known_hosts updated. Original contents retained as /root/.ssh/known_hosts.old WARNING: /root/.ssh/known_hosts.old contains unhashed entries Delete this file to ensure privacy of hostnames # ssh root@XX Permission denied (publickey). # ssh-keygen -H /root/.ssh/known_hosts updated. Original contents retained as /root/.ssh/known_hosts.old WARNING: /root/.ssh/known_hosts.old contains unhashed entries Delete this file to ensure privacy of hostnames # ssh root@X The authenticity of host 'XX' can't be established. RSA key fingerprint is XX. Are you sure you want to continue connecting (yes/no)? # diff known_hosts.old known_hosts 1c1 < |1|BoAbRpUE3F5AzyprJcbjdepeDh8=|x/1AcaLxh45FlShmVQnlgx2qjxY= X --- > |1|nTPsoLxCugQyZi3pqOa2pc/cX64=|bUH5qwZlZPp8msMGHdLtslf3Huk= X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1668093/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1651623] Re: adt tests fail on zesty for apport
** Also affects: apport (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1651623 Title: adt tests fail on zesty for apport Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: New Status in apport source package in Yakkety: New Status in apport source package in Zesty: New Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1651623/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1689646] Re: Installing libapache2-mod-php7.0 doesn't enable PHP module
php7.0 is not in 17.10 (moved to php7.1). It was fixed in Debian in 7.0.8-3. Backporting the fix to 16.04 in the SRU we are currently doing to 7.0.18. ** Also affects: php7.0 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: php7.0 (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: php7.0 (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: php7.0 (Ubuntu Zesty) Status: New => Fix Released ** Changed in: php7.0 (Ubuntu Xenial) Status: New => Triaged ** Changed in: php7.0 (Ubuntu Xenial) Assignee: (unassigned) => Nish Aravamudan (nacc) ** Changed in: php7.0 (Ubuntu) Status: New => Invalid ** Changed in: php7.0 (Ubuntu Yakkety) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1689646 Title: Installing libapache2-mod-php7.0 doesn't enable PHP module Status in php7.0 package in Ubuntu: Invalid Status in php7.0 source package in Xenial: Triaged Status in php7.0 source package in Yakkety: Fix Released Status in php7.0 source package in Zesty: Fix Released Bug description: Steps to reproduce (on Xenial): 1) install libapache2-mod-php7.0 (note the warning/error) apt install libapache2-mod-php7.0 Setting up libapache2-mod-php7.0 (7.0.15-0ubuntu0.16.04.4) ... Warning: Could not load Apache 2.4 maintainer script helper. 2) apache isn't even running ps aux| grep apache # returns nothing 3) the apache2 packages was not pulled in, only apache2-bin dpkg -l| grep -w apache2 On Trusty, "apt install libapache2-mod-php5" was our way to setup PHP and have the MPM prefork enabled. I'm not sure if that was the wrong way and it worked by accident but this behavior change broke our tooling. Additional information: # lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 # apt-cache policy libapache2-mod-php7.0 apache2-bin libapache2-mod-php7.0: Installed: 7.0.15-0ubuntu0.16.04.4 Candidate: 7.0.15-0ubuntu0.16.04.4 Version table: *** 7.0.15-0ubuntu0.16.04.4 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 7.0.4-7ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages apache2-bin: Installed: 2.4.18-2ubuntu3.1 Candidate: 2.4.18-2ubuntu3.1 Version table: *** 2.4.18-2ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.18-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libapache2-mod-php7.0 7.0.15-0ubuntu0.16.04.4 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue May 9 19:58:26 2017 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: php7.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1689646/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1630516] Re: Logrotate doesn't clean old system logs, allowing them to fill the disk
This bug was fixed in the package logrotate - 3.8.7-2ubuntu2.16.04.1 --- logrotate (3.8.7-2ubuntu2.16.04.1) xenial; urgency=medium * createOutputFile: rename already existing file (LP: #1630516) - d/p/ubuntu/createOutputFile-eliminate-stat-open-TOCTOU-race.patch - d/p/ubuntu/createOutputFile-rename-already-existing-file.patch -- Christian EhrhardtWed, 22 Mar 2017 11:47:34 +0100 ** Changed in: logrotate (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1630516 Title: Logrotate doesn't clean old system logs, allowing them to fill the disk Status in One Hundred Papercuts: Triaged Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Trusty: Fix Committed Status in logrotate source package in Xenial: Fix Released Status in logrotate source package in Yakkety: Fix Committed Status in logrotate source package in Zesty: Fix Released Status in logrotate package in Debian: Fix Released Bug description: [Impact] Logrotate fails to rotate a log and then will continue to fail to rotate it until manual intervention takes place. If messaging has not been configured on the system there will be no warning issued to the user. The log will grow day by day until a user intervenes or the drive that the log is stored on is full. Very large log files can make it more difficult to find useful data. Full drives make the rest of the system fail to operate. Backporting a fix would prevent drives filling up on stable releases. [Test Case] Go to your logs area (/var/logs) and create a file with a name ending .2, as would be created part way through the logrotate process. So if you have /var/log/syslog, /var/log/syslog.1, /var/log/syslog.2.gz, /var/log/syslog.3.gz; create a new file named /var/log/syslog.2. Your subsequent log rotate runs will fail. [Regression Potential] - I'd hope the potential is low as it only triggers under certain conditions that are special (target filename in the way). - So far in those conditions it failed to rotate - Yet If despite my hope there still manifests an issue I'd expect it could be renaming files it should not, so people would end up "missing" their logs - the good thing is that this is a rename, so they should find it at different names. - Another thing I consider possible is that some unexpected conditions cause e.g. a crash in the changed code, in that case the logs are not rotated, but since there is no unlink the logs will still exist. - Therefore I consider the Potential low enough to consider the fix. [Other Info] n/a --- Good afternoon. I have started seeing something very similar to Debian Dug 734688 "Logs are not rotated for a month" but in the latest Ubuntu LTS (16.04). I seem to have $ logrotate --version logrotate 3.8.7 bundled in it. A few weeks ago I started getting root emails such as this: > Subject: Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) > > /etc/cron.daily/logrotate: > error: error creating output file /var/log/munin/munin-node.log.1: File exists > run-parts: /etc/cron.daily/logrotate exited with return code 1 When I inspected the area of concern I was able to see that there was an existing .1 file. manager@warden:/var/log/munin$ ll total 580 drwxr-xr-x 2 munin adm 4096 Sep 27 06:31 ./ drwxr-xr-x 13 root syslog 4096 Oct 5 06:26 ../ -rw-r--r-- 1 root root 3440 Sep 26 13:39 munin-node-configure.log -rw-r--r-- 1 root root 490251 Oct 5 10:25 munin-node.log -rw-r--r-- 1 root root56598 Sep 21 02:01 munin-node.log.1 -rw-r--r-- 1 root root24576 Aug 31 02:01 munin-node.log.2 -rw-r--r-- 1 root root 1906 Sep 19 06:25 munin-node.log.8.gz The contents of the munin-node.log file seem to run from the 19th September until today. Unlike other parts of this bug the .1 and .2 files do not seem to be already compressed. I deleted all but the munin-node.log file to see if it would resolve the problem and was going to leave it at that. Then I noticed that I have had another Ubuntu machine which has been sending similar emails for the past week: > Subject: Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) > > /etc/cron.daily/logrotate: > error: error creating output file /var/log/syslog.1.gz: File exists > run-parts: /etc/cron.daily/logrotate exited with return code 1 Different file, different machine but a very similar error message. Checking on the syslog file I can see that it better fits with other reports on this bug as my duplicated .1 files has a corresponding .1.gz file.
[Group.of.nepali.translators] [Bug 1676845] Re: libgles1-mesa is being removed, don't depend on it
This bug was fixed in the package vlc - 2.2.2-5ubuntu0.16.04.2 --- vlc (2.2.2-5ubuntu0.16.04.2) xenial; urgency=medium * Don't enable GLESv1 support. (LP: #1676845) -- Timo AaltonenTue, 28 Mar 2017 14:23:57 +0300 ** Changed in: vlc (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: opentk (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1676845 Title: libgles1-mesa is being removed, don't depend on it Status in opentk package in Ubuntu: Fix Released Status in vlc package in Ubuntu: Fix Released Status in opentk source package in Xenial: Fix Released Status in vlc source package in Xenial: Fix Released Status in opentk source package in Yakkety: Fix Committed Status in vlc source package in Yakkety: Fix Committed Bug description: [Impact] Mesa in zesty has dropped libgles1-mesa, slightly ahead of upstream. Backporting mesa to xenial & yakkety requires packages that depend on it to stop doing that. Nothing really should depend on OpenGL ES v1 (GLESv1), which was meant for fixed-function GPU's, and we don't support those anyway. For a reference, Fedora never enabled support for it in Mesa. [Test case] Check that vlc / libopentk1.1-cil are installable together with Mesa 17.0.x [Regression potential] GLESv1 is not needed by anything really, so there shouldn't be a risk of regressing any use case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opentk/+bug/1676845/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1512992] Re: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package
This bug was fixed in the package zlib - 1:1.2.8.dfsg-2ubuntu4.1 --- zlib (1:1.2.8.dfsg-2ubuntu4.1) xenial-proposed; urgency=medium * SRU * Move zconf.h back to /usr/include (not differing across architectures) anymore. Closes: #787956. LP: #1512992. -- Matthias KloseFri, 03 Mar 2017 18:31:53 +0100 ** Changed in: zlib (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: zlib (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1512992 Title: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 Status in One Hundred Papercuts: Confirmed Status in zlib package in Ubuntu: Fix Released Status in zlib source package in Xenial: Fix Released Status in zlib source package in Yakkety: Fix Released Bug description: Test Case - 1) Install zlib1g-dev:i386 2) Install lib32z1-dev. 3) Observe a package installation failure After enabling -proposed you should be able to install both packages without an issue. Original Description The package did not install when I did a fresh install of 15.10. ProblemType: PackageDistroRelease: Ubuntu 15.10 Package: zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 Date: Wed Nov 4 10:36:43 2015 DuplicateSignature: package:zlib1g-dev:1:1.2.8.dfsg-2ubuntu4:trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 ErrorMessage: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 InstallationDate: Installed on 2015-11-04 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1SourcePackage: zlib Title: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1512992/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1689820] Re: /usr/lib/packagekit/packagekitd:11:pkgCache::Iterator:AcqPackageKitStatus::updateStatus:AcqPackageKitStatus::Fail:pkgAcquire::Worker::RunMessages:pkgAcq
This is quite simple to reproduce: $ pkcon get-updates Getting updates [=] Loading cache [=] Querying [=] Finished [=] Bug fix linux-generic-4.4.0.77.83.amd64 (xenial-updates) Complete Generic Linux kernel and headers Bug fix linux-headers-generic-4.4.0.77.83.amd64 (xenial-updates) Generic Linux kernel headers Bug fix linux-headers-virtual-4.4.0.77.83.amd64 (xenial-updates) Transitional package. Bug fix linux-image-generic-4.4.0.77.83.amd64 (xenial-updates) Generic Linux kernel image Bug fix linux-image-virtual-4.4.0.77.83.amd64 (xenial-updates) This package will always depend on the latest minimal generic kernel image. Bug fix linux-virtual-4.4.0.77.83.amd64 (xenial-updates) Minimal Generic Linux kernel and headers $ pkcon get-update-detail linux-image-virtual Resolving [=] Getting update details[=] Loading cache [=] Downloading packages [ ] (0%) The daemon crashed mid-transaction! This doesn't seem to be specific to the particular package. If I downgrade tzdata $ sudo apt-get install tzdata=2016d-0ubuntu0.16.04 and query that it crashes as well: $ pkcon get-update-detail tzdata Downloading packages [ ] (0%) The daemon crashed mid-transaction! 0x723ad6d5 in AcqPackageKitStatus::updateStatus(pkgAcquire::ItemDesc&, int) () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so (gdb) bt #0 0x723ad6d5 in AcqPackageKitStatus::updateStatus(pkgAcquire::ItemDesc&, int) () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so #1 0x723ad7d3 in AcqPackageKitStatus::Fail(pkgAcquire::ItemDesc&) () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so #2 0x71b2bd96 in pkgAcquire::Worker::RunMessages() () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 #3 0x71b2d9dc in pkgAcquire::Worker::InFdReady() () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 #4 0x71b2f1ba in pkgAcquire::RunFdsSane(fd_set*, fd_set*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 #5 0x71b32dd2 in pkgAcquire::Run(int) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 #6 0x723b4be1 in downloadChangelog(AptCacheFile&, pkgAcquire&, pkgCache::VerIterator, std::__cxx11::basic_string) () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so #7 0x723c6888 in AptIntf::emitUpdateDetail(pkgCache::VerIterator const&) () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so #8 0x723c73c5 in AptIntf::emitUpdateDetails(PkgList const&) () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so #9 0x723cbffd in ?? () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so #10 0x5556e419 in ?? () #11 0x76c0cbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x769866ba in start_thread (arg=0x709ec700) at pthread_create.c:333 #13 0x766bc82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 (gdb) bt full #0 0x723ad6d5 in AcqPackageKitStatus::updateStatus(pkgAcquire::ItemDesc&, int) () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so No symbol table info available. #1 0x723ad7d3 in AcqPackageKitStatus::Fail(pkgAcquire::ItemDesc&) () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so No symbol table info available. #2 0x71b2bd96 in pkgAcquire::Worker::RunMessages() () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 ** Also affects: packagekit (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1689820 Title: /usr/lib/packagekit/packagekitd:11:pkgCache::Iterator:AcqPackageKitStatus::updateStatus:AcqPackageKitStatus::Fail:pkgAcquire::Worker::RunMessages:pkgAcquire::Worker::InFdReady Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Xenial: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 0.8.17-4ubuntu6~gcc5.4ubuntu1.1, the problem page at https://errors.ubuntu.com/problem/8c37a6988b890cc46b415972ef1e2ca746f9ffcc contains
[Group.of.nepali.translators] [Bug 1689820] Re: /usr/lib/packagekit/packagekitd:11:pkgCache::Iterator:AcqPackageKitStatus::updateStatus:AcqPackageKitStatus::Fail:pkgAcquire::Worker::RunMessages:pkgAcq
I confirmed that this is fixed in zesty. ** Changed in: packagekit (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1689820 Title: /usr/lib/packagekit/packagekitd:11:pkgCache::Iterator:AcqPackageKitStatus::updateStatus:AcqPackageKitStatus::Fail:pkgAcquire::Worker::RunMessages:pkgAcquire::Worker::InFdReady Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Xenial: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 0.8.17-4ubuntu6~gcc5.4ubuntu1.1, the problem page at https://errors.ubuntu.com/problem/8c37a6988b890cc46b415972ef1e2ca746f9ffcc 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/packagekit/+bug/1689820/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1686978] Re: linux-hwe: 4.8.0-52.55~16.04.1 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru- testing/xenial/4.8.0-52.55~16.04.1/xenial-4.8-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1686978 Title: linux-hwe: 4.8.0-52.55~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686976 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686978/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1614052] Re: SOSREPORT need to collect OPAL msglog
This bug was fixed in the package sosreport - 3.4-1~ubuntu17.04.1 --- sosreport (3.4-1~ubuntu17.04.1) zesty; urgency=medium * Release of the current artful 3.4 version that fixes some specific Ubuntu issues : - Collection of the OPAL msglog (LP: #1614052) - Add ZFS sosreport plugin (LP: #1666239) * Ubuntu specific modifications to sosreport not yet upstream : - Inclusion of DEP8 tests to verify regression. This is required to SRU to a new major version. - Take into account the iscsi initiator config and logs (LP: #1605243) - d/p/0003-plugins-Handle-stat-errors-on-missing-files.patch: Properly handle os.stat() when file is missing or broken link -- Louis BouchardTue, 25 Apr 2017 16:51:14 +0200 ** Changed in: sosreport (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1614052 Title: SOSREPORT need to collect OPAL msglog Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Trusty: Fix Released Status in sosreport source package in Xenial: Fix Released Status in sosreport source package in Yakkety: Fix Released Status in sosreport source package in Zesty: Fix Released Bug description: [SRU justification] Required to collect OPAL message log [Impact] Logs are unavailable without this fix [Fix] Add collection of /sys/firmware/opal/msglog if it exists [Test Case] Run sosreport on ppc64el with : $ sudo sosreport --batch -opowerpc The content of /sys/firmware/opal/msglog will be collected [~apw: we also need to test a selection of the other data is collected still to ensure we did not regress any non-opal data.] [Regression] None, this was not collected previously. [Original description of the problem] == Comment: #0 - Mukesh K. Ojha - 2016-08-17 02:13:40 == ---Problem Description--- Currently, SOSREPORT version used by 16.04.01 LTS release does not collect OPAL log which is present in /sys/firmware/opal/msglog. A patch has been submitted upstream(https://github.com/sosreport/sos.git) to do the above thing. commit 1bbf9e9690e7f2a5afc234b905537daacaecb6d4 Author: Joel Stanley Date: Tue Apr 15 14:05:17 2014 +0100 Add OPAL log to collected file list The OPAL console log used to live under /sys/kernel/debug/powerpc so it was collected as part of that glob. This patch adds the new location at /sys/firmware/opal/msglog to the list of collected files. Signed-off-by: Joel Stanley Reviewed-by: Vasant Hegde Contact Information = Contact Information = hegdevas...@linux.vnet.ibm.com, mukeo...@in.ibm.com ---uname output--- Ubuntu 16.04.01 LTS Machine Type = All power machine ---Debugger--- A debugger is not configured ---Steps to Reproduce--- root@ltctul57a-p1:/home/mukesh# sosreport sosreport (version 3.2.0a1) This command will collect system configuration and diagnostic information from this Ubuntu system. An archive containing the collected information will be generated in /tmp/sos.sj1x27eq. For more information on Ubuntu visit: http://www.ubuntu.com/ The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Press ENTER to continue, or CTRL-C to quit. Please enter your first initial and last name [ltctul57a-p1]: Please enter the case id that you are generating this report for []: Setting up archive ... Setting up plugins ... Running plugins. Please wait ... Running 73/73: xfs... Creating compressed archive... Your sosreport has been generated and saved in: /tmp/sosreport-ltctul57a-p1-20160810185800.tar.xz The checksum is: 33dbfc480ebf985e4372430537339c1c Please send this file to your support representative. root@ltctul57a-p1:/home/mukesh# root@ltctul57a-p1:/home/mukesh/sosreport-ltctul57a-p1-20160810185800# ls boot dev etc hostnameip_addr lib lsmod lspci netstat ps route sos_commands sos_reports uname usr version.txt date df free installed-debs last lsb-release lsof mount proc pstree runsos_logs sys uptime var vgdisplay root@ltctul57a-p1:/home/mukesh/sosreport-ltctul57a-p1-20160810185800# ls sys/ bus class devices fs kernel module root@ltctul57a-p1:/home/mukesh/sosreport-ltctul57a-p1-20160810185800# No Firmware directory available that confirms the unavailability of OPAL msglog. Userspace tool common name: sosreport The userspace tool has the following
[Group.of.nepali.translators] [Bug 1605243] Re: iscsi initiator related configs and logs are not recorded
This bug was fixed in the package sosreport - 3.4-1~ubuntu17.04.1 --- sosreport (3.4-1~ubuntu17.04.1) zesty; urgency=medium * Release of the current artful 3.4 version that fixes some specific Ubuntu issues : - Collection of the OPAL msglog (LP: #1614052) - Add ZFS sosreport plugin (LP: #1666239) * Ubuntu specific modifications to sosreport not yet upstream : - Inclusion of DEP8 tests to verify regression. This is required to SRU to a new major version. - Take into account the iscsi initiator config and logs (LP: #1605243) - d/p/0003-plugins-Handle-stat-errors-on-missing-files.patch: Properly handle os.stat() when file is missing or broken link -- Louis BouchardTue, 25 Apr 2017 16:51:14 +0200 ** Changed in: sosreport (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1605243 Title: iscsi initiator related configs and logs are not recorded Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Trusty: Fix Released Status in sosreport source package in Xenial: Fix Released Status in sosreport source package in Yakkety: Fix Released Status in sosreport source package in Zesty: Fix Released Bug description: [SRU justification] iscsi initiator data is needed for proper analysis [Impact] Difficult to investigate iscsi problems w/o the data [Fix] Enable the iscsi plugin for Ubuntu and Debian [Test Case] Without the fix, invoking the iscsi plugin will show : # sosreport --batch -oiscsi sosreport (version 3.1) a non-existing plugin (iscsi) was specified in the command line With the fix, the command will run successfully and collect the appropriate data. [Regression] None, the plugin was disabled previously. [Original description of the problem] iscsi useful initiator information such as: 1). etc/iscsi/* 2). iscsiadm -m session -P3 These 2 are useful for debugging the iscsi initiator side bug. However, it's not included by default in the sosreport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1605243/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1614052] Re: SOSREPORT need to collect OPAL msglog
This bug was fixed in the package sosreport - 3.4-1~ubuntu16.10.1 --- sosreport (3.4-1~ubuntu16.10.1) yakkety; urgency=medium * Release of the current artful 3.4 version that fixes some specific Ubuntu issues : - Collection of the OPAL msglog (LP: #1614052) - Add ZFS sosreport plugin (LP: #1666239) * Ubuntu specific modifications to sosreport not yet upstream : - Inclusion of DEP8 tests to verify regression. This is required to SRU to a new major version. - Take into account the iscsi initiator config and logs (LP: #1605243) - d/p/0003-plugins-Handle-stat-errors-on-missing-files.patch: Properly handle os.stat() when file is missing or broken link -- Louis BouchardTue, 25 Apr 2017 16:51:14 +0200 ** Changed in: sosreport (Ubuntu Yakkety) Status: Fix Committed => Fix Released ** Changed in: sosreport (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1614052 Title: SOSREPORT need to collect OPAL msglog Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Trusty: Fix Released Status in sosreport source package in Xenial: Fix Released Status in sosreport source package in Yakkety: Fix Released Status in sosreport source package in Zesty: Fix Released Bug description: [SRU justification] Required to collect OPAL message log [Impact] Logs are unavailable without this fix [Fix] Add collection of /sys/firmware/opal/msglog if it exists [Test Case] Run sosreport on ppc64el with : $ sudo sosreport --batch -opowerpc The content of /sys/firmware/opal/msglog will be collected [~apw: we also need to test a selection of the other data is collected still to ensure we did not regress any non-opal data.] [Regression] None, this was not collected previously. [Original description of the problem] == Comment: #0 - Mukesh K. Ojha - 2016-08-17 02:13:40 == ---Problem Description--- Currently, SOSREPORT version used by 16.04.01 LTS release does not collect OPAL log which is present in /sys/firmware/opal/msglog. A patch has been submitted upstream(https://github.com/sosreport/sos.git) to do the above thing. commit 1bbf9e9690e7f2a5afc234b905537daacaecb6d4 Author: Joel Stanley Date: Tue Apr 15 14:05:17 2014 +0100 Add OPAL log to collected file list The OPAL console log used to live under /sys/kernel/debug/powerpc so it was collected as part of that glob. This patch adds the new location at /sys/firmware/opal/msglog to the list of collected files. Signed-off-by: Joel Stanley Reviewed-by: Vasant Hegde Contact Information = Contact Information = hegdevas...@linux.vnet.ibm.com, mukeo...@in.ibm.com ---uname output--- Ubuntu 16.04.01 LTS Machine Type = All power machine ---Debugger--- A debugger is not configured ---Steps to Reproduce--- root@ltctul57a-p1:/home/mukesh# sosreport sosreport (version 3.2.0a1) This command will collect system configuration and diagnostic information from this Ubuntu system. An archive containing the collected information will be generated in /tmp/sos.sj1x27eq. For more information on Ubuntu visit: http://www.ubuntu.com/ The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Press ENTER to continue, or CTRL-C to quit. Please enter your first initial and last name [ltctul57a-p1]: Please enter the case id that you are generating this report for []: Setting up archive ... Setting up plugins ... Running plugins. Please wait ... Running 73/73: xfs... Creating compressed archive... Your sosreport has been generated and saved in: /tmp/sosreport-ltctul57a-p1-20160810185800.tar.xz The checksum is: 33dbfc480ebf985e4372430537339c1c Please send this file to your support representative. root@ltctul57a-p1:/home/mukesh# root@ltctul57a-p1:/home/mukesh/sosreport-ltctul57a-p1-20160810185800# ls boot dev etc hostnameip_addr lib lsmod lspci netstat ps route sos_commands sos_reports uname usr version.txt date df free installed-debs last lsb-release lsof mount proc pstree runsos_logs sys uptime var vgdisplay root@ltctul57a-p1:/home/mukesh/sosreport-ltctul57a-p1-20160810185800# ls sys/ bus class devices fs kernel module root@ltctul57a-p1:/home/mukesh/sosreport-ltctul57a-p1-20160810185800# No Firmware directory available that confirms the unavailability of OPAL
[Group.of.nepali.translators] [Bug 1605243] Re: iscsi initiator related configs and logs are not recorded
This bug was fixed in the package sosreport - 3.4-1~ubuntu14.04.1 --- sosreport (3.4-1~ubuntu14.04.1) trusty; urgency=medium * Release of the current artful 3.4 version that fixes some specific Ubuntu issues : - Collection of the OPAL msglog (LP: #1614052) - Add ZFS sosreport plugin (LP: #1666239) * Ubuntu specific modifications to sosreport not yet upstream : - Inclusion of DEP8 tests to verify regression. This is required to SRU to a new major version. - Take into account the iscsi initiator config and logs (LP: #1605243) - d/p/0003-plugins-Handle-stat-errors-on-missing-files.patch: Properly handle os.stat() when file is missing or broken link -- Louis BouchardTue, 25 Apr 2017 16:34:41 +0200 ** Changed in: sosreport (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1605243 Title: iscsi initiator related configs and logs are not recorded Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Trusty: Fix Released Status in sosreport source package in Xenial: Fix Released Status in sosreport source package in Yakkety: Fix Released Status in sosreport source package in Zesty: Fix Released Bug description: [SRU justification] iscsi initiator data is needed for proper analysis [Impact] Difficult to investigate iscsi problems w/o the data [Fix] Enable the iscsi plugin for Ubuntu and Debian [Test Case] Without the fix, invoking the iscsi plugin will show : # sosreport --batch -oiscsi sosreport (version 3.1) a non-existing plugin (iscsi) was specified in the command line With the fix, the command will run successfully and collect the appropriate data. [Regression] None, the plugin was disabled previously. [Original description of the problem] iscsi useful initiator information such as: 1). etc/iscsi/* 2). iscsiadm -m session -P3 These 2 are useful for debugging the iscsi initiator side bug. However, it's not included by default in the sosreport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1605243/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1605243] Re: iscsi initiator related configs and logs are not recorded
This bug was fixed in the package sosreport - 3.4-1~ubuntu16.10.1 --- sosreport (3.4-1~ubuntu16.10.1) yakkety; urgency=medium * Release of the current artful 3.4 version that fixes some specific Ubuntu issues : - Collection of the OPAL msglog (LP: #1614052) - Add ZFS sosreport plugin (LP: #1666239) * Ubuntu specific modifications to sosreport not yet upstream : - Inclusion of DEP8 tests to verify regression. This is required to SRU to a new major version. - Take into account the iscsi initiator config and logs (LP: #1605243) - d/p/0003-plugins-Handle-stat-errors-on-missing-files.patch: Properly handle os.stat() when file is missing or broken link -- Louis BouchardTue, 25 Apr 2017 16:51:14 +0200 ** Changed in: sosreport (Ubuntu Yakkety) Status: Fix Committed => Fix Released ** Changed in: sosreport (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1605243 Title: iscsi initiator related configs and logs are not recorded Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Trusty: Fix Released Status in sosreport source package in Xenial: Fix Released Status in sosreport source package in Yakkety: Fix Released Status in sosreport source package in Zesty: Fix Released Bug description: [SRU justification] iscsi initiator data is needed for proper analysis [Impact] Difficult to investigate iscsi problems w/o the data [Fix] Enable the iscsi plugin for Ubuntu and Debian [Test Case] Without the fix, invoking the iscsi plugin will show : # sosreport --batch -oiscsi sosreport (version 3.1) a non-existing plugin (iscsi) was specified in the command line With the fix, the command will run successfully and collect the appropriate data. [Regression] None, the plugin was disabled previously. [Original description of the problem] iscsi useful initiator information such as: 1). etc/iscsi/* 2). iscsiadm -m session -P3 These 2 are useful for debugging the iscsi initiator side bug. However, it's not included by default in the sosreport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1605243/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1614052] Re: SOSREPORT need to collect OPAL msglog
This bug was fixed in the package sosreport - 3.4-1~ubuntu14.04.1 --- sosreport (3.4-1~ubuntu14.04.1) trusty; urgency=medium * Release of the current artful 3.4 version that fixes some specific Ubuntu issues : - Collection of the OPAL msglog (LP: #1614052) - Add ZFS sosreport plugin (LP: #1666239) * Ubuntu specific modifications to sosreport not yet upstream : - Inclusion of DEP8 tests to verify regression. This is required to SRU to a new major version. - Take into account the iscsi initiator config and logs (LP: #1605243) - d/p/0003-plugins-Handle-stat-errors-on-missing-files.patch: Properly handle os.stat() when file is missing or broken link -- Louis BouchardTue, 25 Apr 2017 16:34:41 +0200 ** Changed in: sosreport (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1614052 Title: SOSREPORT need to collect OPAL msglog Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Trusty: Fix Released Status in sosreport source package in Xenial: Fix Released Status in sosreport source package in Yakkety: Fix Released Status in sosreport source package in Zesty: Fix Released Bug description: [SRU justification] Required to collect OPAL message log [Impact] Logs are unavailable without this fix [Fix] Add collection of /sys/firmware/opal/msglog if it exists [Test Case] Run sosreport on ppc64el with : $ sudo sosreport --batch -opowerpc The content of /sys/firmware/opal/msglog will be collected [~apw: we also need to test a selection of the other data is collected still to ensure we did not regress any non-opal data.] [Regression] None, this was not collected previously. [Original description of the problem] == Comment: #0 - Mukesh K. Ojha - 2016-08-17 02:13:40 == ---Problem Description--- Currently, SOSREPORT version used by 16.04.01 LTS release does not collect OPAL log which is present in /sys/firmware/opal/msglog. A patch has been submitted upstream(https://github.com/sosreport/sos.git) to do the above thing. commit 1bbf9e9690e7f2a5afc234b905537daacaecb6d4 Author: Joel Stanley Date: Tue Apr 15 14:05:17 2014 +0100 Add OPAL log to collected file list The OPAL console log used to live under /sys/kernel/debug/powerpc so it was collected as part of that glob. This patch adds the new location at /sys/firmware/opal/msglog to the list of collected files. Signed-off-by: Joel Stanley Reviewed-by: Vasant Hegde Contact Information = Contact Information = hegdevas...@linux.vnet.ibm.com, mukeo...@in.ibm.com ---uname output--- Ubuntu 16.04.01 LTS Machine Type = All power machine ---Debugger--- A debugger is not configured ---Steps to Reproduce--- root@ltctul57a-p1:/home/mukesh# sosreport sosreport (version 3.2.0a1) This command will collect system configuration and diagnostic information from this Ubuntu system. An archive containing the collected information will be generated in /tmp/sos.sj1x27eq. For more information on Ubuntu visit: http://www.ubuntu.com/ The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Press ENTER to continue, or CTRL-C to quit. Please enter your first initial and last name [ltctul57a-p1]: Please enter the case id that you are generating this report for []: Setting up archive ... Setting up plugins ... Running plugins. Please wait ... Running 73/73: xfs... Creating compressed archive... Your sosreport has been generated and saved in: /tmp/sosreport-ltctul57a-p1-20160810185800.tar.xz The checksum is: 33dbfc480ebf985e4372430537339c1c Please send this file to your support representative. root@ltctul57a-p1:/home/mukesh# root@ltctul57a-p1:/home/mukesh/sosreport-ltctul57a-p1-20160810185800# ls boot dev etc hostnameip_addr lib lsmod lspci netstat ps route sos_commands sos_reports uname usr version.txt date df free installed-debs last lsb-release lsof mount proc pstree runsos_logs sys uptime var vgdisplay root@ltctul57a-p1:/home/mukesh/sosreport-ltctul57a-p1-20160810185800# ls sys/ bus class devices fs kernel module root@ltctul57a-p1:/home/mukesh/sosreport-ltctul57a-p1-20160810185800# No Firmware directory available that confirms the unavailability of OPAL msglog. Userspace tool common name: sosreport The userspace tool has the following
[Group.of.nepali.translators] [Bug 1666239] Re: Add ZFS sosreport plugin
This bug was fixed in the package sosreport - 3.4-1~ubuntu14.04.1 --- sosreport (3.4-1~ubuntu14.04.1) trusty; urgency=medium * Release of the current artful 3.4 version that fixes some specific Ubuntu issues : - Collection of the OPAL msglog (LP: #1614052) - Add ZFS sosreport plugin (LP: #1666239) * Ubuntu specific modifications to sosreport not yet upstream : - Inclusion of DEP8 tests to verify regression. This is required to SRU to a new major version. - Take into account the iscsi initiator config and logs (LP: #1605243) - d/p/0003-plugins-Handle-stat-errors-on-missing-files.patch: Properly handle os.stat() when file is missing or broken link -- Louis BouchardTue, 25 Apr 2017 16:34:41 +0200 ** Changed in: sosreport (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1666239 Title: Add ZFS sosreport plugin Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Trusty: Fix Released Status in sosreport source package in Xenial: Fix Released Status in sosreport source package in Yakkety: Fix Released Status in sosreport source package in Zesty: Fix Released Bug description: [Impact] * Current sosreport doesn't include any ZFS verifications, which could be useful for general initial ZFS troubleshooting on Xenial and upward. (Xenial being the release where ZFS has been first introduced in Ubuntu.) [Test Case] #1) Have ZFS installed and configured - https://wiki.ubuntu.com/Kernel/Reference/ZFS #2) Have sosreport installed and configured $ sudo apt-get update $ sudo apt-get install sosreport -y #3) Run sosreport $ /usr/bin/sosreport -a #4) Lookin for a sosreport*.tar.xz file in /tmp - In PATH_TO_SOSREPORT/sos_commands/, there will be no trace of zfs output, cause as of today, there is no ZFS plugin in Ubuntu/Debian nor upstream. [Regression Potential] * No regression * The PR passed all the upstream checks. [Other Info] * Pull Request: https://github.com/sosreport/sos/pull/934 (Closed #934 via 922ea54) * Commit : https://github.com/sosreport/sos/commit/922ea54bf4f9cb488f72a75a180e5351169dd710 [Original Description] I did a PR to upstream sosreport in order to include the ZFS plugin for Ubuntu/Debian. PR: https://github.com/sosreport/sos/pull/934 Commit : https://github.com/sosreport/sos/commit/922ea54bf4f9cb488f72a75a180e5351169dd710 The ZFS plugin is collecting ZFS informations using the following commands : "zfs get all" "zfs list -t all -o space" "zpool list" "zpool status -x" It would be great to have this ZFS plugin available for Xenial (where ZFS has been first introduce in Ubuntu) and upward (Zesty, ...) - Eric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1666239/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1666239] Re: Add ZFS sosreport plugin
This bug was fixed in the package sosreport - 3.4-1~ubuntu16.10.1 --- sosreport (3.4-1~ubuntu16.10.1) yakkety; urgency=medium * Release of the current artful 3.4 version that fixes some specific Ubuntu issues : - Collection of the OPAL msglog (LP: #1614052) - Add ZFS sosreport plugin (LP: #1666239) * Ubuntu specific modifications to sosreport not yet upstream : - Inclusion of DEP8 tests to verify regression. This is required to SRU to a new major version. - Take into account the iscsi initiator config and logs (LP: #1605243) - d/p/0003-plugins-Handle-stat-errors-on-missing-files.patch: Properly handle os.stat() when file is missing or broken link -- Louis BouchardTue, 25 Apr 2017 16:51:14 +0200 ** Changed in: sosreport (Ubuntu Yakkety) Status: Fix Committed => Fix Released ** Changed in: sosreport (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1666239 Title: Add ZFS sosreport plugin Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Trusty: Fix Released Status in sosreport source package in Xenial: Fix Released Status in sosreport source package in Yakkety: Fix Released Status in sosreport source package in Zesty: Fix Released Bug description: [Impact] * Current sosreport doesn't include any ZFS verifications, which could be useful for general initial ZFS troubleshooting on Xenial and upward. (Xenial being the release where ZFS has been first introduced in Ubuntu.) [Test Case] #1) Have ZFS installed and configured - https://wiki.ubuntu.com/Kernel/Reference/ZFS #2) Have sosreport installed and configured $ sudo apt-get update $ sudo apt-get install sosreport -y #3) Run sosreport $ /usr/bin/sosreport -a #4) Lookin for a sosreport*.tar.xz file in /tmp - In PATH_TO_SOSREPORT/sos_commands/, there will be no trace of zfs output, cause as of today, there is no ZFS plugin in Ubuntu/Debian nor upstream. [Regression Potential] * No regression * The PR passed all the upstream checks. [Other Info] * Pull Request: https://github.com/sosreport/sos/pull/934 (Closed #934 via 922ea54) * Commit : https://github.com/sosreport/sos/commit/922ea54bf4f9cb488f72a75a180e5351169dd710 [Original Description] I did a PR to upstream sosreport in order to include the ZFS plugin for Ubuntu/Debian. PR: https://github.com/sosreport/sos/pull/934 Commit : https://github.com/sosreport/sos/commit/922ea54bf4f9cb488f72a75a180e5351169dd710 The ZFS plugin is collecting ZFS informations using the following commands : "zfs get all" "zfs list -t all -o space" "zpool list" "zpool status -x" It would be great to have this ZFS plugin available for Xenial (where ZFS has been first introduce in Ubuntu) and upward (Zesty, ...) - Eric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1666239/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1666239] Re: Add ZFS sosreport plugin
This bug was fixed in the package sosreport - 3.4-1~ubuntu17.04.1 --- sosreport (3.4-1~ubuntu17.04.1) zesty; urgency=medium * Release of the current artful 3.4 version that fixes some specific Ubuntu issues : - Collection of the OPAL msglog (LP: #1614052) - Add ZFS sosreport plugin (LP: #1666239) * Ubuntu specific modifications to sosreport not yet upstream : - Inclusion of DEP8 tests to verify regression. This is required to SRU to a new major version. - Take into account the iscsi initiator config and logs (LP: #1605243) - d/p/0003-plugins-Handle-stat-errors-on-missing-files.patch: Properly handle os.stat() when file is missing or broken link -- Louis BouchardTue, 25 Apr 2017 16:51:14 +0200 ** Changed in: sosreport (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1666239 Title: Add ZFS sosreport plugin Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Trusty: Fix Released Status in sosreport source package in Xenial: Fix Released Status in sosreport source package in Yakkety: Fix Released Status in sosreport source package in Zesty: Fix Released Bug description: [Impact] * Current sosreport doesn't include any ZFS verifications, which could be useful for general initial ZFS troubleshooting on Xenial and upward. (Xenial being the release where ZFS has been first introduced in Ubuntu.) [Test Case] #1) Have ZFS installed and configured - https://wiki.ubuntu.com/Kernel/Reference/ZFS #2) Have sosreport installed and configured $ sudo apt-get update $ sudo apt-get install sosreport -y #3) Run sosreport $ /usr/bin/sosreport -a #4) Lookin for a sosreport*.tar.xz file in /tmp - In PATH_TO_SOSREPORT/sos_commands/, there will be no trace of zfs output, cause as of today, there is no ZFS plugin in Ubuntu/Debian nor upstream. [Regression Potential] * No regression * The PR passed all the upstream checks. [Other Info] * Pull Request: https://github.com/sosreport/sos/pull/934 (Closed #934 via 922ea54) * Commit : https://github.com/sosreport/sos/commit/922ea54bf4f9cb488f72a75a180e5351169dd710 [Original Description] I did a PR to upstream sosreport in order to include the ZFS plugin for Ubuntu/Debian. PR: https://github.com/sosreport/sos/pull/934 Commit : https://github.com/sosreport/sos/commit/922ea54bf4f9cb488f72a75a180e5351169dd710 The ZFS plugin is collecting ZFS informations using the following commands : "zfs get all" "zfs list -t all -o space" "zpool list" "zpool status -x" It would be great to have this ZFS plugin available for Xenial (where ZFS has been first introduce in Ubuntu) and upward (Zesty, ...) - Eric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1666239/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1686648] Re: linux-raspi2: 4.4.0-1055.62 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru- testing/raspi2/4.4.0-1055.62/raspi2-4.4-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1686648 Title: linux-raspi2: 4.4.0-1055.62 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686645 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686648/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1686649] Re: linux-snapdragon: 4.4.0-1058.62 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1686649 Title: linux-snapdragon: 4.4.0-1058.62 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686645 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686649/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1580272] Re: i915-bpo crashes on external hdmi input
This is properly fixed since v4.8.6, but the i915_bpo backport in xenial just needs the warning silenced as requested. ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1580272 Title: i915-bpo crashes on external hdmi input Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Bug description: This issue happens when plugging in an external HDMI projector in mirrored mode. To reproduce this issue: 1) Plug in external HDMI monitor 2) Set mirrored displays 3) Unplug HDMI 4) check dmesg for warnings -- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 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 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 4296 F pulseaudio Date: Tue May 10 10:25:07 2016 InstallationDate: Installed on 2016-05-02 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 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. RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux 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/linux/+bug/1580272/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp