[Bug 1930430] Re: Apache2 Certificate Chain Verification within Proxy not Working after dist-upgrade to focal
** 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930430 Title: Apache2 Certificate Chain Verification within Proxy not Working after dist-upgrade to focal To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1930430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
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 Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926321] Re: [MIR] telegraf
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926321 Title: [MIR] telegraf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegraf/+bug/1926321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904990] Re: Missing i386 version of libnss-sss
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904990 Title: Missing i386 version of libnss-sss To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1904990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929859] Re: wine and wine-development FTBFS with OpenLDAP 2.5
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. https://bugs.launchpad.net/bugs/1929859 Title: wine and wine-development FTBFS with OpenLDAP 2.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1929859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929859] Re: wine and wine-development FTBFS with OpenLDAP 2.5
** 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. https://bugs.launchpad.net/bugs/1929859 Title: wine and wine-development FTBFS with OpenLDAP 2.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1929859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929859] Re: wine and wine-development FTBFS with OpenLDAP 2.5
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 something else in order to prevent the FTBFS. You can find a PPA with both packages built (along with OpenLDAP 2.5) here: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4559/+packages The patches are "backported" from a solution provided by one of the Wine developers. This solution is not upstream and I don't know if it will be adopted or not, because the development version of wine fixed this problem using another approach (which is much harder to backport). Having said that, I talked to the Debian Wine maintainer and he told me he plans to update both wine and wine-development on Debian until the end of the year. Once he does that, we won't need these patches anymore. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1929859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929859] Re: wine and wine-development FTBFS with OpenLDAP 2.5
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929859 Title: wine and wine-development FTBFS with OpenLDAP 2.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1929859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929859] Re: wine and wine-development FTBFS with OpenLDAP 2.5
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 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1929859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929859] [NEW] wine and wine-development FTBFS with OpenLDAP 2.5
Public bug reported: Both wine and wine-development FTBFS when linking against OpenLDAP 2.5. I'm preparing the OpenLDAP 2.5 transition which will happen in this cycle (impish), and so I'm resolving all FTBFSes before uploading the new openldap package to -proposed. ** Affects: wine (Ubuntu) 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 Status: New ** Changed in: wine-development (Ubuntu) Status: New => Confirmed ** Changed in: wine-development (Ubuntu) Importance: Undecided => High ** Changed in: wine-development (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/1929859 Title: wine and wine-development FTBFS with OpenLDAP 2.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1929859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929859] Re: wine and wine-development FTBFS with OpenLDAP 2.5
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1929859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894618] Re: samba vfs glusterfs shares do not work because glusterfs.so is missing from samba-vfs-modules
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 user issues an "apt- get install samba-vfs-glusterfs" command, we want everything to be ready to be used when that command finishes. Having a package that doesn't fully list its dependencies/recommends goes against this goal. As Robie mentioned above, this issue could be driven by someone from the community who has the time and motivation to do the rest of the work. Please note that this person would be working to get the package into the development release of Ubuntu; more work would be needed in order to make this available in Focal (if that's even possible). Having said that, I'd like to say that I understand the frustration here. I put together a PPA containing a samba package for Focal with the glusterfs module enabled. Instead of doing what Andreas did and making sure that the new package doesn't depend on glusterfs (which is in universe), I decided to leave things closer to what Debian does and let it depend on anything that is needed. Please not that this package would not be suitable for the current state of the archive. The PPA is at: https://launchpad.net/~sergiodj/+archive/ubuntu/samba-glusterfs The git repository containing this temporary package is here: https://code.launchpad.net/~sergiodj/ubuntu/+source/samba/+git/samba/+ref /glusterfs-focal I will talk to the team tomorrow and see what can be done regarding this bug, but I make no promises here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894618 Title: samba vfs glusterfs shares do not work because glusterfs.so is missing from samba-vfs-modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1894618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912389] Re: [Patch] SIGSEGV: crash when certificate contains extension longer than 512 bytes
** 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 common to find certificates whose + extensions are larger than 512 bytes. + + [ Test Case ] + + Below you can find a step-by-step procedure to reproduce the bug. Bear + in mind that the "sed" command may be mangled due to Launchpad's text + renderization. + + $ lxc launch images:ubuntu/hirsute net-snmp-bug1912389 + $ lxc shell net-snmp-bug1912389 + # apt update && apt install net-snmp -y + # sed -i "s@^#\s*nsCertType.*@nsCertType = client,email,objsign@; s@^#\s*nsCaRevocationUrl.*@nsCaRevocationUrl = http://www.myverylongurl$(printf '%*s' 512 | tr ' ' 'a').com/ca-crl.pem@; s@^#\s*extendedKeyUsage.*@extendedKeyUsage = critical,timeStamping,serverAuth,clientAuth,codeSigning,emailProtection@; s@^#\s*keyUsage.*@keyUsage = nonRepudiation,digitalSignature,keyEncipherment@" /etc/ssl/openssl.cnf + # openssl req -x509 -out localhost.crt -keyout localhost.key-newkey rsa:2048 -nodes -sha256 -extensions usr_cert -subj '/CN=localhost' -config /etc/ssl/openssl.cnf + # mkdir -p $HOME/.snmp/tls/certs + # cp localhost.crt $HOME/.snmp/tls/certs + # systemctl stop snmpd.service + # snmpd -DALL + ... + not enough space or error in allocation for extenstion + Segmentation fault (core dumped) + # + + [ Where problems could occur ] + + The backported patches are very straightforward and only impact code + that is run when debug (-D) is active. There is not much room for + regression here, especially considering that this is a very recent + version of the package that will very likely not be affected by newer + rebuilds. + + [ Original Description ] + When net-snmp is given a certificate with an extension that is longer than 512 characters, snmp crashes on startup. Steps to Reproduce: 1. Configure net-snmp using an EV certificate from a CA (in this case Globalsign). 2. Start snmpd. 3. Actual results: [root@localhost tls]# systemctl status snmpd.service ● snmpd.service - Simple Network Management Protocol (SNMP) Daemon. -Loaded: loaded (/usr/lib/systemd/system/snmpd.service; disabled; vendor preset: disabled) -Active: failed (Result: core-dump) since Wed 2020-12-16 21:21:59 SAST; 16min ago - Process: 53269 ExecStart=/usr/sbin/snmpd $OPTIONS -f (code=dumped, signal=SEGV) - Main PID: 53269 (code=dumped, signal=SEGV) + Loaded: loaded (/usr/lib/systemd/system/snmpd.service; disabled; vendor preset: disabled) + Active: failed (Result: core-dump) since Wed 2020-12-16 21:21:59 SAST; 16min ago + Process: 53269 ExecStart=/usr/sbin/snmpd $OPTIONS -f (code=dumped, signal=SEGV) + Main PID: 53269 (code=dumped, signal=SEGV) Dec 16 21:21:57 localhost systemd[1]: Starting Simple Network Management Protocol (SNMP) Daemon Dec 16 21:21:58 localhost snmpd[53269]: refusing to read world readable or writable key /etc/snmp/tls/certs/snmpd.crt Dec 16 21:21:58 localhost snmpd[53269]: not enough space or error in allocation for extenstion Dec 16 21:21:59 localhost systemd[1]: snmpd.service: Main process exited, code=dumped, status=11/SEGV Dec 16 21:21:59 localhost systemd[1]: snmpd.service: Failed with result 'core-dump'. Dec 16 21:21:59 localhost systemd[1]: Failed to start Simple Network Management Protocol (SNMP) Daemon.. Expected results: Deamon starts without a crash. Additional info: Fix available here: https://github.com/net-snmp/net-snmp/pull/234 -- 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 longer than 512 bytes To manage notifications about this bug go to: https://bugs.launchpad.net/netsnmp/+bug/1912389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912389] Re: [Patch] SIGSEGV: crash when certificate contains extension longer than 512 bytes
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: [Patch] SIGSEGV: crash when certificate contains extension longer than 512 bytes To manage notifications about this bug go to: https://bugs.launchpad.net/netsnmp/+bug/1912389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912389] Re: [Patch] SIGSEGV: crash when certificate contains extension longer than 512 bytes
Thanks, Graham. This issue impacts Hirsute and Impish. For Impish, the best course of action here would be to wait for Debian to pick up this fix, which would then mean that Ubuntu would automatically pick it up as well. Given that Debian is in freeze right now, I don't know if the net-snmp maintainers there are planning to work on it anytime soon. For Hirsute, we'd need to go through the SRU process. The first step here would be to come up with a reliable set of steps to reproduce this issue, which I haven't been able to do so far (I confess I haven't had the time to test your Let's 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 (sergiodj) Status: Triaged ** Also affects: net-snmp (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: net-snmp (Ubuntu Hirsute) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) ** Changed in: net-snmp (Ubuntu Hirsute) Status: New => Triaged ** Changed in: net-snmp (Ubuntu Hirsute) 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/1912389 Title: [Patch] SIGSEGV: crash when certificate contains extension longer than 512 bytes To manage notifications about this bug go to: https://bugs.launchpad.net/netsnmp/+bug/1912389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912389] Re: [Patch] SIGSEGV: crash when certificate contains extension longer than 512 bytes
** 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. https://bugs.launchpad.net/bugs/1912389 Title: [Patch] SIGSEGV: crash when certificate contains extension longer than 512 bytes To manage notifications about this bug go to: https://bugs.launchpad.net/netsnmp/+bug/1912389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926321] Re: [MIR] telegraf
Phew, finally! Upstream has released a new version of telegraf this weekend, and I've just updated the Ubuntu telegraf package with it. This new version addresses all of the CVEs I'd mentioned, so I think the package is ready for the next step in the MIR process :-). Reassigning to Didier 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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926321 Title: [MIR] telegraf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegraf/+bug/1926321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
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. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
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, IIUC the patch you're proposing fixes the issue experienced by Stephane, but we're not entirely sure that it's the same issue being reported in this bug. Am I right? If that's correct, and if we verify that lincvz can still reproduce the bug even with the fix proposed by Ryan, then the best way forward would be for Stephane to open a new bug so that I can act on 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/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927980] Re: smartd-runner bug causes loss of email recipients
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 the Merge Request. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927980 Title: smartd-runner bug causes loss of email recipients To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1927980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928818] Re: package mysql-server-8.0 8.0.25-0ubuntu0.20.10.1 failed to install/upgrade: installed mysql-server-8.0 package pre-removal script subprocess returned error exit status 1
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 like you tried purging the MySQL packages *after* having installed MariaDB. Could you please try doing the opposite? First, purge MySQL and make sure that there is no mysql- server daemon running. Then, install MariaDB. If you still experience problems doing this, please let us know and try to provide as much detail as you can so that we can attempt to reproduce the issue. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** 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/1928818 Title: package mysql-server-8.0 8.0.25-0ubuntu0.20.10.1 failed to install/upgrade: installed mysql-server-8.0 package pre-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1928818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927755] Re: Fix for CVE-2020-28007 causes build failure when DMARC is enabled
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 Low. Unfortunately this usually means that we won't have the time to work on this bug, but given that you have already come up with a patch/workaround for the problem, I think this is mostly fine. Thank you again! ** Changed in: exim4 (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/1927755 Title: Fix for CVE-2020-28007 causes build failure when DMARC is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1927755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927980] Re: smartd-runner bug causes loss of email recipients
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 which looked very similar to this one: https://www.smartmontools.org/ticket/1454 It *may* be related, but it doesn't seem to directly impact this one (keep reading). After looking at the flow of execution, it was clear that: - smartd will call /usr/share/smartmontools/smartd_warning.sh after having set a bunch of environment variables that affect the execution of the script. For our purposes, the only variables we will need to manually set are SMARTD_ADDRESS and SMARTD_MAILER. - Because SMARTD_MAILER will be set to /usr/share/smartmontools/smartd- runner, this is the script that will be executed afterwards. After looking at what "smartd-runner" does (it invokes every executable under /etc/smartmontools/run.d/), and after verifying that the only thing under /etc/smartmontools/run.d/ is a very simple script called "10mail" (which just invokes the "mail" command with some arguments), it's clear that we can try to reproduce this bug by hand. By the way, here is the smartd function that is responsible for putting the arguments together and actually invoking the smartd_warning.sh script: https://www.smartmontools.org/browser/tags/RELEASE_7_1/smartmontools/smartd.cpp#L1084 In a nutshell, what the function seems to do is: To reproduce the bug, we can: $ lxc launch images:ubuntu/focal smartmontools-focal $ lxc shell smartmontools-focal # apt update && apt install -y smartmontools bsd-mailx # adduser test # SMARTD_ADDRESS="root test" SMARTD_MAILER=/usr/share/smartmontools/smartd-runner /usr/share/smartmontools/smartd_warning.sh # mail root ... verify that there's an email from smartd_warning ... # su - test $ mail No mail for test I verified that the reporter's patch seems to fix the problem. @John, I noticed that you opened a bug against Debian, which is good. However, there is already a bug opened about this problem: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661485 Could you please close your bug and comment on that other bug to let them know that you're also affected? Also, if you have the time, it would be good if you could also open a Merge Request against the Debian smartmontools project on salsa: https://salsa.debian.org/debian/smartmontools Thanks a lot. ** Bug watch added: www.smartmontools.org/ #1454 https://www.smartmontools.org/ticket/1454 ** Changed in: smartmontools (Ubuntu) Status: New => Triaged ** Changed in: smartmontools (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/1927980 Title: smartd-runner bug causes loss of email recipients To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1927980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904990] Re: Missing i386 version of libnss-sss
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. https://bugs.launchpad.net/bugs/1904990 Title: Missing i386 version of libnss-sss To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1904990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904990] Re: Missing i386 version of libnss-sss
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: Missing i386 version of libnss-sss To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1904990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927789] Re: Remove telegraf from the list
** 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 from the list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1927789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927789] [NEW] Remove telegraf from the list
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 way I performed the tests was to use the following excerpt on d/rules: export DEB_LDFLAGS_PREPEND = -flto=auto -ffat-lto-objects and I verified that the linker is being invoked with these options. I therefore think telegraf should be removed from the lto-disabled-list package. Thanks! ** Affects: lto-disabled-list (Ubuntu) Importance: Undecided Assignee: Matthias Klose (doko) 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/1927789 Title: Remove telegraf from the list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1927789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926321] Re: [MIR] telegraf
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. https://bugs.launchpad.net/bugs/1926321 Title: [MIR] telegraf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegraf/+bug/1926321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926321] Re: [MIR] telegraf
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 Title: [MIR] telegraf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegraf/+bug/1926321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1926321] Re: [MIR] telegraf
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 second look before we promote it to > main. Hopefully, as this is midly-supported already, that should be a > quick pass. Thank you very much for the review, Didier :-). > Thanks for the detailed security and CVE analysis, including the > vendored dependencies. Much appreciated :) > > Notes: > Questions: > - I think we should promote it once github.com/gogo/protobuf is fixed and an > upload with the vendored updated dep is done. It seems to be fixed in > 1.18.1+ds1-0ubuntu1, correct? That is correct. The latest version on Impish already has the fix for the gogo/protobuf CVE. Upstream has already fixed it, too. > - Same with github.com/prometheus/prometheus/, let’s wait then for the > latest version of telegraf which isn’t impacted by it (do you have the > version handy? Is it 1.18.1? and so, we can mark this as "DONE"?) The prometheus vulnerability does not affect the version of telegraf that is available on Impish, so I'd consider that "DONE" (or even "INVALID") :-). > - About the github.com/hashicorp/consul CVEs and fixes, do you have > any ETA? I think we should wait for them to be fixed before the actual > promotion (and this can give some time for the security team to assess > the package again), wdyt? Upstream has fixed the CVEs (by updating the hashicorp/consul version they're using) yesterday! I am just waiting for them to cut a release and then I will update the Impish package. > - You are patching the upstream service file in > debian/patches/adjust-service-user.patch but still provides a service > file in debian/telegraf.service. I didn’t see the later installed by > any script, and so, it seems the debian/ one is not needed anymore. Do > you mind having a look and clean that up? (Either removing the patch > which is not needed if we don’t install the upstream one or the unused > .service in debian/) The telegraf.service file under the debian/ directory is actually a symlink to the upstream one; it is needed because dh_installsystemd looks for it when deciding what to install. The patch is needed because we want the telegraf system user to be prefixed by an underscore, following the latest Debian Policy guidelines. So, in summary: both the patch and the symlink are needed :-). > Required TODOs: > - Can you check and update debian/copyright please? Some years are not > present, and copyright attribution are wrong (for instance > vendor/honnef.co/* has some files "Copyright 2014 The Go Authors"). I > think a second look would be good if you can ensure that everything is > up to date. Yes, sure. This will take some time but then again I am waiting until upstream releases a new version anyway :-). > - The package is in the list of lto-disabled list (see > https://launchpad.net/ubuntu/+source/lto-disabled-list). You need to > fix or work-around it directly in the package. If you need an example > for a go package disabling it (due to Go internals): > https://github.com/ubuntu/adsys/blob/main/debian/rules#L11 Ah, good point. I will look into this, thanks. Thanks again for the thorough review! -- Sergio GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926321 Title: [MIR] telegraf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegraf/+bug/1926321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
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 can't say for sure. I will wait until you are able to provide a backtrace or more information. I will see about talking to other OpenLDAP experts here and see if this bug rings any bells for them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913851] Re: pam_winbind should reject disabled users
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" group. You probably knew that already, but I'm leaving it here in case someone else faces the same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1913851 Title: pam_winbind should reject disabled users To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1913851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913851] Re: pam_winbind should reject disabled users
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. The bad news is that the person who was trying to implement the PAM account support on winbind has lost interest in doing so. Anyway, I'm marking this bug as triaged and linking the upstream bug, but unfortunately we won't be able to do much here unless upstream takes the lead on this. Sorry about it. ** Bug watch added: Samba Bugzilla #14622 https://bugzilla.samba.org/show_bug.cgi?id=14622 ** Changed in: samba (Ubuntu) Status: Incomplete => Triaged ** Also affects: samba via https://bugzilla.samba.org/show_bug.cgi?id=14622 Importance: Unknown Status: Unknown ** Changed in: samba (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1913851 Title: pam_winbind should reject disabled users To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1913851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916485] Re: test -x fails inside shell scripts in containers
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913851] Re: pam_winbind should reject disabled users
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: # login inva...@ad1.example.com Password: Your account has been locked. Please contact your System administrator Login incorrect # I'm afraid I don't fully understand what you meant by "which means that they can still be logged into through other credentials." What credentials are you referring to here? If you could provide steps to reproduce what you meant, that would be very helpful. Thank you. ** Changed in: samba (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1913851 Title: pam_winbind should reject disabled users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1913851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
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, and was able to determine that Bionic's openldap already carries an improved version of the patch (unsurprisingly). I've also found an old Launchpad bug (#15270) and the related Debian bug (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=255276) that reports the same problem as you, and is marked having been fixed in Debian (also back in 2005). I am a bit surprised that you're experiencing this problem on Bionic. I understand that it is hard to provide steps for reproducing this problem, but I would like to ask you to provide as much information as you can, please. For example: - Your full openldap configuration (please remove any confidential bits, of course). - Any log messages from slapd or related services. - If you can, please install the debug symbols for openldap/slapd and run "gdb -p $PROCESS_PID" (where "$PROCESS_PID" is slapd's PID), then run a "bt" command and attach the output to this bug. - More information about what is going on in the system when the problem happens. For example, I've read that this might happen when the system load is high; do you notice that as well? Meanwhile, I will mark this bug as Incomplete. Feel free to revert its status back to New once you provide more info. Thanks! ** Bug watch added: Debian Bug tracker #255276 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=255276 ** Changed in: openldap (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/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926324] Re: Autogenerated freshclam.conf should not mention now-deprecated option SafeBrowsing
Thanks for taking the time to report a bug and help making Ubuntu better. I can obviously confirm this problem, but it's a low priority one (upstream seems to have decided that the SafeBrowsing option simply doesn't do anything anymore, so it's not "dangerous" to leave it in the configuration file). For this reason, I think it's better to address this on Debian's clamav package. I went ahead and filed the following MR against Debian clamav: https://salsa.debian.org/clamav-team/clamav/-/merge_requests/3 Eventually this will be accepted (I hope), and then Ubuntu's clamav will incorporate the fix once it's merged. Feel free to subscribe to the MR above if you'd like to follow its progress. Thanks. ** Changed in: clamav (Ubuntu) Status: New => Triaged ** Changed in: clamav (Ubuntu) Importance: Undecided => Low ** Changed in: clamav (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/1926324 Title: Autogenerated freshclam.conf should not mention now-deprecated option SafeBrowsing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1926324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925968] Re: gogo protobuf CVE-2021-3121
** 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 => Triaged ** Changed in: telegraf (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: telegraf (Ubuntu Hirsute) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) ** Changed in: telegraf (Ubuntu Hirsute) Status: Triaged => Fix Released ** Changed in: telegraf (Ubuntu Hirsute) Status: Fix Released => Triaged ** Changed in: telegraf (Ubuntu Impish) 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/1925968 Title: gogo protobuf CVE-2021-3121 To manage notifications about this bug go to: https://bugs.launchpad.net/telegraf/+bug/1925968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926321] Re: [MIR] telegraf
** 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 part of a suite of programs referred to as LMA (Logging, Monitoring and Alert). It is responsible for the Logging; prometheus, prometheus-alertmanager and grafana are the other components of this solution. We, the Ubuntu Server team, have been maintaining the package for the last several months, and we now would like to proceed with the MIR process for it. The telegraf package is being used as the building block of the equivalent telegraf OCI image (see https://hub.docker.com/repository/docker/ubuntu/telegraf), which is an official image provided and supported by Canonical. It is important to also note that the security team is already providing tracking and notification of potential vulnerabilities and CVEs on this OCI image, which means that, indirectly, the Ubuntu telegraf package is already being treated more or less as a main package. [ Security ] Unfortunately, due to the large number of unpackaged Golang dependencies, it was not possible to package telegraf in Debian first and then sync it to Ubuntu. For this reason, the Ubuntu telegraf package contains hundreds of vendorized Golang dependencies inside its orig tarball. I could not find any CVEs for telegraf itself on http://cve.mitre.org/ (the only thing I found was related to telegraf's official OCI image, which does not apply to this MIR). While analysing the Golang dependencies, I have found the following CVEs: - For github.com/dgrijalva/jwt-go/v4: https://nvd.nist.gov/vuln/detail/CVE-2020-26160 This vulnerability does not affect the current version that is in Hirsute/Impish. - For github.com/gogo/protobuf: https://nvd.nist.gov/vuln/detail/CVE-2021-3121 This vulnerability is being addressed at the time of this writing, both by upstream and by us. - For github.com/hashicorp/consul: https://nvd.nist.gov/vuln/detail/CVE-2020-7219 https://nvd.nist.gov/vuln/detail/CVE-2018-19653 https://nvd.nist.gov/vuln/detail/CVE-2020-28053 https://nvd.nist.gov/vuln/detail/CVE-2020-13250 These vulnerabilities do affect the current version in Hirsute/Impish, but they are not trivial to fix and we are working with upstream to address them. - For github.com/prometheus/prometheus/ https://nvd.nist.gov/vuln/detail/CVE-2019-3826 - These vulnerability does affect the current version in Hirsute/Impish, - but it is not trivial to fix and we are working with upstream to - address it. + These vulnerability does *not* affect the latest upstream version of + telegraf, which is being packaged for Impish. [ Quality Assurance ] - The package is installed with a reasonable configuration file and - a proper systemd service. + a proper systemd service. - It does not ask any debconf questions during installation. - There are no long-term outstanding bugs that affect the usability of - the program. + the program. - The package is not available in Debian, so there is no bug there. - The only bug opened against the Ubuntu telegraf package right now is - the one dealing with CVE-2021-3121. + the one dealing with CVE-2021-3121. - The package is well-maintained in Ubuntu by the Ubuntu Server team. - The package does not deal with exotic hardware that is not supported - by Ubuntu. It does offer probes and code to deal with some optional - hardware that may be installed in the user's computer, but by - default this support is disabled in the configuration file. + by Ubuntu. It does offer probes and code to deal with some optional + hardware that may be installed in the user's computer, but by + default this support is disabled in the configuration file. - The package ships with a test suite which is executed during - build-time and passes on all supported architectures. It also ships - with a simple dep8 test. + build-time and passes on all supported architectures. It also ships + with a simple dep8 test. - The package provides a debian/watch file. - The package is lintian-free (including with --pedantic). [ UI standards ] N/A [ Dependencies ] As it is a Golang package, the telegraf binary is statically compiled and doesn't depend on anything else other than libc6. The only extra dependency that was added (due to the postinst script) is adduser, which is also in main. [ Standards compliance ] The package follows FHS and Debian Policy standards to the maximum extent. The only clear violation to the policy, as mentioned above, is the fact that all Golang modules are vendorized (bundled) in the source package. Otherwise, everyth
[Bug 1926321] [NEW] [MIR] telegraf
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 programs referred to as LMA (Logging, Monitoring and Alert). It is responsible for the Logging; prometheus, prometheus-alertmanager and grafana are the other components of this solution. We, the Ubuntu Server team, have been maintaining the package for the last several months, and we now would like to proceed with the MIR process for it. The telegraf package is being used as the building block of the equivalent telegraf OCI image (see https://hub.docker.com/repository/docker/ubuntu/telegraf), which is an official image provided and supported by Canonical. It is important to also note that the security team is already providing tracking and notification of potential vulnerabilities and CVEs on this OCI image, which means that, indirectly, the Ubuntu telegraf package is already being treated more or less as a main package. [ Security ] Unfortunately, due to the large number of unpackaged Golang dependencies, it was not possible to package telegraf in Debian first and then sync it to Ubuntu. For this reason, the Ubuntu telegraf package contains hundreds of vendorized Golang dependencies inside its orig tarball. I could not find any CVEs for telegraf itself on http://cve.mitre.org/ (the only thing I found was related to telegraf's official OCI image, which does not apply to this MIR). While analysing the Golang dependencies, I have found the following CVEs: - For github.com/dgrijalva/jwt-go/v4: https://nvd.nist.gov/vuln/detail/CVE-2020-26160 This vulnerability does not affect the current version that is in Hirsute/Impish. - For github.com/gogo/protobuf: https://nvd.nist.gov/vuln/detail/CVE-2021-3121 This vulnerability is being addressed at the time of this writing, both by upstream and by us. - For github.com/hashicorp/consul: https://nvd.nist.gov/vuln/detail/CVE-2020-7219 https://nvd.nist.gov/vuln/detail/CVE-2018-19653 https://nvd.nist.gov/vuln/detail/CVE-2020-28053 https://nvd.nist.gov/vuln/detail/CVE-2020-13250 These vulnerabilities do affect the current version in Hirsute/Impish, but they are not trivial to fix and we are working with upstream to address them. - For github.com/prometheus/prometheus/ https://nvd.nist.gov/vuln/detail/CVE-2019-3826 These vulnerability does affect the current version in Hirsute/Impish, but it is not trivial to fix and we are working with upstream to address it. [ Quality Assurance ] - The package is installed with a reasonable configuration file and a proper systemd service. - It does not ask any debconf questions during installation. - There are no long-term outstanding bugs that affect the usability of the program. - The package is not available in Debian, so there is no bug there. - The only bug opened against the Ubuntu telegraf package right now is the one dealing with CVE-2021-3121. - The package is well-maintained in Ubuntu by the Ubuntu Server team. - The package does not deal with exotic hardware that is not supported by Ubuntu. It does offer probes and code to deal with some optional hardware that may be installed in the user's computer, but by default this support is disabled in the configuration file. - The package ships with a test suite which is executed during build-time and passes on all supported architectures. It also ships with a simple dep8 test. - The package provides a debian/watch file. - The package is lintian-free (including with --pedantic). [ UI standards ] N/A [ Dependencies ] As it is a Golang package, the telegraf binary is statically compiled and doesn't depend on anything else other than libc6. The only extra dependency that was added (due to the postinst script) is adduser, which is also in main. [ Standards compliance ] The package follows FHS and Debian Policy standards to the maximum extent. The only clear violation to the policy, as mentioned above, is the fact that all Golang modules are vendorized (bundled) in the source package. Otherwise, everything else follows the standards. [ Maintenance ] The telegraf package has already been maintained by the Ubuntu Server team, and this will continue to apply. [ Background information ] We are still considering and discussing whether it makes sense to pursue an SRU exception for MRE applicable to telegraf. We are trying to gather more information from our userbase in order to determine whether they would be benefited from having a newer telegraf package in a stable release, and what the implications of that would be. ** Affects: telegraf (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/1926321 Titl
[Bug 1916485] Re: test -x fails inside shell scripts in containers
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925968] [NEW] gogo protobuf CVE-2021-3121
Public bug reported: The gogo protobuf module that is being used by the image (version 1.3.1) has a vulnerability: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3121 Since this module is bundled (vendorized) inside the source package, we need to update it. ** Affects: telegraf 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/issues #9181 https://github.com/influxdata/telegraf/issues/9181 ** Also affects: telegraf via https://github.com/influxdata/telegraf/issues/9181 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/1925968 Title: gogo protobuf CVE-2021-3121 To manage notifications about this bug go to: https://bugs.launchpad.net/telegraf/+bug/1925968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925182] Re: ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!)
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 service, as the reporter himself mentioned. I'm marking this bug as Triaged and subscribing ubuntu-server, anyway. Thank you both for confirming the bug. ** Changed in: clamav (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/1925182 Title: ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1925182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34
** 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. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34
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 you for following up on Paride's request for further tests. I'm wondering here: I know that the 'sensors' command lets you specify which chips you want to get the temperature for, and given that this problem seems to happen every time you execute the command, then I think it's worth trying to pinpoin which chip is causing the problem here. Could you please try to run the command several times, specifying the different chip names each time, and see what happens? Maybe there's nothing to it, but we never know. Another thing I was going to ask you is this: based on your comments, it seemed to me that you were able to reproduce this problem not only in Ubuntu, but also in other distributions. Is that correct? If it is, do you think you could test a pristine Linux kernel (from https://kernel.org)? If the bug reproduces with it, then I would recommend opening a bug report against the upstream Linux project. For this specific bug, I think it's worth adding the Ubuntu Linux kernel package and seeing what the kernel folks have to say. Maybe they can come up with other things you can try to determine what's going on. I'm setting this bug status back to New and adding the Ubuntu Linux package to it. I'm also going to subscribe myself to this bug so that we don't miss any more updates from you. Thank you. ** Changed in: linux-signed-hwe-5.8 (Ubuntu) Status: Expired => New ** Changed in: lm-sensors (Ubuntu) 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/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1910562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925182] Re: ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!)
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 (for amd64): https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/+build/19629559 - Install the files grabbed above. Verify that the "clamav- freshclam.service" is running. - apt update && apt ugprade. This will upgrade all clamav packages. - Verify that the "clamav-freshclam.service" is still running. Given the unsuccessful attempt to reproduce the problem, I tried searching on the internet for similar reports. I've found some people saying that this scenario might happen when there is a freshclam process blocked, which would prevent the new freshclam process (being started by systemd) from manipulating the log file. I don't know if that's your case, though, because I don't see any explicit error messages saying that there is another blocked freshclam process. I have found https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972974, which, albeit similar, ended up being an apparmor problem that is not present in Ubuntu. I have also double checked your configuration files, and they both seem normal. I'm wondering if this is a problem that happened due to very specific conditions: freshclam must have been busy trying to update the database, and coincidentally unattended-upgrades ran at that very moment and tried to restart the service, leading to the error. Woud you be able to provide a bit more information so that we can try to reproduce the problem determine what's causing it? For example, would you be able to downgrade your freshclam/clamav packages and then update them again? Also, is there anything interesting in journalctl that is worth mentioning here? Some explicit message about the file being locked by another freshclam process, for example? Since there is not enough information in your report to begin triage or to differentiate between a local configuration problem and a bug in Ubuntu, I am marking this bug as "Incomplete". We would be grateful if you would: provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Bug watch added: Debian Bug tracker #972974 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972974 ** Changed in: clamav (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/1925182 Title: ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1925182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925118] Re: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: el subproceso instalado paquete mysql-server-8.0 script post-installation devolvió el código de salida de
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) ... /var/lib/dpkg/info/mysql-server-8.0.postinst: línea 191: /usr/share/mysql-common/configure-symlinks: No existe el archivo o el directorio This file (/usr/share/mysql-common/configure-symlinks) is part of the mysql-common package, which should be installed because it's a dependency of the mysql-server package. It is not clear from the logs what caused this file to be missing; did you perhaps remove this file or its parent directory by hand? You can try purging the mysql-common package and reinstalling it: # apt purge mysql-common # apt install mysql-common This should solve the problem for you. If you haven't deleted the /usr/share/mysql-common/configure-symlinks file by hand, then please try to provide more details about the issue: the MySQL error logs, and the sequence of commands that you're executing would be helpful to try and diagnose what's happening. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** 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/1925118 Title: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: el subproceso instalado paquete mysql-server-8.0 script post-installation devolvió el código de salida de error 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1925118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917362] Re: PAM: smartcard owner isn't associated to user by default
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 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 default To manage notifications about this bug go to: https://bugs.launchpad.net/sssd/+bug/1917362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822012] Re: powernv machine complains of missing skiboot files
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 marking this bug as Incomplete because we were unable to reproduce the issue. Moreover, I would like to reinforce Frédéric's request here and ask that you please provide more details, like what exactly you're trying to do, the commands you're using, the output you're seeing, etc. Thanks. ** Changed in: qemu (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/1822012 Title: powernv machine complains of missing skiboot files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1822012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697339] Re: rpc.gssd performs reverse DNS by default (regardless of -D flag)
** 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 to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1697339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916485] Re: test -x fails inside shell scripts in containers
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 Title: test -x fails inside shell scripts in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916485] Re: test -x fails inside shell scripts in containers
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 ... # apt policy docker.io docker.io: Installed: 20.10.2-0ubuntu1~18.04.2 ... # apt policy runc runc: Installed: 1.0.0~rc93-0ubuntu1~18.04.1 ... Following the reproduction steps listed in the Description section still fail for me: # systemd-nspawn Spawning container h on /root/h. Press ^] three times within 1s to kill container. # bash -c 'test -x /usr/bin/gpg || echo Fail' Fail When I'm in a hirsute Docker container, it also fails: $ docker run -it --rm ubuntu:hirsute root@78506947b11f:/# bash -c 'test -x /usr/bin/gpg || echo Fail' Fail This is impacting the build of the 21.04 OCI images on s390x (amd64, arm64 and ppc64el succeed). I'm still not sure what's causing this, nor why this is happening only on s390x. I will post more details when I have them. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917362] Re: PAM: smartcard owner isn't associated to user by default
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 default To manage notifications about this bug go to: https://bugs.launchpad.net/sssd/+bug/1917362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890406] Re: tmux sessions don't show up with who, users, ...
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 and also tagging it as server-next. ** Changed in: tmux (Ubuntu Focal) Importance: Low => Medium ** Tags added: bitesize 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/1890406 Title: tmux sessions don't show up with who, users, ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1890406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923108] Re: FTBFS against docker 20.10
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: https://bugs.launchpad.net/ubuntu/+source/golang-github-fsouza-go-dockerclient/+bug/1923108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923108] Re: FTBFS against docker 20.10
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 else LGTM to me otherwise. I have tested the patch locally and verified that it does indeed fix the FTBFS that happens without it. The only other comment I have is the fact that the package doesn't have a dep8/autodep8 test (I tried running it locally and got the "SKIP no tests in this package" message), so it may be a bit harder to verify that the functionality stays the same and there are no regressions due to the SRU. -- 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: https://bugs.launchpad.net/ubuntu/+source/golang-github-fsouza-go-dockerclient/+bug/1923108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921011] Re: Fix build against new runc version
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 first need to build golang-github-containers-buildah, and then you have to use the generated package while building libpod. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921011 Title: Fix build against new runc version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1921011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822632] Re: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b69c5feaf58 for symbol `' out of range
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 again, because (a) I had already checked, and (b) the bug happened only on ppc64el. Either way, thank you for going the extra mile and double checking on amd64. -- 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 0x0b69c5feaf58 for symbol `' out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gosu/+bug/1822632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822632] Re: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b69c5feaf58 for symbol `' out of range
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 /var/lib/dpkg/status # gosu nobody true gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x0f3e7ac4af58 for symbol `' out of range Now, installing the package from -proposed and verifying that it fixes the problem: # apt policy gosu gosu: Installed: 1.10-1ubuntu0.18.04.1 Candidate: 1.10-1ubuntu0.18.04.1 Version table: *** 1.10-1ubuntu0.18.04.1 100 100 /var/lib/dpkg/status 1.10-1 500 500 http://us.ports.ubuntu.com/ubuntu-ports bionic/universe ppc64el Packages # gosu nobody true # echo $? 0 This concludes the verification for Bionic. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal ** Tags added: verification-done-bionic verification-done-focal -- 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 0x0b69c5feaf58 for symbol `' out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gosu/+bug/1822632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822632] Re: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b69c5feaf58 for symbol `' out of range
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 /var/lib/dpkg/status # gosu nobody true gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x0b31335eaf58 for symbol `' out of range Now, installing the package from -proposed and verifying that it fixes the problem: # apt policy gosu gosu: Installed: 1.10-1ubuntu0.20.04.1 Candidate: 1.10-1ubuntu0.20.04.1 Version table: *** 1.10-1ubuntu0.20.04.1 100 100 /var/lib/dpkg/status 1.10-1 500 500 http://us.ports.ubuntu.com/ubuntu-ports focal/universe ppc64el Packages # gosu nobody true # echo $? 0 This concludes the verification for Focal. -- 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 0x0b69c5feaf58 for symbol `' out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gosu/+bug/1822632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921872] Re: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
*** 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 /var/log/mysql/error.log mysqld is running as pid 36266 Error: Unable to shut down server with process id 36266 dpkg: error processing package mysql-server-8.0 (--configure): installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 There is nothing really wrong in the mysql error log, from what I can see. I could mark this bug as Incomplete, but it actually looks like a duplicate of #1876900, so I'm marking it as such. Feel free to reopen it if you consider this is a different issue. ** This bug has been marked a duplicate of bug 1876900 package mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921872 Title: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1921872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921630] Re: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de
*** 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: can't create lock file /var/run/mysqld/mysqlx.sock.lock (service startup timeout?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921630 Title: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1921630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921356] Re: package mysql-server-8.0 8.0.22-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
** 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 install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1921356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919322] Re: Backport the container stack in Hirsute
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 (the ZFS one, if I'm understanding correctly). The extra hunk that is being added to the posting script is just related to ZFS, and it has been tested on Hirsute (as mentioned) and backported to Groovy already, and it's making its way down the line. Not sure if this answers the question; let me know if you need more details. 2) Indeed, we need a trasitional package for this one. I am working on it, and will ping someone an AA before proceeding with the upload. I have already left a message on #ubuntu-release to the archive admins asking for a pre-approval before I go ahead and upload. 3) The change is intentional and comes from upstream. I tracked it to the following commit: https://github.com/moby/moby/commit/28e93ed8caad2c15d2b3b704801c71b9584de91e Which, according to the description, was made because PartOf deactivates the socket when the service gets deactivated, which shouldn't happen. This makes sense to me, and historically the systemd bits from these packages have always come from upstream, without any distro-specific change required. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919322 Title: Backport the container stack in Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1919322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822632] Re: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b69c5feaf58 for symbol `' out of range
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 > architectures. True, thanks for the catch. I have updated the "Where problems could occur" section and reworded it in a way that it's clear that I meant "there can be no regressions *on ppc64el*". > Accepting, but please could you add something to the Test Plan to ensure > that the package still basically works on amd64, if that's not already > covered by existing tests? Done for both Bionic and Focal, let me know if that's enough. Thanks, -- Sergio GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 ** 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 of range [Test Plan] You will need a ppc64el machine in order to test this. This bug happens on Bionic and Focal. # apt update # apt install gosu # gosu nobody true gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x0abd18d0af58 for symbol `' out of range + If you check on (e.g.) amd64, you can see that the software works fine. + The following is on Bionic: + + # gosu nobody true + # echo $? + 0 + + Then on Focal: + + # gosu nobody true + # echo $? + 0 + [Where problems could occur] This particular update is not able to cause any regressions, because the software did not work before it. One can always say that there is a chance for a regression when rebuilding an old package from Bionic against newer libraries, but in this case I think the chances are slim to none, especially because gosu depends on very few libraries (which is unusual for a Golang application). [Original Description] After installing "gosu" on Bionic 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 + gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x0b41bcc7af58 for symbol `' out of range I spoke briefly with mwhudson about it (recalling he might've dealt with similar issues previously) and he suggested it probably needs a rebuild and asked me to file a bug. :) (Something something PIC something something PIE something something Go toolchain.) ** 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 of range [Test Plan] You will need a ppc64el machine in order to test this. This bug happens on Bionic and Focal. # apt update # apt install gosu # gosu nobody true gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x0abd18d0af58 for symbol `' out of range If you check on (e.g.) amd64, you can see that the software works fine. The following is on Bionic: # gosu nobody true # echo $? 0 Then on Focal: # gosu nobody true # echo $? 0 [Where problems could occur] - This particular update is not able to cause any regressions, because the - software did not work before it. One can always say that there is a + This particular update is not able to cause any regressions on ppc64el, + because the software did not work before it. + + As for the other architectures, one can always say that there is a chance for a regression when rebuilding an old package from Bionic against newer libraries, but in this case I think the chances are slim to none, especially because gosu depends on very few libraries (which is unusual for a Golang application). [Original Description] After installing "gosu" on Bionic 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 of range I spoke briefly with mwhudson about it (recalling he might've dealt with similar issues previously) and he suggested it probably needs a rebuild and asked me to file a bug. :) (Something something PIC something something PIE something something Go toolchain.) -- 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 0x0b69c5feaf58 for symbol `' out of
[Bug 1822632] Re: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b69c5feaf58 for symbol `' out of range
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 0x0b69c5feaf58 for symbol `' out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gosu/+bug/1822632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822632] Re: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b69c5feaf58 for symbol `' out of range
** 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 Title: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x0b69c5feaf58 for symbol `' out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gosu/+bug/1822632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822632] Re: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b69c5feaf58 for symbol `' out of range
** 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 Title: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x0b69c5feaf58 for symbol `' out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gosu/+bug/1822632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822632] Re: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b69c5feaf58 for symbol `' out of range
** 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) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) ** Changed in: gosu (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: gosu (Ubuntu Focal) Status: Confirmed => 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/1822632 Title: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x0b69c5feaf58 for symbol `' out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gosu/+bug/1822632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822632] Re: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b69c5feaf58 for symbol `' out of range
** 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 of range + + [Test Plan] + + You will need a ppc64el machine in order to test this. This bug happens + on Bionic and Focal. + + # apt update + # apt install gosu + # gosu nobody true + gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x0abd18d0af58 for symbol `' out of range + + [Where problems could occur] + + This particular update is not able to cause any regressions, because the + software did not work before it. One can always say that there is a + chance for a regression when rebuilding an old package from Bionic + against newer libraries, but in this case I think the chances are slim + to none, especially because gosu depends on very few libraries (which is + unusual for a Golang application). + + [Original Description] + After installing "gosu" on Bionic 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 of range I spoke briefly with mwhudson about it (recalling he might've dealt with similar issues previously) and he suggested it probably needs a rebuild and asked me to file a bug. :) (Something something PIC something something PIE something something Go toolchain.) -- 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 0x0b69c5feaf58 for symbol `' out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gosu/+bug/1822632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1920941] Re: spamassassin cron job behaviour undefined message
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 key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920941 Title: spamassassin cron job behaviour undefined message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1920941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920941] Re: spamassassin cron job behaviour undefined message
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 tells me), and rightly so: it is supposed to be provided by the sysadmin, if needed, and it can be used to control the behaviour of invoke-rc.d (for example, prevent it from starting services). I wonder where yours is coming from. Could you please verify that (the file is named /usr/sbin/policy-rc.d), and also provide its contents? Given that we don't have enough information to proceed with the investigation, I'm changing this bug's status to Incomplete. Feel free to mark it as New again when you provide the requested info. Thanks! ** Changed in: spamassassin (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/1920941 Title: spamassassin cron job behaviour undefined message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1920941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920876] Re: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
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: 2021-03-16 10:38:36 Commandline: apt remove phpmyadmin php-mbstring php-zip php-gd php-json php-curl Remove: php-gd:amd64 (2:7.4+75), php-zip:amd64 (2:7.4+75), phpmyadmin:amd64 (4:4.9.5+dfsg1-2), php-json:amd64 (2:7.4+75), php-curl:amd64 (2:7.4+75), php-mbstring:amd64 (2:7.4+75) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2021-03-16 10:39:35 Start-Date: 2021-03-17 11:09:11 Commandline: apt install vim Install: vim-runtime:amd64 (2:8.1.2269-1ubuntu5, automatic), vim:amd64 (2:8.1.2269-1ubuntu5) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2021-03-17 11:10:20 ... and so on. These are very strange errors, and tell me that dpkg is having trouble doing relatively simple operations such as installing vim, htop, etc. >From DpkgTerminalLog.txt, I see a strange, mangled output which eventually ends with: dpkg: error processing package phpmyadmin (--configure): installed phpmyadmin package post-installation script subprocess returned error exit status 1 This means that phpmyadmin failed to be configured, possibly leaving the package in an inconsistent state. I'm not sure offhand if this failure could also impact mysql-server's installation, but it is possible, especially if we take into account the (cryptic) log that comes right before this part: [K[1;1H[37mPackage configuration[7;20H[30m[47m┌──┤ [31mConfiguring phpmyadmin[30m ├───┐[8;20H│ Next step for database installation:... ... [?1049l[23;0;0tdbconfig-common: phpmyadmin configure: aborted. And then, from Logs.var.log.mysql.error.log.txt I see: 2021-03-23T07:33:44.041940Z 0 [ERROR] [MY-010262] [Server] Can't start server: Bind on TCP/IP port: Address already in use 2021-03-23T07:33:44.042209Z 0 [ERROR] [MY-010257] [Server] Do you already have another mysqld server running on port: 3306 ? 2021-03-23T07:33:44.042744Z 0 [ERROR] [MY-010119] [Server] Aborting This means that there is likely another instance of mysqld running, and that's why it was not possible to start it again. Overall, your system seems to be in an inconsistent and/or problematic state based on the outputs I analyzed from the logs. If possible, it would be helpful to have more logs for e.g. the following operations: # apt purge mysql-server-8.0 # apt install mysql-server-8.0 Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** 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/1920876 Title: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1920876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921011] Re: Fix build against new runc version
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921011 Title: Fix build against new runc version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1921011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912691] Re: [SRU] Support runc/1.0.0~rc93-0ubuntu1
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 the "Test Plan" section, s/caught/catch/. - In the "Where problems could occur" section, this sentence seems strange: "We are replacing a system call which would require cgo with a constant." Just pointing it out in case you want to clarify 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/1912691 Title: [SRU] Support runc/1.0.0~rc93-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opengcs/+bug/1912691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909816] Re: asterisk spams console output to syslog due to systemd misconfiguration
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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909816 Title: asterisk spams console output to syslog due to systemd misconfiguration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1909816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918141] Re: nfs-server.service needs name resolution and network online
service do depend on network.target, that only means
that the network has been configured. On physical hardware it can take
significantly longer for the network to come online (8+ seconds for our
10G NICs). Also note that we configure static IP:s via systemd-networkd,
things might behave differently when using DHCP, network-manager etc. In
any case, depending on network.target is almost always wrong, and
network-online.target is usually the right one.
nss-lookup.target is needed to ensure that DNS resolution works, and
nss-user-lookup.target is the best approximation to ensure that netgroup
resolution via sssd or equivalent works. Usually things "just works"
even without these dependencies, but to ensure correct startup they
should be present.
It should be noted that this seems to once have been fixed in Ubuntu,
but has been lost along the way for quite some time. When googling I
find for example https://code.launchpad.net/~ubuntu-branches/ubuntu/wily
/nfs-utils/wily-201507271018/+merge/265946 that fixes the network.target
vs network-online.target dependency, but it has since been lost in the
wind it seems.
** Also affects: nfs-utils (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: nfs-utils (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nfs-utils (Ubuntu Hirsute)
Importance: Undecided
Assignee: Sergio Durigan Junior (sergiodj)
Status: Confirmed
** Also affects: nfs-utils (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: nfs-utils (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 Junior (sergiodj)
** Changed in: nfs-utils (Ubuntu Groovy)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Changed in: nfs-utils (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/1918141
Title:
nfs-server.service needs name resolution and network online
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918141/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909816] Re: asterisk spams console output to syslog due to systemd misconfiguration
@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 scenario that happens often or not. I confess I was taking apache2 as an example here: you have the logs under /var/logs/apache2, and even if you execute apache2 by hand you will still *not* see the log being output to stdout/stderr. In any case, I still think it's not a good idea to silence the stderr input in journalctl, so while I think the proposed patch makes sense, I would remove the "StandardError=null" line from it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909816 Title: asterisk spams console output to syslog due to systemd misconfiguration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1909816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909816] Re: asterisk spams console output to syslog due to systemd misconfiguration
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 with the service file at all. Also, it's important to note that disabling input from stderr in the service file is not a good idea: any errors that happen and are printed there should show up in journalctl. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909816 Title: asterisk spams console output to syslog due to systemd misconfiguration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1909816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918141] Re: nfs-server.service needs name resolution and network online
** 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 name resolution and network online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918141] Re: nfs-server.service needs name resolution and network online
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 needs name resolution and network online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917362] Re: PAM: smartcard owner isn't associated to user by default
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 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 default To manage notifications about this bug go to: https://bugs.launchpad.net/sssd/+bug/1917362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909816] Re: asterisk spams console output to syslog due to systemd misconfiguration
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 Ubuntu. https://bugs.launchpad.net/bugs/1909816 Title: asterisk spams console output to syslog due to systemd misconfiguration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1909816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909816] Re: asterisk spams console output to syslog due to systemd misconfiguration
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 journalctl) - The /var/log/asterisk/messages file I also agree that it is somewhat annoying to have an application dump its logs into journalctl, especially when it already logs things elsewhere. I noticed that you don't actually need to tweak asterisk's service file; all you need to do is edit /etc/asterisk/logger.conf and comment the following line: console => notice,warning,error Once you do that, you will stop seeing the logs on journalctl (but they will keep being log on /var/log/asterisk/messages). I think this is a valid request. Given that the "fix" to this problem is easy and well documented, I am marking this as Low priority. Would you like to try submitting this request to the Debian asterisk package as well? This way, if they fix it in Debian, Ubuntu will automatically pick up the change. Thank you. ** Changed in: asterisk (Ubuntu) Status: New => Triaged ** Changed in: asterisk (Ubuntu) Importance: Undecided => Low ** Tags added: bitesize -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909816 Title: asterisk spams console output to syslog due to systemd misconfiguration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1909816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919016] Re: fcgi.pc file not provided
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: Undecided Status: New ** Changed in: libfcgi (Ubuntu Focal) Status: New => Triaged ** Changed in: libfcgi (Ubuntu Groovy) Status: New => Triaged ** Changed in: libfcgi (Ubuntu Focal) Importance: Undecided => Low ** Changed in: libfcgi (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: libfcgi (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919016 Title: fcgi.pc file not provided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfcgi/+bug/1919016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919016] Re: fcgi.pc file not provided
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 version we ship on Focal does not provide an fcgi.pc file. In theory we could maintain our own Ubuntu-specific fcgi.pc file, but I think it would be easier for you to just adjust the Makefile and manually set LDFLAGS with the correct values for libfcgi. I am marking this bug as Incomplete for now because we need to know your Ubuntu release first. When you provide it, please set this bug status back to "New". Thank you! ** Changed in: libfcgi (Ubuntu) Status: New => Incomplete ** Changed in: libfcgi (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/1919016 Title: fcgi.pc file not provided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfcgi/+bug/1919016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918860] Re: Kontol
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 Ubuntu. https://bugs.launchpad.net/bugs/1918860 Title: Kontol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1918860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919074] Re: cannot login nor create account
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 files that are relevant to this case. Since there is not enough information in your report to begin triage, I am marking this bug as "Incomplete". We would be grateful if you would: provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: apache2 (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/1919074 Title: cannot login nor create account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1919074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915063] Re: Windows 10 wil not install using qemu-system-x86_64
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1915063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly
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, although I have not reproduced it myself. ** Changed in: network-manager (Ubuntu) Status: Incomplete => Triaged ** Changed in: openvpn (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917887 Title: Network Manager OpenVPN nested connections fail to setup routes correctly To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/1917887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly
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 you said you were able to reproduce this problem on more than one version of CentOS, I am inclined to believe that, if this is indeed an issue, it came from upstream. ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #204 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/204 ** Also affects: openvpn via https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/204 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/1917887 Title: Network Manager OpenVPN nested connections fail to setup routes correctly To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/1917887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918259] Re: package apache2 2.4.41-4ubuntu3.1 failed to install/upgrade: installed apache2 package post-installation script subprocess returned error exit status 1
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 /etc/apache2/apache2.conf: No such file or directory And a lot more similar lines show up in the logs. Did you delete the /etc/apache2/ directory or its contents by hand? If yes, then that is the problem. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: apache2 (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/1918259 Title: package apache2 2.4.41-4ubuntu3.1 failed to install/upgrade: installed apache2 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1918259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918141] Re: nfs-server.service needs name resolution and network online
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 basically the same as the one shipped in Focal, so we will have to this there as well), it would be really good to come up with a reproducer that can ideally be run in a VM (lxd, multipass, virt-manager, it doesn't matter). I did a quick test here and fired up two LXDs VMs. I configured nfs- server in one of them, and placed the following in its /etc/exports: /testshare nfs-utils-bug1918141-focal-2.lxd(rw,sync,no_subtree_check) I verified that nfs-utils-bug1918141-focal-2.lxd can be resolved and is not in /etc/hosts, and then restarted the VM. It came back up right away, and the nfs-server service had been started successfully. I fiddled a bit with the systemd services, even created one fake service that just sleeps for a certain amount of time, but I guess that in a VM if network.target is up then you can just use the network right away. Anyway, if you have any ideas on how to reproduce this, I'm all ears. Otherwise, if it's really something hard to do in a VM, then we might just go ahead with the SRU and explain the situation. Thanks. -- 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 name resolution and network online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917718] Re: Can't auto login after upgrading to 2.3.1-3ubuntu4 on 20.10
Thanks for the bug report, Kevin. I followed your instructions on how to reproduce it, but failed. The auto-login feature is working in my pristine Groovy VM even after I fully upgrade the system and install sssd. What Lucas pointed above is indeed strange: you could be facing some unrelated issue (like DNS) that might be affecting how your system behaves. For example, it seems like there is some sort of LDAP-based authentication that you're trying to use, maybe? Other things that caught my attention in the logs: 1) I could not find any mention to sssd.service whatsoever in your journalctl.log. 2) You seem to be using a system that has been configured before. Based on the instructions you posted in the bug description explaining how to reproduce the issue, I was under the impression that the problem happened after a pristine installation of Ubuntu Groovy. Having said all that, I would like to reinforce Lucas's request and ask you to provide your sssd configuration file so that we can try to reproduce the issue here. Also, please try to mention everything that might affect the authentication process, like the use of LDAP servers, AD, etc. Because I could not reproduce the bug locally, I am marking it as Incomplete. When you provide the necessary information, feel free to mark the bug as New again. Thanks. ** Changed in: sssd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917718 Title: Can't auto login after upgrading to 2.3.1-3ubuntu4 on 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1917718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917336] Re: Mailman does not honour MAILMAN_USER on startup
Thanks for the bug report. This happens because of how systemd handles /var/run/. If you look at the directory, you will see that it is actually a symlink to /run/. This directory is populated on every boot. There are a few ways that packages can choose in order to create directories under this directory; mailman chooses to use a tmpfiles.d configuration file. If you look at /usr/lib/tmpfiles.d/mailman.conf you will see this: # path mode uid gid d /run/mailman 0755 list list d /run/lock/mailman 2775 root list In order to achieve what you want, you need to change the "uid" field in the first line. The recommended way to change this file is to actually create a copy of it under /etc/tmpfiles.d/, so that you don't change the original file from the package (which could get overwritten during an update). To summarize, your file /etc/tmpfiles.d/mailman.conf should look like: # path mode uid gid d /run/mailman 0755 www-data list d /run/lock/mailman 2775 root list I am closing this bug as Invalid because it is a local configuration question rather than a problem, but please let us know if the steps above don't work for you. Thanks! ** Changed in: mailman (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917336 Title: Mailman does not honour MAILMAN_USER on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1917336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877704] Re: File get-uid-gid.js is missing
Verification for Groovy: First, verifying that the bug manifests itself: # apt policy node-uid-number node-uid-number: Installed: 0.0.6-1 Candidate: 0.0.6-1 Version table: *** 0.0.6-1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status # npm install yarn -g # grep get-uid-gid .npm/_logs/*-debug.log 57 verbose stack Error: Cannot find module './get-uid-gid.js' 64 error Cannot find module './get-uid-gid.js' Now, installing the updated package from -proposed and verifying that the bug is fixed: # apt policy node-uid-number node-uid-number: Installed: 0.0.6-1ubuntu0.20.10.1 Candidate: 0.0.6-1ubuntu0.20.10.1 Version table: *** 0.0.6-1ubuntu0.20.10.1 500 500 http://archive.ubuntu.com/ubuntu groovy-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 0.0.6-1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages # npm install yarn -g > yarn@1.22.10 preinstall /usr/local/lib/node_modules/yarn > :; (node ./preinstall.js > /dev/null 2>&1 || true) /usr/local/bin/yarn -> /usr/local/lib/node_modules/yarn/bin/yarn.js /usr/local/bin/yarnpkg -> /usr/local/lib/node_modules/yarn/bin/yarn.js + yarn@1.22.10 updated 1 package in 1.731s # ls .npm/_logs/ # ls /usr/lib/nodejs/uid-number/get-uid-gid.js /usr/lib/nodejs/uid-number/get-uid-gid.js The bug has been fixed with the package from -proposed. This concludes the verification for Groovy. ** Tags removed: verification-needed verification-needed-focal verification-needed-groovy ** Tags added: verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877704 Title: File get-uid-gid.js is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/node-uid-number/+bug/1877704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877704] Re: File get-uid-gid.js is missing
Verification for Focal: First, verifying that the bug manifests itself: # apt policy node-uid-number node-uid-number: Installed: 0.0.6-1 Candidate: 0.0.6-1 Version table: *** 0.0.6-1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status # npm install yarn -g # grep get-uid-gid .npm/_logs/*-debug.log 57 verbose stack Error: Cannot find module './get-uid-gid.js' 64 error Cannot find module './get-uid-gid.js' Now, installing the updated package from -proposed and verifying that the bug is fixed: # apt policy node-uid-number node-uid-number: Installed: 0.0.6-1ubuntu0.20.04.1 Candidate: 0.0.6-1ubuntu0.20.04.1 Version table: *** 0.0.6-1ubuntu0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 0.0.6-1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages # npm install yarn -g > yarn@1.22.10 preinstall /usr/local/lib/node_modules/yarn > :; (node ./preinstall.js > /dev/null 2>&1 || true) /usr/local/bin/yarn -> /usr/local/lib/node_modules/yarn/bin/yarn.js /usr/local/bin/yarnpkg -> /usr/local/lib/node_modules/yarn/bin/yarn.js + yarn@1.22.10 updated 1 package in 1.731s # ls .npm/_logs/ # ls /usr/lib/nodejs/uid-number/get-uid-gid.js /usr/lib/nodejs/uid-number/get-uid-gid.js The bug has been fixed with the package from -proposed. This concludes the verification for Focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877704 Title: File get-uid-gid.js is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/node-uid-number/+bug/1877704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916715] Re: fails on install due to systemd-service/sysv-service mismatch and lack of mkdir
This is strange, indeed. The MP for the merge is: https://code.launchpad.net/~sergiodj/ubuntu/+source/python-rtslib- fb/+git/python-rtslib-fb/+merge/397174 As you can read there, I did check if the package installed/uninstalled correctly. Bryce also double-checked it. I don't know if the problem is that we forgot to check if the systemd service file was up or not, or something else. But then again, the error you posted happens right at the installation step, so we would have caught that. I'm puzzled, and I apologize for not having seen this before. Thanks for taking care of this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916715 Title: fails on install due to systemd-service/sysv-service mismatch and lack of mkdir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-rtslib-fb/+bug/1916715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916644] Re: package mysql-server-5.7 5.7.33-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for taking the time to write a report. As you noticed, this was caused by a local configuration issue. As such, I am marking this bug as Invalid. Feel free to reopen it and provide more information if you think it is a real bug. ** Changed in: mysql-5.7 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916644 Title: package mysql-server-5.7 5.7.33-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1916644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916562] Re: libnss-sss removes config when not being purged
Thanks for the report. I can indeed confirm the bug. I could also verify that the behaviour still happens as of Hirsute. I've subscribed the Ubuntu Server team to the bug; we will look into it as time permits. This does not seem to be an urgent issue, though, so it may take a while until it is resolved. ** Changed in: sssd (Ubuntu) Importance: Undecided => Medium ** Also affects: sssd (Ubuntu Hirsute) Importance: Medium Status: Triaged ** Also affects: sssd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: sssd (Ubuntu Focal) Status: New => Triaged ** Changed in: sssd (Ubuntu Focal) 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/1916562 Title: libnss-sss removes config when not being purged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1916562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
