** Changed in: samba (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/1912750
Title:
samba-tool domain provision cr
@Kees Baker, thanks for providing your krb5.conf. Would it be possible
to also provide the contents of any file under /etc/krb5.conf.d/ and
/var/lib/sss/pubconf/krb5.include.d/. I'm wondering if there's anything
in those directories that is influencing the bug. Thanks.
--
You received this
Like Andreas, I cannot reproduce the coredump either.
# smbclient //focal-01.example.com/myshare -k
gensec_spnego_client_negTokenInit_step: Could not find a suitable mechtype in
NEG_TOKEN_INIT
session setup failed: NT_STATUS_INVALID_PARAMETER
Even after using the same options as the ones
Performing the verification on Groovy:
First, confirming that the current sssd manifests the bug:
# apt policy sssd
sssd:
Installed: 2.3.1-3ubuntu2
Candidate: 2.3.1-3ubuntu2
Version table:
*** 2.3.1-3ubuntu2 500
500 http://archive.ubuntu.com/ubuntu groovy-updates/main amd64
Performing the verification on Focal:
First, confirming that the current sssd manifests the bug:
# apt policy sssd
sssd:
Installed: 2.2.3-3ubuntu0.2
Candidate: 2.2.3-3ubuntu0.2
Version table:
*** 2.2.3-3ubuntu0.2 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64
Hi Paride,
Thanks for further investigating. I assumed that the crash was indeed
reproducible by hacking the package, but I think it's important to get a
reproducer that doesn't involve rebuilding anything if we're thinking
about an SRU (for Groovy, for example).
In any case, I think it's
Thanks for the patch, Lucas.
I reviewed it and it seems reasonable. I'd probably use a "Origin:
backport" header and mention the commit URL there as well. I haven't
run the dep8 tests myself but I trust the results you posted :-).
LGTM.
--
You received this bug notification because you are a
Thanks, Paride.
I had also found the same bug yesterday, but I decided not to mark the
bug as Triaged because I still cannot reproduce it.
As noted previously, I would like to be able to reproduce the issue
before moving forward. This will prove useful if we have to SRU the
patch.
I still
Thanks for the report. I've reassigned the bug to net-snmp, since this
is not a nagios-plugins issue.
I'm also having a bit of trouble reproducing this one. I think I
generated the certificates correctly by doing:
# net-snmp-cert genca -I -n hostname.example.com
# net-snmp-cert gencsr -I -t
Thanks for the report.
Just by installing the package I cannot trigger this problem; it
complains that it "cannot find inband device". I wonder what it would
take to have a reproducer for this.
In any case, this looks like a valid bug. Since there is a known and
easy workaround, I'm marking it
** Package changed: nagios-plugins (Ubuntu) => net-snmp (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912390
Title:
[Patch] TLS/DTLS: inconsistent allowed_uses behaviour when in debug
Thanks for the bug report.
This should have been opened against net-snmp, and not nagios-plugins,
right? I'm reassigning it to the proper package.
It seems to me that it's a valid bug, but it would be great to have a
more detailed reproducer. I tried editing /etc/ssl/openssl.cnf and
extend the
Thank you for the bug report.
I am assuming that this bug refers to Hirsute. The PR you linked is
still being reviewed upstream. Eventually it will be accepted and
released upstream. I am marking this bug as a Wishlist for now, since
it seems to me that the feature is not yet ready to be
** Description changed:
+ [ Impact ]
+
+ sssd users on Focal, Groovy and Hirsute can experience problems when
+ setting sssd's apparmor profile to "Enforce" mode. In this scenario,
+ apparmor will prevent sssd from being able to execute programs under the
+ /usr/libexec/sssd/* path, which will
** Also affects: sssd (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: sssd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: sssd (Ubuntu Hirsute)
Importance: Undecided
Assignee: Sergio Durigan Junior (sergiodj)
Status: New
Verification for Groovy.
root@groovy-desktop:~# apt policy sssd
sssd:
Installed: 2.3.1-3
Candidate: 2.3.1-3
Version table:
*** 2.3.1-3 500
500 http://ca.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100 /var/lib/dpkg/status
Booting the VM and verifying that the bug
Verification for Focal:
root@focal-desktop:~# apt policy sssd
sssd:
Installed: 2.2.3-3ubuntu0.1
Candidate: 2.2.3-3ubuntu0.1
Version table:
*** 2.2.3-3ubuntu0.1 500
500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages
100 /var/lib/dpkg/status
** Changed in: sssd (Ubuntu Focal)
Assignee: Sergio Durigan Junior (sergiodj) => Marco Trevisan (Treviño)
(3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905790
Title:
Make S
OK, packages uploaded for Groovy and Focal (waiting on the SRU team
now), and Hirsute.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900642
Title:
sssd won't start
To manage notifications about
t; 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/1900642
Title:
sssd won't start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/
** 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.
https://bugs.launchpad.net/bugs/1910611
Title:
sssd startup fails when appar
Sorry, scratch that, I got confused and assumed that you were mounting a
Samba share. I moved the bug back to cifs-utils.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882980
Title:
unix
AFAIU, the work on SMBv3 UNIX extensions on Samba is ongoing:
https://wiki.samba.org/index.php/SMB3-Linux
So, while cifs-utils tries to use "unix" when mounting the share, Samba
still doesn't support it, and therefore mount.cifs falls back to nounix.
This is not necessarily a bug; it's just
Confirmed that the bug still exists with cifs-utils 6.11-1ubuntu1.
** Changed in: cifs-utils (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/1090760
Title:
Closing after confirming that it's been fixed.
** Changed in: cifs-utils (Ubuntu)
Status: Triaged => 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/260396
Title:
cifs.mount:
Confirmed that the bug still exists with cifs-utils 6.11-1ubuntu1.
** Changed in: cifs-utils (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/1090764
Title:
Brian, thanks so much for accepting the SRU so quick! As it turns out,
I was able to come up with a better, more complete fix, and upstream has
accepted it a few days ago. For that reason, and after consulting with
Robie, I am dropping the verification-* tags from this bug, and will
prepare a
Aside from reinstalling the package, you can try to overwrite your
current apparmor profile with the one that is shipped by default in the
package. Something like the following:
# wget
Thank you for taking the time to file a bug report.
Based on what I can find in the attached logs, I cannot really
understand the sequence of commands that may have led to this error. I
tried reproducing it in a container here, making sure to enable i386
first, but everything (curl, nodejs and
*** This bug is a duplicate of bug 1906627 ***
https://bugs.launchpad.net/bugs/1906627
Thanks for your report. It indeed seems like a duplicate of bug
1906627, so I am marking it as such.
** This bug has been marked a duplicate of bug 1906627
GSS-SPNEGO implementation in cyrus-sasl2 is
Thank you for taking the time to file a bug report.
Could you please provide some reproduction steps here? I'm not a ceph
expert, and it seems like there needs to be some initial configuration
to make ceph work. I did spend some time trying to configure it here,
but it'd be easier if you could
Thank you for the bug report.
Unfortunately, we still don't have enough details to proceed with the
investigation of this problem, so I am not going to change anything
here. If you can provide more information (as per Christian's request),
feel free to mark this bug as New again.
Thanks.
--
Thanks for taking the time to report a bug.
I am unable to reproduce the issue here. I've tried it on a Focal lxd
container, a Focal VM, and a Focal system (native). I'm always able to
execute the following commands:
# sudo nmap -n 192.168.1.1/24
# sudo nmap -4 -vvv -ddd -sn -PR 8.8.8.8
They
Thank you for taking the time to file a bug report.
>From the information you provided, it is hard to determine what the root
cause of the problem is. I see some interesting things, though:
1) According to DpkgHistoryLog.txt, your unnatended-upgrades command has
been failing a lot lately. This
Package uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908149
Title:
dfwinreg: FTBFS on hirsute due to missing Build-Dep
To manage notifications about this bug go to:
Package uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908134
Title:
cura: FTBFS on hirsute
To manage notifications about this bug go to:
** Patch added: "dfwinreg.patch"
https://bugs.launchpad.net/debian/+source/dfwinreg/+bug/1908149/+attachment/5443581/+files/dfwinreg.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908149
rtance: Undecided
Assignee: Sergio Durigan Junior (sergiodj)
Status: Confirmed
** Affects: dfwinreg (Debian)
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #976653
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976653
** Also affects: df
** Patch added: "cura.diff"
https://bugs.launchpad.net/debian/+source/cura/+bug/1908134/+attachment/5443556/+files/cura.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908134
Title:
cura:
ltimaker/Cura/commit/00bc1bfcdc960d4bad62adc4b1615ca4cc6b3cee
** Affects: cura
Importance: Unknown
Status: Unknown
** Affects: cura (Ubuntu)
Importance: Undecided
Assignee: Sergio Durigan Junior (sergiodj)
Status: Confirmed
** Affects: cura (Debian)
Importance: Unk
Finally! Thanks for the detailed steps, Lee. I was finally able to
reproduce it locally.
For the record, these are the commands you can issue to reproduce.
Suppose that you have a samba share named "sambashare" serving a
directory at $HOME/testshare.
$ gio mount smb://127.0.0.1/sambashare
$
@Timo thanks for looking into that. FWIW, I've just opened a MR on
salsa in order to propose this change to the Debian sssd as well:
https://salsa.debian.org/sssd-team/sssd/-/merge_requests/10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
+ [ Impact ]
+
+ Starting from Groovy, sssd became a dependency of ubuntu-desktop. This
+ means that Ubuntu users who install the Desktop version will
+ automatically get sssd installed in their systems.
+
+ By default, sssd does not try to make any assumptions about
@Lee Tae Hoon, thank you for the feedback. I downloaded the zip file
you provided, but I still can't see anything useful in the logs. I
wonder what's really happening. I will have to bug you one more time
and ask you to provide a network trace of the moment of the failure,
please. You can read
I finally had some time to do some investigation on this bug. I
appreciate the analysis done by others, and the patch provided by
Dimitri.
I verified that using ConditionPathExists on sssd.service does prevent
sssd from starting (as expected), which means that the error messages in
the log are
ned) => Sergio Durigan Junior (sergiodj)
** Changed in: sssd (Ubuntu Hirsute)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Changed in: sssd (Ubuntu Groovy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
I forgot to mention, but I:
1) Replaced my smb.conf with Lee Tae Hoon's smb.conf, and tried to
reproduce the error. Everything still works for me.
2) Tried moving files (via terminal and using Nautilus) to the share. I
can access them fine.
3) Tried attaching another disk to my Focal VM,
Thanks for the replies, Rapper_skull an Lee Tae Hoon.
Lee, I have a few questions for you.
1) What is the name of the file you tried to open? Based on the
screenshot you posted earlier, I thought the file was named
IMG_1809.JPG. However, in your logs I don't see any attempt to open a
Hi, thanks for reporting the bug.
Before anything else, I would like to ask if there is any particular
reason why you marked the bug as Invalid. Have you perhaps found the
problem or a workaround? If that is the case, then could you update
this bug and post what you've found? Maybe other users
** Changed in: telegraf (Ubuntu Focal)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897631
Title:
[SRU] Add telegraf to focal's universe repository
To manage
I apologize for the delay, but I'm now starting to investigate this
problem.
As Christian said above, the very first step I have to take is to
reproduce the problem, but for now I am unable to do so. Here is what I
did:
1) Installed a Focal VM from scratch. Made sure that everything is up-
For what it's worth, we have gotten a report about adcli as well.
Lukasz will pull adcli from -upgrades/-security as well. We're
investigating the failures.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for providing more info. I'm marking this bug as New again,
since the ball is now on our court. I'll see if I time to look into
this soon.
** Changed in: realmd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks for the comments.
I was able to confirm this bug by doing:
# cat >> /etc/profile < Triaged
** Changed in: byobu (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to file a bug report.
I have tried to reproduce this problem here, but did not succeed.
Here's what I did:
1) Launched a Bionic VM using lxd
2) apt update && apt upgrade
3) apt-get -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6
-q -y -o
Thank you for taking the time to file a bug report.
>From your logs, I can see the following error message:
[ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11
The code "11" means that the resource is temporarily unavailable. From
my recollection, this error can mean that there is
** Tags added: 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/1900642
Title:
sssd won't start
To manage notifications about this bug go to:
FWIW, the fix has just been pushed upstream:
https://sourceware.org/git/?p=binutils-
gdb.git;a=commit;h=2bf3b79d05bf85e41cbdcb020bd1cc424f59dd9a
If no one else beats me to it, I can try to backport it this weekend.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
rsyslog is missing dep8 tests, which would be really good to have given
the importance of this package and the amount of delta we're currently
carrying.
** Affects: rsyslog (Ubuntu)
Importance: Wishlist
Status: New
** Tags: needs-dep8
--
You received this
** Changed in: samba (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905048
Title:
samba ftbfs in hirsute, needs merge
To manage notifications about
** Changed in: util-linux (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905510
Title:
utils-linux 2.36.1 breaks user mounts (cifs)
To manage
** Changed in: sssd (Ubuntu Focal)
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/1905790
Title:
Recompile SSSD in 20.04 using Open
** Changed in: util-linux (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/1905510
Title:
utils-linux 2.36.1 breaks user mou
Thanks for the comment, Marcin. Yes, you're right, the correct file to
edit was ssh@.service indeed. That was a thinko on my part.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905285
Title:
Thank you for taking the time to file a bug report.
Would you be able to come up with a way for us to reproduce this bug? I
understand that it must be happening in a production environment where
thousands of connections are being made, but maybe we can come up with a
way to reproduce it locally
Thanks for the report.
I was able to reproduce this bug. Basically:
$ systemctl start ssh.socket
$ ssh-keyscan localhost
Interesting enough, I wasn't able to solve the problem by setting
RuntimeDirectoryPreserve=yes. I edited sshd.service and added the
directive there, but I still see the
** Changed in: openssh (Ubuntu)
Status: New => Triaged
** Changed in: openssh (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905285
Title:
Thanks for the bug report.
Based on your logs, this is the error that's happening:
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
ERROR: lock directory /run/samba does not exist
ERROR: pid directory /run/samba does not exist
Server role: ROLE_STANDALONE
[1mdpkg:[0m
Setting the status as Incomplete; still waiting on the reply to Paride's
question.
** Changed in: dovecot (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Set priority to High because it will block samba from migrating, which
will in turn block Python 3.9 from migrating.
** Changed in: util-linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
MP ready, PPA building, dep8 tests (mostly) passing.
We will have to fix bug 1905510 in order to make samba migrate.
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/samba/+git/samba/+merge/394442
--
You received this bug notification because you are a member
Public bug reported:
I'm working on merging samba from Debian (2:4.13.2+dfsg-1), and while
running the autopkgtests for the package I noticed that two tests are
failing. These tests attempt to invoke mount.cifs in order to mount a
user mount point. I investigated and found this on dmesg:
[
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
If someone can prepare a backport, please follow the steps at:
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
All the steps documented there need to be followed. In particular:
1) Explain the bug well
Meanwhile, Guillaume Penin, could you provide the necessary steps to
reproduce this issue? I am not familiar with Tomcat.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904620
Title:
*** This bug is a duplicate of bug 1901708 ***
https://bugs.launchpad.net/bugs/1901708
Thanks for taking the time to report this bug and make Ubuntu better.
By looking at the logs, it seems to me like this bug is a duplicate of
LP #1901708. The following excerpt is what made me reach this
Thank you for taking the time to file a bug report.
Based on the logs attached to the bug, it seems to me that this is a
local configuration issue. Do you have any other instance of Postgresql
running? Based on the log below:
Preparativi per estrarre .../24-postgresql-common_216_all.deb...
@tdaitx asked me to take a look at this problem, and here is what I
found.
1) As he said above, the problem is that Debian/Ubuntu generate
.gnu_debugaltlink sections containing full pathnames to the DWZ alt
debug files. IMO, we should be using dwz's "--relative" option when
invoking it via
For what it's worth, I created a Focal lxd container, followed the
instructions listed in the description, but could not reproduce the
issue. I was able to successfully build wireshark without problems
here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@ElTouco72, samba-libs does not depend on ubuntu-desktop. You can
verify the output of "apt show samba-libs", or do a "apt install --dry-
run samba-libs".
You will see that samba-libs is part of the task "ubuntu-desktop", but
that's a different thing.
--
You received this bug notification
Thank you for taking the time to file a bug report.
Can you provide more details about the issue? By "copy paste mode" I
assume you're referring to the copy mode you enter when you type CTRL+b
[, is this correct? I've made an experiment here and left tmux in this
mode for several minutes, and
Thank you for taking the time to file a bug report.
Based on the logs, it seems like you were trying to upgrade the mysql
version from 8.0.21-1 to 8.0.22-0ubuntu0.20.10.2. It also seems like
this bug is related to LP #1901708, but what I found interesting is that
the time it for the "Server
@xaan, this seems like a different problem (by looking at the logs).
@suraj, would you happen to know if the system load was high during the
upgrade process for some reason?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@A, without the logs there is not way to know whether you're facing the
same issue as Steph.
For the record, I tried generating random data (two tables, 10k lines
each) and inserting into MySQL, and then performing the upgrade using a
container with very limited resources, but even in this
Thank you for taking the time to file a bug report.
By inspecting the logs I see that you tried to install MySQL and MariaDB
together. As you might have noticed, they are incompatible with each
other; therefore, when you try to install one of them, the other is
automatically removed. However,
Hello Luke,
Based on the discussion posted, I could not infer if you have progressed
in diagnosing the issue, or if you're still stuck. Do you have more
news about the bug that you can share with us? Thanks.
** Changed in: dovecot (Ubuntu)
Status: New => Incomplete
--
You received
I'm also able to reproduce this in a hirsute lxd container today
(2020-11-02).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902540
Title:
hirsute fails on add-apt-repository
To manage
First, verifying that the current package fails:
root@bug1784757-rabbitmq-server:~# apt policy rabbitmq-server
rabbitmq-server:
Installed: 3.6.10-1ubuntu0.3
Candidate: 3.6.10-1ubuntu0.3
Version table:
*** 3.6.10-1ubuntu0.3 500
500 http://archive.ubuntu.com/ubuntu
Thank you for taking the time to file a bug report.
I don't have a remote UPS readily available to test, so I did my best to
set up nut locally (using its dummy.dev interface) inside a Focal
container, and then set MODE=netclient in the nut.conf file. I could
not reproduce the bug you reported.
It just occurred to me that I would like to confirm whether my suspicion
is correct. Can you confirm that you have a somewhat large MySQL
database there, please? I am marking this bug as Incomplete for now,
but that's just because I'm waiting on your answer. When you reply,
feel free to move
Thanks for taking the time to report this bug and make Ubuntu better.
Even though I am not able to reproduce the bug in a simple environment,
this seems like a real problem indeed.
Basically, what you (or your system, rather) tried to do was to upgrade
to the latest version of mysql-server (from
*** This bug is a duplicate of bug 1901708 ***
https://bugs.launchpad.net/bugs/1901708
** This bug has been marked a duplicate of bug 1901708
package mysql-server-8.0 8.0.22-0ubuntu0.20.04.2 failed to install/upgrade:
installed mysql-server-8.0 package post-installation script subprocess
Thanks for the bug report, Alexander!
I have a local setup here with an Active Directory running on Windows
Server 2019, and I fired up a Focal VM and tried to reproduce the steps
you mentioned above. In a nutshell, here's what I did:
- realm join mydomain --membership-software=adcli
-
Thank you for taking the time to file a bug report.
I tried reproducing the upgrade path here inside a lxd container. Of
course, since some of the versions you mentioned above are EOL'ed, I
started with bionic and upgraded to focal. Everything worked. I made
sure to have postfix, postfix-doc
Thanks for your report and for making Ubuntu better.
I can confirm this bug. The .in file was added as of:
apache2 (2.4.18-2ubuntu3.16) xenial; urgency=medium
* On Linux, use pthread mutexes. On kfreebsd/hurd, continue using
fctnl because they lack robust pthread mutexes.
(LP:
Thank you for taking the time to file a bug report.
Based on the bug report above, the following snippet caught my
attention:
Error: command ['/usr/sbin/apachectl', '-D DUMP_MODULES'] failed with
exit code 1: apache2: Syntax error on line 142 of
/etc/apache2/apache2.conf: Syntax error on line 3
Thank you for taking the time to file a bug report.
Based on your dpkg history log, it seems like you were not able to "apt
install" other packages before trying to install lua5.2. Can you
provide more information about what happened when you tried to install
lua5.3, for example? It seems like
Thank you for taking the time to file a bug report.
Checking the logs I found that you are installing mysql-server along
with mariadb-server. Even though apt is careful to remove one of the
packages in this case (since both cannot coexist), it is still possible
that some misconfiguration has
Thank you for taking the time to file a bug report.
Checking the logs I found quite a number of messages like these:
2020-09-29T09:51:21.976605Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock
./ibdata1 error: 11
2020-09-29T09:51:22.977176Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock
./ibdata1
While preparing the package for upload to Focal, I chose the following
versioning schema:
1.15.2+ds1-0ubuntu1~20.04.1
The reason is because telegraf on Groovy's universe is currently at
1.15.2+ds1-0ubuntu1. Adding "~20.04.1" to the version guarantees that
when updating the package from Focal to
Public bug reported:
[Impact]
The telegraf[1] package is an agent for collecting, processing,
aggregating, and writing metrics.
Telegraf is part of a suite of programs referred to as LMA (Logging,
Monitoring and Alert). It is responsible for the Logging; prometheus,
prometheus-alertmanager and
801 - 900 of 1010 matches
Mail list logo
