@Andreas:
`pro version` shows `32.3.1~24.04`. I ran `pro collect-logs` and attach
the tarball.
I still see the error message regularly in /var/log/syslog, specifically at
these datetimes:
2024-07-02 07:27:27
2024-07-03 16:12:53
2024-07-05 06:09:08
2024-07-08 00:59:56
2024-07-09 09:25:09
2024-07-
# 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 ..
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)
--
Y
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 uns
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
Casp
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.laun
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
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://
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 oth
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
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 a
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
M
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
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
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.launc
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
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 \
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=Ubun
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 differ
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
(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.launchp
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 c
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
Ti
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
T
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:
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/2056
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
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.outlo
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).
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-17ubu
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
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 mana
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
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:
Receiv
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_
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: e
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:
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@ins
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
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 offic
"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.
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 imag
*** 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 SS
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 no
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 chtm
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
int
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.
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
** 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://bu
** 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.lau
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
** 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.n
** 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.n
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
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
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
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 notificatio
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
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
ApportV
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
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
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)
Im
** 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 notificatio
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 h
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
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
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 cr
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
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.laun
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, manua
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 rota
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:
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
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 o
** 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 X
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 b
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.
h
*** 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
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
Dis
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=eo
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-u
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
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
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 subscri
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 |
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 t
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
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 us
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
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 valida
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
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.
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
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
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 par
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.launchpa
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
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 thi
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 thi
"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 a
1 - 100 of 724 matches
Mail list logo