[Desktop-packages] [Bug 2056732] Re: [BPO] libreoffice 7.6.5 for jammy
** Changed in: libreoffice (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2056732 Title: [BPO] libreoffice 7.6.5 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Released Bug description: [Impact] * LibreOffice 7.6.5 is in its fifth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.5_release * This source packages matches the proposed SRU for mantic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2054111 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/4:7.6.5-0ubuntu0.23.10.1 * Backport target is Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1816/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/15842337/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/amd64/libr/libreoffice/20240229_200220_48eab@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/arm64/libr/libreoffice/20240229_181801_5e256@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/armhf/libr/libreoffice/20240301_025519_366e5@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/ppc64el/libr/libreoffice/20240229_213818_54822@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/s390x/libr/libreoffice/20240301_070812_5c91c@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2056732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056732] Re: [BPO] libreoffice 7.6.5 for jammy
** Changed in: libreoffice (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2056732 Title: [BPO] libreoffice 7.6.5 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Committed Bug description: [Impact] * LibreOffice 7.6.5 is in its fifth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.5_release * This source packages matches the proposed SRU for mantic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2054111 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/4:7.6.5-0ubuntu0.23.10.1 * Backport target is Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1816/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/15842337/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/amd64/libr/libreoffice/20240229_200220_48eab@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/arm64/libr/libreoffice/20240229_181801_5e256@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/armhf/libr/libreoffice/20240301_025519_366e5@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/ppc64el/libr/libreoffice/20240229_213818_54822@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/s390x/libr/libreoffice/20240301_070812_5c91c@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2056732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046150] Re: [BPO] libreoffice 7.5.9 for jammy
** Changed in: libreoffice (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2046150 Title: [BPO] libreoffice 7.5.9 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Released Bug description: [Impact] * LibreOffice 7.5.9 is in its ninth and last bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.9_release * This source packages matches the proposed SRU for lunar handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2044369 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/4:7.5.9-0ubuntu0.23.04.1 * Backport target is Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1776/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/15416837/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20231208_123108_1b879@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/arm64/libr/libreoffice/20231208_175608_c3b14@/log.gz * [armhf] ... (autopkgtests infra problems on this arch) * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/ppc64el/libr/libreoffice/20231208_135706_f6680@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/s390x/libr/libreoffice/20231208_150850_45529@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2046150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046150] Re: [BPO] libreoffice 7.5.9 for jammy
approved, very sorry for the long delay. ** Changed in: libreoffice (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2046150 Title: [BPO] libreoffice 7.5.9 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Committed Bug description: [Impact] * LibreOffice 7.5.9 is in its ninth and last bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.9_release * This source packages matches the proposed SRU for lunar handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2044369 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/4:7.5.9-0ubuntu0.23.04.1 * Backport target is Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1776/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/15416837/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20231208_123108_1b879@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/arm64/libr/libreoffice/20231208_175608_c3b14@/log.gz * [armhf] ... (autopkgtests infra problems on this arch) * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/ppc64el/libr/libreoffice/20231208_135706_f6680@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/s390x/libr/libreoffice/20231208_150850_45529@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2046150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018714] Re: [BPO] libreoffice 7.4.7 for bionic, focal and jammy
** Changed in: libreoffice (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: libreoffice (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: libreoffice (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2018714 Title: [BPO] libreoffice 7.4.7 for bionic, focal and jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: Fix Committed Status in libreoffice source package in Focal: Fix Committed Status in libreoffice source package in Jammy: Fix Committed Bug description: [Impact] * LibreOffice 7.4.7 is in its seventh bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.7_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2018600 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.7-0ubuntu0.22.10.1 * Backport targets are the Bionic/18.04, Focal/20.04 and Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1827/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Bionic/18.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14738812/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/amd64/libr/libreoffice/20230509_091428_b3633@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/arm64/libr/libreoffice/20230510_174443_fea7f@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/armhf/libr/libreoffice/20230509_113953_615bf@/log.gz * [i386l] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/i386/libr/libreoffice/20230509_111407_9f2bc@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/ppc64el/libr/libreoffice/20230509_110221_c7d8a@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/s390x/libr/libreoffice/20230311_013952_49140@/log.gz Focal/20.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14738813/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/20230508_165949_20fb6@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/20230508_213248_aef40@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/armhf/libr/libreoffice/20230508_193232_364c7@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/ppc64el/libr/libreoffice/20230508_173145_777fc@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/s390x/libr/libreoffice/20230510_092544_49ed4@/log.gz Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14738814/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20230508_203244_68a30@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/arm64/libr/libreoffice/20230508_201428_74484@/log.gz * [armhf]
[Desktop-packages] [Bug 2009944] Re: [BPO] libreoffice 7.4.6 for bionic, focal and jammy
Wow someone got crazy with the epoch, jumping from 1 to 4! Wonder what happened there... (not relevant to this backport, just surprising ;-) It LGTM, but the backport-from is still in kinetic-proposed (from lp: 2009354), so we need to wait for that to migrate into kinetic-updates first. Also for the backport to bionic, just keep in mind that after the bionic repo closes (in a month-ish), we won't be able to backport to it, so this might be the last version in bionic-backports. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2009944 Title: [BPO] libreoffice 7.4.6 for bionic, focal and jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: In Progress Status in libreoffice source package in Focal: In Progress Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.4.6 is in its sixth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.6_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2009354 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently released in bionic-/focal-backports [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.6-0ubuntu0.22.10.1 * Backport targets are the Bionic/18.04, Focal/20.04 and Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1717/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Bionic/18.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541804/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/amd64/libr/libreoffice/20230311_021721_5528d@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/arm64/libr/libreoffice/20230311_022133_e8482@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/armhf/libr/libreoffice/20230311_034543_5547f@/log.gz * [i386l] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/i386/libr/libreoffice/20230311_024716_6fc50@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/ppc64el/libr/libreoffice/20230311_013201_6dbb2@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/s390x/libr/libreoffice/20230311_013952_49140@/log.gz Focal/20.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541807/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/20230311_001616_c1e3a@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/20230310_164346_4ac1d@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/armhf/libr/libreoffice/20230311_052748_8b7c3@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/ppc64el/libr/libreoffice/20230310_151809_05c21@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/s390x/libr/libreoffice/20230310_190707_a5b67@/log.gz Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541810/+listing-archive-extra * [amd64]
[Desktop-packages] [Bug 2002941] Re: [BPO] libreoffice 7.4.4 for jammy
The s390 build seems completely broken, most likely due to no fault of the libreoffice package; the infrastructure seems to be broken, as it repeatedly fails to build and also fails to produce any build log. @ricotz do you want to mark this as fix-released since the other archs are completed and published? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2002941 Title: [BPO] libreoffice 7.4.4 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Committed Bug description: [Impact] * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2001911 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently released in jammy. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.4-0ubuntu0.22.10.1 * Backport target is Jammy/22.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1542/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+sourcepub/14441833/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/amd64/libr/libreoffice/20230117_121308_55f21@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/arm64/libr/libreoffice/20230117_004531_c08ab@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/armhf/libr/libreoffice/20230117_192827_df4b4@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/ppc64el/libr/libreoffice/20230116_230929_28cc3@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/s390x/libr/libreoffice/20230117_034834_09f33@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2002941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002941] Re: [BPO] libreoffice 7.4.4 for jammy
** Changed in: libreoffice (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2002941 Title: [BPO] libreoffice 7.4.4 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Committed Bug description: [Impact] * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2001911 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently released in jammy. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.4-0ubuntu0.22.10.1 * Backport target is Jammy/22.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1542/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+sourcepub/14441833/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/amd64/libr/libreoffice/20230117_121308_55f21@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/arm64/libr/libreoffice/20230117_004531_c08ab@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/armhf/libr/libreoffice/20230117_192827_df4b4@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/ppc64el/libr/libreoffice/20230116_230929_28cc3@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/s390x/libr/libreoffice/20230117_034834_09f33@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2002941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1996076] Re: [BPO] libreoffice 7.3.7 for focal
** Changed in: libreoffice (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1996076 Title: [BPO] libreoffice 7.3.7 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Committed Bug description: [Impact] * LibreOffice 7.3.7 is in its seventh bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.7_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995054 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.3.6 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1989418 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.6 is currently released in focal-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.7-0ubuntu0.22.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/20221109_131732_0f324@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/20221109_134252_403d2@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/armhf/libr/libreoffice/20221109_152925_85c50@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/ppc64el/libr/libreoffice/20221109_134511_07b38@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/s390x/libr/libreoffice/20221109_125147_0715b@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 28 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1996082] Re: [BPO] libreoffice 7.3.7 for bionic
** Changed in: libreoffice (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1996082 Title: [BPO] libreoffice 7.3.7 for bionic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: Fix Committed Bug description: [Impact] * LibreOffice 7.3.7 is in its seventh bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.7_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995054 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.3.6 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990382 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.6 is currently released in bionic-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.7-0ubuntu0.22.04.1 * Backport target is Bionic/18.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/amd64/libr/libreoffice/20221109_194619_aafcb@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/arm64/libr/libreoffice/20221109_182935_ad523@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/armhf/libr/libreoffice/20221109_193157_bfaf9@/log.gz * [i386] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/i386/libr/libreoffice/20221110_005928_4e278@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/ppc64el/libr/libreoffice/20221109_191816_d9338@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/s390x/libr/libreoffice/20221109_173606_13453@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 28 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990382] Re: [BPO] libreoffice 7.3.6 for bionic
** Changed in: libreoffice (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1990382 Title: [BPO] libreoffice 7.3.6 for bionic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: Fix Committed Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * This source packages matches the processed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744 and a test build is currently available at https://launchpad.net/~libreoffice/+archive/ubuntu/experimental/+packages * Similar backport of 7.3.6 for focal handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1989418 * LibreOffice 6.0.7 (EOL since November 26, 2018) is currently released in bionic. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.6-0ubuntu0.22.04.1 * Backport target is Bionci/18.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1900/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/amd64/libr/libreoffice/20220921_023821_f6636@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/arm64/libr/libreoffice/20220921_015824_12ef6@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/armhf/libr/libreoffice/20220922_104328_3c444@/log.gz * [i386] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/i386/libr/libreoffice/20220921_150152_8877b@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/ppc64el/libr/libreoffice/20220921_140441_6e26b@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/s390x/libr/libreoffice/20220921_134627_506c7@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987045] Re: [BPO] libreoffice 7.3.5 for focal
** Changed in: libreoffice (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1987045 Title: [BPO] libreoffice 7.3.5 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Committed Bug description: [Impact] * LibreOffice 7.3.5 is in its fifth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.5_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1981966 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * Previous backport of 7.2.7 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1973594 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.2.7 (EOL since June 12, 2022) is currently released in focal-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.5-0ubuntu0.22.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1797/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-ppa/focal/amd64/libr/libreoffice/20220819_142247_194f7@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-ppa/focal/arm64/libr/libreoffice/20220819_165236_1d317@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-ppa/focal/armhf/libr/libreoffice/20220819_173744_60f42@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-ppa/focal/ppc64el/libr/libreoffice/20220819_152216_4dc5e@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-ppa/focal/s390x/libr/libreoffice/20220819_143225_3bdea@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 83 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1987045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973594] Re: [BPO] libreoffice 7.2.7 for focal
This is released now for focal-backports, except for arm64/armhf, which appear to be having quite a hard time keeping up with builds, as they currently haven't even started: https://launchpad.net/ubuntu/+source/libreoffice/1:7.2.7-0ubuntu0.21.10.1~bpo20.04.1 I'm marking this fix released for focal, but if you notice the arm builds fail, please add a comment and I'll take a look at them. ** Changed in: libreoffice (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1973594 Title: [BPO] libreoffice 7.2.7 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Released Bug description: [Impact] * LibreOffice 7.2.7 is in its seventh (and last) bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.7_release * This source packages matches the proposed SRU for impish handled at https://bugs.launchpad.net/ubuntu/impish/+source/libreoffice/+bug/1972155 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.2.6 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969808 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.2.7-0ubuntu0.21.10.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_72/1617/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/amd64/libr/libreoffice/20220518_095601_b5724@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/arm64/libr/libreoffice/20220518_133315_9e5cd@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/armhf/libr/libreoffice/20220518_135411_142bf@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/ppc64el/libr/libreoffice/20220518_143359_edb75@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/s390x/libr/libreoffice/20220518_095423_36802@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 44+ bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1973594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973594] Re: [BPO] libreoffice 7.2.7 for focal
** Changed in: libreoffice (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1973594 Title: [BPO] libreoffice 7.2.7 for focal Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Focal: Fix Committed Bug description: [Impact] * LibreOffice 7.2.7 is in its seventh (and last) bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.7_release * This source packages matches the proposed SRU for impish handled at https://bugs.launchpad.net/ubuntu/impish/+source/libreoffice/+bug/1972155 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.2.6 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969808 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.2.7-0ubuntu0.21.10.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_72/1617/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/amd64/libr/libreoffice/20220518_095601_b5724@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/arm64/libr/libreoffice/20220518_133315_9e5cd@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/armhf/libr/libreoffice/20220518_135411_142bf@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/ppc64el/libr/libreoffice/20220518_143359_edb75@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/s390x/libr/libreoffice/20220518_095423_36802@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 44+ bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1973594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969808] Re: [BPO] libreoffice 7.2.6 for focal
** Changed in: libreoffice (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1969808 Title: [BPO] libreoffice 7.2.6 for focal Status in libreoffice package in Ubuntu: Invalid Status in libreoffice source package in Focal: Fix Released Bug description: [Impact] * LibreOffice 7.2.6 is in its sixth bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.6_release * This source packages matches the proposed SRU for impish handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1963279 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.1.7 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1950467 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.2.6-0ubuntu0.21.10.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_72/1492/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/amd64/libr/libreoffice/20220423_095928_4657f@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/arm64/libr/libreoffice/20220422_233357_f3dd5@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/armhf/libr/libreoffice/20220422_225947_92a7f@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/ppc64el/libr/libreoffice/20220422_210622_9aba9@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/s390x/libr/libreoffice/20220422_204258_093fc@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 52 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969808] Re: [BPO] libreoffice 7.2.6 for focal
** Changed in: libreoffice (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1969808 Title: [BPO] libreoffice 7.2.6 for focal Status in libreoffice package in Ubuntu: Invalid Status in libreoffice source package in Focal: Fix Committed Bug description: [Impact] * LibreOffice 7.2.6 is in its sixth bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.6_release * This source packages matches the proposed SRU for impish handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1963279 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.1.7 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1950467 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.2.6-0ubuntu0.21.10.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_72/1492/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/amd64/libr/libreoffice/20220423_095928_4657f@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/arm64/libr/libreoffice/20220422_233357_f3dd5@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/armhf/libr/libreoffice/20220422_225947_92a7f@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/ppc64el/libr/libreoffice/20220422_210622_9aba9@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/s390x/libr/libreoffice/20220422_204258_093fc@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 52 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949970] Re: attempt to dlopen nonexistent pam_kwallet.so spams log
I think we should ignore hirsute since it reaches EOL next week. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1949970 Title: attempt to dlopen nonexistent pam_kwallet.so spams log Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Bionic: New Status in lightdm source package in Focal: Fix Committed Status in lightdm source package in Hirsute: Fix Committed Status in lightdm source package in Impish: Fix Committed Status in lightdm source package in Jammy: Fix Released Bug description: [impact] lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet which died around Trusty (https://launchpad.net/ubuntu/+source/pam- kwallet) while pam_kwallet5.so comes from kwallet-pam which provides only the newer '5' version, not the older unversioned library file. This results in repeated spam error messages in the system log complaining about failure to load pam_kwallet.so [test case] install/enable lightdm and check system log at boot for messages like: Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so [regression potential] any regression would likely cause problems during login and/or missing or extra log messages during pam authentication. [scope] this is needed in all releases [other info] https://github.com/canonical/lightdm/pull/216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1949970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949970] Re: attempt to dlopen nonexistent pam_kwallet.so spams log
ubuntu@lp1949970-i:~$ dpkg -l lightdm|grep lightdm ii lightdm 1.30.0-0ubuntu4 amd64Display Manager ubuntu@lp1949970-i:~$ journalctl -b -g 'unable to dlopen' -- Journal begins at Tue 2022-01-11 17:28:57 UTC, ends at Tue 2022-01-11 17:59:05 UTC. -- Jan 11 17:58:14 lp1949970-i lightdm[939]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Jan 11 17:58:14 lp1949970-i lightdm[939]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory Jan 11 17:58:16 lp1949970-i lightdm[1083]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Jan 11 17:58:16 lp1949970-i lightdm[1083]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory ...(upgrade and reboot)... ubuntu@lp1949970-i:~$ dpkg -l lightdm|grep lightdm ii lightdm1.30.0-0ubuntu4.21.10.1 amd64Display Manager ubuntu@lp1949970-i:~$ journalctl -b -g 'unable to dlopen' -- Journal begins at Tue 2022-01-11 17:28:57 UTC, ends at Tue 2022-01-11 18:01:00 UTC. -- -- No entries -- -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1949970 Title: attempt to dlopen nonexistent pam_kwallet.so spams log Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Bionic: New Status in lightdm source package in Focal: Fix Committed Status in lightdm source package in Hirsute: Fix Committed Status in lightdm source package in Impish: Fix Committed Status in lightdm source package in Jammy: Fix Released Bug description: [impact] lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet which died around Trusty (https://launchpad.net/ubuntu/+source/pam- kwallet) while pam_kwallet5.so comes from kwallet-pam which provides only the newer '5' version, not the older unversioned library file. This results in repeated spam error messages in the system log complaining about failure to load pam_kwallet.so [test case] install/enable lightdm and check system log at boot for messages like: Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so [regression potential] any regression would likely cause problems during login and/or missing or extra log messages during pam authentication. [scope] this is needed in all releases [other info] https://github.com/canonical/lightdm/pull/216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1949970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949970] Re: attempt to dlopen nonexistent pam_kwallet.so spams log
ubuntu@lp1949970-f:~$ dpkg -l lightdm|grep lightdm ii lightdm1.30.0-0ubuntu4~20.04.1 amd64Display Manager ubuntu@lp1949970-f:~$ journalctl -b -g 'unable to dlopen' -- Logs begin at Tue 2022-01-11 17:28:51 UTC, end at Tue 2022-01-11 18:02:33 UTC. -- Jan 11 17:58:09 lp1949970-f lightdm[1048]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Jan 11 17:58:09 lp1949970-f lightdm[1048]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory Jan 11 17:58:11 lp1949970-f lightdm[1278]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Jan 11 17:58:11 lp1949970-f lightdm[1278]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory ...(upgrade and reboot)... ubuntu@lp1949970-f:~$ dpkg -l lightdm|grep lightdm ii lightdm1.30.0-0ubuntu4~20.04.2 amd64Display Manager ubuntu@lp1949970-f:~$ journalctl -b -g 'unable to dlopen' -- Logs begin at Tue 2022-01-11 17:28:51 UTC, end at Tue 2022-01-11 18:03:41 UTC. -- -- No entries -- ** Tags removed: verification-needed verification-needed-focal verification-needed-impish ** Tags added: verification-done verification-done-focal verification-done-impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1949970 Title: attempt to dlopen nonexistent pam_kwallet.so spams log Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Bionic: New Status in lightdm source package in Focal: Fix Committed Status in lightdm source package in Hirsute: Fix Committed Status in lightdm source package in Impish: Fix Committed Status in lightdm source package in Jammy: Fix Released Bug description: [impact] lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet which died around Trusty (https://launchpad.net/ubuntu/+source/pam- kwallet) while pam_kwallet5.so comes from kwallet-pam which provides only the newer '5' version, not the older unversioned library file. This results in repeated spam error messages in the system log complaining about failure to load pam_kwallet.so [test case] install/enable lightdm and check system log at boot for messages like: Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so [regression potential] any regression would likely cause problems during login and/or missing or extra log messages during pam authentication. [scope] this is needed in all releases [other info] https://github.com/canonical/lightdm/pull/216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1949970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950467] Re: [BPO] libreoffice 7.1.7 for focal
Released to focal-backports, thanks! ** Changed in: libreoffice (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1950467 Title: [BPO] libreoffice 7.1.7 for focal Status in libreoffice package in Ubuntu: Invalid Status in libreoffice source package in Focal: Fix Released Bug description: [Impact] * LibreOffice 7.1.7 is in its seventh (and last) bugfix release of the 7.1 line: https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.7_release * This source packages matches the proposed SRU for hirsute handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1948933 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.1.7-0ubuntu0.21.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_71/1460/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/2020_055401_85a70@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/2020_013227_b21ba@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/armhf/libr/libreoffice/2020_015816_7e469@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/ppc64el/libr/libreoffice/2020_002248_216a6@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/s390x/libr/libreoffice/20211109_232224_7b3ab@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 27 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1950467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950467] Re: [BPO] libreoffice 7.1.7 for focal
** Changed in: libreoffice (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1950467 Title: [BPO] libreoffice 7.1.7 for focal Status in libreoffice package in Ubuntu: Invalid Status in libreoffice source package in Focal: Fix Committed Bug description: [Impact] * LibreOffice 7.1.7 is in its seventh (and last) bugfix release of the 7.1 line: https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.7_release * This source packages matches the proposed SRU for hirsute handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1948933 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.1.7-0ubuntu0.21.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_71/1460/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/2020_055401_85a70@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/2020_013227_b21ba@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/armhf/libr/libreoffice/2020_015816_7e469@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/ppc64el/libr/libreoffice/2020_002248_216a6@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/s390x/libr/libreoffice/20211109_232224_7b3ab@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 27 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1950467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950467] Re: [BPO] libreoffice 7.1.7 for focal
> I have updated the patch thanks! and thanks for adding details to the changelog entry as well to clarify the backport changes, and to update the vcs links. > The new requirement to include a "~bpo" string seems a bit unfortunate The current rules would require the version to change as: 1:7.1.7-0ubuntu0.21.04.1 to 1:7.1.7-0ubuntu0.21.04.1~bpo20.04.1 I do think that generally makes sense, even though including both the '21.04.1' and '20.04.1' releases might be at first confusing. Note this does follow the backport version convention used by Debian: https://backports.debian.org/Contribute/#index4h3 The only possible future problem with that versioning I think is if the full 7.1.7 version was, at some point, *fully* SRU'ed back into focal. At that point, the SRU version would usually be a version like 1:7.1.7-0ubuntu0.20.04.1, which would actually be a lower version number than the version in backports. However, I don't think you are planning to do that (right?), and it's also generally not allowed to do using the SRU process. Other than the version number, the backport looks good to me; if you can upload it with the proper version number, I'm happy to approve it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1950467 Title: [BPO] libreoffice 7.1.7 for focal Status in libreoffice package in Ubuntu: Invalid Status in libreoffice source package in Focal: In Progress Bug description: [Impact] * LibreOffice 7.1.7 is in its seventh (and last) bugfix release of the 7.1 line: https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.7_release * This source packages matches the proposed SRU for hirsute handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1948933 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.1.7-0ubuntu0.21.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_71/1460/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/2020_055401_85a70@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/2020_013227_b21ba@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/armhf/libr/libreoffice/2020_015816_7e469@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/ppc64el/libr/libreoffice/2020_002248_216a6@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/s390x/libr/libreoffice/20211109_232224_7b3ab@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 27 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1532052] Re: "no tablet detected" message in system settings for otherwise-working tablet
** Changed in: trusty-backports Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1532052 Title: "no tablet detected" message in system settings for otherwise-working tablet Status in Linux Mint: New Status in trusty-backports: Won't Fix Status in libwacom package in Ubuntu: Fix Released Bug description: The "Graphics Tablet" panel of the System Settings application reports "No tablet detected" for any tablet, despite the tablets actually moving around the mouse cursor and being usable in applications like GIMP. This prevents the graphical configuration of tablet settings. This is with a fresh install of Linux Mint 17.3 'Rosa' (Cinnamon 64-bit). This message appears even for tablets which were able to be configured under 17.2. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1532052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1285783] Re: Right panel has a transparent background
** Changed in: trusty-backports Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1285783 Title: Right panel has a transparent background Status in trusty-backports: Won't Fix Status in gtk+3.0 package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: Launching gnome-tweak-tool and choosing a category on the left panel makes the right panel transparent. To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1285783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 342224] Re: Please backport libmtp 0.3.6 in Hardy
** Changed in: hardy-backports Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/342224 Title: Please backport libmtp 0.3.6 in Hardy Status in Hardy Backports: Won't Fix Status in libmtp package in Ubuntu: Invalid Bug description: Please update libmtp 0.2.6 currently in Hardy as many mtp device don't work with players like Rhythmbox.Thanks,Luca To manage notifications about this bug go to: https://bugs.launchpad.net/hardy-backports/+bug/342224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 304252] Re: Please backport transmission
** Changed in: hardy-backports Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/304252 Title: Please backport transmission Status in Hardy Backports: Won't Fix Status in Intrepid Ibex Backports: Invalid Status in transmission package in Ubuntu: Invalid Bug description: Transmission 1.51 has a large number of new features, usability improvements and bug fixes. It would be nice to provide this for Intrepid and Hardy users, who now have relatively old versions. To manage notifications about this bug go to: https://bugs.launchpad.net/hardy-backports/+bug/304252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 500625] Re: Local file overwriting due to directory traversal
** Changed in: hardy-backports Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/500625 Title: Local file overwriting due to directory traversal Status in Hardy Backports: Won't Fix Status in transmission package in Ubuntu: Fix Released Status in transmission source package in Lucid: Fix Released Status in transmission source package in Hardy: Fix Released Status in transmission source package in Intrepid: Fix Released Status in transmission source package in Jaunty: Fix Released Status in transmission source package in Karmic: Fix Released Bug description: Binary package hint: transmission I've discovered a design flaw in the Transmission BitTorrent client that I would consider to be a security vulnerability. The Transmission client permits arbitrary characters in the names of files included in torrents, including characters that allow directory traversal (such as "../"). In addition, the client does not prompt the user before overwriting existing files with the same name as a file that is to be downloaded via torrent. An attacker can create a malicious torrent file containing a file named specifically to overwrite important files on disk. For example, "../.ssh/authorized_keys" could be provided as a filename included in a torrent, and Transmission will download the provided file and store it at that location (assuming the default download location of ~/Desktop), overwriting the preexisting keys file and potentially giving an attacker SSH access to the victim's machine. If the user happens to be running Transmission as root (who knows?), the possibilities are even scarier. I have confirmed this behavior with a simple proof-of-concept torrent and text file, which I've attached. To confirm behavior, download the EVIL text file (which is just a sentence of text), and open the attached .torrent file in a child directory. For example, if EVIL is in "~/", open the .torrent from "~/Desktop". The torrent should begin seeding. From another machine, create a blank file (or any file, really) called EVIL at some location. This file represents an existing file on disk, and presumably wouldn't be called "EVIL" in a real situation. Note its contents, and open the .torrent file at a child directory, just as before. Once the download starts, you should note that the EVIL file in the parent directory has been overwritten with the contents of the torrent's EVIL file. Clearly, the desired behavior is to download files into the current directory, not permitting any directory traversal, and perhaps prompting the user before overwriting existing data. This could be easily fixed by stripping ".." from incoming file names. Although this attack requires a victim to open a malicious torrent file, because it does not require the victim to actually execute malicious code I would still consider it a security problem. Torrents are very widespread, and it would be trivial to host a malicious torrent containing legitimate files alongside files designed to compromise a victim's system. The fact that an attacker would have immediate knowledge of compromised victims via the torrent is especially dangerous. I confirmed this behavior in Transmission 1.75 on Karmic, using both the GTK interface and transmission-cli. To manage notifications about this bug go to: https://bugs.launchpad.net/hardy-backports/+bug/500625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 792301] Re: Ericsson F5521gw 3G module for Lenovo not using optimal kernel module
** Changed in: lucid-backports Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/792301 Title: Ericsson F5521gw 3G module for Lenovo not using optimal kernel module Status in Lucid Backports: Won't Fix Status in ModemManager: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: Binary package hint: modemmanager The Ericsson F5521gw 3G module should use the usb_ncm kernel module (/dev/usb0) for connecting for optimal speed and CPU usage (important for HSPA+ connections). Modemmanager needs to be told this for the usb ID 0bdb:1911 (currently only 0bdb:190d supported). See the attached patch already in current version of modemmanager: http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=0b757465ffe6108066d32312ab4e895c372c8f72 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: modemmanager 0.4+git.20110124t203624.00b6cce-2ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic-pae 2.6.38.4 Uname: Linux 2.6.38-9-generic-pae i686 Architecture: i386 Date: Fri Jun 3 12:41:25 2011 ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, user) LANG=nb_NO.UTF-8 SHELL=/bin/bash SourcePackage: modemmanager UpgradeStatus: Upgraded to natty on 2011-04-29 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lucid-backports/+bug/792301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 865907] Re: Please backport tracker to Oneiric
** Changed in: oneiric-backports Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/865907 Title: Please backport tracker to Oneiric Status in Oneiric Backports: Won't Fix Status in tracker package in Ubuntu: Invalid Bug description: Tracker 0.12 is the latest stable release of GNOME's search engine. It is needed for GNOME Documents. I've tested version 12.6-1 by letting it index my home directory and I ran some searches. The indexed documents showed up in GNOME Documents as they were supposed to. Build log: https://launchpadlibrarian.net/81619551/buildlog_ubuntu- oneiric-amd64.tracker_0.12.3-1~ppa1_BUILDING.txt.gz Tracker 0.12 has been in the GNOME 3 PPA for a month now (since October 5). I've been running it on my computer for a month and I've not seen a single complaint about it not working. https://launchpad.net/~gnome3-team/+archive/gnome3/+builds?build_text=tracker_state=all To manage notifications about this bug go to: https://bugs.launchpad.net/oneiric-backports/+bug/865907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked
** Changed in: xenial-backports Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1003950 Title: launcher does not show minimized update manager while clicked Status in Compiz: New Status in Nouveau Xorg driver: New Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity 6.0 series: Fix Released Status in Xenial Backports: Won't Fix Status in binary-driver-fglrx package in Ubuntu: New Status in intel-linux-graphics-installer package in Ubuntu: New Status in unity package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in binary-driver-fglrx source package in Precise: Won't Fix Status in intel-linux-graphics-installer source package in Precise: Won't Fix Status in unity source package in Precise: Fix Released Status in update-manager source package in Precise: Won't Fix Status in xserver-xorg-video-nouveau source package in Precise: Won't Fix Status in binary-driver-fglrx source package in Quantal: Invalid Status in intel-linux-graphics-installer source package in Quantal: Invalid Status in unity source package in Quantal: Fix Released Status in update-manager source package in Quantal: Won't Fix Status in xserver-xorg-video-nouveau source package in Quantal: Invalid Bug description: Found an easy way to reproduce it during brussels sprint: 1. start deja-dup or update-manager 2. kill -9 compiz; metacity 3. compiz --replace === Update manager is showing up in the dock but I can click on the icon all day and nothing happens. Similarly if I do Super-S or Super-W it doesn't show up anywhere. Even if I alt-tab to the application nothing shows up. This happens only when update manager runs on its own. If I kill it and then launch it myself it comes to the foreground just fine. I'm not 100% sure whether this is a unity, compiz, or update-manager bug but so far my bet is on unity. =Original Report= Bug #877444 is showing again in latest updates, please re-open it. This is the exact same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1003950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950467] Re: [BPO] libreoffice 7.1.7 for focal
Hello! > This is meant in addition to > https://bugs.launchpad.net/ubuntu/focal/+source/libreoffice/+bug/192 > not as a replacement. just to reinforce this, the backport definitely shouldn't be relied on as a replacement for proper SRU work, so that bug should definitely continue to be discussed and hopefully the SRU completed. > A recent set of upstream's automated jenkins testing can be found here: ... > Launchpad testing. The libreoffice packages include autopkgtests that were > run and verified as passing. ... > General smoke testing of all the applications in the office suite were > carried out by going through the manual testplan Very good, I think both the upstream tests as well as the autopkgtests for the backported package are important. And for a package like this that's very end-user-focused it's very good to see manual testing as well. I have only 2 concerns with the backport: 1) looking at the debdiff, it seems the backport did require some changes. I'd like to see the specifics of the changes required for the backport at least mentioned in the changelog. Additionally, I have some specific comments on the backport changes: You've made quite a few changes in d/control, to adjust the minimum version of dpkg-dev as well as removing some deps and adding others. For the reduced dpkg-dev min version, where is the corresponding change in code? Why does the newer libreoffice depend on a newer dpkg-dev, but appears to also work fine using the older version? Does the libreoffice in hirsute simply include a dpkg-dev min version that it doesn't actually need? For the removed/added deps, which also have a change in d/rules to compile without (or with) them; I don't think this is necessarily a problem, assuming it really needs to be done for the backport, but it definitely should be listed in the changelog, since removing deps presumably will remove some functionality in the backported version (right?) 2) the specific version of the backported package should include a suffix with 'bpo': https://wiki.ubuntu.com/UbuntuBackports#Preparing_the_Backported_Package This is a new requirement as we just recreated the backports process, so if you were using the 'backportpackage' tool it probably got the version wrong. I rejected the current upload, but if you can reupload with the two concerns above addressed, I don't see any other problems with it. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1950467 Title: [BPO] libreoffice 7.1.7 for focal Status in libreoffice package in Ubuntu: Invalid Status in libreoffice source package in Focal: In Progress Bug description: [Impact] * LibreOffice 7.1.7 is in its seventh (and last) bugfix release of the 7.1 line: https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.7_release * This source packages matches the proposed SRU for hirsute handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1948933 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.1.7-0ubuntu0.21.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_71/1460/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/2020_055401_85a70@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/2020_013227_b21ba@/log.gz * [armhf]
[Desktop-packages] [Bug 1949970] Re: attempt to dlopen nonexistent pam_kwallet.so spams log
** Also affects: lightdm (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu Bionic) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1949970 Title: attempt to dlopen nonexistent pam_kwallet.so spams log Status in lightdm package in Ubuntu: New Status in lightdm source package in Bionic: New Status in lightdm source package in Focal: New Status in lightdm source package in Hirsute: New Status in lightdm source package in Impish: New Status in lightdm source package in Jammy: New Bug description: [impact] lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet which died around Trusty (https://launchpad.net/ubuntu/+source/pam- kwallet) while pam_kwallet5.so comes from kwallet-pam which provides only the newer '5' version, not the older unversioned library file. This results in repeated spam error messages in the system log complaining about failure to load pam_kwallet.so [test case] install/enable lightdm and check system log at boot for messages like: Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so [regression potential] any regression would likely cause problems during login and/or missing or extra log messages during pam authentication. [scope] this is needed in all releases [other info] https://github.com/canonical/lightdm/pull/216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1949970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949970] Re: attempt to dlopen nonexistent pam_kwallet.so spams log
** Description changed: [impact] lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet which died around Trusty (https://launchpad.net/ubuntu/+source/pam- kwallet) while pam_kwallet5.so comes from kwallet-pam which provides only the newer '5' version, not the older unversioned library file. This results in repeated spam error messages in the system log complaining about failure to load pam_kwallet.so [test case] install/enable lightdm and check system log at boot for messages like: Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so [regression potential] any regression would likely cause problems during login and/or missing or extra log messages during pam authentication. [scope] this is needed in all releases + + [other info] + + https://github.com/canonical/lightdm/pull/216 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1949970 Title: attempt to dlopen nonexistent pam_kwallet.so spams log Status in lightdm package in Ubuntu: New Status in lightdm source package in Focal: New Status in lightdm source package in Hirsute: New Status in lightdm source package in Impish: New Status in lightdm source package in Jammy: New Bug description: [impact] lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet which died around Trusty (https://launchpad.net/ubuntu/+source/pam- kwallet) while pam_kwallet5.so comes from kwallet-pam which provides only the newer '5' version, not the older unversioned library file. This results in repeated spam error messages in the system log complaining about failure to load pam_kwallet.so [test case] install/enable lightdm and check system log at boot for messages like: Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so [regression potential] any regression would likely cause problems during login and/or missing or extra log messages during pam authentication. [scope] this is needed in all releases [other info] https://github.com/canonical/lightdm/pull/216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1949970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949970] [NEW] attempt to dlopen nonexistent pam_kwallet.so spams log
Public bug reported: [impact] lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet which died around Trusty (https://launchpad.net/ubuntu/+source/pam- kwallet) while pam_kwallet5.so comes from kwallet-pam which provides only the newer '5' version, not the older unversioned library file. This results in repeated spam error messages in the system log complaining about failure to load pam_kwallet.so [test case] install/enable lightdm and check system log at boot for messages like: Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so [regression potential] any regression would likely cause problems during login and/or missing or extra log messages during pam authentication. [scope] this is needed in all releases ** Affects: lightdm (Ubuntu) Importance: Low Status: New ** Affects: lightdm (Ubuntu Focal) Importance: Low Status: New ** Affects: lightdm (Ubuntu Hirsute) Importance: Low Status: New ** Affects: lightdm (Ubuntu Impish) Importance: Low Status: New ** Affects: lightdm (Ubuntu Jammy) Importance: Low Status: New ** Also affects: lightdm (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu Focal) Importance: Undecided => Low ** Changed in: lightdm (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: lightdm (Ubuntu Impish) Importance: Undecided => Low ** Changed in: lightdm (Ubuntu Jammy) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1949970 Title: attempt to dlopen nonexistent pam_kwallet.so spams log Status in lightdm package in Ubuntu: New Status in lightdm source package in Focal: New Status in lightdm source package in Hirsute: New Status in lightdm source package in Impish: New Status in lightdm source package in Jammy: New Bug description: [impact] lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet which died around Trusty (https://launchpad.net/ubuntu/+source/pam- kwallet) while pam_kwallet5.so comes from kwallet-pam which provides only the newer '5' version, not the older unversioned library file. This results in repeated spam error messages in the system log complaining about failure to load pam_kwallet.so [test case] install/enable lightdm and check system log at boot for messages like: Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so [regression potential] any regression would likely cause problems during login and/or missing or extra log messages during pam authentication. [scope] this is needed in all releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1949970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850775] Re: DNS info is not loaded by dhclient
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1850775 Title: DNS info is not loaded by dhclient Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Hi Team, Could you please help to confirm if this is an issue on Ubuntu19.10 Desktop? 1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines. supersede domain-name "vmware.com"; supersede domain-name-servers 10.117.0.1; 2. Reboot 3. check DNS info by "systemd-resolve --status", the DNS domain and server is not set. But /run/systemd/resolved.conf.d/isc- dhcp-v4-ens160.conf contains the new DNS domain and server. 4. Manually run "systemctl try-reload-or-restart systemd- resolved.service" and then DNS is set correctly, "systemd-resolve --status" output have the new DNS domain and server. I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated correctly after reboot. Thanks, Pengpeng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1864781 Title: System with GeForce GT 520 failed to boot when nvidia-390 was installed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1864781/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889416] Re: pulseaudio.service: Start request repeated too quickly.
** Package changed: systemd (Ubuntu) => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1889416 Title: pulseaudio.service: Start request repeated too quickly. Status in fscrypt package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: PA doesn't start on it's own after the latest update. ``` nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 11min ago TriggeredBy: ● pulseaudio.socket Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal (code=exited, status=1/FAILURE) Main PID: 2774 (code=exited, status=1/FAILURE) Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service. ``` But works after starting it manually. ``` nafallo@wendigo:~$ systemctl --user start pulseaudio nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago TriggeredBy: ● pulseaudio.socket Main PID: 5675 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service... Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nafallo5675 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 15:11:28 2020 InstallationDate: Installed on 2018-06-27 (763 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1889416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812356] Re: AlpsPS/2 ALPS GlidePoint vertical pointer speed is very low
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1812356 Title: AlpsPS/2 ALPS GlidePoint vertical pointer speed is very low Status in libinput package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: https://gitlab.freedesktop.org/libinput/libinput/issues/232 --- While moving pointer (cursor) using Touchpad, vertical movement is very slow and short (= less velocity and less acceleration compared to horizontal axis). Horizontal movement is fine. So, when circle is drawn on the Touchpad, the pointer moves in oval shape. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1168 F pulseaudio /dev/snd/controlC0: user 1168 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jan 18 10:10:35 2019 HibernationDevice: RESUME=UUID=5eb56af0-cec9-43d4-b84a-46d561cecb30 InstallationDate: Installed on 2019-01-13 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80N4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=a791b794-48c2-47fb-b2e6-11085529d9ba ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2016 dmi.bios.vendor: Lenovo dmi.bios.version: BDCN71WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14IBD dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14IBD dmi.modalias: dmi:bvnLenovo:bvrBDCN71WW:bd08/03/2016:svnLENOVO:pn80N4:pvrLenovoYoga500-14IBD:rvnLENOVO:rnLenovoYoga500-14IBD:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14IBD: dmi.product.family: IDEAPAD dmi.product.name: 80N4 dmi.product.version: Lenovo Yoga 500-14IBD dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1812356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1825499 Title: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6] Status in systemd: Fix Released Status in libinput package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in libinput package in Fedora: Won't Fix Bug description: After installing Kubuntu 19.04, I found that vertical sensitivity is much higher than horizontal sensitivity. Installing xserver-xorg-input-synaptics improved the situation a bit and enabled KDE touchpad setting that were disabled. It's very annoying. Laptop: HP Pavilion g6. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Fri Apr 19 12:00:02 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: D4Z91EA#ABV dmi.product.version: 088512005D160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1825499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802375] Re: network printer OKI mc352 not working any more (after update?)
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1802375 Title: network printer OKI mc352 not working any more (after update?) Status in avahi package in Ubuntu: New Status in cups package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: The printer shows up using lpinfo -v: network beh file cups-brf:/ network ipp serial serial:/dev/ttyS0?baud=115200 serial serial:/dev/ttyS4?baud=115200 serial serial:/dev/ttyS5?baud=115200 network lpd network socket network http network https network ipps direct parallel:/dev/lp0 direct parallel:/dev/lp1 direct hp direct hpfax network dnssd://OKI-MC352-26F106._pdl-datastream._tcp.local/ but stays in 'processing' mode forever when I tell it to print the test page. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CupsErrorLog: E [08/Nov/2018:15:21:22 +0100] Unknown directive JobPrivateAccess on line 123 of /etc/cups/cupsd.conf. E [08/Nov/2018:15:21:22 +0100] Unknown directive JobPrivateValues on line 124 of /etc/cups/cupsd.conf. E [08/Nov/2018:15:21:22 +0100] Unknown directive SubscriptionPrivateAccess on line 125 of /etc/cups/cupsd.conf. E [08/Nov/2018:15:21:22 +0100] Unknown directive SubscriptionPrivateValues on line 126 of /etc/cups/cupsd.conf. CurrentDesktop: ubuntu:GNOME Date: Thu Nov 8 20:07:16 2018 InstallationDate: Installed on 2018-06-19 (142 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for OKI-DATA-CORP-MC352: dnssd://OKI-MC352-26F106._pdl-datastream._tcp.local/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/OKI-DATA-CORP-MC352.ppd'] failed with exit code 2: grep: /etc/cups/ppd/OKI-DATA-CORP-MC352.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=UUID=5a33fc23-a448-4980-a91b-fc81d565dc39 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2105 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-V EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2105:bd07/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1802375/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807749] Re: NFS V4 does not mount at system start
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1807749 Title: NFS V4 does not mount at system start Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Bug description: Hi, i'm running a view Ubuntu 18.10 Clients on a Ubuntu 18.04 NFS V4 Server. I'm using Kerberos for user authentication and LDAP for user and group synchronisation. The shares are added to the /etc/fstab on my clients and they should be mounted automatically at system boot. Here is an example line from fstab: nfs.server:/users /home nfs4 sec=krb5i,soft,_netdev,auto 0 0 But after the system has booted and the Login-Screen appears the nfs shares are not mounted on the client. Attached to this bug, you can find an export of my journald entries from my last boot. When I read this log carefully I find the following start order of relevant services: Begin start nss_ldap (from line 822 on) Begin start NetworkManager (from line 1198) Get IP from DHCP (line 2542) NetworkManager Online (line 2551) Try to mount NFS Shares (from line 2253) nss_ldap connected (line 2761) As far as I understand my setup, I do not have DNS before nss_ldap is started. But since mounting the NFS shares needs DNS, the NFS mount sequence should start after nss_ldap is fully started. Thanks for your help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1807749/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
please reopen if this is still an issue for systemd ** Changed in: systemd (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Fix Released Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Status in tilix package in Ubuntu: New Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Incomplete Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734943] Re: no internet access, from any wi-fi network or wired network
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1734943 Title: no internet access, from any wi-fi network or wired network Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: Today, when i started Ubuntu. In bar, on the network icon appear a "?" symbol. I tried to connect Ubuntu to internet with a wired cable and another wi-fi network. He's connect to wi-fi and wired cable network but appears a "?" symbol in the network icon and i don't have access on the internet. Sorry for my bad english :))) Thank you! P.S. i use Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1734943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720976] Re: DNS server in NM static ethernet config fails to configure in systemd-resolved
** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: network-manager (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1720976 Title: DNS server in NM static ethernet config fails to configure in systemd-resolved Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: 1) root@dimension:/home/bp1# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 Codename: artful root@dimension:/home/bp1# 2) systemd: Installed: 234-2ubuntu10 Candidate: 234-2ubuntu10 Version table: *** 234-2ubuntu10 500 500 http://gb.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3) DNS resolution 4) No DNS resolution from my configured DNS (in my case 192.168.1.1) Workarounds: Enable FallbackDNS=8.8.8.8 8.8.4.4 in resolved.conf Or running dhclient Fresh boot of Artful (static IP via network manager and DNS should be at 192.168.1.1): bp1@dimension:~$ ifconfig enp8s0: flags=4163 mtu 1500 inet 192.168.1.5 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::99f:fae5:1467:a576 prefixlen 64 scopeid 0x20 ether 00:1e:4f:e9:f1:c1 txqueuelen 1000 (Ethernet) RX packets 141 bytes 14707 (14.7 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 234 bytes 29807 (29.8 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 16 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 556 bytes 33758 (33.7 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 556 bytes 33758 (33.7 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 bp1@dimension:~$ ping www.dn.se ping: www.dn.se: Name or service not known bp1@dimension:~$ su Password: root@dimension:/home/bp1# systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (enp8s0) Current Scopes: LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no root@dimension:/home/bp1# ping www.dn.se ping: www.dn.se: Name or service not known root@dimension:/home/bp1# nano /etc/systemd/resolved.conf root@dimension:/home/bp1# cat /etc/systemd/resolved.conf # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See resolved.conf(5) for details [Resolve] #DNS= FallbackDNS=8.8.8.8 8.8.4.4 #Domains= #LLMNR=yes #MulticastDNS=yes #DNSSEC=no #Cache=yes #DNSStubListener=udp root@dimension:/home/bp1# ps ax | grep systemd 254 ?Ss 0:00 /lib/systemd/systemd-journald 292 ?Ss 0:00 /lib/systemd/systemd-udevd 573 ?Ssl0:00 /lib/systemd/systemd-timesyncd 585 ?Ss 0:00 /lib/systemd/systemd-networkd 701 ?Ss 0:00 /lib/systemd/systemd-logind 735 ?Ss 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation 844 ?Ss 0:00 /lib/systemd/systemd-resolved
[Desktop-packages] [Bug 1723644] Re: NetworkManager/wicd hang, might be driver issue
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1723644 Title: NetworkManager/wicd hang, might be driver issue Status in linux package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Bug description: Recently I had issues with NetworkManager. When I try to restart or close NetworkManager, the process hangs. First it sends a SIGTERM to the NetworkManager process, and after a while it sends SIGKILL, yet nothing happens. After the attempt to restart/close NetworkManager, the OS behaves badly: - journalctl doesn't work, doesn't output anything, SIGTERMing/SIGABRTing/ SIGKILLing it causes the kill command to hang (no matter how many times I try it), it also hangs the terminal - 'sudo dmesg' hangs (killing it with SIGKILL/SIGTERM/SIGABRT hangs the kill command, can't close the terminal) - the OS won't reboot/suspend/shutdown (it does only after holding the restart button) Suspending/rebooting normally/shutdowning normally the laptop hangs the OS (because of NetworkManager). What I've tried: - reinstalling NetworkManager (uninstalling it using --purge, installing it clean) - deleting ~/.config - deleting ~/.cache - installing a version from NetworkManager from Debian (version: 1.8.4.2), reinstalling NetworkManager from Ubuntu back affects ubuntu affects ubuntu/network-manager affects ubuntu/systemd --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1259 F pulseaudio DistroRelease: Ubuntu 17.10 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-15 (1 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) IpRoute: default via 192.168.100.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.100.0/24 dev wlp3s0 proto kernel scope link src 192.168.100.6 metric 600 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57f3 Realtek Semiconductor Corp. Bus 001 Device 002: ID 0489:e0a3 Foxconn / Hon Hai Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G Package: systemd PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=1df26300-dc4d-42b3-bf5f-0c77c8df7667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 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.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/21/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.29 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.29 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.29:bd07/21/2017:svnAcer:pnAspireE5-575G:pvrV1.29:rvnAcer:rnIronman_SK:rvrV1.29:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.version: V1.29 dmi.sys.vendor: Acer nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0wifi connected/org/freedesktop/NetworkManager/Devices/3 Bojescu 2278c0fb-6947-469e-a8fc-7bbbafb10cf2 /org/freedesktop/NetworkManager/ActiveConnection/1 enp4s0f1 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage
[Desktop-packages] [Bug 1730082] Re: 17.10 Shutdown Delayed 10 Min Due To Wifi
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1730082 Title: 17.10 Shutdown Delayed 10 Min Due To Wifi Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: Won't Fix Bug description: My Lenovo G50 laptop takes roughly 10 min to shut down, due to the wifi. After turning off the "automatically connect" option, shutdown occurs normally. I have found the following processes to have caused the delay: WPA supplicant Network manager Raise network interfaces I hope this can be resolved soon! Thankyou. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1730082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1628868] Re: init.d scripts loop between cups and plymouth
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1628868 Title: init.d scripts loop between cups and plymouth Status in cups package in Ubuntu: Invalid Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Bug description: Устанавливал Kodi. После этого попытался его обновить. И при обновлении ошибки сыплются. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Sep 29 11:17:56 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-09-10 (18 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 80HW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd Title: package udev 229-4ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B6CN16WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G70-70 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G70-70 dmi.modalias: dmi:bvnLENOVO:bvrB6CN16WW:bd07/20/2015:svnLENOVO:pn80HW:pvrLenovoG70-70:rvnLENOVO:rnLenovoG70-70:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG70-70: dmi.product.name: 80HW dmi.product.version: Lenovo G70-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1628868/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699360] Re: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1699360 Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in debconf package in Ubuntu: Confirmed Status in gnome-software package in Ubuntu: Confirmed Status in pam package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Bug description: this all ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libpam-systemd:amd64 232-21ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed Jun 21 00:45:00 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-19 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1699360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713226] Re: systemd-networkd messes up networking
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1713226 Title: systemd-networkd messes up networking Status in ifupdown package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in nplan package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Bug description: Since systemd-234-2ubuntu8 systemd-networkd is enabled by default. This causes problems existing configurations ex1: if the network has ipv6 enables (the host recieves a router advertisement), networkmanager does not configure the network anymore so you get only ipv6 and no ipv4 connections (since systemd-networkd seems to bring only the link up) ex2: if you use systemd-nspawn and configured static ip addresses in /etc/network/interfaces, systemd-networkd adds a dhcp obtained address on the host0 adapter and a 169.254 address For the average user both is not expected, so my solution was systemctl disable systemd-networkd, but since you seem to insist having this enabled, it must be made sure systemd-networkd does not touch existing configurations. My suggestion is: 1) if /etc/network/interfaces contains anything other than lo -> do not enable systemd-networkd 2) if network-manager is enabled, systemd-networkd must be disabled and vice versa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1713226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1676977] Re: Login prompt never presented with ldap login and ldapi set with a name.
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1676977 Title: Login prompt never presented with ldap login and ldapi set with a name. Status in accountsservice package in Ubuntu: New Status in libpam-ldap package in Ubuntu: New Status in systemd package in Ubuntu: Won't Fix Bug description: I have a ldap login configuration that has worked with several Ubuntu versions. Unfortunately it doesn't work with 16.10. If I left my ldapi setting using a name as I used to, the login prompt never appears. If I change the ldapi setting to the IP of the authentication server, the login works perfectly. The authentication server name resolution works fine on 16.10 (after login) and on previous version even during login. It seems to me my problem is related to some ordering issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libpam-ldap 184-8.7ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-44.47-generic 4.8.17 Uname: Linux 4.8.0-44-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Tue Mar 28 14:33:27 2017 InstallationDate: Installed on 2017-03-27 (1 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: libpam-ldap UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1676977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685484] Re: DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1685484 Title: DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Status in systemd package in Debian: Fix Released Bug description: I think it's regression for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1578663 in zesty. 1. NTP servers are send via DHCP and seen by NM: $ nmcli con show connection1 | grep ntp DHCP4.OPTION[30]: requested_ntp_servers = 1 DHCP4.OPTION[31]: ntp_servers = 80.50.231.226 217.96.29.26 212.160.106.226 2. timesyncd is using hardcoded default NTP server: $ systemctl -n 200 status systemd-timesyncd.service * systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-timesyncd.service.d `-disable-with-time-daemon.conf Active: active (running) since Sat 2017-04-22 13:12:23 CEST; 16min ago Docs: man:systemd-timesyncd.service(8) Main PID: 576 (systemd-timesyn) Status: "Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com)." Tasks: 2 (limit: 4915) Memory: 1.5M CPU: 20ms CGroup: /system.slice/systemd-timesyncd.service `-576 /lib/systemd/systemd-timesyncd Apr 22 13:12:23 slodki systemd[1]: Starting Network Time Synchronization... Apr 22 13:12:23 slodki systemd[1]: Started Network Time Synchronization. Apr 22 13:12:53 slodki systemd-timesyncd[576]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). 3. There are not other time sync deamons installed: $ cat /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [Unit] # don't run timesyncd if we have another NTP daemon installed ConditionFileIsExecutable=!/usr/sbin/ntpd ConditionFileIsExecutable=!/usr/sbin/openntpd ConditionFileIsExecutable=!/usr/sbin/chronyd ConditionFileIsExecutable=!/usr/sbin/VBoxService $ ls -l /usr/sbin/{ntpd,openntpd,chronyd,VBoxService} ls: cannot access '/usr/sbin/ntpd': No such file or directory ls: cannot access '/usr/sbin/openntpd': No such file or directory ls: cannot access '/usr/sbin/chronyd': No such file or directory ls: cannot access '/usr/sbin/VBoxService': No such file or directory 4. There is only one default timesyncd.conf file with default values: $ sudo find / -iname \*timesync\* /etc/systemd/timesyncd.conf /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service /etc/dhcp/dhclient-exit-hooks.d/timesyncd /usr/share/man/man5/timesyncd.conf.d.5.gz /usr/share/man/man5/timesyncd.conf.5.gz /usr/share/man/man8/systemd-timesyncd.8.gz /usr/share/man/man8/systemd-timesyncd.service.8.gz /tmp/systemd-private-d029f63116924e99b9fc44caf622e299-systemd-timesyncd.service-6NwdRT /lib/systemd/systemd-timesyncd /lib/systemd/system/systemd-timesyncd.service /lib/systemd/system/systemd-timesyncd.service.d /var/tmp/systemd-private-d029f63116924e99b9fc44caf622e299-systemd-timesyncd.service-jz0q47 $ cat /etc/systemd/timesyncd.conf # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See timesyncd.conf(5) for details. [Time] #NTP= #FallbackNTP=ntp.ubuntu.com 5. DHCP hook installed as /etc/dhcp/dhclient-exit-hooks.d/timesyncd is not working, TIMESYNCD_CONF=/run/systemd/timesyncd.conf.d/01-dhclient.conf is not created. 6. After manually executing steps from hook all works as expected: $ sudo mkdir -p /run/systemd/timesyncd.conf.d/ $ sudo cat [Time] > NTP=80.50.231.226 217.96.29.26 212.160.106.226 > EOF $ sudo systemctl try-restart systemd-timesyncd.service $ sudo systemctl status systemd-timesyncd.service * systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-timesyncd.service.d `-disable-with-time-daemon.conf Active: active (running) since Sat 2017-04-22 13:47:28 CEST; 2min 6s ago Docs: man:systemd-timesyncd.service(8) Main PID: 3094
[Desktop-packages] [Bug 1554662] Re: First client to invoke Xorg via systemd socket activation gets stuck
** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1554662 Title: First client to invoke Xorg via systemd socket activation gets stuck Status in systemd package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: New Bug description: Briefly: if one has a pair of systemd .socket/.service unit files to start Xorg via socket activation, the first X11 client which triggers this socket activation gets stuck (waits forever) , although Xorg starts properly. A second X11 client will then work as expected. For more details, see these upstream bug reports: https://bugs.freedesktop.org/show_bug.cgi?id=93072 https://github.com/systemd/systemd/issues/2765 I've tested Xorg socket activation in Ubuntu 15.10 and 16.04 beta1, as well as openSUSE Leap 42.1 and Tumbleweed. Both Ubuntu releases are affected by this bug, but both openSUSE releases are immune to it. Thus I presume this is a Debian/Ubuntu specific issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1554662/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: systemd (Ubuntu) Status: Invalid => Won't Fix ** Changed in: systemd (Ubuntu) Status: Won't Fix => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in pm-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1574120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1577885] Re: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1577885 Title: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi) Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04 with no issue. I prepare for mounting with the following entry in /etc/fstab my Synology NAS : //192.168.178.61/data /media/server/server_data cifs users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev 0 After login to unity, I mount it with a bash-script (mount -a) which is called from ~/.config/autostart/myMounts.desktop Doing this, and shuting down or rebooting lead into a very delayed shutdown (round about 2 minutes) Pressing ESC Key, showed that the process stops at the command "umount /media/server ..." I have not tested if this also occurs when I am connected via ethernet. I think it is because the (Wifi)Network is already disabled prior all umounts are done. This issue happens even if I type in a shutdown command into a Terminal or if I choose shutdown form the menue, also if I use the power-button. Failure can be avoided if I umount the network-drives manually previouse to reboot. Interim solution was, to create an alias for "shutdown" like "sh /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1577885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1324183] Re: [enhancement] FD passing for unity-system-compositor
** Changed in: systemd (Ubuntu) Status: Triaged => Invalid ** Changed in: systemd Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1324183 Title: [enhancement] FD passing for unity-system-compositor Status in Light Display Manager: New Status in systemd: Invalid Status in Unity System Compositor: Triaged Status in lightdm package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Status in unity-system-compositor package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: Here's the global bug for FD passing from unity-system-compositor to unity8 rather than having a socket file. The general flow would be: *) LightDM gets a client socket from USC *) LightDM sends that fd to logind as a part of the session description (instead of X server number) *) unity8 pulls the fd from logind on startup This then needs an apparmour profile so that dbus denies access to the system-compositor fd from everything that's not unity. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1324183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931301] Re: NIC unavailable after suspend to RAM
> Trying to ifconfig it down/up results in: > SIOCSIFFLAGS: No such device that likely means the kernel driver had some problem waking the device back up, but there's no dmesg attached to the bug so i don't know. This is probably a bug in the 'alx' kernel driver (or, problem with the hardware), not network-manager. ** Package changed: network-manager (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1931301 Title: NIC unavailable after suspend to RAM Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933188] Re: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned
you seem to have some problem with /usr/bin/deb-systemd-invoke, which is a perl script, but it seems to be getting called by /bin/sh. You should try reinstalling init-system-helpers to fix any problem with your script, and/or if you made any changes yourself manually that may be causing the problem. $ sudo apt --reinstall install init-system-helpers ** Package changed: fprintd (Ubuntu) => init-system-helpers (Ubuntu) ** Changed in: init-system-helpers (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1933188 Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post- installation script subprocess returned error exit status 2 Status in init-system-helpers package in Ubuntu: Incomplete Bug description: Got this problem when doing a regular "Update/upgrade" from shell /usr/bin/deb-systemd-invoke: 32 =head1: not found /usr/bin/deb-systemd-invoke: 39: Syntax error: newline unexpected Endless loop of these two lines in bash before the crash. June 22 sentout uopdate ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.4.0-74.83-lowlatency 5.4.114 Uname: Linux 5.4.0-74-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: alsa-ucm-conf:amd64: Install libpam-fprintd:amd64: Install fprintd:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 22 06:52:05 2021 ErrorMessage: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2021-03-29 (84 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: fprintd Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1933188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933188] Re: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned
** Package changed: systemd (Ubuntu) => fprintd (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1933188 Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post- installation script subprocess returned error exit status 2 Status in fprintd package in Ubuntu: New Bug description: Got this problem when doing a regular "Update/upgrade" from shell /usr/bin/deb-systemd-invoke: 32 =head1: not found /usr/bin/deb-systemd-invoke: 39: Syntax error: newline unexpected Endless loop of these two lines in bash before the crash. June 22 sentout uopdate ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.4.0-74.83-lowlatency 5.4.114 Uname: Linux 5.4.0-74-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: alsa-ucm-conf:amd64: Install libpam-fprintd:amd64: Install fprintd:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 22 06:52:05 2021 ErrorMessage: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2021-03-29 (84 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: fprintd Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1933188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)
> Actual results: > * CapsLock key switches on CapsLock LED, the LED state indicates current > CapsLock key function > > Expected results: > * CapsLock LED is always off the 'actual results' sounds like correct behavior to me...? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1925141 Title: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1) Status in kbd-chooser: Unknown Status in kbd package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press key, enter some letters in capitals 5. Press key again, enter some letters in lowercase Actual results: * CapsLock key switches on CapsLock LED, the LED state indicates current CapsLock key function Expected results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803993] Re: Password appears on the VT1 screen
Unfortunately I can't reproduce this bug, even with the 0.9.3-1ubuntu7.18.04.1 version of plymouth installed, so I can't say for sure that it's fixed with plymouth 0.9.3-1ubuntu7.18.04.2. Also note that the [test case] in the description is wrong, that would be correct with the systemd change made earlier, but that change was reverted upstream and in ubuntu, so the test case steps aren't an accurate indication that the bug is fixed or not. Anyone on this bug able to reproduce the main problem, of key output (e.g. passwords) being printed on the console and visible between login sessions, and/or during shutdown? If not, I think we should consider this bug fixed. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: plymouth (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1803993 Title: Password appears on the VT1 screen Status in gdm3 package in Ubuntu: Invalid Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Bug description: [Impact] * The keyboard on the graphical login screen started on VT1 may stop working and or keypresses including passwords are leaked to the terminal console running 'behind' the graphical login screen or environment. [Test Case] * Reboot after installing the fixed systemd package. * Install sysdig * Start sysdig on a remote connection or on a terminal console: $ sudo sysdig evt.type=ioctl | grep request=4B4 * While sysdig is running log in and out 3 times in GDM and press a few keys in the graphical session to see if keyboard still works * Log in and out on an other terminal console, too, running a few commands while being logged in to ensure that keyboard is working. * Observe that on terminal consoles the monitored keyboard setter ioctl is called with argument=3, but where the graphical screen is active only argument=4 is used, unlike with the buggy version observed in https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/comments/14 [Regression Potential] * The fix checks the current keyboard mode of the VT and allows only safe mode switches. The potential regression could be not allowing a valid mode switch keeping a keyboard in a non-operational mode. Testing covers that by typing the keyboard. (continued from bug 1767918) This was found when an administrative error made /home directory inaccessible. Any users that tried to login after that, were not able to (which is expected) but their password appears on the VT1 screen. Under normal circumstances, VT1 is not visible. But once the system was sent into this compromised mode, one can press ctrl+alt+F1 and then ctrl+alt+F2 and get a momentary glance at VT1. One can keep toggling between these key combinations in order to make out the password(s) on VT1. As a further test, I wanted to see if a non-super user could cause this condition, and it is in fact possible. As a regular user, I made their own home directory not writable and then removed ~/.config and logged out. Then logged in as that user again, and although that user can't login the system does go into that mode where passwords appear on VT1 and are viewable with the key combinations mentioned herein. Further, any other users that login will see no problem, but when they logon their passwords also appear on VT1 and are viewable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.3 Uname: Linux 4.19.2-041902-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 19 08:32:59 2018 InstallationDate: Installed on 2018-08-25 (85 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
In focal, the 'native systemd unit' log is not present so the only message to check for is the 'legacy directory' message. root@lp1915887-f:~# dpkg -l systemd|grep systemd ii systemd245.4-4ubuntu3.5 amd64system and service manager root@lp1915887-f:~# journalctl -b --grep legacy --no-pager -- Logs begin at Thu 2021-04-01 17:09:33 UTC, end at Thu 2021-04-01 17:11:46 UTC. -- Apr 01 17:09:45 lp1915887-f systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Apr 01 17:09:46 lp1915887-f systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. root@lp1915887-f:~# dpkg -l systemd|grep systemd ii systemd245.4-4ubuntu3.6 amd64system and service manager root@lp1915887-f:~# journalctl -b --grep legacy --no-pager -- Logs begin at Thu 2021-04-01 17:09:33 UTC, end at Thu 2021-04-01 17:16:09 UTC. -- -- No entries -- ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu. https://bugs.launchpad.net/bugs/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Invalid Status in fam package in Ubuntu: Invalid Status in freeradius package in Ubuntu: Invalid Status in ipfm package in Ubuntu: Invalid Status in n2n package in Ubuntu: Invalid Status in pfm package in Ubuntu: Invalid Status in shadowsocks package in Ubuntu: Invalid Status in sysfsutils package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Invalid Status in xl2tpd package in Ubuntu: Invalid Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Status in systemd package in Debian: Fix Released Bug description: [impact] systemd spams journal with log messages [test case] see journalctl output and search for msgs similar to those listed in original description below; specifically messages containing text with "below legacy directory /var/run/" or "lacks a native systemd unit file" [regression potential] any regession would likely result in logs incorrectly not logged when detecting a problem such as lack of native unit file, or using /var/run. [scope] this is needed in f/g this is fixed upstream with commit https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from debian, which is included in 247.3-2 and later so this is fixed in hirsute already (in -proposed package). these log messages aren't present in b or earlier so aren't needed in x/b [original description] systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [
[Desktop-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
In Groovy for 'legacy directory' logs, with /lib/systemd/system/dbus.socket manually edited to use /var/run... path to reproduce error, with current version logs seen e.g.: Apr 01 17:02:34 lp1915887-g systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. with -proposed version, those logs are not present. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu. https://bugs.launchpad.net/bugs/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Invalid Status in fam package in Ubuntu: Invalid Status in freeradius package in Ubuntu: Invalid Status in ipfm package in Ubuntu: Invalid Status in n2n package in Ubuntu: Invalid Status in pfm package in Ubuntu: Invalid Status in shadowsocks package in Ubuntu: Invalid Status in sysfsutils package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Invalid Status in xl2tpd package in Ubuntu: Invalid Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Status in systemd package in Debian: Fix Released Bug description: [impact] systemd spams journal with log messages [test case] see journalctl output and search for msgs similar to those listed in original description below; specifically messages containing text with "below legacy directory /var/run/" or "lacks a native systemd unit file" [regression potential] any regession would likely result in logs incorrectly not logged when detecting a problem such as lack of native unit file, or using /var/run. [scope] this is needed in f/g this is fixed upstream with commit https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from debian, which is included in 247.3-2 and later so this is fixed in hirsute already (in -proposed package). these log messages aren't present in b or earlier so aren't needed in x/b [original description] systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386742] systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386767] systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a native systemd unit file.
[Desktop-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
ubuntu@lp1915887-g:~$ dpkg -l systemd|grep systemd ii systemd246.6-1ubuntu1.2 amd64system and service manager ubuntu@lp1915887-g:~$ /lib/systemd/system-generators/systemd-sysv-generator SysV service '/etc/init.d/grub-common' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. SysV service '/etc/init.d/apport' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. SysV service '/etc/init.d/virtualbox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. SysV service '/etc/init.d/sysfsutils' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. ubuntu@lp1915887-g:~$ dpkg -l systemd|grep systemd ii systemd246.6-1ubuntu1.3 amd64system and service manager ubuntu@lp1915887-g:~$ /lib/systemd/system-generators/systemd-sysv-generator ubuntu@lp1915887-g:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu. https://bugs.launchpad.net/bugs/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Invalid Status in fam package in Ubuntu: Invalid Status in freeradius package in Ubuntu: Invalid Status in ipfm package in Ubuntu: Invalid Status in n2n package in Ubuntu: Invalid Status in pfm package in Ubuntu: Invalid Status in shadowsocks package in Ubuntu: Invalid Status in sysfsutils package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Invalid Status in xl2tpd package in Ubuntu: Invalid Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Status in systemd package in Debian: Fix Released Bug description: [impact] systemd spams journal with log messages [test case] see journalctl output and search for msgs similar to those listed in original description below; specifically messages containing text with "below legacy directory /var/run/" or "lacks a native systemd unit file" [regression potential] any regession would likely result in logs incorrectly not logged when detecting a problem such as lack of native unit file, or using /var/run. [scope] this is needed in f/g this is fixed upstream with commit https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from debian, which is included in 247.3-2 and later so this is fixed in hirsute already (in -proposed package). these log messages aren't present in b or earlier so aren't needed in x/b [original description] systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49
[Desktop-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
** Description changed: [impact] systemd spams journal with log messages [test case] see journalctl output and search for msgs similar to those listed in - original description below + original description below; specifically messages containing text with + "below legacy directory /var/run/" or "lacks a native systemd unit file" [regression potential] any regession would likely result in logs incorrectly not logged when detecting a problem such as lack of native unit file, or using /var/run. [scope] this is needed in f/g this is fixed upstream with commit https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from debian, which is included in 247.3-2 and later so this is fixed in hirsute already (in -proposed package). these log messages aren't present in b or earlier so aren't needed in x/b [original description] systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386742] systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386767] systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.387281] systemd-sysv-generator[9909]: SysV service '/etc/init.d/virtualbox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388931] systemd-sysv-generator[9909]: SysV service '/etc/init.d/sysfsutils' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388955] systemd-sysv-generator[9909]: SysV service '/etc/init.d/apport' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.389412] systemd-sysv-generator[9909]: SysV service '/etc/init.d/freeradius' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. -- You received
[Desktop-packages] [Bug 1896540] Re: Incorrectly specified Touchpad size for Lenovo T490
> Kernel says: x [1266..5678], y [1162..4694] > Touchpad sends: x [1266..5678], y [1161..4694] -^C unless I'm reading that wrong, the kernel reports exactly the same range as the touchpad sends, so there should be no need for the hwdb to carry x/y values overridding the kernel-reported ranges In upstream systemd, this commit was added for your system's touchpad: https://github.com/systemd/systemd/commit/2ceefe45873d0265fb99bc5757593e5bbb2c732b That commit is included in focal. If that isn't working right for you, I'd suggest opening a merge request, or at least a bug, upstream so they can review/accept any further changes, and if accepted we can consider backporting the change. ** Changed in: libinput (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1896540 Title: Incorrectly specified Touchpad size for Lenovo T490 Status in libinput package in Ubuntu: Invalid Status in systemd package in Ubuntu: Incomplete Bug description: The vertical sensitivity of the touchpad on my laptop Lenovo T490 seemed significantly higher than the horizontal sensitivity. After doing some research I found out that the touchpad size is incorrectly listed by the kernel. Touchpad size listed by the kernel: 77x107mm The real size of the touchpad: 68x100mm Description: Ubuntu 20.04.1 LTS Release: 20.04 Systemd version: 245.4-4ubuntu3.2 Output from the touchpad-edge-detector: miroslav@miroslav-ThinkPad-T490:~$ sudo touchpad-edge-detector 68x100 /dev/input/event5 Touchpad SynPS/2 Synaptics TouchPad on /dev/input/event5 Move one finger around the touchpad to detect the actual edges Kernel says: x [1266..5678], y [1162..4694] Touchpad sends: x [1266..5678], y [1161..4694] -^C Touchpad size as listed by the kernel: 77x107mm User-specified touchpad size: 68x100mm Calculated ranges: 4412/3533 Suggested udev rule: # evdev:name:SynPS/2 Synaptics TouchPad:dmi:bvnLENOVO:bvrN2IET75W(1.53):bd08/21/2019:svnLENOVO:pn20N2CTO1WW:pvrThinkPadT490:rvnLENOVO:rn20N2CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:* EVDEV_ABS_00=1266:5678:65 EVDEV_ABS_01=1161:4694:35 EVDEV_ABS_35=1266:5678:65 EVDEV_ABS_36=1161:4694:35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1896540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
** Description changed: + [impact] + + systemd spams journal with log messages + + [test case] + + see journalctl output and search for msgs similar to those listed in + original description below + + [regression potential] + + any regession would likely result in logs incorrectly not logged when + detecting a problem such as lack of native unit file, or using /var/run. + + [scope] + + this is needed in f/g + + this is fixed upstream with commit https://salsa.debian.org/systemd- + team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from + debian, which is included in 247.3-2 and later so this is fixed in + hirsute already (in -proposed package). + + these log messages aren't present in b or earlier so aren't needed in + x/b + + [original description] + systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386742] systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386767] systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.387281] systemd-sysv-generator[9909]: SysV service '/etc/init.d/virtualbox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388931] systemd-sysv-generator[9909]: SysV service '/etc/init.d/sysfsutils' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388955] systemd-sysv-generator[9909]: SysV service '/etc/init.d/apport' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.389412] systemd-sysv-generator[9909]: SysV service '/etc/init.d/freeradius' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu.
[Desktop-packages] [Bug 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
root@lp1880258-b:~# dpkg -l systemd|grep systemd ii systemd237-3ubuntu10.44 amd64system and service manager root@lp1880258-b:~# host jifaslrjfiudrlj.com Host jifaslrjfiudrlj.com not found: 3(NXDOMAIN) root@lp1880258-b:~# journalctl -b -u systemd-resolved | grep NXDOMAIN Mar 09 18:15:29 lp1880258-b systemd-resolved[786]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Mar 09 18:25:51 lp1880258-b systemd-resolved[786]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. (upgrade/reboot) root@lp1880258-b:~# dpkg -l systemd|grep systemd ii systemd237-3ubuntu10.45 amd64system and service manager root@lp1880258-b:~# host jifaslrjfiudrlj.com Host jifaslrjfiudrlj.com not found: 3(NXDOMAIN) root@lp1880258-b:~# journalctl -b -u systemd-resolved | grep NXDOMAIN root@lp1880258-b:~# ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal ** Tags added: verification-done verification-done-bionic verification-done-focal ** Changed in: systemd (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Status in network-manager source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: [impact] systemd-resolved emits a disturbingly large amount of NXDOMAIN log messages that do not actually indicate any real problem [test case] see original description, or look at any log from any recent Ubuntu system, or search google for endless complaints about NXDOMAIN messages logged by Ubuntu [regression potential] any regression would likely be isolated to systemd-resolved handling of a NXDOMAIN response from its upstream nameserver, including possibly failing to resolve a hostname or delays in resolving hostnames [scope] this is needed for all releases; the patch is not upstream, but carried by Ubuntu [original description] I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
fixed in hirsute with: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=299002546ec2d62e7f0dd7d614ba958fc9df83c2 at version 247.3-1ubuntu4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Status in network-manager source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: [impact] systemd-resolved emits a disturbingly large amount of NXDOMAIN log messages that do not actually indicate any real problem [test case] see original description, or look at any log from any recent Ubuntu system, or search google for endless complaints about NXDOMAIN messages logged by Ubuntu [regression potential] any regression would likely be isolated to systemd-resolved handling of a NXDOMAIN response from its upstream nameserver, including possibly failing to resolve a hostname or delays in resolving hostnames [scope] this is needed for all releases; the patch is not upstream, but carried by Ubuntu [original description] I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
root@lp1880258-f:~# dpkg -l systemd|grep systemd ii systemd245.4-4ubuntu3.4 amd64system and service manager root@lp1880258-f:~# host gfjrisldfjrfj.com Host gfjrisldfjrfj.com not found: 3(NXDOMAIN) root@lp1880258-f:~# journalctl -b -u systemd-resolved | grep NXDOMAIN Mar 09 18:15:29 lp1880258-f systemd-resolved[624]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Mar 09 18:24:39 lp1880258-f systemd-resolved[624]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Mar 09 18:24:49 lp1880258-f systemd-resolved[624]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. (upgrade and reboot) root@lp1880258-f:~# dpkg -l systemd|grep systemd ii systemd245.4-4ubuntu3.5 amd64system and service manager root@lp1880258-f:~# host gfjrisldfjrfj.com Host gfjrisldfjrfj.com not found: 3(NXDOMAIN) root@lp1880258-f:~# journalctl -b -u systemd-resolved | grep NXDOMAIN root@lp1880258-f:~# -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Status in network-manager source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: [impact] systemd-resolved emits a disturbingly large amount of NXDOMAIN log messages that do not actually indicate any real problem [test case] see original description, or look at any log from any recent Ubuntu system, or search google for endless complaints about NXDOMAIN messages logged by Ubuntu [regression potential] any regression would likely be isolated to systemd-resolved handling of a NXDOMAIN response from its upstream nameserver, including possibly failing to resolve a hostname or delays in resolving hostnames [scope] this is needed for all releases; the patch is not upstream, but carried by Ubuntu [original description] I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
with -release version of systemd: root@lp1880258-g:~# host afhjisrfljsdirfj.com Host afhjisrfljsdirfj.com not found: 3(NXDOMAIN) root@lp1880258-g:~# journalctl -b -u systemd-resolved --no-pager ... Mar 09 18:07:46 lp1880258-g systemd-resolved[624]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Mar 09 18:09:11 lp1880258-g systemd-resolved[624]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Mar 09 18:09:14 lp1880258-g systemd-resolved[624]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. root@lp1880258-g:~# dpkg -l systemd|grep systemd ii systemd246.6-1ubuntu1.2 amd64system and service manager root@lp1880258-g:~# host afhjisrfljsdirfj.com Host afhjisrfljsdirfj.com not found: 3(NXDOMAIN) root@lp1880258-g:~# host afhjisrfljsdirfj.com Host afhjisrfljsdirfj.com not found: 3(NXDOMAIN) root@lp1880258-g:~# host afhjisrfljsdirfj.com Host afhjisrfljsdirfj.com not found: 3(NXDOMAIN) root@lp1880258-g:~# journalctl -b -u systemd-resolved --no-pager | grep NXDOMAIN root@lp1880258-g:~# ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Status in network-manager source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Committed Bug description: [impact] systemd-resolved emits a disturbingly large amount of NXDOMAIN log messages that do not actually indicate any real problem [test case] see original description, or look at any log from any recent Ubuntu system, or search google for endless complaints about NXDOMAIN messages logged by Ubuntu [regression potential] any regression would likely be isolated to systemd-resolved handling of a NXDOMAIN response from its upstream nameserver, including possibly failing to resolve a hostname or delays in resolving hostnames [scope] this is needed for all releases; the patch is not upstream, but carried by Ubuntu [original description] I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
** Description changed: + [impact] + + systemd-resolved emits a disturbingly large amount of NXDOMAIN log + messages that do not actually indicate any real problem + + [test case] + + see original description, or look at any log from any recent Ubuntu + system, or search google for endless complaints about NXDOMAIN messages + logged by Ubuntu + + [regression potential] + + any regression would likely be isolated to systemd-resolved handling of + a NXDOMAIN response from its upstream nameserver, including possibly + failing to resolve a hostname or delays in resolving hostnames + + [scope] + + this is needed for all releases; the patch is not upstream, but carried + by Ubuntu + + [original description] + I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf - --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf + --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ - [connectivity] + [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. - Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" - => observe the NXDOMAIN noise over a couple few minutes - + => observe the NXDOMAIN noise over a couple few minutes + Now make the hostname absolute with the trailing dot above and run: -systemctl reload NetworkManager + systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" - => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes + => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. ** Also affects: network-manager (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu Hirsute) Importance: Medium Status: Fix Released ** Also affects: systemd (Ubuntu Hirsute) Importance: Wishlist Status: Triaged ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Groovy) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Hirsute) Status: Triaged => Fix Committed ** Changed in: systemd (Ubuntu Groovy) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Groovy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in network-manager source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in network-manager source package in Focal: Confirmed Status in network-manager source package in Groovy: New Status in systemd source package in Groovy: In Progress Status in network-manager source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Committed Bug description: [impact] systemd-resolved emits a disturbingly large amount of NXDOMAIN log messages that do not actually indicate any real problem [test case] see original description, or look at any log from any recent Ubuntu system, or search google for endless complaints about NXDOMAIN messages logged by Ubuntu [regression potential] any regression would likely be isolated to systemd-resolved handling of a NXDOMAIN response from its upstream nameserver, including possibly failing to resolve a hostname or delays in resolving hostnames [scope]
[Desktop-packages] [Bug 1685754] Re: 'systemd --user' unduly forces umask=0022
** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: 'systemd --user' unduly forces umask=0022 Status in gedit: Invalid Status in gnome-session: Invalid Status in GNOME Terminal: Confirmed Status in Nautilus: Invalid Status in systemd: Unknown Status in dbus package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Bionic: Invalid Status in gnome-terminal source package in Bionic: Invalid Status in systemd source package in Bionic: In Progress Bug description: [impact] pam_umask, from /etc/passwd, is not honored in systemd --user instances [test case] on a desktop system, edit /etc/passwd to change the test user entry (e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field (5th field). For example change: ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash to: ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash You may need to reboot for your X session to pick up the change. Then, from the graphical desktop, open a terminal and run: $ gnome-terminal -e sh in the opened terminal, run: $ umask the number shown should be 0007, as set in the passwd file [regression potential] any regression would likely result in an incorrect umask for the user whose passwd entry is modified. [scope] this is needed only for b this is fixed in systemd upstream by commit 5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in v246, so this is fixed in g and later. This commit was also picked up by Debian and included in the v245 release for focal, so this is fixed in focal already. [original description] In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct umask. In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it systematically displays 0007. But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it systematically displays 0022. That is BAD, and is a security issue. Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each '~/.bashrc', add following content : UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)" if [ "$UMASK" ]; then umask "${UMASK#$USER:*,umask=}" fi In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged. Thank you in advance for a quick correction. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 24 08:36:58 2017 InstallationDate: Installed on 2017-03-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685754] Re: 'systemd --user' unduly forces umask=0022
** Description changed: + [impact] + + pam_umask, from /etc/passwd, is not honored in systemd --user instances + + [test case] + + on a desktop system, edit /etc/passwd to change the test user entry + (e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field (5th + field). For example change: + + ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash + + to: + + ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash + + You may need to reboot for your X session to pick up the change. + + Then, from the graphical desktop, open a terminal and run: + + $ gnome-terminal -e sh + + in the opened terminal, run: + + $ umask + + the number shown should be 0007, as set in the passwd file + + [regression potential] + + any regression would likely result in an incorrect umask for the user + whose passwd entry is modified. + + [scope] + + this is needed only for b + + this is fixed in systemd upstream by commit + 5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in + v246, so this is fixed in g and later. This commit was also picked up by + Debian and included in the v245 release for focal, so this is fixed in + focal already. + + [original description] + In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct umask. In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it systematically displays 0007. But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it systematically displays 0022. That is BAD, and is a security issue. - Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each '~/.bashrc', add following content : UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)" if [ "$UMASK" ]; then - umask "${UMASK#$USER:*,umask=}" + umask "${UMASK#$USER:*,umask=}" fi - - In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged. + In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask + unchanged. Thank you in advance for a quick correction. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 24 08:36:58 2017 InstallationDate: Installed on 2017-03-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: 'systemd --user' unduly forces umask=0022 Status in gedit: Invalid Status in gnome-session: Invalid Status in GNOME Terminal: Confirmed Status in Nautilus: Invalid Status in systemd: Unknown Status in dbus package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Bionic: Invalid Status in gnome-terminal source package in Bionic: Invalid Status in systemd source package in Bionic: Confirmed Bug description: [impact] pam_umask, from /etc/passwd, is not honored in systemd --user instances [test case] on a desktop system, edit /etc/passwd to change the test user entry (e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field (5th field). For example change: ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash to: ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash You may need to reboot for your X session to pick up the change. Then, from the graphical desktop, open a terminal and run: $ gnome-terminal -e sh in the opened terminal, run: $ umask the number shown should be 0007, as set in the passwd file [regression potential] any regression would likely result in an incorrect umask for the user whose passwd entry is modified. [scope] this is needed only for b this is fixed in systemd upstream by commit 5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in v246, so this is fixed in g and later. This commit was also picked up by Debian and included in the v245 release for focal, so this is fixed in focal already. [original description] In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct
[Desktop-packages] [Bug 1685754] Re: 'systemd --user' unduly forces umask=0022
> REGRESSION: With systemd 246.6-1ubuntu1 from Ubuntu 20.10 Beta (Groovy Gorilla), the issue had reappeared I just tested with groovy and can't reproduce the issue; umask is correct under gnome-terminal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: 'systemd --user' unduly forces umask=0022 Status in gedit: Invalid Status in gnome-session: Invalid Status in GNOME Terminal: Confirmed Status in Nautilus: Invalid Status in systemd: Unknown Status in dbus package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Bionic: Invalid Status in gnome-terminal source package in Bionic: Invalid Status in systemd source package in Bionic: Confirmed Bug description: In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct umask. In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it systematically displays 0007. But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it systematically displays 0022. That is BAD, and is a security issue. Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each '~/.bashrc', add following content : UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)" if [ "$UMASK" ]; then umask "${UMASK#$USER:*,umask=}" fi In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged. Thank you in advance for a quick correction. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 24 08:36:58 2017 InstallationDate: Installed on 2017-03-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1160048] Re: add-apt-repository won't uncomment a commented-out source
fixed when using add-apt-repository since groovy ** Changed in: software-properties (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1160048 Title: add-apt-repository won't uncomment a commented-out source Status in software-properties package in Ubuntu: Fix Released Bug description: Assume you're frequently testing software, so you add, remove (purge) and re-add PPAs. sudo add-apt-repository ppa:someteam/ppa sudo apt-get uppdate sudo apt-get install someprogram ... time passes and you no longer need that program, or wish to test your system without it .. sudo ppa-purge ppa:someteam/ppa This will remove the ppa by commenting out the "deb ..." line in the sources file in /etc/apt/sources.list.d Later, you need to do more testing of the app or some other app from the same ppa so you re-add it:- sudo add-apt-repository ppa:someteam/ppa However, this does _not_ add the PPA because the line/file already exists, albeit with a # in front of the "deb ...". Some might argue that it is the fault of ppa-purge for commenting the line out. I disagree. I believe ppa-purge _should_ comment out the "deb ..." line because sometimes you want to go back to the file to remind yourself what the ppa was that you got something from, or to just manually re-enable it. Given the single role of add-apt-repository is to add a ppa, I'd conclude it's add-apt-repository which is broken, given it doesn't add one in this common scenario. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: software-properties-common 0.92.17 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 ApportVersion: 2.9.2-0ubuntu4 Architecture: amd64 Date: Mon Mar 25 21:39:42 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-06-29 (269 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to raring on 2013-01-18 (66 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1160048/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1717522] Re: add-apt-repository --remove & software-properties-gtk do not delete PPA files
this has been fixed in g and later. ** Changed in: software-properties (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1717522 Title: add-apt-repository --remove & software-properties-gtk do not delete PPA files Status in software-properties package in Ubuntu: Fix Released Bug description: When removing a ppa with software-properties-gtk or with : `sudo add-apt-repository --remove ppa:xxx/yyy ` it merely empties the file one wants to remove and leaves an empty theuglyppa.list file in `/etc/apt/sources.list.d/` This seem quite illogical to keep such residue especially for newbies who won't know that they should add : `sudo rm /etc/apt/sources.list.d/theuglyppa.list* ` to their cleaning procedure. Could the removal actually remove ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1717522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915840] [NEW] add-apt-repository does not remove URI if dist is different from local dist
Public bug reported: if a configured repository has a 'dist' value different from the local system's codename, add-apt-repository will not remove it. For example, if this line is currently configured: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main It will not be removed with the command: sudo add-apt-repository -r -U http://dl.google.com/linux/chrome/deb/ ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1915840 Title: add-apt-repository does not remove URI if dist is different from local dist Status in software-properties package in Ubuntu: New Bug description: if a configured repository has a 'dist' value different from the local system's codename, add-apt-repository will not remove it. For example, if this line is currently configured: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main It will not be removed with the command: sudo add-apt-repository -r -U http://dl.google.com/linux/chrome/deb/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1915840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915553] [NEW] add-apt-repository won't remove ppa if ppa has been deleted
Public bug reported: If a ppa is added to the system, and then the ppa is deleted, add-apt- repository fails to remove it, e.g.: $ sudo add-apt-repository -r ppa:ubuntu-support-team/add-apt-repository ERROR: ppa 'ubuntu-support-team/add-apt-repository' not found (use --login if private) the script should remove the source.list entry, which can be calculated even if the ppa doesn't exist anymore. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1915553 Title: add-apt-repository won't remove ppa if ppa has been deleted Status in software-properties package in Ubuntu: New Bug description: If a ppa is added to the system, and then the ppa is deleted, add-apt- repository fails to remove it, e.g.: $ sudo add-apt-repository -r ppa:ubuntu-support-team/add-apt-repository ERROR: ppa 'ubuntu-support-team/add-apt-repository' not found (use --login if private) the script should remove the source.list entry, which can be calculated even if the ppa doesn't exist anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1915553/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913601] [NEW] add-apt-repository does not correctly enable sources
Public bug reported: [impact] 'add-apt-repository -s' should enable deb-src for all existing repos, but doesn't [test case] root@sp-g:~# add-apt-repository -sL deb http://archive.ubuntu.com/ubuntu groovy restricted universe multiverse main deb http://archive.ubuntu.com/ubuntu groovy-updates restricted universe multiverse main deb http://archive.ubuntu.com/ubuntu groovy-backports restricted universe multiverse main deb http://security.ubuntu.com/ubuntu groovy-security restricted universe multiverse main root@sp-g:~# add-apt-repository -s Enabling deb-src for all repositories. Press [ENTER] to continue or Ctrl-c to cancel. Enabled: None Enabled: None Enabled: deb-src http://archive.ubuntu.com/ubuntu groovy-backports multiverse universe restricted main Enabled: deb-src http://archive.canonical.com/ubuntu groovy partner Enabled: None Hit:1 http://security.ubuntu.com/ubuntu groovy-security InRelease Get:2 http://security.ubuntu.com/ubuntu groovy-security/universe Sources [6608 B] Hit:3 http://archive.ubuntu.com/ubuntu groovy InRelease Hit:4 http://archive.ubuntu.com/ubuntu groovy-updates InRelease Hit:5 http://archive.ubuntu.com/ubuntu groovy-backports InRelease Get:6 http://archive.ubuntu.com/ubuntu groovy/multiverse Sources [279 kB] Get:7 http://archive.ubuntu.com/ubuntu groovy/universe Sources [16.3 MB] Get:8 http://archive.canonical.com/ubuntu groovy InRelease [11.4 kB] Get:9 http://archive.ubuntu.com/ubuntu groovy-updates/multiverse Sources [3124 B] Get:10 http://archive.ubuntu.com/ubuntu groovy-updates/universe Sources [19.0 kB] Get:11 http://archive.ubuntu.com/ubuntu groovy-backports/universe Sources [2004 B] Get:12 http://archive.canonical.com/ubuntu groovy/partner Sources [720 B] Fetched 16.6 MB in 6s (2884 kB/s) Reading package lists... Done root@sp-g:~# add-apt-repository -sL deb http://archive.ubuntu.com/ubuntu groovy multiverse restricted main universe deb-src http://archive.ubuntu.com/ubuntu groovy multiverse universe deb http://archive.ubuntu.com/ubuntu groovy-updates multiverse restricted main universe deb-src http://archive.ubuntu.com/ubuntu groovy-updates multiverse universe deb http://archive.ubuntu.com/ubuntu groovy-backports multiverse restricted main universe deb-src http://archive.ubuntu.com/ubuntu groovy-backports multiverse restricted main universe deb-src http://archive.canonical.com/ubuntu groovy partner deb http://security.ubuntu.com/ubuntu groovy-security multiverse restricted main universe deb-src http://security.ubuntu.com/ubuntu groovy-security multiverse universe [regression potential] any regression would likely cause add-apt-repository to incorrectly update the apt sources.list and/or sources.list.d file(s), most likely when modifying the deb-src lines [scope] this is needed in g and later the --enable-source parameter in focal and earlier could only be used with a specific repo to be modified, so this is not applicable to f or earlier ** Affects: software-properties (Ubuntu) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: software-properties (Ubuntu Groovy) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: software-properties (Ubuntu Hirsute) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: software-properties (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Groovy) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: software-properties (Ubuntu Hirsute) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: software-properties (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: software-properties (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: software-properties (Ubuntu Hirsute) Status: New => In Progress ** Changed in: software-properties (Ubuntu Groovy) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1913601 Title: add-apt-repository does not correctly enable sources Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Groovy: In Progress Status in software-properties source package in Hirsute: In Progress Bug description: [impact] 'add-apt-repository -s' should enable deb-src for all existing repos, but doesn't [test case] root@sp-g:~# add-apt-repository -sL deb http://archive.ubuntu.com/ubuntu groovy restricted universe multiverse main deb http://archive.ubuntu.com/ubuntu groovy-updates restricted un
[Desktop-packages] [Bug 1855009] Re: autopkgtests all fail on s390x
** Changed in: network-manager (Ubuntu Xenial) Assignee: Dan Streetman (ddstreet) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Released Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
autopkgtests pass for bionic for all archs, except once for i386, for which I opened bug 1902554; the i386 test passed on retry. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Fix Committed Status in util-linux source package in Focal: Confirmed Bug description: [impact] autopkgtests are failing/flaky and prevent other packages from migrating to -updates [test case] check autopkgtest history [regression potential] in regard to the changed test cases, any regression would likely result in either an incorrectly passed test, or an incorrectly failed test. [scope] for systemd, this is needed for x, b, and f. tests in g appear to be mostly stable, but I've opened MR (linked from this bug) to update the tests there as well. i don't plan to update x, as it's reaching ESM in ~6 months, and backporting the test fixes is more work than just a simple code copy, since there are additional differences/changes needed in the older version of systemd (and python3). the failing/flaky tests in x have been like that forever, and people have just retried them; we can keep retrying them until x moves into ESM next year. [original description] Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F
[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
autopkgtests pass for focal for all archs (except i386 which is expected to fail for focal) ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Fix Committed Status in util-linux source package in Focal: Confirmed Bug description: [impact] autopkgtests are failing/flaky and prevent other packages from migrating to -updates [test case] check autopkgtest history [regression potential] in regard to the changed test cases, any regression would likely result in either an incorrectly passed test, or an incorrectly failed test. [scope] for systemd, this is needed for x, b, and f. tests in g appear to be mostly stable, but I've opened MR (linked from this bug) to update the tests there as well. i don't plan to update x, as it's reaching ESM in ~6 months, and backporting the test fixes is more work than just a simple code copy, since there are additional differences/changes needed in the older version of systemd (and python3). the failing/flaky tests in x have been like that forever, and people have just retried them; we can keep retrying them until x moves into ESM next year. [original description] Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind
[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
ble success rates. ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Description changed: [impact] autopkgtests are failing/flaky and prevent other packages from migrating to -updates [test case] - check systemd autopkgtest history + check autopkgtest history [regression potential] in regard to the changed test cases, any regression would likely result in either an incorrectly passed test, or an incorrectly failed test. [scope] - this is needed for x, b, and f. + for systemd, this is needed for x, b, and f. tests in g appear to be mostly stable, but I've opened MR (linked from this bug) to update the tests there as well. i don't plan to update x, as it's reaching ESM in ~6 months, and backporting the test fixes is more work than just a simple code copy, since there are additional differences/changes needed in the older version of systemd (and python3). the failing/flaky tests in x have been like that forever, and people have just retried them; we can keep retrying them until x moves into ESM next year. [original description] Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until
[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
** Merge proposal linked: https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/392373 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: In Progress Status in util-linux source package in Focal: Confirmed Bug description: [impact] autopkgtests are failing/flaky and prevent other packages from migrating to -updates [test case] check autopkgtest history [regression potential] in regard to the changed test cases, any regression would likely result in either an incorrectly passed test, or an incorrectly failed test. [scope] for systemd, this is needed for x, b, and f. tests in g appear to be mostly stable, but I've opened MR (linked from this bug) to update the tests there as well. i don't plan to update x, as it's reaching ESM in ~6 months, and backporting the test fixes is more work than just a simple code copy, since there are additional differences/changes needed in the older version of systemd (and python3). the failing/flaky tests in x have been like that forever, and people have just retried them; we can keep retrying them until x moves into ESM next year. [original description] Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/)
[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
ok, very sorry for my delay in looking at this. a quick scan of the results for x/b/f show: ddstreet@smaug:~$ autopkgtest-manager --distro systemd -a all -r xenial -cv --since 2month --minimum 6 parsed '2month' as '2020-08-09T14:53:00.893145-04:00' 88: boot-smoke FAIL non-zero exit status 1 (amd64:87 arm64:1) 39: systemd-fsckdFAIL non-zero exit status 1 (amd64:39) 47: boot-and-servicesFAIL non-zero exit status 1 (amd64:41 arm64:6) ddstreet@smaug:~$ autopkgtest-manager --distro systemd -a all -r bionic -cv --since 2month --minimum 6 parsed '2month' as '2020-08-09T14:53:18.194358-04:00' 132: systemd-fsckdFAIL non-zero exit status 1 (i386:14 amd64:117 ppc64el:1) 15: upstream FAIL non-zero exit status 1 (i386:3 amd64:10 ppc64el:1 arm64:1) 29: boot-smoke FAIL non-zero exit status 1 (i386:2 amd64:27) ddstreet@smaug:~$ autopkgtest-manager --distro systemd -a all -r focal -cv --since 2month --minimum 6 parsed '2month' as '2020-08-09T14:56:04.065710-04:00' 96: systemd-fsckdFAIL non-zero exit status 137 (amd64:68 ppc64el:20 s390x:8) 21: systemd-fsckdFAIL non-zero exit status 1 (amd64:1 ppc64el:4 s390x:16) I think the systemd-fsckd failures are issues with how the test is trying to detect 'good' and 'bad' service status, but in any case i rewrote some of the details of how the test works to be simpler and (hopefully) more accurate/reliable, I'm running it through tests from my ppa now, before I upload the test change. I'll take a look at the other test failures; the boot-and-services test has typically had a lot of trouble with services randomly not starting ok, but i'll check on the details. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B
[Desktop-packages] [Bug 1896756] Re: tracker* startup is defined multiple times
** Package changed: systemd (Ubuntu) => tracker (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1896756 Title: tracker* startup is defined multiple times Status in tracker package in Ubuntu: New Bug description: This is about - tracker-miner-fs - tracker-extract - tracker-store Actual Behavior = Their startup is defined in - ${XDG_CONFIG_HOME}/autostart ( more info: https://wiki.archlinux.org/index.php/XDG_Autostart ) - /usr/lib/systemd/user/tracker*.service Expected Behavior === Startup is only defined in one place. Reason: - Managing the software does not get confusing lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Sep 23 20:39:33 2020 MachineType: FUJITSU FMVWB3U27 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro acpi_osi=! "acpi_osi=Windows 2015" pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-07-24 (61 days ago) dmi.bios.date: 01/23/2018 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1896756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration
** Tags added: resolved-resolvconf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pppconfig in Ubuntu. https://bugs.launchpad.net/bugs/1713803 Title: replacement of resolvconf with systemd needs integration Status in android-androresolvd package in Ubuntu: Triaged Status in avahi package in Ubuntu: Triaged Status in bind9 package in Ubuntu: Triaged Status in cloud-init package in Ubuntu: Incomplete Status in cloud-initramfs-tools package in Ubuntu: Invalid Status in dhcpcd5 package in Ubuntu: Confirmed Status in dibbler package in Ubuntu: Won't Fix Status in dnscrypt-proxy package in Ubuntu: Confirmed Status in dnsmasq package in Ubuntu: Invalid Status in dnssec-trigger package in Ubuntu: Invalid Status in fetchmail package in Ubuntu: Confirmed Status in freedombox-setup package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Fix Released Status in ndisc6 package in Ubuntu: Fix Released Status in netscript-2.4 package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: Triaged Status in openvpn package in Ubuntu: Confirmed Status in postfix package in Ubuntu: Invalid Status in pppconfig package in Ubuntu: Confirmed Status in pump package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Invalid Status in sendmail package in Ubuntu: Invalid Status in squid3 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in unbound package in Ubuntu: Triaged Status in vpnc package in Ubuntu: Invalid Status in vpnc-scripts package in Ubuntu: Invalid Status in whereami package in Ubuntu: Triaged Bug description: There is a plan to remove resolvconf from the Ubuntu Server image. resolvconf integrated with other parts of the system in 2 ways: * hooks invoked on change (/etc/resolvconf/update.d/) * resolvconf tool (invoked with -a and -d or -u) Packages which install files into /etc/resolvconf/update.d are: - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns caching path). - resolvconf: This probably isn't necessary in systemd-resolved path. - unbound: This is another "validating, recursive, caching DNS resolver". The list of Depends/Suggests/Recommends on resolvconf. # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show $pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case "$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; Recommends:*) r=recommends;; esac; echo "$r $src"; done | sort -u depends android-androresolvd recommends avahi recommends dhcpcd5 recommends dibbler recommends ndisc6 recommends whereami suggests bind9 suggests dnscrypt-proxy suggests dnsmasq suggests dnssec-trigger suggests fetchmail suggests freedombox-setup suggests isc-dhcp suggests netscript-2.4 suggests openvpn suggests postfix suggests pppconfig suggests pump suggests resolvconf suggests sendmail suggests squid3 suggests vpnc suggests vpnc-scripts ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu9 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 Date: Tue Aug 29 18:53:50 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.vendor: Intel Corporation Related bugs: * bug 1698181: Switch to netplan renderer in Artful * bug 1714308: dns does not work in initramfs after configure_networking * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
hi @cpaelzer, sorry i missed reading this earlier, i'll give all the test failures a look to see what can be done. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are on reasonable success rates. To manage notifications about this bug go to:
[Desktop-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
note there is only one xenial reverse-dep autopkgtest failure, for nfs- utils on s390x, and that test has always failed and can be ignored. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: Fix Committed Status in rpcbind source package in Bionic: Fix Released Status in rpcbind package in Debian: Fix Released Status in Fedora: Confirmed Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, and also adds a check for the existence of an environment variable "RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change the default to remain in place after an upgrade to Focal. Using the environment variable allows anyone to disable the remote calls in x and/or b, and then upgrade to Focal without breaking rpcbind or needing to remove the env var. After the upgrade to Focal, the environment variable (defined in /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored without any change needed to the rpcbind package in Focal or later. [original description] Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
ubuntu@lp304393-x:~$ dpkg -l|grep rpcbind ii rpcbind 0.2.3-0.2ubuntu0.1 amd64converts RPC program numbers into universal addresses ubuntu@lp304393-x:~$ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 *:927 *:* 13471/rpcbind same default behavior after upgrade: ubuntu@lp304393-x:~$ dpkg -l|grep rpcbind ii rpcbind 0.2.3-0.2ubuntu0.16.04.1 amd64converts RPC program numbers into universal addresses ubuntu@lp304393-x:~$ sudo systemctl restart rpcbind ubuntu@lp304393-x:~$ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 *:625 *:* 14441/rpcbind with parameter added, random port disabled: ubuntu@lp304393-x:~$ cat /etc/default/rpcbind RPCBIND_RMTCALL_DEFAULT_DISABLED=1 ubuntu@lp304393-x:~$ sudo systemctl restart rpcbind ubuntu@lp304393-x:~$ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc ubuntu@lp304393-x:~$ with parameter commented, default behavior restored: ubuntu@lp304393-x:~$ cat /etc/default/rpcbind #RPCBIND_RMTCALL_DEFAULT_DISABLED=1 ubuntu@lp304393-x:~$ sudo systemctl restart rpcbind ubuntu@lp304393-x:~$ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 *:660 *:* 14476/rpcbind ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: Fix Committed Status in rpcbind source package in Bionic: Fix Released Status in rpcbind package in Debian: Fix Released Status in Fedora: Confirmed Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, and also adds a check for the existence of an environment variable "RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change the default to
[Desktop-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
bionic verification: ubuntu@lp304393-b:~$ dpkg -l|grep rpcbind ii rpcbind 0.2.3-0.6 amd64 converts RPC program numbers into universal addresses ubuntu@lp304393-b:~$ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:788 0.0.0.0:* 13332/rpcbind after upgrade, same default behavior: ubuntu@lp304393-b:~$ dpkg -l|grep rpcbind ii rpcbind 0.2.3-0.6ubuntu0.18.04.1amd64 converts RPC program numbers into universal addresses ubuntu@lp304393-b:~$ sudo systemctl restart rpcbind ubuntu@lp304393-b:~$ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:707 0.0.0.0:* 14099/rpcbind with parameter set, random port is disabled: ubuntu@lp304393-b:~$ cat /etc/default/rpcbind RPCBIND_RMTCALL_DEFAULT_DISABLED=1 ubuntu@lp304393-b:~$ sudo systemctl restart rpcbind ubuntu@lp304393-b:~$ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc ubuntu@lp304393-b:~$ with param commented, default behavior restored: ubuntu@lp304393-b:~$ cat /etc/default/rpcbind #RPCBIND_RMTCALL_DEFAULT_DISABLED=1 ubuntu@lp304393-b:~$ sudo systemctl restart rpcbind ubuntu@lp304393-b:~$ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:877 0.0.0.0:* 14269/rpcbind ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: In Progress Status in rpcbind source package in Bionic: Fix Committed Status in rpcbind package in Debian: Fix Released Status in Fedora: Confirmed Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, and also adds a check for the existence of an environment variable "RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change
[Desktop-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
** Description changed: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, - and also adds a check for the existence of an environment variable "RPCBIND_RMTCALLS_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. + and also adds a check for the existence of an environment variable "RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change the default to remain in place after an upgrade to Focal. Using the environment variable, instead of changing or adding the cmdline parameter, allows anyone using the variable to disable the remote calls default to upgrade to Focal without breaking rpcbind. After the upgrade to Focal, the environment variable (defined in /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored without any change needed to the rpcbind package in Focal or later. [original description] As this backports that functionality, it Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. ** Description changed: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo
[Desktop-packages] [Bug 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
> One thing that would help with these confusing NXDOMAIN errors in general the vast, VAST majority of the time you see this message it is actually not a NXDOMAIN error. This is due to a Ubuntu-only patch to systemd to work around some select captive portals that are slightly broken, so in any environment outside the broken captive portals (e.g. public wifi that you have to 'click here to accept terms' before getting internet access - and note that not all captive portals are broken) if you see this NXDOMAIN "error" it is almost always just a normal lookup of a domain that doesn't exist, and the error message is simply wrong (this also slows down dns due to forcing fallback to a lower dns protocol level and retry of the already-failed lookup). To clarify specifically for this bug, the lookup of "connectivity- check.ubuntu.com.your_domain" clearly has nothing to do with any "DNS violation", and the NXDOMAIN returned by the upstream nameserver is the *correct* response - that hostname really, actually doesn't exist. network-manager could work around this problematic Ubuntu-only systemd patch, but the real problem is unquestionably that systemd should not have the Ubuntu-only patch that's causing these messages. Fixing this appropriately (i.e. so that systemd still works with the broken captive portal issue) requires access to one of the broken captive portals, so I haven't been able to work on correctly fixing this lately, but it is something I want to do, so we can get rid of the very unfortunate false NXDOMAIN "error" messages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Triaged Status in network-manager source package in Focal: Confirmed Bug description: I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started
** Tags removed: ddstreet -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1726124 Title: DNS domain search paths not updated when VPN started Status in network-manager package in Ubuntu: Confirmed Status in network-manager-openvpn package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications
[Desktop-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
** Tags added: sts -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: In Progress Status in rpcbind source package in Bionic: In Progress Status in rpcbind package in Debian: Fix Released Status in Fedora: Confirmed Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, and also adds a check for the existence of an environment variable "RPCBIND_RMTCALLS_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change the default to remain in place after an upgrade to Focal. Using the environment variable, instead of changing or adding the cmdline parameter, allows anyone using the variable to disable the remote calls default to upgrade to Focal without breaking rpcbind. After the upgrade to Focal, the environment variable (defined in /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored without any change needed to the rpcbind package in Focal or later. [original description] As this backports that functionality, it Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
** Description changed: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc - udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind + udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] - this adds a method to disable rpcbind from listening to the 'random' - port. any regression would likely prevent rpcbind from starting, or may - cause problems with the interaction between rpcinfo and rpcbind, as - rpcinfo may use the random reserved port in some cases, as detailed in - the Debian bug. + this adds a way to disable rpcbind from listening to the 'random' port. + any regression would likely prevent rpcbind from starting, or may cause + problems with the interaction between rpcinfo and rpcbind, as rpcinfo + may use the random reserved port in some cases, as detailed in the + Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. - TBD: specific method to disable rmtcalls in backport + Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, + and also adds a check for the existence of an environment variable "RPCBIND_RMTCALLS_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. + This allows 1) retaining the existing default behavior of rpcbind in x + and b, while also 2) providing a mechanism to change that default for + anyone who does *not* want remote calls to be enabled, and 3) allowing + the mechanism to change the default to remain in place after an upgrade + to Focal. Using the environment variable, instead of changing or adding + the cmdline parameter, allows anyone using the variable to disable the + remote calls default to upgrade to Focal without breaking rpcbind. After + the upgrade to Focal, the environment variable (defined in + /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored + without any change needed to the rpcbind package in Focal or later. [original description] As this backports that functionality, it Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: In Progress Status in rpcbind source package in Bionic: In Progress Status in rpcbind package in Debian: Fix Released Status in Fedora: Confirmed Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved
[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
** Tags removed: sts-sponsor-volunteer ** Tags added: seg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Won't Fix Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
** Description changed: + [impact] + + rpcbind binds to a 'random' reserved port at startup, which can conflict + with the reserved port number for other applications that actually 'own' + the reserved port number. One example is cups, which uses the reserved + port 631. + + This prevents the actual 'owner' of the reserved port from starting, + since it can't bind to its reserved port. + + Additionally, this can raise alarms from security monitoring software + that does not expect programs to be listening on random reserved ports. + + [test case] + + start rpcbind and check which ports it is listening on, e.g.: + + $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc + udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind + + each time rpcbind is restarted, it will be listening to a different + 'random' port. + + [regression potential] + + this adds a method to disable rpcbind from listening to the 'random' + port. any regression would likely prevent rpcbind from starting, or may + cause problems with the interaction between rpcinfo and rpcbind, as + rpcinfo may use the random reserved port in some cases, as detailed in + the Debian bug. + + [scope] + + This is needed only for Bionic and earlier. + + In Focal and later, and in Debian, rpcbind defaults to not opening the + random reserved port. The admin can use the -r parameter to cause + rpcbind to restore the old behavior of opening the random reserved port. + + [other info] + + Note that the -r parameter is a Debian addition, and the upstream + rpcbind has disabled the random port functionality at build time; there + is no runtime parameter to allow the admin to choose the behavior. + + Also, as discussed in the Debian bug, disabling this rpcbind 'feature' + is known to cause problems for the rpcinfo program, which is why Debian + introduced the -r parameter. So, when this -r parameter is backported to + Bionic and earlier, we must retain the default behavior for those + releases, which is for rpcbind to open the random reserved port. + + TBD: specific method to disable rmtcalls in backport + + + [original description] + + As this backports that functionality, it + Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. ** Changed in: rpcbind (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: rpcbind (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: rpcbind (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: rpcbind (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: rpcbind (Ubuntu Bionic) Status: New => In Progress ** Changed in: rpcbind (Ubuntu Xenial) Status: New => In Progress ** Changed in: rpcbind (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: In Progress Status in rpcbind source package in Bionic: In Progress Status in rpcbind package in Debian: Unknown Status in Fedora: Confirmed Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a method to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbi
[Desktop-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
** Also affects: cups (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: rpcbind (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: rpcbind (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cups (Ubuntu) Status: Confirmed => Invalid ** No longer affects: cups (Ubuntu Xenial) ** No longer affects: cups (Ubuntu Bionic) ** Bug watch added: Debian Bug tracker #939890 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939890 ** Also affects: rpcbind (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939890 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: New Status in rpcbind source package in Xenial: New Status in rpcbind source package in Bionic: New Status in rpcbind package in Debian: Unknown Status in Fedora: Confirmed Bug description: Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Whew, this is a long bug. So given comment 40 indicating part of this bug has been fixed in bug 1828639, and comment 42 indicating the any remaining patches should be sent to debian, it seems to me that the ubuntu-sponsors team does not need to be subscribed to this, as it's unclear what parts, if any of the attached patches still apply. Unsubscribing ubuntu-sponsors. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp