For more history on this issue, please see the following Debian bug
report created in June 2021:
openjdk-11-jre-headless: running java in qemu s390 gives a SIGILL at C
[linux-vdso64.so.1+0x6f8] __kernel_getcpu+0x8
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990417
That report links to a
Now that I can reproduce the problem on the latest QEMU 6.1, I created
the following issue with the upstream project:
Java crashes on s390x VM with SIGILL/ILL_PRVOPC at '__kernel_getcpu+0x8'
https://gitlab.com/qemu-project/qemu/-/issues/655
** Bug watch added:
** Attachment added: "hs_err_pid2883.log - log file using QEMU 6.1"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1945540/+attachment/5529623/+files/hs_err_pid2883.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The error still occurs on the same s390x virtual machine with QEMU
version 6.1.
After building QEMU 6.1, I started the virtual machine as follows:
$ ../qemu-6.1.0/build/s390x-softmmu/qemu-system-s390x \
-m 2048 -drive if=virtio,file=s390x-focal.qcow2,cache=none
The QEMU 6.1.0 monitor
See also the following bug reported by Manuel J. on 2021-06-02:
Maven 3.6.3-1 fails to run with OpenJDK 16
https://bugs.launchpad.net/ubuntu/+source/maven/+bug/1930541
Perhaps this bug report should be marked as a duplicate of Bug #1930541
above, as the illegal reflective access is now an error
Now that Ubuntu 20.04 LTS provides the OpenJDK 16 package in the updates
pocket (since May 10, 2021), it would be great to have the fix in Ubuntu
Maven 3.6.3-2 back-ported to Ubuntu 20.04. I'm working around the
problem by installing a local copy of Maven 3.8.1 directly from Apache.
$ apt-cache
I think this bug that I opened is invalid for both openjdk-9 and
openjfx. Sorry for not closing it sooner.
Ubuntu has a separate package for JavaFX, currently at version 11, the
Long Term Support release. The most recent release is version 15,
available on September 8, 2020. OpenJFX follows the
Thank you for adding the two most recent non-LTS releases of OpenJDK in
addition to the base OpenJDK LTS release. Having three OpenJDK releases
in Ubuntu is a great help in solving problems and seeing performance
trends in the JVM.
For example, these Ubuntu packages allowed me to benchmark the
That didn't work either. Using the "intel" driver with:
Option "AccelMethod" "UXA"
still resulted in the following GPU HANG:
[drm] GPU HANG: ecode 9:0:0x85da, in compiz [3398], reason:
Hang on rcs0, action: reset
i915 :00:02.0: Resetting rcs0 after gpu hang
Well, that didn't work for very long. Disabling the acceleration of the
"intel" driver did not solve the problem for me. I tried three more
changes, described below.
(1) Next I tried going back to the "modesetting" driver but with the
acceleration disabled:
/etc/X11/xorg.conf
Section "Device"
I just hit another GPU HANG, this time with the "intel" driver instead
of the "modesetting" driver. The kernel log file (/var/log/kern.log)
shows:
Apr 6 08:59:36 tower kernel: [44387.837794]
[drm] GPU HANG: ecode 9:0:0x85da, in Xorg [1751],
I started to see the same GPU HANG error sometime this year (2020).
I am using the default "modesetting" driver with automatic configuration
and no "xorg.conf" file (/etc/X11/xorg.conf). The Xorg log file
(/var/log/Xorg.1.log) is attached.
The following error occurred on April 1, 2020, at
2020-01-15: OpenJDK 11.0.6 is available on Ubuntu 18.04 LTS with the fix.
2020-01-17: OpenJDK 8 Update 242 is available on Ubuntu 16.04 LTS and Ubuntu
18.04 LTS with the fix.
** Changed in: openjdk-lts (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification
Fix committed upstream in OpenJDK 11.0.6 to be released January 14,
2020.
** Changed in: openjdk-lts (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The font fix is backported to OpenJDK 11.0.6 with the following Backport
Bug Report:
JDK / JDK-8231359
Need to set the FreeType LCD Filter to reduce fringing
https://bugs.openjdk.java.net/browse/JDK-8231359
OpenJDK 11.0.6 is scheduled to be released on January 14, 2020.
OpenJDK 11 Updates
** Summary changed:
- Backport critical JDK-8212071 font fix to OpenJDK 11
+ Backport JDK-8212071 font fix to OpenJDK 11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815119
Title:
Backport
** Description changed:
- This is a request to backport the simple two-line fix for Java Bug
- JDK-8212071 to OpenJDK 11. Doing so will correct a very visible font
- error that has persisted in the OpenJDK since its beginning. The bug is
- best described on the page below. Scroll down to the
** Description changed:
This is a request to backport the simple two-line fix for Java Bug
JDK-8212071 to OpenJDK 11. Doing so will correct a very visible font
error that has persisted in the OpenJDK since its beginning. The bug is
best described on the page below. Scroll down to the
Public bug reported:
This is a request to backport the simple two-line fix for Java Bug
JDK-8212071 to OpenJDK 11. Doing so will correct a very visible font
error that has persisted in the OpenJDK since its beginning. The bug is
best described on the page below. Scroll down to the first set of
It seems that OpenJFX should continue to be packaged separately, just
like any other Java library.
JavaFX was included in Oracle JDK 8 but will be removed in JDK 11, the
next long-term support (LTS) release of the JDK. See the following pages
for updates on the status of JavaFX in the Oracle JDK:
The change suggested in the following comment on GitHub solved the
problem for me without having to edit the database:
Cannot edit tags under 'Categories and Tags' #206
https://github.com/projecthamster/hamster/issues/206#issuecomment-103143461
Just change the following line in the
** Summary changed:
- JavaFX support is in upstream OpenJDK 9 but missing in Ubuntu OpenJDK 9
+ JavaFX support is in Oracle JDK 9 but missing in Ubuntu OpenJDK 9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I misunderstood what I originally downloaded from the JDK 9 General-
Availability Release page (http://jdk.java.net/9/). When Java 9 was
first released, that page had a link to the Oracle JDK, not to the
OpenJDK. Now that Oracle has released a 9.0.1 update, the OpenJDK is
different from the JDK
It seems there are still some dependencies being worked out for the
build process. See:
Cannot build JavaFX modules with boot JDK that does not already include them
https://bugs.openjdk.java.net/browse/JDK-8189111
The workaround mentioned on the OpenJFX mailing list (openjfx-
The OpenJFX source tree is separate from the OpenJDK sources, but its
modules are included as input into the OpenJDK build process. For the
OpenJFX source tree, see here:
Getting the Sources
https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX#BuildingOpenJFX-GettingtheSources
For details on the new version strings, please see this JDK Enhancement
Proposal that was included in OpenJDK 9:
JEP 223: New Version-String Scheme
http://openjdk.java.net/jeps/223
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
OpenJDK 9 in Ubuntu 17.10 is missing the JavaFX support found in the
upstream release. In the command output below, the file "HelloWorld.jar"
is the simple "Hello World" JavaFX application created automatically by
NetBeans when you create a new JavaFX Application project.
I swapped my Lite-On drive for a replacement Samsung drive that Dell
sent to me. As a result, I'm unable to help any further on this bug
report. I returned the Lite-On drive to Dell for further testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
After wiping out my Ubuntu installation with Windows 10 Pro and running
the firmware upgrade, I discovered that it was an upgrade to the version
I already have (48811QD). I also tried a separate DOS firmware upgrade
program that Dell sent to me by e-mail, with the same result:
Model:
Dell asked me to apply the following firmware upgrade, which fixed some
problems on Windows:
LITEONIT Solid State Drive Firmware
http://www.dell.com/support/home/ca/en/cabsdt1/Drivers/DriversDetails?driverId=CWX68
The update program, though, works only on Windows. I'm waiting to find
out from
I opened a Service Request yesterday with Dell regarding my Lite-On CX2
NVMe Series drive. The workstation group escalated the support ticket to
their "High Complexity or Ubuntu" group and told me they would get back
to me by tomorrow (in 24-48 hours).
The last time this happened, there were 329
My system is under warranty, so I'll find out in the next week what Dell
says about the problem. I don't see any way for me to upgrade the
firmware on the device:
http://www.liteonssd.com/en/pcie-ssd/item/client-pcie-ssd/CLIENT-
CX2-SERIES.html
I'm on firmware revision 48811QD, while you're on
No, the errors stopped when I reverted to the Ubuntu 16.04 GA kernel and
X server on May 31.
I have been running error-free for over two weeks with the "linux-
generic" package version 4.4.0.79.85. It appears there may be something
in Linux kernel version 4.8.0-53.56 that caused the problems, but
I'm adding the actual errors I saw, just for the record.
What happens is that the root file system becomes read-only due to
errors on the drive. My root file system is a logical volume on an
encrypted partition (LVM with LUKS encryption), mounted and encrypted
with the following options:
$ mount
My NVMe drive failed again yesterday. I no longer think the errors are
due to the APST support. I'm starting to think it's either something in
the Linux kernel 4.8.0-53 upgrade or simply a problem with the drive
hardware or firmware.
The time-line of the errors is shown below. Note that I never
@kaihengfeng Here you go:
$ sudo nvme id-ctrl /dev/nvme0
NVME Identify Controller:
vid : 0x14a4
ssvid : 0x1b4b
sn : TW0XVRV7LOH006AJ09F1
mn : CX2-8B256-Q11 NVMe LITEON 256GB
fr : 48811QD
rab : 0
ieee: 002303
cmic: 0
mdts: 5
cntlid : 1
ver :
Oops, wrong model number on the Lite-On drive in my Dell Precision Tower
3420. It should be Lite-On Model CX2-8B256-Q11.
The "nvme list" command reports:
Node: /dev/nvme0n1
Model: CX2-8B256-Q11 NVMe LITEON 256GB
Version: 1.2
Namespace: 1
Usage: 0.00 B / 256.06 GB
Format:512
I think I hit this problem, but with the 256 GB Lite-On (or LiteOn) NVMe
M.2 PCIe CX2 Series Enterprise Solid-State Drive Model CA1-8B256 that
came standard in my 2017 Dell Precision Tower 3420.
I'm on the HWE Kernel with the "linux-generic-hwe-16.04" package, having
installed from the Ubuntu
Maybe it's related to this problem:
KVM + Xenial Server. libvirt-bin won't configure
http://askubuntu.com/questions/762924/kvm-xenial-server-libvirt-bin-wont-configure#763935
I had to do something similar to get libvirt-bin started again:
$ sudo systemctl stop apparmor.service
$ sudo apt-get
On 2016-11-15 06:52 AM, Serge Hallyn wrote:
> Wait, what? Perhaps he purposely had disabled it on purpose?
I may have done just that, but I can't remember. I was eager to switch
to LXD in Ubuntu 16.04 instead of using LXC and uvtool in Ubuntu 14.04.
I was surprised that it made the upgrade
Public bug reported:
Upgraded from Ubuntu 14.04.5 to 16.04.1 and package "uvtool-libvirt"
failed to upgrade. All other packages seemed to be installed just fine.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: uvtool-libvirt (not installed)
ProcVersionSignature: Ubuntu
*** This bug is a duplicate of bug 703800 ***
https://bugs.launchpad.net/bugs/703800
In my tests on Ubuntu 14.04, the LXC dnsmasq process is restarted with:
$ sudo restart lxc-net
only when all guest containers are stopped. If one or more containers
are running, the dnsmasq process is left
*** This bug is a duplicate of bug 703800 ***
https://bugs.launchpad.net/bugs/703800
In my tests on Ubuntu 14.04, the LXC dnsmasq process is restarted with:
$ sudo restart lxc-net
only when all guest containers are stopped. If one or more containers
are running, the dnsmasq process is left
Thank you for following up! Unfortunately, I pulled out the NVIDIA
Quadro FX 550 and bought a cheap AMD Radeon HD 5450 graphics adapter a
very long time ago now. I'm using the ATI open-source driver, and
haven't had the problem since. I gave away the NVIDIA adapter.
--
You received this bug
I just upgraded to Ubuntu 12.10, and now I'm seeing the same message on
boot:
/scripts/local-top/cryptroot: line 1: can't open
/dev/mapper/p490-root: no such file
The contents of /var/log/boot.log and /etc/crypttab are below.
/var/log/boot.log:
Reading all physical volumes. This may take
This bug was fixed today by one of the Evince developers. For details on
exactly what the fix does, see my notes here:
https://bugzilla.gnome.org/show_bug.cgi?id=639003#c21
The patch also works when applied to the earlier Evince source code in
the current Ubuntu 11.10. For the impatient, you
apport information
** Tags added: apport-collected oneiric running-unity ubuntu
** Description changed:
The X.Org X server on my Dell Precision 490 Workstation freezes
consistently and permanently each time I load the Web page at the
following address on my Ubuntu 11.10 oneiric system
apport information
** Attachment added: BootLog.gz
https://bugs.launchpad.net/bugs/901793/+attachment/2630735/+files/BootLog.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901793
Title:
Xorg
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630736/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901793
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630737/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901793
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630738/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901793
Title:
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630739/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901793
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630740/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901793
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630741/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901793
Title:
Xorg
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630742/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901793
Title:
Xorg
apport information
** Attachment added: MonitorsGlobal.xml.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630743/+files/MonitorsGlobal.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630745/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901793
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630746/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630747/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901793
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630748/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901793
Title:
Xorg
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630749/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901793
Title:
apport information
** Attachment added: UnitySupportTest.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630750/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630751/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901793
Title:
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630752/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901793
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630753/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901793
Title:
Xorg
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630754/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901793
Title:
apport information
** Attachment added: MonitorsUser.xml.txt
https://bugs.launchpad.net/bugs/901793/+attachment/2630744/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached above is all the information from the apport-collect 901793
command. Attached below are my own captures of the dmesg output and
/var/log/Xorg.0.log file during each of the freezes (using SSH to login
to the system).
I just tried it again, and my system still freezes even after upgrading
Freeze #2 dmesg output. Ends with:
[ 1180.344349] [drm] nouveau :07:00.0: Setting dpms mode 3 on tmds encoder
(output 1)
[ 1347.880775] [drm] nouveau :07:00.0: Setting dpms mode 0 on tmds encoder
(output 1)
** Attachment added: dmesg-2.txt
Freeze #3 dmesg output. Ends with:
[ 417.676011] [drm] nouveau :07:00.0: reloc wait_idle failed: -16
[ 417.676021] [drm] nouveau :07:00.0: reloc apply: -16
[ 420.684021] [drm] nouveau :07:00.0: reloc wait_idle failed: -16
[ 420.684031] [drm] nouveau :07:00.0: reloc apply: -16
Freeze #4 dmesg output. Ends with:
[ 203.796013] [drm] nouveau :07:00.0: Failed to idle channel 4.
[ 203.800081] [drm] nouveau :07:00.0: PGRAPH idle timed out with status
0x08820101
[ 203.800081] [drm] nouveau :07:00.0: Failed: Instance=0x00010f00 Save=1
[ 203.800081] [drm]
Freeze #5 dmesg output. Ends with (nothing nouveau):
[ 44.480010] eth0: no IPv6 routers present
[ 44.796015] eth1: no IPv6 routers present
** Attachment added: dmesg-5.txt
Freeze #2 /var/log/Xorg.0.log file. Ends with:
[ 1170.331] (II) NOUVEAU(0): Modeline 1680x1050x0.0 119.00 1680
1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz)
** Attachment added: Xorg.0.log-2.txt
Freeze #3 /var/log/Xorg.0.log file. Ends with:
[ 500.092] [mi] EQ overflowing. The server is probably stuck in an infinite
loop.
[ 500.092]
Backtrace:
[ 500.122] 0: /usr/bin/X (xorg_backtrace+0x26) [0x460566]
...
** Attachment added: Xorg.0.log-3.txt
Freeze #4 /var/log/Xorg.0.log file. Ends with:
[ 203.047] [mi] EQ overflowing. The server is probably stuck in an infinite
loop.
[ 203.047]
Backtrace:
[ 203.095] 0: /usr/bin/X (xorg_backtrace+0x26) [0x460566]
...
** Attachment added: Xorg.0.log-4.txt
Freeze #5 /var/log/Xorg.0.log file. Ends with:
[ 182.728] [mi] EQ overflowing. The server is probably stuck in an infinite
loop.
[ 182.728]
Backtrace:
[ 182.756] 0: /usr/bin/X (xorg_backtrace+0x26) [0x460566]
...
** Attachment added: Xorg.0.log-5.txt
Freeze #1 dmesg output. Ends with:
[ 636.608016] [drm] nouveau :07:00.0: reloc wait_idle failed: -16
[ 636.608028] [drm] nouveau :07:00.0: reloc apply: -16
** Attachment added: dmesg-1.txt
Freeze #1 /var/log/Xorg.0.log file. Ends with:
[ 146.312] (II) XKB: reuse xkmfile
/var/lib/xkb/server-2B6FA8C3EA6AA113DC680288825EF0846851A010.xkm
[ 146.343] (II) XKB: reuse xkmfile
/var/lib/xkb/server-2B6FA8C3EA6AA113DC680288825EF0846851A010.xkm
[ 146.347] (II) XKB: reuse xkmfile
Public bug reported:
The X.Org X server on my Dell Precision 490 Workstation freezes
consistently and permanently each time I load the Web page at the
following address on my Ubuntu 11.10 oneiric system running Unity 2D:
http://www.google.ca/nexus
I never encountered such freezes in the
Adding the TextArea to a containing Panel seems to cause the problem. A
sample applet that recreates the issue is attached below as
MyApplet.java.
** Attachment added: MyApplet.java
http://launchpadlibrarian.net/25563631/MyApplet.java
--
Draw order causes panels to be obscured on Window
As requested by TJ, I'll look into creating a small applet with source
code that can recreate the problem.
--
Draw order causes panels to be obscured on Window resize
https://bugs.launchpad.net/bugs/358316
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm seeing the problem, but I'm not using RAID. I have two encrypted
partitions -- one setup up automatically during installation, and the
other set up manually with cryptsetup and LUKS.
I copied some big files from one encrypted partition on one hard drive
to another encrypted partition on
I got rid of the hang (or very long delay) by changing this line in
conf/server.xml:
Listener className=org.apache.catalina.core.AprLifecycleListener
SSLEngine=on /
to this:
Listener className=org.apache.catalina.core.AprLifecycleListener
SSLEngine=off /
but then I ran right into this
Hostway had me switch over to two name servers running BIND (instead of
DNSCACHE) in my /etc/resolv.conf file, and now the AOL SPF checks are
working as expected:
Mar 28 13:45:28 ldc1042 policyd-spf[4559]: :HELO client-ip=63.229.3.151;
helo=www.commspeak.com; [EMAIL PROTECTED];
[EMAIL PROTECTED];
I'm using the unmodified default configuration:
/etc/python-policyd-spf/policyd-spf.conf
debugLevel = 0
defaultSeedOnly = 1
HELO_reject = SPF_Not_Pass
Mail_From_reject = Fail
PermError_reject = False
TempError_Defer = False
In the meanwhile, I've just
You mean master.cf, right? Putting the configuration file as an
argument in main.cf caused Postfix to reject all mail with 451 4.3.5
Server configuration error.
/etc/postfix/master.cf
--
# Python Sender Policy Framework (SPF) Service
# See
Here are a few scenarios you may want to consider.
There seems to be a wide variety of responses you can get back when
trying to get long or multiple DNS TXT records -- especially through a
NAT router where you're forwarding port 25 onto an internal mail server.
The machines behind the routers
Actually, I think the following series of commands are more helpful.
First the normal UDP request (with a fall-back to TCP):
[EMAIL PROTECTED]:~$ host -t txt aol.com
;; Warning: Message parser reports malformed message packet.
;; Truncated, retrying in TCP mode.
aol.com descriptive text
I tried it on a third machine, and it's working there. The difference is
as follows. On the machine that fails, the long AOL SPF records are
being returned malformed and pyspf or its underlying support is
failing -- perhaps by design -- to trying again with TCP.
On the machine that fails
Public bug reported:
Will follow up through Web interface.
ProblemType: Bug
Architecture: i386
Date: Sat Mar 22 12:46:20 2008
DistroRelease: Ubuntu 7.10
Package: python-spf 2.0.4-1
PackageArchitecture: all
SourcePackage: pyspf
Uname: Linux www 2.6.22-14-server #1 SMP Sun Oct 14 23:34:23 GMT 2007
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/12812511/Dependencies.txt
--
python-policyd-spf failing on AOL SPF records.
https://bugs.launchpad.net/bugs/205254
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Will follow up through Web interface.
+ It seems that the long SPF records for aol.com are causing
+ python-policyd-spf to fail when getting the DNS TXT record by UDP.
+
+ Here are the TXT records fetched on www.volano.com:
+
+ $ host -t txt aol.com
+ ;; Warning:
to:
main.cf
---
smtpd_recipient_restrictions =
...
check_policy_service unix:private/policy-spf
...
Thanks,
John Neffenger
--
python-policyd-spf failing on AOL SPF records.
https://bugs.launchpad.net/bugs/205254
You received this bug notification because you are a member
Thanks for looking into it. You must be getting the same result as one
of my machines, but not the other. The other of the two machines shown
above (www.volano.com) gets DNS TCP queries just fine, as shown here
(with the -T flag):
[EMAIL PROTECTED]:~$ host -T -t txt aol.com
aol.com descriptive
The command-line upgrade works for me this morning on Dapper. Thanks!
I too, though, tried to upgrade a friend's system from Feisty to Gutsy
yesterday evening, and the entire upgrade failed just because of these
three files. The change to the repositories seems to have disabled a
lot more than
I managed to work around the problem by not letting the installation
script generate its own random password. See my post titled Found a
solution here for details:
Error message about one package after each install
http://ubuntuforums.org/showthread.php?t=545106
--
post-installation fails when
96 matches
Mail list logo
