Public bug reported:
I have created a simple org.weechat.weechat-ssh.desktop to launch gnome-
terminal with an app-id, window title, etc using
gnome-terminal --window --disable-factory --class weechat-ssh --name
weechat-ssh --app-id org.weechat.weechat-ssh --title WeeChat -- ssh
Once APT implements origin tracking this should no longer be a problem,
or it might be; generally speaking the idea is that if you install a
package from one archive, APT doesn't switch it. You can also configure
rules of `o=Ubuntu -> o=UbuntuESM` to allow transitions between
archives.
However
As explained before, the behavior here is intended and not a bug.
@Jan You are free to configure unattended-upgrades to install from the
PPA or add negative pins for the Ubuntu (and UbuntuESM archives, if
enabled) for src:firefox to prevent the snap from being installed.
@Piotr I will not
Oh and various repositories have been configured without a key, possibly
the files they use have been deleted, that is keys in
/etc/apt/trusted.gpg.d or /etx/apt/trusted.gpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The error reported in the first command is
504 Gateway Time-out [IP: 2.18.172.141 443]
A network issue on that server.
In the second run it seems there is a concurrent packgekit transaction
running.
Neither are an error in the client code
** Changed in: apt (Ubuntu)
Status: New =>
** Tags removed: rls-jj-incoming
** Tags added: foundations-todo
** Changed in: python3.10 (Ubuntu Jammy)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
To continue upgrading you can try to remove postgresql-12, this was
inadvertently left in a removal deny list which made the release upgrade
reject the upgrade.
** Tags removed: rls-nn-incoming
** Tags added: foundations-todo
--
You received this bug notification because you are a member of
** Changed in: software-properties (Ubuntu)
Status: Confirmed => In Progress
** Changed in: software-properties (Ubuntu)
Assignee: Nick Rosbrook (enr0n) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: software-properties (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Tags added: deb822
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063484
Title:
Other Software now displays the Suites instead of the Comments
To manage notifications about this bug go to:
Funnily any intermediate command also makes it work:
$ fakechroot env /usr/sbin/chroot /tmp/noble-amd64
groups: cannot find name for group ID 1000
groups: cannot find name for group ID 113
I have no name!@jak-t14-g3:/$
--
You received this bug notification because you are a member of Ubuntu
I assume this fakechroot crash is unrelated however, because it crashes
directly on the chroot whereas what crashes in the bug report is update-
alternatives.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I investigated all sorts of possible combinations
fakechroot fakeroot chroot
fakeroot chroot
fakechroot chroot
chroot
And it only crashed in the fakechroot case, I cannot confirm any crashes
with just chroot; I did do the whole verification inside a container
emulated by qemu-user-static.
I did
This is the crash, you can see it crashes in fakechroot trying to locate
bindtextdomain using dlsym:
#0 0x7100c997d62a in ___dlsym (handle=0x,
name=0x7100c9b13ac1 "bindtextdomain") at ./dlfcn/dlsym.c:66
warning: 66 ./dlfcn/dlsym.c: No such file or directory
(gdb) bt full
** Description changed:
fakechroot chroot chroot-directory "apt-get install -y fakeroot" fails
on arm64, as update-alternatives is crashing; it works fine without
fakechroot.
+
+ Test case:
+
+ #!/bin/sh
+
+ apt install curl fakeroot fakechroot -y
+ curl
Public bug reported:
fakechroot chroot chroot-directory "apt-get install -y fakeroot" fails
on arm64, as update-alternatives is crashing; it works fine without
fakechroot.
** Affects: fakechroot (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
we are using LUNs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066286
Title:
Multipath 0.8.8 reports High CPU usage when having Lun's using
Multipath
To manage notifications about this bug go
Hi,
So far, we have changed how we mount and unmount the disks. By doing so,
we have not had the high CPU usage issue again.
We currently do more checks before mounting the disk. Before we used to mount
without checking if the device was actually visible.
we umount the old disk
sudo
** Description changed:
+ [Impact]
+ Upgrades hang for a long time searching for obsolete software, frustrating
users.
+
+ [Test plan]
+
+ 1. With each, update, and proposed version do:
+
+ 0. launch a container / VM
+ 1. do-release-upgrade
+ 2. Note down the time it took for the
** Description changed:
[Impact]
We have received feedback from users that use NIST-P256 keys for their
repositories that are upset about receiving a warning. APT 2.8.0 in
noble-proposed would bump the warning to an error, breaking them.
We also revoked additional ECC curves, which may
** Description changed:
[Impact]
We have received feedback from users that use NIST-P256 keys for their
repositories that are upset about receiving a warning. APT 2.8.0 in
noble-proposed would bump the warning to an error, breaking them.
+
+ We also revoked additional ECC curves, which may
** Description changed:
- APT 2.9.x and 2.8.0 revoke any of the non-asserted algorithms, we should
- modify the mechanism such that only RSA1024 is raised to an error to
- avoid unwanted regressions while still keeping the set of fully
- supported algorithms small.
+ [Impact]
+ We have received
falling into this string are producing an --audit message
only
** Summary changed:
- Only revoke RSA explicitly
+ More nuanced public key algorithm revocation
** Also affects: apt (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Oracular)
Importance: Undec
Implemented in https://salsa.debian.org/apt-
team/apt/-/merge_requests/365/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073126
Title:
Only revoke RSA explicitly
To manage notifications about
Public bug reported:
While evaluating libreoffice for the -fno-omit-frame-pointer option
presence we identified the following files as having missing flags:
libreoffice-core:
/usr/lib/libreoffice/program/libstaroffice-0.0-lo.so.0
- All compilations units.
libreoffice-draw:
: Undecided
Assignee: Julian Andres Klode (juliank)
Status: New
** Tags: foundations-todo
** Tags added: foundations-todo
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a mem
** Changed in: ubuntu-release-upgrader (Ubuntu Focal)
Status: Triaged => 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/1874272
Title:
Stage "searching for obsolete software" takes
** Tags removed: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2046386
Title:
Ubuntu Studio images aren't being built with a live user
To manage notifications about this bug go to:
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Milestone: ubuntu-24.04 => ubuntu-24.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874272
Title:
Stage "searching for obsolete
The grub patch linked seems similar in that grub is not clearing the
mode correctly when you enter grub text mode, i.e. the menu is drawn/you
enter the console.
However I don't think you are entering the text mode in grub at all, but
you jump straight to the kernel as part of flicker free boot -
** Changed in: apt (Ubuntu Noble)
Milestone: None => ubuntu-24.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060721
Title:
APT 2.8.0: Promote weak key warnings to errors
To manage
We could have warned on upgrades to 24.04, but there's little point in
worrying about mantic now, the update has been published, it has fully
phased, there's not going to be anyone affected by this anymore, and
mantic would be EOL by the time the fix would be ready.
--
You received this bug
You seem to be running an unsupported system that has not been usr-
merged, /lib, /lib64, etc should already be a symlink to /usr/lib,
/usr/lib64, etc. To convert to a supported file system layout, install
the usrmerge package.
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769297
Title:
resume from hibernation broken when resume image is autodetected
(UUID= syntax used)
To manage
** Changed in: htpdate (Ubuntu)
Assignee: (unassigned) => Adrien Nader (adrien)
** Also affects: openssl (Ubuntu)
Importance: Undecided
Status: New
** Tags removed: rls-oo-incoming
** Tags added: foundations-todo
--
You received this bug notification because you are a member of
Assigning this to Nick so we don't lose track of it and can discuss it
next week
** Tags removed: rls-oo-incoming
** Tags added: foundations-todo
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member
** Tags removed: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067672
Title:
[SRU] Openssl copyright/changelog.Debian.gz file points at non-
existent location
To manage
** Description changed:
The ELF package note metadata introduced in dpkg 1.22.6ubuntu11 (refined
in 1.22.6ubuntu14) can cause this failure:
```
gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined
```
This happens when the `-specs=/usr/share/dpkg/elf-package-
You could use the Lenovo Diagnostics menu that comes in the Lenovo
firmware, gotta press some key for options during boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067176
Title:
Boot and
The UBUNTU_CODENAME field is very useful to keep things like PPAs and
third-party integrations working with downstream distributions, such
that I don't think it makes sense to remove that and break them.
** Changed in: base-files (Ubuntu)
Status: New => Opinion
** Tags removed:
The following binaries from gcc-defaults are published in proposed and
need removing:
cpp-for-build cpp-for-host g++-for-build g++-for-host gcc-for-build gcc-
for-host gfortran-for-build gfortran-for-host gccgo-for-build gccgo-for-
host gdc-for-build gdc-for-host gm2-for-build gm2-for-host
*** This bug is a duplicate of bug 1883271 ***
https://bugs.launchpad.net/bugs/1883271
This is a duplicate of bug 1883271 and a merge proposal to fix it is in
https://code.launchpad.net/~xnox/launchpad/+git/launchpad/+merge/452749
** This bug has been marked a duplicate of bug 1883271
I guess we can still install it and see that it works correctly but it
essentially amounts to double verification given it's the same code. And
I'd rather do that as part of the 0.99.49.1 when we actually need to
check that source code handling is correct anyhow.
--
You received this bug
Do we really have a test plan for it? The original test plan no longer
applies, and the code is exactly the same as we have in software-
properties 0.99.48 + software-properties-qt 0.99.48.1 once-off. We don't
have the original 0.99.48 to reproduce the bad case anymore...
Maybe we should just
@racb It's fine to replace the other software-properties upload, there's
no value in releasing it on its own since it just merges software-
properties-qt back into the main package from the temporary once-off we
did to unblock the image building.
No point pushing updated software-properties-* to
Yes sure, this is expected, that's the DEP17 M4 mitigations
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070061
Title:
Clean up the DEP17 dpkg diversions
To manage notifications about this bug
After some testing lately, I'm trying to narrow down even more the
issue.
However this will take some time.
I'll keep you updated.
feeling so far:
after a sudo /sbin/dmsetup remove --force --retry X
and a sudo /sbin/multipathd reconfigure.
followed by a mount.
it triggers the block
Indeed, it also doesn't fit well with the new 3.0 UI, so my plan was to
actually move the messaging until the very end, after all packages have
been successfully installed.
We can't exactly print it after the Y/n prompt directly because then
hundreds of lines will zoom by and you don't see it,
I have a feeling you truncated the first output because it doesn't
actually remove a native libglib2.0-0 but libglib2.0-0:i386 only?
Since you did not go ahead with the removal of libglib2.0-0 anyway, the
packages did not end up becoming auto-removable, and hence `sudo apt
autoremove` did not
There is no mrcal upload that was set to incomplete, only a mrbuild, but
the SRU template was in comment #1 so I copied this to the description
** Description changed:
Due to an update to an unrelated package and insufficient communication
and the rush to get 24.04 out the door, this package
Public bug reported:
As per https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071233, the
debug symbols are stripped with custom strip commands in debian/rules,
causing no debug symbols to be split off, making it impossible to debug
bpftrace.
** Affects: bpftrace (Ubuntu)
Importance:
I'm going to mark this as Won't Fix for mantic given how late we are in
the mantic release cycle; and that it only affects those people who
upgraded early in the mantic development cycle.
** Changed in: python-apt (Ubuntu Mantic)
Status: Confirmed => Won't Fix
--
You received this bug
Yes I forgot the option existed and didn't have the context while
writing the comment, but generally speaking debconf is a crapshoot and
while it is there and it makes sense to use it accordingly, we certainly
should try to avoid introducing more of it.
The file here is a mess, so it's a conffile
Robie, debconf is not a database and any setting in there needs to be
read to a configuration file and any changes in the configuration file
need to be filled back into debconf. The integration for default cmdline
with /etc/default/grub is very complex and already broke a bunch of
times.
Drop-in
>I have a question about this - does the CPU usage stay high until you
run -F? Or will it over time diminish?
as soon as I trigger the command, the CPU usage goes down. And as I
stated before also all the related "Connecting" status -(old
attachment).
I would like to help out running a profiler,
Hi,
I just happened to experience something similar. However in my case the
multipath generates a ton of connections, locking the machine completely
- making it unresponsive.
This behaviour only happens in ubuntu 22.04.
The issue is hard to reproduce - it does not happen often.
but if I have to
** Summary changed:
- do-release-upgrade fails, mantic to noble
+ mantic->noble: E:Error, pkgProblemResolver::Resolve generated breaks, this
may be caused by held packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It seems you have uninstalled the Linux kernel meta packages and it
fails to install them as part of the upgrade. Please install linux-
generic before the upgrade and try again.
** Summary changed:
- do-release-upgrade fails
+ jammy-mantic: E:Error, pkgProblemResolver::Resolve generated breaks,
Thanks for your bug report. Sadly this doesn't have enough data to be
able to investigate it further, so I'm closing it. I'm sure one day
we'll accidentally stumble over a way to reproduce and sort out the
remaining permission issues.
Feel free to look at the specified files and correct their
This is a question for base-files, and as I have said on the mailing
list, we have technically committed to these version strings at archive
opening and it is used in various artefacts and third party places,
since we do set VERSION_ID in os-release - dpkg just inherits it.
** Also affects:
Public bug reported:
[Impact]
If you have Source Code enabled, and you change the pockets configuration to
"all pockets", it will add -backports without source code. The Source Code flag
will still be set in the UI, but after a reload, you can see it is in a mixed
state.
This is more notable
The ubuntu-release-upgrader fix for noble has been uploaded on the 5th
and is waiting for an SRU team member to approve it, then it will enter
proposed, and after validation, and 7 days of no complaints, it will be
released (not on Fridays).
So the earliest possible release date would be the
** Tags removed: rls-nn-incoming
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066995
Title:
apport-gtk keeps prompting to report crashes in a loop
To manage
** Tags removed: rls-nn-incoming
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068933
Title:
all reports with LaunchpadPrivate in them are tagged need-$arch-
** Tags removed: rls-nn-incoming rls-oo-incoming
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069041
Title:
Changing Port in sshd_config and restarting ssh.service
@Seb128 can we shove this over to desktop to do the design work on it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969394
Title:
'Settings & Livepatch' button opens 'settings' tab, not livepatch
The new LUKS2 format stores the metadata in a JSON document which
requires a JSON parser in grub. Given that Ubuntu does not support
encrypted /boot partitions, the decision was made not to enable the
feature such as to prevent the JSON code from becoming an attack vector
to break secure boot.
Reassigning to the correct package. This also needs a grub2-signed task.
We can pick this patch up or if you have experience working with a gbp-
pq managed repository you could propose a merge for that. Either way,
only the UEFI team can actually release any grub updates due to signing.
**
So the context you miss is that os-prober runs each time update-grub
runs on the system still.
The use case here is a highly unusual setup where another OS is directly
installed to a LUKS partition instead of using LVM on top of LUKS, and
one needs to balance whether this is a feature we care
$ reverse-depends -c main libgo23
Reverse-Depends
===
* libgo-14-dev
Packages without architectures listed are reverse-dependencies in: amd64,
arm64, armhf, i386, ppc64el, s390x
$ reverse-depends -c main libgo-14-dev
$ reverse-depends -c main lib32go-14-dev
$ reverse-depends -c main
Public bug reported:
All our architectures are supported by the standard Go toolchain, we
should demote the alternative gcc toolchain to universe, this includes
at least
libgo23 libgo-14-dev lib32go-14-dev libx32go-14-dev lib32go23 libx32go23
Possibly others but all the gccgo compilers
Untagging this, the patch could land via patch pilot, but this is not
really a high priority item.
** Tags removed: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/530252
Title:
** Tags removed: rls-nn-incoming
** Tags added: foundations-todo
** Changed in: glibc (Ubuntu Noble)
Assignee: (unassigned) => Simon Chopin (schopin)
** Changed in: glibc (Ubuntu Oracular)
Assignee: (unassigned) => Simon Chopin (schopin)
--
You received this bug notification because
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Tags removed: rls-nn-incoming
** Tags added: foundations-todo
** Also affects: ubuntu-release-upgrader (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects:
Moving this to the pp cycle as no replacement has appeared yet, so we
can look at it again in 5-6 months.
** Tags removed: rls-oo-incoming
** Tags added: rls-pp-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: rls-oo-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063467
Title:
needrestart should mark services as needing a restart in systemd
To manage notifications about this
** Changed in: glibc (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
** Tags removed: rls-oo-incoming
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think this is more a misunderstanding here, but the "workaround" is
the right solution for this issue.
Specifically, unattended-upgrades is exactly designed to give you less
preferable upgrades because the others are reserved for manual upgrades
(i.e. -security vs -updates). That is, the
I'd suggest raising this with the Debian maintainer in their bug
tracker, but this doesn't seem like a good thing to deviate on for a
community-maintained package, it seems more vital that it be kept
uptodate (currently it's synced automatically from Debian, then it would
need manual work) and I
I tend to agree with zhjs; even if we could force it, cross-grading
ncurses-bin could get hairy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067228
Title:
ncurses/i386 autopkgtest failure
To
** Summary changed:
- [FFe] [HWE] fwupd-efi 1.6 and gnu-efi 3.0.18
+ [SRU] [HWE] fwupd-efi 1.6 and gnu-efi 3.0.18
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060197
Title:
[SRU] [HWE] fwupd-efi
** Tags added: foundations-todo
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067886
Title:
Not being able to upgrade to 24.04 is (now) bug 2067886.
Also for 23.10 the bug was fixed in December in noble-proposed but the
SRU team never bothered releasing it in the 6 months and it got
overriden by a security update which also has been sitting around in
proposed since March now.
--
You
Public bug reported:
[Impact]
Upgrades for users with XFS /boot are wrongly blocked for noble as the
workaround for mantic hasn't been removed.
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
This is not an issue in the LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2039172
Title:
grub 2.12~rc1 fails to load files from large directories on XFS
To manage notifications about this bug
Sorry mawk is not actually essential, so in either case you miss a
Depends. Actually a PreDepends.
I do not believe a PreDepends: awk would work but I'm not sure - does it
require all awks to be configured or just one is the question.
--
You received this bug notification because you are a
The issue here is that apt is forced to remove libreadline8 to allow installing
libreadline8t64. The user has gawk installed which has the higher priority for
awk.
gawk is not essential so it doesn't have the immediate handling of an essential
package.
The python3-uno package uses awk in its
Public bug reported:
[Impact]
Upgrades to noble chmod /dev/null 644, breaking use of the device on multi-user
systems for non-root.
[Test plan]
1. do-release-upgrade mantic -> noble
2. check that /dev/null remains 666
[Where problems could occur]
[Details]
This is a regression of the fix for
Public bug reported:
[Impact]
If you set Dir::Cache or Dir::Cache::pkgcache to /dev/null, /dev/null is
chmodded as we chmod the cache file to 666. This is a semi-common pattern to
not use a cache, and breaks user scripts.
[Test plan]
1. autopkgtests run the large integration test suite
2. run
And sorry likewise, you also configured i386 which is only available on
archive.ubuntu.com and its mirrors.
So you can either drop that, why do you want i386 on arm?
Or you need to add Architectures: i386 to the archive.ubuntu.com
sources, and Architectures: arm64 to the ports.ubuntu.com ones.
This is to be expected, you have configured a mirror but you are using
an arm64 machine, which is only served by ports.ubuntu.com.
** Changed in: update-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
We're still going to need a couple more snapshots of backtraces - it's
important to check if we ever return from pkgDepCache::MarkInstall()
because I do not see an infinite loop in unattended-upgrades
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@jbicha can you provide input into why you removed the block-proposed
tag? This was breaking provisioning new CVM instances and it's not clear
to me that Azure has a new matching encrypt-cloud-image deployed that
would fix that issue.
--
You received this bug notification because you are a
@mfo The only autopkgtest regressions the bot mentioned and that are
visible still, are the ones I flagged earlier (albeit I don't know to
whom). That's software-properties-qt/unknown failing which is to be
expected - software-properties-qt got reabsorbed into this source
package so it cannot run
Public bug reported:
cups-browsed can hang at shutdown in a busy network, but there's nothing
important that requires it to have an ordered shutdown, so just set the
timeout to 0 to kill it immediately.
** Affects: cups (Ubuntu)
Importance: Undecided
Status: New
--
You received
I was looking at the status and made a mistake and changed it. Please,
revert it to Triaged when possible. Thanks and sorry for the
inconvenience.
** Changed in: horizon (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs,
So if you turn on Debug::pkgAcquire::Worker you should probably see it
fail after a @ Queue: Action combined for
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2003851
Title:
occasional hanging
The important point to note is that fetchAfter==0 is the default case if
we did not get retries, so every non-retried item has that value and we
don't want to cycle it. The loop's purpose is to find the smallest
timeout to wait for, as an _optimization_ to the select() call below,
such that if we
We're going to need to fix this properly rather than busy cycle the
queues outside the select loop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2003851
Title:
occasional hanging 'apt-get update'
Public bug reported:
New installation of Ubuntu 24.04 LTS: When I activated the "High
Contrast" accessibility option and opened the App Center, I noticed that
the text in the search bar was not adequately visible. The color of the
search bar background is very similar to the text color, making it
1 - 100 of 12211 matches
Mail list logo