[Group.of.nepali.translators] [Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
trusty and xenial receive bug updates via Pro and not via the main archive anymore, you'll have to get SEG to add bug tasks for Pro and prepare +esm updates with them. ** Changed in: e2fsprogs (Ubuntu Trusty) Status: In Progress => Won't Fix ** Changed in: e2fsprogs (Ubuntu Xenial) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: In Progress Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: In Progress Status in e2fsprogs source package in Focal: In Progress Status in e2fsprogs source package in Jammy: In Progress Status in e2fsprogs source package in Lunar: In Progress Status in e2fsprogs source package in Mantic: In Progress Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1953610] [NEW] cnf-update-db creates unreadable database if wrong umask
Public bug reported: [Impact] If a non-default umask is set for the root user, then the database created by cnf-update-db is not readable by users. This fix ensures databases are created with the correct permissions, but it does not automatically reset permissions for broken databases. [Test plan] The umask changes have little regression potential, are tested in a smoke test, and there is a larger test suite that ensures it does not regress other bits (which again, it really shouldn't) [Where problems could occur] We could have the wrong umask? Admins actually liked c-n-f to crash on them? ** Affects: command-not-found (Ubuntu) Importance: Undecided Status: Fix Committed ** Affects: command-not-found (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: command-not-found (Ubuntu Focal) Importance: Undecided Status: New ** Affects: command-not-found (Ubuntu Impish) Importance: Undecided Status: New ** Affects: command-not-found (Ubuntu Jammy) Importance: Undecided Status: Fix Committed ** Changed in: command-not-found (Ubuntu) Status: New => Fix Committed ** Also affects: command-not-found (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: command-not-found (Ubuntu Jammy) Importance: Undecided Status: Fix Committed ** Also affects: command-not-found (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: command-not-found (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: command-not-found (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: command-not-found (Ubuntu Xenial) ** Description changed: [Impact] If a non-default umask is set for the root user, then the database created by cnf-update-db is not readable by users. + + This fix ensures databases are created with the correct permissions, but + it does not automatically reset permissions for broken databases. [Test plan] The umask changes have little regression potential, are tested in a smoke test, and there is a larger test suite that ensures it does not regress other bits (which again, it really shouldn't) [Where problems could occur] We could have the wrong umask? Admins actually liked c-n-f to crash on them? -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1953610 Title: cnf-update-db creates unreadable database if wrong umask Status in command-not-found package in Ubuntu: Fix Committed Status in command-not-found source package in Bionic: New Status in command-not-found source package in Focal: New Status in command-not-found source package in Impish: New Status in command-not-found source package in Jammy: Fix Committed Bug description: [Impact] If a non-default umask is set for the root user, then the database created by cnf-update-db is not readable by users. This fix ensures databases are created with the correct permissions, but it does not automatically reset permissions for broken databases. [Test plan] The umask changes have little regression potential, are tested in a smoke test, and there is a larger test suite that ensures it does not regress other bits (which again, it really shouldn't) [Where problems could occur] We could have the wrong umask? Admins actually liked c-n-f to crash on them? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1953610/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1937115] Re: Unable to boot/install Impish daily in UEFI boot mode
** Also affects: shim (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: shim-signed (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cd-boot-images-amd64 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: shim (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: shim-signed (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: cd-boot-images-amd64 (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1937115 Title: Unable to boot/install Impish daily in UEFI boot mode Status in OEM Priority Project: Confirmed Status in cd-boot-images-amd64 package in Ubuntu: Fix Released Status in shim package in Ubuntu: Fix Released Status in shim-signed package in Ubuntu: Fix Released Status in cd-boot-images-amd64 source package in Xenial: New Status in shim source package in Xenial: New Status in shim-signed source package in Xenial: New Status in cd-boot-images-amd64 source package in Bionic: New Status in shim source package in Bionic: New Status in shim-signed source package in Bionic: New Status in shim source package in Focal: Fix Released Status in shim-signed source package in Focal: Fix Released Status in cd-boot-images-amd64 source package in Impish: Fix Released Status in shim source package in Impish: Fix Released Status in shim-signed source package in Impish: Fix Released Bug description: [Impact] Removable media fail to boot on some machines due to garbage in firmware generated boot entries. This is a regression from LP: #1929471 introduced in shim 15.4-0ubuntu7. In addition we also cherry-pick https://github.com/rhboot/shim/pull/365 to fix a potential buffer overflow. In addition we also cherry-pick https://github.com/rhboot/shim/pull/396 to fix possible firmware corruption in the fallback loader due to out-of-bounds access to the boot order array. [Test plan] I'm sure someone can test a new daily impish ISO on an affected machine. Verification is not necessary for individual SRU releases. We will also do boot of an installed system, and perform the usual chainloaded netbooting test, prior to uploading. [Regression potential] We'll apply four patches for the main issue: Patches 1/2 (https://github.com/rhboot/shim/pull/393) add a fallback to the default loader (with 2s timeout) if we failed to load any specified loader. This ensures we can always boot our default loader, and hence installed systems, even if there is garbage around. It also adds debugging output for the load option that is being parsed, such that people can debug why it failed. Patches 3 and 4 (https://github.com/rhboot/shim/pull/399) disables parsing load options entirely when booting via the removable media path (boot*.efi). This means that any system where admins generate boot entries like bootx64.efi fwupdx64.efi to load a specific second stage will fail to load that second stage and load grubx64.efi instead. is this a problem in practice? On installed systems, we install \EFI\BOOT\bootx64.efi in addition to \EFI\ubuntu\shimx64.efi, and generate boot loader entries for the latter. The former will always use the fbx64.efi fallback loader to add missing boot loader entries and load grub, hence it doesn't seem to support custom options anyway (you'd have to delete fbx64.efi; and even then - you still have the shimx64.efi binary). On installer media, we do not expect you to specify another second stage loader anyway. It's arguably only problematic there, as those could be read-only and hence you can't rename the binary to shimx64.efi. For the overflow, the fix is trivially correct. For the fallback loader, the fix is reasonably trivial; regression potential there could be failure to add a boot entry which is not super critical. [Original bug report] Testing Ubuntu Impish daily ISO= http://cdimage.ubuntu.com/daily-live/20210721/impish-desktop-amd64.iso The test machines are: 1. Dell [ Optiplex] MT 7040 i7-6700 booting in UEFI mode 2. Dell [ Optiplex] MT 7060, i7-8700 booting in UEFI+secure boot mode Boot from USB media fails with the message: Failed to open /EFI/boot/? invalid parameter No further info available To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1937115/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1931136] Re: Don't unhook ExitBootServices() when EBS protection is disabled
** Changed in: shim-signed (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1931136 Title: Don't unhook ExitBootServices() when EBS protection is disabled Status in shim package in Ubuntu: Fix Released Status in shim-signed package in Ubuntu: Fix Released Status in shim source package in Xenial: Fix Committed Status in shim source package in Focal: Fix Committed Status in shim-signed source package in Focal: Fix Committed Status in shim source package in Hirsute: Fix Committed Bug description: [Impact] This is a regression in shim 15.4 that causes a crash in shim when chainbooting. Also, the machine resets when you exit grub, rather than going back to the EFI shell when launched from it. [Test plan] Boot an Ubuntu hirsute image in Secure Boot mode. While this issue was originally seen while chainbooting in https://github.com/lxc/lxd/issues/8770 - it was shown to be also reproducible just by booting a hirsute instance. [Where problems could occur] In exiting shim, failure to boot, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1931136/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1562733] Re: apt signature requirements prevent updates from some repositories
** Changed in: apt (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1562733 Title: apt signature requirements prevent updates from some repositories Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Won't Fix Bug description: Since xenial updated the requirements for the strength of PGP signatures of packages, packages from some repositories are no longer updated. Apt-get update reports these errors: E: Failed to fetch http://[...]/Release No Hash entry in Release file /var/lib/apt/lists/partial/[...] which is considered strong enough for security purposes E: Some index files failed to download. They have been ignored, or old ones used instead. While the motivation for the change is valid, the result is a potential security problem, as the new versions of the packages that may fix recently discovered vulnerabilities are not automatically installed. One less important but unfortunate effect is a scary message that is displayed to the user, without clear explanation that the problem needs to be addressed by the repository owner. Related: Bug #1558331 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1562733/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1926437] [NEW] [SRU] Backport zstd support, fix bug in python-apt
Public bug reported:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if /usr/bin/zstd
does not exist, it will pass "false" as the compressor, and then
ExtractTar fails (same for other compressors).
[Test plan]
The apt regression tests cover the compression methods extensively, including
even stored compressed lists in /var/lib/apt and fetching Packages files
compressed with such methods, for all compression methods.
The final test is to make apt_inst.DebFile("glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
1923845 work in python3-apt.
[Where problems could occur]
APT:
The changes to APT are adding the zstd compression backend to FileFd and
then linking it into the configuration. The former is adding new code,
triggered only on zstd files, and should not be able to cause
regressions.
The latter is a bunch of small lines here and there, and it caused
issues during backporting in the test suite because it expected
compressors in a specific order. However, chances are that nothing else
has as stringent requirements as the test suite, so I don't believe that
is a problem for existing users.
Bugs can of course be in the code dealing with zstd, and that might open
you up to security vulnerabilities in the zstd code if you pass APT zstd
compressed files.
A regression can be if clients used apt-helper cat-file to cat a zstd-
compressed file ending in .zst - they'll now get uncompressed content,
rather than compressed.
python-apt:
The change just replaces Binary with Name, aligning the code with APT
itself, so it's so trivial, we don't expect regressions.
** Affects: apt (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: python-apt (Ubuntu)
Importance: Undecided
Status: New
** Affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Affects: python-apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Affects: python-apt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Affects: python-apt (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: python-apt (Ubuntu Groovy)
Importance: Undecided
Status: New
** Affects: python-apt (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Affects: python-apt (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: python-apt (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: python-apt (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: python-apt (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: python-apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: python-apt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: python-apt (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: python-apt (Ubuntu Focal)
Importance: Undecided
Status: New
** No longer affects: apt (Ubuntu Bionic)
** No longer affects: apt (Ubuntu Focal)
** No longer affects: apt (Ubuntu Groovy)
** No longer affects: apt (Ubuntu Hirsute)
** No longer affects: apt (Ubuntu Impish)
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1926437
Title:
[SRU] Backport zstd support, fix bug in python-apt
Status in apt package in Ubuntu:
Invalid
Status in python-apt package in Ubuntu:
New
Status in apt source package in Xenial:
New
Status in python-apt source package in Xenial:
New
Status in python-apt source package in Bionic:
New
Status in python-apt source package in Focal:
New
Status in python-apt source package in Groovy:
New
Status in python-apt source package in Hirsute:
New
Status in python-apt source package in Impish:
New
Bug description:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if
/usr/bin/zstd does not exist, it will pass "false" as the
[Group.of.nepali.translators] [Bug 1829860] Re: APT unlocks in same order as it locks
** Changed in: apt (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829860 Title: APT unlocks in same order as it locks Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Won't Fix Status in apt source package in Bionic: Fix Released Status in apt source package in Disco: Fix Released Bug description: [Impact] APT releases the locks in the same order it acquires them, rather than reverse order. Given that we have no waiting for locks, this is not _super_ problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, rather than lock-frontend. [Test case] Watch lock release with strace and see that it unlocks the right way. [Regression potential] Some other locking races or something? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829860/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1415701] Re: apt is unable to handle CDROMS with default mount option
** Changed in: apt (Ubuntu Xenial) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1415701 Title: apt is unable to handle CDROMS with default mount option Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Won't Fix Bug description: I have found i am almost completely unable to use CDROM as an apt repository on Ubuntu 14.04 I found the command apt-cdrom add by default, was unable to detect CDROMs it was attempting to find them in /media/cdrom/ by default ubuntu now seems to mount cds in /media/$USER/ and this is not something set via fstab i was able to get them to add with the command apt-cdrom add -m --cdrom /media/$USER/ I seem to have been able to pull the package list from the CD, but when it comes to installing from it, apt encounters a similar error it ask you to insert the disc in drive /media/cdrom/ again I also am completely unable to add cds via the software & updates setting manager, it always fails to find the cd, which is presumably part of the same issue. manually remounting with sudo mount /dev/cdrom /media/cdrom get some things to work, but most of the actions trigger a remount which goes back to the default location I was finally able to get things working again properly by adding the fstab line /dev/cdrom /media/cdrom udf,iso9660 user,noauto,exec,utf8 0 0 resolves the problem for me but this is a work around not a fix, it may break other stuff In apt conf i have tried setting Acquire::cdrom::mount "file/path/"; with various file paths, the file paths, to try and make it work with the default mount behaviour,this looked to be the right setting to change as the message changed accordingly to what i was setting, but i could not get it to work for actually installing packages, even by setting an absolute file path for my user in the media directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1415701/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1589204] Re: apt-get dist-upgrade and apt full-upgrade not reporting held back package
** Changed in: apt (Ubuntu Xenial) Status: Confirmed => Won't Fix ** Changed in: apt (Ubuntu Trusty) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1589204 Title: apt-get dist-upgrade and apt full-upgrade not reporting held back package Status in apt package in Ubuntu: Confirmed Status in apt source package in Trusty: Won't Fix Status in apt source package in Xenial: Won't Fix Bug description: I have the situation where a package cannot be upgraded because of missing dependencies. However sudo apt-get dist-upgrade and sudo apt full-upgrade and sudo apt upgrade all show 0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. Only sudo apt-get upgrade shows 0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade. I believe all of the above commands should show that 1 cannot be upgraded. This bug is not about the particular package I am trying to install, but about the way apt reports the problem. The details, for reference, are that I am trying to upgrade mosquitto from the mosquitto ppa. After apt-get update I see $ apt-cache policy mosquitto mosquitto: Installed: 1.4.8-1build1 Candidate: 1.4.9-0mosquitto1 Version table: 1.4.9-0mosquitto1 500 500 http://ppa.launchpad.net/mosquitto-dev/mosquitto-ppa/ubuntu xenial/main amd64 Packages *** 1.4.8-1build1 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status but if I try to manually install mosquitto I get The following packages have unmet dependencies. mosquitto : Depends: libwebsockets3 (>= 1.2) but it is not installable and $ apt-cache policy libwebsockets3 libwebsockets3: Installed: (none) Candidate: (none) Due to the fact that libwebsockets3 is not available for Xenial. As I said this bug is not about the problem with this particular package but about the fact that apt does not report that there is a package to be upgraded, but it cannot be done. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 5 08:45:33 2016 InstallationDate: Installed on 2014-10-21 (592 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) SourcePackage: apt UpgradeStatus: Upgraded to xenial on 2016-03-06 (90 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1589204/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1615381] Re: apt-get autoremove may remove current kernel
** Also affects: apt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Hirsute) Importance: Undecided Status: Fix Released ** Also affects: unattended-upgrades (Ubuntu Hirsute) Importance: High Status: Fix Released ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: unattended-upgrades (Ubuntu Bionic) ** No longer affects: unattended-upgrades (Ubuntu Focal) ** No longer affects: unattended-upgrades (Ubuntu Groovy) ** No longer affects: unattended-upgrades (Ubuntu Hirsute) ** Changed in: apt (Ubuntu Groovy) Status: New => Confirmed ** Changed in: apt (Ubuntu Groovy) Status: Confirmed => Triaged ** Changed in: apt (Ubuntu Groovy) Status: Triaged => Confirmed ** Changed in: apt (Ubuntu Focal) Status: New => Confirmed ** Changed in: apt (Ubuntu Bionic) Status: New => Confirmed ** Changed in: apt (Ubuntu Groovy) Status: Confirmed => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Confirmed Status in apt source package in Groovy: Triaged Status in apt source package in Hirsute: Fix Released Bug description: [Impact] APT will try and fail to remove the currently running kernel, when booted into an older kernel that is not protected. May wreak some havoc if mixed with other operations to the point that apt goes weird and needs manual fixing up. [Test case] - Install new kernel - Reboot into kernel not listed as protected in 01autoremove-kernels - Run autoremove [Where problems could occur] We may more easily run out of space in /boot. hirsute has new autoremoval code that runs completely at runtime; but that seems a bit large to SRU after only a few weeks in hirsute. Hence, we should protect the current kernel _in addition_ to the other kernels, just like unattended-upgrades and update-manager do. This increases the risk of filling up /boot compared to older apt versions, but is at the same level as unattended-upgrades and update-manager. [Original bug report] This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 16:11:27 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (114 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: apt UpgradeStatus: No
[Group.of.nepali.translators] [Bug 1916050] [NEW] Invalid base64 for high-bit characters
Public bug reported: [Impact] The Base64Encode function incorrectly encodes using char instead of uint8_t, leading to characters with the high bit set to be encoded wrongly. This function is used for base authentication, and high bits are set for UTF-8 character sequences, so it's likely affecting people with utf-8 user names and passwords and might cause them to be denied access to their https resources (though arguably they'd work around that). [Test case] A unit test has been added that checks that the encoding is correct. [Where problems could occur] This only affects the base64 encoding function, which is only used for quoting user names and passwords in basic auth in http, but it's also exposed to library users and like in python-apt, so problems could occur wherever they use that base64 encoding function as well. ** Affects: apt (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: apt (Ubuntu Xenial) Importance: Undecided Status: Confirmed ** Affects: apt (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Affects: apt (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Affects: apt (Ubuntu Groovy) Importance: Undecided Status: Triaged ** Affects: apt (Ubuntu Hirsute) Importance: Undecided Status: Fix Released ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: apt (Ubuntu Groovy) Status: New => Triaged ** Changed in: apt (Ubuntu Focal) Status: New => Confirmed ** Changed in: apt (Ubuntu Groovy) Status: Triaged => Confirmed ** Changed in: apt (Ubuntu Bionic) Status: New => Confirmed ** Changed in: apt (Ubuntu Xenial) Status: New => Confirmed ** Changed in: apt (Ubuntu Groovy) Status: Confirmed => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1916050 Title: Invalid base64 for high-bit characters Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Confirmed Status in apt source package in Groovy: Triaged Status in apt source package in Hirsute: Fix Released Bug description: [Impact] The Base64Encode function incorrectly encodes using char instead of uint8_t, leading to characters with the high bit set to be encoded wrongly. This function is used for base authentication, and high bits are set for UTF-8 character sequences, so it's likely affecting people with utf-8 user names and passwords and might cause them to be denied access to their https resources (though arguably they'd work around that). [Test case] A unit test has been added that checks that the encoding is correct. [Where problems could occur] This only affects the base64 encoding function, which is only used for quoting user names and passwords in basic auth in http, but it's also exposed to library users and like in python-apt, so problems could occur wherever they use that base64 encoding function as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916050/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1831789] Re: Add "dis_ucode_ldr" to linux boot options for Recovery Mode
** Also affects: grubzfs-testsuite (Ubuntu) Importance: Undecided Status: New ** Changed in: grubzfs-testsuite (Ubuntu Groovy) Status: New => Fix Released ** No longer affects: grubzfs-testsuite (Ubuntu Xenial) ** No longer affects: grubzfs-testsuite (Ubuntu Bionic) ** Description changed: [Impact] Due to some recent problems with a microcode update which broke booting of some laptops I suggest adding "dis_ucode_ldr" to recovery mode boot options to allow booting after a bad microcode update. See the following topics that describe the problems: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620 - https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 When such problems occur it's very hard to see that the microcode loading is the issue, the booting just hangs at the purple screen, even removing "quiet splash" or using the recovery option will not show the error. We'll need to double check that dis_ucode_ldr works as expected across all architectures. According to the kernel docs (Documentation/admin-guide/kernel-parameters.txt), dis_ucode_ldr is x86 only, so my guess is that it will be ignored for other architectures. According to the kernel code (arch/x86/kernel/cpu/microcode/core.c), dis_ucode_ldr works for both AMD and Intel. I have some time tomorrow on test this on a ARM device. This was also discussed Ubuntu Developer mailing list where it was suggested to post this here, see: https://lists.ubuntu.com/archives /ubuntu-devel/2019-June/040725.html [Test case] - Check that dis_ucode_ldr is present on Linux entries + Check that dis_ucode_ldr is present on Linux entries (zsys support in focal+ is verified by grubzfs-testsuite changes) [Regression potential] If you actually require microcode updates to get into userspace, your recovery option won't work anymore. Does this happen? Seems unlikely. ** Changed in: grubzfs-testsuite (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1831789 Title: Add "dis_ucode_ldr" to linux boot options for Recovery Mode Status in grub2 package in Ubuntu: Fix Released Status in grubzfs-testsuite package in Ubuntu: Fix Released Status in grub2 source package in Xenial: Fix Committed Status in grub2 source package in Bionic: Fix Committed Status in grub2 source package in Focal: Fix Committed Status in grubzfs-testsuite source package in Focal: In Progress Status in grub2 source package in Groovy: Fix Released Status in grubzfs-testsuite source package in Groovy: Fix Released Bug description: [Impact] Due to some recent problems with a microcode update which broke booting of some laptops I suggest adding "dis_ucode_ldr" to recovery mode boot options to allow booting after a bad microcode update. See the following topics that describe the problems: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620 - https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 When such problems occur it's very hard to see that the microcode loading is the issue, the booting just hangs at the purple screen, even removing "quiet splash" or using the recovery option will not show the error. We'll need to double check that dis_ucode_ldr works as expected across all architectures. According to the kernel docs (Documentation/admin-guide/kernel-parameters.txt), dis_ucode_ldr is x86 only, so my guess is that it will be ignored for other architectures. According to the kernel code (arch/x86/kernel/cpu/microcode/core.c), dis_ucode_ldr works for both AMD and Intel. I have some time tomorrow on test this on a ARM device. This was also discussed Ubuntu Developer mailing list where it was suggested to post this here, see: https://lists.ubuntu.com/archives /ubuntu-devel/2019-June/040725.html [Test case] Check that dis_ucode_ldr is present on Linux entries (zsys support in focal+ is verified by grubzfs-testsuite changes) [Regression potential] If you actually require microcode updates to get into userspace, your recovery option won't work anymore. Does this happen? Seems unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1831789/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1801338] Re: apt fails to properly handle server-side connection closure
I can't reproduce this anymore, so closing it. ** Changed in: apt (Ubuntu) Status: Triaged => Invalid ** Changed in: apt (Ubuntu) Status: Invalid => Incomplete ** Changed in: apt (Ubuntu) Status: Incomplete => Invalid ** Changed in: apt (Ubuntu Xenial) Status: Confirmed => Invalid ** Changed in: apt (Ubuntu Bionic) Status: Triaged => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1801338 Title: apt fails to properly handle server-side connection closure Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: Invalid Status in apt source package in Bionic: Invalid Bug description: [Impact] In some cases, apt does not correctly handle server-side connection closure after a pipeline, and aborts the file being downloaded with an "Undetermined Error" when the connection has been closed. [Test case] This could be seen by running apt build-dep evince on cosmic with a recent apt with the pipelining fix (such as 1.6.6) against a local mirror running apache from trusty. It remains to be seen whether this is easily reproducible for anyone. [Regression potential] N/A yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1882663] Re: Specify flavour ordering
** Changed in: grub2 (Ubuntu Eoan) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1882663 Title: Specify flavour ordering Status in grub2 package in Ubuntu: Fix Committed Status in grub2 source package in Xenial: New Status in grub2 source package in Bionic: New Status in grub2 source package in Eoan: Won't Fix Status in grub2 source package in Focal: New Status in grub2 source package in Groovy: Fix Committed Bug description: [Impact] We need to be able to override the preferred kernel flavour, examples being: - OEM metapackages need to set the kernel flavour to oem, and later to generic (e.g. when transitioning from 6.0-1000-oem to 6.0-1-generic) - FIPS kernels might cause a downgrade compared to an HWE kernel, but if you enable FIPS and reboot, you want to be booting a FIPS kernel [Regression potential] The change affects the ordering of kernels inside grub, hence a regression could be that we end up with the wrong order of kernels. [Test case] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1882663/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1732962] Re: apport uses sys.argv instead of named arguments
** Changed in: apport (Ubuntu Trusty)
Status: New => Fix Committed
** Changed in: apport (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1732962
Title:
apport uses sys.argv instead of named arguments
Status in Apport:
Fix Committed
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Trusty:
Won't Fix
Status in apport source package in Xenial:
New
Status in apport source package in Bionic:
New
Status in apport source package in Cosmic:
Won't Fix
Status in apport source package in Disco:
Fix Released
Bug description:
data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with
some security updates where we were trying to support a new version of
apport on a host system and one inside a container. Here's something
of an example:
347 # Normal startup
348 if len(sys.argv) not in (5, 6):
349 try:
350 print('Usage: %s [global pid]' % sys.argv[0])
351 print('The core dump is read from stdin.')
We could not maintain backwards compatibility because "global pid" is
an optional argument and "dump mode" was a new argument. So if there
were five arguments its possible the last one was "dump mode" (no
global pid) or "global pid" (no support for dump mode).
Its possible to use strings in /proc/sys/kernel/core_pattern so we
could use those and have apport accept named arguments e.g:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport --pid=%p --signal=%s --core-size=%c --dump-mode=%d
--global-pid=%P
['/home/bdmurray/source-trees/apport/artful/data/apport', '--
pid=5870', '--signal=11', '--core-size=0', '--dump-mode=1', '--global-
pid=5870']
Tyler said "that's probably a nice cleanup to make no matter what
because the magic arg ordering is dangerous".
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1732962/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1311056] Re: apt-add-repository adds duplicate commented/disabled source lines
** Also affects: python-apt (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: software-properties (Ubuntu) ** No longer affects: software-properties (Ubuntu Xenial) ** No longer affects: software-properties (Ubuntu Bionic) ** No longer affects: software-properties (Ubuntu Eoan) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1311056 Title: apt-add-repository adds duplicate commented/disabled source lines Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: New Status in python-apt source package in Bionic: New Status in python-apt source package in Eoan: New Bug description: Trusty Tahr 14.04 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d# That deb-src line should have stayed commented out, and not been duplicated. (Commented deb lines should of course be uncommented, as already fixed per https://bugs.launchpad.net/ubuntu/+source/python- apt/+bug/1042916 .) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1311056/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1732962] Re: apport uses sys.argv instead of named arguments
** Changed in: apport (Ubuntu Cosmic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1732962
Title:
apport uses sys.argv instead of named arguments
Status in Apport:
Fix Committed
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Trusty:
New
Status in apport source package in Xenial:
New
Status in apport source package in Bionic:
New
Status in apport source package in Cosmic:
Won't Fix
Status in apport source package in Disco:
Fix Released
Bug description:
data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with
some security updates where we were trying to support a new version of
apport on a host system and one inside a container. Here's something
of an example:
347 # Normal startup
348 if len(sys.argv) not in (5, 6):
349 try:
350 print('Usage: %s [global pid]' % sys.argv[0])
351 print('The core dump is read from stdin.')
We could not maintain backwards compatibility because "global pid" is
an optional argument and "dump mode" was a new argument. So if there
were five arguments its possible the last one was "dump mode" (no
global pid) or "global pid" (no support for dump mode).
Its possible to use strings in /proc/sys/kernel/core_pattern so we
could use those and have apport accept named arguments e.g:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport --pid=%p --signal=%s --core-size=%c --dump-mode=%d
--global-pid=%P
['/home/bdmurray/source-trees/apport/artful/data/apport', '--
pid=5870', '--signal=11', '--core-size=0', '--dump-mode=1', '--global-
pid=5870']
Tyler said "that's probably a nice cleanup to make no matter what
because the magic arg ordering is dangerous".
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1732962/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1801338] Re: apt fails to properly handle server-side connection closure
** No longer affects: apt (Ubuntu Cosmic) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1801338 Title: apt fails to properly handle server-side connection closure Status in apt package in Ubuntu: Triaged Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Triaged Bug description: [Impact] In some cases, apt does not correctly handle server-side connection closure after a pipeline, and aborts the file being downloaded with an "Undetermined Error" when the connection has been closed. [Test case] This could be seen by running apt build-dep evince on cosmic with a recent apt with the pipelining fix (such as 1.6.6) against a local mirror running apache from trusty. It remains to be seen whether this is easily reproducible for anyone. [Regression potential] N/A yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1831252] Re: panic=-1 is completely ignored by the initrd causing unexpected behaviour
** Also affects: initramfs-tools (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu Disco)
Status: New => In Progress
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1831252
Title:
panic=-1 is completely ignored by the initrd causing unexpected
behaviour
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Xenial:
In Progress
Status in initramfs-tools source package in Bionic:
In Progress
Status in initramfs-tools source package in Disco:
In Progress
Status in initramfs-tools source package in Eoan:
Fix Released
Bug description:
[Impact]
in Ubuntu Core we default to using panic=-1 on the kernel command line
(documented at [1]) to speed up the auto-rollback mechanism of the kernel. on a
kernel level this works just fine and the system reboots immediately ...
when in the initramfs during boot and a panic occurs, no reboot
happens at all, the initrd spawns a shell regardless of the panic=
value ...
[Test case]
Before booting change root=$foo to root=x$foo - this will make it
panic. Then test that
1) "panic=-1" causes an immediate reboot
2) "panic=5" waits 5 seconds
3) no "panic" drops you to a shell
[Regression potential]
This adds some very specific checks for -1 in places that use ${panic}, as
such the regression potential is somewhat limited. If there were a regression,
it could be a syntax error (causing boot to fail) or a sleep not working
correctly (causing sleep to, well, not sleep) - but that's unrealistic.
[Other info]
this is caused by a filter in /usr/share/initramfs-tools/init
panic=*)
panic="${x#panic=}"
case ${panic} in
*[![:digit:].]*)
panic=
;;
esac
;;
this function only lets positive values through, else panic= simply
gets unset
the panic() function itself is also not capable of handling negative
values, it has a sleep call that interprets negative values as
commandline options instead of simply ignoring a negative sleep time
[2] (line 11).
the filter in the init script should allow the -1 value (to comply
with the kernel documentation and behaviour) and the panic() function
should properly skip the sleep call when a negative value for panic=
is set.
[1]
https://github.com/torvalds/linux/blob/v4.17/Documentation/admin-guide/kernel-parameters.txt#L2931
[2] https://paste.ubuntu.com/p/mswD8Cd869/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831252/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1771914] Re: release-upgrade-motd can't update message via apt proxy
Targetting this to xenial so we can verify that this regression won't
happen there when fixing bug 1744318.
** Also affects: update-manager (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1771914
Title:
release-upgrade-motd can't update message via apt proxy
Status in update-manager package in Ubuntu:
Fix Released
Status in update-manager source package in Xenial:
New
Status in update-manager source package in Bionic:
Fix Released
Bug description:
[Impact]
apt proxy settings are not applied to https urls, and thus the
release-upgrade-motd script fails, and upgrades from bionic to new versions
won't be detected either, if you need to use a proxy. This is a regression from
the 1:18.04.6 upload which switched changelogs.ubuntu.com from http to https.
[Test case]
Set acquire::http::proxy to a non-existing host, e.g.
http://invalid.invalid/, and check that the tool fails.
Do the same with acquire::https::proxy.
(Kind of a reverse check, since I don't have a proxy setup to test
against. If there's an actual proxy and otherwise, no internet, it can
be verified by setting the actual proxy and checking that it works
with it).
[Regression potential]
The fix changes the API of init_proxy() in UpdateManager/Core/utils.py to
make it return a dict with 'http' and 'https' members rather than just a
string. It seems the return value is only used by the test case, though, so
that should be fine.
Apart from that, it also allows https proxies now, since we're doing
https anyway, which means that a proxy setting ignored before now is
not. The same applies to the the new proxy variables used - they were
not used before, so things might fail that used to work - like you
specify an invalid https proxy but don't actually need one. Low risk,
though.
[Original bug report]
I have configured apt proxy in apt.conf.d and apt update and apt install can
work correctly. However, when I logged in system everyday, in the login
message, it says:
Failed to connect to https://changelogs.ubuntu.com/meta-release-lts.
Check your Internet connection or proxy settings
After further investigation, I found the the issue is caused in
package python3-update-manager:
python3-update-manager: /usr/lib/python3/dist-
packages/UpdateManager/Core/utils.py
In the init_proxy function of the python script, it only set a http
proxy by below code:
proxy_support = ProxyHandler({"http": proxy})
after changing the line to add https proxy, it can work:
proxy_support = ProxyHandler({"http": proxy, "https":proxy})
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1771914/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1828639] Re: Unlooping all the trigger loops!!!!!
** Changed in: dpkg (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1828639 Title: Unlooping all the trigger loops! Status in dpkg package in Ubuntu: Fix Released Status in dpkg source package in Xenial: Fix Released Status in dpkg source package in Bionic: Fix Committed Status in dpkg source package in Cosmic: Fix Committed Status in dpkg source package in Disco: Fix Released Status in dpkg source package in Eoan: Fix Released Bug description: [Impact] Quite a few bugs in triggers can cause distro upgrades to abort. [Test case] For cosmic -> disco, install ubuntu-mate-desktop and then upgrade. For other releases, there might not be any test cases We should at least run some upgrade tests for a system with ubuntu- desktop installed. [Regression potential] New trigger bugs could of course be caused by the changes. [Original bug report] Encountered when upgrading from cosmic to disco with ubuntu-mate- desktop installed. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: libvlc-bin 3.0.6-1 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 Date: Fri May 10 22:48:10 2019 ErrorMessage: 90.8592:triggers looping, abandoned Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 SourcePackage: vlc Title: package libvlc-bin 3.0.6-1 failed to install/upgrade: 90.8592:triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-05-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1828639/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829860] Re: APT unlocks in same order as it locks
** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829860 Title: APT unlocks in same order as it locks Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Disco: New Bug description: [Impact] APT releases the locks in the same order it acquires them, rather than reverse order. Given that we have no waiting for locks, this is not _super_ problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, rather than lock-frontend. [Test case] ... [Regression potential] ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829860/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1828639] Re: Unlooping all the trigger loops!!!!!
** Also affects: dpkg (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1828639 Title: Unlooping all the trigger loops! Status in dpkg package in Ubuntu: Fix Committed Status in dpkg source package in Xenial: Fix Committed Status in dpkg source package in Bionic: Fix Committed Status in dpkg source package in Cosmic: New Status in dpkg source package in Disco: Fix Committed Status in dpkg source package in Eoan: Fix Committed Bug description: [Impact] Quite a few bugs in triggers can cause distro upgrades to abort. [Test case] For cosmic -> disco, install ubuntu-mate-desktop and then upgrade. For other releases, there might not be any test cases We should at least run some upgrade tests for a system with ubuntu- desktop installed. [Regression potential] New trigger bugs could of course be caused by the changes. [Original bug report] Encountered when upgrading from cosmic to disco with ubuntu-mate- desktop installed. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: libvlc-bin 3.0.6-1 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 Date: Fri May 10 22:48:10 2019 ErrorMessage: 90.8592:triggers looping, abandoned Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 SourcePackage: vlc Title: package libvlc-bin 3.0.6-1 failed to install/upgrade: 90.8592:triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-05-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1828639/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1828639] Re: Fixing all the triggers!
cosmic is reaching eol in 8 days, removing that task. ** Summary changed: - package libvlc-bin 3.0.6-1 failed to install/upgrade: 90.8592:triggers looping, abandoned + Fixing all the triggers! ** Summary changed: - Fixing all the triggers! + Fixing all the trigger bugs! ** No longer affects: dpkg (Ubuntu Cosmic) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1828639 Title: Fixing all the trigger bugs! Status in dpkg package in Ubuntu: Fix Committed Status in dpkg source package in Xenial: Triaged Status in dpkg source package in Bionic: Triaged Status in dpkg source package in Disco: Triaged Status in dpkg source package in Eoan: Fix Committed Bug description: [Impact] Quite a few bugs in triggers can cause distro upgrades to abort. [Test case] For cosmic -> disco, install ubuntu-mate-desktop and then upgrade. For other releases, there might not be any test cases [Regression potential] New trigger bugs could of course be caused by the changes. [Original bug report] Encountered when upgrading from cosmic to disco with ubuntu-mate- desktop installed. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: libvlc-bin 3.0.6-1 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 Date: Fri May 10 22:48:10 2019 ErrorMessage: 90.8592:triggers looping, abandoned Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 SourcePackage: vlc Title: package libvlc-bin 3.0.6-1 failed to install/upgrade: 90.8592:triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-05-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1828639/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1828639] Re: package libvlc-bin 3.0.6-1 failed to install/upgrade: 90.8592:triggers looping, abandoned
I could verify this bug report in a lxd container and that dpkg 1.19.7 (not yet merged) fixes the issue. ** Changed in: vlc (Ubuntu) Status: Confirmed => Triaged ** Package changed: vlc (Ubuntu) => dpkg (Ubuntu) ** Also affects: dpkg (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: dpkg (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: dpkg (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: dpkg (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: dpkg (Ubuntu Eoan) Importance: Undecided Status: Triaged ** Changed in: dpkg (Ubuntu Eoan) Importance: Undecided => High ** Changed in: dpkg (Ubuntu Disco) Status: New => Triaged ** Changed in: dpkg (Ubuntu Cosmic) Status: New => Triaged ** Changed in: dpkg (Ubuntu Bionic) Status: New => Triaged ** Changed in: dpkg (Ubuntu Xenial) Status: New => Triaged ** Changed in: dpkg (Ubuntu Xenial) Importance: Undecided => High ** Changed in: dpkg (Ubuntu Bionic) Importance: Undecided => High ** Changed in: dpkg (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: dpkg (Ubuntu Disco) Importance: Undecided => High ** Changed in: dpkg (Ubuntu Bionic) Importance: High => Critical ** Changed in: dpkg (Ubuntu Bionic) Importance: Critical => High ** Description changed: + [Impact] + Quite a few bugs in triggers can cause distro upgrades to abort. + + [Test case] + For cosmic -> disco, install ubuntu-mate-desktop and then upgrade. + + For other releases, there might not be any test cases + + [Regression potential] + New trigger bugs could of course be caused by the changes. + + [Original bug report] + Encountered when upgrading from cosmic to disco with ubuntu-mate-desktop installed. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: libvlc-bin 3.0.6-1 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 Date: Fri May 10 22:48:10 2019 ErrorMessage: 90.8592:triggers looping, abandoned Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 SourcePackage: vlc Title: package libvlc-bin 3.0.6-1 failed to install/upgrade: 90.8592:triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-05-10 (0 days ago) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1828639 Title: package libvlc-bin 3.0.6-1 failed to install/upgrade: 90.8592:triggers looping, abandoned Status in dpkg package in Ubuntu: Triaged Status in dpkg source package in Xenial: Triaged Status in dpkg source package in Bionic: Triaged Status in dpkg source package in Cosmic: Triaged Status in dpkg source package in Disco: Triaged Status in dpkg source package in Eoan: Triaged Bug description: [Impact] Quite a few bugs in triggers can cause distro upgrades to abort. [Test case] For cosmic -> disco, install ubuntu-mate-desktop and then upgrade. For other releases, there might not be any test cases [Regression potential] New trigger bugs could of course be caused by the changes. [Original bug report] Encountered when upgrading from cosmic to disco with ubuntu-mate- desktop installed. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: libvlc-bin 3.0.6-1 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 Date: Fri May 10 22:48:10 2019 ErrorMessage: 90.8592:triggers looping, abandoned Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 SourcePackage: vlc Title: package libvlc-bin 3.0.6-1 failed to install/upgrade: 90.8592:triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-05-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1828639/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1830169] Re: lvm udev rule fails to call systemd-run
Turns out xenial binaries were not affected at all because they were
built with --disable-udev-systemd-background-jobs
** No longer affects: lvm2 (Ubuntu Xenial)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1830169
Title:
lvm udev rule fails to call systemd-run
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in lvm2 package in Ubuntu:
Fix Released
Status in lvm2 source package in Bionic:
Fix Committed
Status in lvm2 source package in Cosmic:
Fix Released
Status in lvm2 source package in Disco:
Fix Released
Status in lvm2 source package in Eoan:
Fix Released
Bug description:
[Impact]
Judging from the rule, this probably means that volumes do not disappear when
the physical volume disappears.
[Test case]
Not available. But since it's just a path fix, it should not be a problem.
[Regression potential]
Removal might now actually work correctly, but it's not entirely clear how
that could cause a regression.
[Other info]
In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run
command during removal ---
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
But /bin/systemd-run is not found, in fact systemd-run is in /usr/bin
/systemd-run.
xx:~$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
xx:~$ ls /bin/systemd-run
ls: cannot access '/bin/systemd-run': No such file or directory
xx:~$ ls /usr/bin/systemd-run
/usr/bin/systemd-run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830169/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1744318] Re: changelogs.ubuntu.com should be using HTTPS
I think I vaguely recall some issues that occured after this SRU in bionic, but I'm not sure anymore. It certainly means that tools stop working for people behind proxies in quite a few cases (e.g. various apt proxies not allowing https connect; or access to changelogs.ubuntu.com). So we need to consider whether the benefits of backporting this to xenial outweight the risks. ** Also affects: update-manager (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1744318 Title: changelogs.ubuntu.com should be using HTTPS Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Xenial: New Status in update-manager source package in Xenial: New Status in ubuntu-release-upgrader source package in Bionic: Fix Released Status in update-manager source package in Bionic: Fix Released Bug description: Although the packages listed in meta-release files on changelogs.ubuntu.com are signature-checked there doesn't appear to be any way to verify the meta-release files are valid so a man-in-the- middle could maliciously supply an alternate meta-release. meta-release files should be signed with the archive GPG key and/or delivered over HTTPS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1744318/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
** Changed in: gnome-menus (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-menus (Ubuntu Xenial) Status: Confirmed => Invalid ** Changed in: gnome-menus (Ubuntu Bionic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Fix Released Status in gnome-menus package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in gnome-menus source package in Xenial: Invalid Status in ubuntu-release-upgrader source package in Xenial: Invalid Status in gnome-menus source package in Bionic: Invalid Status in ubuntu-release-upgrader source package in Bionic: Fix Released Bug description: [Impact] Upgrades on some systems fail with trigger issues related to gnome-menus. Upgrading libc6 first fixes that, so we modified u-r-u to upgrade it first. [Test case] Restore apt-clone file from comment #20 and upgrade to bionic with u-r-u. [Regression potential] (1) Upgrade of libc6 fails, upgrade would revert (2) If upgrade of libc6 succeeds, but we cannot find an ordering for the remaining upgrades, we are stuck with just libc6 upgraded. It seems unlikely that we find an ordering for all packages, but none for the set without libc6 though. # Original bug report Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64
[Group.of.nepali.translators] [Bug 1766740] Re: apport autopkgtest regression due to kernel packaging changes
** Also affects: apport (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1766740 Title: apport autopkgtest regression due to kernel packaging changes Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: New Status in apport source package in Bionic: Fix Released Bug description: [SRU Justification] In bionic, linux-image-$kvers-$flavor is now built from the linux-signed source package on amd64, not from the linux source package. This now causes a test to fail in the apport test suite: [...] == FAIL: test_run_crash_kernel (__main__.T) run_crash() for a kernel error -- Traceback (most recent call last): File "./test_ui.py", line 1305, in test_run_crash_kernel self.assertEqual(self.ui.opened_url, 'http://linux.bugs.example.com/%i' % se lf.ui.crashdb.latest_id()) AssertionError: 'http://linux-signed.bugs.example.com/5' != 'http://linux.bugs.e xample.com/5' - http://linux-signed.bugs.example.com/5 ? --- + http://linux.bugs.example.com/5 -- Ran 70 tests in 79.815s FAILED (failures=1) [...] (https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- bionic/bionic/amd64/a/apport/20180424_19_45dc8@/log.gz) This test needs to be fixed to know about the packaging change. Note that this packaging change is expected to soon be SRUed back to all Ubuntu releases, so apport's testsuite change should also be SRUed. [Test case] This passes if the autopkgtests pass. [Regression potential] The test could be changed to pass while leaving underlying issues in the code. This has probably not happened here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1766740/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1694702] Re: off-by-one error when translating source records build depends
This was fixed before 1.6, so only xenial and trusty affected at most.
** Changed in: python-apt (Ubuntu)
Status: In Progress => Fix Released
** Also affects: python-apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: python-apt (Ubuntu Xenial)
Status: New => Triaged
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1694702
Title:
off-by-one error when translating source records build depends
Status in python-apt package in Ubuntu:
Fix Released
Status in python-apt source package in Xenial:
Triaged
Bug description:
[Impact]
Out-of-bounds read in an array, causing segmentation fault
[Testcase]
On amd64:
python3-dbg -c 'import apt, apt_pkg; sr=apt_pkg.SourceRecords();
sr.lookup("dq"); print(sr.build_depends)'
crashes.
[Regression potential]
This is a simple off-by-one fix. There really should be no regressions, but
if there were, only for people using SourceRecords.build_depends - the list
could now be shorter (depending on memory).
diff --git a/python/pkgsrcrecords.cc b/python/pkgsrcrecords.cc
index 9ca21c5a..77b490cb 100644
--- a/python/pkgsrcrecords.cc
+++ b/python/pkgsrcrecords.cc
@@ -220,7 +220,7 @@ static PyObject *PkgSrcRecordsGetBuildDepends(PyObject
*Self,void*) {
bd[i].Version.c_str(), pkgCache::CompType(bd[i].Op));
PyList_Append(OrGroup, v);
Py_DECREF(v);
- if (pkgCache::Dep::Or != (bd[i].Op & pkgCache::Dep::Or) || i ==
bd.size())
+ if (pkgCache::Dep::Or != (bd[i].Op & pkgCache::Dep::Or) || i + 1
>= bd.size())
break;
i++;
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1694702/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1830635] [NEW] Regression: xenial: Uses apt_pkg.Error, which is only available in later versions
Public bug reported:
[Impact]
The last SRU introduced a regression in error handling, where apt_pkg.Error is
being caught - but that class is not available in xenial - it still uses
SystemError
[Test case]
Run python3 -c "import apt; apt.Cache().update()" while running apt
update.
You should see:
#
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 468, in update
raise LockFailedException("Failed to lock %s" % lockfile)
apt.cache.LockFailedException: Failed to lock /var/lib/apt/lists/lock
Currently you see:
#
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apt/cache.py", line 63, in __enter__
return self._lock.__enter__()
SystemError: E:Could not get lock /var/lib/apt/lists/lock - open (11: Resource
temporarily unavailable)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/apt/cache.py", line 481, in update
with _WrappedLock(apt_pkg.config.find_dir("Dir::State::Lists")):
File "/usr/lib/python3/dist-packages/apt/cache.py", line 64, in __enter__
except apt_pkg.Error as e:
AttributeError: module 'apt_pkg' has no attribute 'Error'
[Regression potential]
It really can't get worse than this. But FWIW: This only affects code paths
where we could not lock the lists/ or archives/ directory - they currently
throw the AttributeError, and will then throw LockFailedException again - as
they did before the SRU.
** Affects: python-apt (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: python-apt (Ubuntu Xenial)
Importance: Undecided
Status: Triaged
** Description changed:
[Impact]
The last SRU introduced a regression in error handling, where apt_pkg.Error
is being caught - but that class is not available in xenial - it still uses
SystemError
[Test case]
Run python3 -c "import apt; apt.Cache().update()" while running apt
update.
-
You should see:
#
- Traceback (most recent call last):
- File "", line 1, in
- File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 468, in update
- raise LockFailedException("Failed to lock %s" % lockfile)
+ Traceback (most recent call last):
+ File "", line 1, in
+ File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 468, in update
+ raise LockFailedException("Failed to lock %s" % lockfile)
apt.cache.LockFailedException: Failed to lock /var/lib/apt/lists/lock
Currently you see:
#
Traceback (most recent call last):
- File "/usr/lib/python3/dist-packages/apt/cache.py", line 63, in __enter__
- return self._lock.__enter__()
+ File "/usr/lib/python3/dist-packages/apt/cache.py", line 63, in __enter__
+ return self._lock.__enter__()
SystemError: E:Could not get lock /var/lib/apt/lists/lock - open (11:
Resource temporarily unavailable)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
- File "", line 1, in
- File "/usr/lib/python3/dist-packages/apt/cache.py", line 481, in update
- with _WrappedLock(apt_pkg.config.find_dir("Dir::State::Lists")):
- File "/usr/lib/python3/dist-packages/apt/cache.py", line 64, in __enter__
- except apt_pkg.Error as e:
+ File "", line 1, in
+ File "/usr/lib/python3/dist-packages/apt/cache.py", line 481, in update
+ with _WrappedLock(apt_pkg.config.find_dir("Dir::State::Lists")):
+ File "/usr/lib/python3/dist-packages/apt/cache.py", line 64, in __enter__
+ except apt_pkg.Error as e:
AttributeError: module 'apt_pkg' has no attribute 'Error'
[Regression potential]
- It really can't get worse than this.
+ It really can't get worse than this. But FWIW: This only affects code paths
where we could not lock the lists/ or archives/ directory - they currently
throw the AttributeError, and will then throw LockFailedException again - as
they did before the SRU.
** Also affects: python-apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: python-apt (Ubuntu)
Status: New => Invalid
** Changed in: python-apt (Ubuntu Xenial)
Status: New => Triaged
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1830635
Title:
Regression: xenial: Uses
[Group.of.nepali.translators] [Bug 1415701] Re: apt is unable to handle CDROMS with default mount option
Definitely bionic, I just can't recount the alphabet order today; I meant to say it was also fixed in artful (not "cosmic") ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: apt (Ubuntu Xenial) Status: New => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1415701 Title: apt is unable to handle CDROMS with default mount option Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Bug description: I have found i am almost completely unable to use CDROM as an apt repository on Ubuntu 14.04 I found the command apt-cdrom add by default, was unable to detect CDROMs it was attempting to find them in /media/cdrom/ by default ubuntu now seems to mount cds in /media/$USER/ and this is not something set via fstab i was able to get them to add with the command apt-cdrom add -m --cdrom /media/$USER/ I seem to have been able to pull the package list from the CD, but when it comes to installing from it, apt encounters a similar error it ask you to insert the disc in drive /media/cdrom/ again I also am completely unable to add cds via the software & updates setting manager, it always fails to find the cd, which is presumably part of the same issue. manually remounting with sudo mount /dev/cdrom /media/cdrom get some things to work, but most of the actions trigger a remount which goes back to the default location I was finally able to get things working again properly by adding the fstab line /dev/cdrom /media/cdrom udf,iso9660 user,noauto,exec,utf8 0 0 resolves the problem for me but this is a work around not a fix, it may break other stuff In apt conf i have tried setting Acquire::cdrom::mount "file/path/"; with various file paths, the file paths, to try and make it work with the default mount behaviour,this looked to be the right setting to change as the message changed accordingly to what i was setting, but i could not get it to work for actually installing packages, even by setting an absolute file path for my user in the media directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1415701/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1494851] Re: initramfs cryptroot hook script doesn't install cryptsetup if keyfile but no keyscript
** Also affects: cryptsetup (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: cryptsetup (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1494851 Title: initramfs cryptroot hook script doesn't install cryptsetup if keyfile but no keyscript Status in cryptsetup package in Ubuntu: Incomplete Status in cryptsetup source package in Xenial: New Status in cryptsetup source package in Bionic: New Bug description: When crypttab specifies a key-file for the container of the root file- system but there is no keyscript= option no cryptsetup support is installed in the initrd.img. Currently the cryptroot initramfs hook script knows its a problem and will report: cryptsetup: WARNING: target LUKS_OS uses a key file, skipped This is BAD behaviour that renders the root file-system container inaccessible at boot time. Regardless of a key-script being available cryptsetup support should be installed into the initrd.img to enable the user to take manual steps to unlock the container. The hook script has no knowledge about pass phrases that might be set in other LUKS slots that are available to the user. This is the behaviour when a keyscript is specified but doesn't exist. The attached patch modifies the behaviour to include cryptsetup in the initrd.img and modify the warning to the user. cryptsetup: WARNING: target LUKS_OS uses a key file, but no keyscript is set. Please ensure there is also a typed pass-phrase set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1494851/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1359689] Re: cryptsetup password prompt not shown
This should have been fixed in xenial by the merge from unstable. Nvidia stuff is likely a different bug. If you experience this in a later release, consider opening a new bug, thanks! ** Changed in: plymouth (Ubuntu Xenial) Status: Triaged => Fix Released ** Changed in: plymouth (Ubuntu) Status: Triaged => Fix Released ** Tags removed: kernel-graphics rls-x-incoming ** Tags added: kernel-graphic ** Tags removed: kernel-graphic ** Tags added: kernel-graphics -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1359689 Title: cryptsetup password prompt not shown Status in plymouth package in Ubuntu: Fix Released Status in plymouth source package in Utopic: Won't Fix Status in plymouth source package in Vivid: Won't Fix Status in plymouth source package in Xenial: Fix Released Status in plymouth package in Debian: Fix Released Bug description: Currently in utopic the following happens when booting an encrypted setup: Press enter in grub, after a while screen freezes (or turns completely black) and stays like that. When I press the down key, I can see the password prompt. When I press the up key again, I get to the graphical password prompt. This is demonstrated in the following screencast: https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing Maybe this is related to the version of plymouth utopic currently uses, a similar debian bug report seems to be resolved with a newer version 0.9.0-6, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752. --- ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) Package: plymouth 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Tags: utopic Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) MachineType: Dell Inc. Precision M4600 Package: plymouth 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu quiet splash vt.handoff=7 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Tags: utopic TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/10/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1359689/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress
** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1820886 Title: Potential inconsistency due to system halt/reboot being allowed when package installation in progress Status in apt package in Ubuntu: In Progress Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Cosmic: New Status in apt source package in Disco: New Bug description: [System] Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, Cosmic). [Impact] Package installation turns into an inconsistent state if system is rebooted in the middle of an apt install/upgrade. [Test Case] 1. User1 at Ubuntu box issues "sudo apt-get upgrade"; 2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI; 3. System reboots and potentially turns into an inconsistent state. [Remarks] APT should automatically inhibit system halts/reboots while packages being installed/removed. A similar behavior to what is shown by unattended-upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1820886/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1826870] [NEW] cache.commit() doesn't release the archives lock
Public bug reported: [Impact] cache.commit() does not release all the locks it acquires as part of committing. This is a regression of locking fixes in bug 1795407. [Test case] This script should work: #!/usr/bin/env python import apt import subprocess cache = apt.Cache() pkg = cache["hello"] pkg.mark_install() cache.commit() subprocess.check_call(["apt", "remove", "--yes", "hello"]) [Regression potential] Other new locking bugs could pop up ** Affects: python-apt (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: python-apt (Ubuntu Xenial) Importance: Undecided Status: Triaged ** Affects: python-apt (Ubuntu Bionic) Importance: Undecided Status: Triaged ** Affects: python-apt (Ubuntu Cosmic) Importance: Undecided Status: Triaged ** Affects: python-apt (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #922416 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922416 ** Also affects: python-apt (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922416 Importance: Unknown Status: Unknown ** Changed in: python-apt (Ubuntu) Status: New => Fix Released ** Changed in: python-apt (Ubuntu) Status: Fix Released => New ** Also affects: python-apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu) Status: New => Fix Released ** Changed in: python-apt (Ubuntu Xenial) Status: New => Triaged ** Changed in: python-apt (Ubuntu Bionic) Status: New => Triaged ** Changed in: python-apt (Ubuntu Cosmic) Status: New => Triaged ** Description changed: [Impact] - cache.commit() does not release all the locks it acquires as part of committing. + cache.commit() does not release all the locks it acquires as part of committing. This is a regression of locking fixes in bug 1795407. [Test case] This script should work: #!/usr/bin/env python import apt import subprocess cache = apt.Cache() pkg = cache["hello"] pkg.mark_install() cache.commit() subprocess.check_call(["apt", "remove", "--yes", "hello"]) [Regression potential] Other new locking bugs could pop up -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1826870 Title: cache.commit() doesn't release the archives lock Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Triaged Status in python-apt source package in Bionic: Triaged Status in python-apt source package in Cosmic: Triaged Status in python-apt package in Debian: Unknown Bug description: [Impact] cache.commit() does not release all the locks it acquires as part of committing. This is a regression of locking fixes in bug 1795407. [Test case] This script should work: #!/usr/bin/env python import apt import subprocess cache = apt.Cache() pkg = cache["hello"] pkg.mark_install() cache.commit() subprocess.check_call(["apt", "remove", "--yes", "hello"]) [Regression potential] Other new locking bugs could pop up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826870/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1815760] Re: Additional hooks for update
@Mathew Hodson please stop messing with tasks. It's important we have those invalid tasks to say that it does not apply to that branch vs. we just forgot about it. ** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Trusty) Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1815760 Title: Additional hooks for update Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Invalid Status in apt source package in Xenial: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Cosmic: Fix Released Status in apt source package in Disco: Fix Released Bug description: [Impact] We want to write some scripts for apt that run on update if apt shows an update count, to provide further details about the new cache. [Test case] Specify a APT::Update::Post-Invoke-Stats script and check that (1) it shows in apt update (2) it does not show in apt-get update [Regression potential] More scripts may fail the update now, but there should not be any registered so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815760/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1818996] Re: auth.conf.d directory missing
** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1818996 Title: auth.conf.d directory missing Status in apt package in Ubuntu: New Status in apt source package in Trusty: New Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Cosmic: New Status in apt source package in Disco: New Bug description: [Impact] apt in disco and the current set of SRUs introduce support for .conf snippets in auth.conf.d, but accidentally did not introduce the auth.conf.d directory, making it hard to discover if support for it exists, and requiring users to create the dir if it is missing - that's bad UX. [Test case] Install apt, make sure /etc/apt/auth.conf.d exists [Regression potential] It's just a directory, what could possibly go wrong? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1818996/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1815760] Re: Additional hooks for update
** Changed in: apt (Ubuntu Trusty) Status: In Progress => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1815760 Title: Additional hooks for update Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Invalid Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] We want to write some scripts for apt that run on update if apt shows an update count, to provide further details about the new cache. [Test case] Specify a APT::Update-Post-Invoke-Stats script and check that (1) it shows in apt update (2) it does not show in apt-get update [Regression potential] More scripts may fail the update now, but there should not be any registered so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815760/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1814727] Re: Backport never pinning and Packages-Require-Authorization
Sure ** Changed in: apt (Ubuntu Disco) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1814727 Title: Backport never pinning and Packages-Require-Authorization Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: In Progress Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: In Progress Status in apt source package in Cosmic: Incomplete Status in apt source package in Disco: Fix Released Bug description: [Impact] These are not driven from a direct user experience, but are related to other developments: (1) unattended-upgrades could use the never pinning to disable repositories rather than switching candidates. That would simplify code quite a bit. (2) Packages-Require-Authorization lets a repository declare that downloading packages from it requires authorization. This is useful both for private repositories, as it can prevent unattended-upgrades failures if you remove authorization info; and it also allows creating a new form of semi-private repository, where only pool/ requires authorization. [Test case] Tests are included in autopkgtests and cover the common scenarios https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-packages-require-authorization: (1) Add repository with Packages-Require-Authorization and no auth.conf entry: pin -32768 (2) Add repository with Packages-Require-Authorization and a auth.conf entry: pin 500 (3) As (2), but a custom pin still applies https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-policy-pinning#L365 (1) Test that Pin-Priority: never overrides both per-package pins and per-repository pins (2) Test that Pin-Priority: never is only applied for per-repository (Package: *) pins Tests in older releases should be the same, but it's not clear yet. Bug will be updated once the SRUs are ready. [Regression potential] The changes might introduce regressions in pinning. The pinning implementation in trusty is substantially different from the other releases, and should thus require more testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1814727/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1818201] Re: /usr/lib/packagekit/packagekitd:11:__memmove_avx_unaligned_erms:std::char_traits:std::__cxx11::basic_string:std::__cxx11::basic_string:std::__cxx11::bas
SRUs uploaded for bionic and cosmic. Since we do not use packagekit in gnome-software in xenial, not fixing it there. Also not fixing it in trusty, as it's close to EOL. ** Changed in: packagekit (Ubuntu Cosmic) Status: New => In Progress ** Changed in: packagekit (Ubuntu Bionic) Status: New => In Progress ** Changed in: packagekit (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1818201 Title: /usr/lib/packagekit/packagekitd:11:__memmove_avx_unaligned_erms:std::char_traits:std::__cxx11::basic_string:std::__cxx11::basic_string:std::__cxx11::basic_string Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Xenial: Won't Fix Status in packagekit source package in Bionic: In Progress Status in packagekit source package in Cosmic: In Progress Status in packagekit source package in Disco: Fix Released Bug description: [Impact] packagekit (sometimes) crashes when there are errors. [Test case] Check that there are no further cases on the error tracker with the proposed version. [Regression potential] Given that this just changes the return type of a function only used in calls, and the code compiles, there should be no possibility for a regression. Of course, if there were, it'd be segfaults or stuff. [Original info] The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.1.12-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/e9af46c2ad01a15f968379c434fe0bfbf924d034 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1818201/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic
** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-meta (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-meta-hwe (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: apt (Ubuntu Trusty) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Trusty: In Progress Status in linux-meta source package in Trusty: New Status in linux-meta-hwe source package in Trusty: New Status in apt source package in Xenial: In Progress Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: Fix Released Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: Fix Released Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787460/+subscriptions
[Group.of.nepali.translators] [Bug 1814727] Re: Backport never pinning and Packages-Require-Authorization
** Description changed: [Impact] These are not driven from a direct user experience, but are related to other developments: (1) unattended-upgrades could use the never pinning to disable repositories rather than switching candidates. That would simplify code quite a bit. (2) Packages-Require-Authorization lets a repository declare that downloading packages from it requires authorization. This is useful both for private repositories, as it can prevent unattended-upgrades failures if you remove authorization info; and it also allows creating a new form of semi-private repository, where only pool/ requires authorization. [Test case] - Tests are included in autopkgtests and cover the common scenarios. + Tests are included in autopkgtests and cover the common scenarios, except for trusty, where they have to be simulated: https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-packages-require-authorization: (1) Add repository with Packages-Require-Authorization and no auth.conf entry: pin -32768 (2) Add repository with Packages-Require-Authorization and a auth.conf entry: pin 500 (3) As (2), but a custom pin still applies https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-policy-pinning#L365 (1) Test that Pin-Priority: never overrides both per-package pins and per-repository pins (2) Test that Pin-Priority: never is only applied for per-repository (Package: *) pins Tests in older releases should be the same, but it's not clear yet. Bug will be updated once the SRUs are ready. [Regression potential] The changes might introduce regressions in pinning. The pinning implementation in trusty is substantially different from the other releases, and should thus require more testing. ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1814727 Title: Backport never pinning and Packages-Require-Authorization Status in apt package in Ubuntu: New Status in apt source package in Trusty: New Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Cosmic: New Status in apt source package in Disco: New Bug description: [Impact] These are not driven from a direct user experience, but are related to other developments: (1) unattended-upgrades could use the never pinning to disable repositories rather than switching candidates. That would simplify code quite a bit. (2) Packages-Require-Authorization lets a repository declare that downloading packages from it requires authorization. This is useful both for private repositories, as it can prevent unattended-upgrades failures if you remove authorization info; and it also allows creating a new form of semi-private repository, where only pool/ requires authorization. [Test case] Tests are included in autopkgtests and cover the common scenarios, except for trusty, where they have to be simulated: https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-packages-require-authorization: (1) Add repository with Packages-Require-Authorization and no auth.conf entry: pin -32768 (2) Add repository with Packages-Require-Authorization and a auth.conf entry: pin 500 (3) As (2), but a custom pin still applies https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-policy-pinning#L365 (1) Test that Pin-Priority: never overrides both per-package pins and per-repository pins (2) Test that Pin-Priority: never is only applied for per-repository (Package: *) pins Tests in older releases should be the same, but it's not clear yet. Bug will be updated once the SRUs are ready. [Regression potential] The changes might introduce regressions in pinning. The pinning implementation in trusty is substantially different from the other releases, and should thus require more testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1814727/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1815760] Re: Additional hooks for update
** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1815760 Title: Additional hooks for update Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: New Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Cosmic: New Status in apt source package in Disco: Fix Released Bug description: [Impact] We want to write some scripts for apt that run on update if apt shows an update count, to provide further details about the new cache. [Test case] Specify a APT::Update-Post-Invoke-Stats script and check that (1) it shows in apt update (2) it does not show in apt-get update [Regression potential] More scripts may fail the update now, but there should not be any registered so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815760/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1815760] [NEW] Additional hooks for update
Public bug reported: [Impact] We want to write some scripts for apt that run on update if apt shows an update count, to provide further details about the new cache. [Test case] Specify a APT::Update-Post-Invoke-Stats script and check that (1) it shows in apt update (2) it does not show in apt-get update [Regression potential] More scripts may fail the update now, but there should not be any registered so far. ** Affects: apt (Ubuntu) Importance: Undecided Status: In Progress ** Affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Affects: apt (Ubuntu Disco) Importance: Undecided Status: In Progress ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Disco) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1815760 Title: Additional hooks for update Status in apt package in Ubuntu: In Progress Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Cosmic: New Status in apt source package in Disco: In Progress Bug description: [Impact] We want to write some scripts for apt that run on update if apt shows an update count, to provide further details about the new cache. [Test case] Specify a APT::Update-Post-Invoke-Stats script and check that (1) it shows in apt update (2) it does not show in apt-get update [Regression potential] More scripts may fail the update now, but there should not be any registered so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815760/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1815761] [NEW] Alternative to Dpkg::Post-Invoke that runs even if dpkg did not have to be invoked
Public bug reported: [Impact] Dpkg::Post-Invoke is run only when dpkg had to be run. We'd like to be able to show some extra output even if no changes had been made. Imagine "the user disabled the security repo, and does not get any updates shown scenario" - we'd like to be able to tell them that there are security updates available after all. [Test case] To be updated once the mechanism is in place, but basically perform an upgrade w/o changes, and make sure the specified hook runs at the end. [Regression potential] No-change upgrades/install can now fail if this new hooks fail. ** Affects: apt (Ubuntu) Importance: Undecided Status: In Progress ** Affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Affects: apt (Ubuntu Disco) Importance: Undecided Status: In Progress ** Package changed: ubuntu => apt (Ubuntu) ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Disco) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1815761 Title: Alternative to Dpkg::Post-Invoke that runs even if dpkg did not have to be invoked Status in apt package in Ubuntu: In Progress Status in apt source package in Trusty: New Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Cosmic: New Status in apt source package in Disco: In Progress Bug description: [Impact] Dpkg::Post-Invoke is run only when dpkg had to be run. We'd like to be able to show some extra output even if no changes had been made. Imagine "the user disabled the security repo, and does not get any updates shown scenario" - we'd like to be able to tell them that there are security updates available after all. [Test case] To be updated once the mechanism is in place, but basically perform an upgrade w/o changes, and make sure the specified hook runs at the end. [Regression potential] No-change upgrades/install can now fail if this new hooks fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815761/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1815750] Re: autopkgtest failure due to security update
Yes, I know they're broken in xenial, and it's fixed in git, and will be part of the next SRU. ** Changed in: apt (Ubuntu Bionic) Status: New => Invalid ** Changed in: apt (Ubuntu Cosmic) Status: New => Invalid ** Changed in: apt (Ubuntu Trusty) Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1815750 Title: autopkgtest failure due to security update Status in apt package in Ubuntu: New Status in apt source package in Trusty: Invalid Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: Invalid Status in apt source package in Cosmic: Invalid Bug description: [impact] the security update for: SECURITY UPDATE: content injection in http method (CVE-2019-3462) (LP: #1812353) causes an autopkgtest failure for: Failed tests: test-cve-2019-3462-dequote-injection [test case] run autopkgtest on the security-patched version [regression potential] the test needs to be updated, so the regression potential is around the test continuing to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815750/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** No longer affects: apt (Ubuntu) ** No longer affects: apt (Ubuntu Xenial) ** No longer affects: apt (Ubuntu Artful) ** No longer affects: apt (Ubuntu Bionic) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in menu package in Ubuntu: Fix Released Status in menu source package in Xenial: Fix Released Status in menu source package in Artful: Fix Released Status in menu source package in Bionic: Fix Released Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/menu/+bug/1768905/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic
** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-meta (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-meta-hwe (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-meta (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-meta-hwe (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Disco) Importance: Critical Status: Fix Released ** Also affects: linux-meta (Ubuntu Disco) Importance: Critical Status: Triaged ** Also affects: linux-meta-hwe (Ubuntu Disco) Importance: Critical Status: Triaged ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-meta (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-meta-hwe (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Xenial: New Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: New Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: New Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago)
[Group.of.nepali.translators] [Bug 1811120] [NEW] Backport auth.conf.d
Public bug reported: [Impact] Backport auth.conf.d support to allow specifying per-repository authentication data in separate files, so packages can setup authenticated repositories. [Regression potential] We ignore errors from opening auth.conf.d files, so regressions can only occur when parsing a file fails, in which case apt would exit with an error. [Test case] The test suite provides autopkgtests for auth.conf.d which creates an auth.conf.d file and checks that it is successfully used; so we can check if those passed. ** Affects: apt (Ubuntu) Importance: Low Status: Fix Released ** Affects: apt (Ubuntu Trusty) Importance: Low Status: Triaged ** Affects: apt (Ubuntu Xenial) Importance: Low Status: Triaged ** Affects: apt (Ubuntu Bionic) Importance: Low Status: Triaged ** Affects: apt (Ubuntu Cosmic) Importance: Low Status: Triaged ** Affects: apt (Ubuntu Disco) Importance: Low Status: Fix Released ** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Disco) Status: New => Fix Released ** Changed in: apt (Ubuntu Cosmic) Status: New => Triaged ** Changed in: apt (Ubuntu Bionic) Status: New => Triaged ** Changed in: apt (Ubuntu Xenial) Status: New => Triaged ** Changed in: apt (Ubuntu Trusty) Status: New => Triaged ** Changed in: apt (Ubuntu Cosmic) Importance: Undecided => Wishlist ** Changed in: apt (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: apt (Ubuntu Cosmic) Importance: Wishlist => Low ** Changed in: apt (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: apt (Ubuntu Trusty) Importance: Undecided => Low ** Changed in: apt (Ubuntu Disco) Importance: Undecided => Low -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1811120 Title: Backport auth.conf.d Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in apt source package in Xenial: Triaged Status in apt source package in Bionic: Triaged Status in apt source package in Cosmic: Triaged Status in apt source package in Disco: Fix Released Bug description: [Impact] Backport auth.conf.d support to allow specifying per-repository authentication data in separate files, so packages can setup authenticated repositories. [Regression potential] We ignore errors from opening auth.conf.d files, so regressions can only occur when parsing a file fails, in which case apt would exit with an error. [Test case] The test suite provides autopkgtests for auth.conf.d which creates an auth.conf.d file and checks that it is successfully used; so we can check if those passed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1811120/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1396654] Re: C++ demangling support missing from perf
Broken again in disco, let's update the state. ** Also affects: linux (Ubuntu Disco) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: Fix Released ** Also affects: linux-hwe (Ubuntu Disco) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-hwe (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-hwe (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: Fix Released => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1396654 Title: C++ demangling support missing from perf Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Xenial: Incomplete Status in linux-hwe source package in Xenial: Confirmed Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Fix Released Status in linux source package in Bionic: New Status in linux-hwe source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-hwe source package in Cosmic: New Status in linux source package in Disco: Triaged Status in linux-hwe source package in Disco: Confirmed Bug description: Hi, It appears that C++ demangling support is missing from linux-tools-3.16.0-24, on Utopic on arm64. Could the following please be added to the build dependencies for that package: libiberty-dev binutils-dev Installing the above and rebuilding the package fixed the problem for me. Cheers, -- Steve --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.7-0ubuntu8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied DistroRelease: Ubuntu 14.10 IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 RfKill: Error: [Errno 2] No such file or directory Tags: utopic utopic Uname: Linux 3.16.0-24-generic aarch64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: Upgraded to utopic on 2014-11-17 (9 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396654/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1801338] Re: apt fails to properly handle server-side connection closure
It actually did not fix the issue. ** Changed in: apt (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1801338 Title: apt fails to properly handle server-side connection closure Status in apt package in Ubuntu: Triaged Status in apt source package in Xenial: New Status in apt source package in Bionic: Triaged Status in apt source package in Cosmic: Triaged Bug description: [Impact] In some cases, apt does not correctly handle server-side connection closure after a pipeline, and aborts the file being downloaded with an "Undetermined Error" when the connection has been closed. [Test case] This could be seen by running apt build-dep evince on cosmic with a recent apt with the pipelining fix (such as 1.6.6) against a local mirror running apache from trusty. It remains to be seen whether this is easily reproducible for anyone. [Regression potential] N/A yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1800610] [NEW] [SRU] minimize number of manually installed packages
Public bug reported: [Impact] Releases prior to cosmic mark almost all packages manually installed, meaning that obsolete packages are not autoremoved when they should. We fixed this in cosmic, in trunk r1695, by including a new script that marks as automatically installed all dependencies of manually-installed metapackages. [Test case] Run a build and check in the log that some packages are visited by the script in more than one iterations. [Regression potential] First of all, this does not change existing installations; only new ones. The change can cause packages to be autoremoved that were not autoremoved before after performing a package management operation, or dependency change in packages. The change is essentially safe: Since we only mark dependencies of packages in the section "metapackages", and since those receive special treatment by apt: 1. removal due to dependencies/conflicts: the manual bit transfers from the meta to its deps 2. explicit removal (apt remove meta): meta and its dependencies are removed It is not possible to accidentally uninstall the entire metapackage with its dependencies. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Status: In Progress ** Also affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released ** Changed in: livecd-rootfs (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1800610 Title: [SRU] minimize number of manually installed packages Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: New Status in livecd-rootfs source package in Bionic: In Progress Bug description: [Impact] Releases prior to cosmic mark almost all packages manually installed, meaning that obsolete packages are not autoremoved when they should. We fixed this in cosmic, in trunk r1695, by including a new script that marks as automatically installed all dependencies of manually-installed metapackages. [Test case] Run a build and check in the log that some packages are visited by the script in more than one iterations. [Regression potential] First of all, this does not change existing installations; only new ones. The change can cause packages to be autoremoved that were not autoremoved before after performing a package management operation, or dependency change in packages. The change is essentially safe: Since we only mark dependencies of packages in the section "metapackages", and since those receive special treatment by apt: 1. removal due to dependencies/conflicts: the manual bit transfers from the meta to its deps 2. explicit removal (apt remove meta): meta and its dependencies are removed It is not possible to accidentally uninstall the entire metapackage with its dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1800610/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1796808] [NEW] frontend locking regression: dpkg::post-invoke scripts can't install packages
Public bug reported: [Impact] The switch to frontend locking in 1.2.28/1.6.5/1.7~ caused scripts registered in DPkg::Pre-Install-Pkgs DPkg::Pre-Invoke DPkg::Post-Invoke To be run with the frontend lock held. This caused problems with some installer packages like libdvd-pkg which install a locally built package in such a hook. To reduce the impact, a fix has been applied in 1.7.0 which exports the DPKG_FRONTEND_LOCKED variable when running those scripts, allowing dpkg to be run from those scripts. [Test case] Make sure that the test-frontend-lock test run by autopkgtest succeeds. This checks that: (1) the variable is correctly exported to those scripts (2) the frontend lock is still held (3) dpkg can be run from the post-invoke script [Regression potential] Depending on the script (for example, if the script starts a daemon manually or something like that), DPKG_FRONTEND_LOCKED might leak to other processes which might survive the apt call and thus revert surviving process to not using frontend locking. [Other info] This fix is for backwards compatibility only. Starting with the dd cycle, it will be dropped for the Pre-Install-Pkgs and Pre-Invoke scripts. Potentially for post-invoke as well, if we find a better solution for it. ** Affects: apt (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: apt (Ubuntu Xenial) Importance: Undecided Status: Triaged ** Affects: apt (Ubuntu Bionic) Importance: Undecided Status: Triaged ** Affects: apt (Ubuntu Cosmic) Importance: Undecided Status: Fix Released ** Also affects: apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Xenial) Status: New => Triaged ** Changed in: apt (Ubuntu Bionic) Status: New => Triaged ** Changed in: apt (Ubuntu Cosmic) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1796808 Title: frontend locking regression: dpkg::post-invoke scripts can't install packages Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Status in apt source package in Bionic: Triaged Status in apt source package in Cosmic: Fix Released Bug description: [Impact] The switch to frontend locking in 1.2.28/1.6.5/1.7~ caused scripts registered in DPkg::Pre-Install-Pkgs DPkg::Pre-Invoke DPkg::Post-Invoke To be run with the frontend lock held. This caused problems with some installer packages like libdvd-pkg which install a locally built package in such a hook. To reduce the impact, a fix has been applied in 1.7.0 which exports the DPKG_FRONTEND_LOCKED variable when running those scripts, allowing dpkg to be run from those scripts. [Test case] Make sure that the test-frontend-lock test run by autopkgtest succeeds. This checks that: (1) the variable is correctly exported to those scripts (2) the frontend lock is still held (3) dpkg can be run from the post-invoke script [Regression potential] Depending on the script (for example, if the script starts a daemon manually or something like that), DPKG_FRONTEND_LOCKED might leak to other processes which might survive the apt call and thus revert surviving process to not using frontend locking. [Other info] This fix is for backwards compatibility only. Starting with the dd cycle, it will be dropped for the Pre-Install-Pkgs and Pre-Invoke scripts. Potentially for post-invoke as well, if we find a better solution for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796808/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1796081] [NEW] dpkg frontend locking
Public bug reported: [Impact] Frontends of dpkg such as apt and programs using the apt libraries currently acquire the dpkg "lock" lock file. They need to release it before running dpkg, as dpkg also acquires it. Therefore, there is a race condition: In case the application needs to run dpkg multiple times, another application could steal the lock from under it, and the running application would fail in the middle of the install, potentially rendering the system broken. This fixes the problem by introducing an additional "lock-frontend" file that frontends do not release when calling dpkg. When dpkg is not called by a frontend using that file, it will try to acquire the frontend lock as well, preventing it from interfering with such frontends. [Test case] 1. Hold lock, check that dpkg fails to run 2. Hold frontend lock, check that dpkg fails to run 3. Hold frontend lock, run dpkg with DPKG_FRONTEND_LOCKED set, it should succeed [Regression potential] This is an isolated change adding a new lock file. Therefore, regressions can only be expected in the form of that locking failing. [Other info] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html ** Affects: dpkg (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: dpkg (Ubuntu Xenial) Importance: Undecided Status: Triaged ** Affects: dpkg (Ubuntu Bionic) Importance: Undecided Status: Triaged ** Affects: dpkg (Ubuntu Cosmic) Importance: Undecided Status: Fix Released ** Description changed: [Impact] Frontends of dpkg such as apt and programs using the apt libraries currently acquire the dpkg "lock" lock file. They need to release it before running dpkg, as dpkg also acquires it. Therefore, there is a race condition: In case the application needs to run dpkg multiple times, another application could steal the lock from under it, and the running application would fail in the middle of the install, potentially rendering the system broken. This fixes the problem by introducing an additional "lock-frontend" file that frontends do not release when calling dpkg. When dpkg is not called by a frontend using that file, it will try to acquire the frontend lock as well, preventing it from interfering with such frontends. [Test case] 1. Hold lock, check that dpkg fails to run 2. Hold frontend lock, check that dpkg fails to run 3. Hold frontend lock, run dpkg with DPKG_FRONTEND_LOCKED set, it should succeed [Regression potential] This is an isolated change adding a new lock file. Therefore, regressions can only be expected in the form of that locking failing. [Other info] This is part of a wider series of SRUs for frontend locking - - dpkg (this bug) + - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html ** Also affects: dpkg (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: dpkg (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: dpkg (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: dpkg (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: dpkg (Ubuntu Bionic) Status: New => Triaged ** Changed in: dpkg (Ubuntu Xenial) Status: New => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1796081 Title: dpkg frontend locking Status in dpkg package in Ubuntu: Fix Released Status in dpkg source package in Xenial: Triaged Status in dpkg source package in Bionic: Triaged Status in dpkg source package in Cosmic: Fix Released Bug description: [Impact] Frontends of dpkg such as apt and programs using the apt libraries currently acquire the dpkg "lock" lock file. They need to release it before running dpkg, as dpkg also acquires it. Therefore, there is a race condition: In case the application needs to run dpkg multiple times, another application could steal the lock from under it, and the running application would fail in the middle of the install, potentially rendering the system broken. This fixes the problem by introducing an additional "lock-frontend" file that frontends do not release when calling dpkg. When dpkg is not called by a frontend using that file, it will try to acquire the frontend lock as well, preventing it from interfering with such frontends.
[Group.of.nepali.translators] [Bug 1781169] Re: frontend locking
dpkg is moving to its own bug to be able to better track the SRUs ** No longer affects: dpkg (Ubuntu Xenial) ** No longer affects: dpkg (Ubuntu Bionic) ** Summary changed: - frontend locking + apt frontend locking -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1781169 Title: apt frontend locking Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Bug description: [Impact] apt acquires /var/lib/dpkg/lock but has to release it while running dpkg, offering a short window for other clients to acquire the lock. This implements /var/lib/dpkg/lock-frontend which will be acquired earlier and not released by apt for dpkg to run. dpkg will try to acquire the frontend lock as well, unless told not to do so via an environment variable, which apt does; hence concurrent runs of dpkg without other locking can't happen. [Test case] Run strace apt install $something and check that lock-frontend is acquired at the beginning and not released until the end. [Regression potential] Frontend locking failures are in English, as there are no translations yet. More locks also mean more potential for locking to go wrong across programs, but since we don't have any waiting locks we at least won't deadlock. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1790671] Re: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_p
Oh misread, xenial was not affected. ** Changed in: packagekit (Ubuntu Xenial) Status: New => Invalid ** No longer affects: packagekit (Ubuntu Xenial) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1790671 Title: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Bionic: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.1.10-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790671/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1790671] Re: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_p
** Also affects: packagekit (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1790671 Title: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Xenial: New Status in packagekit source package in Bionic: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.1.10-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790671/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1795614] [NEW] packagekit frontend locking
Public bug reported: [Impact] PackageKit needs an adjustment for frontend locking, so it does not release the frontend lock during dpkg invocations, but only the normal dpkg lock. [Test case] 1. Install a package 2. Modify prerm to sleep 3. Remove package via pkcon and check that packagekitd process holds lock-frontend and dpkg holds lock (we release lock by closing the lock files, so just check if the files are open). [Regression potential] Changing the code to call UnLockInner() vs UnLock() makes it do less steps and only release "lock" as before, and not "lock-frontend". That should not be causing any regressions. The patch also adds a call to LockInner() after the dpkg execution to make it reacquire "lock", this could fail. It should not have much impact however, as it only affects a single transaction AFAICT. It does reduce the risk of some frontend not implementing frontend locking from racing while we still hold the frontend lock, though. ** Affects: packagekit (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: packagekit (Ubuntu Xenial) Importance: Undecided Status: Triaged ** Affects: packagekit (Ubuntu Bionic) Importance: Undecided Status: Triaged ** Affects: packagekit (Ubuntu Cosmic) Importance: Undecided Status: Fix Released ** Also affects: packagekit (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: packagekit (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: packagekit (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: packagekit (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: packagekit (Ubuntu Bionic) Status: New => Triaged ** Changed in: packagekit (Ubuntu Xenial) Status: New => Triaged ** Description changed: [Impact] PackageKit needs an adjustment for frontend locking, so it does not release the frontend lock during dpkg invocations, but only the normal dpkg lock. [Test case] 1. Install a package 2. Modify prerm to sleep - 3. Remove package via pkcon and check that packagekitd process holds lock-frontend and dpkg holds lock + 3. Remove package via pkcon and check that packagekitd process holds lock-frontend and dpkg holds lock (we release lock by closing the lock files, so just check if the files are open). [Regression potential] Changing the code to call UnLockInner() vs UnLock() makes it do less steps and only release "lock" as before, and not "lock-frontend". That should not be causing any regressions. The patch also adds a call to LockInner() after the dpkg execution to make it reacquire "lock", this could fail. It should not have much impact however, as it only affects a single transaction AFAICT. It does reduce the risk of some frontend not implementing frontend locking from racing while we still hold the frontend lock, though. -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1795614 Title: packagekit frontend locking Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Xenial: Triaged Status in packagekit source package in Bionic: Triaged Status in packagekit source package in Cosmic: Fix Released Bug description: [Impact] PackageKit needs an adjustment for frontend locking, so it does not release the frontend lock during dpkg invocations, but only the normal dpkg lock. [Test case] 1. Install a package 2. Modify prerm to sleep 3. Remove package via pkcon and check that packagekitd process holds lock-frontend and dpkg holds lock (we release lock by closing the lock files, so just check if the files are open). [Regression potential] Changing the code to call UnLockInner() vs UnLock() makes it do less steps and only release "lock" as before, and not "lock-frontend". That should not be causing any regressions. The patch also adds a call to LockInner() after the dpkg execution to make it reacquire "lock", this could fail. It should not have much impact however, as it only affects a single transaction AFAICT. It does reduce the risk of some frontend not implementing frontend locking from racing while we still hold the frontend lock, though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1795614/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1795407] [NEW] python-apt frontend locking
Public bug reported: [Impact] foo [Test case] bar [Regression potential] baz ** Affects: python-apt (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: python-apt (Ubuntu Xenial) Importance: Undecided Status: Triaged ** Affects: python-apt (Ubuntu Bionic) Importance: Undecided Status: Triaged ** Also affects: python-apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu) Status: New => Fix Released ** Changed in: python-apt (Ubuntu Xenial) Status: New => Triaged ** Changed in: python-apt (Ubuntu Bionic) Status: New => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1795407 Title: python-apt frontend locking Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Triaged Status in python-apt source package in Bionic: Triaged Bug description: [Impact] foo [Test case] bar [Regression potential] baz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1795407/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1781169] Re: frontend locking
** No longer affects: dpkg (Ubuntu) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1781169 Title: frontend locking Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: In Progress Status in dpkg source package in Xenial: New Status in apt source package in Bionic: In Progress Status in dpkg source package in Bionic: New Bug description: [Impact] apt acquires /var/lib/dpkg/lock but has to release it while running dpkg, offering a short window for other clients to acquire the lock. This implements /var/lib/dpkg/lock-frontend which will be acquired earlier and not released by apt for dpkg to run. dpkg will try to acquire the frontend lock as well, unless told not to do so via an environment variable, which apt does; hence concurrent runs of dpkg without other locking can't happen. [Test case] Run strace apt install $something and check that lock-frontend is acquired at the beginning and not released until the end. [Regression potential] Frontend locking failures are in English, as there are no translations yet. More locks also mean more potential for locking to go wrong across programs, but since we don't have any waiting locks we at least won't deadlock. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1794053] [NEW] pkgCacheFile unlocks in destructor even if it did not acquire lock
Public bug reported:
[Impact]
Closing a cache file unlocks the system (loses the lock). This randomly breaks
ubuntu-make, for example.
[Test case]
The following Python code fails, but should succeed, as it locks first, opens a
cache and closes it, and then unlocks.
import apt_pkg, os, gc
apt_pkg.init()
apt_pkg.pkgsystem_lock()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.Cache()
gc.collect()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.pkgsystem_unlock()
[Regression potential]
This fixes a regression introduced in 2001 by
commit b2e465d6d32d2dc884f58b94acb7e35f671a87fe
Author: Arch Librarian
Date: Mon Sep 20 16:56:32 2004 +
Join with aliencode
Author: jgg
Date: 2001-02-20 07:03:16 GMT
Join with aliencode
The fix is to only UnLock from the cache file if the cache file locked
before. It's unclear how far code relies on that regression. That said,
any potential regression should be easily noticable, as it would be a
case of not unlocking where we were unlocking before.
** Affects: apt (Ubuntu)
Importance: High
Assignee: Julian Andres Klode (juliank)
Status: In Progress
** Affects: apt (Ubuntu Trusty)
Importance: High
Status: Triaged
** Affects: apt (Ubuntu Xenial)
Importance: High
Status: Triaged
** Affects: apt (Ubuntu Bionic)
Importance: High
Status: Triaged
** Affects: apt (Ubuntu Cosmic)
Importance: High
Assignee: Julian Andres Klode (juliank)
Status: In Progress
** Changed in: apt (Ubuntu)
Importance: Undecided => High
** Changed in: apt (Ubuntu)
Status: New => In Progress
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Cosmic)
Importance: High
Assignee: Julian Andres Klode (juliank)
Status: In Progress
** Also affects: apt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: apt (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: apt (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: apt (Ubuntu Trusty)
Status: New => Triaged
** Changed in: apt (Ubuntu Xenial)
Status: New => Triaged
** Changed in: apt (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1794053
Title:
pkgCacheFile unlocks in destructor even if it did not acquire lock
Status in apt package in Ubuntu:
In Progress
Status in apt source package in Trusty:
Triaged
Status in apt source package in Xenial:
Triaged
Status in apt source package in Bionic:
Triaged
Status in apt source package in Cosmic:
In Progress
Bug description:
[Impact]
Closing a cache file unlocks the system (loses the lock). This randomly
breaks ubuntu-make, for example.
[Test case]
The following Python code fails, but should succeed, as it locks first, opens
a cache and closes it, and then unlocks.
import apt_pkg, os, gc
apt_pkg.init()
apt_pkg.pkgsystem_lock()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.Cache()
gc.collect()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.pkgsystem_unlock()
[Regression potential]
This fixes a regression introduced in 2001 by
commit b2e465d6d32d2dc884f58b94acb7e35f671a87fe
Author: Arch Librarian
Date: Mon Sep 20 16:56:32 2004 +
Join with aliencode
Author: jgg
Date: 2001-02-20 07:03:16 GMT
Join with aliencode
The fix is to only UnLock from the cache file if the cache file locked
before. It's unclear how far code relies on that regression. That
said, any potential regression should be easily noticable, as it would
be a case of not unlocking where we were unlocking before.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794053/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1667512] Re: [SRU] update-initramfs should sync only the filesystem containing the initramfs image
** Also affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1667512 Title: [SRU] update-initramfs should sync only the filesystem containing the initramfs image Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: New Status in initramfs-tools package in Debian: Fix Released Bug description: [Impact] If there is lots of activity on a different filesystem, high io/cache pressure, or a stale mount updating initramfs might hang because the update-initramfs script calls sync. This leaves the system unresponsive and will require the user to forcefully kill dpkg. [Test Case] One easy way to simulate this is by copying a huge file over nfs. Note: do not use localhost, it is too fast for this purpose, a network bridge over qemu is good enough. 1. Setup a nfs server and export a directory with write permissions for the client 2. Copy a big file over NFS (assumes it is mounted at /mnt in the client) $ dd if=/dev/zero of=/mnt/big_zeros bs=512 count=1M status=progress Note: adjust the "count" accordingly to how fast/slow your system is. 3. Call sync and verify that it only finished after "dd" is done. 4. Repeat step #2 and now call "sync -f /boot/". Verify that it finished immediatly. [Regression Potential] Although syncfs(2) man page [2] states that it works just the same as sync - except being limited to a filesystem -, any actual differences in the implementation can affect how the initrd image file is synced to the disk, leading to unexpected behavior. [Other] If syncfs is unsupported then the 'sync' binary will ensure that a normal system-wide sync is called [1]. The proposed patch won't help in scenarios where the initrd file is located in a busy filesystem (eg. no separated /boot partition). The 'sync' and 'syncfs' specifications are pretty much similar and syncfs is expected to work the same as a normal sync regarding data integrity. Also altought the patch introduces the initrd file as an extra argument which would cause 'sync -f' to fail if the file does not exist, the update-initramfs script would fail earlier than that because that file is created by the 'mv' call a few lines above. Thus no regressions are expected. [References] [1] http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/sync.c?id=8b2bf5295f353016d4f5e6a2317d55b6a8e7fd00 [2] http://manpages.ubuntu.com/manpages/xenial/man2/syncfs.2.html [Original bug report] At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. vmlinuz(/boot/vmlinuz-4.4.0-63-generic ) points to
[Group.of.nepali.translators] [Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution
Nothing actionable here for apt, so I'll close this. We should consider making frontend locking more flexible for scripts using apt, though, so scripts can hold the lock all the time and drive apt. ** Changed in: apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1693361 Title: cloud-init sometimes fails on dpkg lock due to concurrent apt- daily.service execution Status in APT: Confirmed Status in cloud-init: Fix Released Status in apt package in Ubuntu: Invalid Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Yakkety: Won't Fix Status in cloud-init source package in Zesty: Fix Released Status in cloud-init source package in Artful: Fix Released Bug description: === Begin SRU Template === [Impact] A cloud-config that contains packages to install (see below) or 'package_upgrade' will run 'apt-get update'. That can sometimes fail as a result of contention with the apt-daily.service that updates that information. Cloud-config showing the problem is just like: $ cat my.yaml #cloud-config packages: ['hello'] [Test Case] lxc-proposed-snapshot is https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot It publishes an image to lxd with proposed enabled and cloud-init upgraded. a.) launch an instance with proposed version of cloud-init and some user-data. This is platform independent. The test case demonstrates lxd. $ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \ "package_upgrade: true" > config.yaml $ release=xenial $ ref=proposed-$release $ ./lxc-proposed-snapshot --proposed --publish $release $ref; b.) start the instance $ name=$release-1693361 $ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml) $ sleep 1 $ lxc exec $name -- tail -f /var/log/cloud-init.log /var/log/cloud-init-output.log # watch this boot. c.) Look for evidence of systemd failure journalctl -o short-precise | grep -i break journalctl -o short-precise | grep -i order [Regression Potential] Regression chance here is low. Its possible that ordering loops could occur. When that does happen, journalctl will mention it. Unfortunately in such cases systemd somewhat randomly picks a service to kil so behavior is somewhat undefined. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=11121fe4 === End SRU Template === apt-daily is now a systemd service rather than being invoked by cron.daily. If one builds a custom AMI it is possible that the apt- daily.timer will fire during boot. This can fire at the same time cloud-init is running and if cloud-init loses the race the invocation of apt (e.g. use of "packages:" in the config) will fail. There is a lot of discussion online about this change to apt-daily (e.g. unattended upgrades happening during business hours, delaying boot, etc.) and discussion of potential systemd changes regarding timers firing during boot (c.f. https://github.com/systemd/systemd/issues/5659). While it would be better to solve this in apt itself, I suggest that cloud-init be defensive when calling apt and implement some retry mechanism. Various instances of people running into this issue: https://github.com/chef/bento/issues/609 https://clusterhq.atlassian.net/browse/FLOC-4486 https://github.com/boxcutter/ubuntu/issues/73 https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1693361/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1778547] Re: Broken system lock counting
Fixed in 1.7.0~alpha1 in cosmic
** Changed in: apt (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1778547
Title:
Broken system lock counting
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Released
Status in apt source package in Artful:
Fix Released
Status in apt source package in Bionic:
Fix Released
Bug description:
[Impact]
System lock unrefing is broken, off-by-one error. Locking twice opens a
second fd for the lock file, and the old fd gets lost and remains open for the
remaining duration of the program
[Test case]
Executing the following script should show one lock file in the first
line, and none in the last line.
def maybe_readlink(path):
try:
return os.readlink(path)
except:
return ""
import os, apt_pkg
apt_pkg.init()
apt_pkg.pkgsystem_lock()
apt_pkg.pkgsystem_lock()
print([(p, maybe_readlink("/proc/self/fd/" + p)) for p in
os.listdir("/proc/self/fd")])
apt_pkg.pkgsystem_unlock()
apt_pkg.pkgsystem_unlock()
print([(p, maybe_readlink("/proc/self/fd/" + p)) for p in
os.listdir("/proc/self/fd")])
[Test output]
good, cosmic:
[('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3',
'/var/lib/dpkg/lock'), ('4', '')]
[('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3',
'')]
bad, bionic:
[('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3',
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', '/var/lib/dpkg/lock'),
('6', ''), ('17', 'socket:[53931]')]
[('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3',
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17',
'socket:[53931]')]
[Regression potential]
A locking change can potentially break locking, but this one seems like an
obvious off-by-one error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778547/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-menus (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu Bionic) Status: New => Triaged ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-release-upgrader (Ubuntu Xenial) Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Triaged Status in gnome-menus source package in Xenial: Confirmed Status in ubuntu-release-upgrader source package in Xenial: Invalid Status in gnome-menus source package in Bionic: New Status in ubuntu-release-upgrader source package in Bionic: Triaged Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press
[Group.of.nepali.translators] [Bug 1778738] Re: Default to early instead of auto when MODULES=most
Same for bionic with: Get:17 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 intel-microcode amd64 3.20180425.1~ubuntu0.18.04.2 [1143 kB] Get:18 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 amd64-microcode amd64 3.20180524.1~ubuntu0.18.04.2 [32.3 kB] ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Changed in: intel-microcode (Ubuntu Artful) Status: Fix Committed => Won't Fix ** Changed in: amd64-microcode (Ubuntu Artful) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1778738 Title: Default to early instead of auto when MODULES=most Status in amd64-microcode package in Ubuntu: Fix Released Status in intel-microcode package in Ubuntu: Fix Released Status in amd64-microcode source package in Trusty: Triaged Status in intel-microcode source package in Trusty: Fix Committed Status in amd64-microcode source package in Xenial: Fix Committed Status in intel-microcode source package in Xenial: Fix Committed Status in amd64-microcode source package in Artful: Won't Fix Status in intel-microcode source package in Artful: Won't Fix Status in amd64-microcode source package in Bionic: Fix Committed Status in intel-microcode source package in Bionic: Fix Committed Bug description: [Impact] Initramfs for MODULES=most should build with all microcodes installed [Test case] Have both amd64-microcode and intel-microcode installed, and MODULES=most set. Test generated initramfs in both amd64 and intel machines and make sure the microcodes load. If that's not feasible, we should at least run update-initramfs with -v and ensure that it says the right things: I: amd64-microcode: installing AMD64 microcode into the early initramfs... intel-microcode: adding microcode for either all or selected Intel processor models [long list of microcodes] [Regression potential] Some tools will fail to understand the initramfs, as it now has two cpio archives prepended (e.g. lsinitramfs skips intel microcode archive, as seen in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886424) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1778738/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
guile-2.2 is also affected by these triggers, but probably not that urgent, as it's not in xenial and not used as much as 2.0 in bionic/cosmic. ** Changed in: guile-2.2 (Ubuntu) Status: New => Triaged ** Changed in: guile-2.2 (Ubuntu Xenial) Status: New => Triaged ** Changed in: guile-2.2 (Ubuntu Bionic) Status: New => Triaged ** No longer affects: guile-2.2 (Ubuntu Xenial) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in django-countries package in Ubuntu: Fix Released Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: Fix Released Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: Won't Fix Status in guile-2.0 package in Ubuntu: In Progress Status in guile-2.2 package in Ubuntu: Triaged Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: Triaged Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: Fix Released Status in neurodebian package in Ubuntu: Fix Released Status in nevow package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: Fix Released Status in pike8.0 package in Ubuntu: Fix Released Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: Won't Fix Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in bumblebee source package in Xenial: Fix Committed Status in clutter-imcontext source package in Xenial: Won't Fix Status in django-countries source package in Xenial: In Progress Status in dochelp source package in Xenial: Fix Committed Status in dovecot source package in Xenial: In Progress Status in fusiondirectory source package in Xenial: In Progress Status in gdk-pixbuf source package in Xenial: Fix Committed Status in glib2.0 source package in Xenial: Fix Committed Status in gosa source package in Xenial: Won't Fix Status in guile-2.0 source package in Xenial: Triaged Status in hicolor-icon-theme source package in Xenial: Fix Committed Status in libomxil-bellagio source package in Xenial: Triaged Status in libreoffice source package in Xenial: Triaged Status in ltsp source package in Xenial: In Progress Status in mate-icon-theme source package in Xenial: Fix Committed Status in maxima source package in Xenial: Fix Committed Status in neurodebian source package in Xenial: Fix Committed Status in nevow source package in Xenial: Fix Committed Status in octave source package in Xenial: Fix Committed Status in packagekit source package in Xenial: Fix Committed Status in pike7.8 source package in Xenial: In Progress Status in pike8.0 source package in Xenial: In Progress Status in postgresql-common source package in Xenial: Fix Committed Status in qgis source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: Won't Fix Status in shared-mime-info source package in Xenial: Fix Committed Status in sphinx source package in Xenial: Fix Committed Status in syslog-ng-incubator source package in Xenial: In Progress Status in tex-common source package in Xenial: Fix Committed Status in wokkel source package in Xenial: In Progress Status in xpdf source package in Xenial: Fix Committed Status in yorick source package in Xenial: Fix Committed Status in appstream source package in Bionic: Fix Released Status in bumblebee source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in django-countries source package in Bionic: Fix Released Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in Bionic: In Progress Status in gdk-pixbuf source package
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
** Also affects: guile-2.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in django-countries package in Ubuntu: Fix Released Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: Fix Released Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: Won't Fix Status in guile-2.0 package in Ubuntu: Triaged Status in guile-2.2 package in Ubuntu: Triaged Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: Triaged Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: Fix Released Status in neurodebian package in Ubuntu: Fix Released Status in nevow package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: Fix Released Status in pike8.0 package in Ubuntu: Fix Released Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: Won't Fix Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in bumblebee source package in Xenial: Fix Committed Status in clutter-imcontext source package in Xenial: Won't Fix Status in django-countries source package in Xenial: In Progress Status in dochelp source package in Xenial: Fix Committed Status in dovecot source package in Xenial: In Progress Status in fusiondirectory source package in Xenial: In Progress Status in gdk-pixbuf source package in Xenial: Fix Committed Status in glib2.0 source package in Xenial: Fix Committed Status in gosa source package in Xenial: Won't Fix Status in guile-2.0 source package in Xenial: Triaged Status in hicolor-icon-theme source package in Xenial: Fix Committed Status in libomxil-bellagio source package in Xenial: Triaged Status in libreoffice source package in Xenial: Triaged Status in ltsp source package in Xenial: In Progress Status in mate-icon-theme source package in Xenial: Fix Committed Status in maxima source package in Xenial: Fix Committed Status in neurodebian source package in Xenial: Fix Committed Status in nevow source package in Xenial: Fix Committed Status in octave source package in Xenial: Fix Committed Status in packagekit source package in Xenial: Fix Committed Status in pike7.8 source package in Xenial: In Progress Status in pike8.0 source package in Xenial: In Progress Status in postgresql-common source package in Xenial: Fix Committed Status in qgis source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: Won't Fix Status in shared-mime-info source package in Xenial: Fix Committed Status in sphinx source package in Xenial: Fix Committed Status in syslog-ng-incubator source package in Xenial: In Progress Status in tex-common source package in Xenial: Fix Committed Status in wokkel source package in Xenial: In Progress Status in xpdf source package in Xenial: Fix Committed Status in yorick source package in Xenial: Fix Committed Status in appstream source package in Bionic: Fix Released Status in bumblebee source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in django-countries source package in Bionic: Fix Released Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in Bionic: In Progress Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: Won't Fix Status in guile-2.0 source package in Bionic: Triaged Status in guile-2.2 source package in Bionic: Triaged Status in hicolor-icon-theme source package in Bionic: Fix Released
[Group.of.nepali.translators] [Bug 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies
Cherry-picked the change into xenial's 1.2.y branch for the next SRU. Will do that in trusty too. ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Xenial) Status: New => Triaged ** Changed in: apt (Ubuntu Trusty) Status: New => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1698159 Title: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in unattended-upgrades source package in Trusty: New Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: New Status in apt source package in Bionic: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: When running kernel version 4.4.0-78 (for example) and the unattended- upgrade packages installs a new kernel 4.4.0-79 (for example) the linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic packages are removed by the Remove-Unused-Dependencies rule, because unlike "normal" kernel packages they are not excluded by /etc/apt/apt.conf.d/01autoremove-kernels. The linux-cloud-tools package has the hyper-v integration services daemons in it, so it's deletion leaves some of the integration not working. Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other hyper-v users aren't caught out by this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.6 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 15 15:27:35 2017 InstallationDate: Installed on 2016-04-25 (415 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: [modified] modified.conffile..etc.update-motd.d.90-updates-available: [deleted] modified.conffile..etc.update-motd.d.98-fsck-at-reboot: [deleted] modified.conffile..etc.update-motd.d.98-reboot-required: [deleted] mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-04-25T16:28:36.64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1698159/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
Nothing installs the files that trigger reconf-inetd, so not fixing that. ** Changed in: reconf-inetd (Ubuntu) Status: Triaged => Won't Fix ** Changed in: reconf-inetd (Ubuntu Bionic) Status: Triaged => Won't Fix ** Changed in: reconf-inetd (Ubuntu Xenial) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in django-countries package in Ubuntu: Fix Released Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: Fix Released Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: Won't Fix Status in guile-2.0 package in Ubuntu: Triaged Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: Triaged Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: Fix Released Status in neurodebian package in Ubuntu: Fix Released Status in nevow package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: Fix Released Status in pike8.0 package in Ubuntu: Fix Released Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: Won't Fix Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in bumblebee source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in django-countries source package in Xenial: In Progress Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: In Progress Status in fusiondirectory source package in Xenial: In Progress Status in gdk-pixbuf source package in Xenial: Fix Committed Status in glib2.0 source package in Xenial: Fix Committed Status in gosa source package in Xenial: Won't Fix Status in guile-2.0 source package in Xenial: Triaged Status in hicolor-icon-theme source package in Xenial: Fix Committed Status in libomxil-bellagio source package in Xenial: Triaged Status in libreoffice source package in Xenial: Triaged Status in ltsp source package in Xenial: In Progress Status in mate-icon-theme source package in Xenial: Fix Committed Status in maxima source package in Xenial: In Progress Status in neurodebian source package in Xenial: In Progress Status in nevow source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: Fix Committed Status in pike7.8 source package in Xenial: In Progress Status in pike8.0 source package in Xenial: In Progress Status in postgresql-common source package in Xenial: In Progress Status in qgis source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: Won't Fix Status in shared-mime-info source package in Xenial: Fix Committed Status in sphinx source package in Xenial: Fix Committed Status in syslog-ng-incubator source package in Xenial: In Progress Status in tex-common source package in Xenial: Fix Committed Status in wokkel source package in Xenial: In Progress Status in xpdf source package in Xenial: Fix Committed Status in yorick source package in Xenial: Fix Committed Status in appstream source package in Bionic: Fix Released Status in bumblebee source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in django-countries source package in Bionic: Fix Released Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in Bionic: In Progress Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: Won't Fix Status in guile-2.0
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
Marking gosa as Won't fix, as newer versions moved to interest-await explicitly. The plugins depend on gosa, so the trigger being await is fine. ** Changed in: gosa (Ubuntu) Status: In Progress => Won't Fix ** Changed in: gosa (Ubuntu) Assignee: Łukasz Zemczak (sil2100) => (unassigned) ** Changed in: gosa (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: gosa (Ubuntu Bionic) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in django-countries package in Ubuntu: Fix Released Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: Fix Released Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: Won't Fix Status in guile-2.0 package in Ubuntu: Triaged Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: Triaged Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: Fix Released Status in neurodebian package in Ubuntu: Fix Released Status in nevow package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: Fix Released Status in pike8.0 package in Ubuntu: Fix Released Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: Won't Fix Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in bumblebee source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in django-countries source package in Xenial: In Progress Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: In Progress Status in fusiondirectory source package in Xenial: In Progress Status in gdk-pixbuf source package in Xenial: Fix Committed Status in glib2.0 source package in Xenial: Fix Committed Status in gosa source package in Xenial: Won't Fix Status in guile-2.0 source package in Xenial: Triaged Status in hicolor-icon-theme source package in Xenial: Fix Committed Status in libomxil-bellagio source package in Xenial: Triaged Status in libreoffice source package in Xenial: Triaged Status in ltsp source package in Xenial: In Progress Status in mate-icon-theme source package in Xenial: Fix Committed Status in maxima source package in Xenial: In Progress Status in neurodebian source package in Xenial: In Progress Status in nevow source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: Fix Committed Status in pike7.8 source package in Xenial: In Progress Status in pike8.0 source package in Xenial: In Progress Status in postgresql-common source package in Xenial: In Progress Status in qgis source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: Won't Fix Status in shared-mime-info source package in Xenial: Fix Committed Status in sphinx source package in Xenial: Fix Committed Status in syslog-ng-incubator source package in Xenial: In Progress Status in tex-common source package in Xenial: Fix Committed Status in wokkel source package in Xenial: In Progress Status in xpdf source package in Xenial: Fix Committed Status in yorick source package in Xenial: Fix Committed Status in appstream source package in Bionic: Fix Released Status in bumblebee source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in django-countries source package in Bionic: Fix Released Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in Bionic: In Progress Status in gdk-pixbuf source package in Bionic: Fix Released
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: pike7.8 (Ubuntu Xenial) Status: New => In Progress ** Changed in: pike7.8 (Ubuntu Xenial) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: pike8.0 (Ubuntu) Status: New => Fix Released ** Changed in: pike8.0 (Ubuntu Bionic) Status: New => Fix Released ** Changed in: pike8.0 (Ubuntu Xenial) Status: New => In Progress ** Changed in: pike8.0 (Ubuntu Xenial) Assignee: (unassigned) => Julian Andres Klode (juliank) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in django-countries package in Ubuntu: Fix Released Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: Fix Released Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: Fix Released Status in neurodebian package in Ubuntu: Fix Released Status in nevow package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: Fix Released Status in pike8.0 package in Ubuntu: Fix Released Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in bumblebee source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in django-countries source package in Xenial: In Progress Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: In Progress Status in fusiondirectory source package in Xenial: In Progress Status in gdk-pixbuf source package in Xenial: Fix Committed Status in glib2.0 source package in Xenial: Fix Committed Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: Fix Committed Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in ltsp source package in Xenial: In Progress Status in mate-icon-theme source package in Xenial: Fix Committed Status in maxima source package in Xenial: In Progress Status in neurodebian source package in Xenial: In Progress Status in nevow source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: Fix Committed Status in pike7.8 source package in Xenial: In Progress Status in pike8.0 source package in Xenial: In Progress Status in postgresql-common source package in Xenial: In Progress Status in qgis source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: Fix Committed Status in sphinx source package in Xenial: Fix Committed Status in syslog-ng-incubator source package in Xenial: In Progress Status in tex-common source package in Xenial: Fix Committed Status in wokkel source package in Xenial: In Progress Status in xpdf source package in Xenial: Fix Committed Status in yorick source package in Xenial: Fix Committed Status in appstream source package in Bionic: Fix Released Status in bumblebee source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in django-countries source package in Bionic: Fix Released Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in Bionic: In Progress Status in gdk-pix
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: pike7.8 (Ubuntu) Status: New => Fix Released ** Changed in: pike7.8 (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in django-countries package in Ubuntu: Fix Released Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: Fix Released Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: Fix Released Status in neurodebian package in Ubuntu: Fix Released Status in nevow package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: Fix Released Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in bumblebee source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in django-countries source package in Xenial: In Progress Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: In Progress Status in fusiondirectory source package in Xenial: In Progress Status in gdk-pixbuf source package in Xenial: Fix Committed Status in glib2.0 source package in Xenial: Fix Committed Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: Fix Committed Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in ltsp source package in Xenial: In Progress Status in mate-icon-theme source package in Xenial: Fix Committed Status in maxima source package in Xenial: In Progress Status in neurodebian source package in Xenial: In Progress Status in nevow source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: Fix Committed Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in qgis source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: Fix Committed Status in sphinx source package in Xenial: Fix Committed Status in syslog-ng-incubator source package in Xenial: In Progress Status in tex-common source package in Xenial: Fix Committed Status in wokkel source package in Xenial: In Progress Status in xpdf source package in Xenial: Fix Committed Status in yorick source package in Xenial: Fix Committed Status in appstream source package in Bionic: Fix Released Status in bumblebee source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in django-countries source package in Bionic: Fix Released Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in Bionic: In Progress Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: syslog-ng-incubator (Ubuntu) Status: In Progress => Fix Released ** Changed in: bumblebee (Ubuntu Bionic) Status: New => Fix Released ** Changed in: django-countries (Ubuntu Bionic) Status: New => Fix Released ** Changed in: maxima (Ubuntu Bionic) Status: New => Fix Released ** Changed in: neurodebian (Ubuntu Bionic) Status: New => Fix Released ** Changed in: nevow (Ubuntu Bionic) Status: New => Fix Released ** Changed in: qgis (Ubuntu Bionic) Status: New => Fix Released ** Changed in: syslog-ng-incubator (Ubuntu Bionic) Status: New => Fix Released ** Changed in: ltsp (Ubuntu) Status: In Progress => Fix Released ** Changed in: ltsp (Ubuntu Bionic) Status: New => Fix Released ** Changed in: ltsp (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in django-countries package in Ubuntu: Fix Released Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: Fix Released Status in neurodebian package in Ubuntu: Fix Released Status in nevow package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in bumblebee source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in django-countries source package in Xenial: In Progress Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: In Progress Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: Fix Committed Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in ltsp source package in Xenial: In Progress Status in mate-icon-theme source package in Xenial: In Progress Status in maxima source package in Xenial: In Progress Status in neurodebian source package in Xenial: In Progress Status in nevow source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in qgis source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in syslog-ng-incubator source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in wokkel source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in bumblebee source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: wokkel (Ubuntu Xenial) Status: New => In Progress ** Changed in: wokkel (Ubuntu Bionic) Status: New => In Progress ** Changed in: wokkel (Ubuntu) Status: In Progress => Fix Released ** Changed in: bumblebee (Ubuntu Xenial) Status: New => In Progress ** Changed in: django-countries (Ubuntu Xenial) Status: New => In Progress ** Changed in: maxima (Ubuntu Xenial) Status: New => In Progress ** Changed in: neurodebian (Ubuntu Xenial) Status: New => In Progress ** Changed in: nevow (Ubuntu Xenial) Status: New => In Progress ** Changed in: qgis (Ubuntu Xenial) Status: New => In Progress ** Changed in: syslog-ng-incubator (Ubuntu Xenial) Status: New => In Progress ** Changed in: bumblebee (Ubuntu) Status: In Progress => Fix Released ** Changed in: django-countries (Ubuntu) Status: In Progress => Fix Released ** Changed in: maxima (Ubuntu) Status: In Progress => Fix Released ** Changed in: neurodebian (Ubuntu) Status: In Progress => Fix Released ** Changed in: nevow (Ubuntu) Status: In Progress => Fix Released ** Changed in: qgis (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in django-countries package in Ubuntu: Fix Released Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: Fix Released Status in neurodebian package in Ubuntu: Fix Released Status in nevow package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in bumblebee source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in django-countries source package in Xenial: In Progress Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: In Progress Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: Fix Committed Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in ltsp source package in Xenial: In Progress Status in mate-icon-theme source package in Xenial: In Progress Status in maxima source package in Xenial: In Progress Status in neurodebian source package in Xenial: In Progress Status in nevow source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in qgis source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in syslog-ng-incubator source package in Xenial: In Progress Status in tex-common source package in Xenial: In
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: dochelp (Ubuntu Xenial) Status: New => Triaged ** Changed in: dochelp (Ubuntu Xenial) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: dochelp (Ubuntu) Status: New => Fix Released ** Changed in: dochelp (Ubuntu Bionic) Status: New => Fix Released ** Changed in: dochelp (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: Fix Released Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the po
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
clutter-imcontext declares an interest on /usr/lib/clutter- imcontext/immodules, but no package ships files in there, so not fixing that in a stable release. Not sure about devel. ** Changed in: clutter-imcontext (Ubuntu Xenial) Status: Triaged => Won't Fix ** Changed in: clutter-imcontext (Ubuntu Bionic) Status: Triaged => Won't Fix ** Changed in: yorick (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: Fix Released Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: postgresql-common (Ubuntu Xenial) Status: New => Triaged ** Changed in: postgresql-common (Ubuntu Xenial) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: postgresql-common (Ubuntu Bionic) Status: New => Fix Released ** Changed in: postgresql-common (Ubuntu) Status: New => Fix Released ** Changed in: postgresql-common (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Triaged Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Triaged Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: New Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the po
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
Turns out goopg was not affected, it does not exist in xenial.
** No longer affects: goopg (Ubuntu)
** No longer affects: goopg (Ubuntu Bionic)
** No longer affects: goopg (Ubuntu Xenial)
** Changed in: packagekit (Ubuntu)
Status: New => Fix Released
** Changed in: packagekit (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: packagekit (Ubuntu Xenial)
Status: New => In Progress
** Changed in: appstream (Ubuntu Xenial)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: appstream (Ubuntu)
Assignee: Julian Andres Klode (juliank) => (unassigned)
** Changed in: gdk-pixbuf (Ubuntu Xenial)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: gdk-pixbuf (Ubuntu)
Assignee: Julian Andres Klode (juliank) => (unassigned)
** Changed in: glib2.0 (Ubuntu)
Assignee: Julian Andres Klode (juliank) => (unassigned)
** Changed in: glib2.0 (Ubuntu Xenial)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: hicolor-icon-theme (Ubuntu Xenial)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: hicolor-icon-theme (Ubuntu)
Assignee: Julian Andres Klode (juliank) => (unassigned)
** Changed in: mate-icon-theme (Ubuntu Xenial)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: mate-icon-theme (Ubuntu)
Assignee: Julian Andres Klode (juliank) => (unassigned)
** Changed in: packagekit (Ubuntu Xenial)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: shared-mime-info (Ubuntu Xenial)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: shared-mime-info (Ubuntu)
Assignee: Julian Andres Klode (juliank) => (unassigned)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1780996
Title:
Convert triggers to noawait
Status in appstream package in Ubuntu:
Fix Released
Status in clutter-imcontext package in Ubuntu:
New
Status in dochelp package in Ubuntu:
New
Status in dovecot package in Ubuntu:
New
Status in fusiondirectory package in Ubuntu:
New
Status in gdk-pixbuf package in Ubuntu:
Fix Released
Status in glib2.0 package in Ubuntu:
Fix Released
Status in gosa package in Ubuntu:
New
Status in guile-2.0 package in Ubuntu:
New
Status in hicolor-icon-theme package in Ubuntu:
Fix Released
Status in libomxil-bellagio package in Ubuntu:
New
Status in libreoffice package in Ubuntu:
Fix Released
Status in mate-icon-theme package in Ubuntu:
Fix Released
Status in octave package in Ubuntu:
New
Status in packagekit package in Ubuntu:
Fix Released
Status in pike7.8 package in Ubuntu:
New
Status in pike8.0 package in Ubuntu:
New
Status in postgresql-common package in Ubuntu:
New
Status in reconf-inetd package in Ubuntu:
New
Status in shared-mime-info package in Ubuntu:
Fix Released
Status in sphinx package in Ubuntu:
Fix Released
Status in tex-common package in Ubuntu:
Fix Released
Status in xpdf package in Ubuntu:
Fix Released
Status in yorick package in Ubuntu:
Fix Released
Status in appstream source package in Xenial:
In Progress
Status in clutter-imcontext source package in Xenial:
New
Status in dochelp source package in Xenial:
New
Status in dovecot source package in Xenial:
New
Status in fusiondirectory source package in Xenial:
New
Status in gdk-pixbuf source package in Xenial:
In Progress
Status in glib2.0 source package in Xenial:
In Progress
Status in gosa source package in Xenial:
New
Status in guile-2.0 source package in Xenial:
New
Status in hicolor-icon-theme source package in Xenial:
In Progress
Status in libomxil-bellagio source package in Xenial:
New
Status in libreoffice source package in Xenial:
Triaged
Status in mate-icon-theme source package in Xenial:
In Progress
Status in octave source package in Xenial:
New
Status in packagekit source package in Xenial:
In Progress
Status in pike7.8 source package in Xenial:
New
Status in pike8.0 source package in Xenial:
New
Status in postgresql-common source package in Xenial:
New
Status in reconf-inetd source package in Xenial:
New
Status in shared-mime-info source package in Xenial:
In Progress
Status in sphinx source package in Xenial:
In Progress
Status in tex-common source package in Xenial:
In Progress
Status in xpdf source package in Xenial:
In Progress
Status in yorick source package in Xenial:
In Progress
Status in appstream source package in Bionic:
Fix Released
Status in clutter-imcontext source package in Bionic:
New
Status in dochelp source package in Bionic:
New
Status in dovecot source package in Bionic:
New
Status in fusiondirectory source package in Bionic:
New
Status in gdk-pixbuf source package in Bionic:
Fix Released
Status in
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: gdk-pixbuf (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: gdk-pixbuf (Ubuntu) Status: New => Fix Released ** Changed in: gdk-pixbuf (Ubuntu Bionic) Status: New => Fix Released ** Changed in: gdk-pixbuf (Ubuntu Xenial) Status: New => In Progress ** Changed in: shared-mime-info (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: shared-mime-info (Ubuntu) Status: New => Fix Released ** Changed in: shared-mime-info (Ubuntu Bionic) Status: New => Fix Released ** Changed in: shared-mime-info (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: New Status in packagekit source package in Bionic: New Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: mate-icon-theme (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: mate-icon-theme (Ubuntu) Status: New => Fix Released ** Changed in: mate-icon-theme (Ubuntu Bionic) Status: New => Fix Released ** Changed in: mate-icon-theme (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: New Status in glib2.0 package in Ubuntu: Fix Released Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Status in sphinx package in Ubuntu: New Status in tex-common package in Ubuntu: New Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: New Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: New Status in glib2.0 source package in Xenial: In Progress Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: New Status in sphinx source package in Xenial: New Status in tex-common source package in Xenial: New Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: New Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: New Status in glib2.0 source package in Bionic: Fix Released Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: New Status in packagekit source package in Bionic: New Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: New Status in sphinx source package in Bionic: New Status in tex-common source package in Bionic: New Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: New Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configur
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: appstream (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: appstream (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: glib2.0 (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: glib2.0 (Ubuntu Bionic) Status: New => Fix Released ** Changed in: glib2.0 (Ubuntu) Status: New => Fix Released ** Changed in: glib2.0 (Ubuntu Xenial) Status: New => In Progress ** Changed in: hicolor-icon-theme (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: hicolor-icon-theme (Ubuntu) Status: New => Fix Released ** Changed in: hicolor-icon-theme (Ubuntu Bionic) Status: New => Fix Released ** Changed in: hicolor-icon-theme (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: New Status in glib2.0 package in Ubuntu: Fix Released Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: New Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Status in sphinx package in Ubuntu: New Status in tex-common package in Ubuntu: New Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: New Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: New Status in glib2.0 source package in Xenial: In Progress Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: New Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: New Status in sphinx source package in Xenial: New Status in tex-common source package in Xenial: New Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: New Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: New Status in glib2.0 source package in Bionic: Fix Released Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: New Status in octave source package in Bionic: New Status in packagekit source package in Bionic: New Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: New Status in sphinx source package in Bionic: New Status in tex-common source package in Bionic: New Status in xpdf source package in Bionic: Fix Re
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
Missing in this bug: kubuntu-settings ubuntu-gnome-defaults/xenial ubuntu-mate-artwork/xenial these are tracked in bug 1750465. ** Also affects: hicolor-icon-theme (Ubuntu) Importance: Undecided Status: New ** Also affects: mate-icon-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: New Status in glib2.0 package in Ubuntu: New Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: New Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: New Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Status in sphinx package in Ubuntu: New Status in tex-common package in Ubuntu: New Status in xpdf package in Ubuntu: New Status in yorick package in Ubuntu: New Status in appstream source package in Xenial: Triaged Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: New Status in glib2.0 source package in Xenial: New Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: New Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: New Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: New Status in sphinx source package in Xenial: New Status in tex-common source package in Xenial: New Status in xpdf source package in Xenial: New Status in yorick source package in Xenial: New Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: New Status in glib2.0 source package in Bionic: New Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: New Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: New Status in octave source package in Bionic: New Status in packagekit source package in Bionic: New Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: New Status in sphinx source package in Bionic: New Status in tex-common source package in Bionic: New Status in xpdf source package in Bionic: New Status in yorick source package in Bionic: New Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B then fails. This is a limitation of triggers: They are not exposed in Packages files, so we don't see them. What this means is that
[Group.of.nepali.translators] [Bug 1780996] [NEW] Convert triggers to noawait
Public bug reported: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B then fails. This is a limitation of triggers: They are not exposed in Packages files, so we don't see them. What this means is that packages with await triggers either need to have all triggering packages depend on them (e.g. B Depends A), or they need to be moved to noawait. This bug is about moving triggers to be noawait, by changing "activate" to "activate-noawait" and/or "interest" to "interest-noawait". If it turns out the trigger should be "await", we should explictly use the "interest-await" and "activate-await" variants in cosmic too. [Test case] There is no test case. [Regression potential] Packages triggering other packages are now configured even without the package being triggered being fully configured (they will be in the triggers-pending state). In most cases, this is not a problem. However, packages should be usable when configured, so for example, a package installing a gsettings schema would need to depend on the appropriate gsettings stuff and keep triggering it via await, as it would crash otherwise despite being configured. ** Affects: appstream (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: clutter-imcontext (Ubuntu) Importance: Undecided Status: New ** Affects: dochelp (Ubuntu) Importance: Undecided Status: New ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Affects: fusiondirectory (Ubuntu) Importance: Undecided Status: New ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Affects: goopg (Ubuntu) Importance: Undecided Status: New ** Affects: gosa (Ubuntu) Importance: Undecided Status: New ** Affects: guile-2.0 (Ubuntu) Importance: Undecided Status: New ** Affects: hicolor-icon-theme (Ubuntu) Importance: Undecided Status: New ** Affects: libomxil-bellagio (Ubuntu) Importance: Undecided Status: New ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: mate-icon-theme (Ubuntu) Importance: Undecided Status: New ** Affects: octave (Ubuntu) Importance: Undecided Status: New ** Affects: packagekit (Ubuntu) Importance: Undecided Status: New ** Affects: pike7.8 (Ubuntu) Importance: Undecided Status: New ** Affects: pike8.0 (Ubuntu) Importance: Undecided Status: New ** Affects: postgresql-common (Ubuntu) Importance: Undecided Status: New ** Affects: reconf-inetd (Ubuntu) Importance: Undecided Status: New ** Affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New ** Affects: sphinx (Ubuntu) Importance: Undecided Status: New ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Affects: xpdf (Ubuntu) Importance: Undecided Status: New ** Affects: yorick (Ubuntu) Importance: Undecided Status: New ** Affects: appstream (Ubuntu Xenial) Importance: Undecided Status: Triaged ** Affects: clutter-imcontext (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: dochelp (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: dovecot (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: fusiondirectory (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: gdk-pixbuf (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: glib2.0 (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: goopg (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: gosa (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: guile-2.0 (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: hicolor-icon-theme (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: libomxil-bellagio (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: libreoffice (Ubuntu Xenial) Importance: Undecided Status: Triaged ** Affects: mate-icon-theme (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: octave (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: packagekit (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: pike7.8 (Ubuntu
[Group.of.nepali.translators] [Bug 1737441] Re: /usr/bin/unattended-upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string
** Description changed: + [Impact] + Some applications, like unattended-upgrades or update-manager, reopen the apt cache. They also keep around old apt.Package objects however, and operate on them after reopening. Under the hood, this means that apt_pkg.Package objects belonging to an old cache are passed to a new cache. + + APT relies on the ID of the package (it's position in the cache) for + it's operation. So if a package has ID 0 in the old cache, and a + different package has ID 0 in the new cache, performing operations on + the old package would perform it on the new package. If the old + package's ID is out of bounds in the new cache, the behavior is + undefined - it's an out of bounds array access. + + [Test case] + The attached test case has a list of packages 0-9, a-z; stores the package "z" into a variable, then reopens the cache. It then marks z for deletion. This either segfaults or does nothing; when it should mark z for deletion. + + More test cases like this are in the autopkgtest. + + [Regression potential] + The initial fix introduced bug 1780099, there might be similar bugs lurking. However, these bugs would have been undefined behavior before and might have caused segmentation faults or did the wrong thing. It seems likely that any regression cannot possibly be worse than the current state. + + The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Description changed: [Impact] Some applications, like unattended-upgrades or update-manager, reopen the apt cache. They also keep around old apt.Package objects however, and operate on them after reopening. Under the hood, this means that apt_pkg.Package objects belonging to an old cache are passed to a new cache. APT relies on the ID of the package (it's position in the cache) for it's operation. So if a package has ID 0 in the old cache, and a different package has ID 0 in the new cache, performing operations on the old package would perform it on the new package. If the old package's ID is out of bounds in the new cache, the behavior is undefined - it's an out of bounds array access. [Test case] The attached test case has a list of packages 0-9, a-z; stores the package "z" into a variable, then reopens the cache. It then marks z for deletion. This either segfaults or does nothing; when it should mark z for deletion. More test cases like this are in the autopkgtest. [Regression potential] The initial fix introduced bug 1780099, there might be similar bugs lurking. However, these bugs would have been undefined behavior before and might have caused segmentation faults or did the wrong thing. It seems likely that any regression cannot possibly be worse than the current state. - + [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Also affects: python-apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu Xenial) Status: New => Triaged ** Changed in: unattended-upgrades (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1737441 Title: /usr/bin/unattended- upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string Status in python-apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in python-apt source package in Trusty: New Status in unattended-upgrades source package in
[Group.of.nepali.translators] [Bug 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method
** Description changed: - == xenial / trusty == - [Impact] - Some applications, like unattended-upgrades or update-manager, reopen the apt cache. They also keep around old apt.Package objects however, and operate on them after reopening. Under the hood, this means that apt_pkg.Package objects belonging to an old cache are passed to a new cache. - - APT relies on the ID of the package (it's position in the cache) for - it's operation. So if a package has ID 0 in the old cache, and a - different package has ID 0 in the new cache, performing operations on - the old package would perform it on the new package. If the old - package's ID is out of bounds in the new cache, the behavior is - undefined - it's an out of bounds array access. - - [Test case] - The attached test case has a list of packages 0-9, a-z; stores the package "z" into a variable, then reopens the cache. It then marks z for deletion. This either segfaults or does nothing; when it should mark z for deletion. - - More test cases like this are in the autopkgtest. - - [Regression potential] - The initial fix introduced bug 1780099, there might be similar bugs lurking. However, these bugs would have been undefined behavior before and might have caused segmentation faults or did the wrong thing. It seems likely that any regression cannot possibly be worse than the current state. - - == bionic+ === - [Impact] python-apt 1.6 raises an exception when objects of an old cache are passed to a apt_pkg.DepCache methods for a different cache. Prior to that, those would either segfault, succeed, or silently operate on a different object, as they use package/version ids, and e.g. two different packages in the old and new cache might have the same id. With 1.6.1, we introduce a remapping algorithm that remaps objects of apt.Cache() when calling apt.Cache.open(), allowing old objects to be used after reopening, as long as they exist in the new cache. If they don't exist in the new cache, apt_pkg.CacheMismatchError will be raised from the apt_pkg layer. [Test case] import apt c=apt.Cache() p=c["apt"] c.open() p.mark_install() [Regression potential] Could be remapping to wrong items which would cause us to install a wrong version, for example. Compared to pre-bionic, bionic is a regression already, though, and any regression caused here is less important than what we have now. [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** No longer affects: python-apt (Ubuntu Xenial) ** No longer affects: python-apt (Ubuntu Trusty) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Won't Fix Status in update-manager source package in Trusty: Confirmed Status in update-manager source package in Xenial: Confirmed Status in python-apt source package in Bionic: Fix Released Status in update-manager source package in Bionic: Won't Fix Status in python-apt source package in Cosmic: Fix Released Status in update-manager source package in Cosmic: Won't Fix Bug description: [Impact] python-apt 1.6 raises an exception when objects of an old cache are passed to a apt_pkg.DepCache methods for a different cache. Prior to that, those would either segfault, succeed, or silently operate on a different object, as they use package/version ids, and e.g. two different packages in the old and new cache might have the same id. With 1.6.1, we introduce a remapping algorithm that remaps objects of apt.Cache() when calling apt.Cache.open(), allowing old objects to be used after reopening, as long as they exist in the new cache. If they don't exist in the new cache, apt_pkg.CacheMismatchError will be raised from the apt_pkg layer. [Test case] import apt c=apt.Cache() p=c["apt"] c.open() p.mark_install() [Regression potential] Could be remapping to wrong items which would cause us to install a wrong version, for example. Compared to pre-bionic, bionic is a regression already, though, and any regression caused here is less important than what we have now. [Original bug report] The Ubuntu Error Tracker
[Group.of.nepali.translators] [Bug 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method
** Also affects: python-apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: update-manager (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: update-manager (Ubuntu Trusty) Importance: Undecided Status: New ** Description changed: + == xenial / trusty == + [Impact] + Some applications, like unattended-upgrades or update-manager, reopen the apt cache. They also keep around old apt.Package objects however, and operate on them after reopening. Under the hood, this means that apt_pkg.Package objects belonging to an old cache are passed to a new cache. + + APT relies on the ID of the package (it's position in the cache) for + it's operation. So if a package has ID 0 in the old cache, and a + different package has ID 0 in the new cache, performing operations on + the old package would perform it on the new package. If the old + package's ID is out of bounds in the new cache, the behavior is + undefined - it's an out of bounds array access. + + [Test case] + The attached test case has a list of packages 0-9, a-z; stores the package "z" into a variable, then reopens the cache. It then marks z for deletion. This either segfaults or does nothing; when it should mark z for deletion. + + More test cases like this are in the autopkgtest. + + [Regression potential] + The initial fix introduced bug 1780099, there might be similar bugs lurking. However, these bugs would have been undefined behavior before and might have caused segmentation faults or did the wrong thing. It seems likely that any regression cannot possibly be worse than the current state. + + == bionic+ === + [Impact] python-apt 1.6 raises an exception when objects of an old cache are passed to a apt_pkg.DepCache methods for a different cache. Prior to that, those would either segfault, succeed, or silently operate on a different object, as they use package/version ids, and e.g. two different packages in the old and new cache might have the same id. With 1.6.1, we introduce a remapping algorithm that remaps objects of apt.Cache() when calling apt.Cache.open(), allowing old objects to be used after reopening, as long as they exist in the new cache. If they don't exist in the new cache, apt_pkg.CacheMismatchError will be raised from the apt_pkg layer. [Test case] import apt c=apt.Cache() p=c["apt"] c.open() p.mark_install() [Regression potential] Could be remapping to wrong items which would cause us to install a wrong version, for example. Compared to pre-bionic, bionic is a regression already, though, and any regression caused here is less important than what we have now. [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Attachment added: "Test case for xenial/trusty" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1773316/+attachment/5159649/+files/a.py -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Won't Fix Status in python-apt source package in Trusty: Confirmed Status in update-manager source package in Trusty: Confirmed Status in python-apt source package in Xenial: Confirmed Status in update-manager source package in Xenial: Confirmed Status in python-apt source package in Bionic: Fix Released Status in update-manager source package in Bionic: Won't Fix Status in python-apt source package in Cosmic: Fix Released Status in update-manager source package in Cosmic: Won't Fix Bug description: == xenial / trusty == [Impact] Some applications, like unattended-upgrades or update-manager, reopen the apt cache. They also keep around old apt.Package objects however, and operate on them after reopening. Under the hood, this means that apt_pkg.Package objects belonging to an old cache are passed to a new cache. APT relies on the ID of the package (it's position in the cache) for it's operation. So if a package has ID 0 in the old cache, and a different package has ID 0 in the new cache,
[Group.of.nepali.translators] [Bug 1724869] Re: ndiswrapper 1.60-3~ubuntu16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
** Changed in: ndiswrapper (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1724869 Title: ndiswrapper 1.60-3~ubuntu16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 Status in ndiswrapper package in Ubuntu: Invalid Status in ndiswrapper source package in Xenial: Fix Released Bug description: [Impact] Currently the DKMS package fails to install in supported custom kernels that are based on 4.11 or 4.13. That includes the current 4.11 hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom and cloud kernels as well. [Test Case] Install the DKMS package with the 4.13 hwe-edge kernel from -proposed. The package installation should proceed without any errors. [Regression Potential] Although new patches were added, the regression risk is very low since the new changes are conditionally compiled based on the kernel version. Besides that the new package was tested with the following kernels in an amd64 environment: - linux-generic 4.4 - linux-hwe 4.10 - linux-hwe-edge 4.11 - linux-hwe-edge 4.13 (from xenial-proposed) - linux-azure 4.11 - linux-azure-edge 4.13 (which is in process of getting promoted to xenial-proposed) [Original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/ndiswrapper/20171018_120708_19fbd@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/ndiswrapper/20171018_121335_19fbd@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1724869/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1778551] Re: Add linux-modules* packages to VersionedKernelPackages
** Also affects: apt (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Artful) Status: New => In Progress ** Changed in: apt (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1778551 Title: Add linux-modules* packages to VersionedKernelPackages Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: In Progress Status in apt source package in Artful: In Progress Bug description: == SRU Justification == Impact: The 4.15 hwe kernel includes some package shuffling, so the VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs to be updated to include linux-modules* packages. Fix: Backport the conf file changes from bionic. Test Case: Confirm that linux-modules* packages are autoremoved according to the same rules used for linux-image* packages. Regression Potential: Minimal. Probably the worst case is that some packages that should be autoremoved are not, but since these changes have been in use in bionic for a while now no regressions are expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778551/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1778551] Re: Add linux-modules* packages to VersionedKernelPackages
Yup. We probably want an easier test case, though? ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Xenial) Status: New => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1778551 Title: Add linux-modules* packages to VersionedKernelPackages Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Bug description: == SRU Justification == Impact: The 4.15 hwe kernel includes some package shuffling, so the VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs to be updated to include linux-modules* packages. Fix: Backport the conf file changes from bionic. Test Case: Confirm that linux-modules* packages are autoremoved according to the same rules used for linux-image* packages. Regression Potential: Minimal. Probably the worst case is that some packages that should be autoremoved are not, but since these changes have been in use in bionic for a while now no regressions are expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778551/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Bug watch added: Debian Bug tracker #900838 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900838 ** Also affects: menu (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900838 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Committed Status in apt source package in Xenial: New Status in menu source package in Xenial: New Status in apt source package in Artful: New Status in menu source package in Artful: New Status in apt source package in Bionic: New Status in menu source package in Bionic: New Status in menu package in Debian: Unknown Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Adding tasks for down to xenial, but not sure what we want to do. I don't foresee any trouble with that change, but we can't test it, and even if we get a failing upgrade, we can only test for that release. ** Changed in: menu (Ubuntu) Status: In Progress => Fix Committed ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: menu (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: menu (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: menu (Ubuntu Artful) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Committed Status in apt source package in Xenial: New Status in menu source package in Xenial: New Status in apt source package in Artful: New Status in menu source package in Artful: New Status in apt source package in Bionic: New Status in menu source package in Bionic: New Bug description: I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1593469] Re: [2.0] VMware power type error: __init__() takes 1 positional argument but 2 were given
** Also affects: python-pyvmomi (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1593469 Title: [2.0] VMware power type error: __init__() takes 1 positional argument but 2 were given Status in MAAS: Incomplete Status in python-pyvmomi package in Ubuntu: Fix Released Status in python-pyvmomi source package in Xenial: New Bug description: When adding VMware power type in 2.0.0 beta7: Failed to query node's BMC - __init__() takes 1 positional argument but 2 were given The same VMware details (UUID, vCenter IP address, username/password, etc.) worked in an earlier version of the maas server, which was Ubuntu 14.04 / maas 1.9. Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---= ii maas2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all "Metal as a Service" is a physical cloud and IPAM ii maas-cli2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS client and command-line interface un maas-cluster-controller (no description available) ii maas-common 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server common files ii maas-dhcp 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS DHCP server ii maas-dns2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS DNS server ii maas-proxy 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS Caching Proxy ii maas-rack-controller2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Rack Controller for MAAS ii maas-region-api 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Region controller API service for MAAS ii maas-region-controller 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Region Controller for MAAS un maas-region-controller-min (no description available) un python-django-maas (no description available) un python-maas-client (no description available) un python-maas-provisioningserver (no description available) ii python3-django-maas 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server Django web framework (Python 3) ii python3-maas-client 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS python API client (Python 3) ii python3-maas-provisioningserver 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server provisioning libraries (Python 3) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1593469/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1762766] Re: apt-get update hangs when apt-transport-https is not installed
I think so, but I don't think it's worth pushing out an update just for that change. It's been broken since forever, so it's not like it's fixing a regression or something; so I'd probably wait for something else to attach it to. ** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Trusty) Status: New => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1762766 Title: apt-get update hangs when apt-transport-https is not installed Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in apt source package in Xenial: Triaged Status in apt package in Debian: Fix Released Bug description: When "apt-get update" is run on a docker container running Ubuntu v16.04 and containing an additional apt source repository hosted on an https webserver, the "apt-get update" command hangs. The hang happens after connections to http ubuntu hosts are complete, and apt-get remains stuck on "Working" at 0%. Removing the sources file for the https repo causes apt-get to complete normally. The source file contains 4 separate entries to 4 different repos on the same https server. When the source file is modified so that just *one* entry exists to one repo on the https server, we suddenly get a sensible error message that tells us that apt-transport-https needs to be installed. Installing apt-transport-https into the docker container before adding the sources list to the https servers works around the problem and sanity returns. Key notes: - The use of docker isn't related to the bug, except that the docker image doesn't contain the apt-transport-https package whereas our cloud images do contain this package by default. This can give the impression that this is a docker bug when it's not. - The hang in "apt-get update" seems to occur when the sources file contains more than one entry in the file. When just one entry exists in the file (and all other entries are commented out) a sensible error messages appears. - We encountered this on a host that didn't support cut and paste, sorry :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1762766/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1762766] Re: apt-get update hangs when apt-transport-https is not installed
I'm not sure when we fixed that, but we did. So bionic works fine. Not sure about artful. ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Xenial) Status: New => Triaged ** Bug watch added: Debian Bug tracker #870675 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870675 ** Also affects: apt (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870675 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1762766 Title: apt-get update hangs when apt-transport-https is not installed Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Status in apt package in Debian: Unknown Bug description: When "apt-get update" is run on a docker container running Ubuntu v16.04 and containing an additional apt source repository hosted on an https webserver, the "apt-get update" command hangs. The hang happens after connections to http ubuntu hosts are complete, and apt-get remains stuck on "Working" at 0%. Removing the sources file for the https repo causes apt-get to complete normally. The source file contains 4 separate entries to 4 different repos on the same https server. When the source file is modified so that just *one* entry exists to one repo on the https server, we suddenly get a sensible error message that tells us that apt-transport-https needs to be installed. Installing apt-transport-https into the docker container before adding the sources list to the https servers works around the problem and sanity returns. Key notes: - The use of docker isn't related to the bug, except that the docker image doesn't contain the apt-transport-https package whereas our cloud images do contain this package by default. This can give the impression that this is a docker bug when it's not. - The hang in "apt-get update" seems to occur when the sources file contains more than one entry in the file. When just one entry exists in the file (and all other entries are commented out) a sensible error messages appears. - We encountered this on a host that didn't support cut and paste, sorry :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1762766/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1522675] Re: Warning messages about unsandboxed downloads
Uploaded update-notifier to xenial-proposed. ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: aptitude (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: synaptic (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: update-notifier (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: apt (Ubuntu Xenial) ** Changed in: update-notifier (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: update-notifier (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: update-notifier (Ubuntu Xenial) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: update-notifier (Ubuntu Xenial) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in aptitude source package in Xenial: New Status in synaptic source package in Xenial: New Status in update-notifier source package in Xenial: In Progress Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: READ ME FIRST = This is a cosmetic issue. The warning message is just that— a warning. Though the message comes up, there is no problem with the install/upgrade happening like normal. That said, feel free to ignore it. It will get fixed, but it's nowhere near as urgent as bugs that actually result in the wrong behavior rather than just a simple extra message. update-notifier SRU --- [Impact] Cosmetic. Warnings when installing packages using update-notifier downloading stuff [Test case] Install flashplugin-installer with apt and check that the output does not contain a message like this: W: Can't drop privileges for downloading as file '...' couldn't be accessed by user '_apt' [Regression Potential] It just chowns /var/lib/update-notifier/package-data- downloads/partial/ to _apt:root, there should not be any regression. Original report --- Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1613184] Re: method mirror broken at 1.3
@Bojan The fix would have been in 1.4.8, but zesty is not supported anymore - please upgrade to artful. ** Changed in: apt (Ubuntu Zesty) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1613184 Title: method mirror broken at 1.3 Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Zesty: Won't Fix Bug description: [Impact] The mirror method always dies with a SEGV. It does not initialize _system but calls a function that sometimes uses it. [Test case] Use a mirror sources.list entry like deb mirror://mirrors.ubuntu.com/mirrors.txt zesty main restricted universe multiverse [Regression potential] The fix is small, and simply avoids using _system if _system is NULL in the called method. There should not be any regressions due to this. https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=cba5c5a26a9bf00724f8ea647ac61b30e32734ba To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1613184/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1751225] Re: apt update hangs when repository url is redirect url
OK, so: xenial: affected artful, bionic: NOT affected So I might just want to revert this commit in an apt 1.2.26 release and look at it again later. ** Changed in: apt (Ubuntu Artful) Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1751225 Title: apt update hangs when repository url is redirect url Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: In Progress Status in apt source package in Artful: Invalid Bug description: [Impact] When using redirect url on /etc/apt/sources.list apt update command hangs this is affected with commit https://anonscm.debian.org/git/apt/apt.git/commit/?id=dd547ebaffd2aceb42e2908f1d5f0ab386af6cb1 In my test, moving below[1] code after[2] [1] ### if (ContentLength == 0) return true; ### [2] if (Encoding == Closes) Encoding = Stream; ### it worked fine. [Test Case] echo "deb http://packages.cloudfoundry.org/debian stable main" > /etc/apt/sources.list.d/cloudfoundry-cli.list apt update [Regression] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1751225/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1751225] Re: apt update hangs when repository url is redirect url
OK, so I need to dig a bit further into this. I think if I move the if I break things elsewhere. IIRC, I added the if that early because, when apt received a redirect with Content-Length: 0, it started hanging, and that fixed it. But maybe it breaks some other stuff now. ** Changed in: apt (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1751225 Title: apt update hangs when repository url is redirect url Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: Triaged Status in apt source package in Artful: New Bug description: [Impact] When using redirect url on /etc/apt/sources.list apt update command hangs this is affected with commit https://anonscm.debian.org/git/apt/apt.git/commit/?id=dd547ebaffd2aceb42e2908f1d5f0ab386af6cb1 In my test, moving below[1] code after[2] [1] ### if (ContentLength == 0) return true; ### [2] if (Encoding == Closes) Encoding = Stream; ### it worked fine. [Test Case] echo "deb http://packages.cloudfoundry.org/debian stable main" > /etc/apt/sources.list.d/cloudfoundry-cli.list apt update [Regression] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1751225/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
