** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
Importance: Undecided
Status: New
** Also affects: lm-sensors (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Hello munbi and thanks for this bug report. I marked the other two bugs
you filed as duplicates of this one, and added "tasks" for the packages
you filed the other bugs against. One bug report can track a problem
across several packages, so there's no need for multiple reports.
I don't think xserv
Hi Alessandro and thanks for this bug report. This is the kind of fix
that can be backported to existing stable releases using the SRU process
[1]. Given that every change comes with a regression risk, the most
important ingredient of a SRU is the broken use case that the proposed
upgrade fixes, se
Hello and thanks for your bug report. From the logs it seems that mysql
failed to start because of another "stray" instance of mysql running in
background:
2021-02-03T22:28:02.718655Z 0 [ERROR] [MY-011300] [Server] Plugin mysqlx
reported: 'Setup of socket: '/var/run/mysqld/mysqlx.sock' failed, ca
Hello and thanks for your bug report. From the logs it seems that mysql
failed to start because of another "stray" instance of mysql running in
background:
2021-02-03T08:20:14.195877Z 0 [ERROR] [MY-011300] [Server] Plugin mysqlx
reported: 'Setup of socket: '/var/run/mysqld/mysqlx.sock' failed, ca
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since there isn't enough information in your report to differentiate
between a local configuration problem and a bug in Ubuntu, I'm marking
this bug as Incomplete.
If indeed this is a local configuration problem,
** Also affects: libisoburn (Ubuntu)
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/1914587
Title:
make-edge-iso.sh fails on focal/ppc64el images
To manag
Well, those tens-of-gigabytes image sizes are definitely not normal. I
tried to make xorriso output to stdout to make it skip the free space on
target partition check, but it failed in the same way.
I added a libisoburn (= xorriso) task to this bug and subscribed Thomas
Schmitt, in case he wants t
** Also affects: clamav via
https://bugzilla.clamav.net/show_bug.cgi?id=12672
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/1915095
Title:
clamscan m
Hi,
The interesting bits of the script are at [1], however more concise
steps to reproduce are:
1. download [2]
2. xorriso -indev focal-live-server-ppc64el.iso -report_el_torito as_mkisofs
This generates a list of "as mkisofs" options containing the '--
interval:local_fs:1718121313d-3352666579d'
Hi Ante and thanks for this bug report. According to what I see in the scripts
the certs gets copied over: it happens via /lib/systemd/system/postfix@.service
which has this
ExecStartPre directive:
ExecStartPre=/usr/lib/postfix/configure-instance.sh %i
and configure-instance.sh copies the cert
A reload is not enough to trigger a configure-instance.sh run, a full
restart is needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915238
Title:
warning: /var/spool/postfix/etc/ssl/certs/ca-cer
** Changed in: postfix (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/1915238
Title:
warning: /var/spool/postfix/etc/ssl/certs
Thank you for your report. We're not aware of any major issue affecting
the virtualization stack distributed with Ubuntu Focal: if it was broken
as badly as you describe we'd be certainly receiving many bug report
about it. This is not to easily dismiss your bug report as "not a bug,
local corrupti
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Since there isn't enough information in your report to
differentiate between a local configuration problem and a bug in Ubuntu,
I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, y
** Also affects: casper (Ubuntu)
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/1804334
Title:
Live/overlayfs apparmor DENIED open "upper/etc/mysql/conf.d"
Thanks for this bug report. This is in my opinion more a casper (= live
system) issue than an issue with the specific package providing the
AppArmor profile, so I added a casper task.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Hello Richard and thanks for this bug report. According to the manpage
the -f option is equivalent to the --rfcomm long option, which isn't
really well documented. Just to check: are you actually trying to use
netstat in rfcomm mode? My impression is that --rfcomm is a legacy
option superseded by -
Hello Bryan and thanks for this bug report. I tried to build ipmitool in
a clean Focal LXD container and couldn't reproduce the issue. In short
what I did is the following:
1. lxc launch ubuntu:focal paride-f
2. lxc exec paride-f bash
3. uncommented the relevant deb-src lines in /e/a/sources.list
Hello and thanks for all the debugging work here. I agree with your
analysis, I think that we have a bug here and the fix you proposed LGTM.
However despite my efforts I couldn't reproduce the segfault. I
specifically tried with ubuntu-minimal:focal containers with just
apache2 and libapache2-mod-p
Hello Rolf and thanks for this bug report. I can't reproduce the issue
you described neither on my laptop, which has been following Ubuntu
"devel" for quite some cycles now, nor in a clean LXD container running
Hirsute.
You brought freeradius as an example, but freeradius *does* ship with a
system
Hi Yuan, please do not call the /etc/init.d scripts directly, they're
not guaranteed to work as one may expect and are in good part a legacy a
pre-systemd times. Please use systemctl(1) instead, e.g.:
$ systemctl status mysql
$ systemctl stop mysql
$ systemctl start mysql
and similar.
**
The [homes] section is commented out in the provided smb.conf. I could
reproduce it locally by running:
$ net usershare add games /tmp/X
net usershare add: share name games is already a valid system user name
again with [homes] commented out (the default). This seems to be a known
limitation
Hi,
By proposing to set the status to Wontfix I recognize that not being
able to setup usershares named like users can be an annoyance, at least
in some cases, but realistically we're not going to put any effort
towards fixing it. We certainly won't deviate from samba upstream: the
regression pote
I'm setting this to Fix Released again, as the fix released with curtin
20.1-29-g81144052-0ubuntu1 did address the curtin bug. The remaining
issue (LP: #183) was in the kernel and that's Fix Released too.
** Changed in: curtin (Ubuntu)
Status: Fix Committed => Fix Released
--
You rece
Hi,
The PR you linked hasn't been merged yet, and indeed
https://github.com/nmap/nmap/issues/1176 is still open. Even after this
is fixed in a new upstream release of nmap I personally doubt the fix
will be backported to Focal, it doesn't tick enough boxes in [1].
However once the package will be
** Bug watch added: github.com/net-snmp/net-snmp/issues #233
https://github.com/net-snmp/net-snmp/issues/233
** Also affects: netsnmp via
https://github.com/net-snmp/net-snmp/issues/233
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a me
I found the upstream bug for this issue:
https://github.com/net-snmp/net-snmp/issues/233
The fix landed in the upstream master and V5-9-patches branches [1], but
the issue is still open lacking verification. The patch doesn't apply
cleanly on version 5.8, the version currently in Focal, Groovy an
** Also affects: libpam-mount (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: pcre2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: libpam-mount (Ubuntu Focal)
Status: New => Triaged
--
You received this bug notification because you a
This was fixed in Debian by [1] and landed in Hirsute as part of a sync.
The fix won't land in Focal automatically, it's Stable Release Update
[1] that has to be driven manually.
[1]
https://salsa.debian.org/debian/libpam-mount/-/commit/c166793d582048587a4091a6deed9824b535f4c8
[2] https://wiki.ub
Hi Sergio,
I did manage to reproduce the crash by lowering SNMP_MAXBUF_SMALL and
rebuilding the package, as Graham suggested. I couldn't generate a
certificate crashing snmpd with the default value of 512, but most
likely I didn't manage to add a very long extension to the certs I
generated.
In m
Hi,
I think that part of the comments here are actually related to LP:
#1900642, which is now fixed in groovy-updates and hirsute. However
initial bug description from Ian Collier specifies that this bug report
is about the case where a valid sssd.conf exists, but sssd fails to
start due to a diff
** Also affects: systemd (Ubuntu)
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/1908065
Title:
Invalid SYSLOG_PID for (systemd) journal messages
To manag
Hi Valters,
This really seems to be a systemd issue: sssd never sets SYSLOG_PID when
calling sd_journal_send(), yet journalctl shows e.g. SYSLOG_PID=sudo
instead of an empty string. Looks like systemd is mixing the variables
or leaking one into the others. The sssd upstream patch you pointed to
ma
I'm changing the main bug task to Fix Released as IIUC this is fixed in
>= Groovy.
Still valid and in our queue for Focal, needs a SRU.
** Changed in: sysstat (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: netsnmp via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964054
Importance: Unknown
Status: Unknown
** No longer affects: netsnmp
** Also affects: net-snmp (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964054
Importance: Unknown
Sta
I subscribed Jacek Oleskow to the bug as he reported he has several
affected systems, maybe he'll be able to help with the verification.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858763
Title:
Hi RedScourge,
the attached patch is a bit dirty, probably because it has been
generated by diffing apache2ctl from different package versions, and I
think it has a bug: you call
systemctl start "$APACHE_SYSTEMD_SERVICE"
in the 'restart|graceful)' case stanza, while we want 'systemctl reload'
** 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/1885527
Title:
cloud-init regenerating ssh-keys
To manage notifications about this
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I tried to reproduce this problem in a fresh Ubuntu Focal install by
installing mysql-server-8.0 and then mariadb-server with the same
commands you gave as they appear in the attached DpkgHistoryLog:
apt-get ins
** Changed in: ipmitool (Ubuntu)
Importance: Wishlist => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864612
Title:
requests ipmi-tool to include lasted patch for supporting quanta
server
Hi,
While the new livecd-rootfs unblocked the snapd seeding, it seems that
it triggered another problem later in the subiquity install process.
The 20200729.1 bionic-live-server-amd64 image now fails to install
because /media/filesystem/var/lib/snapd/seed/seed.yaml is missing. The
full install lo
Note: the bionic-live-server 20200729.1 images have been built with
-proposed enabled. Build log:
https://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-
server/bionic/daily-live-20200729.1.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
OK, I set this bug back to Fix Committed, thanks for looking into this.
I like the idea of patching subiquity so it doesn't assume a seed.yaml
is there, as it's not a broken configuration by itself.
** Changed in: livecd-rootfs (Ubuntu Bionic)
Status: New => Fix Committed
--
You received
** Changed in: ndctl (Ubuntu)
Status: New => 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/1889172
Title:
upgrade ndctl v69
To manage notifications about this bug go to:
https:/
Hi Mauro,
Thanks for your follow-up comment and analysis in LP: #1605948, we are
however not able to do debugging work or provide support for non-Ubuntu
distributions. If you are able to provide steps to reproduce the issue
in a clean Ubuntu system we'll certainly look into it, being glad to
know
*** This bug is a duplicate of bug 1592669 ***
https://bugs.launchpad.net/bugs/1592669
Replied to LP: #1605948, as this bug report is marked as a duplicate of
it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Hi Cliff,
This is odd, but if I understand correctly you have a setup that
triggers the problem and a slightly different setup that does not, on
the same system. This means we are in a good position already. I'd
follow Christian's suggestion and make them even more and more similar
until you can s
Thanks for this bug report. The problem can be reproduced by running the
following in a fresh Focal LXD container:
apt update
apt install mariadb-server
apt remove mariadb-server
apt install mysql-server
At this point mysql is in a very broken state. Its systemd units looks
masked:
# s
Hello Nicholas and thanks for reporting this bug. The log files you
attached make me think that you had a running instance of mysqld which
had been started manually - or in any case without using the systemd
unit. For example:
2020-07-29T04:06:16.742135Z 0 [Warning] [MY-011810] [Server] Insecure
c
Hello Simon and thanks for your bug report and for the detailed steps to
reproduce it. The command causing the error is mysql_upgrade, which can
also be run manually, without triggering the execution of the postinst.
The command has been dropped in mysql-8, as the upgrade is now done
automatically
** Changed in: mysql-5.7 (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/1889472
Title:
mysql-server-5.7 postinst fails when in read-only mode
To manage notific
As noted by Robie @racb this is fundamentally a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1490071
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
OK, so the directory being in /home is the culprit, I could reproduce
the issue and found where the problem is. At some point rsync added
ProtectHome=on
option to its service file, /lib/systemd/system/rsync.service. This has been
reverted in upstream git at [1] as it's too restrictive. The f
I tested an ISO image with bionic-proposed enabled [1] and I can confirm
livecd-rootfs 2.525.45 fixes this bug.
[1] https://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-
server/bionic/daily-live-20200729.1.log
--
You received this bug notification because you are a member of Ubuntu
I think this is basically a duplicate of LP: #1833586. SRUing the fix
was discussed there but vorlon was not positive about it, see comment #6
there.
I'm marking the open-iscsi task as Triaged, but if stick with Steve's
opinion then this is to be considered a Won't Fix.
** Also affects: open-iscs
Hello and thanks for this bug report. I am able to reproduce the issue,
which interestingly is not present in Groovy. I installed tmux 3.1b-1
from Groovy on a Focal system and it *does* set the utmp entries, so
something must have changed between tmux 3.0a-2 and 3.1b-1. I had a look
at the Ubuntu (
Hello and thanks for filing this bug report. Looks like that mysql
failed to start because its TCP port was already in use:
2020-08-12T12:40:32.253089Z 0 [ERROR] [MY-010262] [Server] Can't start server:
Bind on TCP/IP port: Address already in use
2020-08-12T12:40:32.253564Z 0 [ERROR] [MY-010257]
Hi Christian and thanks for this bug report. I see that unbound is
linked against libpython3.6 (only), so I think it requires
python3-unbound instead of python-unbound.
Note that Python 2 reached its end of life and it's been mostly removed
for the newer Ubuntu versions, python-unbound in particul
I think that a more acceptable workaround would be adding a script to
/usr/lib/systemd/system-sleep/
that stops the service pre-sleep and starts it post-sleep. See systemd-
sleep(8) on how this can be implemented. I'd then propose it to the
Debian package maintainers; Ubuntu will then pickup th
** Changed in: libvirt (Ubuntu)
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/1887592
Title:
virsh list hangs because of qemu-system-i386 defunct so libvirtd ha
Hi,
What you describe appears to be an upstream change and it can't be
considered as a bug in Ubuntu. There are several threads with requests
similar to yours with proposed workarounds which I hope you'll find
helpful:
https://github.com/tmux/tmux/issues/1115
https://github.com/tmux/tmux/issues/1
** Also affects: autofs (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968675
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/1891548
Tit
Hi Michael and thanks for all the digging. If I understand correctly
there are two issues here:
1. The slapd crash due to the caseExactMatch/caseExactIA5Match typo, for
which you submitted a fix upstream [1].
2. The need to "start ; stop ; restart" the slapd service in order to
avoid the "invalid
Hi,
I'd say that the problem is with mysqld using a different CA certificate
from the one specified by the ssl-ca option. I doubt it's the
letsencrypt certificate the one being used, correct me if I'm wrong (y
can check with e.g. `openssl c_client`).
Could you please:
1. share the ssl config sni
Hi Pengpeng,
I think it boils down to arbitrary choice: we either need to discard the
head or the tail of the list, and the current implementation discards
the tail. I think the most common way to order nameservers is by
decreasing priority, so the current implementation is the least
surprising to
This is happening again with Focal and Groovy:
tox -e citest -- run --os-name=focal --platform=lxd --preserve-data
--data-dir=results --verbose --deb=cloud-
init_20.2-134-g747723a4-1\~bddeb_all.deb --test-
config=tests/cloud_tests/testcases/modules/lxd_bridge.yaml
Was fixed by: https://github.com/canonical/cloud-init/commit/4ce67201
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776958
Title:
error creating lxdbr0.
To manage notifications about this bug go t
It seems we require an extra step:
lxc network detach-profile lxdbr0 default
otherwise the deletion fails with:
Error: The network is currently in use.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
https://github.com/canonical/cloud-init/pull/542
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776958
Title:
error creating lxdbr0.
To manage notifications about this bug go to:
https://bugs.launc
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => New
** Changed in: cloud-init
Assignee: (unassigned) => Paride Legovini (paride)
** Changed in: cloud-init
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bu
Hello Duvan and thanks for this bug report. The failure is:
/var/lib/dpkg/info/mysql-server-8.0.postinst: line 47: kill: (18631) -
Permission denied
By looking at the postinst script that line is just:
kill "$server_pid"
and as that script runs as root I'm surprised by the error. However yo
** Changed in: df-libreoffice
Importance: Medium => Unknown
** Changed in: df-libreoffice
Status: Invalid => Unknown
** Changed in: df-libreoffice
Remote watch: Document Foundation Bugzilla #137599 => Document Foundation
Bugzilla #137248
--
You received this bug notification because
tdf #137599 was marked as a duplicate of tdf #137248. I updated the
upstream bug to watch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900454
Title:
Calc doesn't recalculate formulas on cell cont
Hi,
I agree: the "stale" resolv.conf may disrupt the nameserver
configuration, and do it in a way that depends on the number of
nameservers listed there.
Adding the /etc/resolv.conf nameservers to the *tail* of the nameserver
list (trimmed to 3 entries) may be the most sensible thing to do.
--
Hi Julien and thanks for filing this bug.
I think your suggestion could work in principle, however I doubt it will
be implemented in practice. It would mean modifying a package to support
an unsupported package and more in general an unsupported setup.
Splitting the package in Debian would requir
Similar to LP: #1882527 but apparently not caused by a big database in
this case. I'm leaving this to Incomplete as without further information
it will be difficult to act on it. As Sergio wrote this can't be
reproduced from a fresh install.
@Steph any idea on what could have cause the upgrade ope
Hello colin and thanks for filing this bug report. The error message
shows a syntax error in a dovecot configuration file:
doveconf: Fatal: Error in configuration file
/etc/dovecot/conf.d/10-master.conf line 71: Unexpected '}'
This doesn't seem related to the upgrade. If you modified the file whi
Hello and thanks for this bug report. In the attached DpkgTerminalLog I
see the following error:
Warning: Unable to start the server.
Erro do analisador AppArmor para /etc/apparmor.d/usr.sbin.mysqld in
/etc/apparmor.d/usr.sbin.mysqld na linha 9: N?o foi poss?vel abrir
'abstractions/mysql'
which
Hello and thanks for your bug report. The main error here seems to be:
[ERROR] [MY-010262] [Server] Can't start server: Bind on TCP/IP port:
Address already in use
which is likely to be caused by a instance of mysqld not running under
control of the service init system (systemd). Killing it (or r
Hello suraj and thanks for this bug report. The problem is that the
"server upgrade" operation took too long and exceeded the 5min timeout
currently in place:
2020-10-28T05:32:22.777181Z 4 [System] [MY-013381] [Server] Server upgrade from
'80021' to '80022' started.
2020-10-28T05:38:34.718235Z 4
Thanks John for the reproducer.
(Per standup discussion) what we can do is probably handle the case
where /dev/console exists but can't be written to more gracefully. I
think this is the only place where /dev/console is written to:
https://github.com/canonical/cloud-
init/blob/master/cloudinit/ut
** Bug watch added: Sourceware.org Bugzilla #26262
https://sourceware.org/bugzilla/show_bug.cgi?id=26262
** Also affects: binutils via
https://sourceware.org/bugzilla/show_bug.cgi?id=26262
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Hello Florian and thanks for this bug report. The vmware page you linked
says that:
This issue is resolved in VMware vSphere 6.7 Update 3,
available at VMware downloads.
which makes me think that:
- This is actually a vSphere bug
- The bug is fixed in the newer versions of vSphere
- The prop
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since there isn't enough information in your report to differentiate
between a local configuration problem and a bug in Ubuntu, I'm marking
this bug as Incomplete.
If indeed this is a local configuration problem,
Speaking specifically of the libvirt task: in comment #12 Christian dug
into this issue and concluded that this is not a libvirt bug, proposing
to set it to Invalid and focus on LP: #1754871, which is now Fix
Released.
I see no elements here pointing to a libvirt bug, but as I can't fully
rule it
Given that Utkarsh confirmed this is a bug and even found where it
originates from I think this can be considered Triaged.
I also subscribed the ubuntu-server team.
** Changed in: rabbitmq-server (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are
Hi and thanks for the follow-up. As I understand this is a limitation of
ClamAV's parser for YARA rules. If this is the case there's little we
can do on the Ubuntu side to add support for it, and I'd suggest you to
file a bug or feature request to ClamAV upstream.
This is what I deduced from some
Hi Axel,
As far as I know the raspi image should use systemd-timesyncd for time
synchronization, with no need to manually install chrony or ntpd. Could
you please paste the output of the following commands:
systemctl status systemd-timesyncd
timedatectl status
timedatectl timesync-status
f
Hi Axel and thanks for the follow up. Good to know that the issue is
gone I guess: nobody likes problems that come and go without
explanation, but let's try to ascribe this one to a variable we didn't
identify.
I'm marking this bug report as Invalid for now. Should you hit the
problem again please
** Changed in: sysstat (Ubuntu Bionic)
Importance: Medium => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921747
Title:
Backport missing %gnice CPU value for tickless CPU in sysstat.
To ma
Hello and thanks for you follow up! Happy to hear that you found the
root cause of the issue. As this was a local configuration problem
rather than a bug in Ubuntu I'm setting the status of this bug to
Invalid. Should you believe there is actually a bug here please comment
back with your findings a
Thank you for your report.
If I understand correctly you are trying to compile something from
source, and the compilation doesn't work anymore on Focal, while it did
on Bionic. This might be because the libpcap package got updated and
it's not compatible anymore with your codebase. However in this
Hi Matthias,
This is fixed already in pmdk 1.10-1ubuntu1 (currently in hirsute-
proposed). Christian filed an upstream bug for this here:
https://github.com/pmem/pmdk/issues/5197.
Marking this as Fix Released.
** Bug watch added: github.com/pmem/pmdk/issues #5197
https://github.com/pmem/pmdk/
Hi Mark and thanks for this bug report. I can see how the flag
introduced by the "sftp-force-permissions" patch could come handy,
however I doubt we are going to include in the Ubuntu package unless
there's a compelling reason for doing so. And if such a compelling
reason did exist, then I think it
Hello Michael and thanks for this bug report. I don't have a system I
can reproduce the issue on at the moment, but your analysis looks
correct to me. Integrating your open-iscsi-sanbootable.finalrd into the
open-iscsi.finalrd hook shipped with the open-iscsi Ubuntu package
should do the trick.
Th
Hello Malte, thanks for this bug report and for providing some minimal
steps to reproduce it. I could reproduce the issue you described and
verified that it doesn't happen when using vbernat's PPA, as you stated.
I checked the haproxy changelog for the 2.0 branch [1] and its full git
history [2] ho
Hello Hadmut and thanks for this bug report. From reading the
information here I think user hadmut1 should be created, while I don't
expect hadmut2 and hadmut3 to show up in the installed system.
Specifying the user in the 'identity' section shouldn't be necessary
when specifying users like you did
This has been fixed in 2.19-1ubuntu1.
** Changed in: pycparser (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/1870070
Title:
pycparser ftbfs in foca
We are using a rather old upstream snapshot of ipxe: commit a25a16d
dates back to April 2015. I guess this is because upstream didn't tag
any release between 2010 and January 2, 2020, when version v1.20.1 was
tagged.
The FTBFS does not happen with the latest upstream version, as the use
of bfd has
401 - 500 of 1596 matches
Mail list logo
