[Bug 1945540] Re: Java crashes on s390x VM with SIGILL/ILL_PRVOPC at '__kernel_getcpu+0x8'
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 simple C program that can reproduce the error. ** Bug watch added: Debian Bug tracker #990417 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990417 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945540 Title: Java crashes on s390x VM with SIGILL/ILL_PRVOPC at '__kernel_getcpu+0x8' To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-gitlab/+bug/1945540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945540] Re: Java crashes on s390x VM with SIGILL/ILL_PRVOPC at '__kernel_getcpu+0x8'
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: gitlab.com/qemu-project/qemu/-/issues #655 https://gitlab.com/qemu-project/qemu/-/issues/655 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945540 Title: Java crashes on s390x VM with SIGILL/ILL_PRVOPC at '__kernel_getcpu+0x8' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1945540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945540] Re: Java crashes on s390x VM with SIGILL/ILL_PRVOPC at '__kernel_getcpu+0x8'
** 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. https://bugs.launchpad.net/bugs/1945540 Title: Java crashes on s390x VM with SIGILL/ILL_PRVOPC at '__kernel_getcpu+0x8' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1945540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945540] Re: Java crashes on s390x VM with SIGILL/ILL_PRVOPC at '__kernel_getcpu+0x8'
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 shows: (qemu) info version 6.1.0 On the guest, I installed the new 'openjdk-17-jre-headless' OpenJDK 17 package in Ubuntu 20.04. Although the installation fails because of this bug, the 'java' command is available after the attempt to install the package. $ sudo apt-get install openjdk-17-jre-headless The error in this bug report still occurs: $ /usr/lib/jvm/java-17-openjdk-s390x/bin/java --version # # A fatal error has been detected by the Java Runtime Environment: # # SIGILL (0x4) at pc=0x03ff9e4fe6f4, pid=2883, tid=2884 # # JRE version: (17.0+35) (build ) # Java VM: OpenJDK 64-Bit Server VM (17+35-Ubuntu-120.04, mixed # mode, sharing, tiered, compressed oops, compressed class ptrs, # serial gc, linux-s390x) # Problematic frame: # C [linux-vdso64.so.1+0x6f8] __kernel_getcpu+0x8 # # 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/ubuntu/core.2883) # # An error report file with more information is saved as: # /home/ubuntu/hs_err_pid2883.log # # Aborted (core dumped) I'll also attach the corresponding log file. For reference, the guest shows the following CPU information under QEMU 6.1. $ lscpu Architecture:s390x CPU op-mode(s): 32-bit, 64-bit Byte Order: Big Endian CPU(s): 1 On-line CPU(s) list: 0 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s) per book: 1 Book(s) per drawer: 1 Drawer(s): 1 NUMA node(s):1 Vendor ID: IBM/S390 Machine type:3906 BogoMIPS:13370.00 Hypervisor: KVM/Linux Hypervisor vendor: KVM Virtualization type: full Dispatching mode:horizontal NUMA node0 CPU(s): 0 ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945540 Title: Java crashes on s390x VM with SIGILL/ILL_PRVOPC at '__kernel_getcpu+0x8' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1945540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754602] Re: guice compatibility with Java 9: "WARNING: Illegal reflective access by com.google.inject.internal."
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 with OpenJDK 16 instead of the prior warnings. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754602 Title: guice compatibility with Java 9: "WARNING: Illegal reflective access by com.google.inject.internal." To manage notifications about this bug go to: https://bugs.launchpad.net/guice/+bug/1754602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930541] Re: Maven 3.6.3-1 fails to run with OpenJDK 16
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 policy openjdk-16-jdk openjdk-16-jdk: Installed: 16.0.1+9-1~20.04 Candidate: 16.0.1+9-1~20.04 Version table: *** 16.0.1+9-1~20.04 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages 100 /var/lib/dpkg/status Without the fix, installing OpenJDK 16 breaks Maven. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930541 Title: Maven 3.6.3-1 fails to run with OpenJDK 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maven/+bug/1930541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721852] Re: JavaFX support is in Oracle JDK 9 but missing in Ubuntu OpenJDK 9
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 same six-month release schedule as OpenJDK, with the same version numbers, generally made available one week before each OpenJDK release. Personally, I would like to see the openjfx package updated in the same manner as the OpenJDK packages, which include the intermediate releases between the Long Term Support versions. I have been unable to find the plans for OpenJFX on Ubuntu, though. ** Changed in: openjfx (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721852 Title: JavaFX support is in Oracle JDK 9 but missing in Ubuntu OpenJDK 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-9/+bug/1721852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871161] Re: SRU: remove openjdk-14 from the release pocket, and re-introduce it in the updates pocket
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 performance of certain buffer-copying operations on ARM processors across JDK versions 11, 13, and 14, with surprising results. See the bar charts on the following page for examples: JavaFX FramebufferY8 Benchmarks https://jgneff.github.io/framebufferY8/ There's always AdoptOpenJDK, but it's great to have the packages built and ready to go directly within Ubuntu. It also helps in verifying that there are no critical differences between the builds by AdoptOpenJDK and Ubuntu. Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871161 Title: SRU: remove openjdk-14 from the release pocket, and re-introduce it in the updates pocket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-13/+bug/1871161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724047] Re: xserver terminates frequently, journal says drm/i915: Resetting chip after gpu hang
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 [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout i915 :00:02.0: Resetting chip after gpu hang [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -5 After all these tests, my current guess is that the hardware acceleration in my Web browsers (Firefox and Chromium) is triggering the error in the graphics driver or firmware. I disabled the hardware acceleration in Firefox and Chromium. I also now avoid running anything that uses Electron, such as the Skype and Signal desktop snap packages, because I don't know how to disable the hardware acceleration in an Electron app. After about a week, the problem occurs now only if I forget and leave Skype running for an afternoon. I'm hoping this can continue to function as a simple work-around. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724047 Title: xserver terminates frequently, journal says drm/i915: Resetting chip after gpu hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server-hwe-16.04/+bug/1724047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724047] Re: xserver terminates frequently, journal says drm/i915: Resetting chip 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" Identifier "Intel Graphics" Driver "modesetting" Option "AccelMethod" "none" EndSection Eventually, the screen went into some kind of infinite-updating loop among all the window and was completely unresponsive. The kernel log file (/var/log/kern.log) contained the messages: Apr 12 10:00:25 tower kernel: [ 4941.921796] show_signal_msg: 21 callbacks suppressed Apr 12 10:00:25 tower kernel: [ 4941.921808] GpuWatchdog[7196]: segfault at 0 ip 55f89a514727 sp 7f8ec6d966d0 error 6 in signal-desktop[55f89733a000+53d7000] I'm not sure whether the Signal desktop snap application triggered the problem, but those were the last messages before having to power-off the system. (2) Next I removed the "/etc/X11/xorg.conf" file and reverted to the original Ubuntu 16.04 kernel version 4.4 instead of the Hardware Enablement (HWE) version 4.15. That eventually encountered the same infinite-updating loop problem. (3) So a couple of days ago I switched back to the HWE kernel version 4.15 and updated the Xorg configuration to use UXA instead of the default SNA acceleration method. Several posts on the Internet suggested that it might solve problems with Intel Skylake graphics. (I have Intel HD Graphics P530 on a 2015 "Skylake" Xeon E3-1225v5 processor.) /etc/X11/xorg.conf Section "Device" Identifier "Intel Graphics" Driver "intel" # Acceleration method: Unified Acceleration Architecture Option "AccelMethod" "UXA" EndSection So far, so good. It has been only a couple of days, though, and sometimes the problem takes several days to occur. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724047 Title: xserver terminates frequently, journal says drm/i915: Resetting chip after gpu hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server-hwe-16.04/+bug/1724047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724047] Re: xserver terminates frequently, journal says drm/i915: Resetting chip after gpu hang
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], reason: Hang on rcs0, action: reset i915 :00:02.0: Resetting rcs0 after gpu hang [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout i915 :00:02.0: Resetting chip after gpu hang asynchronous wait on fence i915:compiz[3304]/1:56366 timed out [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -5 Now I will try with the hardware acceleration disabled, still using the "intel" driver, as follows (/etc/X11/xorg.conf): --- # Tries "intel" instead of "modesetting" driver to fix GPU HANG # https://bugs.launchpad.net/ubuntu/+source/xorg-server-hwe-16.04/+bug/1724047 Section "Device" Identifier "Intel Graphics" Driver "intel" # Disables acceleration Option "NoAccel" "True" # Disables only 3D acceleration (Direct Rendering Infrastructure) # Option "DRI" "False" EndSection --- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724047 Title: xserver terminates frequently, journal says drm/i915: Resetting chip after gpu hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server-hwe-16.04/+bug/1724047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724047] Re: xserver terminates frequently, journal says drm/i915: Resetting chip after gpu hang
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 18:36:30. [drm] GPU HANG: ecode 9:0:0x85da, in Xorg [1784], reason: Hang on rcs0, action: reset i915 :00:02.0: Resetting rcs0 after gpu hang [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout i915 :00:02.0: Resetting chip after gpu hang [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -5 [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. The next error occurred on April 4, 2020 at 12:15:13. [drm] GPU HANG: ecode 9:0:0x85da, in skypeforlinux [17067], reason: Hang on rcs0, action: reset i915 :00:02.0: Resetting rcs0 after gpu hang [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout i915 :00:02.0: Resetting chip after gpu hang [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -5 [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. I have now switched to the older "intel" driver to see whether that might solve the problem, using the following "xorg.conf" file: # Try "intel" instead of "modesetting" driver to fix GPU HANG. Section "Device" Identifier "Intel Graphics" Driver "intel" # Disables acceleration # Option "NoAccel" "True" # Disables only 3D acceleration (Direct Rendering Infrastructure) # Option "DRI" "False" EndSection My system information is listed below (now showing the "intel" graphics driver). $ uname -a Linux tower 4.15.0-91-generic #92~16.04.1-Ubuntu SMP Fri Feb 28 14:57:22 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.6 LTS Release:16.04 Codename: xenial $ inxi -S -M -C -G -y 80 System: Host: tower Kernel: 4.15.0-91-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: Dell product: Precision Tower 3420 Mobo: Dell model: 08K0X7 v: A01 Bios: Dell v: 2.13.1 date: 06/14/2019 CPU: Quad core Intel Xeon E3-1225 v5 (-HT-MCP-) cache: 8192 KB clock speeds: max: 3300 MHz 1: 917 MHz 2: 1962 MHz 3: 1896 MHz 4: 1349 MHz Graphics: Card: Intel HD Graphics P530 Display Server: X.Org 1.19.6 driver: intel Resolution: 2560x1440@59.95hz GLX Renderer: Mesa DRI Intel HD Graphics P530 (Skylake GT2) GLX Version: 3.0 Mesa 18.0.5 ** Attachment added: "Matched modesetting as autoconfigured driver 0" https://bugs.launchpad.net/ubuntu/+source/xorg-server-hwe-16.04/+bug/1724047/+attachment/5347151/+files/Xorg.1.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724047 Title: xserver terminates frequently, journal says drm/i915: Resetting chip after gpu hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server-hwe-16.04/+bug/1724047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815119] Re: Backport JDK-8212071 font fix to OpenJDK 11
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815119 Title: Backport JDK-8212071 font fix to OpenJDK 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1815119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815119] Re: Backport JDK-8212071 font fix to OpenJDK 11
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. https://bugs.launchpad.net/bugs/1815119 Title: Backport JDK-8212071 font fix to OpenJDK 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1815119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815119] Re: Backport JDK-8212071 font fix to OpenJDK 11
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 https://wiki.openjdk.java.net/display/JDKUpdates/JDK11u This bug report can be closed. -- 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 JDK-8212071 font fix to OpenJDK 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1815119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815119] Re: Backport JDK-8212071 font fix to OpenJDK 11
** 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 JDK-8212071 font fix to OpenJDK 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1815119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815119] Re: Backport critical JDK-8212071 font fix to OpenJDK 11
** 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 first set of Font - Demo screenshots for a quick view of the problem in the "Before" and - "After" images. + This is a request to backport the two-line fix for Java Bug JDK-8212071 + to OpenJDK 11. Doing so will correct a visible font error that has been + in the OpenJDK since its beginning. The bug is described on the page + below. Scroll down to the first set of Font Demo screenshots for a quick + view of the problem in the "Before" and "After" images. OpenJDK FreeType Font Fix https://github.com/jgneff/openjdk-freetype - The page above links to the official report in the Java Bug System: + The official report in the Java Bug System is here: Need to set the FreeType LCD Filter to reduce fringing https://bugs.openjdk.java.net/browse/JDK-8212071 - The consequences of this bug have been far-reaching. It's one of the - reasons why JetBrains created their own fork of the JDK to include in - IntelliJ IDEA [1]; why we have popular forks of the JDK just to fix the - fonts on Ubuntu [2]; and why the snap for NetBeans 10 now ships with - sub-pixel rendering entirely disabled by default [3], reverting to - grayscale anti-aliasing. + I believe the consequences of this bug have been far-reaching. It's one + of the reasons why JetBrains created their own fork of the JDK to + include in IntelliJ IDEA [1]; why we have popular forks of the JDK to + fix the fonts on Ubuntu [2]; and why the snap for NetBeans 10 ships with + sub-pixel rendering disabled by default [3], reverting to grayscale + anti-aliasing. - Personally it's why, after programming in Java since 1996, I was ready - to abandon the platform completely for any other alternative that could - simply get the fonts right -- Python and Qt, Dart and Flutter, - JavaScript and Electron, anything. Worse yet, the exact same problem - existed in JavaFX as well, but for entirely different reasons [4]. That - made it appear as if this was some font problem intrinsic to Java - itself. Instead, they were both the most trivial of bugs that - nonetheless persisted for years, making Java look terrible on Ubuntu or - any other Debian-based distribution. I wonder how many others just - walked away -- from NetBeans, from JavaFX, from Java -- in silence. + Personally, it's why I was ready to abandon the platform. The same + problem occurred in JavaFX as well, but for different reasons [4]. That + made it appear as if this was something intrinsic to Java itself. + Instead, they were both simple bugs that nonetheless persisted for + years, making Java and JavaFX look bad on Ubuntu and any other Debian- + based distribution. - Let's fix this. I don't think we can wait until OpenJDK 12. Let me know - if I can help in any way. + I don't think we can wait for OpenJDK 12. Let me know how I can help. Thank you, John [1] https://github.com/JetBrains/jdk8u_jdk [2] https://launchpad.net/~no1wantdthisname/+archive/ubuntu/openjdk-fontfix [3] https://cwiki.apache.org/confluence/display/NETBEANS/Font+Rendering+Issues [4] https://github.com/javafxports/openjdk-jfx/issues/229 -- 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 critical JDK-8212071 font fix to OpenJDK 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1815119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815119] Re: Backport critical JDK-8212071 font fix to OpenJDK 11
** 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 first set of Font Demo screenshots for a quick view of the problem in the "Before" and "After" images. OpenJDK FreeType Font Fix https://github.com/jgneff/openjdk-freetype The page above links to the official report in the Java Bug System: Need to set the FreeType LCD Filter to reduce fringing https://bugs.openjdk.java.net/browse/JDK-8212071 The consequences of this bug have been far-reaching. It's one of the - reasons why JetBrains created their own fork of the JDK to included in + reasons why JetBrains created their own fork of the JDK to include in IntelliJ IDEA [1]; why we have popular forks of the JDK just to fix the fonts on Ubuntu [2]; and why the snap for NetBeans 10 now ships with sub-pixel rendering entirely disabled by default [3], reverting to grayscale anti-aliasing. Personally it's why, after programming in Java since 1996, I was ready to abandon the platform completely for any other alternative that could simply get the fonts right -- Python and Qt, Dart and Flutter, JavaScript and Electron, anything. Worse yet, the exact same problem existed in JavaFX as well, but for entirely different reasons [4]. That made it appear as if this was some font problem intrinsic to Java itself. Instead, they were both the most trivial of bugs that nonetheless persisted for years, making Java look terrible on Ubuntu or any other Debian-based distribution. I wonder how many others just walked away -- from NetBeans, from JavaFX, from Java -- in silence. Let's fix this. I don't think we can wait until OpenJDK 12. Let me know if I can help in any way. Thank you, John [1] https://github.com/JetBrains/jdk8u_jdk [2] https://launchpad.net/~no1wantdthisname/+archive/ubuntu/openjdk-fontfix [3] https://cwiki.apache.org/confluence/display/NETBEANS/Font+Rendering+Issues [4] https://github.com/javafxports/openjdk-jfx/issues/229 -- 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 critical JDK-8212071 font fix to OpenJDK 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1815119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815119] [NEW] Backport critical JDK-8212071 font fix to OpenJDK 11
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 Font Demo screenshots for a quick view of the problem in the "Before" and "After" images. OpenJDK FreeType Font Fix https://github.com/jgneff/openjdk-freetype The page above links to the official report in the Java Bug System: Need to set the FreeType LCD Filter to reduce fringing https://bugs.openjdk.java.net/browse/JDK-8212071 The consequences of this bug have been far-reaching. It's one of the reasons why JetBrains created their own fork of the JDK to included in IntelliJ IDEA [1]; why we have popular forks of the JDK just to fix the fonts on Ubuntu [2]; and why the snap for NetBeans 10 now ships with sub-pixel rendering entirely disabled by default [3], reverting to grayscale anti-aliasing. Personally it's why, after programming in Java since 1996, I was ready to abandon the platform completely for any other alternative that could simply get the fonts right -- Python and Qt, Dart and Flutter, JavaScript and Electron, anything. Worse yet, the exact same problem existed in JavaFX as well, but for entirely different reasons [4]. That made it appear as if this was some font problem intrinsic to Java itself. Instead, they were both the most trivial of bugs that nonetheless persisted for years, making Java look terrible on Ubuntu or any other Debian-based distribution. I wonder how many others just walked away -- from NetBeans, from JavaFX, from Java -- in silence. Let's fix this. I don't think we can wait until OpenJDK 12. Let me know if I can help in any way. Thank you, John [1] https://github.com/JetBrains/jdk8u_jdk [2] https://launchpad.net/~no1wantdthisname/+archive/ubuntu/openjdk-fontfix [3] https://cwiki.apache.org/confluence/display/NETBEANS/Font+Rendering+Issues [4] https://github.com/javafxports/openjdk-jfx/issues/229 ** Affects: openjdk-lts (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/1815119 Title: Backport critical JDK-8212071 font fix to OpenJDK 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1815119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721852] Re: JavaFX support is in Oracle JDK 9 but missing in Ubuntu OpenJDK 9
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: Oracle Java SE Support Roadmap http://www.oracle.com/technetwork/java/eol-135779.html The Future of JavaFX and Other Java Client Roadmap Updates https://blogs.oracle.com/java-platform-group/the-future-of-javafx-and-other-java-client-roadmap-updates The associated white paper has more details: Java Client Roadmap Update http://www.oracle.com/technetwork/java/javase/javaclientroadmapupdate2018mar-4414431.pdf The white paper includes the following items in its Executive Summary: • JavaFX new fixes will continue to be supported on Java SE 8 through March 2022 and removed from Java SE 11. • Swing and AWT will continue to be supported on Java SE 8 through at least March 2025, and on Java SE 11 (18.9 LTS) through at least September 2026. • Oracle has begun conversations with interested parties in the Java ecosystem on the stewardship of JavaFX, Swing and AWT beyond the above referenced timeframes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721852 Title: JavaFX support is in Oracle JDK 9 but missing in Ubuntu OpenJDK 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-9/+bug/1721852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978296] Re: Tags section hidden on Time Tracker Preferences dialog
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 "preferences.ui" file for Hamster on Ubuntu 16.04: $ cd /usr/share/hamster-applet/ $ diff preferences.ui.old preferences.ui 607c607 < False --- > True Line 607 is found just after the "tags_frame" object: ... True 1 ** Bug watch added: github.com/projecthamster/hamster/issues #206 https://github.com/projecthamster/hamster/issues/206 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/978296 Title: Tags section hidden on Time Tracker Preferences dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hamster-applet/+bug/978296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721852] Re: JavaFX support is in Oracle JDK 9 but missing in Ubuntu OpenJDK 9
** 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. https://bugs.launchpad.net/bugs/1721852 Title: JavaFX support is in Oracle JDK 9 but missing in Ubuntu OpenJDK 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-9/+bug/1721852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721852] Re: JavaFX support is in upstream OpenJDK 9 but missing in Ubuntu OpenJDK 9
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 from Oracle and is in fact missing the JavaFX support. So the upstream OpenJDK does not contain JavaFX support after all. It appears from the mailing list that JavaFX will be included in some later release. Oracle JDK http://www.oracle.com/technetwork/java/javase/downloads/index.html $ ~/opt/jdk-9.0.1/bin/java -version java version "9.0.1" Java(TM) SE Runtime Environment (build 9.0.1+11) Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode) $ ~/opt/jdk-9.0.1/bin/java -jar HelloWorld.jar Hello World! Hello World! Upstream OpenJDK http://jdk.java.net/9/ $ ~/opt/openjdk-9.0.1/bin/java -version openjdk version "9.0.1" OpenJDK Runtime Environment (build 9.0.1+11) OpenJDK 64-Bit Server VM (build 9.0.1+11, mixed mode) $ ~/opt/openjdk-9.0.1/bin/java -jar HelloWorld.jar Error: Could not find or load main class helloworld.HelloWorld Caused by: java.lang.NoClassDefFoundError: javafx/application/Application -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721852 Title: JavaFX support is in upstream OpenJDK 9 but missing in Ubuntu OpenJDK 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-9/+bug/1721852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721852] Re: JavaFX support is in upstream OpenJDK 9 but missing in Ubuntu OpenJDK 9
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- d...@openjdk.java.net) is to use the Oracle JDK 9 build as the boot JDK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721852 Title: JavaFX support is in upstream OpenJDK 9 but missing in Ubuntu OpenJDK 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-9/+bug/1721852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721852] Re: JavaFX support is in upstream OpenJDK 9 but missing in Ubuntu OpenJDK 9
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 Packaging it with the OpenJDK is described here: Integration with OpenJDK 9 https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX#BuildingOpenJFX-IntegrationwithOpenJDK9 which says: -- Build OpenJFX first. Configure the JDK with the following addition: --with-import-modules=_path_to_openjfx/9-dev/build/modular-sdk Then build the JDK as normal. -- I built OpenJFX many times, but I have not yet tried this new procedure for including it in OpenJDK 9. I'm willing to help and try it myself if you run into any problems. I'm eager to see JavaFX finally integrated into the OpenJDK packages on Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721852 Title: JavaFX support is in upstream OpenJDK 9 but missing in Ubuntu OpenJDK 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-9/+bug/1721852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722410] Re: java9: -version output seems wrong: "9-Ubuntu"
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. https://bugs.launchpad.net/bugs/1722410 Title: java9: -version output seems wrong: "9-Ubuntu" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-9/+bug/1722410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721852] [NEW] JavaFX support is in upstream OpenJDK 9 but missing in Ubuntu OpenJDK 9
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. Upstream Release (JavaFX support included): JDK 9 General-Availability Release http://jdk.java.net/9/ $ ~/opt/jdk-9/bin/java -version java version "9" Java(TM) SE Runtime Environment (build 9+181) Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode) $ ~/opt/jdk-9/bin/java -jar HelloWorld.jar Hello World! Hello World! Ubuntu Release (missing support for JavaFX): Package: openjdk-9-jre (9~b181-4) [universe] https://packages.ubuntu.com/artful/openjdk-9-jre $ /usr/lib/jvm/java-9-openjdk-amd64/bin/java -version openjdk version "9-Ubuntu" OpenJDK Runtime Environment (build 9-Ubuntu+0-9b181-4) OpenJDK 64-Bit Server VM (build 9-Ubuntu+0-9b181-4, mixed mode) $ /usr/lib/jvm/java-9-openjdk-amd64/bin/java -jar HelloWorld.jar Error: Could not find or load main class helloworld.HelloWorld Caused by: java.lang.NoClassDefFoundError: javafx/application/Application ** Affects: openjdk-9 (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/1721852 Title: JavaFX support is in upstream OpenJDK 9 but missing in Ubuntu OpenJDK 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-9/+bug/1721852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694596] Re: LiteOn NVMe issue
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694596 Title: LiteOn NVMe issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694596] Re: LiteOn NVMe issue
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: CX2-8B256-Q11 NVMe LITEON 256GB Current FW: 48811QD No Firmware Upgrade Needed(N01) I reinstalled Ubuntu but this time with the Hardware Enablement (HWE) kernel version 4.8.0.58.29 installed by Ubuntu 16.04.2, just to see whether the error happens again. My home directory is safe on a secondary drive this time. At this point, if the Lite-On drive fails as it did before, I guess I'll just buy the Samsung 960 EVO SSD (MZ-V6E250BW) as a replacement and see whether Dell will let me return the Lite-On Technology CX2 NVMe Series SSD (CX2-8B256) for a refund. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694596 Title: LiteOn NVMe issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694596] Re: LiteOn NVMe issue
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 Dell whether there's a way to apply the update without installing Windows over my current Ubuntu installation. For example, I thought I might use a WinPE bootable flash drive to apply the update: WinPE: Create USB Bootable drive https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-create-usb-bootable-drive -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694596 Title: LiteOn NVMe issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694596] Re: LiteOn NVMe issue
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 different errors on the root file system, all seemingly random. I included a couple of them in Comment #4 above. I think I've deleted the file that captured all of the errors. Even after recovering from the file system errors, it does seem that I lost some files, such as the icons in Thunderbird context menus and other random things. $ sudo nvme get-feature -f 0x0c -H /dev/nvme0 get-feature:0x0c (Autonomous Power State Transition), Current value: Autonomous Power State Transition Enable (APSTE): Disabled Auto PST Entries. Entry[ 0] . Idle Time Prior to Transition (ITPT): 5000 ms Idle Transition Power State (ITPS): 3 . Entry[ 1] . Idle Time Prior to Transition (ITPT): 5000 ms Idle Transition Power State (ITPS): 3 . Entry[ 2] . Idle Time Prior to Transition (ITPT): 5000 ms Idle Transition Power State (ITPS): 3 . Entry[ 3] . Idle Time Prior to Transition (ITPT): 1 ms Idle Transition Power State (ITPS): 4 . Entry[ 4] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 5] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 6] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 7] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 8] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 9] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[10] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[11] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[12] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[13] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[14] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[15] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[16] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[17] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[18] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[19] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[20] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[21] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[22] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[23] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0
[Bug 1694596] Re: LiteOn NVMe issue
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 revision 488110B, but otherwise it's the same drive model (CX2-8B256-Q11 NVMe LITEON 256GB). I had errors on the file system even after I disabled the APST support by adding "nvme_core.default_ps_max_latency_us=0" to the kernel parameters. Is there any chance that running for a month with the APST support could have made the errors continue even after disabling it? I will post an update with Dell's response before the end of the month. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694596 Title: LiteOn NVMe issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694596] Re: LiteOn NVMe issue
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 reluctant to risk more data loss to double check. Note that I was running with the HWE kernel version 4.8 for a couple of months, but I didn't see the errors until I upgraded to 4.8.0-53, and then I saw the file system errors all the time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694596 Title: LiteOn NVMe issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694596] Re: LiteOn NVMe issue
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 | grep ubuntu /dev/mapper/ubuntu--vg-root on / type ext4 (rw,relatime,errors=remount-ro,data=ordered) $ sudo cryptsetup status nvme0n1p3_crypt /dev/mapper/nvme0n1p3_crypt is active and is in use. type:LUKS1 cipher: aes-xts-plain64 keysize: 512 bits device: /dev/nvme0n1p3 offset: 4096 sectors size:498063360 sectors mode:read/write flags: discards When the file system was re-mounted read-only due to errors, I booted Ubuntu 16.04.2 from a USB flash drive and ran "e2fsck" to repair the file system: ubuntu@ubuntu:~$ sudo e2fsck -pfv /dev/mapper/ubuntu--vg-root /dev/mapper/ubuntu--vg-root: recovering journal /dev/mapper/ubuntu--vg-root: Inodes that were part of a corrupted orphan linked list found. /dev/mapper/ubuntu--vg-root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) So then I ran the command again without the "-p" option, but with the "-y" option to answer "yes" to all questions, and the command fixed 329 errors: ubuntu@ubuntu:~$ sudo e2fsck -fvy /dev/mapper/ubuntu--vg-root e2fsck 1.42.13 (17-May-2015) Pass 1: Checking inodes, blocks, and sizes Inodes that were part of a corrupted orphan linked list found. Fix? yes [ ... 327 errors not shown ...] Free inodes count wrong (13486735, counted=13478898). Fix? yes /dev/mapper/ubuntu--vg-root: * FILE SYSTEM WAS MODIFIED * 1045518 inodes used (7.20%, out of 14524416) 2413 non-contiguous files (0.2%) 851 non-contiguous directories (0.1%) # of inodes with ind/dind/tind blocks: 27/27/27 Extent depth histogram: 975523/235 30224290 blocks used (52.03%, out of 58093568) 0 bad blocks 6 large files 838712 regular files 113346 directories 67 character device files 29 block device files 3 fifos 28 links 93308 symbolic links (69609 fast symbolic links) 44 sockets 1045537 files This is the second day I'm running with the Ubuntu 16.04 GA Linux kernel version 4.4.0-78 (instead of the HWE Linux kernel), and it still seems to be okay, but the problem can take a few days to appear. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694596 Title: LiteOn NVMe issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694596] Re: LiteOn NVMe APST issue
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 defined the "default_ps_max_latency_us" parameter to 6000. I only set it to a value of zero. Parameter "nvme_core.default_ps_max_latency_us" is not defined: 2017-04-04 Upgraded to 4.8.0-46.49 2017-04-24 Upgraded to 4.8.0-49.52 ← Adds NVMe APST support (LP: #1664602) 2017-05-01 Upgraded to 4.8.0-51.54 2017-05-16 Upgraded to 4.8.0-52.55 2017-05-25 Upgraded to 4.8.0-53.56 ← Errors on NVMe drive Parameter "nvme_core.default_ps_max_latency_us" is set to zero: 2017-05-29 Linux 4.8.0-53.56 (APST disabled) ← Running OK 2017-05-30 Linux 4.8.0-53.56 (APST disabled) ← Running OK 2017-05-31 Linux 4.8.0-53.56 (APST disabled) ← Errors on NVMe drive At this point, I switched from the Hardware Enablement (HWE) stack back to the original General Availability (GA) stack for the Linux kernel and X server on Ubuntu 16.04. 2017-05-31 Linux 4.4.0-78.90 (GA) ← Running OK so far 2017-06-01 Linux 4.4.0-78.90 (GA) ← Running OK so far I hope this change will help determine whether the errors are due to the drive itself or something in the Linux 4.8 upgrade. I guess we should close this bug report, or at least rename it. Thank you, John -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694596 Title: LiteOn NVMe APST issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
@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 : 10200 rtd3r : f4240 rtd3e : f4240 oaes: 0 oacs: 0x1f acl : 3 aerl: 3 frmw: 0x14 lpa : 0x2 elpe: 63 npss: 4 avscc : 0x1 apsta : 0x1 wctemp : 358 cctemp : 368 mtfa: 50 hmpre : 0 hmmin : 0 tnvmcap : 256060514304 unvmcap : 0 rpmbs : 0 sqes: 0x66 cqes: 0x44 nn : 1 oncs: 0x1f fuses : 0 fna : 0 vwc : 0x1 awun: 255 awupf : 7 nvscc : 1 acwu: 0 sgls: 0 ps0 : mp:8.00W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps1 : mp:4.00W operational enlat:5 exlat:5 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps2 : mp:2.10W operational enlat:5 exlat:5 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps3 : mp:0.1000W non-operational enlat:5000 exlat:5000 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps4 : mp:0.0100W non-operational enlat:5 exlat:10 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
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 B + 0 B FW Rev:48811QD -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
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 16.04.2 LTS amd64 ISO file. I didn't notice any file system errors until I upgraded to the "linux- image-4.8.0-53-generic" package on May 25, 2017. Below is my upgrade schedule showing when the errors occurred: 2017-04-04 Upgraded to 4.8.0-46.49 2017-04-24 Upgraded to 4.8.0-49.52 ← Adds NVMe APST support (LP: #1664602) 2017-05-01 Upgraded to 4.8.0-51.54 2017-05-16 Upgraded to 4.8.0-52.55 2017-05-25 Upgraded to 4.8.0-53.56 ← Started noticing errors on NVMe drive First my Thunderbird Lightning calendar database got corrupted so I couldn't add events. One time the system just froze, with the mouse cursor and keyboard not working. Yesterday, the root file system remounted read-only after waking from suspend. This morning I added "nvme_core.default_ps_max_latency_us=0" to the Grub configuration, and after repairing the file system errors with "e2fsck", everything seems to be working fine so far: /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash swapaccount=1 nvme_core.default_ps_max_latency_us=0" I'm considering moving back to the GA 16.04 kernel, just to be more conservative in my system updates. Is the general advice to use the HWE kernel only if we need support for some new hardware, but otherwise, stay on the GA kernel? Is there anything in Kernel version 4.8.0-53 that may have caused the problem or made it more likely to appear? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641801] Re: package uvtool-libvirt (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
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 install --reinstall qemu-kvm libvirt-bin $ sudo systemctl start apparmor.service $ sudo systemctl restart libvirt-bin and then: $ sudo apt-get install --reinstall uvtool uvtool-libvirt Now it all seems to be working again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641801 Title: package uvtool-libvirt (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1641801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1641801] Re: package uvtool-libvirt (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
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 fail, though, and also surprised it prompted me to file a bug report. I thought it was just going to send an automated crash report. I just rebooted, removed all of the orphaned packages, and cleaned up after the upgrade myself, and everything seems fine now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641801 Title: package uvtool-libvirt (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1641801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641801] [NEW] package uvtool-libvirt (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
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 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Nov 14 18:40:59 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-04 (469 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: uvtool Title: package uvtool-libvirt (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-11-15 (0 days ago) ** Affects: uvtool (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641801 Title: package uvtool-libvirt (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/1641801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043588] Re: sudo restart lxc-net does not kill/restart dnsmasq
*** 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 running with its old settings when lxc-net is restarted. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1043588 Title: sudo restart lxc-net does not kill/restart dnsmasq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1043588/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1043588] Re: sudo restart lxc-net does not kill/restart dnsmasq
*** 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 running with its old settings when lxc-net is restarted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043588 Title: sudo restart lxc-net does not kill/restart dnsmasq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1043588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Re: Xorg freezes visiting www.google.ca/nexus
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/901793 Title: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 824961] Re: Ubuntu 11.04 Server with encrypted LVM on dm RAID0 -- Incorrect metadata area header checksum - No volume groups found - ALERT! /dev/mapper/MachineName-root does not exist
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 a while... Found volume group p490 using metadata type lvm2 3 logical volume(s) in volume group p490 now active /scripts/local-top/cryptroot: line 1: can't open /dev/mapper/p490-root: no such file fsck from util-linux 2.20.1 fsck from util-linux 2.20.1 fsck from util-linux 2.20.1 /dev/mapper/p490-root: clean, 220625/1003680 files, 1770508/4006912 blocks (check after next mount) /dev/sda1: clean, 263/124496 files, 53854/248832 blocks /dev/mapper/p490-home: clean, 175868/13721600 files, 17080230/54867968 blocks /etc/crypttab: sda5_crypt UUID=497c7a02-64bf-496e-9cff-f0611c8c2490 none luks sdb3_crypt UUID=e35c4825-3fd1-4145-8b5c-33a6f64172ef none luks,noauto The system seems to boot normally after the message, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/824961 Title: Ubuntu 11.04 Server with encrypted LVM on dm RAID0 -- Incorrect metadata area header checksum - No volume groups found - ALERT! /dev/mapper/MachineName-root does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/824961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 682492] Re: Evince: Save Settings as default doesn't work
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 can download the patch into your home directory and apply it locally with something like: $ sudo apt-get install gnome-devel $ sudo apt-get build-dep evince $ apt-get source evince $ cd evince-3.2.1 $ patch -p1 ~/0001-Save-always-settings-that-can-bse-saved-as-default-i.patch $ ./configure $ make $ sudo make install This places the fixed Evince in /usr/local/bin, so you should pick it up right away. There is also a less invasive alternative to working around the bug using a simple Bash script, available here: https://bugzilla.gnome.org/show_bug.cgi?id=639003#c17 I would really like to see this fix included in the next release of Ubuntu. I switched to Ubuntu back in 2006, and I can think of no bug since then that has been more bothersome—even maddening—than this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/682492 Title: Evince: Save Settings as default doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/682492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Re: Xorg freezes visiting www.google.ca/nexus
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 running Unity 2D: http://www.google.ca/nexus I never encountered such freezes in the previous release of Ubuntu (11.04 natty). The freeze happens with both Mozilla Firefox 8.0 and Chromium 15.0.874.106 (Developer Build 107270 Linux). No updates to the screen occur (no clock updates, for example), but I can SSH into the system to gather information and reboot. There is usually no CPU activity, but one out of the four freezes yesterday had X using over 50 percent CPU usage during the freeze. I followed the instructions here: https://wiki.ubuntu.com/X/Troubleshooting/Freeze to capture the dmesg output and Xorg.0.log file for each of the four freezes yesterday. Below are the answers to the questions recommended on that page. Q: When did you upgrade to this version of Ubuntu? When did you first notice the freezes occurring? A: I upgraded about 3 weeks ago and first noticed the freezes about 2 weeks ago while using the Web browser. Q: How frequently do the freezes occur? How many per day would you say you experience? A: They occur about once per week, but yesterday I found a Web site (www.google.ca/nexus) that can cause the freeze each and every time it loads in a Web browser (Firefox and Chromium). Q: List the applications you typically have open at the time of the freeze. A: I usually have open at least the Web browser (Firefox or Chromium) and the Terminal. I may also have open GnuCash, a VirtualBox guest running Windows, NetBeans, and Thunderbird. Q: Think back to the last few times it froze. What activities were you doing in each of those times? A: The last four times it froze, I simply clicked a link to go to the site www.google.ca/nexus or loaded it directly from the address bar. Q: Do you have compiz enabled? Does the issue go away if you disable it? A: I am running Unity 2D, the Unity interface for non-accelerated graphics cards. I see compositing effects, so perhaps I'm running compiz. I'll look into disabling it. Q: If your system is a laptop, do you suspend/resume it? Had you resumed at some point prior to the freezes? A: My system is a Dell Precision 490 Workstation. I suspend it at night, but this freeze occurs even right after a fresh reboot after visiting the Google Nexus page. Additional information: $ lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 $ apt-cache policy xserver-xorg-video-nouveau xserver-xorg-video-nouveau: Installed: 1:0.0.16+git20110411+8378443-1 Candidate: 1:0.0.16+git20110411+8378443-1 Version table: *** 1:0.0.16+git20110411+8378443-1 0 500 http://ca.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status + --- + .tmp.unity.support.test.0: + + ApportVersion: 1.23-0ubuntu4 + Architecture: amd64 + CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,imgpng,gnomecompat,place,snap,regex,grid,move,session,vpswitch,unitymtgrabhandles,mousepoll,animation,wall,expo,ezoom,workarounds,fade,scale,unityshell] + CompositorRunning: None + DistUpgraded: Log time: 2011-11-22 22:41:56.988316 + DistroCodename: oneiric + DistroRelease: Ubuntu 11.10 + DistroVariant: ubuntu + DkmsStatus: + virtualbox, 4.1.2, 3.0.0-13-generic, x86_64: installed + virtualbox, 4.1.2, 3.0.0-14-generic, x86_64: installed + ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu + GraphicsCard: + nVidia Corporation NV43GL [Quadro FX 550] [10de:014d] (rev a2) (prog-if 00 [VGA controller]) +Subsystem: nVidia Corporation Device [10de:0349] + InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110426) + MachineType: Dell Inc. Precision WorkStation 490 + Package: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 + PackageArchitecture: amd64 + ProcEnviron: + LC_TIME=en_DK.UTF-8 + LANGUAGE=en_CA:en + PATH=(custom, user) + LANG=en_CA.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-14-generic root=/dev/mapper/hostname-root ro quiet + ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 + Tags: oneiric running-unity ubuntu + Uname: Linux 3.0.0-14-generic x86_64 + UpgradeStatus: Upgraded to oneiric on 2011-11-23 (19 days ago) + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare + dmi.bios.date: 04/25/2008 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A08 + dmi.board.name: 0F9382 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 7 + dmi.chassis.vendor: Dell Inc. + dmi.modalias:
[Bug 901793] BootLog.gz
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 freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] CurrentDmesg.txt
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 Title: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Dependencies.txt
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 Title: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] DpkgLog.txt
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: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] GconfCompiz.txt
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 Title: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] LightdmLog.txt
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 Title: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Lspci.txt
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 freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Lsusb.txt
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 freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] MonitorsGlobal.xml.txt
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. https://bugs.launchpad.net/bugs/901793 Title: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] ProcCpuinfo.txt
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 Title: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] ProcInterrupts.txt
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. https://bugs.launchpad.net/bugs/901793 Title: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] ProcModules.txt
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 Title: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] UdevDb.txt
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 freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] UdevLog.txt
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: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] UnitySupportTest.txt
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. https://bugs.launchpad.net/bugs/901793 Title: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] XorgLog.txt
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: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] XorgLogOld.txt
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 Title: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Xrandr.txt
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 freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] xdpyinfo.txt
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: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] MonitorsUser.xml.txt
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. https://bugs.launchpad.net/bugs/901793 Title: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Re: Xorg freezes visiting www.google.ca/nexus
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 to the most recent Linux 3.0.0-14-generic #23-Ubuntu kernel. At least until Google updates that Nexus page, it seems I can cause the freeze each and every time. -- 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 freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Re: Xorg freezes visiting www.google.ca/nexus
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 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+attachment/2630800/+files/dmesg-2.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 freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Re: Xorg freezes visiting www.google.ca/nexus
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 [ 423.684009] [drm] nouveau :07:00.0: reloc wait_idle failed: -16 [ 423.684014] [drm] nouveau :07:00.0: reloc apply: -16 [ 426.724013] [drm] nouveau :07:00.0: reloc wait_idle failed: -16 [ 426.724022] [drm] nouveau :07:00.0: reloc apply: -16 ** Attachment added: dmesg-3.txt https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+attachment/2630801/+files/dmesg-3.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 freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Re: Xorg freezes visiting www.google.ca/nexus
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] nouveau :07:00.0: IP: 0x28, Opcode: 0x00500060 [ 203.800081] [drm] nouveau :07:00.0: 0x40030C = 0x0029 ** Attachment added: dmesg-4.txt https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+attachment/2630802/+files/dmesg-4.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 freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Re: Xorg freezes visiting www.google.ca/nexus
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 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+attachment/2630816/+files/dmesg-5.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 freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Re: Xorg freezes visiting www.google.ca/nexus
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 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+attachment/2630818/+files/Xorg.0.log-2.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 freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Re: Xorg freezes visiting www.google.ca/nexus
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 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+attachment/2630819/+files/Xorg.0.log-3.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 freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Re: Xorg freezes visiting www.google.ca/nexus
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 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+attachment/2630820/+files/Xorg.0.log-4.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 freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Re: Xorg freezes visiting www.google.ca/nexus
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 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+attachment/2630821/+files/Xorg.0.log-5.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 freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Re: Xorg freezes visiting www.google.ca/nexus
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 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+attachment/2630799/+files/dmesg-1.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 freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] Re: Xorg freezes visiting www.google.ca/nexus
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 /var/lib/xkb/server-2B6FA8C3EA6AA113DC680288825EF0846851A010.xkm [ 146.352] (II) XKB: reuse xkmfile /var/lib/xkb/server-2B6FA8C3EA6AA113DC680288825EF0846851A010.xkm ** Attachment added: Xorg.0.log-1.txt https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+attachment/2630817/+files/Xorg.0.log-1.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 freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901793] [NEW] Xorg freezes visiting www.google.ca/nexus
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 previous release of Ubuntu (11.04 natty). The freeze happens with both Mozilla Firefox 8.0 and Chromium 15.0.874.106 (Developer Build 107270 Linux). No updates to the screen occur (no clock updates, for example), but I can SSH into the system to gather information and reboot. There is usually no CPU activity, but one out of the four freezes yesterday had X using over 50 percent CPU usage during the freeze. I followed the instructions here: https://wiki.ubuntu.com/X/Troubleshooting/Freeze to capture the dmesg output and Xorg.0.log file for each of the four freezes yesterday. Below are the answers to the questions recommended on that page. Q: When did you upgrade to this version of Ubuntu? When did you first notice the freezes occurring? A: I upgraded about 3 weeks ago and first noticed the freezes about 2 weeks ago while using the Web browser. Q: How frequently do the freezes occur? How many per day would you say you experience? A: They occur about once per week, but yesterday I found a Web site (www.google.ca/nexus) that can cause the freeze each and every time it loads in a Web browser (Firefox and Chromium). Q: List the applications you typically have open at the time of the freeze. A: I usually have open at least the Web browser (Firefox or Chromium) and the Terminal. I may also have open GnuCash, a VirtualBox guest running Windows, NetBeans, and Thunderbird. Q: Think back to the last few times it froze. What activities were you doing in each of those times? A: The last four times it froze, I simply clicked a link to go to the site www.google.ca/nexus or loaded it directly from the address bar. Q: Do you have compiz enabled? Does the issue go away if you disable it? A: I am running Unity 2D, the Unity interface for non-accelerated graphics cards. I see compositing effects, so perhaps I'm running compiz. I'll look into disabling it. Q: If your system is a laptop, do you suspend/resume it? Had you resumed at some point prior to the freezes? A: My system is a Dell Precision 490 Workstation. I suspend it at night, but this freeze occurs even right after a fresh reboot after visiting the Google Nexus page. Additional information: $ lsb_release -rd Description:Ubuntu 11.10 Release:11.10 $ apt-cache policy xserver-xorg-video-nouveau xserver-xorg-video-nouveau: Installed: 1:0.0.16+git20110411+8378443-1 Candidate: 1:0.0.16+git20110411+8378443-1 Version table: *** 1:0.0.16+git20110411+8378443-1 0 500 http://ca.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: xserver-xorg-video-nouveau (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/901793 Title: Xorg freezes visiting www.google.ca/nexus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 358316] Re: Draw order causes panels to be obscured on Window resize
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 resize https://bugs.launchpad.net/bugs/358316 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 358316] Re: Draw order causes panels to be obscured on Window resize
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 275604] Re: Hard disk graph in panel applet constantly reads 0%
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 another hard drive. The GNOME System Monitor Disk graph showed no activity and always read 0% in use. In case it helps, here are a few cat /proc/diskstats | grep 'sda5' where /dev/sda5 was being read: 85 sda5 508674 162562 89202476 2621612 217217 396877 4915240 4481024 0 1655820 7106140 85 sda5 508902 162639 89257316 2621928 217217 396877 4915240 4481024 0 1656068 7106452 85 sda5 509192 162834 89325884 2622336 217217 396877 4915240 4481024 1 1656384 7106860 85 sda5 509435 162996 89380980 2622720 217217 396877 4915240 4481024 0 1656648 7107244 85 sda5 509690 163158 89439404 2623040 217217 396877 4915240 4481024 0 1656888 7107564 And here are a few cat /proc/diskstats | grep 'sdb3' where /dev/sdb3 was being written: 8 19 sdb3 910 4335 8085 39740 1442684 8492129 79484712 34341148 50 935392 34797252 8 19 sdb3 910 4335 8085 39740 1443024 8507159 79596096 34435400 92 936644 34899536 8 19 sdb3 910 4335 8085 39740 1443300 8513908 79684296 34544964 0 937684 35008688 8 19 sdb3 911 4335 8093 39748 1445398 8517307 79728232 34546388 3 938172 35010120 8 19 sdb3 911 4335 8093 39748 1446796 8537921 79853568 34583604 93 939416 35063652 -- Hard disk graph in panel applet constantly reads 0% https://bugs.launchpad.net/bugs/275604 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 287644] Re: tomcat hangs on startup if ssl is enabled
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 error in the log file: 25-Nov-2008 9:15:58 AM org.apache.catalina.core.AprLifecycleListener init INFO: Loaded APR based Apache Tomcat Native library 1.1.12. 25-Nov-2008 9:15:58 AM org.apache.catalina.core.AprLifecycleListener init INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. 25-Nov-2008 9:15:59 AM org.apache.coyote.http11.Http11AprProtocol init SEVERE: Error initializing endpoint java.lang.Exception: Socket bind failed: [22] Invalid argument ... which apparently involves the IPv6 networking support and has been fixed by Apache: Socket bind fails on tomcat startup when using apr https://issues.apache.org/bugzilla/show_bug.cgi?id=43327 There's a work-around for that, which I haven't tried, of removing IPv6 support in /etc/modprobe.d/aliases, but I think I'll just uninstall libtcnative-1 and wait. I was hoping APR would speed up Tomcat's startup time (perhaps with native random number generation?), but it seems to be about the same. -- tomcat hangs on startup if ssl is enabled https://bugs.launchpad.net/bugs/287644 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205254] Re: python-policyd-spf failing on AOL SPF records.
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]; Mar 28 13:45:29 ldc1042 policyd-spf[4559]: access neither permitted nor denied:Mail From client-ip=63.229.3.151; helo=www.commspeak.com; [EMAIL PROTECTED]; [EMAIL PROTECTED]; I also no longer receive the error message, Message parser reports malformed message packet, when getting the DNS TXT records from the command line: [EMAIL PROTECTED]:~$ host -t txt aol.com ;; Truncated, retrying in TCP mode. aol.com descriptive text spf2.0/pra ip4:152.163.225.0/24 ip4:205.188.139.0/24 ip4:205.188.144.0/24 ip4:205.188.156.0/23 ip4:205.188.159.0/24 ip4:64.12.136.0/23 ip4:64.12.138.0/24 ip4:64.12.143.99/32 ip4:64.12.143.100/32 ip4:64.12.143.101/32 ptr:mx.aol.com ?all aol.com descriptive text v=spf1 ip4:152.163.225.0/24 ip4:205.188.139.0/24 ip4:205.188.144.0/24 ip4:205.188.156.0/23 ip4:205.188.159.0/24 ip4:64.12.136.0/23 ip4:64.12.138.0/24 ip4:64.12.143.99/32 ip4:64.12.143.100/32 ip4:64.12.143.101/32 ptr:mx.aol.com ?all John -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205254] Re: python-policyd-spf failing on AOL SPF records.
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 added warn_if_reject: main.cf --- smtpd_recipient_restrictions = ... warn_if_reject check_policy_service unix:private/policy-spf ... I'm asking Hostway (my dedicated server provider) whether they know why I'm getting the error, Message parser reports malformed message packet on the UDP DNS response. I still get the error even with the firewall disabled. I don't get the error on other machines in other locations. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205254] Re: python-policyd-spf failing on AOL SPF records.
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 https://bugs.launchpad.net/bugs/205254. policy-spf unix - n n - - spawn user=nobody argv=/usr/bin/policyd-spf /etc/python-policyd-spf/policyd-spf.conf That seems to do the trick! I faked an e-mail message from AOL and got this: Mar 24 14:56:12 ldc1042 postfix/smtpd[26624]: connect from www.commspeak.com[63.229.3.151] Mar 24 14:56:13 ldc1042 policyd-spf[26626]: :HELO client-ip=63.229.3.151; helo=www.commspeak.com; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Mar 24 14:56:13 ldc1042 policyd-spf[26626]: SPF Temporary Error: DNS Ran off end of data:Mail From client-ip=63.229.3.151; helo=www.commspeak.com; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Mar 24 14:56:13 ldc1042 postfix/smtpd[26624]: 390801400FF: client=www.commspeak.com[63.229.3.151] ... Mar 24 14:56:13 ldc1042 postfix/smtpd[26624]: disconnect from www.commspeak.com[63.229.3.151] No more NOQUEUE: reject on the SPF Temporary Error. I'm also receiving valid AOL messages now, too. I'm waiting to hear back from Hostway about the malformed UDP DNS response. Thank you, John -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205254] Re: python-policyd-spf failing on AOL SPF records.
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 below are getting DNS from the routers, which proxy normal UDP DNS requests (not TCP, and sometimes not TXT requests) to their upstream name servers (obtained by DHCP). (1) Machine behind router #1: $ host -t txt aol.com ;; connection timed out; no servers could be reached (2) Machine behind router #2: $ host -t txt aol.com ;; Truncated, retrying in TCP mode. ;; Connection to 192.168.0.1#53(192.168.0.1) for aol.com failed: connection refused. (3) Machine behind router #3: $ host -t txt aol.com aol.com descriptive text spf2.0/pra ip4:152.163.225.0/24 ip4:205.188.139.0/24 ip4:205.188.144.0/24 ip4:205.188.156.0/23 ip4:205.188.159.0/24 ip4:64.12.136.0/23 ip4:64.12.138.0/24 ip4:64.12.143.99/32 ip4:64.12.143.100/32 ip4:64.12.143.101/32 ptr:mx.aol.com ?all $ host -t txt aol.com aol.com descriptive text v=spf1 ip4:152.163.225.0/24 ip4:205.188.139.0/24 ip4:205.188.144.0/24 ip4:205.188.156.0/23 ip4:205.188.159.0/24 ip4:64.12.136.0/23 ip4:64.12.138.0/24 ip4:64.12.143.99/32 ip4:64.12.143.100/32 ip4:64.12.143.101/32 ptr:mx.aol.com ?all Notice that it randomly gets one or the other of the two possible TXT records without any errors, but it never gets both. (4) Machine with direct connection (no NAT router): [EMAIL PROTECTED]:/etc/postfix$ host -t txt aol.com ;; Warning: Message parser reports malformed message packet. ;; Truncated, retrying in TCP mode. aol.com descriptive text v=spf1 ip4:152.163.225.0/24 ip4:205.188.139.0/24 ip4:205.188.144.0/24 ip4:205.188.156.0/23 ip4:205.188.159.0/24 ip4:64.12.136.0/23 ip4:64.12.138.0/24 ip4:64.12.143.99/32 ip4:64.12.143.100/32 ip4:64.12.143.101/32 ptr:mx.aol.com ?all aol.com descriptive text spf2.0/pra ip4:152.163.225.0/24 ip4:205.188.139.0/24 ip4:205.188.144.0/24 ip4:205.188.156.0/23 ip4:205.188.159.0/24 ip4:64.12.136.0/23 ip4:64.12.138.0/24 ip4:64.12.143.99/32 ip4:64.12.143.100/32 ip4:64.12.143.101/32 ptr:mx.aol.com ?all That's the one at Hostway with the malformed response which started all this. It seems as more things get stuffed into the DNS TXT records, this could become more of a problem. Thanks, John -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205254] Re: python-policyd-spf failing on AOL SPF records.
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 spf2.0/pra ip4:152.163.225.0/24 ip4:205.188.139.0/24
ip4:205.188.144.0/24 ip4:205.188.156.0/23 ip4:205.188.159.0/24
ip4:64.12.136.0/23 ip4:64.12.138.0/24 ip4:64.12.143.99/32 ip4:64.12.143.100/32
ip4:64.12.143.101/32 ptr:mx.aol.com ?all
aol.com descriptive text v=spf1 ip4:152.163.225.0/24 ip4:205.188.139.0/24
ip4:205.188.144.0/24 ip4:205.188.156.0/23 ip4:205.188.159.0/24
ip4:64.12.136.0/23 ip4:64.12.138.0/24 ip4:64.12.143.99/32 ip4:64.12.143.100/32
ip4:64.12.143.101/32 ptr:mx.aol.com ?all
Then a direct TCP-only request, which works fine:
[EMAIL PROTECTED]:~$ host -T -t txt aol.com
aol.com descriptive text spf2.0/pra ip4:152.163.225.0/24 ip4:205.188.139.0/24
ip4:205.188.144.0/24 ip4:205.188.156.0/23 ip4:205.188.159.0/24
ip4:64.12.136.0/23 ip4:64.12.138.0/24 ip4:64.12.143.99/32 ip4:64.12.143.100/32
ip4:64.12.143.101/32 ptr:mx.aol.com ?all
aol.com descriptive text v=spf1 ip4:152.163.225.0/24 ip4:205.188.139.0/24
ip4:205.188.144.0/24 ip4:205.188.156.0/23 ip4:205.188.159.0/24
ip4:64.12.136.0/23 ip4:64.12.138.0/24 ip4:64.12.143.99/32 ip4:64.12.143.100/32
ip4:64.12.143.101/32 ptr:mx.aol.com ?all
Then on the same machine, asking spf.py to test an AOL address (using
the client IP address and HELO name from the Postfix log files):
[EMAIL PROTECTED]:~$ python /usr/share/python-support/python-spf/spf.py
64.12.138.200 [EMAIL PROTECTED] imr-m06.mx.aol.com
('temperror', 451, 'SPF Temporary Error: DNS Ran off end of data')
That's the same error I'm getting in the mail log. Then on the same
machine, asking spf.py just to get the AOL SPF records:
[EMAIL PROTECTED]:~$ python /usr/share/python-support/python-spf/spf.py aol.com
Traceback (most recent call last):
File /usr/share/python-support/python-spf/spf.py, line 1621, in module
print q.dns_spf(sys.argv[1])
File /usr/share/python-support/python-spf/spf.py, line 1010, in dns_spf
a = [t for t in self.dns_txt(domain) if RE_SPF.match(t)]
File /usr/share/python-support/python-spf/spf.py, line 1045, in dns_txt
return [''.join(a) for a in self.dns(domainname, 'TXT')]
File /usr/share/python-support/python-spf/spf.py, line 1150, in dns
for k, v in DNSLookup(name, qtype, self.strict):
File /usr/share/python-support/python-spf/spf.py, line 105, in DNSLookup
raise TempError, 'DNS ' + str(x)
__main__.TempError: DNS Ran off end of data
I get the same thing running policyd-spf directly:
[EMAIL PROTECTED]:~$ policyd-spf
client_address=64.12.138.200
helo_name=imr-m06.mx.aol.com
[EMAIL PROTECTED]
[EMAIL PROTECTED]
action=defer_if_permit Received-SPF: Temperror (SPF Temporary Error: DNS
Ran off end of data) Mail From client-ip=64.12.138.200;
helo=imr-m06.mx.aol.com; [EMAIL PROTECTED];
[EMAIL PROTECTED];
Do you get the same results?
Thanks,
John
** Changed in: pyspf (Ubuntu)
Status: Invalid = New
--
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.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205254] Re: python-policyd-spf failing on AOL SPF records.
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 (ldc1042), I get:
[EMAIL PROTECTED]:~$ host -t txt aol.com
;; Warning: Message parser reports malformed message packet.
;; Truncated, retrying in TCP mode.
aol.com descriptive text v=spf1 ... ptr:mx.aol.com ?all
aol.com descriptive text spf2.0/pra ... ptr:mx.aol.com ?all
On the machine that works (gx110), I get:
[EMAIL PROTECTED]:~$ host -t txt aol.com
;; Truncated, retrying in TCP mode.
aol.com descriptive text spf2.0/pra ... ptr:mx.aol.com ?all
aol.com descriptive text v=spf1 ... ptr:mx.aol.com ?all
with no Warning: Message parser reports malformed message packet
error. More importantly, I also get:
[EMAIL PROTECTED]:~$ python /usr/share/python-support/python-spf/spf.py
64.12.138.200 [EMAIL PROTECTED] imr-m06.mx.aol.com
('pass', 250, 'sender SPF authorized')
So now I need to figure out why my Hostway dedicated server would be
getting a malformed DNS response by UDP.
Thank you,
John
--
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.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205254] [NEW] python-policyd-spf failing on AOL SPF records.
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 i686 GNU/Linux ** Affects: pyspf (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205254] Re: python-policyd-spf failing on AOL SPF records.
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205254] Re: python-policyd-spf failing on AOL SPF records.
** 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: Message parser reports malformed message packet. + ;; Truncated, retrying in TCP mode. + aol.com descriptive text v=spf1 ip4:152.163.225.0/24 ip4:205.188.139.0/24 + ip4:205.188.144.0/24 ip4:205.188.156.0/23 ip4:205.188.159.0/24 + ip4:64.12.136.0/23 ip4:64.12.138.0/24 ip4:64.12.143.99/32 + ip4:64.12.143.100/32 ip4:64.12.143.101/32 ptr:mx.aol.com ?all + aol.com descriptive text spf2.0/pra ip4:152.163.225.0/24 + ip4:205.188.139.0/24 ip4:205.188.144.0/24 ip4:205.188.156.0/23 + ip4:205.188.159.0/24 ip4:64.12.136.0/23 ip4:64.12.138.0/24 + ip4:64.12.143.99/32 ip4:64.12.143.100/32 ip4:64.12.143.101/32 + ptr:mx.aol.com ?all + + Here is the timeout getting the TXT records on www.commspeak.com, + presumably because they're dropped by intervening routers: + + $ host -t txt aol.com + ;; connection timed out; no servers could be reached + + The Postfix configuration on both machines is: + + main.cf + --- + smtpd_recipient_restrictions = + ... + warn_if_reject check_policy_service unix:private/policy-spf + ... + + master.cf + - + ... + # Python Sender Policy Framework (SPF) Service + policy-spf unix - n n - - spawn + user=nobody argv=/usr/bin/policyd-spf + + In the Postfix log files, I get the following on www.volano.com: + + Mar 14 11:24:39 ldc1042 postfix/smtpd[8296]: connect from + imr-m06.mx.aol.com[64.12.138.200] + Mar 14 11:24:39 ldc1042 policyd-spf[8298]: :HELO client-ip=64.12.138.200; + helo=imr-m06.mx.aol.com; [EMAIL PROTECTED]; + [EMAIL PROTECTED]; + Mar 14 11:24:39 ldc1042 policyd-spf[8298]: SPF Temporary Error: + DNS Ran off end of data:Mail From client-ip=64.12.138.200; + helo=imr-m06.mx.aol.com; [EMAIL PROTECTED]; + [EMAIL PROTECTED]; + Mar 14 11:24:39 ldc1042 postfix/smtpd[8296]: NOQUEUE: reject: RCPT + from imr-m06.mx.aol.com[64.12.138.200]: 450 4.7.1 [EMAIL PROTECTED]: + Recipient address rejected: Received-SPF: Temperror (SPF Temporary + Error: DNS Ran off end of data) Mail From client-ip=64.12.138.200; + helo=imr-m06.mx.aol.com; [EMAIL PROTECTED]; + [EMAIL PROTECTED]; ; from=[EMAIL PROTECTED] to=[EMAIL PROTECTED] + proto=ESMTP helo=imr-m06.mx.aol.com + Mar 14 11:24:40 ldc1042 postfix/smtpd[8296]: disconnect from + imr-m06.mx.aol.com[64.12.138.200] + + On www.commspeak.com I get: + + Mar 14 09:24:07 www postfix/smtpd[2882]: connect from + imr-m06.mx.aol.com[64.12.138.200] + Mar 14 09:24:08 www policyd-spf[2886]: :HELO client-ip=64.12.138.200; + helo=imr-m06.mx.aol.com; [EMAIL PROTECTED]; + [EMAIL PROTECTED]; + Mar 14 09:24:38 www policyd-spf[2886]: SPF Temporary Error: DNS + Timeout:Mail From client-ip=64.12.138.200; helo=imr-m06.mx.aol.com; + [EMAIL PROTECTED]; [EMAIL PROTECTED]; + Mar 14 09:24:38 www postfix/smtpd[2882]: NOQUEUE: reject: RCPT from + imr-m06.mx.aol.com[64.12.138.200]: 450 4.7.1 [EMAIL PROTECTED]: + Recipient address rejected: Received-SPF: Temperror (SPF Temporary Error: + DNS Timeout) Mail From client-ip=64.12.138.200; helo=imr-m06.mx.aol.com; + [EMAIL PROTECTED]; [EMAIL PROTECTED]; + ; from=[EMAIL PROTECTED] to=[EMAIL PROTECTED] proto=ESMTP + helo=imr-m06.mx.aol.com + Mar 14 09:24:40 www postfix/smtpd[2882]: disconnect from + imr-m06.mx.aol.com[64.12.138.200] 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 i686 GNU/Linux -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205254] Re: python-policyd-spf failing on AOL SPF records.
I edited the original Bug Description to provide additional information. (I reported the bug through apport-cli but didn't want to use elinks to enter all the info.) Oh, one more change -- the log files shown above are when I did not have warn_if_reject for the SPF checks. The log files correspond 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 of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205254] Re: python-policyd-spf failing on AOL SPF records.
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 text v=spf1 ip4:152.163.225.0/24 ip4:205.188.139.0/24 ip4:205.188.144.0/24 ip4:205.188.156.0/23 ip4:205.188.159.0/24 ip4:64.12.136.0/23 ip4:64.12.138.0/24 ip4:64.12.143.99/32 ip4:64.12.143.100/32 ip4:64.12.143.101/32 ptr:mx.aol.com ?all aol.com descriptive text spf2.0/pra ip4:152.163.225.0/24 ip4:205.188.139.0/24 ip4:205.188.144.0/24 ip4:205.188.156.0/23 ip4:205.188.159.0/24 ip4:64.12.136.0/23 ip4:64.12.138.0/24 ip4:64.12.143.99/32 ip4:64.12.143.100/32 ip4:64.12.143.101/32 ptr:mx.aol.com ?all There's no router blocking DNS TCP requests on that machine, yet python- policyd-spf still fails on the machine getting the TXT records shown above with this message: Mar 14 11:24:39 ldc1042 policyd-spf[8298]: SPF Temporary Error: DNS Ran off end of data:Mail From client-ip=64.12.138.200; helo=imr-m06.mx.aol.com; [EMAIL PROTECTED]; [EMAIL PROTECTED]; It's as if it's not trying TCP at all -- just failing on the UDP request. I apologize for confusing the issue with the DNS Timeout message on the second machine behind the router (www.commspeak.com). Are you using python-policyd-spf and getting AOL messages without problems? For now, all messages from all AOL addresses are rejected (temporarily, over and over again) if I enable python-policyd-spf. Thank you, John -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 163116] Re: libsmbclient: upgrade fails with error 403
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 just the Samba update. -- libsmbclient: upgrade fails with error 403 https://bugs.launchpad.net/bugs/163116 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106689] Solved by not using random password
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 already configured https://bugs.launchpad.net/bugs/106689 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
