Marking as Won't Fix on Xenial due to ESM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453463
Title:
undefined symbol: FAMNoExists
To manage notifications about this bug go to:
** Changed in: lighttpd (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/1453463
Title:
undefined symbol: FAMNoExists
To manage notifications about
FWIW, I haven't checked whether a simple rebuild of the package would be
enough to fix this. I will try to set up a PPA later and confirm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931306
Heh, this ended up in my triage today :-).
Anyway, I'm confirming that the bug happens on Focal, but unfortunately
this will be a low priority one for us. I'm also confirming that Impish
doesn't suffer from this problem; the debuginfo files from postfix-
dbgsym there do have the correct DWARF
Thank you for the bug report. I confirm the warning during the
installation of the package on Focal (Impish is not affected). Given
that this is a relatively harmless warning, and that using "is not" in
this particular case still renders the correct result, I'm setting this
bug's priority as
** Changed in: genshi (Ubuntu)
Status: New => Triaged
** Changed in: genshi (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931179
Title:
Still waiting on the SRU team to address this. I will ping them today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912389
Title:
[Patch] SIGSEGV: crash when certificate contains extension
** Also affects: apache2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: apache2 (Ubuntu Focal)
Status: New => Triaged
** Changed in: apache2 (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: apache2 (Ubuntu)
Status: Triaged => Fix Released
Hi lincvz,
We are still trying to determine the best approach here. This is on my
TODO list, and hopefully I can put something together by the end of this
week.
Thank you for your patience.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks for your input, Alex. Absolutely, if you feel like this package
needs a full review then let's do it; I don't want to jump any steps in
the process here :-).
Thank you, and let me know if you need anything from my side in order to
make this review quicker/easier for the Security team.
--
https://launchpad.net/ubuntu/+source/sssd
sssd has been uploaded and migrated to impish-release. This upload
brings back i386 support, including libnss-sss. I'm marking this bug as
Fix Released.
** Changed in: sssd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug
Thanks for the review, Lucas. Indeed, the formatting problem was a
mistake on my end, thanks for catching it.
I've now uploaded both packages to -proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: wine (Ubuntu)
Status: Confirmed => In Progress
** Changed in: wine-development (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, I've posted both patches now.
You will notice that they are basically the same; this is because both
projects share the same orig tarball (or at least a very big part of
it).
These patches introduce a rename of the "ldap_connect" function (which
is now present on OpenLDAP 2.5 as well) to
This is the patch for wine.
** Patch added: "wine-openldap-ftbfs-fix.patch"
https://bugs.launchpad.net/ubuntu/+source/wine-development/+bug/1929859/+attachment/5500758/+files/wine-openldap-ftbfs-fix.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is the wine-development patch.
** Patch added: "wine-development-openldap-ftbfs-fix.patch"
https://bugs.launchpad.net/ubuntu/+source/wine-development/+bug/1929859/+attachment/5500759/+files/wine-development-openldap-ftbfs-fix.patch
--
You received this bug notification because you are
)
Importance: High
Assignee: Sergio Durigan Junior (sergiodj)
Status: Confirmed
** Affects: wine-development (Ubuntu)
Importance: High
Assignee: Sergio Durigan Junior (sergiodj)
Status: Confirmed
** Also affects: wine-development (Ubuntu)
Importance: Undecided
These packages are not covered by git-ubuntu, so I will be posting
patches here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929859
Title:
wine and wine-development FTBFS with OpenLDAP 2.5
To
Thank you for your interest in this issue.
Let me start by addressing the question of why we can't (or rather
"don't want") to provide a samba-vfs-glusterfs package without the
direct dependency to glusterfs. We strive to provide good quality
packages for Ubuntu users, and that means that if a
** Description changed:
+ [ Impact ]
+
+ Users can experience a segmentation fault on snmpd (part of net-snmp)
+ when using a certificate that contains an extension longer than 512
+ bytes and debug output (-D) is enabled. Although this only happens when
+ debugging, it seems to be pretty
OK, finally I was able to trigger the bug locally using a self-signed
cert. I am going to start writing the SRU template for it.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912389
Title:
Encrypt suggestion, though).
I will see if I can reproduce it locally and then start the SRU process.
If you already have a detailed set of steps to reproduce the bug, please
let me know. Thanks.
** Also affects: net-snmp (Ubuntu Impish)
Importance: Medium
Assignee: Sergio Durigan Junior
** Changed in: net-snmp (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Changed in: net-snmp (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
and changing the bug status to Confirmed, as
requested. Thanks!
** Changed in: telegraf (Ubuntu)
Assignee: Sergio Durigan Junior (sergiodj) => Didier Roche (didrocks)
** Changed in: telegraf (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification becau
OK, here it is:
https://launchpad.net/~sergiodj/+archive/ubuntu/openldap-bug1926265
lincvz, could you please give this a try and check if this package fixes
the issue? Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the further investigation, Stephane and Ryan. Much
appreciated!
It would be interesting to know if lincvz could test an openldap built
with Ryan's patch, to check if he can still reproduce the bug with it.
I am going to prepare a PPA with Ryan's patch and let you know ASAP.
Ryan,
Thank you for your reply.
Unfortunately I cannot help you with salsa; I don't manage the system.
I know you can ask for help on the #salsa channel (OFTC IRC network);
maybe someone there will be able to help you with the user creation.
Once you are able to login you should also be able to create
Thank you for taking the time to file a bug report.
Based on the logs you posted, it seems like you have both MySQL and
MariaDB installed in the system. This scenario is not really supported
and can lead to errors, especially during the upgrade/removal processes,
which is your case. It seems
Thanks for taking the time to report this bug and make Ubuntu better.
This issue seems to affect only people who are compiling their own
versions of exim4. For this reason, the security doesn't plan to act on
it. I've subscribed the Ubuntu Server team to this bug, and will set
the priority to
I tried investigating this bug a bit more with Athos' help.
First, I cannot easily reproduce it because smartd doesn't even start
when running on virtualized environments, and I don't feel like using my
own host machine to test the problem.
Then, I noticed that there is a bug filed upstream
I'm going to update the sssd package to reflect what we've discussed.
** Changed in: sssd (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Hi Steve,
I had a chance to talk to Timo and Andreas and we all agree that it
should be OK to drop the B-D on gdbm on i386. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904990
Title:
** Changed in: lto-disabled-list (Ubuntu)
Assignee: Matthias Klose (doko) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927789
Title:
Remove telegraf f
Public bug reported:
I have tested the latest telegraf that is available in Impish
(telegraf_1.18.1+ds1-0ubuntu1) and verified that it compiles & tests
fine with LTO on all supported architectures, as can be seen here:
https://launchpad.net/~sergiodj/+archive/ubuntu/telegraf-lto/+packages
The
Thank you, Didier. I'm in touch with upstream and asked them if it's
possible to cut a new release ASAP with the CVE fixes. I'll let you
know when the update is done :-).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FWIW, I've just completed the d/copyright update/review. I'm now
waiting on the new upstream release which will fix the aforementioned
CVEs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926321
On Thursday, May 06 2021, Didier Roche wrote:
> [Summary]
> The package is in a very good shape, higher than most of the ones we
> review. I have few questions but no big blocker. I feel it would be
> still good for the security team (even if they already support it to
> some point) to have a
Thanks for following up.
It is hard to say what might be happening and whether switching to MDB
will help or not. I'm still puzzled that you're seeing this hang on a
relatively new version of OpenLDAP. The fact that it didn't happen on
Trusty may be helpful when diagnosing the issue, but I
FWIW, as a workaround what you can do is create a group which contains
disabled users on the AD (e.g., "DisabledUsers"), and add the following
directive to /etc/ssh/sshd_config:
DenyGroups DisabledUsers
Then, whenever you disable a user on the AD you also include it into the
"DisabledUsers"
Thank you for the further details.
Indeed, I was able to reproduce and confirm this locally. It is a
limitation of winbind. In fact, I have found an upstream bug about this
problem:
https://bugzilla.samba.org/show_bug.cgi?id=14622
The "good news" is that upstream is aware of such limitation.
Hello! The kernel team has applied the fix to their pre-release branch.
They have a 5-week release cycle, so we should be seeing a new Bionic
Linux kernel with the fix in the following 3-4 weeks. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for the bug report and apologies for the delay in getting back to
you.
I configured a Bionic VM acting as an AD member, joined the AD, and then
disabled one of the users in the AD DC. I noticed that issuing a "login
inva...@ad1.example.com" correctly displays the following message:
#
Thank you for taking the time to file a bug report.
This one looks like a rabbit hole :-(. I've also found many (very) old
reports of similar problems, but they all appear to have been fixed a
while ago (before Bionic was released). I even found a possible patch
(from 2005) to fix the issue,
nee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926324
Title:
Autogenerated freshclam.conf should not mention now-deprecated option
Safe
** Also affects: telegraf (Ubuntu Impish)
Importance: Medium
Assignee: Sergio Durigan Junior (sergiodj)
Status: Triaged
** Also affects: telegraf (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: telegraf (Ubuntu Hirsute)
Status: New => Tria
** Description changed:
[ Availability ]
The telegraf package has been part of Ubuntu's universe repository
since Groovy. It successfully builds and the tests pass on all
supported architectures: amd64, arm64, armhf, ppc64el, riscv64 and
s390x.
[ Rationale ]
Telegraf is
Public bug reported:
[ Availability ]
The telegraf package has been part of Ubuntu's universe repository
since Groovy. It successfully builds and the tests pass on all
supported architectures: amd64, arm64, armhf, ppc64el, riscv64 and
s390x.
[ Rationale ]
Telegraf is part of a suite of
Dan, let me know if you need help driving the Linux kernel SRU forward.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916485
Title:
test -x fails inside shell scripts in containers
To
Importance: Unknown
Status: Unknown
** Affects: telegraf (Ubuntu)
Importance: Medium
Assignee: Sergio Durigan Junior (sergiodj)
Status: Triaged
** Changed in: telegraf (Ubuntu)
Importance: Undecided => Medium
** Bug watch added: github.com/influxdata/telegraf/iss
Ah, thanks for the further investigation, Simon.
Indeed, I was able to reproduce the problem when using apparmor and
verifying that /usr/bin/freshclam is confined.
I'm not sure if there's much we can do here; the best course of action
for those experiencing this bug is to just restart the
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-signed-hwe-5.8 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Gabriele,
Thank you for the bug report and the help with the investigation!
I apologize that this bug was marked as Expired; this is done by an
automatic process after a period of inactivity. Somehow this fell
through the cracks of our triage process, but now we're on it again :-).
Thank
Thank you for taking the time to file a bug report.
So, I've spent some time trying to reproduce it here, but was
unsuccessful. Here's what I tried:
- Create a Bionic LXD container.
- Grab the .deb files for the last-but-one clamav version that was
available in Bionic. They can be found here
Thank you for taking the time to file a bug report.
There is no error log from MySQL in the bug, so the investigation I
performed has been limited by this. But upon looking at
DpkgTerminalLog.txt, I found the following error message:
Configurando mysql-server-8.0 (8.0.23-0ubuntu0.20.04.1) ...
Hi Iain,
AFAIK there is no pending upload to fix this bug on Hirsute -- is there?
The only work I've done was to backport the patches mentioned in the
Description and upload the package to a PPA. Unless Marco has made an
upload, of course.
--
You received this bug notification because you are
Thank you for your bug report, and thanks Frédéric for the initial
triage.
I agree with Frédéric's findings here: the skiboot file is properly
installed in a Focal system by qemu-system-data. Also, as he mentioned,
qemu-skiboot is a virtual package; it doesn't really provide anything.
I am
** 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/bugs/1697339
Title:
rpc.gssd performs reverse DNS by default (regardless of -D flag)
To manage notifications about this bug go
Thanks for the investigation, Dan. I tested the Linux package from your
PPA on a s390x machine and can confirm that it does solve the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916485
Before I change the status of this bug, I would like to report my
findings here.
I am testing things on a Bionic s390x machine with everything up-to-
date:
# apt policy systemd
systemd:
Installed: 237-3ubuntu10.46
...
# apt policy containerd
containerd:
Installed: 1.4.4-0ubuntu1~18.04.2
...
Thanks for the reply, Marco. Does this mean that we can close this bug
for SSSD, then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917362
Title:
PAM: smartcard owner isn't associated to user by
Thanks for the feedback, Philipp.
I was able to further investigate this bug and found that the following
upstream commit fixes it:
https://github.com/tmux/tmux/commit/54efe337993b5571728a09b247c7f39d493659a8
Given that this bug is affecting unattended-upgrade users, I'm raising
its Importance
Awesome, thanks Lucas. LGTM now, +1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923108
Title:
FTBFS against docker 20.10
To manage notifications about this bug go to:
Thanks for taking care of this, Lucas.
I reviewed the patch and have two minor comments:
- Since you're adding a delta to the package, update-maintainer needs to
be run.
- Now that you have an Ubuntu bug number, I think you could add the
"Bug-Ubuntu" DEP-3 header to the patches.
Everything
FWIW, I've tested both patches and can confirm that they fix the FTBFSes
that are happening (I've had a problem trying to build libpod in a
container, but then I tested on sbuild and it worked. It may have been
something in the container itself).
If someone would like to try these patches: you
Thanks. Perhaps I should have been clearer and said that I did test and
made sure that the rebuild still worked on amd64 when Robie asked me
about it, and only after doing that I updated the SRU template. When it
was time to perform the verification, I found it unnecessary to check on
amd64
Verification for Bionic (using a ppc64el machine):
First, verifying that the problem manifests:
# apt policy gosu
gosu:
Installed: 1.10-1
Candidate: 1.10-1
Version table:
*** 1.10-1 500
500 http://us.ports.ubuntu.com/ubuntu-ports bionic/universe ppc64el
Packages
100
Verification for Focal (using a ppc64el machine):
First, verifying that the problem manifests:
# apt policy gosu
gosu:
Installed: 1.10-1
Candidate: 1.10-1
Version table:
*** 1.10-1 500
500 http://us.ports.ubuntu.com/ubuntu-ports focal/universe ppc64el
Packages
100
*** This bug is a duplicate of bug 1876900 ***
https://bugs.launchpad.net/bugs/1876900
Thank you for taking the time to report a bug.
Unfortunately, the amount of information in the logs is not enough to
diagnose the problem. The only strange thing is this part:
mysqld will log errors to
*** This bug is a duplicate of bug 1899248 ***
https://bugs.launchpad.net/bugs/1899248
This one looks like a duplicate of #1899248, so I marked it as such.
** This bug has been marked a duplicate of bug 1899248
package mysql-server-8.0 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade:
** Changed in: mysql-8.0 (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/1921356
Title:
package mysql-server-8.0 8.0.22-0ubuntu0.20.04.3 failed to
Thanks for the review.
Lucas is off today, but I talked to him briefly about this SRU and here
is the summary of the discussion:
1) According to Lucas, this should not be a problem because we are
backporting a version from Hirsute, which already contains the postinst
excerpt you're referring to
On Wednesday, March 24 2021, Robie Basak wrote:
>> This particular update is not able to cause any regressions, because
> the software did not work before it.
>
> What about on amd64? Am I right in understanding that this bug only
> affects ppc64el? But we have no choice but to rebuild for all
>
Thanks for the review, Lucas. I've uploaded both packages now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822632
Title:
gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at
** Patch added: "gosu-bionic.patch"
https://bugs.launchpad.net/ubuntu/+source/gosu/+bug/1822632/+attachment/5480547/+files/gosu-bionic.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822632
** Patch added: "gosu-focal.patch"
https://bugs.launchpad.net/ubuntu/+source/gosu/+bug/1822632/+attachment/5480548/+files/gosu-focal.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822632
** Changed in: gosu (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: gosu (Ubuntu Focal)
Status: New => Confirmed
** Changed in: gosu (Ubuntu Bionic)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Changed in: gosu (Ubuntu Focal)
** Description changed:
+ [Impact]
+
+ After installing "gosu" on Bionic/Focal on ppc64el, attempts to run the
+ resulting "gosu" binary result in the following error message:
+
+ gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc
+ at 0x0b41bcc7af58 for symbol `' out
On Wednesday, March 24 2021, Ken Marsh wrote:
> Sergio,
> Thank you for reviewing this report.
>
> This system indeed has a custom /usr/sbin/policy-rc.d, so it appears to be
> our own issue.
> Sorry I didn't catch that.
>
> Closing this issue.
That's totally fine! Thanks :-).
--
Sergio
GPG
Thank you for taking the time to report this bug.
I could not reproduce this on a fresh Bionic LXD container, but
something caught my attention in your bug report: the mention of policy-
rc.d.
This is a script that is not provided by any package in the archive (at
least that's what apt-file
Thank you for taking the time to file a bug report.
Based on the logs you attached to the bug, I can see a few things that
caught my attention and are making me wonder whether this is a local
configuration issue.
First, from DpkgHistoryLog.txt, I see a bunch of dpkg errors like:
Start-Date:
Thanks, Lucas.
I was involved in the investigation of the libpod breakage and feel
confident that this is the right way to go.
I did try to build both libpod and buildah with equivalent patches
locally, and everything succeeds. I'm +1 on both patches.
--
You received this bug notification
Thanks, Lucas.
I reviewed the patches and they look fine. A very small nit: you're
using your @debian.org email in the Groovy changelog.
Other than that, all 3 patches LGTM. I did build all 3 packages in a
local sbuild, and the builds succeeded.
A few comments about the SRU template:
- In
OK, thanks for replying back. I think it is clear that I don't know
much about asterisk; my comment was based on a general feeling that
standard error messages should not be silenced. But I will step back
and let you guys decide what is best in this scenario :-). Thanks.
--
You received this
ls (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: nfs-utils (Ubuntu Focal)
Status: New => Confirmed
** Changed in: nfs-utils (Ubuntu Groovy)
Status: New => Confirmed
** Changed in: nfs-utils (Ubuntu Bionic)
Assignee: (unassigned) => Sergio Durigan Ju
@timecop, yes, that would mean that, if you want to see output when
executing asterisk "by hand", then you would have to reenable the
console logging in the configuration file.
OK, that was a good point, and I'm not an asterisk expert so I have no
idea whether "attaching to remote console" is a
Thanks for the patch, Utkarsh.
I'm not sure I agree with it. I think a better approach would be to
comment out the line I mentioned by default, since it doesn't seem to be
useful, given that the logs are already recorded in the log file under
/var/log/asterisk. This way, we won't need to mess
** Changed in: nfs-utils (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918141
Title:
nfs-server.service needs n
Thanks Niklas, I was able to reproduce the bug here. I'm working on
fixing the service file and will post MPs soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918141
Title:
nfs-server.service
Just as a reminder, I create a PPA with the proposed fix here:
https://launchpad.net/~sergiodj/+archive/ubuntu/sssd-
bug1917362/+packages
Let me know when you can test it, and how the testing goes. Thanks!
** Changed in: sssd (Ubuntu)
Status: Triaged => In Progress
--
You received
Just to clarify something here: if Debian fixes the problem, the change
will show up *in a next release of Ubuntu*. We will still have to SRU
the fix to Focal/Groovy/Hirsute as applicable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you for taking the time to report a bug, and sorry for not getting
back to you sooner. This must have fallen through the cracks and we
didn't process it during our daily triages.
I can confirm here that asterisk will output its logs to two places:
- The console (which is what ends up in
I'm setting the status to Triaged. You don't need to set it back to
New. Thanks!
** Changed in: libfcgi (Ubuntu)
Status: Incomplete => Triaged
** Also affects: libfcgi (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: libfcgi (Ubuntu Groovy)
Importance:
Thank you for taking the time to file a bug report.
It is not clear to me which Ubuntu release you are using. I know that
libfcgi-dev on Hirsute does have the .pc file, so I am assuming you are
probably using Focal or Groovy.
I think this is a sensible request, but unfortunately the libfcgi
Sorry, the bug report needs to be written in English so that we can
understand and act on it. I am closing this bug as Invalid.
** Changed in: apache2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you for taking the time to file a bug report.
You need to give us more information and details about the problem you
are facing so that we can investigate it and determine whether we can
fix it or not. Please, describe what the problem is, what you are
trying to do, and upload any log
I'm subscribing Christian to this bug, who is our QEMU expert.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915063
Title:
Windows 10 wil not install using qemu-system-x86_64
To manage
Unfortunately I don't know. I would recommend commenting on the bug in
order to let upstream know that more people are affected by this
problem. You can try posting your reproduction instructions there, and
provide more information if upstream needs it.
I am marking this bug as Triaged,
Thank you for your reply, Riccardo.
I found the following upstream bug report that looks similar to yours:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/204
Can you confirm that this is the same issue?
Your setup seems a bit complex to configure locally, and given that
Thank you for taking the time to file a bug report.
>From your logs, I see that the apache2 configuration files could not be
found during the upgrade process, and were probably deleted earlier.
For example, this line:
exit code 1: apache2: Could not open configuration file
Thanks for the report and the great description.
The rationale here makes sense to me, and I agree with updating the
packages in order to solve the described issue. However, since we will
have to SRU this into Focal and Bionic (and I've just noticed that
Hirsute's nfs-server.service file is
701 - 800 of 1060 matches
Mail list logo
