[Bug 2070095] Re: apt_news.py download forced unsandboxed
# pro collect-logs [info] A new version is available: 32.3.1~24.04 Please run: sudo apt install ubuntu-pro-client to get the latest bug fixes and new features. # ls -hal /run/ubuntu-advantage/ total 8.0K drwxr-xr-x 3 root root 100 Jul 4 12:28 . drwxr-xr-x 36 root root 1.2K Jul 4 12:27 .. -rw-r--r-- 1 root root 399 Jul 3 16:00 aptnews.json -rw-r--r-- 1 root root 12 Jul 4 12:28 candidate-version drwxr-xr-x 2 root root 40 Jul 4 09:47 notices And after updating ubuntu-pro-client: # pro collect-logs # -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070095 Title: apt_news.py download forced unsandboxed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2070095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070095] Re: apt_news.py download forced unsandboxed
I now think this relates to ubuntu-advantage-tools and/or ubuntu pro- client. I do not have ubuntu-advantage-tools installed but I do have ubuntu-pro-client and I have directory /etc/ubuntu-advantage which contains uaclient.conf. ** Package changed: ubuntu => ubuntu-advantage-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070095 Title: apt_news.py download forced unsandboxed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2070095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070095] [NEW] apt_news.py download forced unsandboxed
Public bug reported: I am not sure which package this relates to, but after a recent upgrade from Ubuntu 22.04 to 24.04 LTS I have started seeing messages in syslog like this: 17:29:03 python3[89]: /usr/lib/python3/dist-packages/uaclient/apt_news.py:207: Warning: W:Download is performed unsandboxed as root as file '/run/ubuntu-advantage/aptnews.json' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) 17:29:03 python3[89]: acq.run() It seems to me that user _apt lacks write permission for anything in /run, hence the problem. I realise the script is getting round the problem by running unsandboxed instead but this message is ugly. What I have installed that might be related (I do not have ubuntu-advantage-tools): # dpkg-query --list|grep -E "^.i.*(news|-pro-|apt).*(amd64|all)" ii apt2.7.14build2 amd64commandline package manager ii apt-utils 2.7.14build2 amd64package management related utility programs ii libapt-pkg6.0t64:amd64 2.7.14build2 amd64package management runtime library ii motd-news-config 13ubuntu10 all Configuration for motd-news shipped in base-files ii python-apt-common 2.7.7ubuntu1 all Python interface to libapt-pkg (locales) ii python3-apt2.7.7ubuntu1 amd64Python 3 interface to libapt-pkg ii ubuntu-pro-client 32.3~24.04 amd64Management tools for Ubuntu Pro ii ubuntu-pro-client-l10n 32.3~24.04 amd64Translations for Ubuntu Pro Client ** Affects: 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/2070095 Title: apt_news.py download forced unsandboxed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2070095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069505] [NEW] package sa-compile 4.0.0-8ubuntu5 failed to install/upgrade: installed sa-compile package post-installation script subprocess returned error exit status 2
Public bug reported: bug on upgrading from 22.04 to 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: sa-compile 4.0.0-8ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-112.122-generic 5.15.152 Uname: Linux 5.15.0-112-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CloudBuildName: server CloudSerial: 20190813.1 Date: Sat Jun 15 16:18:15 2024 ErrorMessage: installed sa-compile package post-installation script subprocess returned error exit status 2 PackageArchitecture: all Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: spamassassin Title: package sa-compile 4.0.0-8ubuntu5 failed to install/upgrade: installed sa-compile package post-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to noble on 2024-06-15 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-23T12:30:10 ** Affects: spamassassin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cloud-image noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069505 Title: package sa-compile 4.0.0-8ubuntu5 failed to install/upgrade: installed sa-compile package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/2069505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056153] Re: Removing the systemd-resolved package breaks DNSSEC validation
This bug continues into Noble. I continue to add "options edns0 trust- ad" to /etc/resolv.conf after removing systemd-resolved, but it would be nice not having to do so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056153 Title: Removing the systemd-resolved package breaks DNSSEC validation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2056153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
Postfix already has a configuration page for SPF [0], albeit requiring a package from universe. So although removing the SPF snippet from Exim could be an option in the short-term, I do think in the long-term Ubuntu's SPF support for Exim should be somewhat equivalent to that of Postfix's. Adding a fragile snippet to a docs would come with the same caveats as including a fragile snippet in the stock Exim config, just with less culpability. Ultimately using Exim's native SPF facility, i.e. that of libspf2, is the right approach in my mind. [0] - https://help.ubuntu.com/community/Postfix/SPF -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
Option three would be to remove the spf section completely until a non- broken sustainable solution is implemented, especially if libspf2 is going to take some time to implement. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
Thank you, I would appreciate you reiterating the case for libspf2. Aside from the fact that this implementation is looking (recurrently) fragile, this Ubuntu delta, disabled by default, is probably not getting enough attention to spot bugs. This bug has been open for three months and only one other person said "me too". We can't say if this is because few people enable it, or whether a lot of people are yet to notice everything is "Received-SPF: none", but it's a concern in itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
It was floated before but it's worth raising again. What are the chances of bringing libspf2 to main and falling back into line with Debian? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
No, I was not invoking bash, I was using the code I quoted previously
and testing the scenarios at port 25.
An empty $sender_address variable would create a missing argument and
likely break spfquery.mail-spf-perl, I haven't tested that scenario yet.
$sender_host_address should always be present and sanitised by
definition.
condition = ${run{/usr/bin/spfquery.mail-spf-perl \
--ip $sender_host_address \
--scope mfrom \
--identity $sender_address} \
{no}{${if eq {$runrc}{1}{yes}{no
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056372
Title:
Enabling SPF checks with CHECK_RCPT_SPF doesn't work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
Good find, I am still running my ${quote:}-less version at the moment so
I was able to test the scenarios in that bug report.
All three of the following senders were correctly rejected as spf fail
by my server (example.com hard fails all senders in its spf record):
MAIL FROM: "$PWD"@example.com
MAIL FROM: "x --help "@example.com
MAIL FROM: le...@example.com
RCPT TO:
550-[SPF] is not allowed to send mail
550 from example.com.
So whatever the reason it was allowing an spf fail to pass back then, it
no longer appears to be the case now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056372
Title:
Enabling SPF checks with CHECK_RCPT_SPF doesn't work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
Thinking more about this, wouldn't invoking /bin/bash actually increase
the attack potential, by allowing for backticks and $() to execute via
user-supplied data?
Also, it's not clear to me that ${quote} escapes backticks or $().
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056372
Title:
Enabling SPF checks with CHECK_RCPT_SPF doesn't work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056443] Re: CHECK_RCPT_SPF SPF check fails if inbound IP address is IPv6
Closing this, as this will be fixed by bug #2056372 ** Changed in: exim4 (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/2056443 Title: CHECK_RCPT_SPF SPF check fails if inbound IP address is IPv6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
I agree, I also do not know the potential risks of removing ${quote:}
from tainted variables, so this needs further research before
implementation. Or we go with yours.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056372
Title:
Enabling SPF checks with CHECK_RCPT_SPF doesn't work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049977] Re: journalctl --follow --grep lists lines in wrong order
It was a problem in mantic, fixed in noble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049977 Title: journalctl --follow --grep lists lines in wrong order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2049977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
Hi Mitchell,
Your version works for me as well.
In the interim I have been successfully using the following
configuration. Would this be potentially useful, or are there issues
with removing ${quote:} from --ip and --identity?
condition = ${run{/usr/bin/spfquery.mail-spf-perl \
--ip $sender_host_address \
--scope mfrom \
--identity $sender_address} \
{no}{${if eq {$runrc}{1}{yes}{no
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056372
Title:
Enabling SPF checks with CHECK_RCPT_SPF doesn't work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067057] Re: Unattended-upgrades order of restart caused failure to bind address
Contents of unattended-upgrades log, to confirm unattended-upgrades initiated the updates: 2024-05-24 06:27:37,661 INFO Starting unattended upgrades script 2024-05-24 06:27:37,662 INFO Allowed origins are: o=Ubuntu,a=noble, o=Ubuntu,a=noble-security, o=UbuntuESMApps,a=noble-apps-security, o=UbuntuESM,a=noble-infra-security, o=Ubuntu,a=noble-updates, o=Ubuntu,a=noble-proposed, o=Ubuntu,a=noble-backports 2024-05-24 06:27:37,662 INFO Initial blacklist: 2024-05-24 06:27:37,662 INFO Initial whitelist (not strict): 2024-05-24 06:27:40,144 INFO Packages that will be upgraded: klibc-utils libklibc libssl3t64 openssl 2024-05-24 06:27:40,144 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2024-05-24 06:27:57,367 INFO All upgrades installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067057 Title: Unattended-upgrades order of restart caused failure to bind address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2067057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067057] [NEW] Unattended-upgrades order of restart caused failure to bind address
Public bug reported: This morning, nginx wan't working, so I checked the journal. It appears an overnight unattended-upgrades restarted a lot of services, including systemd-networkd and nginx. Logs pasted at the end, I am running Ubuntu 24.04. I bind nginx to specific IP addresses, because different daemons listen on different addresses. When nginx was brought back up, it failed because the requested IP address had not yet come back up. It would appear unattended-upgrades attempted to restart a lot of services at once, causing nginx to attempt to bind to an address which had not yet come back up. Could there be more careful ordering of execution to avoid such problems? May 24 06:27:54 alpha systemd[1]: Stopping packagekit.service - PackageKit Daemon...May 24 06:27:54 alpha systemd[1]: packagekit.service: Deactivated successfully. May 24 06:27:54 alpha systemd[1]: Stopped packagekit.service - PackageKit Daemon. May 24 06:27:54 alpha systemd[1]: exim4.service: Deactivated successfully. May 24 06:27:54 alpha systemd[1]: Stopped exim4.service - exim Mail Transport Agent. May 24 06:27:54 alpha systemd[1]: exim4.service: Consumed 15.241s CPU time, 26.4M memory peak, 0B memory swap peak. May 24 06:27:54 alpha systemd[1]: Starting exim4.service - exim Mail Transport Agent... May 24 06:27:54 alpha systemd[1]: Starting packagekit.service - PackageKit Daemon... May 24 06:27:54 alpha systemd[1]: Stopping php8.3-fpm.service - The PHP 8.3 FastCGI Process Manager... May 24 06:27:54 alpha systemd[1]: Stopping ssh.service - OpenBSD Secure Shell server... May 24 06:27:54 alpha sshd[1427]: Received signal 15; terminating. May 24 06:27:54 alpha systemd-journald[365]: Journal stopped May 24 06:27:55 alpha systemd[1]: Stopping systemd-journald.service - Journal Service... May 24 06:27:55 alpha systemd-journald[365]: Received SIGTERM from PID 1 (systemd). May 24 06:27:55 alpha systemd[1]: netplan-ovs-cleanup.service - OpenVSwitch configuration for cleanup was skipped because of an unmet condition check (ConditionFileIsExecutable=/usr/bin/ovs-vsctl). May 24 06:27:55 alpha systemd[1]: systemd-networkd-wait-online.service: Deactivated successfully. May 24 06:27:55 alpha systemd[1]: Stopped systemd-networkd-wait-online.service - Wait for Network to be Configured. May 24 06:27:55 alpha systemd[1]: Stopping systemd-networkd-wait-online.service - Wait for Network to be Configured... May 24 06:27:55 alpha systemd[1]: Stopping systemd-networkd.service - Network Configuration... May 24 06:27:55 alpha systemd[1]: ssh.service: Deactivated successfully. May 24 06:27:55 alpha systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. May 24 06:27:55 alpha systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... May 24 06:27:55 alpha systemd[1]: nginx.service: Deactivated successfully. May 24 06:27:55 alpha systemd[1]: Stopped nginx.service - A high performance web server and a reverse proxy server. May 24 06:27:55 alpha systemd[1]: nginx.service: Consumed 6.168s CPU time, 21.6M memory peak, 0B memory swap peak. May 24 06:27:55 alpha systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server... May 24 06:27:55 alpha systemd[1]: Stopping systemd-timesyncd.service - Network Time Synchronization... May 24 06:27:55 alpha systemd[1]: systemd-journald.service: Deactivated successfully. May 24 06:27:55 alpha systemd[1]: Stopped systemd-journald.service - Journal Service. May 24 06:27:55 alpha systemd[1]: systemd-journald.service: Consumed 49.437s CPU time, 173.6M memory peak, 0B memory swap peak. May 24 06:27:55 alpha systemd[1]: systemd-networkd.service: Deactivated successfully. May 24 06:27:55 alpha systemd[1]: Stopped systemd-networkd.service - Network Configuration. May 24 06:27:55 alpha systemd[1]: systemd-networkd.service: Consumed 3.016s CPU time, 3.6M memory peak, 0B memory swap peak. May 24 06:27:55 alpha systemd[1]: systemd-timesyncd.service: Deactivated successfully. May 24 06:27:55 alpha systemd[1]: Stopped systemd-timesyncd.service - Network Time Synchronization. May 24 06:27:55 alpha systemd[1]: systemd-timesyncd.service: Consumed 1.742s CPU time, 2.2M memory peak, 0B memory swap peak. May 24 06:27:55 alpha systemd[1]: Starting systemd-journald.service - Journal Service... May 24 06:27:55 alpha systemd[1]: Starting systemd-networkd.service - Network Configuration... May 24 06:27:55 alpha systemd-journald[224525]: Collecting audit messages is disabled. May 24 06:27:55 alpha systemd[1]: Starting systemd-timesyncd.service - Network Time Synchronization... May 24 06:27:55 alpha systemd[1]: Started ssh.service - OpenBSD Secure Shell server. May 24 06:27:55 alpha systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE May 24 06:27:55 alpha systemd[1]: nginx.service: Failed with result 'exit-code'. May 24 06:27:55 alpha systemd-journald[224525]: Journal started May 24 06:27:55 alpha systemd-journald[224525]: System Journal
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
Re-marking as new since I've supplied all requested information. ** Changed in: exim4 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
(and comment #6) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
No, you should be seeing a header. Are the steps you followed the same as that which I wrote in comment #5 of this report? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
No errors in /var/log/exim4/mainlog, just normal mail flow logs. I suspect some sort of error was introduced in the code for the #1998678 fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
Possibly related to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1998678 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
It was a clean install of Noble, for some reason the spf check always returns "none". It is very easily reproducible, as per my comment #5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
Still an issue in noble / 24.04. "Received-SPF: none" is reported in the headers of received mail for senders known to have an spf record configured. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
Also, this should not be marked as "incomplete" as I have supplied all the required information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
I get the correct result when running spfquery.mail-spf-perl manually. $ /usr/bin/spfquery.mail-spf-perl --ip 40.92.113.65 --scope mfrom --identity exam...@outlook.com pass outlook.com: Sender is authorized to use 'exam...@outlook.com' in 'mfrom' identity (mechanism 'include:spf.protection.outlook.com' matched) outlook.com: Sender is authorized to use 'exam...@outlook.com' in 'mfrom' identity (mechanism 'include:spf.protection.outlook.com' matched) Received-SPF: pass (outlook.com: Sender is authorized to use 'exam...@outlook.com' in 'mfrom' identity (mechanism 'include:spf.protection.outlook.com' matched)) receiver=alpha.cress.org.uk; identity=mailfrom; envelope-from="exam...@outlook.com"; client-ip=40.92.113.65 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
According to the exim4 changelog, the spf logic was modified in Aug 2023. exim4 (4.96-17ubuntu1) mantic; urgency=medium * Merge with Debian unstable (LP: #2030098). Remaining changes: - Disable external SPF support to avoid Build-Depends on libspf2-dev (only available in universe). SPF can still be implemented via spf-tools-perl, as documented in exim4.conf.template. This reverts Vcs-Git commit 494f1fe, first released in 4.95~RC0-1. (LP #1952738) + d/control: drop Build-Depends on libspf2-dev. + d/EDITME.exim4-heavy.diff: disable support for libspf2. + d/d/c/a/30_exim4-config_check_rcpt: restore SPF logic based on spfquery.mail-spf-perl from spf-tools-perl, but without the previously supported helo detection. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
I'm using exim4-daemon-heavy. $ apt list --installed | grep exim4 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. exim4-base/mantic-updates,mantic-security,now 4.96-17ubuntu2.2 amd64 [installed,automatic] exim4-config/mantic-updates,mantic-security,now 4.96-17ubuntu2.2 all [installed,automatic] exim4-daemon-heavy/mantic-updates,mantic-security,now 4.96-17ubuntu2.2 amd64 [installed,automatic] exim4/mantic-updates,mantic-security,now 4.96-17ubuntu2.2 all [installed] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
Also: `update-exim4.conf` and restart exim before sending mail to yourself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
exim4.conf.template is completely unmodified from stock mantic. Bug can be replicated by: 1. Installing mantic 2. Installing exim4 and spf-tools-perl 3. `dpkg-reconfigure exim4-config` and make it accept mail 4. Adding CHECK_RCPT_SPF = true to /etc/exim4/exim4.conf.localmacros 5. Sending yourself an email from Gmail or Outlook and checking the spf header That's all I did. ** Attachment added: "exim4.conf.localmacros" https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+attachment/5755338/+files/exim4.conf.localmacros -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056443] Re: CHECK_RCPT_SPF SPF check fails if inbound IP address is IPv6
Quite possibly related, although the way the error manifests is different. If the other bug is fixed, then it's very possible this one will be too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056443 Title: CHECK_RCPT_SPF SPF check fails if inbound IP address is IPv6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
Hi Mitchell, I am setting CHECK_RCPT_SPF = true in /etc/exim4/exim4.conf.localmacros where local macros are typically set. I have run `update-exim4.conf` and `systemctl restart exim4`. Then I send myself an email from an outlook.com account, which has SPF enabled, and the headers report: Received-SPF: none I am expecting to see: Received-SPF: pass -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
Note: this bug relates to inbound IPv4 addresses. IPv6 addresses are affected by a separate bug: #2056443 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056443] [NEW] CHECK_RCPT_SPF SPF check fails if inbound IP address is IPv6
Public bug reported: On mantic, when CHECK_RCPT_SPF = true and spf-tools-perl is installed, Exim4 logs an error and fails the SPF check if the inbound IP address is IPv6: 2024-03-07 11:58:35 H=mail-yb1-xb2c.google.com [2607:f8b0:4864:20::b2c] Warning: Unexpected error in SPF check. ** Affects: exim4 (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/2056443 Title: CHECK_RCPT_SPF SPF check fails if inbound IP address is IPv6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] [NEW] Enabling SPF checks with CHECK_RCPT_SPF doesn't work
Public bug reported: As I understand it, enabling SPF validation in Exim4 simply requires setting CHECK_RCPT_SPF to true and installing the spf-tools-perl package. However, in mantic, every email has this header, regardless of whether the sender's domain has an SPF TXT record set: Received-SPF: none ** Affects: exim4 (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/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056153] [NEW] Removing the systemd-resolved package breaks DNSSEC validation
Public bug reported: Removing the systemd-resolved package breaks glibc DNSSEC validation, because it removes an existing line from the new /etc/resolv.conf file. This line should be retained so that packages like Exim can continue to use the AD bit after systemd-resolved is removed. ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad search vcn.oraclevcn.com ubuntu@instance:~$ sudo apt remove systemd-resolved ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 169.254.169.254 search vcn.oraclevcn.com ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056153 Title: Removing the systemd-resolved package breaks DNSSEC validation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2056153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823171] Re: systemd-resolve hides DS records in explicit queries
DNSSEC isn't required to query a DS record. The reason your query succeeded after you enabled DNSSEC is because systemd-resolved caches it internally as a result of the DNSSEC lookup. Once the DS query is cached, the bug will not manifest. Another way to cache it is: ubuntu@server:~$ dig ripe.net ds @127.0.0.53 +short ubuntu@server:~$ dig ripe.net ds @127.0.0.54 +short 10186 13 2 BC15C85E16FE7C651EAAFCEE3B1F1C956217A5B70A536BFEF38C24A9 AB7B9A3F ubuntu@server:~$ dig ripe.net ds @127.0.0.53 +short 10186 13 2 BC15C85E16FE7C651EAAFCEE3B1F1C956217A5B70A536BFEF38C24A9 AB7B9A3F -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823171 Title: systemd-resolve hides DS records in explicit queries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977764] [NEW] kernel modules "zstd" and "z3fold" missing.
Public bug reported: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: arm64-image jammy raspi-image z3fold zstd zswap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1977764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974178] Re: Missing vhost_vsock kernel module in 5.15.0
"sudo apt install linux-modules-extra-raspi" worked and installed the missing module. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974178 Title: Missing vhost_vsock kernel module in 5.15.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1974178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974178] [NEW] Missing vhost_vsock kernel module in 5.15.0
Public bug reported: Hey All, I am new to the container, lxc, lxd stuff and I am at the end of my knowledge. I have a fresh setup with a Raspberry PI 4 installed with Ubuntu 22.04 arm64. So far everything works fine for containers but I can't get any vm to launch. > ~ lxc launch images:ubuntu/focal ubuntu --vm > > Creating ubuntu > Error: Failed instance creation: Failed creating instance record: Instance > type "virtual-machine" is not supported on this server: vhost_vsock kernel > module not loaded Seems like I am missing a kernel module, but I was not able to find or load it. Already googled for it but was not able to find any matching problem with solution. Additional Information: > ~ uname -r > 5.15.0-1005-raspi > ~ dpkg -l | grep linux-image > ii linux-image-5.15.0-1005-raspi 5.15.0-1005.5 > arm64Linux kernel image for version 5.15.0 on ARMv8 SMP > ~ modprobe vhost_vsock > modprobe: FATAL: Module vhost_vsock not found in directory > /lib/modules/5.15.0-1005-raspi > ~ lsmod | grep vsock ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974178 Title: Missing vhost_vsock kernel module in 5.15.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1974178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618041] Re: Cannot login to Ubuntu One Single Sign-On Account to install Snaps
*** This bug is a duplicate of bug 1616943 *** https://bugs.launchpad.net/bugs/1616943 same here on brand new 20.04 LTS running in VM on HyoerV SSO and Ubuntu One accounts work fine on webs, but Livepatch setup lets me enter SSO initally, then prompts for local admin, before coming back to SSO sign-in screen with incorrect email/password -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618041 Title: Cannot login to Ubuntu One Single Sign-On Account to install Snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1618041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946833] Re: Merge bind9 from Debian unstable for 22.04
It would be ideal if 9.18 could be included before the feature freeze. Any news? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946833 Title: Merge bind9 from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1946833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871306] Re: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf)
on 22.04 Daily Live from today everything works out of the Box on ASUS C200 with Bay Trail -- 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/1871306 Title: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871306] Re: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf)
Now I changed with my main Setup to 21.10 and after setting snd_intel_dspcfg.dsp_driver=2 the Sound is Pitched down and too slow. When I try to install firmware-sof-signed dpkg terminates with the error saying that the sof files are already installed by linux-firmware, but the required file intel/sof-tplg/sof-byt-max98090.tplg is not included in linux-firmware, or firmware-sof-signed. After Installing https://github.com/thesofproject/sof-bin/ directly from github sound works perfectly without snd_intel_dspcfg.dsp_driver=2. So in 22.04 this should be included by default in linux-firmware. -- 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/1871306 Title: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946909] Re: Merge unbound from Debian unstable for 22.04
Please ensure that whatever happens, Unbound on Ubuntu continues to be compiled with the nghttp2 library. Unbound on Debian is currently not compiled with nghttp2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946909 Title: Merge unbound from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1946909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871306] Re: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf)
In my readings without the snd_intel_dspcfg.dsp_driver=2 the system uses sof mode which requires the package firmware-sof-signed. But I can not do any testing about that from live system so I will do when I changed permanent to 21.10 and provide the results. -- 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/1871306 Title: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871306] Re: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf)
** Attachment added: "alsainfo-inteldsp2.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+attachment/5534257/+files/alsainfo-inteldsp2.txt -- 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/1871306 Title: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871306] Re: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf)
** Attachment added: "dmesg-inteldsp2.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+attachment/5534256/+files/dmesg-inteldsp2.txt -- 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/1871306 Title: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871306] Re: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf)
Wow this solves the problem. Thanks for your fast and competent help. For interest I will provide dmesg and alsainfo from 21.10 with dsp2 -- 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/1871306 Title: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871306] Re: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf)
** Attachment added: "dmesg.21.04.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+attachment/5534213/+files/dmesg.21.04.txt -- 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/1871306 Title: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871306] Re: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf)
** Attachment added: "dmesg.21.10.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+attachment/5534214/+files/dmesg.21.10.txt -- 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/1871306 Title: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871306] Re: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf)
Hey, thanks for your fast reply. When I do dmesg | grep 'journal -b0' there is no result, or did I get something wrong? -- 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/1871306 Title: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871306] Re: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf)
Issue was fixed on Asus Chromebook C200 with Ubuntu 21.04. But on Ubuntu 21.10 the Card is not detected anymore. Alsainfo 20.04:https://pastebin.com/raw/wXsT6w1r Alsainfo 21.10 https://pastebin.com/raw/SWZNJ4AT -- 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/1871306 Title: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871306] Re: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf)
Issue has been fixed with 21.04 out of the Box, but is present again on 21.10. Chromebook C200. -- 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/1871306 Title: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782709] Re: Updating systemd kills network on bionic
I changed my networking setup to use netplan and the problem disappeared. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782709 Title: Updating systemd kills network on bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927877] Re: DoH support is disabled
The Debian MR has still not been actioned. Can we now consider enabling DoH support in Ubuntu's Unbound package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927877 Title: DoH support is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1927877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930150] [NEW] package libpython3.9-minimal 3.9.5-1+focal1 failed to install/upgrade: trying to overwrite '/usr/lib/python3.9/typing.py', which is also in package libpython3.9-stdlib:amd64 3.9.5
Public bug reported: This was encountered during an automated install of updates this morning. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpython3.9-minimal 3.9.5-1+focal1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 30 07:04:26 2021 DuplicateSignature: package:libpython3.9-minimal:3.9.5-1+focal1 Unpacking libpython3.9-stdlib:amd64 (3.9.5-3~20.04.1) over (3.9.5-1+focal1) ... dpkg: error processing archive /tmp/apt-dpkg-install-P4IDTX/4-libpython3.9-stdlib_3.9.5-3~20.04.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3.9/test/ann_module.py', which is also in package libpython3.9-testsuite 3.9.5-1+focal1 ErrorMessage: trying to overwrite '/usr/lib/python3.9/typing.py', which is also in package libpython3.9-stdlib:amd64 3.9.5-1+focal1 InstallationDate: Installed on 2020-07-05 (328 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: python3.9 Title: package libpython3.9-minimal 3.9.5-1+focal1 failed to install/upgrade: trying to overwrite '/usr/lib/python3.9/typing.py', which is also in package libpython3.9-stdlib:amd64 3.9.5-1+focal1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python3.9 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-conflict third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930150 Title: package libpython3.9-minimal 3.9.5-1+focal1 failed to install/upgrade: trying to overwrite '/usr/lib/python3.9/typing.py', which is also in package libpython3.9-stdlib:amd64 3.9.5-1+focal1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.9/+bug/1930150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927877] Re: DoH support is disabled
I would support this, DNS-over-HTTPS is increasing in usage and its omission is frustrating. I had to compile from source on Hirsute to enable it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927877 Title: DoH support is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1927877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927877] Re: DoH support is disabled
Thanks, I mostly copied the bug report from the Debian package. Is there someone here that can nudge the package managers at Debian? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927877 Title: DoH support is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1927877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927877] [NEW] DoH support is disabled
Public bug reported: NLnetLabs has added DNS-over-HTTPS support to Unbound as of release 1.12.0. The current Ubuntu package delivering this release however has no DoH support. For DoH to work, Unbound simply would need to be compiled with the nghttp2 library. ** Affects: unbound (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/1927877 Title: DoH support is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1927877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923264] Re: request-tracker4 is incompatible with mysql-server-8.0
** Bug watch added: Debian Bug tracker #986707 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986707 ** Also affects: request-tracker4 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986707 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/1923264 Title: request-tracker4 is incompatible with mysql-server-8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/request-tracker4/+bug/1923264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
my problem is I think likely better covered by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1803391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
TTFN: To add to (and correct) my earlier comments: after the updating shown there, the machine had to be rebooted manually. Checking /var/log/apt/term.log it appears that the upgrade did complete successfully: Log started: 2021-01-07 13:28:19 (Reading database ... 151099 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.43_i386.deb ... Unpacking libnss-systemd:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.43_i386.deb ... Unpacking libpam-systemd:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../systemd_237-3ubuntu10.43_i386.deb ... Unpacking systemd (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.43_i386.deb ... Unpacking libsystemd0:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Setting up libsystemd0:i386 (237-3ubuntu10.43) ... Setting up systemd (237-3ubuntu10.43) ... Setting up libnss-systemd:i386 (237-3ubuntu10.43) ... Setting up libpam-systemd:i386 (237-3ubuntu10.43) ... Processing triggers for libc-bin (2.27-3ubuntu1.4) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for dbus (1.12.2-1ubuntu1.2) ... Processing triggers for ureadahead (0.100.0-21) ... Log ended: 2021-01-07 13:29:10 ... this even though the (ssh) interface died at the point where systemd was being set up. The system now runs systemd 237-3ubuntu10.43. But based on past experience I think the same thing will happen the next time there is a version upgrade of systemd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1803391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
I have this problem with Ubuntu 18.04 system set up with 'encrypted LVM' (standard Ubuntu recipe as per the alternate installer). Whenever there is systemd upgrade it hangs (whole machine crashes - other logins not possible) and has to be manually rebooted (which is not ideal as the machine is 1500 miles away). Note the installed version of systemd seems to be 237-3ubuntu10.42, obviously I am unable to update it. I have another machine also Ubuntu 18.04 system set up with 'encrypted LVM' which has systemd 237-3ubuntu10.43 and does not have this problem. Latest instance of this problem: # apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 3,414 kB of archives. After this operation, 7,168 B of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libnss-systemd i386 237-3ubuntu10.43 [111 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libpam-systemd i386 237-3ubuntu10.43 [114 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 systemd i386 237-3ubuntu10.43 [2,964 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libsystemd0 i386 237-3ubuntu10.43 [225 kB] Fetched 3,414 kB in 1s (3,309 kB/s) (Reading database ... 151099 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.43_i386.deb ... Unpacking libnss-systemd:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.43_i386.deb ... Unpacking libpam-systemd:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../systemd_237-3ubuntu10.43_i386.deb ... Unpacking systemd (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.43_i386.deb ... Unpacking libsystemd0:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Setting up libsystemd0:i386 (237-3ubuntu10.43) ... Setting up systemd (237-3ubuntu10.43) ... [system dies] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1803391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903914] [NEW] Launching Oracle Sql Developer crashes due to openjdk
Public bug reported: Oracle SQL Developer Copyright (c) 2005, 2020, Oracle and/or its affiliates. All rights reserved. # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f7dbe01443a, pid=47548, tid=47630 # # JRE version: OpenJDK Runtime Environment (11.0.9+11) (build 11.0.9+11-Ubuntu-0ubuntu1.20.04) # Java VM: OpenJDK 64-Bit Server VM (11.0.9+11-Ubuntu-0ubuntu1.20.04, mixed mode, tiered, compressed oops, g1 gc, linux-amd64) # Problematic frame: # V [libjvm.so+0x8ae43a] # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /home/dominic/Downloads/sqldeveloper/sqldeveloper/bin/core.47548) # ** Affects: openjdk-lts (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Launching Oracle Sql Developer crash due to openjdk + Launching Oracle Sql Developer crashes due to openjdk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903914 Title: Launching Oracle Sql Developer crashes due to openjdk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1903914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902401] [NEW] touchpad not working
Public bug reported: Immediately after installing ubuntu 20.04 LTS on my new laptop from the default Windows 10 in S installation, my touchpad on my Lenovo IdeaPad 3 15IIL05 stopped working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dominic1211 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 22:25:25 2020 InstallationDate: Installed on 2020-11-01 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b6d9 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=facc9b9f-0d1e-408b-b048-4e9e209c09b3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN40WW:bd08/10/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1902401/+attachment/5429900/+files/devices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902401 Title: touchpad not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Affected by this also. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892569] [NEW] Font scaling not working correctly 20.04
Public bug reported: During log in screen and after all text on desktop is enlarged. (no accessibility settings are turned on) During log in, text scaling can be reset by turning on and off the text scaling accessibility option, however scaling after login is still messed up. After log in, manual reset of font scaling factor in gnome-tweak software is needed. Settings are not saved after reboot. ** Affects: gnome-shell (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/1892569 Title: Font scaling not working correctly 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875950] Re: rsyslog log files failing to rotate
VM reinstalled, logs are rotating now. ** Changed in: logrotate (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/1875950 Title: rsyslog log files failing to rotate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1875950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875950] Re: rsyslog log files failing to rotate
My mistake, error does not appear with: sudo logrotate -d /etc/logrotate.conf For some reason my logs are not being rotated though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875950 Title: rsyslog log files failing to rotate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1875950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875950] [NEW] rsyslog log files failing to rotate
Public bug reported: In focal, /etc/logrotate.conf contains: su root adm logrotate does not rotate files in /var/log: error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. Parent directory permissions: drwxrwxr-x 9 root syslog 4096 Apr 29 17:17 log ** Affects: logrotate (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/1875950 Title: rsyslog log files failing to rotate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1875950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875495] [NEW] Additional notifications that there are updates available to install appear on screen even if previous notifications have not been dismissed,
Public bug reported: Having left my computer logged in but locked for a few days, I came back to it to find 9 dialog boxes notifying me that there are new updates to install. I would have expected a new dialog to only appear if there is not already a dialog present on the screen, otherwise a lot of these dialogs could build up. Ubuntu Release Info: Description:Ubuntu 18.04.4 LTS Release:18.04 notify-osd version: 0.9.35+16.04.20160415-0ubuntu2 A screenshot showing the 9 dialogs is attached. These all originally appeared on top of each other in the centre of the screen, but I moved them to see how many there were. I think this is actually a bug in either the Software or Software Updater programs, but running `ubuntu-bug -w` and clicking the dialog showed notify-osd as the program responsible for the window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: notify-osd 0.9.35+16.04.20160415-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.21+ x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Apr 27 21:08:25 2020 DesktopSession: 'ubuntu' ExecutablePath: /usr/lib/x86_64-linux-gnu/notify-osd GtkTheme: 'Ambiance' IconTheme: 'ubuntu-mono-dark' InstallationDate: Installed on 2020-02-07 (80 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.21+ root=UUID=97111647-8898-45cb-94b2-704f31e37b9c ro quiet splash vt.handoff=1 RelatedPackageVersions: xserver-xorg N/A libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 libdrm2 2.4.99-1ubuntu1~18.04.2 xserver-xorg-video-intel N/A xserver-xorg-video-ati N/A SourcePackage: notify-osd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2901 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2901:bd10/16/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-IGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: notify-osd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "A screenshot showing the 9 dialogs." https://bugs.launchpad.net/bugs/1875495/+attachment/5362034/+files/Selection_005.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875495 Title: Additional notifications that there are updates available to install appear on screen even if previous notifications have not been dismissed, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1875495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853585] Re: Intel graphics card not detected and reverts to llvmpipe
** Summary changed: - Intel graphics card not detected, reverts to llvmpipe + Intel graphics card not detected and reverts to llvmpipe ** Description changed: [Impact] Ubuntu 18.04 install (also seen on 16) is unable to detect integrated Intel graphics card (Intel Iris Plus). Using a Dell XPS 13 2-in-1 7390 the machine is unable to detect attached monitors, change resolutions, or adjust brightness. [Information] - There is a dual boot Windows 10 partition, which can access the integrated graphics card without issue and connects to attached monitors on boot. + There is a dual boot Windows 10 partition, which can access the integrated graphics card without issue and connects to attached monitors on boot. Reinstallation following destruction of the W10 partition reveals the issue is unaffected by this duality. $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 % uname -o 4.15.0-70-generic $ apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 Version table: *** 2:2.99.917+git20171229-1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ lspci -v 00:02.0 VGA compatible controller: Intel Corporation Device 8a52 (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device 08b0 Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at 603d00 (64-bit, non-prefetchable) [size=16M] Memory at 40 (64-bit, prefetchable) [size=256M] I/O ports at 4000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: System Settings -> Details: Graphics llvmpipe (LLVM 8.0, 256 bits) [Attempted Fix] $ sudo apt-get purge nux-tools Fix for #1767468 /etc/X11/Xsession.d/50_check_unity_support is not present. No changes observed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853585 Title: Intel graphics card not detected and reverts to llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853585] [NEW] Intel graphics card not detected, reverts to llvmpipe
Public bug reported: [Impact] Ubuntu 18.04 install (also seen on 16) is unable to detect integrated Intel graphics card (Intel Iris Plus). Using a Dell XPS 13 2-in-1 7390 the machine is unable to detect attached monitors, change resolutions, or adjust brightness. [Information] There is a dual boot Windows 10 partition, which can access the integrated graphics card without issue and connects to attached monitors on boot. $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 % uname -o 4.15.0-70-generic $ apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 Version table: *** 2:2.99.917+git20171229-1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ lspci -v 00:02.0 VGA compatible controller: Intel Corporation Device 8a52 (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device 08b0 Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at 603d00 (64-bit, non-prefetchable) [size=16M] Memory at 40 (64-bit, prefetchable) [size=256M] I/O ports at 4000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: System Settings -> Details: Graphics llvmpipe (LLVM 8.0, 256 bits) [Attempted Fix] $ sudo apt-get purge nux-tools Fix for #1767468 /etc/X11/Xsession.d/50_check_unity_support is not present. No changes observed. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Description changed: + [Impact] + Ubuntu install is unable to detect integrated Intel graphics card (Intel Iris Plus). Using a Dell XPS 13 2-in-1 7390 the machine is unable to detect attached monitors, change resolutions, or adjust brightness. + + [Information] + There is a dual boot Windows 10 partition, which can access the integrated graphics card without issue and connects to attached monitors on boot. + $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 % uname -o 4.15.0-70-generic $ apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: - Installed: 2:2.99.917+git20171229-1 - Candidate: 2:2.99.917+git20171229-1 - Version table: - *** 2:2.99.917+git20171229-1 500 - 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 2:2.99.917+git20171229-1 + Candidate: 2:2.99.917+git20171229-1 + Version table: + *** 2:2.99.917+git20171229-1 500 + 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + 100 /var/lib/dpkg/status $ lspci -v 00:02.0 VGA compatible controller: Intel Corporation Device 8a52 (rev 07) (prog-if 00 [VGA controller]) - Subsystem: Dell Device 08b0 - Flags: bus master, fast devsel, latency 0, IRQ 255 - Memory at 603d00 (64-bit, non-prefetchable) [size=16M] - Memory at 40 (64-bit, prefetchable) [size=256M] - I/O ports at 4000 [size=64] - [virtual] Expansion ROM at 000c [disabled] [size=128K] - Capabilities: - + Subsystem: Dell Device 08b0 + Flags: bus master, fast devsel, latency 0, IRQ 255 + Memory at 603d00 (64-bit, non-prefetchable) [size=16M] + Memory at 40 (64-bit, prefetchable) [size=256M] + I/O ports at 4000 [size=64] + [virtual] Expansion ROM at 000c [disabled] [size=128K] + Capabilities: System Settings -> Details: Graphics llvmpipe (LLVM 8.0, 256 bits) - Attempted fix: - $ sudo apt-get purge nux-tools + [Attempted Fix] + $ sudo apt-get purge nux-tools Fix for #1767468 - /etc/X11/Xsession.d/50_check_unity_support is not present. + /etc/X11/Xsession.d/50_check_unity_support is not present. No changes observed. ** Description changed: [Impact] - Ubuntu install is unable to detect integrated Intel graphics card (Intel Iris Plus). Using a Dell XPS 13 2-in-1 7390 the machine is unable to detect attached monitors, change resolutions, or adjust brightness. + Ubuntu 18.04 install (also seen on 16) is unable to detect integrated Intel graphics card (Intel Iris Plus). Using a Dell XPS 13 2-in-1 7390 the machine is unable to detect attached monitors, change resolutions, or adjust brightness. [Information] - There is a dual boot Windows 10 partition, which can access the integrated graphics card without issue and connects to attached monitors on boot. + There is a dual boot Windows 10 partition, which can access the integrated graphics card without issue and connects to attached monitors on boot. $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 % uname -o 4.15.0-70-generic $ apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 Version table: *** 2:2.99.917+git20171229-1 500 500 http://gb.archive.ubuntu.com/ubuntu
[Bug 1853585] Re: Intel graphics card not detected, reverts to llvmpipe
Related bug: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610 Possible duplicate, but unclear: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1772366 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853585 Title: Intel graphics card not detected, reverts to llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767468] Re: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration
*** This bug is a duplicate of bug 1768610 *** https://bugs.launchpad.net/bugs/1768610 I have witnessed a _related_ issue but it does not appear to be precisely the same problem. https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853585 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767468 Title: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1767468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853466] [NEW] I have installed the xserver-xorg-video-intel package but cannot detect monitor
Public bug reported: The monitor U2414H is not detected by Ubuntu, the graphics card displayed in settings is llvmpipe (LLVM 8.0, 256 bits). I believe it should be "Intel Iris Plus Graphics", which is what shows up in Windows Device Manager (my device is set up to dual boot). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 21 15:03:21 2019 DistUpgraded: SystemError: E:Setting in Stop via TCSAFLUSH for stdin failed! - tcsetattr (5: Input/output error), W:Operation was interrupted before it could finish DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8042, 4.15.0-70-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-70-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08b0] InstallationDate: Installed on 2019-11-15 (6 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=4540fdd6-b986-43c5-99ec-e2baa34ca219 ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-11-19 (2 days ago) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Nov 21 15:01:07 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853466 Title: I have installed the xserver-xorg-video-intel package but cannot detect monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1853466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849298] Re: unattended-upgrade is checking o=UbuntuESM, a=eoan-security when disabled in config
I just realised it's enabled by /etc/apt/apt.conf.d/51ubuntu-advantage- esm. Closing bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849298 Title: unattended-upgrade is checking o=UbuntuESM,a=eoan-security when disabled in config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1849298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849298] Re: unattended-upgrade is checking o=UbuntuESM, a=eoan-security when disabled in config
Not sure I can close the bug. Nevertheless it's confusing to have this configuration in two places. Maybe deserves a review. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849298 Title: unattended-upgrade is checking o=UbuntuESM,a=eoan-security when disabled in config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1849298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849298] [NEW] unattended-upgrade is checking o=UbuntuESM, a=eoan-security when disabled in config
Public bug reported:
My /etc/apt/apt.conf.d/50unattended-upgrades file looks like this:
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
// "${distro_id}ESM:${distro_codename}";
// "${distro_id}ESM:${distro_codename}-security";
"${distro_id}:${distro_codename}-updates";
"${distro_id}:${distro_codename}-proposed";
"${distro_id}:${distro_codename}-backports";
};
Nevertheless, the logs show that o=UbuntuESM,a=eoan-security is allowed
for updates despite not being enabled in config:
2019-10-22 08:10:46,075 INFO Initial blacklist :
2019-10-22 08:10:46,077 INFO Initial whitelist:
2019-10-22 08:10:46,077 INFO Starting unattended upgrades script
2019-10-22 08:10:46,077 INFO Allowed origins are: o=Ubuntu,a=eoan,
o=Ubuntu,a=eoan-security, o=Ubuntu,a=eoan-updates, o=Ubuntu,a=eoan-proposed,
o=Ubuntu,a=eoan-backports, o=UbuntuESM,a=eoan-security
** Affects: unattended-upgrades (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/1849298
Title:
unattended-upgrade is checking o=UbuntuESM,a=eoan-security when
disabled in config
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1849298/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822351] Re: Nautilus does not open after updating to 19.04
Also in case that helps, I experience the same bug. In addition, #2 did not work for me. Immediately after executing "tracker reset -e" on a shell, nautilus shows instantly after a click, but the problem comes back at the next reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822351 Title: Nautilus does not open after updating to 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1822351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785573] Re: incrontab changes its contents, and fails, under certain conditions
These points are not relevant here and are old: some of them are fixed in version 0.12. If the OP still has concerns they should be taken up with the incron maintainer at https://github.com/ar-/incron. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785573 Title: incrontab changes its contents, and fails, under certain conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/incron/+bug/1785573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819977] Re: razor2 had unknown error during get_server_info
Great workaround tip thanks @strredwolf. You can use either 208.83.137.117 or 208.83.137.118, the current problem is with 208.83.139.205. To test, set the ip you want to test in /etc/hosts. Example: 208.83.139.205 discovery.razor.cloudmark.com Then: # echo "test" | spamassassin -D razor2 2>&1 | grep " csl" ...Razor Discovery Server discovery.razor.cloudmark.com had no valid csl servers... OR ...Discovery Server discovery.razor.cloudmark.com replying with csl=c302.cloudmark.com... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819977 Title: razor2 had unknown error during get_server_info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1819977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817466] Re: Ram usage increases gradually until it reaches 100% and a hard reset is needed.
After switching back to gdm3 I have checked RAM usage repeatedly and the problem has not recurred. There is a gradual increase in RAM usage, but it is no longer enough to freeze the display. As a hypothesis, is it possible that something about enabling lightdm could have solved the problem even though I am now running gdm3? I attach the output of processes.txt anyway, this was after several hours use, with RAM having slowly increased to about 70%. ** Attachment added: "processes.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1817466/+attachment/5243622/+files/processes.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817466 Title: Ram usage increases gradually until it reaches 100% and a hard reset is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1817466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1817466] Re: Ram usage increases gradually until it reaches 100% and a hard reset is needed.
I have switched to lightdm to avoid the bug, I will switch back this evening to cause the problem again, RAM usage was measured by System Monitor, CPU usage was not high, only RAM usage which slowly increased until the display froze. The issue has been reported by multiple users in the forum (see link in my original message). Currently running default Ubuntu desktop with lightdm, RAM usage remains steady over several hours usage. On Mon, 2019-02-25 at 02:21 +, Daniel van Vugt wrote: > Can you please provide a screenshot from what you are using to assess > that RAM usage is "100%"? > > Also, next time the problem happens please also run this command: > > ps auxw > processes.txt > > and then send us the resulting file 'processes.txt' > > ** Changed in: gdm3 (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/1817466 Title: Ram usage increases gradually until it reaches 100% and a hard reset is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1817466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817466] [NEW] Ram usage increases gradually until it reaches 100% and a hard reset is needed.
Public bug reported: Running Ubuntu 18.04 on Dell Latitude-E5420 with 3.7 GB RAM Gnome 3.28.2. Updated from Ubuntu 16.04. Applications freeze after about an hour continuous use, while applications are running RAM use increases gradually typically from about 55% to 100%. The solution is to use lightdm as the display manager. Default Ubuntu DE appears to work fine with lightdm. I tested other DEs with gdm3 and the same problem was present. The problem has been reported in forums https://ubuntuforums.org/showthread.php?t=2390915 with a number of users reporting that the solution is to use lightdm, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_43_46_generic_47 wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 24 14:21:52 2019 InstallationDate: Installed on 2018-09-27 (150 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2019-01-29 (25 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817466 Title: Ram usage increases gradually until it reaches 100% and a hard reset is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1817466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802334] Re: update tesseract-ocr to 4.0.0 stable
Confirm that this needs doing, the beta version installed in Bionic (18.04) is flawed, for instance running for orientation (--psm 0) gives segmentation fault. Installing stable 4.0.0 (using ppa https://launchpad.net/~alex-p/+archive/ubuntu/tesseract-ocr) gets rid of this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802334 Title: update tesseract-ocr to 4.0.0 stable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tesseract/+bug/1802334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812366] [NEW] outdated version, please update
Public bug reported: This version (0.23.0-1) is now outdated and I believe this is why I receive warning mails from letsencrypt like this: Hello, **Action is required to prevent your Let's Encrypt certificate renewals from breaking.** Your Let’s Encrypt client used ACME TLS-SNI-01 domain validation to issue a certificate in the past 60 days. TLS-SNI-01 validation is reaching end-of-life and will stop working on **February 13th, 2019.** You need to update your ACME client to use an alternative validation method (HTTP-01, DNS-01 or TLS-ALPN-01) before this date or your certificate renewals will break and existing certificates will start to expire. If you need help updating your ACME client, please open a new topic in the Help category of the Let's Encrypt community forum: https://community.letsencrypt.org/c/help Please answer all of the questions in the topic template so we can help you. For more information about the TLS-SNI-01 end-of-life please see our API announcement: https://community.letsencrypt.org/t/february-13-2019-end-of-life-for- all-tls-sni-01-validation-support/74209 Thank you, Let's Encrypt Staff ** Affects: python-certbot (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/1812366 Title: outdated version, please update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1812366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739936] Re: Screen flickering on Razer Blade Stealth (Late 2017) - [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun?
I'm also on Stealth late 2016 (QHD). So far, I survived using i915.enable_rc6=0 until that parameter was removed from newer kernels, then I switched to using intel_idle.max_cstate=4. I still wish someone would find the real root cause of this issue. Today, I noticed the flickering stops completely when I do "rmmod nvme" (booted into usb live ubuntu). Anyone knows how these 2 drivers can possibly affect each-other? The flickering also temporarily stops while I'm writing a disk image to the nvme ssd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739936 Title: Screen flickering on Razer Blade Stealth (Late 2017) - [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1739936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802090] Re: update overwrites sshd_config
attached: /var/log/apt/term.log ** Attachment added: "term.log.gz" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+attachment/5210010/+files/term.log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802090 Title: update overwrites sshd_config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1802090] Re: update overwrites sshd_config
The update to 18.04 was a long time ago, the problem occurred this morning... On Wed, 7 Nov 2018 at 13:01, Marc Deslauriers < marc.deslauri...@canonical.com> wrote: > It looks like you upgraded from Ubuntu 16.04 to Ubuntu 18.04. > >From the log file: > > Unpacking openssh-server (1:7.6p1-4) over (1:7.2p2-4ubuntu2.4) ... > > Then the upgrade asked you what to do with the modified conffile, again, > from the log: > > Configuring openssh-server > sshd_config: A new version (/tmp/filerMG8sJ) of configuration file > /etc/ssh/sshd_config is available, but the > version installed currently has been locally modified. > What do you want to do about modified configuration file sshd_config? > install the package maintainer's > version > keep the local version currently installed > show the differences between the versions > show a side-by-side difference between the versions > start a new shell to examine the situation > > # nano /tmp/filerMG8sJ > > Replacing config file /etc/ssh/sshd_config with new version > > At which point you edited the file and instructed the upgrade process to > use the new package version. > > I'm not quite sure what you expect this bug to resolve, the package > seems to be acting as it should. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1802090 > > Title: > update overwrites sshd_config > > Status in openssh package in Ubuntu: > Incomplete > > Bug description: > The latest update for Bionic (18.04.1) either overwrote or modified my > /etc/ssh/sshd_config with the result that I could no longer access my > machine using ssh. > > A specific > Port [x] > line was removed and replaced by: > #Port 22 > > This was the only change. It happened as part of an automated process > this morning - presumably a security update. > > Was this behaviour intended?! > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802090 Title: update overwrites sshd_config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802090] Re: update overwrites sshd_config
It was an automatic update, file attached ** Attachment added: "apt-term.log" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+attachment/5209992/+files/apt-term.log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802090 Title: update overwrites sshd_config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802090] [NEW] update overwrites sshd_config
Public bug reported: The latest update for Bionic (18.04.1) either overwrote or modified my /etc/ssh/sshd_config with the result that I could no longer access my machine using ssh. A specific Port [x] line was removed and replaced by: #Port 22 This was the only change. It happened as part of an automated process this morning - presumably a security update. Was this behaviour intended?! ** Affects: openssh (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/1802090 Title: update overwrites sshd_config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796863] Re: Upgrade to version 3.4.2 for Bionic
Yes please can we have this asap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796863 Title: Upgrade to version 3.4.2 for Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1796863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796546] [NEW] wrong hard-coded socket location in amavisd-release
Public bug reported: In amavis 2.11 the utility amavisd-release has a hard-coded location for amavisd's unix socket at line 90 as '/var/amavis/amavisd.sock' which is not aligned with the location actually set in /etc/amavis/conf.d/25-amavis_helpers where it is "/var/lib/amavis/amavisd.sock". This causes amavisd-release to fail when trying to release a quarantined email for delivery. Changing the hard-coded location in /usr/sbin/amavisd-release at line 90 to match the setting in /etc/amavis/conf.d/25-amavis_helpers fixes the problem. The previous version of amavis (2.10), used with Ubuntu 16.04, did not have this problem I think. I believe it is new with the version installed (using apt-get) with Ubuntu 18.04 (i.e. 2.11). I have not tested intervening distros. This bug is an incompatibility between the setting in debian package of amavis 2.11 which has: /etc/amavis/conf.d/25-amavis_helpers at line 25: $unix_socketname = "/var/lib/amavis/amavisd.sock"; /usr/sbin/amavisd-release at line 90: $socketname = '/var/amavis/amavisd.sock'; As directory /var/amavis does not exist, the only realistic solution is to change the setting in amavisd-release. The problem arises because in Debian (and hence Ubuntu), $MYHOME is hard-coded to /var/lib/amavis whereas in the default installation, it is /var/amavis. And amavisd-release does not seem to use the $MYHOME setting. ** Affects: amavisd-new (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/1796546 Title: wrong hard-coded socket location in amavisd-release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1796546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786195] Re: broken audio/muffled, no system audio
The bug was not gone when using kernel 4.4 there was also an additional kernel between 4.4 and 4.15 that was available. I tried that as well. same result.no fix. Since then I backed up my system and did a completely fresh install of 18.04LTS and the issue is still not fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786195 Title: broken audio/muffled, no system audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786195] Re: broken audio/muffled, no system audio
The bug was not gone when using kernel 4.4 there was also an additional kernel between 4.4 and 4.15 that was available. I tried that as well. same result.no fix. Since then I backed up my system and did a completely fresh install of 18.04LTS and the issue is still not fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786195 Title: broken audio/muffled, no system audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786195] Re: broken audio/muffled, no system audio
"16.04 used kernel 4.4 and you are presently using kernel 4.15" Have been running 18.04 for a week. Until earlier today issue was not present, each day until now however, had been just fine. Is "4.15" the same kernel used at install of "18.04"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786195 Title: broken audio/muffled, no system audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786195] Re: broken audio/muffled, no system audio
uname -a Linux novgorod-LinuxBook 4.4.146-0404146-generic #201808061143 SMP Mon Aug 6 15:51:56 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786195 Title: broken audio/muffled, no system audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
