This is not a problem we can fix on our side. It is an upstream shim
problem. Every distribution you want to boot will need a fixed shim, and
it's not a priority right now, given that we have a moratorium on new
shims being signed.
We have the ability to secure boot Ubuntu already, by not chainloa
I cannot reproduce that issue from #11
# apt install locales-all # get the locale
# export LANG=sv_SE.UTF-8
# locale
LANG=sv_SE.UTF-8
LANGUAGE=
LC_CTYPE="sv_SE.UTF-8"
LC_NUMERIC="sv_SE.UTF-8"
LC_TIME="sv_SE.UTF-8"
LC_COLLATE="sv_SE.UTF-8"
LC_MONETARY="sv_SE.UTF-8"
LC_MESSAGES="sv_SE.UTF-8"
LC_PAPE
OK I believe what has happened here is that you are running mixed-locale
systems, and the cache was generated with en_US or C locales. If you run
mixed language systems, you have to set
Acquire::Languages { "language code 1"; "language code 2"; ... };
e.g.
Acquire::Languages { "sv_SE"; "sv"; en"
Public bug reported:
[Impact]
In bug 1161743 we discovered that if a system is configured with multiple
locales, only the locales of the user who generated the apt-cache will be
available for translated descriptions.
[Test case]
# apt install locales-all # get the locale
# export LANG=sv_SE.UT
That's correct. 33 was a hot fix release for a data loss in 31 that did
not include the changes from 32. They'll come back in 34.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896091
Title:
[i915]
** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2004-2020
** Changed in: aptdaemon (Ubuntu)
Assignee: Ravikant (ravikantcool) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Changed in: apt (Ubuntu)
Assignee: Sebastián Astudillo (zhoku) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871268
Title:
Installation fails due to useless immediate config
** Changed in: apt (Ubuntu Groovy)
Status: Fix Released => Triaged
** Changed in: apt (Ubuntu Focal)
Status: Fix Released => Triaged
** Changed in: apt (Ubuntu Bionic)
Status: Fix Released => Confirmed
** Changed in: apt (Ubuntu Bionic)
Status: Confirmed => New
--
Y
The first chance to fix it was in August, the next chance to fix it is
in February. There's really no urgency here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871268
Title:
Installation fails du
There is an easy workaround, too: just don't check the box to install
third party drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871268
Title:
Installation fails due to useless immediate co
You'll be able to install the driver after having rebooted and upgraded
the distribution. You don't have to (and can't atm) do it _during_
install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871268
Yes the security team has the packages ready to go out for a week now
essentially.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907676
Title:
segmentation fault when opening fd
To manage notifica
They prepared the updates on the same day as the fix (well the full
regression fix with the follow-up commits) but did not roll out the fix
so far because only dak reported a regression and codesearch did not
yield any other users of that interface.
--
You received this bug notification because y
Eric, the updates are built ready in the security team PPA since Dec 10
and only need to be released. I've subscribed security team, but you
might want to talk to them directly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773457
Title:
Full-system encryption needs to be supported out-of-the-box including
The issue reported here is that /boot is not encrypted in the supported
configurations. Which is meh - we don't have much authenticated
encryption, so boot can still be manipulated. Sealed TPM measurements
address the problem of verifying the bootloader, kernel, initrd, and the
configuration better
I think the answer there is fscrypt - native encryption at the
filesystem level supported by ext4 and some other day - but I'm not sure
what the plans are. Partitioning is hard and the requirement to setup a
separate /boot and crypt device are not always possible, though it is
less of an issue thes
Support for Python 2 was dropped system-wide.
** Changed in: python-apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909173
Title:
Python-apt for Python2.x
** Changed in: powertop (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740861
Title:
Packaging version 2.9
To manage notifications about this bug go to:
https
** Changed in: powertop (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740861
Title:
Packaging version 2.9
To manage notifications about this bug go
APT, by design, only picks candidate versions when installing
dependencies, and the non-pinned proposed version is not the candidate.
apt install foo/target has some logic to switch dependencies to target
too, which works sometimes, but it's nothing that happens when using
pinning.
** Changed in:
sbuild passes:
--solver aspcud -o APT::Solver::Strict-Pinning=false -o
'APT::Solver::aspcud::Preferences=-removed,-changed,-new,+sum(solution
,apt-pin)'
That probably works here too. I guess I'd try without, and then fall back to it
if pure APT can't handle it.
--
You received this bug notifi
(unassigned) => Julian Andres Klode (juliank)
** Changed in: dpkg (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760979
Tit
I think with basically trivial patches in just dpkg, apt, python-apt,
and packagekit we should have solved most of that. At least the apt
tools, and any tool using python-apt or packagekit will be safe from
being interfered with.
** Also affects: python-apt (Ubuntu)
Importance: Undecided
Note that dpkg and apt need to go first, then we can add support to
other tools. The solution is not entirely optimal (at least
theoretically): Crashing the frontend releases the frontend lock, so
other frontends could start doing stuff (though probably fail at dpkg
lock). It would have been nice t
Marking it as New for the UIFe tracking.
** Summary changed:
- ubuntu-bug says that snap packages are not installed
+ [UIFe] ubuntu-bug says that snap packages are not installed
** Description changed:
- 1.
+ User Interface Freeze Exception Justification
+ =
Well, no filename was specified for "tee"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732030
Title:
'apt update' dies with seccomp error
To manage notifications about this bug go to:
https://bug
Uploaded socat with tests enabled (most of them, some fail due to
OpenSSL 1.1 and cipher negotiation restrictions in there)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756870
Title:
[MIR] socat
No - it's the "store" method that's failing (e.g.
recompressing/decompressing files). I disallowed socket and friends for
that, so that's failing. I mean, it's a decompress/compress method, it
should not have network access.
--
You received this bug notification because you are a member of Ubuntu
Or generally allow network and the getdents stuff, and just block more
esoteric syscalls for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732030
Title:
'apt update' dies with seccomp error
T
I wonder if we should turn the sandbox off by default for bionic. Not
sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732030
Title:
'apt update' dies with seccomp error
To manage notifications
Public bug reported:
[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]
TODO
[Regression potential]
TODO
** Affects: apt (Ubuntu)
Imp
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 Ubuntu
Bugs, which is subscribed
es: 870675)
(LP: #1762766)
[ Julian Andres Klode ]
* Fix lock counting in debSystem (LP: #1778547)
* apt.conf.autoremove: Catch some new Ubuntu module packages (LP: #1778551)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Description changed:
[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]
- TODO
+
+ Executing the following script should show on
** Changed in: apt (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778547
Title:
Broken system lock counting
To manage notifications about this
** Description changed:
+ [Impact]
+ dirmngr processes are left hanging around
+
+ [Test case]
+ apt-key adv --recv-keys "8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092"
< /dev/null ; ps aux
+
+ should not show a dirmngr process after exit (except for any that was
+ there before running it,
** Changed in: apt (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766542
Title:
Installation blocks when the machine is behind a proxy server
To ma
** Description changed:
- When the machine is behind a proxy server, the installation will block
- for a while (several minutes) to retrieve the package lists. The
- timeouts are too long and makes user feels the machine may have some
- problems.
+ [Impact]
+ APT takes a long time to notice when c
** 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 Ubuntu
** Changed in: apt (Ubuntu Artful)
Status: Confirmed => In Progress
** Changed in: apt (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778
** Changed in: apt (Ubuntu Xenial)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762766
Title:
apt-get update hangs when apt-transport-https is not installed
Public bug reported:
MODULES=most should have microcode for all CPUs, so it's usable
everywhere.
** Affects: amd64-microcode (Ubuntu)
Importance: Undecided
Status: Fix Committed
** Affects: intel-microcode (Ubuntu)
Importance: Undecided
Status: Fix Committed
** Tags
** Changed in: apt (Ubuntu)
Status: New => In Progress
** Changed in: apt (Ubuntu)
Importance: Undecided => High
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Ub
** Also affects: update-manager (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: update-manager (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Hey, Anders, don't you want to verify it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722411
Title:
gnutls28 in trusty no longer validates many valid certificate chains,
such as google.com
To
** Changed in: ndiswrapper (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724869
Title:
ndiswrapper 1.60-3~ubuntu16.04.1 ADT test failure with linux-hwe-
*** This bug is a duplicate of bug 1777652 ***
https://bugs.launchpad.net/bugs/1777652
** This bug has been marked a duplicate of bug 1777652
ndiswrapper 1.60-3~ubuntu16.04.2 ADT test failure with linux-hwe-edge
4.15.0-23.25~16.04.1
--
You received this bug notification because you are a
depmod failed here when configuring linux image, reassigning
** Package changed: ndiswrapper (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750480
Title:
package ndiswrap
*** This bug is a duplicate of bug 1777652 ***
https://bugs.launchpad.net/bugs/1777652
** This bug has been marked a duplicate of bug 1777652
ndiswrapper 1.60-3~ubuntu16.04.2 ADT test failure with linux-hwe-edge
4.15.0-23.25~16.04.1
--
You received this bug notification because you are a
Not touching ndiswrapper in trusty, as the package has diverted a lot
since then.
** Changed in: ndiswrapper (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672
Not touching ndiswrapper in trusty, as the package has diverted a lot
since then.
** Changed in: ndiswrapper (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Not touching ndiswrapper in trusty, as the package has diverted a lot
since then. It's still invalid anyway, regardless of whether there are
duplicates or not.
** Changed in: ndiswrapper (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a membe
Not touching ndiswrapper in trusty, as the package has diverted a lot
since then.
** Changed in: ndiswrapper (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Sorry, few typos in the script
** Description changed:
[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 follow
=== bionic OK (1.6.1 -> 1.6.2) =
+ lxc launch -e ubuntu:bionic lp1778547-bionic
Creating lp1778547-bionic
Starting lp1778547-bionic
+ sleep 5
+ lxc exec lp1778547-bionic -- sh -c 'apt-cache policy libapt-pkg5.0 | grep
Inst ; python3 /home/jak/a.py'
Installed: 1.6.1
[
Verified. The first dirmngr started by 1.6.1 stayed alive even after
1.6.2 finished executing; the dirmngr started by 1.6.2 was not alive
anymore.
+ lxc launch -e ubuntu:bionic lp1773992-bionic
Creating lp1773992-bionic
** Description changed:
- 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.
+ [Impact]
+ Two or more sources with an unknown protocol cause apt update to
huh, why did it say backports? Me looks again, and sees the package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762766
Title:
apt-get update hangs when apt-transport-https is not installed
To m
No package in proposed yet.
curl http://archive.ubuntu.com/ubuntu/dists/xenial-backports/main
/binary-amd64/Packages.xz | xzcat | grep ^Package
does not show apt. odd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Verified now, despite me not changing my verification script. Odd.
with 1.2.26, it times out:
+ lxc exec lp1762766-xenial -- sh -c 'apt-cache policy apt libapt-pkg5.0 | grep
Inst ; timeout 5s apt update'
Installed: 1.2.26
Installed: 1.2.26
0% [Working]+ lxc stop lp1762766-xenial
I had to tweak the time outs a bit, as I quickly get some errors from
the networking stack (like 7s or so), but I could successfully verify
the fix now, using a standard ubuntu:bionic lxd container, and modifying
the routes, and setting a lower timeout:
+ ip r del default
+ ip r add default via 10
So, u-r-u runs /usr/bin/gnome-session-inhibit --inhibit idle --inhibit-
only - running that manually works fine to block stuff on cosmic, but
not sure about xenial.
systemd-inhibit --what=idle does not prevent locking.
--
You received this bug notification because you are a member of Ubuntu
Bugs
Packages for test to inject (4 kernels, -20, 21, 22, 23).
** Attachment added: "Packages"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778551/+attachment/5157702/+files/Packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Verification done. It shows that with apt 1.2.26, the -22 module-extra
are removed, despite their kernel being kept, and that's fixed in
1.2.27. Full log attached, highlight:
Before:
The following packages will be REMOVED:
libfreetype6 linux-image-4.15.0-20-generic linux-image-4.15.0-21-generic
Same results on artful
** Attachment added: "artful.log"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778551/+attachment/5157707/+files/artful.log
** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful
--
You received
** Description changed:
- 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:
+ [Impact]
+ apt proxy settings are not applied to https urls, and thus the
release-upgrade-motd scr
** Description changed:
[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 cha
** Changed in: update-manager (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771914
Title:
release-upgrade-motd can't update message via apt pro
** Also affects: intel-microcode (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: amd64-microcode (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: intel-microcode (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects:
In order to debug this further, we need a copy of /var/log/apt/term.log.
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779129
Title:
pa
** Description changed:
- MODULES=most should have microcode for all CPUs, so it's usable
- everywhere.
+ [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 generat
I'm not sure how feasible retesting loading of the firmware is for the 8
SRUs. We tested that once on cosmic per vendor, so given that the rest
is equal, just ensuring it's there is probably fine.
** Description changed:
[Impact]
Initramfs for MODULES=most should build with all microcodes ins
This was fixed in 1.1 or later, not entirely sure about the exact
version.
** Changed in: apt (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/948461
Ti
We made things work better for unreadable files, so I think that's fixed
in cosmic and probably bionic.
** Changed in: apt (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I think we have gotten better at this, but it seems pointless to
constantly keep a bug open here. When we add a new symbol it is usually
not used by anything and it will eventually get added to the file.
If there are any specific instances where packages use new symbols we do
not declare, file a b
*** This bug is a duplicate of bug 1697120 ***
https://bugs.launchpad.net/bugs/1697120
** This bug has been marked a duplicate of bug 1697120
artful's apt-file and aptitude complains about Ubuntu sources.list
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
*** This bug is a duplicate of bug 1697120 ***
https://bugs.launchpad.net/bugs/1697120
** This bug is no longer a duplicate of bug 975312
duplicated sources list entry
** This bug has been marked a duplicate of bug 1697120
artful's apt-file and aptitude complains about Ubuntu sources.lis
These days we mostly fetch based on what the InRelease file tells us, so
this message is seen less. In any case, it's not an error, otherwise it
would tell you, it's just progress logging.
** Changed in: apt (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification becau
Won't fix as before
** Changed in: apt (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710618
Title:
Please support libkibi
To manage notifications about thi
Closed as it has been fixed as mentioned in previous comment.
** Changed in: apt (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/184354
Title:
apt sh
It is my understanding that automatic kernel removal has been added in
update-manager. They are also removed automatically in unattended-
upgrades. There should be a maximum of 3 kernel versions left, in order
to recover if a new kernel fails.
** Changed in: update-manager (Ubuntu)
Status:
The system seems to be in a broken state. awk is pseudo-essential, as
base-files depends on it, so it should not be (possible to) removed
(it).
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Public bug reported:
[Impact]
The apt.Package objects use the id as the hash, but the hash can change after
reopening, meaning that code will fail to work, for example:
c=apt.Cache()
p=c["a"]
set_of_p={p}
c.open()
assert p in set_of_p
will fail.
[Test case]
The above test case is run as part o
This update causes a regression that is tracked in bug 1780099 - notably
the __hash__ of an apt.Package can change after opening, so if used in a
set, or as a dict key, the package won't be found anymore. The
regression is less worse than the previous state, but will be fixed
shortly.
--
You rece
*** This bug is a duplicate of bug 1773316 ***
https://bugs.launchpad.net/bugs/1773316
Public bug reported:
[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 reopenin
** 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-mana
** Changed in: python-apt (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780099
Title:
Cache remapping breaks hashing of Package objects
To manage notific
** Description changed:
[Impact]
The apt.Package objects use the id as the hash, but the hash can change after
reopening, meaning that code will fail to work, for example:
c=apt.Cache()
p=c["a"]
set_of_p={p}
c.open()
assert p in set_of_p
will fail.
[Test case]
- The abo
debdiff
** Patch added: "redis_5_4.0.9-1_5_4.0.9-1ubuntu0.1.diff"
https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1805822/+attachment/5217316/+files/redis_5_4.0.9-1_5_4.0.9-1ubuntu0.1.diff
** Also affects: redis (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in:
Public bug reported:
This is a simple forward port of the relevant parts of the xenial
update.
* CVE-2018-11218 needed no changes, applied as-is
* CVE-2018-11219 needed some whitespace changes
* CVE-2018-12326 needed some more changes, I picked the equivalent referenced
upstream commit
The pack
Oh, and here is a diff of the diffs - xenial vs bionic, for double
checking :)
** Patch added: "diff.diff"
https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1805822/+attachment/5217317/+files/diff.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The variables are usually http_proxy and https_proxy, not uppercase
versions. That said, gpg does not seem to honor either. It does,
however, honor an option --keyserver-options http-proxy=, although it is
deprecated.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The fix is to put .asc or .gpg files in trusted.gpg.d and not use apt-
key.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433761
Title:
apt-key and add-apt-repository don't honor Acquire::http::Pro
I reproduced this using:
$ kvm -bios /usr/share/OVMF/OVMF_CODE.fd -device e1000,netdev=n1 -netdev
user,id=n1,tftp=/boot/efi,bootfile=/EFI/ubuntu/grubx64.efi
and manually booting shim from the iPXE commandline which then tries to
chainload grubx64.efi.
iPXE> boot tftp://10.0.2.2/EFI/boot/bootx64.
We need a crash dump to be able to investigate this. Apport can probably
help you with apport-collect 1790613 or something. Without a crash dump
we don't see where it crashed and thus can't do much.
** Changed in: packagekit (Ubuntu)
Status: New => Incomplete
--
You received this bug noti
With systemd-boot instead of grub, it simply fails, pretendign the file
does not exist.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable to load shimx64.efi using iPXE over UEFI
r.Arch() is called even if ver is not valid.
** Changed in: packagekit (Ubuntu)
Status: New => Triaged
** Changed in: packagekit (Ubuntu)
Status: Triaged => In Progress
** Changed in: packagekit (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed
Sent fix upstream: https://github.com/hughsie/PackageKit/pull/273
** Changed in: packagekit (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790671
Uploaded
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790671
Title:
/usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_jo
701 - 800 of 5951 matches
Mail list logo
