Hi Christian,
At least one qemu guest is needed to reproduce the issue, correct? As I
couldn't with a simple install/uninstall.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905377
Title:
postrm f
Thanks for the additional info!
I tried to reproduce this with piuparts, as it performs an install-
upgrade-purge test by installing the package from the archive, upgrading
it using the package to test, and then trying to remove it. It doesn't
reproduce as apt-get detects the installed package has
Hello Adam and thanks for the additional information. It would be very
useful to gather more information from sssd in the moment it crashes (or
hangs and restarts). Could you try stopping the sssd service and running
it manually in foreground with a higher debug level? Something like:
sudo sssd
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857584
Title:
MySQL X protocol port 33060 listening on network by default
To manage notifications about this bug
** Tags removed: server-next server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857584
Title:
MySQL X protocol port 33060 listening on network by default
To manage notifications a
.
** Affects: germinate (Ubuntu)
Importance: Undecided
Assignee: Paride Legovini (paride)
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905987
Title:
germinate-upda
** Changed in: germinate (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905987
Title:
germinate-update-metapackage: wrong handl
Hello Max and thank you for your bug report. The logs show that MySQL
couldn't start because a lock was already held:
2020-11-29T15:47:55.240238Z 0 [ERROR] [MY-011300] [Server] Plugin mysqlx
reported: 'Setup of socket: '/var/run/mysqld/mysqlx.sock' failed, can't
create lock file /var/run/mysqld/my
** Changed in: etckeeper (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860769
Title:
should record changes after snap transactions
To manage notificati
** Changed in: etckeeper (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/1860769
Title:
should record changes after snap transactions
To manage notificat
Hello and thanks for this bug report. I can confirm the issue affects
both Ubuntu and Debian. Given that the bug doesn't interfere with the
most common use cases of gpsd, and that gpsd is currently a sync from
Debian, I believe this bug would be best fixed in Debian. Ubuntu will
then pick up the fi
Hello Andreas and thanks for this bug report. I can reproduce the issue
you describe on Focal and Hirsute. A very similar command is given as an
example in pmt-ehd's manpage (pmt-ehd(8), not installed by libpam-mount-
bin but available in the source package, see [1]).
I'm marking this bug as Triag
Thank you Alexander for the additional information. I noticed you are
using Ubuntu 20.10. Is the missing subdomain problem you are observing a
regression of Ubuntu 20.10, or is the problem present even with earlier
version of Ubuntu (e.g. 20.04 LTS)?
Setting up a reproducer for this kind of issue
Hello Ritesh and thanks for this bug report. According to the attached
logs MySQL failed to start because it couldn't create the lock file for
mysqlx:
2020-12-02T16:32:19.508811Z 0 [ERROR] [MY-011292] [Server] Plugin mysqlx
reported: 'Preparation of I/O interfaces failed, X Protocol won't be acce
xorriso now fails with (full error below):
SORRY : Cannot make proposal to produce APM of loaded image
however this is not obvious from the logs because of a /dev/null
redirect. I think it's safe to drop it, see
https://github.com/canonical/subiquity/pull/900.
Full xorriso error:
$ xorriso -
Thanks for this bug report. This is fixed already in Hirsute (the
current development release) in version 2:3.55-1ubuntu4, but as you
noted the bug still affects Groovy.
** Changed in: nss (Ubuntu)
Status: New => Triaged
** Also affects: nss (Ubuntu Groovy)
Importance: Undecided
Hi Nisha,
We love squashing bugs, but we can't help doing so in other
distributions. If you're already running the latest version of OpenWRT
my suggestion is to file a bug report there and point the OpenWRT devs
to this bug report, it should ease their debugging work and provide
justification for
Hi Eugene,
I could reproduce the issue from a clean Hirsute VM. Steps:
1. lxc launch ubuntu-daily:hirsute paride-h-vm --vm
2. lxc exec paride-h-vm bash
3. apt update
4. apt full-upgrade
5. apt install postfix
# Debconf config as: Satellite system.
# All the rest left with default values
6.
Note: the very same steps in a ubuntu:focal VM do not lead to the same
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916541
Title:
smtp "fatal: unknown service: smtp/tcp", probably after lib
Can't be reproduced with the latest 5.8 kernel; likely fixed upstream
by:
https://lkml.org/lkml/2020/9/4/259
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Changed in: clamav (Ubuntu Xenial)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926300
Title:
clamdscan - MULTISCAN parameter causes Segmentation fault er
Hi Codrin,
Please note that Xenial reached end of standard support on April 30
2021. Extended Security Maintenance for Xenial is provided to customers
through Ubuntu Advantage. See:
https://lists.ubuntu.com/archives/ubuntu-announce/2021-March/000266.html
--
You received this bug notification be
(Sorry for the duplicate comment, apparently me and Marc were replying
at the same time. The good thing that we both pointed to the very same
announcement!)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Changed in: simplestreams (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908452
Title:
MAAS stops working and deployment fa
** Also affects: simplestreams (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: simplestreams (Ubuntu Focal)
Status: New => Triaged
** Changed in: simplestreams (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a
smoser sponsored the upload:
$ dput ubuntu ../out/simplestreams_0.1.0-46-gb1f40d99-0ubuntu1_source.changes
Checking signature on .changes
gpg: ../out/simplestreams_0.1.0-46-gb1f40d99-0ubuntu1_source.changes: Valid
signature from 1E4410A4024BC6F0
Checking signature on .dsc
gpg: ../out/simplestream
Hi,
The python3-flake8 package currently in focal-proposed depends on
packages which are not in focal-proposed, and is therefore
uninstallable:
The following packages have unmet dependencies:
python3-flake8 : Depends: python3-pycodestyle (>= 2.6.0) but it is not going
to be installed
Hello Sven and thanks for this bug report. It seems that the
NO_AUTO_CREATE_USER option is set in a custom config file you have on
your system (/etc/mysql.conf.d/sdnet.cnf). From the logs you posted:
MySQLConf.etc.mysql.conf.d.sdnet.cnf:
[mysqld]
# Disable "ONLY_FULL_GROUP_BY" for SDNET / RIM
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I tried to reproduce the issue from a clean LXD container but wasn't
able to: rabbitmq-server installed just fine. If you want to try this
yourself you could do something on these lines:
$ lxc launch ubuntu:hirs
** Tags added: verification-failed-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883175
Title:
Missing code linter support for python3.8 language features
To manage notifications about this
Hello Dominik and thanks for this bug report. An umbrella bug report
doesn't really help here, especially given that there's no single "reset
config files on updates" policy in Ubuntu. Actually it's quite the
contrary: as a Debian derivative Ubuntu basically inherits [1] and in
particular [2].
Ple
Hello Robert and thanks for this bug report. The attached logs show
errors like:
Cannot stat file /proc/4232/fd/5: Permission denied
Cannot stat file /proc/4232/fd/6: Permission denied
Cannot stat file /proc/4232/fd/7: Permission denied
Cannot stat file /proc/4232/fd/8: Permission denied
happenin
** Changed in: simplestreams (Ubuntu Focal)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908452
Title:
MAAS stops working and deploym
Hi Logan,
There were no updates in that time window. As you can't reproduce the
problem I'm marking this bug report as Invalid. Should you find out
there's actually an issue here, possibly requiring some different
conditions to be triggered, please feel free to change the bug status
back to New an
** Description changed:
+ [Impact]
+
+ The bug is about simplestreams possibly getting stuck waiting forever
+ for an an HTTP response that never comes, e.g. because of networking
+ issues. This can potentially affect any package depending on
+ simplestreams, but specifically it was reported affe
** Changed in: simplestreams (Ubuntu Focal)
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/1908452
Title:
MAAS stops working and deployment fails after `Loading
** Changed in: nss (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931104
Title:
Test of dogtag-pki is failing on s390x vs the
** Changed in: keepalived (Ubuntu Bionic)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795420
Title:
[SRU] Keepalived update from 1.2.19
** Changed in: samba (Ubuntu Focal)
Assignee: (unassigned) => Paride Legovini (paride)
** Changed in: samba (Ubuntu Groovy)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: simplestreams (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: simplestreams (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: simplestreams (Ubuntu Groovy)
Assignee: (unassigned) => Paride Legovini (paride)
** Chan
** Changed in: simplestreams (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: simplestreams (Ubuntu Groovy)
Status: In Progress => Fix Committed
** Changed in: simplestreams (Ubuntu Hirsute)
Status: In Progress => Fix Committed
--
You received this bug not
** Changed in: samba (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/1914420
Title:
/usr/sbin/smbd:6:volume_label:smbd_do_qfsinfo:smbd_smb2_request_process_g
Hi Mark,
My guess is that you have a `search .` line in your /etc/resolv.conf.
The postfix postinst script tries to guess the machines FQDN in several
ways, and one way is concatenating with a '.' the local hostname and the
resolv.conf "search" domain. You can see this logic here:
https://git.lau
** Changed in: pmdk (Ubuntu Hirsute)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931063
Title:
Include powerpc port upstream fixes
*** This bug is a duplicate of bug 1906970 ***
https://bugs.launchpad.net/bugs/1906970
@Mark happy that it worked and thanks for marking this as a duplicate.
It seems that `search .` should be supported after all, I'm adding more
information to LP: #1906970, in case you want to follow.
--
Yo
Sergio (~sergiodj) did some digging on `search .` and found out that it
should be supported after all. I'm copy/pasting here his email to
ubuntu-server@lists.u.c for future reference:
=== Message-ID: <87k0msqlzy@ubuntu.com> ===
I think the reporter from #1906970 is right: it seems that "searc
Hello and thanks for your bug report. This log excerpt suggest that you
installed or are trying to install an unofficial or modified mysql
package:
DuplicateSignature:
package:mysql-server-8.0:8.0.25-0ubuntu0.20.04.1
Setting up mysql-server-8.0 (8.0.25-0ubuntu0.20.04.1) ...
/var/lib/dpkg/info/m
Hello Lloyd,
That *may* be a bug related but different from this one. Apparently you
have an ExcludePath that triggers this warning:
LibClamAV Warning: cli_realpath: Invalid arguments.
and then clamdscan segfaults. I'd try to identify the ExcludePath rule
causing the warning and check if remov
Hello Steve and thanks for your bug report. It seems that dovecot is
failing to start because a systemd mount unit has been masked:
Failed to restart dovecot.service: Unit var.mount is masked.
I think this can only be the result of manually masking the unit via
`systemctl mask`. In this case th
I meant "Hello Mark", I mixed up two bug reports, I'm sorry :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933750
Title:
package dovecot-core 1:2.3.7.2-1ubuntu3.4 failed to install/upgrade:
in
Hello Steve and thanks for your bug report. It seems that dovecot is
failing to start because a systemd mount unit has been masked:
Failed to restart dovecot.service: Unit var.mount is masked.
I think this can only be the result of manually masking the unit via
`systemctl mask`. In this case th
The reply was meant for a different bug report, I'm sorry for the
confusion. By sheer luck I'll be able to reuse most of it here :-).
According to the logs mysql is failing to start because:
[ERROR] [MY-012209] [InnoDB] Multiple files found for the same tablespace ID:
[ERROR] [MY-012202] [InnoDB]
@Michael: the installer: output should still be present, but
only as a printout in the console output (/dev/console), cloud-init
doesn't log it anymore in cloud-init-output.log. This is the relevant
change:
https://github.com/canonical/cloud-
init/commit/b794d426b9ab43ea9d6371477466070d86e10668
-
Hi, I did some digging here and I think we're dealing with two different
issues.
(1) I can reproduce the FATAL error given in the original bug
description on a Xenial system, but not on Bionic, where keepalived
understands the syntax.
(2) However in Bionic I get the following error when trying to
** Changed in: keepalived (Ubuntu Xenial)
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/1795420
Title:
[SRU] Keepalived update from 1.2.19 to 1.2.24 breaks suppor
** Summary changed:
- [SRU] Keepalived update from 1.2.19 to 1.2.24 breaks support for /dev/tcp
health check
+ Keepalived update from 1.2.19 to 1.2.24 breaks support for /dev/tcp health
check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
The /usr/share/doc/keepalived/samples/keepalived.conf.vrrp.localcheck
sample configuration file shows how to check if a TCP port is open using
a `script`, e.g.:
vrrp_script chk_http_port {
script "https://github.com/acassen/keepalived/issues/1926
** Affects: keepalive
Note for context: this is a spin-off from LP: #1795420.
** Bug watch added: github.com/acassen/keepalived/issues #1926
https://github.com/acassen/keepalived/issues/1926
** Also affects: keepalived via
https://github.com/acassen/keepalived/issues/1926
Importance: Unknown
Status: Un
if a TCP port is open, e.g. something like:
script "bash -c ' Fix Released
** Changed in: keepalived (Ubuntu Bionic)
Assignee: Paride Legovini (paride) => (unassigned)
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Bu
Hello Bill,
I agree with Matthias' reply: fetchmail seems to be working just as
expected. Also please note that we use this bug tracker to work on bugs
in Ubuntu, so feature requests like a per-account SOCKS4a config
parameter don't really fit here; at a first look the right venue would
be [1].
I
Public bug reported:
Please promote the following binary packages built from src:fuse3 to
main:
- libfuse3-3
- libfuse3-dev
[Availability]
The inclusion of fuse3 in Ubuntu is fairly recent, first being imported
in Focal as a sync from Debian, however its predecessor src:fuse from
the same u
Hello Codrin and thanks for your bug report. From your testing it seems
to me that the segfault is triggered by using --fdpass together with
--multiscan, rather than by --multiscan alone. From your comment to [1]
it seems that you agree.
I think the "base" upstream bug here is [2], which according
** Tags added: regression-update
** Also affects: clamav (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: clamav (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: clamav (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed
Thanks Utkarsh. TIL that by default the apt resolver ignores the
alternative build-dependencies, considering only the first one. The
package builds with the apt resolver specifying --resolve-alternatives.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Hello and thanks for this bug report. I had a look a the runc bug
reports and changes to see if I could easily spot a relevant change, but
I couldn't. I don't have a good hypothesis of what could be wrong, but
I'd start checking if the newer runc is causing a higher memory or CPU
usage, causing com
Hi Bob and thanks for this bug report. In debugging this it would
greatly help to have a reproducer from a clean Focal system, e.g. a LXD
container. You can get one by doing:
lxc launch ubuntu:focal nagios-debug
lxc exec nagios-debug bash
and then provide a minimal but complete set of steps t
Hello Dominic and thanks for this bug report. I agree it would make
sense to add DoH support in the current Ubuntu development release
(Impish), however I think the required change should ideally be made in
Debian (rationale: avoid adding a delta to a sync and we're early in the
devel cycle). Ubunt
Hi Mark and thanks for this bug report. The clamav d/changelog for
version 0.102.2+dfsg-1 has this entry:
* Set ReceiveTimeout to 0 which is upstream default.
dated 2020-02-09. In 2018 the timeout was bumped from 5s to 30s to solve
[1], but apparently 30s aren't enough in some scenarios. I ackn
Hello and thanks for this bug report. From the attached terminal log I
guess you manually interrupted the upgrade process at some point. Was it
stuck, and for how long?
In general there isn't really enough information here for a developer to
confirm this issue is a bug, or to begin working on it,
Hello Ross and thanks for this bug report. Did you actually verify that
adding a
BrowserMatch " Konqueror/5" redirect-carefully
line to setenvif.conf resolves the issue?
Anyway the file belongs to the packaging and not to the upstream source,
so the fix belongs to Ubuntu. Waiting for your feed
Hi, I went a bit down the rabbit hole Sergio mentioned and found the
same old reports and nothing really useful. I'd also be curios to see if
the problem still occurs with the newer releases.
Did you see this happen on more that one machine/deployment?
The backtrace didn't suggest my anything, bu
Thanks David for this bug report. I think this bug belongs to the
resource-agents package and not to pacemaker. Please note that resource-
agents is in the "universe" component of Ubuntu, and therefore only gets
community support. (Ubuntu 21.10 will also offer a resource-agent-
supported package of
Hi David, on "main" vs "universe" see:
https://help.ubuntu.com/community/Repositories/Ubuntu
For community help, possibly on driving a Stable Release Upgrade, see:
https://ubuntu.com/support/community-support
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Public bug reported:
[Somehow adapted from the linked Debian bug]
Newly created (but possibly also existing) schroots with mk-sbuild and
sbuild-launchpad-chroot are missing target/usr/libexec/qemu-binfmt/.
This leads to errors like:
$ schroot -c
E: 15binfmt: touch: cannot touch
'/var/run/schro
For reference, the Debian MR is:
https://salsa.debian.org/dns-team/unbound/-/merge_requests/14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927877
Title:
DoH support is disabled
To manage notifi
I'm marking this bug as Triaged: I didn't try to reproduce it locally,
but I think it's clear enough we have a bug here. Also tagging this as a
regression.
** Changed in: runc (Ubuntu)
Status: Incomplete => Triaged
** Tags added: regression-update server-next
--
You received this bug not
I just noticed this affects torkoal (cloud-init
20.4.1-0ubuntu1~18.04.1). On reboot we have:
[ 36.428237] cloud-init[4810]: failed run of stage modules-config
[ 36.428373] cloud-init[4810]:
[ 36.428434] cloud-init[4810]: Traceback
** Also affects: sosreport via
https://github.com/sosreport/sos/issues/2495
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922925
Title:
version.txt
Hello Niklas and thanks for this bug report. In short, my suggestion
here is to file this bug against the unbound Debian package [1]. The
rationale is:
- The unbound Ubuntu package is currently a sync from Debian, which means it
carries no Ubuntu specific changes. Fixing this in Debian minimizes
Hi Guilherme,
Answering your question in comment #6:
> Why one method executes from DataSourceAzure.py
> whereas the other from azure.py?
The reason is not that interesting and won't really help here. Some log
messages generated in DataSourceAzure.py are logged using a helper
function defined in
** Also affects: subiquity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923045
Title:
cloud-init + installer not creating user accounts
To manage noti
Hi again Guilherme,
I don't think there's any useful information hiding in the fact that
cloud-init logs some messages as DataSourceAzure.py[DEBUG] and others as
azure.py[DEBUG]. Look at:
https://github.com/canonical/cloud-
init/blob/45db197cfc7e3488baae7dc1053c45da070248f6/cloudinit/sources/Data
Hi Hadmut and thanks for your additional debugging work here and for
sharing your findings.
I agree this looks like a documentation issue: especially the fact that
the 'identity' and 'user-data/users' sections are mutually exclusive and
'lock_passwd' need better documentation and possibly some exa
Hi, I don't think that's a viable option as cloud-init may very well be
the component that allows the network interface to be configured with a
routable address, so we can't wait such an address to be available
before configuring the machine, at least not in general.
--
You received this bug noti
*** This bug is a duplicate of bug 1922739 ***
https://bugs.launchpad.net/bugs/1922739
** This bug has been marked a duplicate of bug 1922739
AttributeError: 'DataSourceNoCloud' object has no attribute 'vendordata2_raw'
--
You received this bug notification because you are a member of Ubu
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
Hello Bill and thanks for this bug report. I can see the issue you
described here (thanks for the reproducer), however I believe it should
be filed/fixed upstream. Maybe [1] should be expanded to cover --remove-
source-files, as the two issues could be related.
Diverging from upstream (or from Deb
** Changed in: cloud-init (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/1919177
Title:
Azure: issues with accelerated networking on Hirsute
To manage notif
Hello Gauthier and thanks for this bug report. What you describe looks
very much like this issue:
https://github.com/canonical/ubuntu-advantage-client/issues/1502
Do you think that could be it? I.e, do you hit the problem using Pro
images on Azure?
** Bug watch added: github.com/canonical/ubuntu
Hello Andrea and thanks for this bug report. A similar bug has been
filed in Debian back in 2013:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714275
and tagged as wontfix. AIUI the problem is that arch-specific manpages
do not exist for all the archs, and the qemu-system-ARCH manpages
bas
Hello and thanks for this bug report. You mentioned you hit this problem
from a fresh 21.10 install, however two things that caught my attention:
- The package you are trying to install is for i386, for which there is no
installation media for Impish. I guess you added i386 as a foreign
archite
** Changed in: tomcat7 (Ubuntu Xenial)
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/1666570
Title:
Post install script has error in RegEx
To manage notification
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
There isn't really enough information here for a developer to confirm
this issue is a bug, or to begin working on it, so I am marking this bug
Incomplete for now.
If you can provide exact steps so that a developer
Hi Paolo and thanks for your bug report. I'm not sure I fully understand
the issue you're describing here (adding "expected result" and "actual
result" sections would help), but my impression is that you are
describing a (mis?)behavior of PHP as released upstream, rather than an
Ubuntu-specific iss
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934997
Title:
Authentication fails after upgrading sssd to 2.2.3-3ubuntu0.6
To manage notifications about this bug go
Public bug reported:
[Summary]
Please promote bin:libnet-snmp-perl to main. It's the only binary
package built by src:libnet-snmp-perl. The package is a "new" dependency
of bin:amavisd-new which is in main. I say "new" in quotes because is
was already a dependency, but d/control missed it up to v
After some work and testing, here are my findings.
- The dogtag-pki autopkgtest failure is manually reproducible
using autopkgtest-virt-lxd.
- The dogtag-pki autopkgtests pass with in Impish using
libnss3 *from the archive* (uploaded and built on Hirsute).
- The dogtag-pki autopkgtests FA
Rebuilding the same source package on Groovy produces a "good" libnss3
package (the Impish dogtag-pki autopkgtests pass when using it). This
means that a build-dependency that was upgraded in Hirsute caused the
regression.
(As Christian made me notice rebuilding on Hirsute *release* with no
update
Diff of the sbuild Installed-Build-Depends from the "good" Hirsute build
that produced the nss packages now in the archive and a "bad" Hirsute
build done in an up-to-date Hirsute schroot:
--- good2021-07-21 12:02:03.870339411 +0200
+++ bad 2021-07-21 12:03:20.367850047 +0200
@@ -3,38 +3,39
My plan is now to:
- Setup a Groovy container
- Build nss 2:3.61-1ubuntu2 and verify the libnss3 is good
- Add Hirsute to sources.list and manually update the
Build-Deps, starting from the usual suspects (compilers),
hopefully finding which package breaks the dogtag-pki tests.
The testbe
1 - 100 of 1545 matches
Mail list logo
